September 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-9726) inconsistent licensing terms across JBoss Tools - SOA Tooling site

by Nick Boldt (JIRA)

inconsistent licensing terms across JBoss Tools - SOA Tooling site ------------------------------------------------------------------ Key: JBIDE-9726 URL: https://issues.jboss.org/browse/JBIDE-9726 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools, pi4soa, Savara, teiid, updatesite Affects Versions: 3.3.0.M3 Reporter: Nick Boldt Assignee: Kris Verlaenen Fix For: 3.3.0.M4 Attachments: inconsistent-license-details.png Most features in JBoss Tools have a license from Red Hat which mentions EPL, GPL, and other licenses. It's a catch-all which allows a cleaner view of what's being installed. !inconsistent-license-details.png! The following features should adopt this statement in their features so that we're consistent across the board: Savara (GPL) Drools (ASL) pi4soa (ASL) Teiid (EPL) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

9
15
0 / 0

[JBoss JIRA] Created: (JBIDE-9727) Drools license terms could be consistent w/ rest of JBoss Tools - SOA Tooling site

by Nick Boldt (JIRA)

Drools license terms could be consistent w/ rest of JBoss Tools - SOA Tooling site ---------------------------------------------------------------------------------- Key: JBIDE-9727 URL: https://issues.jboss.org/browse/JBIDE-9727 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: drools Affects Versions: 3.3.0.M3 Reporter: Nick Boldt Assignee: Kris Verlaenen Fix For: 3.3.0.M4 Most features in JBoss Tools have a license from Red Hat which mentions EPL, GPL, and other licenses. It's a catch-all which allows a cleaner view of what's being installed. See parent task for details. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

6
10
0 / 0

[JBoss JIRA] Created: (JBIDE-8490) top down ws impl class contains wrong value for WebService.serviceName

by Lukas Jungmann (JIRA)

top down ws impl class contains wrong value for WebService.serviceName ---------------------------------------------------------------------- Key: JBIDE-8490 URL: https://issues.jboss.org/browse/JBIDE-8490 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.Final Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick -have attached wsdl - it defines 4 (basic with 2 ports, extra with 2 ports, square with 1 port and square12 with 1 port) services -create a web service from it => actual: all generated web service impl classes have serviceName attribute of @WebService set to "square" expected: serviceName attribute of @WebService set to - "square" in SquarePortTypeImpl - "basic" in AddPortTypeImpl and MinusPortTypeImpl - "extra" in DividerPortTypeImpl and MultiplyPortTypeImpl -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

5
16
0 / 0

[JBoss JIRA] Created: (JBIDE-6771) Exception creating top-down web service implementation class

by Jeff DeLong (JIRA)

Exception creating top-down web service implementation class ------------------------------------------------------------ Key: JBIDE-6771 URL: https://jira.jboss.org/browse/JBIDE-6771 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.M1 Environment: Mac Eclipse 3.6 Reporter: Jeff DeLong Assignee: Brian Fitzpatrick I tried to create a top down web service from a WSDL generated by Savara plugins. When I got to the JBoss Web Service Code Generation Configuration, I go the following error Failed to generate implementation class org.eclipse.core.runtime.CoreException: Failed to Generate Web Service code, please check the log for more details at org.jboss.tools.ws.creation.core.commands.ImplementationClassCreationCommand.getCompilationUnitForInterface(ImplementationClassCreationCommand.java:446) at org.jboss.tools.ws.creation.core.commands.ImplementationClassCreationCommand.generateImplClass(ImplementationClassCreationCommand.java:133) at org.jboss.tools.ws.creation.core.commands.ImplementationClassCreationCommand.execute(ImplementationClassCreationCommand.java:97) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:359) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:254) at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$6.run(SimpleCommandEngineManager.java:294) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1008) at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:264) at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:91) at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.getNextPage(WizardPageManager.java:154) at org.eclipse.wst.command.internal.env.ui.widgets.SimpleWizardPage.getNextPage(SimpleWizardPage.java:136) at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:887) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:426) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:3776) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1367) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1390) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1375) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1187) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3622) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3277) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:254) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:274) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:3776) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1367) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1390) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1375) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1187) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3622) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3277) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) 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:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) eclipse.buildId=I20100608-0911 java.version=1.6.0_20 java.vendor=Apple Inc. BootLoader constants: OS=macosx, ARCH=x86, WS=cocoa, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product -keyring /Users/jdelong/.eclipse_keyring -showlocation Command-line arguments: -os macosx -ws cocoa -arch x86 -product org.eclipse.epp.package.jee.product -keyring /Users/jdelong/.eclipse_keyring -showlocation Error Tue Aug 03 16:41:40 MDT 2010 Failed to Generate Web Service code, please check the log for more details org.eclipse.core.runtime.CoreException: Failed to Generate Web Service code, please check the log for more details at org.jboss.tools.ws.creation.core.commands.ImplementationClassCreationCommand.getCompilationUnitForInterface(ImplementationClassCreationCommand.java:446) at org.jboss.tools.ws.creation.core.commands.ImplementationClassCreationCommand.generateImplClass(ImplementationClassCreationCommand.java:133) at org.jboss.tools.ws.creation.core.commands.ImplementationClassCreationCommand.execute(ImplementationClassCreationCommand.java:97) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:359) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:254) at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$6.run(SimpleCommandEngineManager.java:294) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1008) at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:264) at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:91) at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.getNextPage(WizardPageManager.java:154) at org.eclipse.wst.command.internal.env.ui.widgets.SimpleWizardPage.getNextPage(SimpleWizardPage.java:136) at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:887) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:426) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:3776) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1367) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1390) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1375) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1187) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3622) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3277) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:254) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:274) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:3776) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1367) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1390) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1375) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1187) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3622) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3277) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) 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:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) My server is JBoss EAP and I used JBossWS as web services runtime. I will attach the WSDL file and XSDs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

5
41
0 / 0

[JBoss JIRA] Created: (JBIDE-9800) Open CDI Named Bean dialog works incorrectly with beans declared in seam-config

by Alexey Kazakov (JIRA)

Open CDI Named Bean dialog works incorrectly with beans declared in seam-config ------------------------------------------------------------------------------- Key: JBIDE-9800 URL: https://issues.jboss.org/browse/JBIDE-9800 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI extensions Affects Versions: 3.3.0.M3 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M4 EXECUTE: Download/clone and install http://seamframework.org/Seam3/SecurityModule as an existing maven project. Make sure CDI support is enabled for the projects. EXECUTE: Open /seam-security-example-openid-rp/src/main/resources/META-INF/seam-beans.xml EXECUTE: Remove org.jboss.seam.security.external.openid.OpenIdRpInApplicationScopeProducer (line 25) to fix this XML. Save the file. FAILURE: There is a warning "A few beans (IdentityImpl) have the same EL name and the name is not resolvable [JSR-299 §5.3.1]" on /seam-security/src/main/java/org/jboss/seam/security/IdentityImpl.java IdentityImpl.java and seam-beans.xml are placed in different but dependent projects. In this case seam-security-example-openid-rp has two beans with the same name identity. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-9729) Teiid license terms could be consistent w/ rest of JBoss Tools - SOA Tooling site

by Nick Boldt (JIRA)

Teiid license terms could be consistent w/ rest of JBoss Tools - SOA Tooling site --------------------------------------------------------------------------------- Key: JBIDE-9729 URL: https://issues.jboss.org/browse/JBIDE-9729 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: teiid Reporter: Nick Boldt Assignee: Barry LaFond Fix For: 3.3.0.M4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

7
10
0 / 0

[JBoss JIRA] Created: (JBIDE-9464) test failures in org.jboss.tools.esb.ui.bot.test

by Nick Boldt (JIRA)

test failures in org.jboss.tools.esb.ui.bot.test ------------------------------------------------ Key: JBIDE-9464 URL: https://issues.jboss.org/browse/JBIDE-9464 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: esb Affects Versions: 3.3.0.M3 Reporter: Nick Boldt Assignee: Brian Fitzpatrick Fix For: 3.3.0.M4 svn co http://svn.jboss.org/repos/jbosstools/trunk/ cd trunk; mvn clean install [INFO] org.jboss.tools.esb.ui.bot.test ................... FAILURE [19.709s] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

9
28
0 / 0

[JBoss JIRA] Created: (JBDS-1778) JBDS50_0430: [COMMIT] (Dev) Document/QA Maven Archetypes

by mark yarborough (JIRA)

JBDS50_0430: [COMMIT] (Dev) Document/QA Maven Archetypes -------------------------------------------------------- Key: JBDS-1778 URL: https://issues.jboss.org/browse/JBDS-1778 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: Requirements Reporter: mark yarborough Fix For: 5.0.0.Beta1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
7
0 / 0

[JBoss JIRA] Created: (JBDS-1769) JBDS50_0425: [COMMIT] (Dev) Modular Delivery (eg. SOA plug-ins)

by mark yarborough (JIRA)

JBDS50_0425: [COMMIT] (Dev) Modular Delivery (eg. SOA plug-ins) --------------------------------------------------------------- Key: JBDS-1769 URL: https://issues.jboss.org/browse/JBDS-1769 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: Requirements Reporter: mark yarborough -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-9239) Custom deploy folders should be added to AS7 setup like done for previous issues

by Max Rydahl Andersen (JIRA)

Custom deploy folders should be added to AS7 setup like done for previous issues -------------------------------------------------------------------------------- Key: JBIDE-9239 URL: https://issues.jboss.org/browse/JBIDE-9239 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Blocker Fix For: 3.3.0.M3 JBIDE-9085 allows targeting custom deploy folder but doesn't register the location at startup/deregister at shutdown like was done via jmx in old days. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

7
19
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 2011