CXF JAXB JAXBEncoderDecoder unmarshalling error : unexpected element when having qualified elements?

I've seen some similar issues with package-info's not being picked up properly there.

I've seen some similar issues with package-info's not being picked up properly there. Another option could be to add the -xjc-npa flag to the wsdl2java command to have it not use the package-info at all and stick the namespaces in all the other places.

1 Thank you very much indeed for your help. This not only that solved the problem I had with 'unexpected element' error when elements of response are prefixed with namespace but also fixed another problem I had with wsdl2java not creating the 'namespace' attribute for @XmlType annotation in the generated java classes. I run my application as a standalone application in JVM and have a custom class loader which loads the classes generated by wsdl2java.

I could see that package-info. Java is loaded by the class loader but the namespace attribute from package was for @XmlSchema not for @XmlType – john Jun 3 at 7:04.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.