September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15261) Cannot create wordpress example

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15261?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-15261: ---------------------------------------- Assignee: Max Rydahl Andersen (was: Andre Dietisheim) Plz review my PR for maintenance at https://github.com/jbosstools/jbosstools-openshift/pull/215 > Cannot create wordpress example > ------------------------------- > > Key: JBIDE-15261 > URL: https://issues.jboss.org/browse/JBIDE-15261 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Beta2 > Reporter: nan wei > Assignee: Max Rydahl Andersen > Fix For: 4.2.0.Alpha1 > > Attachments: create-wordpress-example.png, initial-build-failed.png > > > Version: > JBoss Deverloper Studio 7 Beta > OpenShift Plugin: 2.5.0.Beta2-v20130621-1052-B65 > OpenShift Enterprise 1.2/2013-07-18.4 > How reproducible: > always > Steps to Reproduce: > 1. Create an app in the JBoss Deverloper Studio. > Name: mysqltest > Type: PHP 5.3(php-5.3) > Embeddable Cartridges: MySQL Database 5.1(mysql-5.1) > 2. Click Advanced > Add Source Code:https://github.com/openshift/wordpress-example > !create-wordpress-example.png! > Actual results: > When creating an app, check mysql cartridge and add source code together, it will fail, and return the following error: > !initial-build-failed.png! > {code} > Could not create application "a3" > Could not request https://broker.ose0717.com/broker/rest/domains/nwei/applications: The initial build for the application failed. Last 10 kB of build output: > httpd (no pid file) not running > Could not find mysql database. Please run: > rhc cartridge add -a a3 -c mysql-5.1 > then make a sample commit (add whitespace somewhere) and re-push > An error occurred executing 'gear postreceive' > For more details about the problem, try running the command again with the '--trace' option. > {code} > But if use rhc client, there is no such problem, it is created successfully. > # rhc app create mysqltest1 php-5.3 mysql-5.1 --from-code=https://github.com/openshift/wordpress-example -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15435) "installed plugins" detection seems fishy in project examples / central

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15435?page=com.atlassian.jira.plugi... ] Snjezana Peco edited comment on JBIDE-15435 at 9/5/13 4:12 PM: --------------------------------------------------------------- A JBoss Tools Central connector isn't installed if any IU defined in the connector descriptor isn't installed. The Project Examples plugin fix checks if the plugins defined in a project xml file are installed. The GWT project example requires only the com.google.gwt.core plugin. The com.google.gwt.eclipse.sdkbundle.feature and com.google.gdt.eclipse.suite.e42.feature features are required by the "Google Plugin for Eclipse (GPE) + Google Web Toolkit SDK (GWT)" connector. I can reproduce the issue because, in my distribution, the com.google.gdt.eclipse.suite.e42.feature feature is installed and includes the com.google.gwt.core plugin, but the com.google.gwt.eclipse.sdkbundle.feature feature isn't installed. The com.google.gwt.eclipse.sdkbundle plugin is also installed, but isn't included in a feature. I have installed all the JBoss Tools features using the JBT update site and got such a distribution. We could add a JBoss Tools Central connector fix/requirement to the examples component. was (Author: snjeza): A JBoss Tools Central connector isn't installed if any IU defined in the connector descriptor isn't installed. The Project Examples plugin fix checks if the plugins defined in a project xml file are installed. The GWT project example requires only the com.google.gwt.core plugin. The com.google.gwt.eclipse.sdkbundle.feature and com.google.gdt.eclipse.suite.e42.feature features are required by the "Google Plugin for Eclipse (GPE) + Google Web Toolkit SDK (GWT)" connector. I can reproduce the issue because, in my distribution, the com.google.gdt.eclipse.suite.e42.feature feature is installed and includes the com.google.gwt.core plugin, but the com.google.gwt.eclipse.sdkbundle.feature feature isn't installed. The com.google.gwt.eclipse.sdkbundle plugin is also installed, but isn't included in a feature. I have installed all the JBoss Tools features using the JBT update site and got such a distribution. We could add a JBoss Tools Central connector fix/requirement to the examples component. > "installed plugins" detection seems fishy in project examples / central > ----------------------------------------------------------------------- > > Key: JBIDE-15435 > URL: https://issues.jboss.org/browse/JBIDE-15435 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, discovery, project-examples > Affects Versions: 4.1.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: needinfo > Fix For: 4.1.1.Alpha2 > > > Following JBDS-2753, [~maxandersen] says he installed the JBoss GWT connector, which dragged the GPE plugins. > Some functionality seem missing according to Max (which ones?). In the JBoss Central 'software updates' page, the GWT/GPE connector is shown as missing. In the GWT example wizard, the feature appears as installed. One of the 2 is wrong, obviously. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15435) "installed plugins" detection seems fishy in project examples / central

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15435?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-15435: --------------------------------------- A JBoss Tools Central connector isn't installed if any IU defined in the connector descriptor isn't installed. The Project Examples plugin fix checks if the plugins defined in a project xml file are installed. The GWT project example requires only the com.google.gwt.core plugin. The com.google.gwt.eclipse.sdkbundle.feature and com.google.gdt.eclipse.suite.e42.feature features are required by the "Google Plugin for Eclipse (GPE) + Google Web Toolkit SDK (GWT)" connector. I can reproduce the issue because, in my distribution, the com.google.gdt.eclipse.suite.e42.feature feature is installed and includes the com.google.gwt.core plugin, but the com.google.gwt.eclipse.sdkbundle.feature feature isn't installed. The com.google.gwt.eclipse.sdkbundle plugin is also installed, but isn't included in a feature. I have installed all the JBoss Tools features using the JBT update site and got such a distribution. We could add a JBoss Tools Central connector fix/requirement to the examples component. > "installed plugins" detection seems fishy in project examples / central > ----------------------------------------------------------------------- > > Key: JBIDE-15435 > URL: https://issues.jboss.org/browse/JBIDE-15435 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, discovery, project-examples > Affects Versions: 4.1.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: needinfo > Fix For: 4.1.1.Alpha2 > > > Following JBDS-2753, [~maxandersen] says he installed the JBoss GWT connector, which dragged the GPE plugins. > Some functionality seem missing according to Max (which ones?). In the JBoss Central 'software updates' page, the GWT/GPE connector is shown as missing. In the GWT example wizard, the feature appears as installed. One of the 2 is wrong, obviously. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15261) Cannot create wordpress example

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15261?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15261: ------------------------------------------ PR for 4.2.0.Alpha1: https://github.com/jbosstools/jbosstools-openshift/pull/214 PR for 4.1.1.Alpha1: https://github.com/jbosstools/jbosstools-openshift/pull/215 > Cannot create wordpress example > ------------------------------- > > Key: JBIDE-15261 > URL: https://issues.jboss.org/browse/JBIDE-15261 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Beta2 > Reporter: nan wei > Assignee: Andre Dietisheim > Fix For: 4.2.0.Alpha1 > > Attachments: create-wordpress-example.png, initial-build-failed.png > > > Version: > JBoss Deverloper Studio 7 Beta > OpenShift Plugin: 2.5.0.Beta2-v20130621-1052-B65 > OpenShift Enterprise 1.2/2013-07-18.4 > How reproducible: > always > Steps to Reproduce: > 1. Create an app in the JBoss Deverloper Studio. > Name: mysqltest > Type: PHP 5.3(php-5.3) > Embeddable Cartridges: MySQL Database 5.1(mysql-5.1) > 2. Click Advanced > Add Source Code:https://github.com/openshift/wordpress-example > !create-wordpress-example.png! > Actual results: > When creating an app, check mysql cartridge and add source code together, it will fail, and return the following error: > !initial-build-failed.png! > {code} > Could not create application "a3" > Could not request https://broker.ose0717.com/broker/rest/domains/nwei/applications: The initial build for the application failed. Last 10 kB of build output: > httpd (no pid file) not running > Could not find mysql database. Please run: > rhc cartridge add -a a3 -c mysql-5.1 > then make a sample commit (add whitespace somewhere) and re-push > An error occurred executing 'gear postreceive' > For more details about the problem, try running the command again with the '--trace' option. > {code} > But if use rhc client, there is no such problem, it is created successfully. > # rhc app create mysqltest1 php-5.3 mysql-5.1 --from-code=https://github.com/openshift/wordpress-example -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15314) WS Tester fails to execute test if SOAPAction value is null

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15314?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick resolved JBIDE-15314. --------------------------------------- Resolution: Done Done > WS Tester fails to execute test if SOAPAction value is null > ----------------------------------------------------------- > > Key: JBIDE-15314 > URL: https://issues.jboss.org/browse/JBIDE-15314 > 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.Alpha1 > > > Discovered while testing the bpm-service quickstart for SwitchYard via the WS Tester. If the SOAP operation in the WSDL includes a SOAP action, the test works just fine. But if it's missing and the WSDL is not SOAP 1.2, it fails. -- 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, 7 months

1
0
0 / 0

[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 resolved JBIDE-15307. --------------------------------------- Resolution: Done Done > 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.Alpha1 > > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14366) openshift-java-client: add method overloads that allow users to provide specific timeouts to specific operations

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14366?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-14366. -------------------------------------- Resolution: Done > openshift-java-client: add method overloads that allow users to provide specific timeouts to specific operations > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-14366 > URL: https://issues.jboss.org/browse/JBIDE-14366 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > We need to have means for users to provide specific timeouts for specific operations. Ex. to create an application we'd call > {code} > domain.createApplication(name, cartridge, scale, gear) > {code} > If we want to increase timeouts for this specific operation, we cannot. We have to increase the url connection timeouts via the system properties. We should therefore offer > {code} > domain.createApplication(name, cartridge, scale, gear, TIMEOUT) > {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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15262) openshift-java-client: allow to provide cartridges when creating an application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15262?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15262: ------------------------------------------ released openshift-java-client-2.4.0.SNAPSHOT to jboss nexus > openshift-java-client: allow to provide cartridges when creating an application > ------------------------------------------------------------------------------- > > Key: JBIDE-15262 > URL: https://issues.jboss.org/browse/JBIDE-15262 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.0.Alpha1 > > > For certain openshift example one needs to be able to add cartridges when creating the application, not only afterwards. Without the cartridge present in the application some examples (ex. wordpress example at https://github.com/openshift/wordpress-example) will fail the initial build. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15392) Add api in server needed for source lookup

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15392?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-15392: --------------------------------------- Rob, Could you please tell where RuntimeJarUtility is placed? > Add api in server needed for source lookup > ------------------------------------------ > > Key: JBIDE-15392 > URL: https://issues.jboss.org/browse/JBIDE-15392 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven, server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > > As uncovered in https://github.com/jbosstools/jbosstools-central/pull/128/files#L5L120 we got a problem with source lookup code always having to play catchup with server changes. > We need to define a stable api that can be used here. > lets outline what api is actually needed and then subjiras for the specifics. > For me it looks like server lookup needs a few things: > 0. know exact version of server > 1. know the file structure of a certain server > 2. get dir or directories that contain jar that is the "runtime" > My guess is that #2 might just be sufficient for source code lookup. > Any comments ? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15431) Increment version for jbosstools-vpe module

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15431?page=com.atlassian.jira.plugi... ] Denis Golovin reassigned JBIDE-15431: ------------------------------------- Assignee: Denis Golovin > Increment version for jbosstools-vpe module > ------------------------------------------- > > Key: JBIDE-15431 > URL: https://issues.jboss.org/browse/JBIDE-15431 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Affects Versions: 4.1.1.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.1.1.Alpha1 > > Attachments: vpe-api-cahnges.html > > > API has binary compatible changes -> version for vpe module should be incremented. Eclipse guide recommends to increment minor version, but I would recommend to follow our old approach and increment service version to avoid conflicts with master branch. Thus proposed update is: > jbosstools-4.1.x: 3.5.0 => 3.5.1 > master: 3.5.0 => 3.5.100 -- 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, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2013