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-5005) uddi osgi integration
Date Sat, 26 Dec 2009 08:02:29 GMT

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

David Jencks commented on GERONIMO-5005:
----------------------------------------

Integrating the current juddi could be a lot of work.  It's a non-enterprise jpa web app that
uses PersistenceManager.getEntityManager() rather than EntityManagerFactory.getEntityManager().
 Assembly of the Registry looks like it might be difficult to disentangle.  Some jpa use seems
to be runtime in web service calls, and some seems to be at startup to set up the Registry
object. ee DI should work for the web services.  For the other uses I think we'll need to
use ee DI into a listener or servlet (currently a servlet is used) and pass the emf into the
components that need it.

> uddi osgi integration
> ---------------------
>
>                 Key: GERONIMO-5005
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5005
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: osgi
>    Affects Versions: 3.0
>            Reporter: David Jencks
>             Fix For: 3.0
>
>
> Upgrade uddi support to osgi and also up to date juddi.  Juddi needs to apply JUDDI-299
which among other things bundleizes juddi.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message