[OpenVPMS Developers] Proposed change to ESCI RegistryS ervice

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:

1) multiple deployments of OpenVPMS in a single Tomcat instance

2) 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.

An alternative would be to mandate that WSDL urls are not password protected,

but I think the approach outlined above is a better one.

Thoughts?

 

-Tim

If you'd like to unsubscribe and stop receiving these emails click here: http://u64393.sendgrid.org/wf/unsubscribe?rp=wC%2FhuYqm%2Bx1zWpeXJ%2BPcaZLA7XYjCpsQX%2FftzlAEgLM8tHh8VeInwQJN40fUunhsTwccI27r5NVSOz%2BWTpwobw%3D%3D&u=F6OnsR29SgiESVjLkSK61A%2Fut.

Syndicate content