[JBoss JIRA] (JBIDE-14739) Generated JBoss WS SOAP message is invalid
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14739?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-14739:
-------------------------------------------
This is quite weird, since I can get the WSDL after a full republish and the echo operation is there. It works (generating the SOAP message via JBoss WISE) if I do it a second time, but fails that first time EVERY time if I've already successfully generated the SOAP message for the other operation.
> 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] (JBIDE-14739) Generated JBoss WS SOAP message is invalid
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14739?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-14739:
-------------------------------------------
Excellent point. Turns out it's a ResourceNotAvailableException.
{code}
org.jboss.wise.core.exception.ResourceNotAvailableException: Cannot find requested method (operation): echo
at org.jboss.wise.core.client.impl.reflection.WSDynamicClientImpl.getWSMethod(WSDynamicClientImpl.java:208)
at org.jboss.wise.ui.internal.util.WiseUtil$1.run(WiseUtil.java:88)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
{code}
I've republished the project on the server (a full republish via the tooling) and am seeing the echo operation show up in the wsdl. Is it being cached somewhere?
> 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] (JBIDE-11903) OpenShift Explorer: add Application start/stop/restart
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11903?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-11903:
------------------------------------------
we're running out of time for this nice-to-have. Thus postponing to 4.1.x
> OpenShift Explorer: add Application start/stop/restart
> -------------------------------------------------------
>
> Key: JBIDE-11903
> URL: https://issues.jboss.org/browse/JBIDE-11903
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Beta2
> Environment: Eclipse plugin
> Reporter: Nam Duong
> Assignee: Andre Dietisheim
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Beta2
>
>
> The OpenShift Console view should contain controls for application start|stop|restart to match the functionality of the CLI. Currently, if you select Window->Show View->Others->OpenShift Express Console, then login in and select an application. The right-click menu doesn't have start|stop|restart so users have to either install the rhc client tools or ssh onto the OpenShift host gear.
--
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-11903) OpenShift Explorer: add Application start/stop/restart
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11903?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-11903:
-------------------------------------
Fix Version/s: 4.1.x
(was: 4.1.0.Beta2)
> OpenShift Explorer: add Application start/stop/restart
> -------------------------------------------------------
>
> Key: JBIDE-11903
> URL: https://issues.jboss.org/browse/JBIDE-11903
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Beta2
> Environment: Eclipse plugin
> Reporter: Nam Duong
> Assignee: Andre Dietisheim
> Labels: new_and_noteworthy
> Fix For: 4.1.x
>
>
> The OpenShift Console view should contain controls for application start|stop|restart to match the functionality of the CLI. Currently, if you select Window->Show View->Others->OpenShift Express Console, then login in and select an application. The right-click menu doesn't have start|stop|restart so users have to either install the rhc client tools or ssh onto the OpenShift host gear.
--
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-11881) Display application state in OpenShift Explorer and Properties view
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11881?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-11881:
------------------------------------------
we're running out of time for this nice-to-have. Thus postponing to 4.1.x
> Display application state in OpenShift Explorer and Properties view
> -------------------------------------------------------------------
>
> Key: JBIDE-11881
> URL: https://issues.jboss.org/browse/JBIDE-11881
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Beta3
> Reporter: Xavier Coulon
> Assignee: Andre Dietisheim
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Beta2
>
>
> From Bugzilla#805989
> The state of the application on each gear can be checked using the gear_groups
> rest api.
> /broker/rest/domains/<domain-name>/applications/<app-name>/gear_groups
> This rest call reflects the state of the application on each gear based on the
> contents of the file $OPENSHIFT_GEAR_DIR/runtime/.state
> The following states should be tracked in ~/runtime/.state
> stopped
> building
> deploying
> started
> idle
> unknown
--
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-11881) Display application state in OpenShift Explorer and Properties view
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11881?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-11881:
-------------------------------------
Fix Version/s: 4.1.x
(was: 4.1.0.Beta2)
> Display application state in OpenShift Explorer and Properties view
> -------------------------------------------------------------------
>
> Key: JBIDE-11881
> URL: https://issues.jboss.org/browse/JBIDE-11881
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Beta3
> Reporter: Xavier Coulon
> Assignee: Andre Dietisheim
> Labels: new_and_noteworthy
> Fix For: 4.1.x
>
>
> From Bugzilla#805989
> The state of the application on each gear can be checked using the gear_groups
> rest api.
> /broker/rest/domains/<domain-name>/applications/<app-name>/gear_groups
> This rest call reflects the state of the application on each gear based on the
> contents of the file $OPENSHIFT_GEAR_DIR/runtime/.state
> The following states should be tracked in ~/runtime/.state
> stopped
> building
> deploying
> started
> idle
> unknown
--
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-14462) HTML5/jQuery Mobile Palette Missing Elements
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14462?page=com.atlassian.jira.plugi... ]
Alexey Kazakov resolved JBIDE-14462.
------------------------------------
Resolution: Done
> HTML5/jQuery Mobile Palette Missing Elements
> --------------------------------------------
>
> Key: JBIDE-14462
> URL: https://issues.jboss.org/browse/JBIDE-14462
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Burr Sutter
> Assignee: Alexey Kazakov
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Beta2
>
> Attachments: Audio.png, AudioWizBan.png, Form.png, FormWizBan.png, Image.png, ImageWizBan.png, Label.png, LabelWizBan.png, LabelWizBan.png, scr.png, Video.png, VideoWizBan.png
>
>
> form
> img
> video
> audio
> label
> !scr.png!
--
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-14462) HTML5/jQuery Mobile Palette Missing Elements
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14462?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-14462:
-----------------------------------
Description:
form
img
video
audio
label
!scr.png!
was:
form
img
video
audio
label
!src.png!
> HTML5/jQuery Mobile Palette Missing Elements
> --------------------------------------------
>
> Key: JBIDE-14462
> URL: https://issues.jboss.org/browse/JBIDE-14462
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Burr Sutter
> Assignee: Alexey Kazakov
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Beta2
>
> Attachments: Audio.png, AudioWizBan.png, Form.png, FormWizBan.png, Image.png, ImageWizBan.png, Label.png, LabelWizBan.png, LabelWizBan.png, scr.png, Video.png, VideoWizBan.png
>
>
> form
> img
> video
> audio
> label
> !scr.png!
--
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