Jaxb is responsible for this and it is the normal behaviour. I read once
why they do it. I think
it has to do with the fact that you can this way feed a collection class
into it that behaving differently than the expected one.
So for example jaxb makes sure you have an ArrayList implementation.
It is not so bad though as you can easily clear the collection and add
all items of a given collection into it.
At the start I did not like this behaviour but now I think it is quite good.
Christian
Am 04.05.2011 12:37, schrieb srinivas thallapalli:
In mywebservice operation which takes java.util.List type, with wsdl2java
generated code the xxxxRequest.java file does not contain set method for
that property?. Can anybody please explain
why the setter method not generated.
Thanks
--
View this message in context:
http://cxf.547215.n5.nabble.com/wsdl2java-code-generation-tp4369470p4369470.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Christian Schneider
http://www.liquid-reality.de
CXF and Camel Architect
SOPERA - The Application Integration Division of Talend
http://www.talend.com
