There shouldn't be any problems. In my case, I had my JIBX stuff in a separate project that got included into my webapp so I had to provide a *.gwt.xml file in it's base folder and do an include in my main *.gwt.xml file but other than that everything "just worked".
I was working with RPC methods, passing my XML domain objects back and forth and converting them to XML on the server side without any gwt related problems. Now I should note that I had a little it of trouble with JIBX itself in terms of converting enums to XML but that isn't related to GWT and a benefit of JIBX is you can modify your java beans to your heart's content (as long as your mapping files reflect what needs to be converted) and I was able to solve any problems that way. Another thing to mention is that JIBX has relatively little in terms of validation in order to keep its conversion process light. But since it produces beans you could, in theory, use a jsr 303 implementation to do the validation annotations there (a bit of duplication from the XML schema but can't be helped at the moment). -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
