[JBoss JIRA] (JBIDE-14597) ng-app AngularJS
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14597?page=com.atlassian.jira.plugi... ]
Burr Sutter commented on JBIDE-14597:
-------------------------------------
[~maxandersen]
How much influence can we bring to bear on Luna to have this sorted out in that release?
> ng-app AngularJS
> ----------------
>
> Key: JBIDE-14597
> URL: https://issues.jboss.org/browse/JBIDE-14597
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, upstream
> Reporter: Burr Sutter
> Assignee: Alexey Kazakov
> Priority: Critical
> Fix For: 4.2.x
>
> Attachments: 2013-05-23_0752.png, 2013-05-23_1548.png, html5_demo.fsh, Screen Shot 2013-05-23 at 3.51.53 PM.png
>
>
> Warning:
> Undefined attribute name (ng-app).
> Undefined attribute name (ng-controller).
> AngularJS is part of the new HTML5 Scaffolding feature in Forge 1.3
> forge install-plugin angularjs
--
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, 8 months
[JBoss JIRA] (JBIDE-15309) Marker wizard: the marker I add is not git added, committed and then pushed
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15309?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15309:
-------------------------------------
Workaround Description: After you created the marker, open the navigator view, unfold the *.openshift/markers/* directory and pick *Team->Add to Index* from the context menu on your marker file (ex. enable_jpda). The server adapter will commit and push the file that you added manually. (was: After you created the marker, open the navigator view, unfold the *.openshift/markers/* directory and pick *Team->Add to Index* from the context menu on your marker file (ex. enable_jpda))
> Marker wizard: the marker I add is not git added, committed and then pushed
> ---------------------------------------------------------------------------
>
> Key: JBIDE-15309
> URL: https://issues.jboss.org/browse/JBIDE-15309
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 4.1.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.Alpha1
>
>
--
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, 8 months
[JBoss JIRA] (JBIDE-15307) Testing deployed SwitchYard service with SOAP gateway fails with SOAPException
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15307?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-15307:
-------------------------------------------
Turns out the issue was with how I was detecting SOAP 1.2 vs. SOAP 1.1. Will have a fix momentarily.
> Testing deployed SwitchYard service with SOAP gateway fails with SOAPException
> ------------------------------------------------------------------------------
>
> Key: JBIDE-15307
> URL: https://issues.jboss.org/browse/JBIDE-15307
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Affects Versions: 4.1.0.Final
> Reporter: Brian Fitzpatrick
> Assignee: Brian Fitzpatrick
> Fix For: 4.1.1.Final
>
>
> While testing the SwitchYard tooling, discovered an issue where a deployed SwitchYard service with a SOAP gateway could not be tested. The exception is being caught and the message "InputStream does not represent a valid SOAP 1.1 Message" is being returned to the user.
> The exception is logged:
> {code}
> java.lang.Exception: javax.xml.ws.WebServiceException: javax.xml.soap.SOAPException: InputStream does not represent a valid SOAP 1.1 Message
> 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.WebServiceException: javax.xml.soap.SOAPException: InputStream does not represent a valid SOAP 1.1 Message
> at com.sun.xml.internal.ws.message.saaj.SAAJMessage.access(Unknown Source)
> at com.sun.xml.internal.ws.message.saaj.SAAJMessage.getPayloadNamespaceURI(Unknown Source)
> at com.sun.xml.internal.ws.api.message.Message.getOperation(Unknown Source)
> at com.sun.xml.internal.ws.api.message.Message.getOperation(Unknown Source)
> at com.sun.xml.internal.ws.api.message.Message.isOneWay(Unknown Source)
> at com.sun.xml.internal.ws.handler.HandlerTube.checkOneWay(Unknown Source)
> at com.sun.xml.internal.ws.handler.HandlerTube.processRequest(Unknown Source)
> at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Unknown Source)
> at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Unknown Source)
> at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Unknown Source)
> at com.sun.xml.internal.ws.api.pipe.Fiber.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> Caused by: javax.xml.soap.SOAPException: InputStream does not represent a valid SOAP 1.1 Message
> at com.sun.xml.internal.messaging.saaj.soap.ver1_1.SOAPPart1_1Impl.createEnvelopeFromSource(Unknown Source)
> at com.sun.xml.internal.messaging.saaj.soap.SOAPPartImpl.getEnvelope(Unknown Source)
> ... 14 more
> {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, 8 months
[JBoss JIRA] (JBIDE-15308) Application Details: Cannot copy application url
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15308?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15308:
-------------------------------------
Workaround Description: Click on the Public URL value and you get a new external browser (tab) that is pointing to your application. Copy the url you get in the browser.
Workaround: Workaround Exists
> Application Details: Cannot copy application url
> ------------------------------------------------
>
> Key: JBIDE-15308
> URL: https://issues.jboss.org/browse/JBIDE-15308
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.0.Alpha1
>
>
> # ASSERT: make sure that you have an application on OpenShift
> # ASSERT: make sure that you have your connection defined in the OpenShift Explorer
> # EXEC: in OpenShift Explorer: unfold your connection, select your application and choose *Details* in the context menu
> # EXEC: in the upcoming dialog try to invoke the context menu on the value of the *Public URL*
> Result:
> There's no context menu in the cell with the value of the Public URL. The context menu appears in all other cells and offers *Copy*
> Expected:
> We should also have a context menu in the Public URL cell.
--
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, 8 months
[JBoss JIRA] (JBIDE-15308) Application Details: Cannot copy application url
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-15308:
----------------------------------------
Summary: Application Details: Cannot copy application url
Key: JBIDE-15308
URL: https://issues.jboss.org/browse/JBIDE-15308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.1.0.Final
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.2.0.Alpha1
# ASSERT: make sure that you have an application on OpenShift
# ASSERT: make sure that you have your connection defined in the OpenShift Explorer
# EXEC: in OpenShift Explorer: unfold your connection, select your application and choose *Details* in the context menu
# EXEC: in the upcoming dialog try to invoke the context menu on the value of the *Public URL*
Result:
There's no context menu in the cell with the value of the Public URL. The context menu appears in all other cells and offers *Copy*
Expected:
We should also have a context menu in the Public URL cell.
--
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, 8 months
[JBoss JIRA] (JBIDE-15308) Application Details: Cannot copy application url
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15308?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15308:
-------------------------------------
Priority: Minor (was: Major)
> Application Details: Cannot copy application url
> ------------------------------------------------
>
> Key: JBIDE-15308
> URL: https://issues.jboss.org/browse/JBIDE-15308
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.0.Alpha1
>
>
> # ASSERT: make sure that you have an application on OpenShift
> # ASSERT: make sure that you have your connection defined in the OpenShift Explorer
> # EXEC: in OpenShift Explorer: unfold your connection, select your application and choose *Details* in the context menu
> # EXEC: in the upcoming dialog try to invoke the context menu on the value of the *Public URL*
> Result:
> There's no context menu in the cell with the value of the Public URL. The context menu appears in all other cells and offers *Copy*
> Expected:
> We should also have a context menu in the Public URL cell.
--
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, 8 months
[JBoss JIRA] (JBIDE-15307) Testing deployed SwitchYard service with SOAP gateway fails with SOAPException
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15307?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-15307:
-------------------------------------------
Ok. For some reason, when testing against an EAP 6.1/SY 1.0 instance, I'm not getting a good response when I invoke the web service. You can see the call here: https://github.com/jbosstools/jbosstools-webservices/blob/master/plugins/...
The response object is not a SOAPMessage when it comes back here: https://github.com/jbosstools/jbosstools-webservices/blob/master/plugins/...
We are using an older version (2.1.0) of javax.xml.ws from the Eclipse Orbit repository - which is the most recent version available in Orbit.
> Testing deployed SwitchYard service with SOAP gateway fails with SOAPException
> ------------------------------------------------------------------------------
>
> Key: JBIDE-15307
> URL: https://issues.jboss.org/browse/JBIDE-15307
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Affects Versions: 4.1.0.Final
> Reporter: Brian Fitzpatrick
> Assignee: Brian Fitzpatrick
> Fix For: 4.1.1.Final
>
>
> While testing the SwitchYard tooling, discovered an issue where a deployed SwitchYard service with a SOAP gateway could not be tested. The exception is being caught and the message "InputStream does not represent a valid SOAP 1.1 Message" is being returned to the user.
> The exception is logged:
> {code}
> java.lang.Exception: javax.xml.ws.WebServiceException: javax.xml.soap.SOAPException: InputStream does not represent a valid SOAP 1.1 Message
> 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.WebServiceException: javax.xml.soap.SOAPException: InputStream does not represent a valid SOAP 1.1 Message
> at com.sun.xml.internal.ws.message.saaj.SAAJMessage.access(Unknown Source)
> at com.sun.xml.internal.ws.message.saaj.SAAJMessage.getPayloadNamespaceURI(Unknown Source)
> at com.sun.xml.internal.ws.api.message.Message.getOperation(Unknown Source)
> at com.sun.xml.internal.ws.api.message.Message.getOperation(Unknown Source)
> at com.sun.xml.internal.ws.api.message.Message.isOneWay(Unknown Source)
> at com.sun.xml.internal.ws.handler.HandlerTube.checkOneWay(Unknown Source)
> at com.sun.xml.internal.ws.handler.HandlerTube.processRequest(Unknown Source)
> at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Unknown Source)
> at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Unknown Source)
> at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Unknown Source)
> at com.sun.xml.internal.ws.api.pipe.Fiber.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> Caused by: javax.xml.soap.SOAPException: InputStream does not represent a valid SOAP 1.1 Message
> at com.sun.xml.internal.messaging.saaj.soap.ver1_1.SOAPPart1_1Impl.createEnvelopeFromSource(Unknown Source)
> at com.sun.xml.internal.messaging.saaj.soap.SOAPPartImpl.getEnvelope(Unknown Source)
> ... 14 more
> {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, 8 months