You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Mike Edwards (JIRA)" <de...@tuscany.apache.org> on 2010/09/18 12:48:38 UTC
[jira] Closed: (TUSCANY-3123) Enable implementation-bpel-runtime
for OSGi on SCA Java 2.0
[ https://issues.apache.org/jira/browse/TUSCANY-3123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Edwards closed TUSCANY-3123.
---------------------------------
Closing resolved issues
> Enable implementation-bpel-runtime for OSGi on SCA Java 2.0
> -----------------------------------------------------------
>
> Key: TUSCANY-3123
> URL: https://issues.apache.org/jira/browse/TUSCANY-3123
> Project: Tuscany
> Issue Type: Bug
> Affects Versions: Java-SCA-2.0
> Reporter: Mike Edwards
> Assignee: Mike Edwards
> Fix For: Java-SCA-2.0
>
>
> implementation-bpel-runtime has a major dependency on the Apache ODE project, which provides the runtime BPEL execution engine required to run BPEL processes.
> As well as the direct dependencies on ODE modules, ODE itself has a large web of dependencies on modules from a range of other sources.
> The problem with ODE and its web of dependencies is that very few of them are built for OSGi and simply using the individual JARs causes classloading failures in many places. One of the biggest issues is that there are API / Provider pairs that use the META-INF/services approach to loading the provider classes for the API.
> This requires that special handling is done for the implementation-bpel-runtime module in order for it to run successfully under OSGi.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.