Today, I was running into an interesting issue while registering services in OWSM.
Lets say you are registering a service with the OWSM gateway. The WSDL of the service might import other WSDLs. If the WSDLs are imported using a relative location, things dont seem to work [registration would go through]- this is because OWSM does not seem to support virtualizing of imported WSDLs at a relative location. [Note that it does support virtualizing of imported XSDs.]
i.e.
<definitions>
...
<import namespace=www.po.com location="../po.wsdl"/>
...
</definitions>
would not work.
What you could do instead is to host this WSDL through Apache, and then refer to the imported WSDL as an absolute URL
for e.g.
<definitions>
....
<import namespace=www.po.com location="http://myserver.com:7777/wsdls/po.wsdl"/>
....
</definitions>
I invite comments from the readers on any other interesting alternatives they have taken to alleviate this issue.
