[ 
https://issues.apache.org/jira/browse/TUSCANY-3123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724456#action_12724456
 ] 

Mike Edwards commented on TUSCANY-3123:
---------------------------------------

Design approach:

Build a single JAR containing the implementation-bpel-runtime classes PLUS the 
ODE JARs and a selected set of the ODE dependency JARs.

The ODE and ODE dependency JARs are then also placed into the Bundle-Classpath: 
attribute of the MANIFEST.MF so that all the classes from those JARs are all 
loaded by the classloader of the implementation-bpel-runtime bundle, so 
avoiding the problems of not finding the provider classes and also not 
requiring us to produce specialized MANIFEST files for each of these 
non-Tuscany JARs.

Note that when not running under OSGi, these embedded JARs are ignored.

> 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.

Reply via email to