[
http://jira.jboss.com/jira/browse/JBESB-1509?page=comments#action_12396323 ]
Tom Fennelly commented on JBESB-1509:
-------------------------------------
Right, they shouldn't... but Jeff's version of soapUI (not sure yet which it is)
wouldn't consume the WSDL (not sure what the error was either :-) ) and having the
preamble in there is def not an error, so no worries :-)
ESB mediated WSDLs have no xml preamble, which may cause issues for
some clients
--------------------------------------------------------------------------------
Key: JBESB-1509
URL:
http://jira.jboss.com/jira/browse/JBESB-1509
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.2.1
Reporter: Tom Fennelly
Assigned To: Tom Fennelly
Fix For: 4.2.1 CP1
Quote from Jeff Delong...
"I finally had time to figure this out. The WSDL that is generated and accessible
via the Contract web app is missing the ?xml tag at the beginning of the document:
<?xml version="1.0" encoding="UTF-8"?>
meaning it could not be read by a tool such as SoapUI. Once I saved the WSDL to a file
and added the ?xml tag it could be read, and the service consumed, but SoapUI. It does
invoke the web service correctly, through the jboss remoting http port, and proper ESB
actions are invoked."
I couldn't reproduce this error in my env, but we should add the preamble anyway.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira