September 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1006) Concurrent use of 'repeat' and 'transition' in a timer declaration will result in an execution of a non existing timer.

by Andreas Schienagel (JIRA)

Concurrent use of 'repeat' and 'transition' in a timer declaration will result in an execution of a non existing timer. ----------------------------------------------------------------------------------------------------------------------- Key: JBPM-1006 URL: http://jira.jboss.com/jira/browse/JBPM-1006 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.1 Reporter: Andreas Schienagel Assigned To: Tom Baeyens As described in http://www.jboss.com/index.html?module=bb&op=viewtopic&t=112192 "If you set an transition on a timer, this transition will be taken if it reaches the duedate and no further repetitions are possible cause the timer is deleted from db. So far so good... But if you set the repeat option as well, the engine tries to execute the timer once more: " -- 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

18 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-980) superstate-enter not fired when taking a transition directly to the super state

by Olivier Cuzacq (JIRA)

superstate-enter not fired when taking a transition directly to the super state ------------------------------------------------------------------------------- Key: JBPM-980 URL: http://jira.jboss.com/jira/browse/JBPM-980 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2 Environment: JBpm 3.2GA Reporter: Olivier Cuzacq Assigned To: Tom Baeyens Priority: Minor Let's consider a simple example using a super-state : <start-state name="start"> <transition to="buildPhase"/> </start-state> <super-state name="buildPhase"> <event type="superstate-enter"> <action class="com..." /> </event> ... <state name="waitForValidation"> <transition to="../deliveryPhase"/> </state> <event type="superstate-leave"> <action class="com..." /> </event> The superstate leave event is fired, but enter is not. Looking at the code this seems 'normal' : - Transition.take: if ( destination.getSuperState()!=null ) { ... fire the event ... - SuperState.execute : Node startNode = (Node) nodes.get(0); startNode.enter(executionContext); Going from a node to a super-state taking an explicit transition wont cause the event to be fired as dest.getSuperState == null. Then the super state will be executed and the first node will be entered without any kind of 'transient' transition being taken. If we look at the doc : (http://docs.jboss.com/jbpm/v3/userguide/processmodelling.html#superstatee... ) 9.6.2. Superstate events ... These events will be fired no matter over which transitions the node is entered or left respectively -> I cant find anything more precise about the expected behaviour AFAIAC I would expect the super-enter event being fired whatever the enter context (thru an innder node, or referencing the super-state itself). Best regards Olivier Cuzacq -- 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

18 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1660) Identity portlet configuration should allow to specify static and dynamic values

by Thomas Heute (JIRA)

Identity portlet configuration should allow to specify static and dynamic values -------------------------------------------------------------------------------- Key: JBPORTAL-1660 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1660 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Identity Reporter: Thomas Heute Assigned To: Emanuel Muckenhuber Fix For: 2.8 Final In the configuration file we should have something like: <values> <value key="foo">Foo</value> <value key="bar">Bar</value> </values> Foo and Bar should be localized, it should check in the resource bundle for something like: SOMEPREFIX_Foo and default to "Foo" if it doesn't exist. For dynamic values like themes, locales and timezones we should allow the following syntax: <values name="org.jboss.portal.THEMES"/> <values name="org.jboss.portal.LOCALES"/> <values name="org.jboss.portal.TIMEZONES"/> (All the name still have to be defined, those are just examples) -- 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

18 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1637) XML configuration of user properties

by Thomas Heute (JIRA)

XML configuration of user properties ------------------------------------ Key: JBPORTAL-1637 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1637 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Portal Identity Reporter: Thomas Heute Assigned To: Emanuel Muckenhuber Fix For: 2.8 Final parsed with jbossxb -- 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

18 years, 10 months

3
11
0 / 0

[JBoss JIRA] Commented: (JBPORTAL-615) Adding interceptors dynamically

by Marcel Dullaart (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-615?page=comments#action_12375340 ] Marcel Dullaart commented on JBPORTAL-615: ------------------------------------------ Sorry for the mistake during re-opening, I noticed the note slightly after clicking the send button (I should read more carefully). My conclusion might have been a bit premature. I deployed my sar file, which works fine in 2.4.1, containing 3 MBean's of which 2 inject their selves during startService in the server interceptor chain. I had noticed the change in MBean name, so I changed my MBean dependency accordingly to But then I got the following stack for one of the 2 MBean's, the other is similar: 14:36:06,197 WARN [ServiceController] Problem creating service portal:service=Interceptor,type=Server,name=AnonymousLocale java.lang.NullPointerException: Failed to find method for operation: create invoke on resource: org.epo.portal.interceptor.server.localization.LocaleInterceptor@14ad86c at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:149) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995) at $Proxy0.create(Unknown Source) at org.jboss.system.ServiceController.create(ServiceController.java:330) at org.jboss.system.ServiceController.create(ServiceController.java:273) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.create(Unknown Source) at org.jboss.deployment.SARDeployer.create(SARDeployer.java:258) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor126.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy8.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) > Adding interceptors dynamically > ------------------------------- > > Key: JBPORTAL-615 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-615 > Project: JBoss Portal > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: Portal Server > Affects Versions: 2.6.1 Final > Reporter: Marcel Dullaart > Fix For: 2.6.2 Final > > Attachments: JBossInterceptorStack.java > > > Please add the ability to dynamically add an interceptor at runtime, without touching the jboss-portal package. > I found the way to add an interceptor via changing the jboss-service.xml, but I like to prevent changing that file if anyway possible. -- 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

18 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-288) Fork/Join and child token deactivation

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-288?page=all ] Tom Baeyens closed JBPM-288. ---------------------------- Resolution: Done sorry it took so long > Fork/Join and child token deactivation > -------------------------------------- > > Key: JBPM-288 > URL: http://jira.jboss.com/jira/browse/JBPM-288 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0 > Environment: Any > Reporter: Lukasz Czekierda > Assigned To: Tom Baeyens > Priority: Critical > Fix For: jBPM jPDL 3.2.2 > > Attachments: processdefinition.xml, SimpleProcessTest.java > > > Join implementation has incorrectly/no implemented activation of finished child tokens. They remain active till the end of the whole process. Example from junit test (Wfp03SynchronizationTest.testSynchronizationFirstTokenFirst) works perfectly as long as is unmodified. After adding a few bottom lines and changing a transition in join I get my error. Token.end is called on children and the root token in the LAST state, when finishing the entire process. When in stateX or stateY, the process still reports two active child tokens. > --- > "<process-definition>" + > " <start-state name='start'>" + > " <transition to='fork' />" + > " </start-state>" + > " <fork name='fork'>" + > " <transition name='first' to='one' />" + > " <transition name='second' to='two' />" + > " </fork>" + > " <state name='one'>" + > " <transition to='join' />" + > " </state>" + > " <state name='two'>" + > " <transition to='join' />" + > " </state>" + > " <join name='join'>" + > " <transition to='stateX' />" + > " </join>" + > " <state name='stateX'>" + > " <transition to='stateY' />" + > " </state>" + > " <state name='stateY'>" + > " <transition to='end' />" + > " </state>" + > " <end-state name='end' />" + > "</process-definition>" -- 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

18 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPORTAL-615) Adding interceptors dynamically

by Thomas Heute (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-615?page=comments#action_12375329 ] Thomas Heute commented on JBPORTAL-615: --------------------------------------- What's the problem exactly ? The methods moved to JBossInterceptorStackFactory.java, is that the issue ? > Adding interceptors dynamically > ------------------------------- > > Key: JBPORTAL-615 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-615 > Project: JBoss Portal > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: Portal Server > Affects Versions: 2.6.1 Final > Reporter: Marcel Dullaart > Fix For: 2.6.2 Final > > Attachments: JBossInterceptorStack.java > > > Please add the ability to dynamically add an interceptor at runtime, without touching the jboss-portal package. > I found the way to add an interceptor via changing the jboss-service.xml, but I like to prevent changing that file if anyway possible. -- 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

18 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1535) Make GG xml retrieval timeout parameterizable

by Julien Viet (JIRA)

Make GG xml retrieval timeout parameterizable --------------------------------------------- Key: JBPORTAL-1535 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1535 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Julien Viet Assigned To: Boleslaw Dawidowicz Fix For: 2.6.2 Final, 2.8 Final -- 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

18 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1038) getNodeTypes() and getNodeNames() are switched in org.jbpm.graph.node.NodeTypes

by Marcel Lanz (JIRA)

getNodeTypes() and getNodeNames() are switched in org.jbpm.graph.node.NodeTypes ------------------------------------------------------------------------------- Key: JBPM-1038 URL: http://jira.jboss.com/jira/browse/JBPM-1038 Project: JBoss jBPM Issue Type: Bug Affects Versions: jBPM jPDL 3.2 Reporter: Marcel Lanz Assigned To: Tom Baeyens Priority: Minor getNodeTypes() is returning nodeNames and getNodeNames() returns the nodeTypes -- 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

18 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1050) Missing security-role element in jbpm-console web.xml

by James Baxter (JIRA)

Missing security-role element in jbpm-console web.xml ----------------------------------------------------- Key: JBPM-1050 URL: http://jira.jboss.com/jira/browse/JBPM-1050 Project: JBoss jBPM Issue Type: Bug Components: Web Interface Affects Versions: jBPM jPDL 3.2.1 Reporter: James Baxter Assigned To: Tom Baeyens Priority: Optional The jbpm-console uses a security role named 'user' in a security-constraint but does not declare the role in a security-role element. This produces the following console output: [code] INFO [ContextConfig] WARNING: Security role name user used in an <auth-constraint> without being defined in a <security-role> [/code] This issue can be fixed by adding the following to the web.xml: [code] <security-role> <role-name>user</role-name> </security-role> [/code] -- 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

18 years, 10 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

jboss-jira September 2007