March 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2767) Redirect the user to the last page he left when the session expires

by Lijun Yan (JIRA)

Redirect the user to the last page he left when the session expires ------------------------------------------------------------------- Key: JBSEAM-2767 URL: http://jira.jboss.com/jira/browse/JBSEAM-2767 Project: JBoss Seam Issue Type: Feature Request Components: Security Affects Versions: 2.0.1.GA Reporter: Lijun Yan The business scenario here is: When a user attempts to access a page and the session has timed out, he is redirected to the login page with a message explaining that he need to log in again. After the user completes the log in, he should be redirected to the last page where he tried to interact. We didn't find any built-in Seam configuration could help with this requirement. So we implement it programmatically. We save the last view id to the Cookie when session times out, and then recover the last view id when the user re-logs in. We are wondering whether there is any Seam component we could take advantage of. With the coming org.jboss.seam.sessionExpired event (http://jira.jboss.com/jira/browse/JBSEAM-2257), can we do something like: <event type="org.jboss.seam.sessionExpired"> <action execute="#{redirect.captureCurrentView}"/> </event> <event type="org.jboss.seam.postAuthenticate"> <action execute="#{redirect.returnToCapturedView}"/> </event> I tried this setting now, with the sessionExpired event developed as Jacob's blog (http://solutionsfit.com/blog/2007/11/16/session-expired-messages-using-se...), the error is: 2008-03-18 16:33:51,313 ERROR *http-8080-2* SeamPhaseListener.beforePhase:120 [] uncaught exception javax.el.PropertyNotFoundException: Target Unreachable, identifier 'redirect' resolved to null We also have question about how the conversation plays in this redirection. For example, the session expires when the user is at some results page, when he re-logs in, how to keep all the result data on that page and other states? Basically how to save and replay a conversation? -- 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
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2737) Use seamframework.org style in Seam docs

by Pete Muir (JIRA)

Use seamframework.org style in Seam docs ---------------------------------------- Key: JBSEAM-2737 URL: http://jira.jboss.com/jira/browse/JBSEAM-2737 Project: JBoss Seam Issue Type: Task Components: Documentation Issues Reporter: Pete Muir Fix For: 2.0.2.GA Replace jboss.org styles with seamframework.org style. -- 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-2734) Build docs from ant refdoc target

by Pete Muir (JIRA)

Build docs from ant refdoc target --------------------------------- Key: JBSEAM-2734 URL: http://jira.jboss.com/jira/browse/JBSEAM-2734 Project: JBoss Seam Issue Type: Task Components: Documentation Issues Reporter: Pete Muir Priority: Critical Fix For: 2.0.2.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

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2739) Use full version number in both PDF and HTML docs

by Pete Muir (JIRA)

Use full version number in both PDF and HTML docs ------------------------------------------------- Key: JBSEAM-2739 URL: http://jira.jboss.com/jira/browse/JBSEAM-2739 Project: JBoss Seam Issue Type: Task Components: Documentation Issues Reporter: Pete Muir Priority: Critical Fix For: 2.0.2.GA The PDF docs currently just have 2.0 (they need e.g. 2.0.2.CR1). The HTML docs currently don't have any version number. -- 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
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2356) Give the ability to extend the list of EL functions supportem by Seam EL resolver

by Olivier Thierry (JIRA)

Give the ability to extend the list of EL functions supportem by Seam EL resolver ---------------------------------------------------------------------------------- Key: JBSEAM-2356 URL: http://jira.jboss.com/jira/browse/JBSEAM-2356 Project: JBoss Seam Issue Type: Feature Request Components: EL Affects Versions: 2.0.0.GA Reporter: Olivier Thierry There is no easy way to use a custom EL function for example in a resource bundle. There are two EL functions today (s:hasRole and s:hasPermissions) which are hard-coded in org.jboss.seam.el.SeamFunctionMapper class. It would be nice to have the possibility to extend the list of these EL functions with our custom ones, without having to modify Seam source code. -- 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
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2765) Injection doesn't work for Seam components declared in components.xml when used as web services

by Olivier Thierry (JIRA)

Injection doesn't work for Seam components declared in components.xml when used as web services ----------------------------------------------------------------------------------------------- Key: JBSEAM-2765 URL: http://jira.jboss.com/jira/browse/JBSEAM-2765 Project: JBoss Seam Issue Type: Bug Components: WS Affects Versions: 2.0.1.GA Environment: JBoss 4.2.0.GA Reporter: Olivier Thierry I created a Seam component and I want to expose it as a web service. Everything works well when the component is declared with @Name annotation. But injection doesn't work when the component is declared in components.xml file. The problem happens only when calling the Seam component as a web service. -- 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
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2748) s:link and s:button with a view parameter are preloading the view

by Peter Boevink (JIRA)

s:link and s:button with a view parameter are preloading the view ----------------------------------------------------------------- Key: JBSEAM-2748 URL: http://jira.jboss.com/jira/browse/JBSEAM-2748 Project: JBoss Seam Issue Type: Bug Components: JSF Controls Affects Versions: 2.1.0.A1 Environment: WinXP, jboss-4.2.2.GA, JDK1.5.*, jboss-seam-2.0.1.GA Reporter: Peter Boevink Create a JSF view (e.g. UserList.xhtml) which makes use of <s:link/> or <s:button/> including the 'view' parameter e.g.: <s:link view="UserEdit.xhtml"/> UserList.seam should be rendered making use of a long-running conversation, e.g.: UserList.page.xml: <begin-conversation/> The 'UserEdit.page.xml' references a bean by making use of: <action execute="#{userHome.wire}"/> Now visit the UserList.seam page which holds the s:link reference to UserEdit.xhtml..... Don't click this s:link but open the debug.seam page to see what conversations exist with their objects. You''ll see a long running conversation (created by UserList.page.xml). Surprisingly, this conversation contains a 'userHome' object that should not be created before loading UserEdit.seam! Expected behaviour is than a long running conversation without objects. Making use of the <s:link/> tag with a typo in the 'view' parameter: <s:link view="typo.xhtml"/> Creates a long-running conversation without objects. So it looks like the page referred by the view parameter is somehow rendered and the beans referred by that page are pre-loaded in the currently active conversation scope. This causes undesired behaviour when making use of nested conversation e.g.: <s:link view="UserEdit.xhtml" propagation="nest"/> or <s:link view="UserEdit.xhtml"> <s:conversationPropagation type="nested" /> </s:link> The beans referred by the UserEdit.seam page are now loaded in the parent conversation instead of the nested one. -- 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
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2762) PageContext is null after exception recovery in some cases - causes HTTP 500

by ja my last name (JIRA)

PageContext is null after exception recovery in some cases - causes HTTP 500 ---------------------------------------------------------------------------- Key: JBSEAM-2762 URL: http://jira.jboss.com/jira/browse/JBSEAM-2762 Project: JBoss Seam Issue Type: Bug Components: Exception Handling Affects Versions: 2.0.1.GA Environment: jboss4.2.2 Reporter: ja my last name NPE occurs in Pages.java line 686 (Contexts.getPageContext() returns null). My config: <page view-id="*"> <param name="tnetBackUrl" /> ... </page> <exception class="java.lang.Exception"> <redirect view-id="/error.xhtml"> <message>Error has occured, please contact administrator</message> </redirect> </exception> NPE occurs with such config during postback if uncatched exception was thrown during INVOKE_APPLICATION phase. As a result HTTP 500 is returned. problem seems to disapear if following is used instead: <page view-id="*"> <param name="tnetBackUrl" value="#{redirectManager.backUrl}"/> ... </page> where redirectManager is event scoped pojo. -- 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-2593) Cap and Join not working correctly in UIStroke

by Tim Blommerde (JIRA)

Cap and Join not working correctly in UIStroke ---------------------------------------------- Key: JBSEAM-2593 URL: http://jira.jboss.com/jira/browse/JBSEAM-2593 Project: JBoss Seam Issue Type: Bug Components: PDF Affects Versions: 2.0.1.GA, 2.0.1.CR2, 2.0.1.CR1, 2.0.0.GA Reporter: Tim Blommerde There is a small copy-and-paste error in the 'joinValue(String join)' method of the UIStroke class (org.jboss.seam.pdf.ui.UIStroke). Because of this error, setting the cap value of a Stroke to something else then 'round' causes a Runtime Exception and setting a join value does not work. Below I've added a fix for the joinMethod: public int joinValue(String join) { if (join == null || join.equalsIgnoreCase("miter")) { return BasicStroke.JOIN_MITER; } else if (join.equalsIgnoreCase("round")) { return BasicStroke.JOIN_ROUND; } else if (join.equalsIgnoreCase("bevel")) { return BasicStroke.JOIN_BEVEL; } throw new RuntimeException("invalid join value: " + join); } -- 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
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-273) Specify HTTP headers in pages.xml

by Norman Richards (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-273?page=all ] Norman Richards closed JBSEAM-273. ---------------------------------- Resolution: Done Done > Specify HTTP headers in pages.xml > --------------------------------- > > Key: JBSEAM-273 > URL: http://jira.jboss.com/jira/browse/JBSEAM-273 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF Integration > Reporter: Gavin King > Assigned To: Norman Richards > Fix For: 2.1.0.GA > > > Eg. it would be very useful to be able to do: > <page view-id="document.xhtml" expires="20000"/> > Where expires gives a number in seconds, which is converted by Seam to an absolute time. > But more generally, we want to be able to do stuff like: > <page view-id="document.xml"> > <header name="Content-Type">test/xml</header> > </page> -- 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
0
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