Provide a way to transform traditional jar to OSGi bundle when user install the
jar into G repository.
------------------------------------------------------------------------------------------------------
Key: GERONIMO-5586
URL: https://issues.apache.org/jira/browse/GERONIMO-5586
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Affects Versions: 3.0
Reporter: Forrest Xia
As G server fundamentally turn into an OSGi based java ee application server,
all libraries are required to be a OSGi bundle. But this may not work friendly
to popular Java EE user.
Let's say a simple scenario that deploys a data source to G server:
1. User uses install-library command or admin console to install the jdbc
driver into G repository
2. User prepare a datasource deployment plan that depends on the installed jdbc
driver
3. User uses deploy command or admin console to deploy the datasource
The deployer will report a ClassNotFound exception saying jdbc driver class is
not found. Java EE user may confuse around here, since they know they've
installed the jdbc libraries into the repository, but why encounter the CNF
exception?
>From user-friendly aspect, G server is better to provide a way to transform
>traditional jar into a OSGi bundle transparently.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
