jibx

Spring WS + JIBX “No adapter for endpoint” Error

柔情痞子 提交于 2019-11-28 11:48:37
问题 I use JIBX to create my entity classes from XSD files. It is configured in pom.xml and creates classes when I do a "maven: compile" I also use spring-ws. When I test my web service with SOAPUI I get the infamous error; "No adapter for endpoint GetTransactionsResponse getTransactions(GetTransactionsRequest), Is your endpoint annotated with @Endpoint, or does.." I checked all the threads here about that error but didn't help. I have one Parent.xsd and it imports 2 child xsd's. They are all in

Simple Java Xml to POJO mapping/binding?

谁都会走 提交于 2019-11-28 10:05:50
I'm trying to figure out the simplest way to map an xml file to to a plain old java object. Note: That in my example the xml doesn't quite match up with my intended POJO. ///////// THE XML <?xml version="1.0" encoding="UTF-8"?> <Animal> <standardName> <Name>Cat</Name> </standardName> <standardVersion> <VersionIdentifier>V02.00</VersionIdentifier> </standardVersion> </Animal> ////// THE INTENDED POJO class Animal { private String name; private String versionIdentifier; } Regular JAXB (with annotations) won't work as the JAXM Element name annotations don't allow me to specifiy nested elements.

JAXB - Creating modules for reuse

跟風遠走 提交于 2019-11-27 09:30:52
Does JAXB support modular code generation? Most of my background is with JibX for XML marshalling, but for legacy reasons our firm is using JAXB. One feature that was available for JIBX was modular code generation . Say I have a main schema but I have several different envelopes for that schema. With JibX I could create a jar file out of the JibX'ed core schema, and then in separate projects I could JibX my envelope schemas and simply point to the shared jar instead of having to duplicate the code generation of the core schemas for each envelope. I don't yet see a way for JAXB to handle this -

JAXB - Creating modules for reuse

无人久伴 提交于 2019-11-26 14:44:36
问题 Does JAXB support modular code generation? Most of my background is with JibX for XML marshalling, but for legacy reasons our firm is using JAXB. One feature that was available for JIBX was modular code generation. Say I have a main schema but I have several different envelopes for that schema. With JibX I could create a jar file out of the JibX'ed core schema, and then in separate projects I could JibX my envelope schemas and simply point to the shared jar instead of having to duplicate the