[
http://jira.jboss.com/jira/browse/JBESB-1547?page=all ]
Brian Carothers updated JBESB-1547:
-----------------------------------
Attachment: retry-patch-JBESB-1547.txt
Looking at the patch file, it had some absolute paths in it that were tied to my eclipse
install. I cleaned those up, reapplied the patch against a clean nightly build of the ESB
(labs/jbossesb/trunk/product) from 2-3 nights ago, and re-tested. It worked right for the
existing service case (with no contract info available) and the non-existing service case
(returned a 404).
If this patch doesn't fix it, please post the contract.jsp from SOA-P and I'll
craft a patch against it. Not sure why they'd be different though.
Apologies for any inconvenience that this caused.
Contract console should generate HTTP 404 when asking for
non-deployed service WSDL
-----------------------------------------------------------------------------------
Key: JBESB-1547
URL:
http://jira.jboss.com/jira/browse/JBESB-1547
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Tooling
Affects Versions: 4.2.1
Reporter: Jiri Pechanec
Fix For: 4.3
Attachments: patch-JBESB-1547.txt, retry-patch-JBESB-1547.txt
Try
http://localhost:8080/contract/contract.jsp?serviceCat=blah&serviceNa...
The HTTP/404 should be returned when trying to obtains WSDL but page with text
"null" is returned.
--
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