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/02 12:36:51 UTC

[jira] Closed: (JAXME-10) PATCH generated TypeHandler, Overly strict property/element ordering

Message:

   The following issue has been closed.

   Resolver: Jochen Wiedmann
       Date: Thu, 2 Sep 2004 3:36 AM

Thanks for pointing this out, Nacho! I am closing the report.

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

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JAXME-10
    Summary: PATCH generated TypeHandler, Overly strict property/element ordering
       Type: Bug

     Status: Closed
 Resolution: CANNOT REPRODUCE

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

   Assignee: 
   Reporter: Henrik Vendelbo

    Created: Sat, 1 Nov 2003 1:21 PM
    Updated: Thu, 2 Sep 2004 3:36 AM
Environment: Operating System: Other
Platform: Other

Description:
When I create a JAXB object and only set some of the properties I can marshall 
it without a problem, producing neat XML.

When I then try to unmarshal it I get an exception.

Apparently elements in the sequence must be set in that order, without 
skipping any so that for

<element name="prop1">
<element name="prop2">
<element name="prop3">

An object created and marshalled after setting 2 properties
object.setProp1
object.setProp2

will work fine when unmarshalling.

While
object.setProp1
object.setProp3

will bomb since one was skipped.

To fix it the xxTypeHandler generated code needs to relax the check by changing

switch (__state) {
  case 4:
    __state = 5;

to

switch (__state) {
  case 0:
  case 3:
  case 4:
    __state = 5;

(As far as I can tell, that is)


---------------------------------------------------------------------
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