juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kurt T Stam (JIRA)" <juddi-...@ws.apache.org>
Subject [jira] Commented: (JUDDI-248) Perform top-down analysis of startup elements to come up with unified method
Date Wed, 10 Jun 2009 17:43:07 GMT

    [ https://issues.apache.org/jira/browse/JUDDI-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718147#action_12718147
] 

Kurt T Stam commented on JUDDI-248:
-----------------------------------

I think the easiest way would be to require the user to call Registry.start or something before
starting to use the registry. In a war deployment the RegistryServlet can do this on startup.
If we do this then we can remove the ServiceBase class.

> Perform top-down analysis of startup elements to come up with unified method
> ----------------------------------------------------------------------------
>
>                 Key: JUDDI-248
>                 URL: https://issues.apache.org/jira/browse/JUDDI-248
>             Project: jUDDI
>          Issue Type: Improvement
>    Affects Versions: 3.0beta
>            Reporter: Jeff Faath
>            Assignee: Jeff Faath
>             Fix For: 3.0
>
>
> Several pieces are involved in starting up juddi including initiating config, instantiating
persistence manger, starting up subscription notifier, etc.  This startup process should be
unified across all the ways juddi can be run (servlet, embedded, etc.).

-- 
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