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 2010/03/11 00:15:27 UTC

[jira] Created: (JUDDI-379) the name of either the juddi client config manager or filename should be configurable

the name of either the juddi client config manager or filename should be configurable
-------------------------------------------------------------------------------------

                 Key: JUDDI-379
                 URL: https://issues.apache.org/jira/browse/JUDDI-379
             Project: jUDDI
          Issue Type: Sub-task
          Components: uddi-client
    Affects Versions: 3.0.1
            Reporter: Kurt T Stam
            Assignee: Kurt T Stam
             Fix For: 3.0.2


The use case is as follows, if inVM transport is used, the war will not contain a uddi.xml file, in that case you should be able to set the manager name (in case there are more then one client config files on the classpath). 

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


[jira] Closed: (JUDDI-379) the name of either the juddi client config manager or filename should be configurable

Posted by "Kurt T Stam (JIRA)" <ju...@ws.apache.org>.
     [ https://issues.apache.org/jira/browse/JUDDI-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kurt T Stam closed JUDDI-379.
-----------------------------

    Resolution: Fixed

Fixed, you can now pass in the name of the config file in the servlet config  "uddi.client.manager.name". See the UDDIClientServlet.

> the name of either the juddi client config manager or filename should be configurable
> -------------------------------------------------------------------------------------
>
>                 Key: JUDDI-379
>                 URL: https://issues.apache.org/jira/browse/JUDDI-379
>             Project: jUDDI
>          Issue Type: Sub-task
>          Components: uddi-client
>    Affects Versions: 3.0.1
>            Reporter: Kurt T Stam
>            Assignee: Kurt T Stam
>             Fix For: 3.0.2
>
>
> The use case is as follows, if inVM transport is used, the war will not contain a uddi.xml file, in that case you should be able to set the manager name (in case there are more then one client config files on the classpath). 

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