January 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-634) Conversation is not created when @Begin annotated method is invoked

by Dan Liu (JIRA)

Conversation is not created when @Begin annotated method is invoked ------------------------------------------------------------------- Key: JBSEAM-634 URL: http://jira.jboss.com/jira/browse/JBSEAM-634 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.1.0.GA Reporter: Dan Liu Priority: Blocker I have a bookmarkable page that is opened through s:link with its action method annotated with @Begin(join=true) in a conversation scoped bean. The s:linke generated url has a parameter "cid=2;clr=true". When I restart my browser and paste the url, I get an error saying that conversation can't be found. I think the correct behavior should to create a new conversation when @Being annotated method is invoked and cid can't be found. -- 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
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-636) Session-scoped SFSB that uses @Unwrap does not get destroyed correctly on session timeout

by jazir malik (JIRA)

Session-scoped SFSB that uses @Unwrap does not get destroyed correctly on session timeout ----------------------------------------------------------------------------------------- Key: JBSEAM-636 URL: http://jira.jboss.com/jira/browse/JBSEAM-636 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.1.0.GA Reporter: jazir malik If a SFSB Seam component in the session scope uses @Unwrap to expose a non-Seam component, then an error occurs on session timeout: java.lang.IllegalArgumentException: method not found: destroy for component: user (check that it is declared on the session bean business interface) at org.jboss.seam.Component.callComponentMethod(Component.java:1809) at org.jboss.seam.Component.callDestroyMethod(Component.java:1747) at org.jboss.seam.contexts.Contexts.destroy(Contexts.java:189) at org.jboss.seam.contexts.Lifecycle.endSession(Lifecycle.java:230) at org.jboss.seam.servlet.SeamListener.sessionDestroyed(SeamListener.java:45) at org.apache.catalina.session.StandardSession.expire(StandardSession.java:687) at org.apache.catalina.session.StandardSession.isValid(StandardSession.java:579) at org.apache.catalina.session.ManagerBase.processExpires(ManagerBase.java:678) at org.apache.catalina.session.ManagerBase.backgroundProcess(ManagerBase.java:663) at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1284) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBas e.java:1569) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBas e.java:1578) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBas e.java:1578) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1558) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.NoSuchMethodException: entity.User.destroy() at java.lang.Class.getMethod(Class.java:1581) at org.jboss.seam.Component.callComponentMethod(Component.java:1788) ... 14 more Seam is looking for a destroy() method on the object that is unwrapped, NOT on the managing SFSB. -- 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
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-625) s:link ignore rendererd attribute

by Peter Muir (JIRA)

s:link ignore rendererd attribute --------------------------------- Key: JBSEAM-625 URL: http://jira.jboss.com/jira/browse/JBSEAM-625 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.1.0.GA Reporter: Peter 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

17 years, 4 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-640) org.jboss.seam.timeToneSelected event is a misspelling in TimeZoneSelector

by Bart Schuller (JIRA)

org.jboss.seam.timeToneSelected event is a misspelling in TimeZoneSelector -------------------------------------------------------------------------- Key: JBSEAM-640 URL: http://jira.jboss.com/jira/browse/JBSEAM-640 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.1.1.GA Reporter: Bart Schuller The patch in JBSEAM-536 included the line Events.instance().raiseEvent( "org.jboss.seam.timeToneSelected", getTimeZoneId() ); in org.jboss.seam.core.TimeZoneSelector which should probably be Events.instance().raiseEvent( "org.jboss.seam.timeZoneSelected", getTimeZoneId() ); (the same misspelling has been added in the method comment) -- 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
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-638) Table drops are not reflected in seam-gen

by Zeljko Trogrlic (JIRA)

Table drops are not reflected in seam-gen ----------------------------------------- Key: JBSEAM-638 URL: http://jira.jboss.com/jira/browse/JBSEAM-638 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 1.1.0.GA Environment: Windows XP Professional SP 2 Reporter: Zeljko Trogrlic After table is deleted, change is not reflected in seam-gen tasks: "seam generate-entities" does not remove generated Java files. If generated files are removed manually, "seam restart" does not remove files from exploded-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, 5 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-121) Support per-token variables in jBPM

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-121?page=comments#action_12349540 ] Ronald van Kuijk commented on JBSEAM-121: ----------------------------------------- I have not used this much in real life jbpm usage. I did use variables per task, which are in fact a copy of the values they had on the process level when the task was created. This sometimes leads to unexpected (unwanted?) behaviour, since e.g. with parallel tasks, the process level variables might have been updated without a (or any) user knowing this. A mechanism like a warning that the values have changed since the task was created might be an option. This is imo however a jbpm issue > Support per-token variables in jBPM > ----------------------------------- > > Key: JBSEAM-121 > URL: http://jira.jboss.com/jira/browse/JBSEAM-121 > Project: JBoss Seam > Issue Type: Feature Request > Components: BPM > Reporter: Gavin King > Assigned To: Gavin King > > jBPM variables can be scoped to the entire process instance, or to a single path of execution (Token). Currently Seam does not support the second kind of variable. This is not sufficient. Do we need a new PROCESS_PATH context?? Even this may not be enough in theory, since jBPM actually supports a kind of Token hierarchy. Is there some other solution? -- 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, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2007