May 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1238) pages.xml - allow EL expressions in <redirect>

by Stephan Bublava (JIRA)

pages.xml - allow EL expressions in <redirect> ---------------------------------------------- Key: JBSEAM-1238 URL: http://jira.jboss.com/jira/browse/JBSEAM-1238 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.2.1.GA Reporter: Stephan Bublava Priority: Minor <redirect view-id="#{currentPage.viewId}" /> throws an exception. It would be nice, if expressions were allowed here. -- 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

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1221) propagation=drop

by Leo Baschy (JIRA)

propagation=drop ---------------- Key: JBSEAM-1221 URL: http://jira.jboss.com/jira/browse/JBSEAM-1221 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.2.1.GA Environment: all Reporter: Leo Baschy Use is to be in <s:link view="/myOther.xhtml" propagation="drop" value="Outta Here" /> propagation="none" is almost the same, but "none" leaves conversations stored in an inactive state until they timeout. One might not want that, either not to use storage, or not to allow to come back, etc. To reiterate what is specified and has been said, but still may be puzzling at times, specifically when used with s:link view="/any.xhtml", propagation="end" has effect at the end of the target page. propagation="drop" should be like propagation="none" combined with the destruction of "end". As a matter of symbolism, if you "drop" it then it breaks and does no longer exist. For now one can get the effect by instead doing this (note the funny spelling of "conversaction" != "conversation"): <s:link action="#{conversaction.endAndTo('/myOther.xhtml')}" value="Outta Here" /> backed by import org.jboss.seam.annotations.Name; import org.jboss.seam.core.Conversation; @Name("conversaction") public class Conversaction { public String endAndTo(String viewId) { Conversation.instance().end(); return viewId; } } Would be nice to avoid the redirect. -- 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

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1212) Unnecessary exception printed in log when accesing page which require logged in.

by Mariusz Smykula (JIRA)

Unnecessary exception printed in log when accesing page which require logged in. -------------------------------------------------------------------------------- Key: JBSEAM-1212 URL: http://jira.jboss.com/jira/browse/JBSEAM-1212 Project: JBoss Seam Issue Type: Feature Request Components: Security Affects Versions: 1.2.1.GA Environment: Seam 1.2.1, ICEFaces 1.5.3, JBoss AS 4.0.5 Reporter: Mariusz Smykula 17:21:49,890 ERROR [SeamPhaseListener] uncaught exception org.jboss.seam.security.NotLoggedInException at org.jboss.seam.security.Identity.checkRestriction(Identity.java:156) at org.jboss.seam.pages.Page.enter(Page.java:206) at org.jboss.seam.core.Pages.enterPage(Pages.java:276) at org.jboss.seam.jsf.AbstractSeamPhaseListener.enterPage(AbstractSeamPhaseListener.java:276) at org.jboss.seam.jsf.AbstractSeamPhaseListener.beforeRender(AbstractSeamPhaseListener.java:214) at org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:56) at org.apache.myfaces.lifecycle.PhaseListenerManager.informPhaseListenersBefore(PhaseListenerManager.java:70) at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:373) at com.icesoft.faces.webapp.xmlhttp.PersistentFacesServlet.service(PersistentFacesServlet.java:406) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:63) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:60) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:79) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Unknown Source) -- 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

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1203) Redirect doesn't allow viewId as EL

by Alan Fehr (JIRA)

Redirect doesn't allow viewId as EL ----------------------------------- Key: JBSEAM-1203 URL: http://jira.jboss.com/jira/browse/JBSEAM-1203 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 1.2.1.GA Reporter: Alan Fehr Using an EL expression in the viewId in a redirect in *.page.xml doesn't work, as it is not interpreted. Changing public void redirect(String viewId, Map<String, Object> parameters, boolean includeConversationId) in org.jboss.seam.core.Manager to incorporate this at the beginning did the trick for me: if (viewId.contains("#{")) {viewId = (String)Expressions.instance().createValueBinding(viewId).getValue();} Of course, actually parsing the string to find out if it really is an EL expression would be much better, I didn't have the time to find out how. Also the value binding may be the wrong way to go, but hey, it worked for me. It would be nice if redirecting to an EL viewId would be possible in the next release. -- 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

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1153) Parts of Seam difficult to internationalise

by Tony Herstell (JIRA)

Parts of Seam difficult to internationalise ------------------------------------------- Key: JBSEAM-1153 URL: http://jira.jboss.com/jira/browse/JBSEAM-1153 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.2.1.GA Reporter: Tony Herstell Priority: Minor Some text messages in seam are not easy to internationalise. e.g. captcha warning IN the doco it is not clear what jsf keys to use to override the jsf messages (and I dont even know if they are internationalised) -- 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

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1136) Support multiple projects in Seam Gen

by Michael Yuan (JIRA)

Support multiple projects in Seam Gen ------------------------------------- Key: JBSEAM-1136 URL: http://jira.jboss.com/jira/browse/JBSEAM-1136 Project: JBoss Seam Issue Type: Feature Request Reporter: Michael Yuan Assigned To: Michael Yuan Priority: Minor Support seam-gen property files in project directories, and the SEAM_HOME/seam-gen/build.properties is just the "default" property file if you do not specify the target project. See the forum thread below for more discussions. -- 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

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1109) Need Demo Portal application using Facelets

by Magesh Kumar B (JIRA)

Need Demo Portal application using Facelets ------------------------------------------- Key: JBSEAM-1109 URL: http://jira.jboss.com/jira/browse/JBSEAM-1109 Project: JBoss Seam Issue Type: Feature Request Components: Portal Affects Versions: 1.2.0.GA Environment: JBossPortal 2.4.1 Reporter: Magesh Kumar B The existing example portlet uses only jsps as JSF Views. Need more concrete example that uses facelets and XHTML. -- 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

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1082) E-mail obfuscation

by Adrian Mitev (JIRA)

E-mail obfuscation ------------------ Key: JBSEAM-1082 URL: http://jira.jboss.com/jira/browse/JBSEAM-1082 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Adrian Mitev It is a nice idea for Seam to have a way (component) for obfuscating text/email. Like this: http://www.seowebsitepromotion.com/obfuscate_email.asp -- 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

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1067) Allow EntityConverter to work with h:inputText and rich:suggestionBox

by Damian Harvey (JIRA)

Allow EntityConverter to work with h:inputText and rich:suggestionBox --------------------------------------------------------------------- Key: JBSEAM-1067 URL: http://jira.jboss.com/jira/browse/JBSEAM-1067 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.2.0.GA Environment: All Reporter: Damian Harvey Priority: Minor There is a requirement to be able to use the entityConverter or similar pattern in conjunction with h:inputText and the rich:suggestionBox. Ideally it would operate in a similar fashion to how the s:selectItems can take an entity and display a label. When persisting the entity is sent from the form rather than the value of the h:inputText The same functionality would also be useful with the icefaces Suggestion box. -- 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

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1001) Hot deploy for JavaBean components listed in components.xml

by Gavin King (JIRA)

Hot deploy for JavaBean components listed in components.xml ----------------------------------------------------------- Key: JBSEAM-1001 URL: http://jira.jboss.com/jira/browse/JBSEAM-1001 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King * components.xml does not currently know how to use the hotdeploy classloader * also, Initialization.redeploy() needs to account for components.xml changes, etc -- 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

2
1
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 May 2007