|
Home > Archive > Apache Directory Project > April 2006 > [naming] XmlConfigurator and element order
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
[naming] XmlConfigurator and element order
|
|
| Jeff Lansing 2006-02-14, 5:45 pm |
| Hi,
I thought it would be useful to chain MINA IoFilters together using JNDI,
something like this:
<?xml version="1.0" encoding="UTF-8"?>
<naming>
<context>
<resource name="ibs/session/chain"
type="xtcf.ibs.session.DefaultIoFilterChainBuilder">
<parameter>
<name>factory</name>
<value>xtcf.ibs.session.IoFilterChainBuilderFactory</value>
</parameter>
<parameter>
<name>raw-logger</name>
<value>org.apache.mina.filter.LoggingFilter</value>
</parameter>
<parameter>
<name>raw-handler</name>
<value>xtcf.ibs.message.handler.RawMessageHandler</value>
</parameter>
<parameter>
<name>raw-message-codec</name>
<value>xtcf.ibs.message.handler.RawCodecFilter</value>
</parameter>
<parameter>
<name>parser-logger</name>
<value>org.apache.mina.filter.LoggingFilter</value>
</parameter>
<parameter>
<name>xml-handler</name>
<value>xtcf.ibs.message.handler.XMLMessageHandler</value>
</parameter>
<parameter>
<name>xml-logger</name>
<value>org.apache.mina.filter.LoggingFilter</value>
</parameter>
<parameter>
<name>jms-handler</name>
<value>xtcf.ibs.message.handler.JMSMessageHandler</value>
</parameter>
</resource>
</context>
</naming>
Unfortunately this doesn't work correctly because the XmlConfigurator
(actually the Config.Resource inner class) destroys the order of the
elements. I'm pretty sure that, although XML attributes are unordered, there
is an implied order to XML elements. Shouldn't this order be preserved?
Thanks,
Jeff
| |
| Brett Porter 2006-02-14, 5:45 pm |
| I assume this is because it uses a HashMap to store parameters. I
would think it is unusual to use resource parameters for this purpose.
Usually I used a set or parameters retrieved as a list instead.
However, you could file a bug to ask that the order in the map be preserved=
..
- Brett
On 2/15/06, Jeff Lansing <jlansing-6PsT7PARKNC5jOOfXgogbA@public.gmane.org> wrote:
>
>
>
> Hi,
>
>
>
> I thought it would be useful to chain MINA IoFilters together using JNDI,
> something like this:
>
> <?xml version=3D"1.0" encoding=3D"UTF-8"?>
>
> <naming>
>
> <context>
>
> <resource name=3D"ibs/session/chain"
> type=3D"xtcf.ibs.session.DefaultIoFilterChainBuilder">
>
> <parameter>
>
> <name>factory</name>
>
>
> <value>xtcf.ibs.session.IoFilterChainBuilderFactory</value>
>
> </parameter>
>
> <parameter>
>
> <name>raw-logger</name>
>
> <value>org.apache.mina.filter.LoggingFilter</value>
>
> </parameter>
>
> <parameter>
>
> <name>raw-handler</name>
>
>
> <value>xtcf.ibs.message.handler.RawMessageHandler</value>
>
> </parameter>
>
> <parameter>
>
> <name>raw-message-codec</name>
>
>
> <value>xtcf.ibs.message.handler.RawCodecFilter</value>
>
> </parameter>
>
> <parameter>
>
> <name>parser-logger</name>
>
> <value>org.apache.mina.filter.LoggingFilter</value>
>
> </parameter>
>
> <parameter>
>
> <name>xml-handler</name>
>
>
> <value>xtcf.ibs.message.handler.XMLMessageHandler</value>
>
> </parameter>
>
> <parameter>
>
> <name>xml-logger</name>
>
> <value>org.apache.mina.filter.LoggingFilter</value>
>
> </parameter>
>
> <parameter>
>
> <name>jms-handler</name>
>
>
> <value>xtcf.ibs.message.handler.JMSMessageHandler</value>
>
> </parameter>
>
> </resource>
>
> </context>
>
> </naming>
>
> Unfortunately this doesn't work correctly because the XmlConfigurator
> (actually the Config.Resource inner class) destroys the order of the
> elements. I'm pretty sure that, although XML attributes are unordered, th=
ere
> is an implied order to XML elements. Shouldn't this order be preserved?
>
>
>
> Thanks,
>
>
>
> Jeff
| |
| Trustin Lee 2006-04-24, 7:56 am |
| Hi Jeff,
I'm terribly sorry for this slooooooow response. Please reply if you still
have an interest. Is this issue fixed? Did you post a JIRA issue related
with this?
Thanks,
Trustin
On 2/15/06, Jeff Lansing <jlansing-6PsT7PARKNC5jOOfXgogbA@public.gmane.org> wrote:
>
> Hi,
>
>
>
> I thought it would be useful to chain MINA IoFilters together using JNDI,
> something like this:
>
> <?xml version="1.0" encoding="UTF-8"?>
>
> <naming>
>
> <context>
>
> <resource name="ibs/session/chain" type="
> xtcf.ibs.session.DefaultIoFilterChainBuilder">
>
> <parameter>
>
> <name>factory</name>
>
> <value>xtcf.ibs.session.IoFilterChainBuilderFactory</value>
>
> </parameter>
>
> <parameter>
>
> <name>raw-logger</name>
>
> <value>org.apache.mina.filter.LoggingFilter</value>
>
> </parameter>
>
> <parameter>
>
> <name>raw-handler</name>
>
> <value>xtcf.ibs.message.handler.RawMessageHandler</value>
>
> </parameter>
>
> <parameter>
>
> <name>raw-message-codec</name>
>
> <value>xtcf.ibs.message.handler.RawCodecFilter</value>
>
> </parameter>
>
> <parameter>
>
> <name>parser-logger</name>
>
> <value>org.apache.mina.filter.LoggingFilter</value>
>
> </parameter>
>
> <parameter>
>
> <name>xml-handler</name>
>
> <value>xtcf.ibs.message.handler.XMLMessageHandler</value>
>
> </parameter>
>
> <parameter>
>
> <name>xml-logger</name>
>
> <value>org.apache.mina.filter.LoggingFilter</value>
>
> </parameter>
>
> <parameter>
>
> <name>jms-handler</name>
>
> <value>xtcf.ibs.message.handler.JMSMessageHandler</value>
>
> </parameter>
>
> </resource>
>
> </context>
>
> </naming>
>
> Unfortunately this doesn't work correctly because the XmlConfigurator
> (actually the Config.Resource inner class) destroys the order of the
> elements. I'm pretty sure that, although XML attributes are unordered, there
> is an implied order to XML elements. Shouldn't this order be preserved?
>
>
>
> Thanks,
>
>
>
> Jeff
>
--
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP key fingerprints:
* E167 E6AF E73A CBCE EE41 4A29 544D DE48 FE95 4E7E
* B693 628E 6047 4F8F CFA4 455E 1C62 A7DC 0255 ECA6
|
|
|
|
|