[ 
https://issues.apache.org/jira/browse/OEP-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Blevins moved OPENEJB-516 to OEP-12:
------------------------------------------

        Fix Version/s:     (was: (not version related))
          Component/s:     (was: eclipse)
    Affects Version/s:     (was: (not version related))
                  Key: OEP-12  (was: OPENEJB-516)
              Project: OpenEJB Eclipse Plugin  (was: OpenEJB)

> OpenEjb Server Adapter will require a runtime bundle
> ----------------------------------------------------
>
>                 Key: OEP-12
>                 URL: https://issues.apache.org/jira/browse/OEP-12
>             Project: OpenEJB Eclipse Plugin
>          Issue Type: New Feature
>            Reporter: Sachin Patel
>            Assignee: Jonathan Gallimore
>
> In order for the OpenEjb eclipse plugin to depend on the external openejb 
> jars, a runtime bundle will be required that provides a wrapper bundle around 
> the openejb jars so they can be used by the eclipse plugins to invoke any 
> code in openejb. 
> Two packaging methods are available:
> (1) Physically include the openejb jars inside a 
> org.apache.openejb.runtime.v30 bundle.  Since the eclipse plugin isn't 
> currently mavenized, the packaging of the openejb jars won't be dynamic and 
> if new versions of the jars are needed they will need to be updated in source 
> control.  This is probably the best and easiest approach to get things 
> working.
> (2) The org.apache.openejb.runtime.v30 bundle can have manifest entries that 
> can point to external jars and when the bundle starts these jars will be 
> included in the bundle's classloader.  The  only disadvantage to this 
> approach is the fact that though at runtime these jars will resolve, the 
> Plugin Development Enviorment in eclipse cannot yet resolve the jars so will 
> make plugin development an issue if any classes in those jars are needed.  
> The compiler may not be able to resolve them.  I'm hoping this has been fixed 
> in Eclipse 3.3, and if so then this would be the ideal approach.

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