To the best of my knowledge, this is a recent addition, and I imagine
an unintneded consequence. I know of no way to alter its behavior.
One of the Castor XML guys will have to tell you if, at the time they
wrote the multivalue stuff, they thought of adding a flag to the
field entry that allows you to disable multivalue... And if they
didn't, file a bug on XML as a blocker for 0.9.9.
My only *immediate* thought is that maybe you can get away with
confusing it by telling it that the value "bbb" and "ccc" pointed to
by the referenced information isn't a primitive... configure it with
java.lang.String instead of string, and hope to blind it; I imagine
it can only do multivalue on primitive values, and you can probably
trick the system into believing it's got a complex mapping instead.
If that works as a workaround, be sure and file that with the bug -
they may choose to document, rather than fix it.
On 3 Aug 2005, at 15:14, Shuai Zhang wrote:
Thanks for your suggestion :)
May we'll try this method if my problem really can't be resolved by
mapping file.
Question below is a little different from the original one.
The input xml is:
<Foo>
<name name="aaa"/>
<value value="bbb"/>
<value value="ccc"/>
</Foo>
But the output file is:
<Foo>
<name name="aaa"/>
<value value="bbb ccc"/>
</Foo>
They are not exactly the same and we think this is not acceptable
Do you think this problem can be resolved?
-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
