[
https://issues.jboss.org/browse/JBIDE-11294?page=com.atlassian.jira.plugi...
]
Brian Fitzpatrick commented on JBIDE-11294:
-------------------------------------------
Jaroslav, can you make sure that when you create the Bottom-up service you are selecting
JBossWS as the Web service runtime type instead of one of the "Axis" varieties?
That said, the WS Tester won't be able to invoke the WSDL from the workspace - the
project isn't the running instance of the service. You'd need to run with the
deployed WSDL path.
So this
(file:/C:/workspaces/runtime-New_configuration-Aug8/JBIDE-11294-29May/wsdl/HelloWorldService.wsdl)
should return a "java.net.ConnectException: Connection refused: connect"
exception.
And this
(file:/C:/Runtimes3/jboss-as-7.1.0.Final/standalone/data/wsdl/JBIDE-11707EAR.ear/JBIDE-11707.war/HelloWorldService.wsdl)
returns the expected SOAP response message.
There simply isn't enough detail coming out of the project as the WS Tester runs today
to get the running URL for the WSDL.
Error is thrown in error log when testing improper URL of Web Service
with Web Service Tester
---------------------------------------------------------------------------------------------
Key: JBIDE-11294
URL:
https://issues.jboss.org/browse/JBIDE-11294
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.3.0.Beta1
Reporter: Jaroslav Jankovič
Assignee: Brian Fitzpatrick
Fix For: 3.3.0.CR1
Attachments: jbide-11294.patch
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
In my opinion, if I want to test some web service with Web Service tester and provide
some wsdl file with improper URL location, message in Response Body should be adequate.
There is no need to throw error in error log.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira