No. There is no issue in putting JIBX *.java files in shared package. I use it in shared package without any issue. Make sure you r using JIBX 1.2.3
Deepak On Fri, Sep 16, 2011 at 5:49 PM, J.Ganesan <[email protected]>wrote: > Mike, > > Will there be any issue in putting the JIBX generated *.java files in > shared package ? If not, JIBX has a huge advantage. I tried to put the > *.java files from JAXB in shared package and I encountered a number > of compilation problems. > > J.Ganesan > www.DataStoreGwt.com > > On Sep 15, 8:23 pm, Maiku <[email protected]> wrote: > > Hi, > > > > If you are not totally tied to JAXB you may want to check out JIBX. I > > was successfully using the beans that it creates on both Server side > > and Client side. The way it marshals is by injecting information into > > the bytecode and this seems to allow GWT to still recognize the source > > of the beans as being the same as the compiled server object. > > > > I have since refactored to use RequestFactory so that this entire > > issue is moot but if you cannot then I highly recommend JIBX. > > > > - Mike > > -- > 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. > > -- 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.
