You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jaxme-dev@ws.apache.org by ja...@ws.apache.org on 2004/09/11 15:27:37 UTC

[jira] Created: (JAXME-34) Mixed complex types without a particle

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JAXME-34

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

     Status: Unassigned
   Priority: Minor

    Project: JaxMe
 Components: 
             JaxMeXS
   Versions:
             current (nightly)

   Assignee: 
   Reporter: Mik Lernout

    Created: Sat, 11 Sep 2004 6:25 AM
    Updated: Sat, 11 Sep 2004 6:25 AM
Environment: n.a.

Description:
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.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org


[jira] Commented: (JAXME-34) Mixed complex types without a particle

Posted by ja...@ws.apache.org.
The following comment has been added to this issue:

     Author: Mik Lernout
    Created: Mon, 13 Sep 2004 2:46 AM
       Body:
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:
  http://issues.apache.org/jira/browse/JAXME-34?page=comments#action_53066

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JAXME-34

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
 Components: 
             JaxMeXS
   Versions:
             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.

Description:
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.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org


[jira] Closed: (JAXME-34) Mixed complex types without a particle

Posted by ja...@ws.apache.org.
Message:

   The following issue has been closed.

   Resolver: Jochen Wiedmann
       Date: Mon, 13 Sep 2004 12:25 PM

Patch integrated in 0.3 and HEAD. See also
http://lists.w3.org/Archives/Public/xmlschema-dev/2004Sep/0039.html

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JAXME-34

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

     Status: Closed
   Priority: Minor
 Resolution: FIXED

    Project: JaxMe
 Components: 
             JaxMeXS
   Versions:
             current (nightly)

   Assignee: Jochen Wiedmann
   Reporter: Mik Lernout

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

Description:
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.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org


[jira] Updated: (JAXME-34) Mixed complex types without a particle

Posted by ja...@ws.apache.org.
The following issue has been updated:

    Updater: Mik Lernout (mailto:mik@futurestreet.org)
       Date: Sat, 11 Sep 2004 6:28 AM
    Comment:
The patch that will fix the bug
    Changes:
             Attachment changed to mixed-type-without-elements.patch
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/JAXME-34?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JAXME-34

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

     Status: Unassigned
   Priority: Minor

    Project: JaxMe
 Components: 
             JaxMeXS
   Versions:
             current (nightly)

   Assignee: 
   Reporter: Mik Lernout

    Created: Sat, 11 Sep 2004 6:25 AM
    Updated: Sat, 11 Sep 2004 6:28 AM
Environment: n.a.

Description:
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.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org


[jira] Updated: (JAXME-34) Mixed complex types without a particle

Posted by ja...@ws.apache.org.
The following issue has been updated:

    Updater: Mik Lernout (mailto:mik@futurestreet.org)
       Date: Sat, 11 Sep 2004 6:27 AM
    Comment:
The XML Schema that exposes the test
    Changes:
             Attachment changed to attgD005.xsd
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/JAXME-34?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JAXME-34

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

     Status: Unassigned
   Priority: Minor

    Project: JaxMe
 Components: 
             JaxMeXS
   Versions:
             current (nightly)

   Assignee: 
   Reporter: Mik Lernout

    Created: Sat, 11 Sep 2004 6:25 AM
    Updated: Sat, 11 Sep 2004 6:27 AM
Environment: n.a.

Description:
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.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org