[ 
https://issues.apache.org/jira/browse/XMLBEANS-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462642
 ] 

Radu Preotiuc-Pietro commented on XMLBEANS-308:
-----------------------------------------------

Actually, the main consideration surrounding our use of jsr173 is of a legal 
nature.

jsr173_1.0_api.jar is what we have the legal go-ahead to use and I remember it 
was a long process to get this smoothed out and get Cliff's blessing.

So first question I would ask: where and how is stax-api-1.0.1.jar distributed 
and what other Apache projects are using it? If this is something that is used 
widely inside Apache, we would be happy to get XmlBeans aligned.


> jsr173_1.0_api.jar should be removed from dependencies in favor of 
> stax-api-1.0.1.jar
> -------------------------------------------------------------------------------------
>
>                 Key: XMLBEANS-308
>                 URL: https://issues.apache.org/jira/browse/XMLBEANS-308
>             Project: XMLBeans
>          Issue Type: Improvement
>    Affects Versions: unspecified, Version 2.1, Version 2.2
>            Reporter: Jeff Peterson
>
> jsr173_1.0_api.jar contains known bugs in the specification.
> See: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6306251
> While this problem does not directly affect the XmlBeans project, it can 
> cause class loader problems if someone needs to use newer versions of the 
> javax.stream api.  Please update XmlBeans distirbutions to include the 
> less-buggy stax-api-1.0.1.jar instead, especially in the maven/maven2 
> repositories.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to