You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Kurt Stam (JIRA)" <ju...@ws.apache.org> on 2008/09/08 03:40:44 UTC
[jira] Updated: (JUDDI-71) Integrating JUDDI in a managed
environment
[ https://issues.apache.org/jira/browse/JUDDI-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt Stam updated JUDDI-71:
---------------------------
Fix Version/s: 3.0
> Integrating JUDDI in a managed environment
> ------------------------------------------
>
> Key: JUDDI-71
> URL: https://issues.apache.org/jira/browse/JUDDI-71
> Project: jUDDI
> Issue Type: Improvement
> Components: Feature Requests Section
> Reporter: Anil Saldhana
> Assignee: Kurt Stam
> Priority: Minor
> Fix For: 3.0
>
>
> Apache juddi is a software application that provides UDDI server capabilities. The design has flexibility to plug it in any container (be it a web container, a J2EE Application Server or a pure web services container). I am eager to see jUDDI being refactored/repackaged to the following subsystems (make it seperate jars):
> a) Core [just plain uddi functionality, no knowledge of web/Web service dependence].
> b) Web Service server component. [Deals with creation/Reception/Processing of SOAP Messages].
> c) Web Service Client component. [Deals with creation/Reception/Processing of SOAP Messages].
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: juddi-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: juddi-dev-help@ws.apache.org