Sorry, what identifier do you refer to? Please post an example.
WSDL report an include on a other *123456*.wsdl
Where 123456 is a random number that change from a deploy to another!
EAR is deployed as file (not exploded).
<definitions name="WMI" targetNamespace="http://impl.service.wmi.cuc.unipa.it/"> <import location="http://immawebtest.unipa.it:8080/wmi-ws/services?wsdl&resource=Services_PortType1628.wsdl" namespace="http://service.wmi.cuc.unipa.it/"/> <service name="WMI"> <port binding="ns1:ServicesBinding" name="servicesPort"> <soap:address location="http://immawebtest.unipa.it:8080/wmi-ws/services"/> </port> </service> </definitions>
You can see that there's an import (line 2) on other wsdl (with a random number) that depends on deploy!
any solution to this issue ?
working around the problem, why not include a static reference to a wsdl within a war and just have your clients use that wsdl?
Are you building this WSDL first?
some of my services have import statements and when bringing up service?wsdl, i'm presented with a completely flat wsdl. No import statements.
You might want to check for some metadata resolver errors when deploying this