January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-655) Refactor @Service beans

by Bill Burke (JIRA)

Refactor @Service beans ----------------------- Key: EJBTHREE-655 URL: http://jira.jboss.com/jira/browse/EJBTHREE-655 Project: EJB 3.0 Issue Type: Task Reporter: Bill Burke Assigned To: Carlo de Wolf Fix For: EJB 3.0 RC9 - FD Refactor @Service beans to fix a number of problems: * magic methods for lifecycle methods: - create/start/stop/destroy * lifecycle methods are not required to be in @Management (MBean) interface. * @Management interface is not registered with the ServiceController (Controller in MC land). It *IS* registered as a regular MBean though. * If lifecycle methods exist on @Management interface, they must be intercepted on the container so that the appropriate Controler start/stop is done on the container. This would mean that you have to specify a <bind> in the Service aspect domain in ejb3-interceptors-aop.xml -- 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

17 years, 3 months

4
7
0 / 0

[JBoss JIRA] Created: (GPD-10) can't find resource

by Tom Baeyens (JIRA)

can't find resource ------------------- Key: GPD-10 URL: http://jira.jboss.com/jira/browse/GPD-10 Project: JBoss jBPM GPD Issue Type: Bug Reporter: Tom Baeyens Assigned To: Koen Aers i don't know why, but when trying to deploy the example process websale after modifying the form.create.xhtml, i got this exception that disabled depoyment of the process. java.lang.NullPointerException at org.jbpm.ui.util.ProcessDeployer.addClassOrResource(Unknown Source) at org.jbpm.ui.util.ProcessDeployer.addClassesAndResources(Unknown Source) at org.jbpm.ui.util.ProcessDeployer.createParBytes(Unknown Source) at org.jbpm.ui.util.ProcessDeployer.access$1(Unknown Source) at org.jbpm.ui.util.ProcessDeployer$1.run(Unknown Source) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:369) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:479) at org.jbpm.ui.util.ProcessDeployer.showProgressMonitorDialog(Unknown Source) at org.jbpm.ui.util.ProcessDeployer.deploy(Unknown Source) at org.jbpm.ui.editor.form.deployment.DeploymentForm$1.widgetSelected(Unknown Source) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) 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:585) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336) at org.eclipse.core.launcher.Main.basicRun(Main.java:280) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952) -- 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

17 years, 3 months

3
10
0 / 0

[JBoss JIRA] Created: (GPD-23) deployment with problems still gives "process was deployed successfull"

by Koen Aers (JIRA)

deployment with problems still gives "process was deployed successfull" ----------------------------------------------------------------------- Key: GPD-23 URL: http://jira.jboss.com/jira/browse/GPD-23 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.alpha3 Add more meaningful result notifications upon deploying process archives. -- 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

17 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (GPD-32) Class chooser limited to jbpm3.1.1 jar classes in Eclipse 3.2 (designer 3.0.9+)

by Koen Aers (JIRA)

Class chooser limited to jbpm3.1.1 jar classes in Eclipse 3.2 (designer 3.0.9+) ------------------------------------------------------------------------------- Key: GPD-32 URL: http://jira.jboss.com/jira/browse/GPD-32 Project: JBoss jBPM GPD Issue Type: Bug Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.beta1 When trying to lookup the class implementing an action handler, the class chooser dialog fails to see classes other than those in jBPM-3.1.1. This applies to task assignments as well. To re-create, create an action handler in a different eclipse project, place that project on the classpath of the process project, and invoke the class chooser for an action in a process definition. Typing the short name of the class does not cause the list of candidates to appear. Nor does typing the fully qualified name. Typing in "ActionHandler" causes candidates from the jBPM-3.1.1 jar file to appear. Classpath is proven to be complete, because pasting the fully qualified class name into the handler class field causes the designer to display the configuration fields that are available. This is also the workaround. -- 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

17 years, 4 months

2
7
0 / 0

[JBoss JIRA] Created: (GPD-16) moving nodes around corrupts process

by Koen Aers (JIRA)

moving nodes around corrupts process ------------------------------------ Key: GPD-16 URL: http://jira.jboss.com/jira/browse/GPD-16 Project: JBoss jBPM GPD Issue Type: Bug Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers in the XML i moves some nodes around. that lead to a corrupted graphical view. i tried to delete the whole gpd.xml content (and then the whole) file in the hope that the graphical content would be restored, but instead i lost the content of the processdefinition.xml and had to start all over again. -- 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

17 years, 4 months

3
9
0 / 0

[JBoss JIRA] Created: (GPD-34) Review the extension points and mechanism.

by Koen Aers (JIRA)

Review the extension points and mechanism. ------------------------------------------ Key: GPD-34 URL: http://jira.jboss.com/jira/browse/GPD-34 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Reporter: Koen Aers Assigned To: Koen Aers -- 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

17 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-3495) Windows service for JBossAS

by Luc Texier (JIRA)

Windows service for JBossAS --------------------------- Key: JBAS-3495 URL: http://jira.jboss.com/jira/browse/JBAS-3495 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Other Environment: Win32 Reporter: Luc Texier Fix For: JBossAS-5.0.0.Beta Windows users have a hard time deploying JBossAS as a Windows service. Most of them try to use JavaService from ObjectWeb which is too generic to support properly an application server instance. For exemple, generating thread dumps is impossible. Also the experience has shown that this tool is fairly broken causing hang-ups. -- 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

17 years, 4 months

5
9
0 / 0

[JBoss JIRA] Created: (JBAS-3425) Remove ClusterPartition's creation of a unique node name

by Brian Stansberry (JIRA)

Remove ClusterPartition's creation of a unique node name -------------------------------------------------------- Key: JBAS-3425 URL: http://jira.jboss.com/jira/browse/JBAS-3425 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 With the completion of JGRP-129, a unique node name can be obtained from the JGroups layer, so we should remove the creation of the name by cluster partition. -- 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

17 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3864) HttpSession replication does not always retry if replication fails

by Brian Stansberry (JIRA)

HttpSession replication does not always retry if replication fails ------------------------------------------------------------------ Key: JBAS-3864 URL: http://jira.jboss.com/jira/browse/JBAS-3864 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-4.2.0.CR1 If replication of a session fails, the session replication layer does not retry. This leaves the local session map in JBossCacheManager out of sync with the distributed cache. If there is a failover while the distributed cache is out of sync, the user will see stale data. Need to retry a (configurable) X number of times. If the session still doesn't replicate, need to decide what to do -- i.e. is it too late in the request cycle to throw an exception and return an error to the client? -- 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

17 years, 4 months

3
9
0 / 0

[JBoss JIRA] Created: (JBAS-3764) Benchmark effect of JBoss Serialization in http session repl

by Brian Stansberry (JIRA)

Benchmark effect of JBoss Serialization in http session repl ------------------------------------------------------------ Key: JBAS-3764 URL: http://jira.jboss.com/jira/browse/JBAS-3764 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 Benchmark to help decide whether to use it and whether to make it an option. -- 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

17 years, 4 months

2
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2007