Hi,
I did some more work on this and discovered the following:
1) The CXF maven codegen plugin was not binding the generated java files.
2) I used the CXF maven codegen plugin to generate the source files from
the wsdl. Then jibx:bind to bind them. I ran a test and managed to
unmarshall and marshall an XML file successfully. This proves that JIBX is
configured ok.
3) I managed to set the data binding in the JAX-WS test case via the
JaxWsProxyFactoryBean class. This is a reference to my last message.
4) I then tried again to access the SOAP service but received the error
'Exception in thread "main" java.lang.RuntimeException:
org.jibx.runtime.JiBXException: Unable to access binding information for
class ... Make sure the binding has been compiled'. The offending class is
an enum - could this have anything to do with it?
I think there is something wrong with the way the CXF has set up its path
to the bindings files. Does anyone have any info to help? Thank you very
much in advance.
Best regards,
James
On 28 November 2012 15:24, James Annesley <ja...@annesley.net> wrote:
> Hi,
>
> I am trying to use CXF maven codegen plugin with my schema with some
> success. I am succeeding in configuring it for JIBX, generating the Java
> source and binding them.
>
> I am having trouble building a front end however. Using JAX-WS I receive
> the message "Unable to create JAXBContext". I have checked for JAX-WS JIBX
> binding annotations on the generated files. What else could be the problem
> and solution?
>
>
> James
>
------------------------------------------------------------------------------
Keep yourself connected to Go Parallel:
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
http://goparallel.sourceforge.net
_______________________________________________
jibx-users mailing list
jibx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-users
