September 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1669) Make the JBossCachePersistenceManager compatible with JBoss Cache 1.4.1

by Sohil Shah (JIRA)

Make the JBossCachePersistenceManager compatible with JBoss Cache 1.4.1 ----------------------------------------------------------------------- Key: JBPORTAL-1669 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1669 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal CMS Reporter: Sohil Shah Assigned To: Sohil Shah Priority: Minor Fix For: 2.6.3 Final For details look at http://jira.jboss.com/jira/browse/JBPORTAL-1626 -- 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
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1046) merge clusteredjms changes into JBPAPP_4_2, Branch_4_2

by William DeCoste (JIRA)

merge clusteredjms changes into JBPAPP_4_2, Branch_4_2 ------------------------------------------------------ Key: EJBTHREE-1046 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1046 Project: EJB 3.0 Issue Type: Task Affects Versions: Branch_4_2 Reporter: William DeCoste Assigned To: William DeCoste -- 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: (JBAOP-382) Remove Complex Advice Signatures from Classic Mode

by Flavia Rainone (JIRA)

Remove Complex Advice Signatures from Classic Mode -------------------------------------------------- Key: JBAOP-382 URL: http://jira.jboss.com/jira/browse/JBAOP-382 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Flavia Rainone Assigned To: Flavia Rainone Priority: Minor Fix For: 2.0.0.alpha5 We need to update PerVMAdvice class, to remove the possibility of advices that receive joinpoint arguments (currently, the matching of parameters is not completely functional). We will leave the possibility of receiving joinpoint arguments as parameters to the annotated-parameters signature. This task also includes moving arg tests to beforeafterArgs package. PS: documentation is already stating that only annotated-parameters advice signatures can feature joinpoint arguments as parameters. No need to update documentation here. -- 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
9
0 / 0

[JBoss JIRA] Closed: (JBBUILD-283) media pom

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-283?page=all ] Paul Gier closed JBBUILD-283. ----------------------------- Resolution: Out of Date Issue replaced by JBBUILD-411 > media pom > --------- > > Key: JBBUILD-283 > URL: http://jira.jboss.com/jira/browse/JBBUILD-283 > Project: JBoss Build System > Issue Type: Sub-task > Components: Maven > Reporter: Ruel Loehr > Assigned To: Paul Gier > Fix For: Maven Build - App Server > > -- 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: (JBPM-255) I18N for the webapp

by Fady Matar (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-255?page=comments#action_12375738 ] Fady Matar commented on JBPM-255: --------------------------------- Why don't we create samples of internationalization, let's say adding french and some eastern language? An earlier issue tackled the handling of eastern encoding, we might combine the two issues together and get it sorted out > I18N for the webapp > ------------------- > > Key: JBPM-255 > URL: http://jira.jboss.com/jira/browse/JBPM-255 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Web Interface > Reporter: Ronald van Kuijk > Assigned To: Ronald van Kuijk > Priority: Optional > Fix For: jBPM 3.3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Not everybody speaks dutch -- 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: (JBPM-616) prevent duplicate form submissions

by Fady Matar (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-616?page=comments#action_12375737 ] Fady Matar commented on JBPM-616: --------------------------------- I'll give it a test and apply it to the form. I recall doing something similar way back. > prevent duplicate form submissions > ---------------------------------- > > Key: JBPM-616 > URL: http://jira.jboss.com/jira/browse/JBPM-616 > Project: JBoss jBPM > Issue Type: Task > Components: Web Interface > Reporter: Tom Baeyens > Assigned To: David Lloyd > Fix For: jBPM 3.3 > > > for hints and tips, you can have a look at http://raibledesigns.com/page/rd?anchor=how_does_your_mvc_framework -- 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: (JBPM-616) prevent duplicate form submissions

by Fady Matar (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-616?page=comments#action_12375736 ] Fady Matar commented on JBPM-616: --------------------------------- I don't get this issue, can anybody elaborate? > prevent duplicate form submissions > ---------------------------------- > > Key: JBPM-616 > URL: http://jira.jboss.com/jira/browse/JBPM-616 > Project: JBoss jBPM > Issue Type: Task > Components: Web Interface > Reporter: Tom Baeyens > Assigned To: David Lloyd > Fix For: jBPM 3.3 > > > for hints and tips, you can have a look at http://raibledesigns.com/page/rd?anchor=how_does_your_mvc_framework -- 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: (JBBUILD-276) Jbossas remoting components pom

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-276?page=all ] Paul Gier closed JBBUILD-276. ----------------------------- Resolution: Out of Date Issue replaced by JBBUILD-411 > Jbossas remoting components pom > -------------------------------- > > Key: JBBUILD-276 > URL: http://jira.jboss.com/jira/browse/JBBUILD-276 > Project: JBoss Build System > Issue Type: Sub-task > Components: Maven > Reporter: Ruel Loehr > Assigned To: Paul Gier > Fix For: Maven Build - App Server > > -- 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] Updated: (JBBUILD-251) Pulling down src or binaries based upon configuration

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-251?page=all ] Paul Gier updated JBBUILD-251: ------------------------------ Fix Version/s: JBossBuild - Maint 2007 (was: Maven Build - App Server) > Pulling down src or binaries based upon configuration > ----------------------------------------------------- > > Key: JBBUILD-251 > URL: http://jira.jboss.com/jira/browse/JBBUILD-251 > Project: JBoss Build System > Issue Type: Feature Request > Components: Maven > Reporter: Ruel Loehr > Fix For: JBossBuild - Maint 2007 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > From Adrian on the dev list: > The problem I don't see addressed (and the main reason why I started the jbossbuild prototype) is to have a top level which includes multiple projects. > e.g. I wanted people to be able to do something like: > <build> > <component name="JBossAS" download="binary" quality="LastGoodTests"> > <component name="EJB3" download="source"/> > </component> > <component name="Seam" download="source"/> </build> > This would checkout the last binaries for JBossAS that passed the testsuite (except EJB3 which is latest source) and also Seam. > You would then be able to build a Seam environment with just the > EJB3 and Seam sources. > i.e. the developer only has to worry about the problems with the stuff he is working on, rather than figuring out why something unrelated doesn't compile/work. > Instead, the jbossbuild project morphed into a mechanism to download thirdparty binaries with buildmagic still used for the main build. -- 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: (JBPM-633) Asynchronous Action Handler required for async continuations

by Prasad Nuthalapati (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-633?page=comments#action_12375716 ] Prasad Nuthalapati commented on JBPM-633: ----------------------------------------- I have created a process flow application which can be used by multiple users concurrently. As these users may decide to save the work in various states and it may take a long time like a week to reach the end point - I am trying to use asynchronous continuations. As there is only a single CommandExecutorThread on which all async ActionHandler execute methods are called for different processes what should we do to ensure all the threads are safe? Also, will this be an issue to have so many threads in wait state for so long? I appreciate any feedback Thanks Prasad > Asynchronous Action Handler required for async continuations > ------------------------------------------------------------ > > Key: JBPM-633 > URL: http://jira.jboss.com/jira/browse/JBPM-633 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM 3.1 > Reporter: Mark Shotton > Assigned To: Tom Baeyens > > As there is only a single CommandExecutorThread on which all async ActionHandler execute methods are called, it is important to write execute methods that run asynchronously when these may be long running; otherwise the CommandExecutorThread is held up from processing other actions. > This presents a thread safety problem. The problem lies in beginning a new transaction from within the ActionHandler execute method; e.g. > (1) Prior to executing an action, the JBPM framework opens a new JbpmContext and locks the token. > (2) The framework executes the action by calling ActionHandler.execute(ExecutionContext executionContext); the ExecutionContext provides access to the JbpmContext opened by the framework. > (3) I start a new thread from within the execute method to execute asynchronously. > (4) The execute method exits and the framework saves and closes the original JbpmContext and token > (5) The new thread opens a second JbpmContext and finds and progresses the token (this being possible even if the framework has not unlocked its token yet because the new thread gets a new copy of the token that is not locked; tokens are locked in memory; not at a database level). > (6) The new thread saves and closes the second JbpmContext. > The problem arises when the framework attempts to save a token that has already been progressed by the new thread; or the new thread tries to progress a token that has since been updated by the framework ? we have a race condition. > I think that there are a couple of obvious solutions: > (1) As a work-around, the execute method starts the new thread and then sets a context variable in the process instance ? this will not be saved to the database until the framework closes its JbpmContext. The asynchronous thread sleeps until the process instance has the context variable set before progressing the token. > (2) The JBPM framework examines the class of the ActionHandler before calling its execute method; if it is an instance of an AsyncActionHandler, the framework gets the process instance ID and task instance ID from the token and then saves and closes its JbpmContext. It then calls the execute method of the AsyncActionHandler, passing in the process instance ID and task instance ID (the latter may be null) instead of the ExecutionContext. > I think that the latter solution or something like it would be a very useful addition to the JBPM framework. -- 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