[JBoss JIRA] (JBIDE-12098) OpenShift Explorer: Timeout exception when forcing domain deletion
by Stefan Bunciak (JIRA)
Stefan Bunciak created JBIDE-12098:
--------------------------------------
Summary: OpenShift Explorer: Timeout exception when forcing domain deletion
Key: JBIDE-12098
URL: https://issues.jboss.org/browse/JBIDE-12098
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.CR1
Reporter: Stefan Bunciak
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.3.0.CR1, 3.3.x
Attachments: deletedomain.png
Tried to force domain deletion while having (medium geared) application on OpenShift.
Screenshot:
!deletedomain.png|thumbnail!
Stack trace:
{code}
com.openshift.client.OpenShiftTimeoutException: Could not request url https://openshift.redhat.com/broker/rest/domains/rhdomain, connection timed out
at com.openshift.internal.client.RestService.request(RestService.java:109)
at com.openshift.internal.client.RestService.request(RestService.java:89)
at com.openshift.internal.client.RestService.request(RestService.java:74)
at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:137)
at com.openshift.internal.client.DomainResource$DeleteDomainRequest.execute(DomainResource.java:329)
at com.openshift.internal.client.DomainResource.destroy(DomainResource.java:166)
at org.jboss.tools.openshift.express.internal.ui.action.DeleteDomainAction$1.run(DeleteDomainAction.java:94)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBIDE-12371) Update Eclipse Target Platform to use Graphiti 0.9
by Rob Cernich (JIRA)
Rob Cernich created JBIDE-12371:
-----------------------------------
Summary: Update Eclipse Target Platform to use Graphiti 0.9
Key: JBIDE-12371
URL: https://issues.jboss.org/browse/JBIDE-12371
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: SOA Tooling, SwitchYard, target-platform
Affects Versions: 3.3.x
Reporter: Rob Cernich
Assignee: Douglas Palmer
Priority: Critical
SwitchYard loosely integrates with the Eclipse BPMN2 editor, which has recently upgraded to Graphiti 0.9. Because of this, SwitchYard could not be installed alongside the BPMN2, so SwitchYard needed to upgrade to Graphiti 0.9. This has caused the soa-tools 3.3.x aggregate build to fail because it cannot locate the Graphiti 0.9 plugins.
If SwitchYard is the only project relying on Graphiti, we can simply upgrade the target platforms for Indigo and Juno to include Graphiti 0.9.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (JBIDE-12409) Smooks Editor is not properly connecting source and target data, drawing lines on random directions
by Isaac Rooskov (JIRA)
Isaac Rooskov created JBIDE-12409:
-------------------------------------
Summary: Smooks Editor is not properly connecting source and target data, drawing lines on random directions
Key: JBIDE-12409
URL: https://issues.jboss.org/browse/JBIDE-12409
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: smooks
Affects Versions: 3.2.2.Final
Reporter: Vinicius Martinez
Assignee: Brian Fitzpatrick
Priority: Critical
*From Bugzilla*
Description of problem:
Users are facing an accord issue with Smooks Editor which is not connecting input and outputs sources, thus, it's drawing lines on "random" directions
Steps to Reproduce:
1- Create a new ESB project
2 - File > New > Other > Smooks Configuration File
3 - Select Input Task
4 -Set Input Type to XSD/WSDL
5 - Add an XSD file in the Input Data section
6 - Click (+) next to Input Task > Apply Template > Message Type XML > Load an XSD file
Actual results:
Line does not connect two elements, and is drawn in a random direction
Expected results:
The "connection" between Input and Destiny should be perfectly aligned
Isaac's Note: Setting Vinicius as the reporter since he was in Bugzilla.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months