[
https://jira.jboss.org/jira/browse/JBWS-2725?page=com.atlassian.jira.plug...
]
David Ward commented on JBWS-2725:
----------------------------------
The only thing that rings a bell is the mention of the error "Content is not allowed
in prolog." It reminded me of JBESB-2664, where the HttpMessageComposer was not
setting the appropriate character encoding to match the content type. That issue,
however, had to do with ESB Message composition, not anything to do with the contract
application, as seen here. So long as the contract jsp page is returning WSDL with the
appropriate character encoding and content type, you should be fine.
If I remember correctly, an empty document could also cause this problem. However,
looking at contract.jsp, it looks like we spit out <Unavailable/> if that's the
case.
Sorry I couldn't be more help. My vote is that if you can't reproduce the issue,
mark it as such and close it.
wsonsume doesn't like the contract app URLs
(
http://localhost:8080/contract)
----------------------------------------------------------------------------
Key: JBWS-2725
URL:
https://jira.jboss.org/jira/browse/JBWS-2725
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native, tools-jaxws
Affects Versions: jbossws-2.0.2
Reporter: Tom Fennelly
Assignee: Alessio Soldano
Fix For: jbossws-native-3.2.2
The WSDL URL for ESB based webservices are of the form
"http://127.0.0.1:8080/contract/contract.jsp?serviceCat=MyServiceCategory&serviceName=MyWSProducerService&protocol=http".
The wsconsume tool doesn't like them. See the example below. Might be a JBossWS
specific issue at
org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumerImpl.java:190).
wsconsume -v -k -o
/Jboss/ESB/trunk/product/samples/quickstarts/webservice_producer/build/wsclient
http://127.0.0.1:8080/contract/contract.jsp?serviceCat=MyServiceCategory&...
parsing WSDL...
[ERROR] Content is not allowed in prolog.
line 12 of
http://127.0.0.1:8080/contract/contract.jsp?serviceCat=MyServiceCategory
[ERROR] Failed to read the WSDL document:
http://127.0.0.1:8080/contract/contract.jsp?serviceCat=MyServiceCategory, because 1) could
not find the document; /2) the document could not be read; 3) the root element of the
document is not <wsdl:definitions>.
unknown location
Failed to parse the WSDL.
Failed to invoke WsImport
java.lang.IllegalStateException: WsImport invocation failed. Try the verbose switch for
more information
at
org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumerImpl.java:190)
at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(WSConsume.java:216)
at org.jboss.wsf.spi.tools.cmd.WSConsume.main(WSConsume.java:79)
'serviceName' is not recognized as an internal or external command,
operable program or batch file.
'protocol' is not recognized as an internal or external command,
operable program or batch file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira