You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Jim Marino (JIRA)" <tu...@ws.apache.org> on 2006/05/13 19:51:09 UTC
[jira] Commented: (TUSCANY-362) Move StAX jars from server/lib to
common/lib
[ http://issues.apache.org/jira/browse/TUSCANY-362?page=comments#action_12383403 ]
Jim Marino commented on TUSCANY-362:
------------------------------------
This doesn't seem right as a long term solution since we should segregate the runtime's usage of StaX from application code since it is a common case where the runtime uses a different version/implementation than application code. I'm going to reopen this as an issue for post-M1
> Move StAX jars from server/lib to common/lib
> --------------------------------------------
>
> Key: TUSCANY-362
> URL: http://issues.apache.org/jira/browse/TUSCANY-362
> Project: Tuscany
> Type: Bug
> Components: Java SCA Tomcat Integration
> Versions: Java-M1
> Reporter: ant elder
> Assignee: Raymond Feng
> Priority: Critical
> Fix For: Java-M1
> Attachments: 362-patch.txt
>
> Currently the distribution has the StAX jars in tomcat server/lib. This means they are not accessable by user applications. StAX is used in Rhino E4X so this breaks any JavaScript/E4X component running in Tomcat, but it would also break any user application that wantted to use StAX.
> See TUSCANY-282 and TUSCANY-82
> It may be possible to work around the problem by bundling the StAX jars in the web app, I've not tried. We already put a bunch of other stuff in Tomcat common/lib so I don't see why StAX should be any different.
> Assigning to Raymond as he's got the distribution JIRA TUSCANY-282
--
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