September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15341) use latest parent pom & target platform so we can release BPEL tooling v 1.2.100.Final

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15341?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15341: ---------------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.1.Final) set proper fix version. > use latest parent pom & target platform so we can release BPEL tooling v 1.2.100.Final > -------------------------------------------------------------------------------------- > > Key: JBIDE-15341 > URL: https://issues.jboss.org/browse/JBIDE-15341 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: bpel > Affects Versions: 4.1.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.1.Alpha1 > > > Root pom should reference the latest final parent pom (4.1.0.Final-SNAPSHOT) instead of 4.1.0.Alpha1-SNAPSHOT. > Target platform referenced should be the Kepler version (4.1.1.Final) rather than the Juno version (4.0.0). > Once that's fixed and the build is blue, we should release BPEL tooling v 1.2.100.Final and include it in the latest JBTIS 4.1.0 / 4.1.1 aggregate site builds. -- 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-15310) JPP6.1 needs strict serverbean detector

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15310?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15310: ---------------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.1.Final) set proper fix version. > JPP6.1 needs strict serverbean detector > --------------------------------------- > > Key: JBIDE-15310 > URL: https://issues.jboss.org/browse/JBIDE-15310 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.1.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.1.1.Alpha1 > > > While JBDS-2703 fixes the issue of jpp-6.1 being incorrectly recognized, it'd be better if there was a strict detector for identifying jpp-6.1. -- 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-11365) Allow the user to add "Restart Module" function as a keyboard-shortcut

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11365?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-11365: ---------------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.1.Final) set proper fix version. > Allow the user to add "Restart Module" function as a keyboard-shortcut > ---------------------------------------------------------------------- > > Key: JBIDE-11365 > URL: https://issues.jboss.org/browse/JBIDE-11365 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 3.3.0.Beta1 > Reporter: Adrian Mitev > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.1.1.Alpha1 > > > Because ANYTHING is possible and the infinite is unknown at zombo.com! -- 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-15363) CLONE - NullPointerException reported in Eclipse Error view after using "Materialize Library..." on uninitialized classpath container

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15363?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15363: ---------------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.1.Final) set proper fix version. > CLONE - NullPointerException reported in Eclipse Error view after using "Materialize Library..." on uninitialized classpath container > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15363 > URL: https://issues.jboss.org/browse/JBIDE-15363 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, maven > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.1.1.Alpha1 > > > {code} > org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:63) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:850) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:743) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:727) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:662) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) > at org.eclipse.equinox.launcher.Main.run(Main.java:1450) > at org.eclipse.equinox.launcher.Main.main(Main.java:1426) > Caused by: java.lang.NullPointerException > at org.jboss.tools.common.jdt.ui.buildpath.dialog.MaterializeLibraryDialog.<init>(MaterializeLibraryDialog.java:102) > at org.jboss.tools.common.jdt.ui.buildpath.handlers.MaterializeLibraryHandler.execute(MaterializeLibraryHandler.java:80) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) > ... 37 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-15314) WS Tester fails to execute test if SOAPAction value is null

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15314?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15314: ---------------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.1.Final) set proper fix version. > 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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15307?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15307: ---------------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.1.Final) set proper fix version. > 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-15338) use latest parent pom & target platform so we can release jBPM3 tooling v 4.5.200.Final

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15338?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15338: ---------------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.1.Final) set proper fix version. > use latest parent pom & target platform so we can release jBPM3 tooling v 4.5.200.Final > --------------------------------------------------------------------------------------- > > Key: JBIDE-15338 > URL: https://issues.jboss.org/browse/JBIDE-15338 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jbpm > Affects Versions: 4.1.0.Final > Reporter: Nick Boldt > Assignee: Koen Aers > Fix For: 4.1.1.Alpha1 > > > Root pom should reference the latest final parent pom (4.1.0.Final-SNAPSHOT) instead of 4.1.0.Alpha2-SNAPSHOT. > Target platform referenced should be the Kepler version (4.1.1.Final) rather than the Juno version (4.0.0). > Once that's fixed and the build is blue, we should release jbpm3 tooling v 4.5.200.Final and include it in the latest JBTIS 4.1.0 / 4.1.1 aggregate site builds. -- 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-15342) use latest parent pom & target platform so we can release ESB tooling v 1.5.300.Final

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15342?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15342: ---------------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.1.Final) set proper fix version. > use latest parent pom & target platform so we can release ESB tooling v 1.5.300.Final > ------------------------------------------------------------------------------------- > > Key: JBIDE-15342 > URL: https://issues.jboss.org/browse/JBIDE-15342 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: esb > Affects Versions: 4.1.0.Final > Reporter: Nick Boldt > Assignee: Brian Fitzpatrick > Fix For: 4.1.1.Alpha1 > > > Root pom should reference the latest final parent pom (4.1.0.Final-SNAPSHOT) instead of 4.1.0.CR1-SNAPSHOT. > Target platform referenced should be the Kepler version (4.1.1.Final) rather than the Juno version (4.0.0). > Once that's fixed and the build is blue, we should release ESB tooling v 1.5.300.Final and include it in the latest JBTIS 4.1.0 / 4.1.1 aggregate site builds. -- 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-13651) Export Native target platform project

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13651?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13651: ---------------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.1.Final) set proper fix version. > Export Native target platform project > ------------------------------------- > > Key: JBIDE-13651 > URL: https://issues.jboss.org/browse/JBIDE-13651 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Priority: Minor > Fix For: 4.1.1.Alpha1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Create a wizard to export native projects to supported target platforms. For iOS it will be Xcode project and for Android it will be ADT. Once exported projects will have no relation with our tools and it is expected that they will continue their life on their respected tool sets. -- 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-14979) Remote Wildfly cannot be started - password not accepted

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14979?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14979: ---------------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.1.Final) set proper fix version. > Remote Wildfly cannot be started - password not accepted > -------------------------------------------------------- > > Key: JBIDE-14979 > URL: https://issues.jboss.org/browse/JBIDE-14979 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.1.0.Beta2 > Environment: OS X Mountain Lion - client > RHEL 6 - remote server > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.1.1.Alpha1 > > > When I try to create a remote server using the wildfly adapter I get stuck on tools asking me for a password and not accepting the correct password. > A side issue is that when you ignore the dialog and then try to stop the server, it will show [Stopped] in the server view, but the process will keep running on the server - it should kill the process. -- 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