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 2010/01/06 20:30:54 UTC
[jira] Created: (JUDDI-336) Make service names configurable in
client
Make service names configurable in client
-----------------------------------------
Key: JUDDI-336
URL: https://issues.apache.org/jira/browse/JUDDI-336
Project: jUDDI
Issue Type: Improvement
Affects Versions: 3.0
Reporter: Jeff Faath
Assignee: Jeff Faath
Priority: Minor
Fix For: 3.0.1
The names of the UDDI services should be made configurable in the client API as UDDI implementations can differ on their names. The default will be left at jUDDI's service names.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JUDDI-336) Fix WSDL endpoint so they align with
the spec.
Posted by "Kurt T Stam (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt T Stam updated JUDDI-336:
------------------------------
Component/s: core
Priority: Critical (was: Minor)
Assignee: Kurt T Stam (was: Jeff Faath)
Summary: Fix WSDL endpoint so they align with the spec. (was: Make service names configurable in client)
> Fix WSDL endpoint so they align with the spec.
> ----------------------------------------------
>
> Key: JUDDI-336
> URL: https://issues.apache.org/jira/browse/JUDDI-336
> Project: jUDDI
> Issue Type: Improvement
> Components: core
> Affects Versions: 3.0
> Reporter: Jeff Faath
> Assignee: Kurt T Stam
> Priority: Critical
> Fix For: 3.0.1
>
>
> The names of the UDDI services should be made configurable in the client API as UDDI implementations can differ on their names. The default will be left at jUDDI's service names.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (JUDDI-336) Fix WSDL endpoint so they align with the
spec.
Posted by "Kurt T Stam (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt T Stam closed JUDDI-336.
-----------------------------
Resolution: Fixed
> Fix WSDL endpoint so they align with the spec.
> ----------------------------------------------
>
> Key: JUDDI-336
> URL: https://issues.apache.org/jira/browse/JUDDI-336
> Project: jUDDI
> Issue Type: Improvement
> Components: core
> Affects Versions: 3.0
> Reporter: Jeff Faath
> Assignee: Kurt T Stam
> Priority: Critical
> Fix For: 3.0.1
>
>
> The names of the UDDI services should be made configurable in the client API as UDDI implementations can differ on their names. The default will be left at jUDDI's service names.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JUDDI-336) Fix WSDL endpoint so they align with
the spec.
Posted by "Tom Cunningham (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802314#action_12802314 ]
Tom Cunningham commented on JUDDI-336:
--------------------------------------
I think the service and the namespace need to be changed in juddi-cxf to match what's here in the descriptor :
http://www.oasis-open.org/committees/uddi-spec/doc/tn/uddi-spec-tc-tn-jax-rpc-20050126/wsdl/uddi_v3_service.wsdl
The service should be "UDDI_Service" by default and rather than define the xmlns in the endpoint like we do in beans.xml, I think they all need to be v3_service.
> Fix WSDL endpoint so they align with the spec.
> ----------------------------------------------
>
> Key: JUDDI-336
> URL: https://issues.apache.org/jira/browse/JUDDI-336
> Project: jUDDI
> Issue Type: Improvement
> Components: core
> Affects Versions: 3.0
> Reporter: Jeff Faath
> Assignee: Kurt T Stam
> Priority: Critical
> Fix For: 3.0.1
>
>
> The names of the UDDI services should be made configurable in the client API as UDDI implementations can differ on their names. The default will be left at jUDDI's service names.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JUDDI-336) Fix WSDL endpoint so they align with
the spec.
Posted by "Kurt T Stam (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802664#action_12802664 ]
Kurt T Stam commented on JUDDI-336:
-----------------------------------
The spec mentioned above is for the clientside. Our UDDIService class is an example implementation. We now aligned our services names with the ones defined in this spec. I believe that we do not need to use the uddi_v3_service.wsdl itself as it would make the deployment very brittle as the endpoints are hardcoded in it.
> Fix WSDL endpoint so they align with the spec.
> ----------------------------------------------
>
> Key: JUDDI-336
> URL: https://issues.apache.org/jira/browse/JUDDI-336
> Project: jUDDI
> Issue Type: Improvement
> Components: core
> Affects Versions: 3.0
> Reporter: Jeff Faath
> Assignee: Kurt T Stam
> Priority: Critical
> Fix For: 3.0.1
>
>
> The names of the UDDI services should be made configurable in the client API as UDDI implementations can differ on their names. The default will be left at jUDDI's service names.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.