You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xmlbeans.apache.org by "Ian P. Springer (JIRA)" <xm...@xml.apache.org> on 2005/01/31 18:01:19 UTC

[jira] Created: (XMLBEANS-105) NPE while initializing a type system w/ a type that extends an a complex type from a different type system

NPE while initializing a type system w/ a type that extends an a complex type from a different type system
----------------------------------------------------------------------------------------------------------

         Key: XMLBEANS-105
         URL: http://issues.apache.org/jira/browse/XMLBEANS-105
     Project: XMLBeans
        Type: Bug
    Versions: Version 1    
 Environment: n/a
    Reporter: Ian P. Springer
 Attachments: stacktrace.txt, xmlbeans-bug.zip

This bug occurs w/ v1.0.3, as well as w/ v1 SVN top-of-tree.

It occurs in the following situation:

- schema A defines type A, which is a complex type containing a sequence of one anon complex types. schema A is xmlbeans-compiled into A.jar

- schema B contains type B which extends type A. it also defines an element of type B. schema B is compiled into B.jar, passing A.jar into scomp's classpath option

- B.xml is an instance doc containing a document element of type B

- when we try to parse() B.xml, w/ A.jar and B.jar in the JVM classpath, we get a big stack trace w/ a root cause of an NPE during type system initialization (see the attached stack trace)


-- 
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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org


[jira] Commented: (XMLBEANS-105) NPE while initializing a type system w/ a type that extends an a complex type from a different type system

Posted by "Ian P. Springer (JIRA)" <xm...@xml.apache.org>.
     [ http://issues.apache.org/jira/browse/XMLBEANS-105?page=comments#action_58574 ]
     
Ian P. Springer commented on XMLBEANS-105:
------------------------------------------

I verified the fix. Thanks for the super fast turnaround!

I have one more request. Would you please post current 1.0.4 SNAPSHOTs of xbean.jar and xbean_xpath.jar to http://www.apache.org/dist/java-repository/xmlbeans/jars/?

Thanks,
Ian


> NPE while initializing a type system w/ a type that extends an a complex type from a different type system
> ----------------------------------------------------------------------------------------------------------
>
>          Key: XMLBEANS-105
>          URL: http://issues.apache.org/jira/browse/XMLBEANS-105
>      Project: XMLBeans
>         Type: Bug
>     Versions: Version 1
>  Environment: n/a
>     Reporter: Ian P. Springer
>     Assignee: Jacob Danner
>      Fix For: Version 1.0.4 (jdk1.3 port), Version 1.0.4, Version 2
>  Attachments: stacktrace.txt, xmlbeans-bug.zip
>
> This bug occurs w/ v1.0.3, as well as w/ v1 SVN top-of-tree.
> It occurs in the following situation:
> - schema A defines type A, which is a complex type containing a sequence of one anon complex types. schema A is xmlbeans-compiled into A.jar
> - schema B contains type B which extends type A. it also defines an element of type B. schema B is compiled into B.jar, passing A.jar into scomp's classpath option
> - B.xml is an instance doc containing a document element of type B
> - when we try to parse() B.xml, w/ A.jar and B.jar in the JVM classpath, we get a big stack trace w/ a root cause of an NPE during type system initialization (see the attached stack trace)

-- 
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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org


[jira] Updated: (XMLBEANS-105) NPE while initializing a type system w/ a type that extends an a complex type from a different type system

Posted by "Ian P. Springer (JIRA)" <xm...@xml.apache.org>.
     [ http://issues.apache.org/jira/browse/XMLBEANS-105?page=history ]

Ian P. Springer updated XMLBEANS-105:
-------------------------------------

    Attachment: xmlbeans-bug.zip

This test case demonstrates the bug. A xerces.jar and a v1 xbean.jar are not included, but are required to run the test.


> NPE while initializing a type system w/ a type that extends an a complex type from a different type system
> ----------------------------------------------------------------------------------------------------------
>
>          Key: XMLBEANS-105
>          URL: http://issues.apache.org/jira/browse/XMLBEANS-105
>      Project: XMLBeans
>         Type: Bug
>     Versions: Version 1
>  Environment: n/a
>     Reporter: Ian P. Springer
>  Attachments: stacktrace.txt, xmlbeans-bug.zip
>
> This bug occurs w/ v1.0.3, as well as w/ v1 SVN top-of-tree.
> It occurs in the following situation:
> - schema A defines type A, which is a complex type containing a sequence of one anon complex types. schema A is xmlbeans-compiled into A.jar
> - schema B contains type B which extends type A. it also defines an element of type B. schema B is compiled into B.jar, passing A.jar into scomp's classpath option
> - B.xml is an instance doc containing a document element of type B
> - when we try to parse() B.xml, w/ A.jar and B.jar in the JVM classpath, we get a big stack trace w/ a root cause of an NPE during type system initialization (see the attached stack trace)

-- 
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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org


[jira] Resolved: (XMLBEANS-105) NPE while initializing a type system w/ a type that extends an a complex type from a different type system

Posted by "Kevin Krouse (JIRA)" <xm...@xml.apache.org>.
     [ http://issues.apache.org/jira/browse/XMLBEANS-105?page=history ]
     
Kevin Krouse resolved XMLBEANS-105:
-----------------------------------

      Assign To: Jacob Danner
     Resolution: Fixed
    Fix Version: Version 1.0.4
                 Version 1.0.4 (jdk1.3 port)
                 Version 2

I'm suprised we didn't run into this earlier.  Should be fixed now.

> NPE while initializing a type system w/ a type that extends an a complex type from a different type system
> ----------------------------------------------------------------------------------------------------------
>
>          Key: XMLBEANS-105
>          URL: http://issues.apache.org/jira/browse/XMLBEANS-105
>      Project: XMLBeans
>         Type: Bug
>     Versions: Version 1
>  Environment: n/a
>     Reporter: Ian P. Springer
>     Assignee: Jacob Danner
>      Fix For: Version 2, Version 1.0.4, Version 1.0.4 (jdk1.3 port)
>  Attachments: stacktrace.txt, xmlbeans-bug.zip
>
> This bug occurs w/ v1.0.3, as well as w/ v1 SVN top-of-tree.
> It occurs in the following situation:
> - schema A defines type A, which is a complex type containing a sequence of one anon complex types. schema A is xmlbeans-compiled into A.jar
> - schema B contains type B which extends type A. it also defines an element of type B. schema B is compiled into B.jar, passing A.jar into scomp's classpath option
> - B.xml is an instance doc containing a document element of type B
> - when we try to parse() B.xml, w/ A.jar and B.jar in the JVM classpath, we get a big stack trace w/ a root cause of an NPE during type system initialization (see the attached stack trace)

-- 
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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org


[jira] Commented: (XMLBEANS-105) NPE while initializing a type system w/ a type that extends an a complex type from a different type system

Posted by "Ian P. Springer (JIRA)" <xm...@xml.apache.org>.
     [ http://issues.apache.org/jira/browse/XMLBEANS-105?page=comments#action_58318 ]
     
Ian P. Springer commented on XMLBEANS-105:
------------------------------------------

Note, using the attached test case, I confirmed that this bug exists only in v1 (i.e. it does not occur w/ v2).


> NPE while initializing a type system w/ a type that extends an a complex type from a different type system
> ----------------------------------------------------------------------------------------------------------
>
>          Key: XMLBEANS-105
>          URL: http://issues.apache.org/jira/browse/XMLBEANS-105
>      Project: XMLBeans
>         Type: Bug
>     Versions: Version 1
>  Environment: n/a
>     Reporter: Ian P. Springer
>  Attachments: stacktrace.txt, xmlbeans-bug.zip
>
> This bug occurs w/ v1.0.3, as well as w/ v1 SVN top-of-tree.
> It occurs in the following situation:
> - schema A defines type A, which is a complex type containing a sequence of one anon complex types. schema A is xmlbeans-compiled into A.jar
> - schema B contains type B which extends type A. it also defines an element of type B. schema B is compiled into B.jar, passing A.jar into scomp's classpath option
> - B.xml is an instance doc containing a document element of type B
> - when we try to parse() B.xml, w/ A.jar and B.jar in the JVM classpath, we get a big stack trace w/ a root cause of an NPE during type system initialization (see the attached stack trace)

-- 
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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org


[jira] Updated: (XMLBEANS-105) NPE while initializing a type system w/ a type that extends an a complex type from a different type system

Posted by "Ian P. Springer (JIRA)" <xm...@xml.apache.org>.
     [ http://issues.apache.org/jira/browse/XMLBEANS-105?page=history ]

Ian P. Springer updated XMLBEANS-105:
-------------------------------------

    Attachment: stacktrace.txt

This is the stack trace that is printed by XmlBeans when the NPE occurs.


> NPE while initializing a type system w/ a type that extends an a complex type from a different type system
> ----------------------------------------------------------------------------------------------------------
>
>          Key: XMLBEANS-105
>          URL: http://issues.apache.org/jira/browse/XMLBEANS-105
>      Project: XMLBeans
>         Type: Bug
>     Versions: Version 1
>  Environment: n/a
>     Reporter: Ian P. Springer
>  Attachments: stacktrace.txt, xmlbeans-bug.zip
>
> This bug occurs w/ v1.0.3, as well as w/ v1 SVN top-of-tree.
> It occurs in the following situation:
> - schema A defines type A, which is a complex type containing a sequence of one anon complex types. schema A is xmlbeans-compiled into A.jar
> - schema B contains type B which extends type A. it also defines an element of type B. schema B is compiled into B.jar, passing A.jar into scomp's classpath option
> - B.xml is an instance doc containing a document element of type B
> - when we try to parse() B.xml, w/ A.jar and B.jar in the JVM classpath, we get a big stack trace w/ a root cause of an NPE during type system initialization (see the attached stack trace)

-- 
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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org


[jira] Closed: (XMLBEANS-105) NPE while initializing a type system w/ a type that extends an a complex type from a different type system

Posted by "Jacob Danner (JIRA)" <xm...@xml.apache.org>.
     [ http://issues.apache.org/jira/browse/XMLBEANS-105?page=all ]
     
Jacob Danner closed XMLBEANS-105:
---------------------------------


Fix Verified, closing

> NPE while initializing a type system w/ a type that extends an a complex type from a different type system
> ----------------------------------------------------------------------------------------------------------
>
>          Key: XMLBEANS-105
>          URL: http://issues.apache.org/jira/browse/XMLBEANS-105
>      Project: XMLBeans
>         Type: Bug
>     Versions: Version 1
>  Environment: n/a
>     Reporter: Ian P. Springer
>     Assignee: Jacob Danner
>      Fix For: Version 2, Version 1.0.4, Version 1.0.4 (jdk1.3 port)
>  Attachments: stacktrace.txt, xmlbeans-bug.zip
>
> This bug occurs w/ v1.0.3, as well as w/ v1 SVN top-of-tree.
> It occurs in the following situation:
> - schema A defines type A, which is a complex type containing a sequence of one anon complex types. schema A is xmlbeans-compiled into A.jar
> - schema B contains type B which extends type A. it also defines an element of type B. schema B is compiled into B.jar, passing A.jar into scomp's classpath option
> - B.xml is an instance doc containing a document element of type B
> - when we try to parse() B.xml, w/ A.jar and B.jar in the JVM classpath, we get a big stack trace w/ a root cause of an NPE during type system initialization (see the attached stack trace)

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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