You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Douglas Scott Jackson (JIRA)" <ji...@apache.org> on 2008/02/14 22:31:08 UTC
[jira] Created: (ODE-242) Usage of Xerces classes generates
instability with regard to app servers
Usage of Xerces classes generates instability with regard to app servers
------------------------------------------------------------------------
Key: ODE-242
URL: https://issues.apache.org/jira/browse/ODE-242
Project: ODE
Issue Type: Bug
Components: BPEL Runtime
Affects Versions: 1.2
Environment: weblogic 9.2
Reporter: Douglas Scott Jackson
Application servers typically include a version of xerces in their system classpath may conflict with
the version used by Ode. Altering the class loading hierarchy of an App Server such as weblogic is
not supported. This means that applications wishing to bundle or use Ode will have a tough time
supporting different versions of the app server. Applications may need to support multiple versions
of application servers due to support policies. Therefore using a technology like xerces may inhibit
the adoption of Ode greatly. In my experience higher level APIs (JAXB, JAXP, etc) are far more likely
to work across multiple versions of servers.
An example of this is trying to use the current 1.2 version of Ode sources with Weblogic 9.2.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-242) Usage of Xerces classes generates
instability with regard to app servers
Posted by "Paul R. Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569118#action_12569118 ]
Paul R. Brown commented on ODE-242:
-----------------------------------
Once upon a time, we had to hard-wire the version of Xerces that we were using because some bugs in versions that were out there (e.g., shipping with Tomcat) would cause problems with schemas when loading WSDL (as Matthieu was saying).
More likely than not, any modern version of Xerces will work.
> Usage of Xerces classes generates instability with regard to app servers
> ------------------------------------------------------------------------
>
> Key: ODE-242
> URL: https://issues.apache.org/jira/browse/ODE-242
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.2
> Environment: weblogic 9.2
> Reporter: Douglas Scott Jackson
>
> Application servers typically include a version of xerces in their system classpath that may conflict with
> the version used by Ode. Altering the class loading hierarchy of an App Server such as weblogic is
> not supported. This means that applications wishing to bundle or use Ode will have a tough time
> supporting different versions of the app server. Applications may need to support multiple versions
> of application servers due to support policies. Therefore using a technology like xerces may inhibit
> the adoption of Ode greatly. In my experience higher level APIs (JAXB, JAXP, etc) are far more likely
> to work across multiple versions of servers.
> An example of this is trying to use the current 1.2 version of Ode sources with Weblogic 9.2.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-242) Usage of Xerces classes generates
instability with regard to app servers
Posted by "Douglas Scott Jackson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Douglas Scott Jackson updated ODE-242:
--------------------------------------
Description:
Application servers typically include a version of xerces in their system classpath that may conflict with
the version used by Ode. Altering the class loading hierarchy of an App Server such as weblogic is
not supported. This means that applications wishing to bundle or use Ode will have a tough time
supporting different versions of the app server. Applications may need to support multiple versions
of application servers due to support policies. Therefore using a technology like xerces may inhibit
the adoption of Ode greatly. In my experience higher level APIs (JAXB, JAXP, etc) are far more likely
to work across multiple versions of servers.
An example of this is trying to use the current 1.2 version of Ode sources with Weblogic 9.2.
was:
Application servers typically include a version of xerces in their system classpath may conflict with
the version used by Ode. Altering the class loading hierarchy of an App Server such as weblogic is
not supported. This means that applications wishing to bundle or use Ode will have a tough time
supporting different versions of the app server. Applications may need to support multiple versions
of application servers due to support policies. Therefore using a technology like xerces may inhibit
the adoption of Ode greatly. In my experience higher level APIs (JAXB, JAXP, etc) are far more likely
to work across multiple versions of servers.
An example of this is trying to use the current 1.2 version of Ode sources with Weblogic 9.2.
> Usage of Xerces classes generates instability with regard to app servers
> ------------------------------------------------------------------------
>
> Key: ODE-242
> URL: https://issues.apache.org/jira/browse/ODE-242
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.2
> Environment: weblogic 9.2
> Reporter: Douglas Scott Jackson
>
> Application servers typically include a version of xerces in their system classpath that may conflict with
> the version used by Ode. Altering the class loading hierarchy of an App Server such as weblogic is
> not supported. This means that applications wishing to bundle or use Ode will have a tough time
> supporting different versions of the app server. Applications may need to support multiple versions
> of application servers due to support policies. Therefore using a technology like xerces may inhibit
> the adoption of Ode greatly. In my experience higher level APIs (JAXB, JAXP, etc) are far more likely
> to work across multiple versions of servers.
> An example of this is trying to use the current 1.2 version of Ode sources with Weblogic 9.2.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-242) Usage of Xerces classes generates
instability with regard to app servers
Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569113#action_12569113 ]
Matthieu Riou commented on ODE-242:
-----------------------------------
We're using Xerces because we more or less have to. We rely on its internal APIs for schemas handling. It's really needed to extract schemas from WSDLs and check what are the actual types of variables and we can't replace that with JAXB or JAXP.
What you can try is to replace the Xerces version used by ODE with the one provided with Weblogic or vice-versa. One of the two combinations should work.
> Usage of Xerces classes generates instability with regard to app servers
> ------------------------------------------------------------------------
>
> Key: ODE-242
> URL: https://issues.apache.org/jira/browse/ODE-242
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.2
> Environment: weblogic 9.2
> Reporter: Douglas Scott Jackson
>
> Application servers typically include a version of xerces in their system classpath that may conflict with
> the version used by Ode. Altering the class loading hierarchy of an App Server such as weblogic is
> not supported. This means that applications wishing to bundle or use Ode will have a tough time
> supporting different versions of the app server. Applications may need to support multiple versions
> of application servers due to support policies. Therefore using a technology like xerces may inhibit
> the adoption of Ode greatly. In my experience higher level APIs (JAXB, JAXP, etc) are far more likely
> to work across multiple versions of servers.
> An example of this is trying to use the current 1.2 version of Ode sources with Weblogic 9.2.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ODE-242) Usage of Xerces classes generates
instability with regard to app servers
Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthieu Riou resolved ODE-242.
-------------------------------
Resolution: Invalid
> Usage of Xerces classes generates instability with regard to app servers
> ------------------------------------------------------------------------
>
> Key: ODE-242
> URL: https://issues.apache.org/jira/browse/ODE-242
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.2
> Environment: weblogic 9.2
> Reporter: Douglas Scott Jackson
>
> Application servers typically include a version of xerces in their system classpath that may conflict with
> the version used by Ode. Altering the class loading hierarchy of an App Server such as weblogic is
> not supported. This means that applications wishing to bundle or use Ode will have a tough time
> supporting different versions of the app server. Applications may need to support multiple versions
> of application servers due to support policies. Therefore using a technology like xerces may inhibit
> the adoption of Ode greatly. In my experience higher level APIs (JAXB, JAXP, etc) are far more likely
> to work across multiple versions of servers.
> An example of this is trying to use the current 1.2 version of Ode sources with Weblogic 9.2.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.