[JBoss JIRA] (JBIDE-13527) [tester] freeze parsing wsdl
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13527?page=com.atlassian.jira.plugi... ]
Alessio Soldano commented on JBIDE-13527:
-----------------------------------------
Hi Brian,
where does Wise enters the picture here in the actual ws endpoint invocation, besides for generating the body? IOW, afaics looking at the code and the stacktrace, the exception here is thrown when doing "Service s = Service.create(serviceURL, serviceQName);", which would then be used to create the dispatch object to be later passed the actual body to send. Now, where does the service namespace come from there? My gut feeling is that's not the same used when leveraging wise to generate the soap body.
Again, feel free to catch me on IRC.
> [tester] freeze parsing wsdl
> ----------------------------
>
> Key: JBIDE-13527
> URL: https://issues.jboss.org/browse/JBIDE-13527
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Affects Versions: 3.3.2.Final
> Reporter: Alessio Soldano
> Assignee: Brian Fitzpatrick
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Beta1
>
> Attachments: jaxws-complex.war, threaddump.txt
>
>
> JBT freezes when the ws tester is used to consume the wsdl contract for the jaxws-complex.war test deployment of JBossWS testsuite.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (JBIDE-14739) Generated JBoss WS SOAP message is invalid
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14739?page=com.atlassian.jira.plugi... ]
Alessio Soldano commented on JBIDE-14739:
-----------------------------------------
Hi Brian,
let's see if we can get more info about the issue (sorry if the questions look a bit stupid).
- Is *really* no exception being thrown by wise in client.getWSMethod()? I see a bunch of empty catch blocks after that in getSampleSOAPInputMessageFromWISE method, so wondering if it's not trapped and ignore. And if it's not throwing an exception, what's in the returned WSMethod instance?
- Is a new wsdl definition actually passed to getSampleSOAPInputMessageFromWISE after the echo() ws method is added? Btw, given you have keepSources=true, you could try have a look at the generated sources in the temp dir and see if the new method is actually there in the sources generated the second time.
- Forget about the SOAPFaultException you get, that's the minimum I'd expect from the invalid request that's being sent... however, I'm a bit concerned about those com.sun.xml.internal.ws entries in the stacktrace; are you really using the JAXWS RI on purpose or is it by chance?
You can catch me on the internal IRC server (#jbossws) or on the WidlFly channel on the public one.
> Generated JBoss WS SOAP message is invalid
> ------------------------------------------
>
> Key: JBIDE-14739
> URL: https://issues.jboss.org/browse/JBIDE-14739
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Affects Versions: 4.1.0.Beta1
> Reporter: Jaroslav Jankovič
> Assignee: Brian Fitzpatrick
> Fix For: 4.1.0.Beta2
>
>
> STEP: create dynamic web project and register web.xml (to be able to create simple soap web service)
> STEP: create simple web service (File -> New -> Other -> JBoss Tools -> Simple Web Service with default settings
> STEP: run a server, deploy a project
> STEP: open Web Service Tester, enter url of web service and try to invoke its default method (sayHello)
> STEP: open the generated web service class (HelloWorld.java)
> STEP: add a new web method like this:
> {code}
> @WebMethod()
> public String echo() {
> return "Hello World";
> }
> {code} redeploy the project
> STEP: open web service tester again, url should be still set on text box, so click on the "Get from WSDL"
> STEP: in opened dialog, choose the new method "echo", and press OK
> ASSERT: generated request message has valid format
> {code}
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
> <soap:Header/>
> <soap:Body>
> <ns2:echo xmlns:ns2="http://webservices.samples.jboss.org/"/>
> </soap:Body>
> </soap:Envelope>
> {code}
> ASSERT: invoking the generated message tends to valid response
> FAIL: generated request message has invalid format
> {code}
> <?xml version="1.0" encoding="utf-8" standalone="yes" ?>
> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" >
> <soap:Header>
> </soap:Header>
> <soap:Body>
> </soap:Body>
> </soap:Envelope>
> {code}
> FAIL: invoking the message throws a SOAPFaultException:
> {code}
> java.lang.Exception: javax.xml.ws.soap.SOAPFaultException: Fault occurred while processing.
> at org.jboss.tools.ws.ui.utils.JAXWSTester2.doTest(JAXWSTester2.java:205)
> at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.handleWSTest(JAXRSWSTestView2.java:1823)
> at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.access$34(JAXRSWSTestView2.java:1809)
> at org.jboss.tools.ws.ui.views.JAXRSWSTestView2$21.run(JAXRSWSTestView2.java:1726)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: javax.xml.ws.soap.SOAPFaultException: Fault occurred while processing.
> at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178)
> at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:111)
> at com.sun.xml.internal.ws.client.dispatch.DispatchImpl$DispatchAsyncInvoker$1.onCompletion(DispatchImpl.java:450)
> at com.sun.xml.internal.ws.client.Stub$1.onCompletion(Stub.java:381)
> at com.sun.xml.internal.ws.api.pipe.Fiber.completionCheck(Fiber.java:502)
> at com.sun.xml.internal.ws.api.pipe.Fiber.run(Fiber.java:420)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> {code}
> This issue occurs only the first time. After the first try, other tries are successful in words of SOAP message generation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (TOOLSDOC-358) Check 'install' sections as product name change will affect CSP
by Michelle Murray (JIRA)
Michelle Murray created TOOLSDOC-358:
----------------------------------------
Summary: Check 'install' sections as product name change will affect CSP
Key: TOOLSDOC-358
URL: https://issues.jboss.org/browse/TOOLSDOC-358
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Getting Started Guide, Installation Guide
Affects Versions: 4.1.0
Reporter: Michelle Murray
Assignee: Michelle Murray
Fix For: 4.1.0
Product name changing to Red Hat JBoss Developer Studio. Changes to CSP should be complete at end of June 2013. Recheck install instructions as these reference the product name labels in the CSP. Install instructions are provided in both Installation Guide and Getting Started Guide.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months