I'm sorry for multiple posts in row. I've made a mistake in previous post: "brake" instead of "break".
According to javadocs on @XmlSeeAlso commenting it out can break instantiation of JAXBContext but it could be easily worked around and doesn't affects my project. I am using list of all ObjectFactory classes to create JAXBContext. So JAXBContext has references for all classes generated by JAXB. On Dec 6, 1:42 pm, Alan <[EMAIL PROTECTED]> wrote: > Hi, Jason. > > Does commenting out @XmlSeeAlso affected on your xml binding? > I'm not jaxb guru, but I think it can brake marshalling of that class. > > On Oct 9, 9:01 am, jason <[EMAIL PROTECTED]> wrote: > > > The real problem is the @XmlSeeAlso. > > I commented it out from Paragarph.class. Gwt still report > > XmlElement eror for other classes. But the gwt compilation finished > > successfully. > > I hope commentting out @XmlSeeAlso does not effect my xml binding. > > > -jason --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
