> return errorMessage;
>
> }
>
>
>
> public void setErrorMessage(java.lang.String errorMessage) {
>
> this.errorMessage = errorMessage;
>
> }
>
>
>
> }
>
>
>
> And then you need Calendar – Date translation
>
>
011 11:14 AM
To: google-web-toolkit@googlegroups.com
Subject: Re: GWT RPC - WebServiceClient
We have exact same situation and it all works.
We use apache cxf as the communication between the GWT servlets and the
API layer on another server.
When the WSDLs are created for the apache cxf, we ge
We have exact same situation and it all works.
We use apache cxf as the communication between the GWT servlets and the API
layer on another server.
When the WSDLs are created for the apache cxf, we generate a client side jar
and include it in the GWT project. This allows us access to the java obje
I can't speak to the CXF issue but I use many JAXB generated objects
across GWT-RPC . The solution I used is detailed here: http://goo.gl/VK2JY
which strictly deals with JAXB annotations (extracting the annotations
into a separate jar).
If for some reason that doesn't suffice I've also had excelle
Like you, I read that it was possible but ran into the same issues. I
ended up having to strip down the generated classes to POJO, which
clearly reduces the advantages of using something like JAX-B in the
first place. My understanding is that there are some classes in
javax.xml that will never wo
