-
1. Re: xbean won't validate in Eclipse - No declaration ca be found for jms:endpoi
ubhole Mar 3, 2009 8:56 AM (in response to nicolas-duminil)Can you provide a full xbean? I tried using archetype and it does validate and builds correctly for me.
-
2. Re: xbean won't validate in Eclipse - No declaration ca be found for jms:en
scranton_scranton Mar 6, 2009 11:13 AM (in response to nicolas-duminil)Nicolas,
Is the full validation error something like
cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'jms:enpoint'
If so, I believe its because, as the error says, the Eclipse validator is in strict mode, and the servicemix-jms schema has
<xs:any namespace='##other' minOccurs='0' maxOccurs='unbounded'/>
references that allow other elements (e.g. child bean references) within the jms:endpoint. The problem is that if you don't have a child that matches this entry than strictly speaking its not valid.
If the Schema xs:any entry had a processContents='lax' attribute, than the validation error goes away.
Everything works correctly, but I agree that its very annoying to have errors flags in your project.
As a short term work around you can download the offending schma, add the processContents='lax' attribute to the various xs:any childern, and update your Eclipse | Preferences | XML Catalog to use your modified version. Obviously not a good long term fix - that will probably entail changes to the release schema - but it will make those very annoying 'false positive' validation errors to go away.
I'm attaching a modified version of the servicemix-saxon xsd for reference.
Hope this helps,
Scott
-
servicemix-saxon-2008.01.xsd 13.7 KB
-