March 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1811) DefaultActionListener is not call when using s:link

by Andy Bosch (JIRA)

DefaultActionListener is not call when using s:link --------------------------------------------------- Key: JBSEAM-1811 URL: http://jira.jboss.com/jira/browse/JBSEAM-1811 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.2.1.GA Environment: Jboss 4.0.5 GA and JBoss 4.2.0 Reporter: Andy Bosch In JSF in faces-config.xml you can create your own actionlistener with <action-listener> com.company.MyActionListener </action-listener> This actionlistener will be executed each time, a commandLink or commandButton is pressed. When using s:link or s:button the actionlistener is not called. -- 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

4
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1542) Identify process not only by root token, to allow for concurrency

by Gavin King (JIRA)

Identify process not only by root token, to allow for concurrency ----------------------------------------------------------------- Key: JBSEAM-1542 URL: http://jira.jboss.com/jira/browse/JBSEAM-1542 Project: JBoss Seam Issue Type: Feature Request Components: BPM Reporter: Gavin King Assigned To: Gavin King Fix For: 1.3.0.GA Currently we identify the process by the process id, and ignore the fact that jBPM allows fork-and-join using multiple Tokens. This is inflexible, especially for service orchestration. -- 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

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2489) Define deployment handler API

by Pete Muir (JIRA)

Define deployment handler API ----------------------------- Key: JBSEAM-2489 URL: http://jira.jboss.com/jira/browse/JBSEAM-2489 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.1.CR1 Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.0.1.GA API for handling scanned items from classpath -- 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
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2111) coerceToType / javaassist error when converting types for multi selection

by Damian Harvey (JIRA)

coerceToType / javaassist error when converting types for multi selection ------------------------------------------------------------------------- Key: JBSEAM-2111 URL: http://jira.jboss.com/jira/browse/JBSEAM-2111 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.CR2 Environment: Mac OSX. Jboss 4.2.1, Java 1.5 Reporter: Damian Harvey When trying to display values in an h:selectManyCheckbox I get an error: java.lang.IllegalArgumentException: Cannot convert com.locuslive.odyssey.entity.Groups@3960f3 of typ e class com.locuslive.odyssey.entity.Groups to class com.locuslive.odyssey.entity.Groups_$$_javassis t_219 I have created a very basic project with PERSON, GROUP and PERSONGROUP entities. I've attached it after emptying the lib directory. Essentially on the PersonEdit page I want to be able to select which Groups the Person may belong to. This is done with the selectManyCheckbox. The checkbox is populated with a list of GROUPs from a GroupList. It is bound to a variable in the PersonHome called 'groups'. This is a list of Groups that is extracted from the PersonGroup table for that user. The stacktrace is in the forum post. I have also generated the attached project under Seam 1.2.1.GA and the problem is not there. -- 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

4
17
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2609) Locking issue for ConversationEntry when using Conversation.instance().leave()

by Jacob Orshalick (JIRA)

Locking issue for ConversationEntry when using Conversation.instance().leave() ------------------------------------------------------------------------------ Key: JBSEAM-2609 URL: http://jira.jboss.com/jira/browse/JBSEAM-2609 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.1.GA Reporter: Jacob Orshalick Priority: Minor When using Conversation.instance().leave(), it seems that the ConversationEntry lock is not released. *Sometimes* it can be obtained when attempting to resume the conversation but other times it cannot. This results in the user being redirected to the no-conversation-view-id. This can be observed by placing Conversation.instance.leave() in an action that redirects to another page. Then simply use the back-button and resume the conversation by clicking a link on the page. You may have to try this several times to get the result. I will see if I can create a reliable test case and attach it. Manager.switchConversation() performs an unlock of the ConversationEntry prior to switching, which would also make sense in the case of leave (since it is really a switch to a temp conversation). The workaround is simply executing the following: Code: Conversation conversation = Conversation.instance(); ConversationEntry entry = ConversationEntries.instance().getConversationEntry(conversation.getId()); conversation.leave(); entry.unlock(); -- 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

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2724) internationalize Home default messages

by Martin Trummer (JIRA)

internationalize Home default messages -------------------------------------- Key: JBSEAM-2724 URL: http://jira.jboss.com/jira/browse/JBSEAM-2724 Project: JBoss Seam Issue Type: Feature Request Components: Framework Affects Versions: 2.0.1.GA Reporter: Martin Trummer Default messages in org.jboss.seam.framework.Home class should be configurable via resource bundle keys. -- 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

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1585) Update portal example to JBoss AS 4.2.0.GA

by Pete Muir (JIRA)

Update portal example to JBoss AS 4.2.0.GA ------------------------------------------ Key: JBSEAM-1585 URL: http://jira.jboss.com/jira/browse/JBSEAM-1585 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.0.BETA1 Reporter: Pete Muir -- 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

3
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2569) Delete/Edit buttons on directory browser

by Gavin King (JIRA)

Delete/Edit buttons on directory browser ---------------------------------------- Key: JBSEAM-2569 URL: http://jira.jboss.com/jira/browse/JBSEAM-2569 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Gavin King Assigned To: Christian Bauer We need to be able to delete documents, or go direct to the edit screen from the directory view. -- 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

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2618) Testing notifications.

by Tom Benninger (JIRA)

Testing notifications. ---------------------- Key: JBSEAM-2618 URL: http://jira.jboss.com/jira/browse/JBSEAM-2618 Project: JBoss Seam Issue Type: Task Reporter: Tom Benninger Assigned To: Tom Benninger Priority: Trivial testing notifications. -- 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
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2570) Switching back to the edit user screen with the workspace switcher

by Gavin King (JIRA)

Switching back to the edit user screen with the workspace switcher ------------------------------------------------------------------ Key: JBSEAM-2570 URL: http://jira.jboss.com/jira/browse/JBSEAM-2570 Project: JBoss Seam Issue Type: Bug Environment: Firefox Reporter: Gavin King Switching back to the edit user screen with the workspace switcher results in a page that does not render the tabs correctly (some .js error). -- 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

3
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues March 2008