[jbosstools-issues] [JBoss JIRA] (JBIDE-16066) Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog
[
https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi...
]
Brian Fitzpatrick edited comment on JBIDE-16066 at 9/30/14 6:15 PM:
--------------------------------------------------------------------
You can get around the "Runtime Location not set" problem by defining a JBoss AS
7.1 runtime that points to EAP. Going that route, I was able to create a Dynamic Web
Project, create a WSDL there, and then create a new Web Service (top-down), which created
a new EAR file that was deployed just fine. And I was able to get to the WSDL via the WS
Tester without incident.
was (Author: bfitzpat):
You can get around the "Runtime Location not set" problem by defining a JBoss AS
7.1 runtime that points to EAP. Going that route, I was able to create a Dynamic Web
Project, create a WSDL there, and then create a new Web Service (top-down), which created
a new EAR file that was deployed just fine.
Top-Down WS deployment isn't successful when selecting Start/Test
service in Web Service dialog
-----------------------------------------------------------------------------------------------
Key: JBIDE-16066
URL: https://issues.jboss.org/browse/JBIDE-16066
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Affects Versions: 4.1.1.CR1
Environment: JBDS 7.1.0 CR1, EAP-6.1
Reporter: Radoslav Rábara
Assignee: Brian Fitzpatrick
Fix For: 4.2.0.CR2
Attachments: topDownServer.log
Deployment isn't successful when Top-Down web service is created with slider level
selected to "Start service" or "Test service". Project is deployed to
the server but the service endpoint isn't added so the service is not accessible.
It works with other slider levels and all levels works when the server isn't started
before the web service is created.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)