[JBoss JIRA] (JBIDE-12118) OpenShift: more specific auth error description
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12118?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-12118:
------------------------------------------
I am not sure that having an uniformous error message really is what we want. There are many other reasons for SSH failures, not just keys that are not listed. You can cancel the passphrase dialog when you're prompted, you can have invalid keys and you can also have keys that are removed from OpenShift.
IMHO there's nothing but some wording that can get improved but we tell the user what operation he triggered went wrong unveiling the internal details in the details only.
WDYT?
> OpenShift: more specific auth error description
> -----------------------------------------------
>
> Key: JBIDE-12118
> URL: https://issues.jboss.org/browse/JBIDE-12118
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.0.CR1
> Reporter: Stefan Bunciak
> Assignee: Xavier Coulon
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: port.png, tail.png
>
>
> Provide a uniform message in the Error dialogs like in JBIDE-11810, saying that user probably doesn't have ssh key listed in preferences.
> Current state:
> * Port forwarding, environment variables
> !port.png|thumbnail!
> * Tail files
> !tail.png|thumbnail!
--
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, 3 months
[JBoss JIRA] (JBIDE-12306) OpenShift wizard remebers filled app info even though I'm using a different user
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12306?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-12306.
--------------------------------------
Resolution: Out of Date
This does not happen any more in the current implementation (4.2.0.Alpha1). Once you get back to the credentials page and return to the applications page, all the settings are resetted. Especially the name of the existing application is blanked thus the error described in the description wont appear.
> OpenShift wizard remebers filled app info even though I'm using a different user
> --------------------------------------------------------------------------------
>
> Key: JBIDE-12306
> URL: https://issues.jboss.org/browse/JBIDE-12306
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.2.0.Alpha1, 4.0.0.Alpha1
>
> Attachments: JBIDE-11310.patch, JBIDE12306.patch, prefilled.png
>
>
> The wizard model probably doesn't refresh/reset...
--
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, 3 months
[JBoss JIRA] (JBIDE-15307) Testing deployed SwitchYard service with SOAP gateway fails with SOAPException
by Brian Fitzpatrick (JIRA)
Brian Fitzpatrick created JBIDE-15307:
-----------------------------------------
Summary: 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, 3 months