November 2006 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-197) Order task list by priority

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-197?page=all ] Gavin King updated JBSEAM-197: ------------------------------ Fix Version/s: 1.2.0.BETA1 > Order task list by priority > --------------------------- > > Key: JBSEAM-197 > URL: http://jira.jboss.com/jira/browse/JBSEAM-197 > Project: JBoss Seam > Issue Type: Feature Request > Components: BPM > Reporter: Gavin King > Priority: Minor > Fix For: 1.2.0.BETA1 > > > Should make it possible to sort the tasks in the task list by priority. -- 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, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-382) TaskConversationContext or TASK scope

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-382?page=all ] Gavin King updated JBSEAM-382: ------------------------------ Fix Version/s: 1.2.0.BETA1 > TaskConversationContext or TASK scope > ------------------------------------- > > Key: JBSEAM-382 > URL: http://jira.jboss.com/jira/browse/JBSEAM-382 > Project: JBoss Seam > Issue Type: Feature Request > Components: BPM > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.2.0.BETA1 > > > We could support an alternative implementation of the conversation Context where variables get saved not to the HttpSession but to the jBPM database. > This would mean that the work in progress could be recovered by the user. > Alternatively, we could have a special TASK context. -- 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, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-157) Pageflow composition

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-157?page=all ] Gavin King updated JBSEAM-157: ------------------------------ Fix Version/s: 1.2.0.BETA1 > Pageflow composition > -------------------- > > Key: JBSEAM-157 > URL: http://jira.jboss.com/jira/browse/JBSEAM-157 > Project: JBoss Seam > Issue Type: Feature Request > Components: BPM > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.2.0.BETA1 > > > The jBPM mechanism for process composition does not work for pageflow. Need to figure out a different mechanism. AFAICT, this needs to be solved more in jBPM than in Seam. -- 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, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-408) actionListener="#{foo.bar}" where bar() has no ActionEvent parameter

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-408?page=all ] Gavin King updated JBSEAM-408: ------------------------------ Fix Version/s: 1.1.0.GA (was: 1.1.0.CR1) slip > actionListener="#{foo.bar}" where bar() has no ActionEvent parameter > -------------------------------------------------------------------- > > Key: JBSEAM-408 > URL: http://jira.jboss.com/jira/browse/JBSEAM-408 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF > Affects Versions: 1.1.0.BETA1 > Reporter: Gavin King > Assigned To: Gavin King > Priority: Minor > Fix For: 1.1.0.GA > > > I hate the useless ActionEvent polluting my business code. I already fixed this in facelets, need a solution for JSP also. -- 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, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-116) Pluggable conversationId handler

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-116?page=all ] Gavin King updated JBSEAM-116: ------------------------------ Fix Version/s: 1.1.0.GA (was: 1.1.0.CR1) slippin (yet again), despite votes > Pluggable conversationId handler > -------------------------------- > > Key: JBSEAM-116 > URL: http://jira.jboss.com/jira/browse/JBSEAM-116 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Gavin King > Priority: Critical > Fix For: 1.1.0.GA > > > Currently, there is no way to plug in a user-defined strategy for decoding and encoding the conversationId in the request/response. > We need this to really properly support AJAX/Soap invocations. -- 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, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-395) Alternate "dispatcher" strategies

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-395?page=comments#action_12347128 ] Gavin King commented on JBSEAM-395: ----------------------------------- I am inclined to slip this one - except it has two votes ..... hmmmm, what to do .... > Alternate "dispatcher" strategies > --------------------------------- > > Key: JBSEAM-395 > URL: http://jira.jboss.com/jira/browse/JBSEAM-395 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Affects Versions: 1.1.0.BETA1 > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.1.0.CR1 > > > Currently, dispatch of asynchronous calls and events is done via the timer service. There are really good reasons to support other dispatching strategies such as quartz, jBPM, etc. This can be done simply by supporting @Asynchronous(dispatcher="#{name}"). -- 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, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-401) Contexts.destroy(BusinessProcessContext) hits the database after the seam managed transaction ends

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-401?page=all ] Gavin King updated JBSEAM-401: ------------------------------ Fix Version/s: 1.1.0.GA (was: 1.1.0.CR1) Priority: Minor (was: Critical) slipping > Contexts.destroy(BusinessProcessContext) hits the database after the seam managed transaction ends > -------------------------------------------------------------------------------------------------- > > Key: JBSEAM-401 > URL: http://jira.jboss.com/jira/browse/JBSEAM-401 > Project: JBoss Seam > Issue Type: Bug > Components: Core > Affects Versions: 1.1.0.BETA1 > Reporter: Gavin King > Assigned To: Gavin King > Priority: Minor > Fix For: 1.1.0.GA > > -- 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, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-409) WebSessionContext.flush causing out of memory

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-409?page=all ] Gavin King closed JBSEAM-409. ----------------------------- Resolution: Done Fixed, please test it for me, thanks! > WebSessionContext.flush causing out of memory > --------------------------------------------- > > Key: JBSEAM-409 > URL: http://jira.jboss.com/jira/browse/JBSEAM-409 > Project: JBoss Seam > Issue Type: Bug > Components: Portal > Affects Versions: 1.1.0.BETA1 > Reporter: jarkko Lietolahti > Assigned To: Gavin King > Priority: Critical > Fix For: 1.1.0.CR1 > > -- 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, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-421) Update to Seam i18n to support resource bundle types

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-421?page=all ] Gavin King closed JBSEAM-421. ----------------------------- Resolution: Done I made a one-word change: private -> protected on loadBundle(). You should be able to do anything you like by subclassing now. > Update to Seam i18n to support resource bundle types > ---------------------------------------------------- > > Key: JBSEAM-421 > URL: http://jira.jboss.com/jira/browse/JBSEAM-421 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Affects Versions: 1.1.0.BETA1 > Reporter: Todd Smart > Fix For: 1.1.0.CR1 > > Attachments: extras.zip, ResourceBundle.java, ResourceBundle.java > > > The current Seam i18n ResourceBundle class only supports loading java.util.ResourceBundle resource bundles. > Feature Request: > ------------------------ > 1) Add an attribute to ResourceBundle called: resourceType (to facilitate use of other resource bundle types). This attribute would be configured in seam.properties. > 2) Update the loadBundle() method to allow for loading through other resource bundle types. > See attached update to org.jboss.seam.ResourceBundle (sample supporting classes, property file, and sql script also provided for reference). > Regards, > Todd Smart > todd.smart(a)smartbinary.com -- 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, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-421) Update to Seam i18n to support resource bundle types

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-421?page=comments#action_12347124 ] Gavin King commented on JBSEAM-421: ----------------------------------- Wouldn't it be easier if I just factor out a createBundle() method and let you override on a subclass? > Update to Seam i18n to support resource bundle types > ---------------------------------------------------- > > Key: JBSEAM-421 > URL: http://jira.jboss.com/jira/browse/JBSEAM-421 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Affects Versions: 1.1.0.BETA1 > Reporter: Todd Smart > Fix For: 1.1.0.CR1 > > Attachments: extras.zip, ResourceBundle.java, ResourceBundle.java > > > The current Seam i18n ResourceBundle class only supports loading java.util.ResourceBundle resource bundles. > Feature Request: > ------------------------ > 1) Add an attribute to ResourceBundle called: resourceType (to facilitate use of other resource bundle types). This attribute would be configured in seam.properties. > 2) Update the loadBundle() method to allow for loading through other resource bundle types. > See attached update to org.jboss.seam.ResourceBundle (sample supporting classes, property file, and sql script also provided for reference). > Regards, > Todd Smart > todd.smart(a)smartbinary.com -- 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, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2006