[jbosstools-issues] [JBoss JIRA] Assigned: (JBIDE-5870) Cannot create JbossWS service with client enabled

[Brian Fitzpatrick (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBIDE-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Fitzpatrick reassigned JBIDE-5870:
----------------------------------------

    Assignee: Feng Qian


Hey Grid...

This is a weird one. There's two parts to it. There's a runtime fix that's in JBossWS that is in EAP 5.01, but not in SOA-P 5.0, which doesn't really help us. That's the first part.

The second part is that since SOA-P 5 doesn't include EAP 5.01, we need to create a workaround in the tooling. Now, I've been looking at your web service code in JBossWebServiceClient in WS.creation.ui and it doesn't seem to be called, but that would seem the logical place to create the application.xml with the contents matching the web service from the earlier comment by David Ward. 

So #1, I have no idea why your code isn't getting called in the "develop(...)" method of JBossWebServiceClient, but it's not. If that happens, that would be the best place to create an application.xml file in META-INF/ if it doesn't exist or update it if it does.

#2, why does the Tomcat deploy of this web service not create an EAR with an inner WAR? It works fine in JBossWS if it's just a WAR that is deployed. Is there a reason this web service for JBossWS must be deployed in an EAR?

This is CRITICAL and BLOCKING us sending our the CR2 builds. We must get this fixed as soon as possible (or sooner if possible). But I want to know WHAT you do to fix it so we understand what's going on. So please attach patches if you fix the code or simply write out as clearly as you can what you are doing or what you found to fix it.

Thanks

--Fitz

> Cannot create JbossWS service with client enabled
> -------------------------------------------------
>
>                 Key: JBIDE-5870
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5870
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Webservices
>    Affects Versions: 3.1.0.CR1
>            Reporter: Libor Zoubek
>            Assignee: Feng Qian
>            Priority: Critical
>             Fix For: 3.1.0.CR2
>
>         Attachments: JbossWS.java
>
>
> creation of new JbossWS cannot be finished when 
> Steps to reproduce :
> 1. Create new Dynamic project
> 2. Create new class with javax.jws annotations or use the attached one
> 3. Create new JbossWS based web service : New -> Other -> Web Service
> 3.1. Service implementation:select your class
> 3.2. Web service runtime: JbossWS
> 3.3. Client type : java Proxy, move slider to 'Develop client' or above
> 4. Finish or Next, does not matter if you check anything there
> 5. You get a MessageBox telling : Selection must be WSDL.
> 6. WSDL seems to get published, web service seems too, but one can' test it
> btw:  How can I retrieve WSDL from jboss as? Jboss-as does not say something like : 'New service is deployed, wsdl is here'

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira