Marcus Crafter wrote:
> Nice, it's a little more elaborate and I like it.
>
> Multiple argument constructors could be done with Parameters:
>
> <entry name="server" type="our.server.class.name">
> <Parameter value="our.machine.name"/>
> <Parameter value="our.machine.port"/>
> </entry>
>
> (hmm.. but is the parsing order guarenteed ?)
>
> Representing non-string constants is a little tough though
> (eg. does value="1" mean the string "1" or the integer value 1 ?).
>
> One would almost have to follow something like JNI's representation
> for objects, eg. value="java/lang/String|14" which isn't so nice, or
> drop non-string values alltogether. Supporting non-primitive argument
> types is another issue alltogether. :(
In the our.machine.port example, if the entry type was
"java.lang.Integer" (as it would have to be for contexts)
it would work.
Also, the parsing order follows the same semantics as the XML parsing
order. So the answer is yes.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
