[
https://issues.apache.org/jira/browse/OPENEJB-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Gallimore closed OPENEJB-516.
--------------------------------------
Resolution: Fixed
Assignee: Jonathan Gallimore
Closing this issue as discussed here:
http://www.nabble.com/Re%3A-OpenEJB-Eclipse-Plugin-update-p18874064.html
The plugin should now add javaee-api and openejb-client jars from the
OPENEJB_HOME directory to the classpath of any project that uses the OpenEJB
runtime.
> OpenEjb Server Adapter will require a runtime bundle
> ----------------------------------------------------
>
> Key: OPENEJB-516
> URL: https://issues.apache.org/jira/browse/OPENEJB-516
> Project: OpenEJB
> Issue Type: New Feature
> Components: eclipse
> Affects Versions: (not version related)
> Reporter: Sachin Patel
> Assignee: Jonathan Gallimore
> Fix For: (not version related)
>
>
> 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.
