-
1. Re: Possible problem with bean-deployer_2_0.xsd
dmlloyd Nov 6, 2008 11:58 AM (in response to dmlloyd)By the way, validating it (second-hand via my contact at JetBrains) with another tool produces marginally more useful output:
SystemID: D:\LloydsXSD\bean-deployer_2_0.xsd Location: 139:36 Description: rcase-RecurseLax.2: There is not a complete functional mapping between the particles. URL: http://www.w3.org/TR/xmlschema-1/#rcase-RecurseLax SystemID: D:\LloydsXSD\bean-deployer_2_0.xsd Location: 139:36 Description: src-redefine.6.2.2: Group 'valueGroup' does not properly restrict the group it redefines; constraint violated: 'rcase-RecurseLax.2'. URL: http://www.w3.org/TR/xmlschema-1/#src-redefine
-
2. Re: Possible problem with bean-deployer_2_0.xsd
adrian.brock Nov 6, 2008 12:14 PM (in response to dmlloyd)I don't read alienese and the error messages aren't very helpful.
But I'd guess from this link (see the table) that you are not allowed to
derive a choice from a choice except under very specific circumstances?
http://www.w3.org/TR/xmlschema-1/#cos-particle-restrict
If that's true, its kind of stupid since both choice groups are identical. ;-)
But the obvious fix would be to not redefine the choice group and just
specify it explicitly in bean-deployer-2.0.xsd.
Its exactly the same definition so we aren't actually gaining anything
from the redefine that I can see? -
3. Re: Possible problem with bean-deployer_2_0.xsd
adrian.brock Nov 6, 2008 12:23 PM (in response to dmlloyd)"adrian@jboss.org" wrote:
But I'd guess from this link (see the table) that you are not allowed to
derive a choice from a choice except under very specific circumstances?
http://www.w3.org/TR/xmlschema-1/#cos-particle-restrict
From that link:
One of the following must be true:
2.2.1 {particles} is empty and the particle within which this <choice> appears has {min occurs} of 0.
2.2.2 All of the following must be true:
2.2.2.1 The particle within which this <choice> appears has {max occurs} and {min occurs} of 1.
...
This isn't true for baseCollectionType which has an unbounded choice<xsd:complexType name="baseCollectionType"> <xsd:choice minOccurs="0" maxOccurs="unbounded"> <xsd:group ref="valueGroup"/> </xsd:choice> ...
-
4. Re: Possible problem with bean-deployer_2_0.xsd
dmlloyd Nov 6, 2008 2:00 PM (in response to dmlloyd)In any case this doesn't look like the source of the IDEA problem after all (they're still researching it though)...
-
5. Re: Possible problem with bean-deployer_2_0.xsd
dmlloyd Nov 30, 2008 10:40 AM (in response to dmlloyd)Ah, they found the issue. It's a bug in IDEA, and it has been fixed in their recent 8.0.1 release. Hooray
-
6. Re: Possible problem with bean-deployer_2_0.xsd
alesj Nov 30, 2008 3:54 PM (in response to dmlloyd)"david.lloyd@jboss.com" wrote:
and it has been fixed in their recent 8.0.1 release. Hooray
It works like a charm. Finally! :-) -
7. Re: Possible problem with bean-deployer_2_0.xsd
wolfgangknauf Jun 16, 2009 3:47 PM (in response to dmlloyd)Same problem for Eclipse 3.4.2/WebTools 3.0.4 (which uses Xerces 2.9.0 for validation as far as I know).
Any plans to change something on the JBoss side? I don't know whether the error message is correct or not.
Thanks
Wolfgang -
8. Re: Possible problem with bean-deployer_2_0.xsd
aloubyansky Jun 29, 2009 8:43 AM (in response to dmlloyd)I commented on the errors some time ago here
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223327
If it's still not fixed it should be. -
9. Re: Possible problem with bean-deployer_2_0.xsd
wolfgangknauf Jul 1, 2009 6:26 AM (in response to dmlloyd)The validation error is also in JIRA as part of https://jira.jboss.org/jira/browse/JBMICROCONT-446
Wolfgang