April 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-8774) Seam2 WAR applications with Boss6 throw javax.naming.NameAlreadyBoundException thrown for TimerServiceDispatcher/local

by Gerry Matte (JIRA)

Seam2 WAR applications with Boss6 throw javax.naming.NameAlreadyBoundException thrown for TimerServiceDispatcher/local ---------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8774 URL: https://issues.jboss.org/browse/JBIDE-8774 Project: Tools (JBoss Tools) Issue Type: Bug Components: ejb3 Affects Versions: 3.2.0.Final Environment: JBoss Developer Studio 4.0.0.GA with 64 bit Java 1.6.0_24-b07 running on Windows 7 x64 with SP1 SEAM 2.2.1.Final JBoss 6.0.0.Final Reporter: Gerry Matte Assignee: Rob Stryker I created two application WARs with totally different datasources/persistence contexts. The first one is using persistence but second one is not using persistence. My first application has been in production for a month or two. When I tried to implement a second SEAM 2.2.1.Final WAR application a javax.naming.NameAlreadyBoundException was thrown for TimerServiceDispatcher/local stating that local is already bound. Both applications were created using the Eclipse "New SEAM Project" wizard and configured as a WAR application rather than an EAR application. (I'm actually using JBoss Developer 4.0). I made zero changes to any XML files other than web.xml to define some servlets and configure authentication using JBoss's JAAS container Authentication. This error did not happen on my development PC because I don't run multiple applications in the same jboss so there was no conflict between two application both trying to bind the same JNDI names. Currently, I am unable to implement a second WAR based application in this environment (Seam 2.2.1.Final on JBoss 6.0.0.Final). I may soon have to downgrade my servers back to version 5.1 until this problem is fixed by someone. Gerry -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBIDE-7798) Drools project wizard : better pre-selection version of generated code

by Libor Zoubek (JIRA)

Drools project wizard : better pre-selection version of generated code ----------------------------------------------------------------------- Key: JBIDE-7798 URL: https://jira.jboss.org/browse/JBIDE-7798 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: drools Affects Versions: 3.2.0.Beta2 Reporter: Libor Zoubek Assignee: Kris Verlaenen When creating new project, on 3rd page, when user can select drools runtime and select version of drools to generate sample sources. Selection of 'Generate code compatible with' should filter/depend on drools runtime selection. It makes no sense if you have drools 4.x to allow generating 5.x compatible sources. Moreover, when user creates new project just entering project name and has as selected 4.x as default runtime. Project with 80 errors is generated. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8069) Problem Saving Content in Drools BPMN2 Editor

by Steve Yokanovich (JIRA)

Problem Saving Content in Drools BPMN2 Editor --------------------------------------------- Key: JBIDE-8069 URL: https://issues.jboss.org/browse/JBIDE-8069 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools Affects Versions: 3.2.0.Beta2 Environment: Linux x86_64 Reporter: Steve Yokanovich Assignee: Kris Verlaenen Error when trying to save a Drools Flow file. I experienced this problem using the 3.2.0.Beta Tools installed in Eclipse 3.6 on Linux x86_64 and Windows 7 32Bit. I then downloaded the JBoss Developer Studio Early Access Release and found the same problem existed. eclipse.buildId=M20100909-0800 java.version=1.6.0_19 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Command-line arguments: -os linux -ws gtk -arch x86_64 java.lang.NullPointerException at org.drools.bpmn2.xml.XmlBPMNProcessDumper.visitProcess(XmlBPMNProcessDumper.java:136) at org.drools.bpmn2.xml.XmlBPMNProcessDumper.dump(XmlBPMNProcessDumper.java:88) at org.drools.eclipse.flow.bpmn2.editor.BPMNModelEditor.writeModel(Unknown Source) at org.drools.eclipse.flow.bpmn2.editor.BPMNModelEditor.writeModel(Unknown Source) at org.drools.eclipse.flow.common.editor.GenericModelEditor.doSave(Unknown Source) at org.eclipse.ui.internal.SaveableHelper$2.run(SaveableHelper.java:151) at org.eclipse.ui.internal.SaveableHelper$5.run(SaveableHelper.java:277) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) at org.eclipse.jface.window.ApplicationWindow$1.run(ApplicationWindow.java:759) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.window.ApplicationWindow.run(ApplicationWindow.java:756) at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:2600) at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:285) at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:264) at org.eclipse.ui.internal.SaveableHelper.savePart(SaveableHelper.java:156) at org.eclipse.ui.internal.EditorManager.savePart(EditorManager.java:1369) at org.eclipse.ui.internal.WorkbenchPage.savePart(WorkbenchPage.java:3334) at org.eclipse.ui.internal.WorkbenchPage.saveEditor(WorkbenchPage.java:3347) at org.eclipse.ui.internal.SaveAction.run(SaveAction.java:76) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) 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$6.handleEvent(ActionContributionItem.java:452) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) 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) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

4
6
0 / 0

[JBoss JIRA] Created: (JBDS-1264) DSL Validation

by Jim Tyrrell (JIRA)

DSL Validation -------------- Key: JBDS-1264 URL: https://jira.jboss.org/browse/JBDS-1264 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Environment: All Reporter: Jim Tyrrell When authoring a DLS file you will typically have variable names of the type: "{disabilityType}"=customer: Customer(disabilityType == "{disabilityType}") or something like this. If the Customer object does not exist some sort of problem should be noted in the Problems section. Also a DSL might look like this: {percentage}=eval(customer.disabledPercent >= {percentage}) This to is a little harder as the customer is a variable that is implied. -- 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

14 years, 11 months

4
3
0 / 0

[JBoss JIRA] Created: (JBDS-1548) JBRULES-2884: Drools classpath container allows modification for source and JavaDoc locations

by Masafumi Miura (JIRA)

JBRULES-2884: Drools classpath container allows modification for source and JavaDoc locations ---------------------------------------------------------------------------------------------- Key: JBDS-1548 URL: https://issues.jboss.org/browse/JBDS-1548 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: drools Affects Versions: 3.0.1.GA Reporter: Masafumi Miura -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBDS-1267) Highlighting a line in the Domain Specific Editor, the Delete key should work

by Jim Tyrrell (JIRA)

Highlighting a line in the Domain Specific Editor, the Delete key should work ----------------------------------------------------------------------------- Key: JBDS-1267 URL: https://jira.jboss.org/browse/JBDS-1267 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Affects Versions: 3.0.1.GA Environment: All Reporter: Jim Tyrrell When I am editing or creating a Domain Specific Language it would be nice to have an Accelerator on the delete key to delete the highlighted line instead of having to click "Remove". It should also be possible to highlight all of them and be able to delete them all, although this might get in the way of what you happens when you click "Edit" -- 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

14 years, 11 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-8179) Java content assist for bean names in JSF 2.0 annotations

by Yahor Radtsevich (JIRA)

Java content assist for bean names in JSF 2.0 annotations --------------------------------------------------------- Key: JBIDE-8179 URL: https://issues.jboss.org/browse/JBIDE-8179 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF Affects Versions: 3.2.0.CR1 Reporter: Yahor Radtsevich Assignee: Alexey Kazakov Fix For: 3.3.x Attachments: ManagedBean-mockup.png Provide content assist suggestions for the bean names of the following annotations: 1. @ManagedBean (see ManagedBean-mockup.png) 2. @ReferencedBean 3. @NamedEvent -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-8098) Validate that no unknown attributes are used according to tablibs

by Lukas Fryc (JIRA)

Validate that no unknown attributes are used according to tablibs ----------------------------------------------------------------- Key: JBIDE-8098 URL: https://issues.jboss.org/browse/JBIDE-8098 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: JSF Reporter: Lukas Fryc Assignee: Alexey Kazakov Currently, when you type nonexistent attribute, you are lost in the battle trying to find what's wrong. Try this: <h:commandButton id="commandButton" value="Submit" > <a4j:ajax onComplete="alert('completed')" /> </h:commandButton> Neither JSF-RI nor the IDE warn you that you did a mistake and that you should use "oncomplete" instead to show the alert window on completion. <h:commandButton id="commandButton" value="Submit" > <a4j:ajax oncomplete="alert('completed')" /> </h:commandButton> I propose to check this mistakes on level of IDE and trigger warnings where the unknown attributes is used to give user feedback . -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6914) Allow seam-gen style profiles for different environments such as prod and dev

by Samuel Mendenhall (JIRA)

Allow seam-gen style profiles for different environments such as prod and dev ----------------------------------------------------------------------------- Key: JBIDE-6914 URL: https://jira.jboss.org/browse/JBIDE-6914 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Seam Affects Versions: 3.1.1 Reporter: Samuel Mendenhall Assignee: Alexey Kazakov Fix For: 3.2.x A nice feature would be able to build a Seam EAR/WAR based on a defined profile that can be quickly changes such as -Dprofile=prod or -Dprofile-dev, which will allow for say persistence-prod.xml and persistence-dev.xml like in seam-gen. Currently this feature is not in JBDS so deploying to various environments is an added effort when it should be transparent. -- 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

14 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6095) Support for CDI implementation libraries selection and/or installation

by Jiri Peterka (JIRA)

Support for CDI implementation libraries selection and/or installation ---------------------------------------------------------------------- Key: JBIDE-6095 URL: https://jira.jboss.org/jira/browse/JBIDE-6095 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdi (jsr-299) Affects Versions: 3.1.0.GA Environment: Possibility to automatically select/download CDI implementation libraries into the project when CDI support is enabled. Reporter: Jiri Peterka Fix For: 3.2.next -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
3
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 April 2011