You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Tom Cunningham (JIRA)" <ju...@ws.apache.org> on 2009/11/12 03:14:39 UTC
[jira] Created: (JUDDI-307) Need to grab the current transport from
the wrapper classes (UDDInquiryService, etc)
Need to grab the current transport from the wrapper classes (UDDInquiryService, etc)
------------------------------------------------------------------------------------
Key: JUDDI-307
URL: https://issues.apache.org/jira/browse/JUDDI-307
Project: jUDDI
Issue Type: Bug
Components: uddi-client
Affects Versions: 3.0
Reporter: Tom Cunningham
Assignee: Tom Cunningham
Fix For: 3.0.1
In 3.0, the InVMTransport is hard-coded into the wrapper classes. We need to grab the transport from the config.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JUDDI-307) Need to grab the current transport
from the wrapper classes (UDDInquiryService, etc)
Posted by "Tom Cunningham (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Cunningham resolved JUDDI-307.
----------------------------------
Resolution: Fixed
Use uddi.xml to determine current transport.
> Need to grab the current transport from the wrapper classes (UDDInquiryService, etc)
> ------------------------------------------------------------------------------------
>
> Key: JUDDI-307
> URL: https://issues.apache.org/jira/browse/JUDDI-307
> Project: jUDDI
> Issue Type: Bug
> Components: uddi-client
> Affects Versions: 3.0
> Reporter: Tom Cunningham
> Assignee: Tom Cunningham
> Fix For: 3.0.1
>
>
> In 3.0, the InVMTransport is hard-coded into the wrapper classes. We need to grab the transport from the config.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.