[ https://jira.jboss.org/jira/browse/JBDS-1105?page=com.atlassian.jira.plug... ] Brian Fitzpatrick commented on JBDS-1105: ----------------------------------------- Well, you should be able to get to the WSDL in the list at: http://localhost:8080/jbossws/services. But it doesn't seem to create or deploy it. It registers that there's a WSDL there, but you can't get to it. And I think you should see it in the EAR that gets deployed to [runtime]/server/default/deploy, but it's not showing up there either. Not seeing anything useful in the server log either... -- 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

[ https://jira.jboss.org/jira/browse/JBDS-1105?page=com.atlassian.jira.plug... ] Max Rydahl Andersen commented on JBDS-1105: ------------------------------------------- About viewing in JBossws/services see: https://jira.jboss.org/jira/browse/JBIDE-5725 How can it deploy something that can't be remove-added? -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5870?page=com.atlassian.jira.plu... ] Max Rydahl Andersen updated JBIDE-5870: --------------------------------------- Component/s: Webservices Fix Version/s: 3.1.0.CR2 Priority: Critical (was: Major) Moved to jbide since not jbds specific. Also marking as critical for CR2 - not for fixing, but at least for understanding what is going on 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

[ https://jira.jboss.org/jira/browse/JBIDE-5870?page=com.atlassian.jira.plu... ] David Ward commented on JBIDE-5870: ----------------------------------- I looked at what Brian sent me, and I have a fix. Basically, you need to add a META-INF/application.xml to the ear file, and define a context path for the war. If you don't, the URL for WSDL defaults to this: http://127.0.0.1:8080/JBIDE1105WSEAR-JBIDE1105WS/JbossWS?wsdl when it really needs to be this: http://127.0.0.1:8080/JBIDE1105WS/JbossWS?wsdl So, the fix, as I mentioned above, is to add a META-INF/application.xml to the ear file like specificying the context path: <?xml version="1.0" encoding="UTF-8"?> <application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd" version="5"> <display-name>JBIDE1105WS</display-name> <module> <web> <web-uri>JBIDE1105WS.war</web-uri> <context-root>/JBIDE1105WS</context-root> </web> </module> </application> Hope this helps, David -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5870?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-5870: -------------------------------------------- David, is this a bug or feature ? shuoldn't it just work without application.xml ? Brian, its not about deployment here, its about project creation - it should add the application.xml when creating the project. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5870?page=com.atlassian.jira.plu... ] 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 -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5870?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-5870: -------------------------------------------- Grid, im way more interested in us not having to generate WAR in EAR. The tomcat stuff does it, why dont we ? -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5870?page=com.atlassian.jira.plu... ] Feng Qian updated JBIDE-5870: ----------------------------- Attachment: org.jboss.tools.ws.creation.patch The patch is a fix for this issue. Just did some basic tests. If someone wait for this fix, please test it at first with me. I will go on testing for this on more scene in some hours. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5870?page=com.atlassian.jira.plu... ] Brian Fitzpatrick commented on JBIDE-5870: ------------------------------------------ Grid, though I'm not getting the same error Libor is, I'm still getting the "Selection Must be WSDL" error dialog even with your patch. What steps are you following to get this to work? -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5870?page=com.atlassian.jira.plu... ] Brian Fitzpatrick commented on JBIDE-5870: ------------------------------------------ I take that back... It does work, but it still gives me the Selection Must Be WSDL message for some reason. If I remove the project from the server and put it back on the server, it deploys fine and the JbossWS console can see it. But the wizard is deploying it to: 08:07:04,457 INFO [TomcatDeployment] deploy, ctxPath=/webJBIDE5870d 08:07:04,585 INFO [WSDLFilePublisher] WSDL published to: file:/NotBackedUp/bfitzpat/runtimes/jboss-soa-p.5.0.0/jboss-as/server/default/data/wsdl/webJBIDE5870dEAR.ear/webJBIDE5870d.war/Hello4060797287880385934.wsdl And it's resolving to an endpoint of: Endpoint Name jboss.ws:context=webJBIDE5870dEAR-webJBIDE5870d,endpoint=JbossWS Endpoint Address http://localhost:8080/webJBIDE5870dEAR-webJBIDE5870d/JbossWS?wsdl This doesn't work for the JBossWS console. It can't find it. But if you cancel the wizard after it fails and undeploy the EAR from the server, then redeploy it, it works. There is an application.xml in the EAR in both cases, but for some reason it's not deploying correctly from the wizard. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5870?page=com.atlassian.jira.plu... ] David Ward commented on JBIDE-5870: ----------------------------------- Wow. Sorry I'm late coming back to the party. The reason I suggested adding a foo.ear/META-INF/application.xml was so that you could specify the context root of the war file, so that the URL to the WSDL is what is expected. That was fine IMO, because I was told the problem only exists if the application packaging was EAR. However, if the application packaging is just WAR, then the name of the context root will default to the name of the WAR file (minus the .war extension). However, if you don't want that, all you have to do is add a foo.war/WEB-INF/jboss-web.xml and specify the context root there, like so: <?xml version="1.0" encoding="UTF-8"?> <jboss-web> <context-root>bar</context-root> </jboss-web> So in the above, if the WAR was called "foo.war", having the above would mean the URL would instead be http://localhost:8080/bar/. So basically, you don't have to have an EAR project just because you want to configure the context root. Make sense? Hope this helps, David -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5870?page=com.atlassian.jira.plu... ] Brian Fitzpatrick updated JBIDE-5870: ------------------------------------- Attachment: final.patch Final patch fixing the issue. This will be delivered to the CR2 branch ("*.x") and trunk. The remaining issue is that the WTP Web Services wizard will still complain about the WSDL. Close the error dialog and cancel the wizard and the service should have deployed correctly in the EAR with the associated application.xml. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5870?page=com.atlassian.jira.plu... ] Brian Fitzpatrick resolved JBIDE-5870. -------------------------------------- Resolution: Done -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5870?page=com.atlassian.jira.plu... ] Feng Qian commented on JBIDE-5870: ---------------------------------- Hi Libor, You means you get the same error-- 'Selection must be WSDL' when you creating axis2 web service? I said it should be wtp web service framework issues, we should launch a issue to wtp. -- 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

[ https://jira.jboss.org/browse/JBIDE-5870?page=com.atlassian.jira.plugin.s... ] Libor Zoubek closed JBIDE-5870. ------------------------------- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira