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 2013/05/12 16:15:16 UTC

[jira] [Resolved] (JUDDI-611) UDDIClerkManager renamed to UDDIClient

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

Kurt T Stam resolved JUDDI-611.
-------------------------------

    Resolution: Fixed
    
> UDDIClerkManager renamed to UDDIClient
> --------------------------------------
>
>                 Key: JUDDI-611
>                 URL: https://issues.apache.org/jira/browse/JUDDI-611
>             Project: jUDDI
>          Issue Type: Improvement
>          Components: uddi-client
>            Reporter: Kurt T Stam
>            Assignee: Kurt T Stam
>             Fix For: 3.1.5
>
>
> Over the juddi-client evolved and functionality was added rather organically as needed. When creating the examples that we start shipping now it became evident that a rename along with some small refactorings were needed.
> I tried deprecating the UDDIClerkManager in favor of UDDIClient but manager -> client changes in the client config are making backwards compatibility hard and confusing. I've added an uddi-client.xsd to facilitate fixing people's existing client  config.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira