This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I am trying to set up JAXB to build classes when my eclipse builds. Another project here has this set up by an ex-employee but we need to update it to a more recent version. I think I am doing the equivalent of everything he did, but I keep getting warnings (and other errors) like the following:
I have confirmed that I can reach the url. The offending tag in my xsd is:
Yes. Updating JAXB. The third complaint of the error message (that it doesn't start with <xsd:schema>, is true. The file at the end of that URL starts with <xs:schema> not xsd. It seems like that little 'd' might be the source of my problems. But why does the XML parser think that is appropriate? I see nothing in my project or any xsd file that attempts to create an xsd namespace. In fact, a text search of my entire project confirms that xsd only occurs as file name suffixes, and in comments. The URL it blows up on is in a schema I downloaded that defines the Atom feed, and is publicly in use, and the reference it blows up on is public, from w3c.
I saw some forum posts implying that there was a validation bug in past versions, but I am updating to 2.2.1.