MOXy @XmlPath ignored?

The most likely cause of this issue is that you are missing the jaxb. Properties file to specify that EclipseLink MOXy should be used as the JAXB provider. The jaxb.

Properties file must be placed in the same package as your domain model and contain the following entry.

The most likely cause of this issue is that you are missing the jaxb. Properties file to specify that EclipseLink MOXy should be used as the JAXB provider. The jaxb.

Properties file must be placed in the same package as your domain model and contain the following entry: javax.xml.bind.context. Factory=org.eclipse.persistence.jaxb. JAXBContextFactory For More Information: bdoughan.blogspot.com/2011/05/specifying... bdoughan.blogspot.com/2010/09/xpath-base... bdoughan.blogspot.com/2011/03/map-to-ele....

Great honor being answered directly from "the source" :-). Yes, it was the jaxb. Properties file missing.

I performed some more test on these files, to confirm that I can have a different provider each package. Ok till I tried to marshal classes from different packages with JAXBContext. NewInstance(pkg1.

C1. Class, pkg2. C2.

Class)... but this is a pretty advanced issue. – AgostinoX May 10 at 22:46.

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.