December 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2377) Conversation Switcher broken when using Explicit Conversations

by Samuel Mendenhall (JIRA)

Conversation Switcher broken when using Explicit Conversations -------------------------------------------------------------- Key: JBSEAM-2377 URL: http://jira.jboss.com/jira/browse/JBSEAM-2377 Project: JBoss Seam Issue Type: Bug Components: Core Reporter: Samuel Mendenhall Priority: Minor My test project consists of CatHome and KittenHome (hey, I like cats) with the respective entities, ect... On the create method of CatHome and KittenHome I have: @Begin(id="TheKittenConversation") @Begin(id="TheCatConversation") I have the standard conversation switcher syntax from the Docs. Now when I create a cat, then a kitten, then I go to switch back to the cat with the switcher, the page just refreshes and does not go anywhere. I did some debugging and the "actualOutcome" from the ./src/main/org/jboss/seam/faces/Switcher.java is the explicit id which in this case is "TheCatConversation". Ok, so the method returns this string, nothing happens, nothing is redirected, why would anything happen. However, if I just do @Begin instead of the explicit ids and rerun the project then this piece of code is hit and the redirect happens: else{ ConversationEntry ce = ConversationEntries.instance().getConversationEntry(conversationIdOrOutcome); if (ce!=null) { resultingConversationIdOrOutcome = ce.getId(); System.out.println("ce.getId(): " + ce.getId() + " redirection..."); ce.redirect(); } } But if I use explict, that is never encountered because isOutcome is true and the else is not evaluated: if (isOutcome) { resultingConversationIdOrOutcome = conversationIdOrOutcome; actualOutcome = conversationIdOrOutcome; } So I removed the if else completely and Explicit conversations and the conversation switcher worked perfect. The resulting select method looks like: public String select() { String actualOutcome; ConversationEntry ce = ConversationEntries.instance().getConversationEntry(conversationIdOrOutcome); if (ce!=null) { resultingConversationIdOrOutcome = ce.getId(); ce.redirect(); } actualOutcome = null; return actualOutcome; } which means the outcome returned will always be null, versus in the case of explicit conversations, be the explict conversation 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

16 years, 7 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1956) Convert seam-discs to use poms for dependency management

by Pete Muir (JIRA)

Convert seam-discs to use poms for dependency management -------------------------------------------------------- Key: JBSEAM-1956 URL: http://jira.jboss.com/jira/browse/JBSEAM-1956 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.0.CR1 Reporter: Pete Muir Assigned To: 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

16 years, 7 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1749) Move Seam UI Tests into main test strucutre

by Pete Muir (JIRA)

Move Seam UI Tests into main test strucutre ------------------------------------------- Key: JBSEAM-1749 URL: http://jira.jboss.com/jira/browse/JBSEAM-1749 Project: JBoss Seam Issue Type: Task Components: JSF Affects Versions: 2.0.0.BETA1 Reporter: Pete Muir Assigned To: Pete Muir Priority: Minor -- 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

16 years, 7 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1123) Constrain width or height for s:graphicImage

by Shane Bryzak (JIRA)

Constrain width or height for s:graphicImage -------------------------------------------- Key: JBSEAM-1123 URL: http://jira.jboss.com/jira/browse/JBSEAM-1123 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 1.2.1.GA Reporter: Shane Bryzak Assigned To: Pete Muir Priority: Minor Pete - It would be nice if s:transformImageSize could constrain an image by either its width or height. I have a scenario where neither the width or height should exceed 80px, yet the ratio should be maintained. Something along the lines of this syntax would probably do the job but you can probably come up with something nicer: <s:graphicImage value="#{image}"> <s:transformImageSize max-width="80" max-height="80" maintainRatio="true"/> </s:graphicImage> -- 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

16 years, 7 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2012) User agent aware skinning

by Gavin King (JIRA)

User agent aware skinning ------------------------- Key: JBSEAM-2012 URL: http://jira.jboss.com/jira/browse/JBSEAM-2012 Project: JBoss Seam Issue Type: Feature Request Components: JSF, Wiki Affects Versions: 2.0.1.GA Reporter: Gavin King Assigned To: Pete Muir Especially for the Wiki, we should develop a generalized solution for mapping user agents to skinned facelets. I'm thinking we would use the facelets ResourceResolver for this. <theme:skinSelector> <theme:skins> <key>Windows CE</key><value>winCE</value> <key>SonyEricsson</key><value>sonyEricsson</value> <theme:skins> </theme:skinSelector> Then a view id like home.xhtml would actually resolve to home.xhtml, home_winCE.xhtml or home_sonyEricsson.xhtml, depending upon the user agent. -- 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

16 years, 7 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1455) PrioritizableConverter should use @Around/@Within

by Pete Muir (JIRA)

PrioritizableConverter should use @Around/@Within ------------------------------------------------- Key: JBSEAM-1455 URL: http://jira.jboss.com/jira/browse/JBSEAM-1455 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 1.3.0.ALPHA Reporter: Pete Muir Assigned To: Pete Muir Priority: Minor -- 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

16 years, 7 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1097) Embed forms in emails

by Pete Muir (JIRA)

Embed forms in emails --------------------- Key: JBSEAM-1097 URL: http://jira.jboss.com/jira/browse/JBSEAM-1097 Project: JBoss Seam Issue Type: Feature Request Components: Mail Affects Versions: 1.2.0.GA Reporter: Pete Muir Assigned To: Pete Muir This would allow you to embed a JSF form in an email template, and have it operate as a normal form. -- 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

16 years, 7 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1955) Provide optional POM support in seam-gen

by Pete Muir (JIRA)

Provide optional POM support in seam-gen ---------------------------------------- Key: JBSEAM-1955 URL: http://jira.jboss.com/jira/browse/JBSEAM-1955 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.0.CR1 Reporter: Pete Muir Assigned To: 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

16 years, 7 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1886) document notion of "foreground" conversation

by Matt Drees (JIRA)

document notion of "foreground" conversation -------------------------------------------- Key: JBSEAM-1886 URL: http://jira.jboss.com/jira/browse/JBSEAM-1886 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.0.BETA1 Reporter: Matt Drees Priority: Minor >From the referenced forum post, I just learned that conversation timeouts don't behave like session timeouts; timeouts only occur in requests, and there is a notion of a "foreground" conversation that doesn't timeout. I like this design, but I don't think the documentation makes this clear. I think people's intuition is that conversation timeouts will happen just like session timeouts. Could you please explain this more clearly in the docs? -- 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

16 years, 7 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-730) User/Role/Permission model

by Gavin King (JIRA)

User/Role/Permission model -------------------------- Key: JBSEAM-730 URL: http://jira.jboss.com/jira/browse/JBSEAM-730 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Gavin King Assigned To: Shane Bryzak Fix For: 1.2.0.BETA1 There should be an optional component which plugs into Seam/Security to provide the following model: Role (name, description, manager??) User extends Role (password, firstName, lastName, additionalNames, email) RoleRole (role, role) Permission(objectName, operationName) RolePermission(role,permission) RoleInstancePermission(objectName, operationName, objectId) This model would be extensible by the user, simply using inheritance. There would be a built-in management console for creating users and roles and assigning roles and permissions. -- 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

16 years, 7 months

5
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2007