ws-jaxme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (JAXME-34) Mixed complex types without a particle
Date Mon, 13 Sep 2004 09:46:38 GMT
The following comment has been added to this issue:

     Author: Mik Lernout
    Created: Mon, 13 Sep 2004 2:46 AM
Well, I could not find anything in the specs that actually comment on that. The complex type
can only contain a simple content type, but if we do it the way you propose than the jaxme
content model does not reflect the XML Schema. 
I'm not a great supporter of this kind of behaviour (see also substitution groups that become
choice groups) but there are precedents in the code already.
Also: there is nothing that the interface of simpleContent can add, as there is no more information
on what the simple content ought to be...

All in all: I prefer the patch as supplied: it is correct, simple, doesn't spread confusion.
View this comment:

View the issue:

Here is an overview of the issue:
        Key: JAXME-34
    Summary: Mixed complex types without a particle
       Type: Bug

     Status: Open
   Priority: Minor

    Project: JaxMe
             current (nightly)

   Assignee: Jochen Wiedmann
   Reporter: Mik Lernout

    Created: Sat, 11 Sep 2004 6:25 AM
    Updated: Mon, 13 Sep 2004 2:46 AM
Environment: n.a.

When parsing a complex type that is set to have mixed content, and there is no particle defined,
JaxMeXS assumes the content is empty instead of mixed.

I uncovered this when I was testing JaxMe XS against the Microsoft test in the XML Schema
Test Collection in the file /msxsdtest/attributeGroup/attgD005.xsd. I will attach it to this
bug for reference, together with a patch that will fix it.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message