November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Moved: (GPD-249) CLONE -Cannot create process definition in root project folder

by Koen Aers (JIRA)

[ https://jira.jboss.org/jira/browse/GPD-249?page=com.atlassian.jira.plugin... ] Koen Aers moved JBIDE-3141 to GPD-249: -------------------------------------- Project: JBoss jBPM GPD (was: Tools (JBoss Tools)) Key: GPD-249 (was: JBIDE-3141) Component/s: jpdl (was: jbpm) Fix Version/s: jBPM jPDL Designer 3.1.6 (was: 3.0.0.cr1) > CLONE -Cannot create process definition in root project folder > -------------------------------------------------------------- > > Key: GPD-249 > URL: https://jira.jboss.org/jira/browse/GPD-249 > Project: JBoss jBPM GPD > Issue Type: Bug > Components: jpdl > Environment: jBPM designer: 3.1.5Beta1-N200810230806 > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Critical > Fix For: jBPM jPDL Designer 3.1.6 > > > Tried to create a process definition in the top level of a project (that is, I selected a project as the destination folder, not a subfolder within the project). The following exception appears repeatedly while typing the process name in the wizard, and the Finish button is not enabled. If I select a subfolder, the wizard completes without error. > ------------------------------- > java.lang.IllegalArgumentException: Path must include project and resource name: /test_jbpm > at org.eclipse.core.runtime.Assert.isLegal(Assert.java:64) > at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:1628) > at org.eclipse.core.internal.resources.Container.getFolder(Container.java:137) > at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.checkContainerPathValid(Unknown Source) > at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.verifyContentsValid(Unknown Source) > at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.access$0(Unknown Source) > at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage$3.modifyText(Unknown Source) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:167) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033) > 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:253) > at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:273) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:281) > 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:247) > at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500) > 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.Widget.sendEvent(Widget.java:1158) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033) > at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) > at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) > 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:386) > 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:549) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) > at org.eclipse.equinox.launcher.Main.run(Main.java:1236) -- 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

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (GPD-249) Cannot create process definition in root project folder

by Koen Aers (JIRA)

[ https://jira.jboss.org/jira/browse/GPD-249?page=com.atlassian.jira.plugin... ] Koen Aers updated GPD-249: -------------------------- Summary: Cannot create process definition in root project folder (was: CLONE -Cannot create process definition in root project folder) > Cannot create process definition in root project folder > ------------------------------------------------------- > > Key: GPD-249 > URL: https://jira.jboss.org/jira/browse/GPD-249 > Project: JBoss jBPM GPD > Issue Type: Bug > Components: jpdl > Environment: jBPM designer: 3.1.5Beta1-N200810230806 > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Critical > Fix For: jBPM jPDL Designer 3.1.6 > > > Tried to create a process definition in the top level of a project (that is, I selected a project as the destination folder, not a subfolder within the project). The following exception appears repeatedly while typing the process name in the wizard, and the Finish button is not enabled. If I select a subfolder, the wizard completes without error. > ------------------------------- > java.lang.IllegalArgumentException: Path must include project and resource name: /test_jbpm > at org.eclipse.core.runtime.Assert.isLegal(Assert.java:64) > at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:1628) > at org.eclipse.core.internal.resources.Container.getFolder(Container.java:137) > at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.checkContainerPathValid(Unknown Source) > at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.verifyContentsValid(Unknown Source) > at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.access$0(Unknown Source) > at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage$3.modifyText(Unknown Source) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:167) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033) > 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:253) > at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:273) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:281) > 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:247) > at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500) > 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.Widget.sendEvent(Widget.java:1158) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033) > at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) > at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) > 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:386) > 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:549) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) > at org.eclipse.equinox.launcher.Main.run(Main.java:1236) -- 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

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-384) Implement usage of BeanMetaData abstract and parent attributes

by Ales Justin (JIRA)

Implement usage of BeanMetaData abstract and parent attributes -------------------------------------------------------------- Key: JBMICROCONT-384 URL: https://jira.jboss.org/jira/browse/JBMICROCONT-384 Project: JBoss Microcontainer Issue Type: Feature Request Components: Deployment Reporter: Ales Justin Priority: Minor Make use of BeanMetaData::abstract and BeanMetaData::parent. It is currently not used, as it doesn't have proper handling. The idea is to cover this examples: simple skeleton: <bean name="skeleton" class="org.jboss.acme.AbstractService" abstract="true"> <property name="kernel"></inject bean="KernelName"></property> <property name="tm"></inject bean="TM"></property> ... // many properties </bean> classes derived from skeleton: <bean name="x1" class="org.jboss.acme.X1" parent="skeleton"/> <bean name="x2" class="org.jboss.acme.X2" parent="skeleton"/> <bean name="y" class="org.jboss.acme.AbstractY" parent="x1" abstract="true" /> <bean name="z" class="org.jboss.acme.Z" parent="y"/> == less xml dupliction Beans with abstract==true don't really get instantiated, they just serve as metadata holder. -- 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

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-364) Upgrade to jboss aop 2.0.0.CR19

by Kabir Khan (JIRA)

Upgrade to jboss aop 2.0.0.CR19 ------------------------------- Key: JBMICROCONT-364 URL: https://jira.jboss.org/jira/browse/JBMICROCONT-364 Project: JBoss Microcontainer Issue Type: Thirdparty Change Components: AOP Reporter: Kabir Khan Assignee: Kabir Khan -- 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

15 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-182) Integrate VFS ClassLoader into new deployers and jboss-head

by Adrian Brock (JIRA)

Integrate VFS ClassLoader into new deployers and jboss-head ----------------------------------------------------------- Key: JBMICROCONT-182 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-182 Project: JBoss MicroContainer Issue Type: Task Components: Deployment Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossMC_2_0_0_CR1 Integrate VFSClassLoader into JBoss Head, including OSGi dependencies/versioning -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2231) Wrong version of Producer Configuration XSD is used

by Chris Laprun (JIRA)

Wrong version of Producer Configuration XSD is used --------------------------------------------------- Key: JBPORTAL-2231 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2231 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.7.0 Final Reporter: Chris Laprun Assignee: Chris Laprun Fix For: 2.7.1 Final 2.7 is still set to use 2.6 schema. Thanks, Denis Morozov for the report! -- 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

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2229) WSRP producer configuration file cannot be created when not using HSQL

by Chris Laprun (JIRA)

WSRP producer configuration file cannot be created when not using HSQL ---------------------------------------------------------------------- Key: JBPORTAL-2229 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2229 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.7 Final, 2.7.0 Final Reporter: Chris Laprun Assignee: Chris Laprun Fix For: 2.7.1 Final, 2.6.8 Final server/default/data/portal/ doesn't exist in that case causing the error. Thanks, Denis Morozov for the report. -- 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

15 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-6166) regression - org.jboss.test.security.test.authorization.XACMLEJBIntegrationUnitTestCase

by Dimitris Andreadis (JIRA)

regression - org.jboss.test.security.test.authorization.XACMLEJBIntegrationUnitTestCase --------------------------------------------------------------------------------------- Key: JBAS-6166 URL: https://jira.jboss.org/jira/browse/JBAS-6166 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Security Reporter: Dimitris Andreadis Assignee: Stefan Guilhen Priority: Critical Fix For: JBossAS-5.0.0.GA http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test... org.jboss.test.security.test.authorization.XACMLEJBIntegrationUnitTestCase.testMethodAccess org.jboss.test.security.test.authorization.XACMLEJBIntegrationUnitTestCase.testJBAS6067 Stefan, those 2 failures crept in with the change in: http://fisheye.jboss.com/changelog/JBossAS/?cs=80401 -- 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

15 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (SECURITY-304) Release Security 2.0.2.GA Libraries

by Anil Saldhana (JIRA)

Release Security 2.0.2.GA Libraries ----------------------------------- Key: SECURITY-304 URL: https://jira.jboss.org/jira/browse/SECURITY-304 Project: JBoss Security and Identity Management Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Anil Saldhana Assignee: Anil Saldhana -- 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

15 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBNAME-8) Security Permissions for JNDI sensitive operations

by Anil Saldhana (JIRA)

Security Permissions for JNDI sensitive operations -------------------------------------------------- Key: JBNAME-8 URL: https://jira.jboss.org/jira/browse/JBNAME-8 Project: JBoss Naming Issue Type: Task Components: jnpserver Affects Versions: 5.0.0.CR2 Reporter: Anil Saldhana Assignee: Scott M Stark Fix For: 5.0.0.GA ctx.rebind is the most critical. Please add perms to all JNDI ops. -- 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

15 years, 7 months

2
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2008