Community
Participate
Working Groups
.xjb is the recommended file extension for JAXB Bindings customizations, Eclipse should recognize these as XML files out of the box. -- Configuration Details -- Product: SpringSource Tool Suite 2.6.1.201105041000-RELEASE (com.springsource.sts.ide) Installed Features: org.eclipse.wst.xml_ui.feature 3.2.3.v201102160550-7H7AFUWDxumQJOi9ghcTb5YgkwEZ
Is the problem that Dali doesn't recognize these file types as JAXB bindings customization files, or that eclipse doesn't recognize .xjb files as xml extensions?
I'm not sure I understand your question. How can I check if Dali recognizes these files as JAXB bindings customizations?
What is the exact nature of the problem? Does the problem happen when attempting to edit .xjb files? That is - does the xml editor recognize them? Or are you talking about more specific JAXB use cases?
Maybe you could elaborate on how you found out that they're not already treated as XML files? And attach an example?
I expected that when I double-clicked a .xjb file, it would open in the XML Editor, but it opens in the plain Text Editor. Also, I checked Eclipse's XML Catalog and didn't find any entry for the http://java.sun.com/xml/ns/jaxb namespace.
I see what you are talking about now. Nitin, is this something that should go in WTP proper, seeing as I believe some packages do not pick up Dali functionality? I think the JAXB schema should likely go in jst common schemas. Not sure about the .xjb content type.
An example would be good. (In reply to comment #6) > I see what you are talking about now. > > Nitin, is this something that should go in WTP proper, seeing as I believe some > packages do not pick up Dali functionality? Would those packages be working with this file type, though? I would expect the formal association/content-type to come from Dali, but even then the XML header at the beginning of the file should cause it to be treated as XML by the platform.
It depends. We don't have any functionality that deals directly with this file type. I see that wst.xml has basic support for wsdl file types, even though there is a wsdl plugin. And I believe one of the reasons that some packages don't pick up Dali JAXB is that they have their own JAXB functionality. So, I guess I really am asking you. :)
We don't need a full-fledged .xjb content type, just to associate it with the xml content type.
So do we have a verdict here? If not, let's just define this in Dali for now and open a bug to move it to WTP proper. I don't want this to just sit in limbo.
Committed .xjb file association (with .xml content type) for M6. Waiting to see if we can still get JAXB bindings schema in.
I'll see if I can get the schema approved in time.
(In reply to comment #12) > I'll see if I can get the schema approved in time. This isn't going to happen. Deferring to next release.
Created attachment 214602 [details] patch Here's a patch for when we're ready.
IP request has been approved. http://dev.eclipse.org/ipzilla/show_bug.cgi?id=6427
Added for M2. But also logged a bug against WTP to move the schema to jst standard schemas. Bug 388007
