You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by "Alfredo Scotto (JIRA)" <xe...@xml.apache.org> on 2006/09/19 00:32:22 UTC
[jira] Updated: (XERCESJ-1190) Web application using Xerces 2.7.1
with JAXP is blocking validation of Deployment Descriptors with
xsi:schemaLocation in Deployment Manager
[ http://issues.apache.org/jira/browse/XERCESJ-1190?page=all ]
Alfredo Scotto updated XERCESJ-1190:
------------------------------------
Attachment: web-app_2_4.xsd
schema of web.xml
> Web application using Xerces 2.7.1 with JAXP is blocking validation of Deployment Descriptors with xsi:schemaLocation in Deployment Manager
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: XERCESJ-1190
> URL: http://issues.apache.org/jira/browse/XERCESJ-1190
> Project: Xerces2-J
> Issue Type: Bug
> Components: JAXP (javax.xml.parsers)
> Affects Versions: 2.4.0
> Environment: Xerces 2.7.1 with Websphere 6.0 (latest update), any OS, IBM JVM 1.4.xx (latest update from IBM)
> Reporter: Alfredo Scotto
> Attachments: web-app_2_4.xsd, web.xml
>
>
> I have a wev application using Xerces/Xalan 2.7.1 by JAXP. When I deployed that application on Websphere 6 standalone it will not be able to deploy new applications using schemaLocation like j2ee1.4 and schema web-app_2_4.xsd. This is the default schema on WAS 6. It's look like the JAXP initialization executed from my web appl. is changing what weblogic is using. Both are running on same JVM but from different classloader. I tried to put those jars in endorsed folder but this blocks completely websphere activities. IBM included Xerces jar, it doesn't include the version but it doesn't include javax.xml.xpath apis so it coud be 2.4.1.
> I also noted that there are no ways to parse those kind of xml with schemaLocation without define entityResolver. IBM could has solved that problem but I need javax.xml.xpath implementation and they haven't.
> Probably that interference could be generated by:
> - Same configuration class walking too much,
> - schemaLocation handler with problems,
> - Builder or configuration unique at JVM level
> All of those are very bad and I guess many are experiencing this problem.
--
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: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org