[
https://issues.apache.org/jira/browse/GERONIMO-5056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire updated GERONIMO-5056:
-----------------------------------
Issue Type: Sub-task (was: Bug)
Parent: GERONIMO-5087
> Make jsr88 work in trunk
> ------------------------
>
> Key: GERONIMO-5056
> URL: https://issues.apache.org/jira/browse/GERONIMO-5056
> Project: Geronimo
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: deployment
> Affects Versions: 3.0
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 3.0
>
>
> Our jsr88 client in 2.2 worked by firing up a geronimo kernel and using some
> plugins to set up the connection to the target server and the local
> Configurers. To do the same in trunk we'd need to at least start an osgi
> environment, and possibly all of karaf.
> This might be too heavyweight. Since AFAIK no one has ever or ever will use
> the DConfigBean support and IIRC it is optional, lets try for a simpler
> initial solution to this problem.
> We can construct a jar that has a simpler DeploymentFactoryImpl and just
> include all the classes it needs right in that jar. The maven-bundle-plugin
> will pull all these classes in from the dependencies. Ugly but it seems to
> work.
> I'm putting this in our base karaf-framework under lib/jsr88. I think
> putting it directly in lib causes problems with osgi and separating it makes
> it a little clearer it's not really intended to be used by a geronimo server.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
