[JBoss JIRA] (JBIDE-11454) Make the status of modules be closer to reality
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11454?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-11454.
---------------------------------
Resolution: Done
Yep. The change was "rolled back" so the previous version is still there. Thats what my testing time shows.
> Make the status of modules be closer to reality
> -----------------------------------------------
>
> Key: JBIDE-11454
> URL: https://issues.jboss.org/browse/JBIDE-11454
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Environment: JBoss Developer Studio 5 Beta
> JBoss Enterprise Application 6 Beta
> Reporter: Mustafa Musaji
> Assignee: Rob Stryker
> Priority: Minor
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Beta2
>
>
> When deployment of an application fails on JBoss EAP, JBoss Tools doesn't recognize this as failure and continues to report the status as [Started, Synchronized].
> This a request to add the ability for JBDS to report back via the console when a deployment fails due to application errors.
--
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-14741) Have show in > Cheat sheets work at project level
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-14741:
-------------------------------------------
Summary: Have show in > Cheat sheets work at project level
Key: JBIDE-14741
URL: https://issues.jboss.org/browse/JBIDE-14741
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: project-examples
Reporter: Max Rydahl Andersen
Fix For: 4.1.0.Beta2
If a project has a cheatsheet etc. we recognize on project open users should be able to right click the Project and do Show in Cheat sheets.
This is to avoid TOOLSDOC-336 where users have to make .cheatsheet visible to find the cheatsheet.
--
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-14549) Deploying archive via drag&drop triggers server start
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14549?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-14549:
--------------------------------
Component/s: upstream
Linking to upstream bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=409826
> Deploying archive via drag&drop triggers server start
> -----------------------------------------------------
>
> Key: JBIDE-14549
> URL: https://issues.jboss.org/browse/JBIDE-14549
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: archives, upstream
> Affects Versions: 4.1.0.Beta1
> Reporter: Jaroslav Jankovič
> Assignee: Rob Stryker
> Fix For: 4.1.1.Final
>
>
> If archive is deployed with Publish dialog, server is (correctly) not started. However, drag&drop archive under server in servers view cause server starting.
> STEP: create a simple java project
> STEP: create an archive in it (via explorer/view)
> STEP: in Project Explorer view, expand Project Archives explorer, select the created archive and drag & drop into server in server's view
> ASSERT: archive is deployed on the server
> FAIL: server start is initiated but I think it should be not, because archive deploy via Publish Archive dialog doesn't trigger server's start
> There is another bug. When user wants to drag&drop whole project into the server, server's starting process is also initiated, but should be not.
> STEP: create a simple java project
> STEP: open Project Explorer view and drag & drop the project into a server
> ASSERT: project is deployed
> ASSERT: server is not started
> STEP: undeploy the project from a server
> STEP: create an archive in the project
> STEP: drag & drop the project into a server
> ASSERT: project is deployed
> FAIL: server's start is triggered
--
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-14544) Cannot run Cordova project on Android Emulator/Device
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14544?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-14544:
-------------------------------------
Separate issue created for MS Windows OS. https://issues.jboss.org/browse/JBIDE-14740
> Cannot run Cordova project on Android Emulator/Device
> -----------------------------------------------------
>
> Key: JBIDE-14544
> URL: https://issues.jboss.org/browse/JBIDE-14544
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.0.Beta1
> Environment: Fedora 17 32bit
> Android 4.1.2
> Reporter: Stefan Bunciak
> Assignee: Gorkem Ercan
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.1.0.Beta2
>
> Attachments: runasandroidemulatorwin7_32.png, Screen Shot 2013-06-03 at 10.50.52 AM.png
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> {code}
> java.io.IOException: No such file or directory
> at java.io.UnixFileSystem.createFileExclusively(Native Method)
> at java.io.File.createNewFile(File.java:883)
> at org.jboss.tools.aerogear.hybrid.core.util.FileUtils.fileCopy(FileUtils.java:105)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidProjectGenerator.generateNativeFiles(AndroidProjectGenerator.java:99)
> at org.jboss.tools.aerogear.hybrid.core.platform.AbstractPlatformProjectGenerator.generateNow(AbstractPlatformProjectGenerator.java:68)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:68)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:825)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:706)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
--
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 Jaroslav Jankovič (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14739?page=com.atlassian.jira.plugi... ]
Jaroslav Jankovič updated JBIDE-14739:
--------------------------------------
Description:
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 one time. After first try, second try (and others) is successful in words of SOAP message generation.
was:
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}
> 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č
> 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 one time. After first try, second try (and others) is 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] (JBIDE-14739) Generated JBoss WS SOAP message is invalid
by Jaroslav Jankovič (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14739?page=com.atlassian.jira.plugi... ]
Jaroslav Jankovič updated JBIDE-14739:
--------------------------------------
Description:
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.
was:
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 one time. After first try, second try (and others) is successful in words of SOAP message generation.
> 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č
> 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