geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GERONIMO-5586) Provide a way to transform traditional jar to OSGi bundle when user install the jar into G repository.
Date Mon, 06 Jun 2011 21:32:59 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-5586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045132#comment-13045132
] 

David Jencks commented on GERONIMO-5586:
----------------------------------------

There's a pax "wrap" url handler that is easy to configure to do a conversion.  Experience
at pax indicates that it probably works well enough.  How should this be accessed?  I wrote
a little bit of code for the repository portlet that checks whether an artifact you are adding
is a bundle and if not runs it through the wrap url handler.  Is this enough?

> 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
>            Assignee: David Jencks
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message