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 T Stam (JIRA)" <ju...@ws.apache.org> on 2009/05/31 19:52:07 UTC

[jira] Updated: (JUDDI-234) autoregistration of our own jUDDI endpoints

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

Kurt T Stam updated JUDDI-234:
------------------------------

    Fix Version/s:     (was: 3.0)
                   3.0beta

> autoregistration of our own jUDDI endpoints
> -------------------------------------------
>
>                 Key: JUDDI-234
>                 URL: https://issues.apache.org/jira/browse/JUDDI-234
>             Project: jUDDI
>          Issue Type: Improvement
>            Reporter: Kurt T Stam
>            Assignee: Kurt T Stam
>             Fix For: 3.0beta
>
>
> We registrer our own WSDL endpoints as part of the install data (root_businessEntity). 
> ...
> <bindingTemplate bindingKey="" serviceKey="">
>           <description>UDDI Inquiry API V3</description>
>           <accessPoint useType="endpoint">http://localhost:8080/juddi/services/inquiry?wsdl</accessPoint>
>           <tModelInstanceDetails>
>             <tModelInstanceInfo tModelKey="uddi:uddi.org:v3_inquiry">
> ...
> We reference the port (8080) in this data, but we may not be deploying the app to this port. Should we be doing some kind of 'autoregistration' instead?
> For now the workaround is to edit this data.

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