[
https://issues.jboss.org/browse/JBESB-3802?page=com.atlassian.jira.plugin...
]
Sato Tadayoshi commented on JBESB-3802:
---------------------------------------
I report another issue related to the commit r38166. When I turn
{{'cache-remote-schemas'}} on and try to look at a WSDL published by JBR-Gateway
(HTTP) via {{http://localhost:8080/contract/}} using a browser, I receive the following
error (which is Firefox's):
{noformat}
XML Parsing Error: XML or text declaration not at start of entity
Location:
http://localhost:8080/contract/contract.jsp?serviceCat=MyCategory&ser...
Line Number 18, Column 1:<?xml version="1.0"
encoding="UTF-8"?><definitions
xmlns="http://schemas.xmlsoap.org/wsdl/" ...
^
{noformat}
The reason I found is as follows; The contract.jsp originally prepends blank lines to its
output due to the jsp directives. It is ok until now because AbstractWsdlContractPublisher
don't add {{"<?xml version="1.0"
encoding="UTF-8"?>"}} on top of the published WSDLs. However, this XML
declaration is introduced by this fix when {{'cache-remote-schemas'}} is turned
on. That's why we get the above error.
The best resolution for the issue I think would be just adding {{"<%@page
trimDirectiveWhitespaces="true" %>"}} to contract.jsp. I've attached
the patch. Please review it.
Thanks.
Rewrite schemas imported by SOAPProcessor to point to locally cached
versions
-----------------------------------------------------------------------------
Key: JBESB-3802
URL:
https://issues.jboss.org/browse/JBESB-3802
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Environment: JBoss Enterprise SOA-P 5.2
Reporter: Jason Shepherd
Attachments: JBESB-3802_contract_jsp.patch
When wrapping an external webservice using SOAPProcessor, the contract is correctly
published in the contract web application, see JBESB-3789. However any schema files
imported by the wrapped web service are referenced on the wrapped web service, they are
not cached by the ESB. Please cache a copy of the imported schemas locally, so that a
client of the ESB does not have to contact the original, wrapped, web service to retrieve
the schemas.
This issue will fix will also effect JBR, HTTP gateway schemas as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira