Return service urls from RegistryService methods instead of WSDL urls ---------------------------------------------------------------------

Key: ESCI-8 URL: https://openvpms.atlassian.net/browse/ESCI-8 Project: e-Supply Chain Interface Issue Type: Task Affects Versions: 1.0-beta-2 Reporter: Tim Anderson Assignee: Tony De Keizer Fix For: 1.0-beta-3

In the 1.0-beta-2 ESCI implementation, the RegistryService getInboxService() and getOrderService() return the WSDL urls of the InboxService and OrderService respectively.

It is proposed that: * these methods change to return the service urls instead E.g: https://vetsupplies.com/inbox instead of https://vetsupplies.com/inbox?wsdl * the RegistryService service url is used by clients rather than its WSDL url E.g: https://vetsupplies.com/registry instead of https://vetsupplies.com/registry?wsdl

This is necessary to get round a limitation in the JAX-WS implementation which requires a java.net.Authenticator to be used to access WSDL that is password protected. The Authenticator is a singleton, registered via Authenticator.setDefault(), replacing any existing Authenticator. This prevents:

# multiple deployments of OpenVPMS in a single Tomcat instance # deployment of ESCI in containers that register their own Authenticator implementation

There is a performance and bandwidth benefit in this change in that WSDL will not need to be retrieved for each connection to a supplier service.

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://openvpms.atlassian.net/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

_______________________________________________ OpenVPMS Developers Mailing List developers@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/developers Posts from this mailing list can be viewed online and replied to in the OpenVPMS Developer's forum- http://tinyurl.com/openvdf