You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Jeff Faath (JIRA)" <ju...@ws.apache.org> on 2008/12/05 10:28:44 UTC

[jira] Resolved: (JUDDI-47) Make juddi a J2EE 1.4 compliant Web Service

     [ https://issues.apache.org/jira/browse/JUDDI-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Faath resolved JUDDI-47.
-----------------------------

    Resolution: Fixed

This has been completed for the v3 release.  The UDDI APIs are exposed via JAX-WS web services.

> Make juddi a J2EE 1.4 compliant Web Service
> -------------------------------------------
>
>                 Key: JUDDI-47
>                 URL: https://issues.apache.org/jira/browse/JUDDI-47
>             Project: jUDDI
>          Issue Type: Improvement
>          Components: J2EE Web Service (Jaxrpc/Saaj)
>            Reporter: Anil Saldhana
>            Assignee: Jeff Faath
>            Priority: Trivial
>             Fix For: 3.0alpha
>
>
> jUDDI on the server side can be implemented as a Java Service End Point Interface (SEI). Using J2EE tools, a WSDL can be generated and published on the web. Clients like Apache Scout can always invoke this J2EE compliant web services using DII.
> Since a WSDL can be published, it can be interoperable (WS-I Basic Profile compliant).
> Just a thought.....
>  

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