December 2006 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-432) Support @IfInvalid functionality without @IfInvalid

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-432?page=comments#action_12348880 ] Gavin King commented on JBSEAM-432: ----------------------------------- OIC > Support @IfInvalid functionality without @IfInvalid > --------------------------------------------------- > > Key: JBSEAM-432 > URL: http://jira.jboss.com/jira/browse/JBSEAM-432 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Affects Versions: 1.1.0.BETA1 > Reporter: Christian Bauer > Assigned To: Norman Richards > Fix For: 1.1.1.GA > > > The "Previous Page" button has to Update Model Values, but not Process Validations: > <h:form> > <f:facet name="beforeInvalidField"> > <h:graphicImage value="/img/attention.gif" > width="18" height="18" > styleClass="attentionImage"/> > </f:facet> > <f:facet name="afterInvalidField"> > <s:message/> > </f:facet> > <f:facet name="aroundInvalidField"> > <s:span styleClass="errors"/> > </f:facet> > <div class="errors" align="center"> > <h:messages globalOnly="true"/> > </div> > <s:validateAll> > <div class="entry"> > <div class="label">#{messages['Firstname']}:</div> > <div class="input"> > <s:decorate> > <h:inputText size="32" required="true" > value="#{register.user.firstname}"/> > </s:decorate> > </div> > </div> > <div class="entry"> > <div class="label">#{messages['Lastname']}:</div> > <div class="input"> > <s:decorate> > <h:inputText size="32" required="true" > value="#{register.user.lastname}"/> > </s:decorate> > </div> > </div> > <div class="entry"> > <div class="label">#{messages['Email']}:</div> > <div class="input"> > <s:decorate> > <h:inputText size="32" required="true" > value="#{register.user.email}"/> > </s:decorate> > </div> > </div> > <div class="entry"> > <div class="label"> </div> > <div class="input"> > <h:commandButton value="#{messages['PrevPage']}" styleClass="button" > action="register"/> > <h:commandButton value="#{messages['NextPage']}" styleClass="button" > action="#{register.enterProfile}"/> > </div> > </div> > </s:validateAll> > </h: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

19 years, 3 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-432) Support @IfInvalid functionality without @IfInvalid

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-432?page=comments#action_12348878 ] Gavin King commented on JBSEAM-432: ----------------------------------- What Christian wants is to have a wizard where you can remember non-valid entry, but still allow backward navigation. The only logical place to keep the non-valid entry is on the model, so basically the idea is to allow a "back" button that skips validation and goes straight through to UPDATE_MODEL_VALUES. You would obviously only use this in conjunction with an atomic extended persistence context. > Support @IfInvalid functionality without @IfInvalid > --------------------------------------------------- > > Key: JBSEAM-432 > URL: http://jira.jboss.com/jira/browse/JBSEAM-432 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Affects Versions: 1.1.0.BETA1 > Reporter: Christian Bauer > Assigned To: Norman Richards > Fix For: 1.1.1.GA > > > The "Previous Page" button has to Update Model Values, but not Process Validations: > <h:form> > <f:facet name="beforeInvalidField"> > <h:graphicImage value="/img/attention.gif" > width="18" height="18" > styleClass="attentionImage"/> > </f:facet> > <f:facet name="afterInvalidField"> > <s:message/> > </f:facet> > <f:facet name="aroundInvalidField"> > <s:span styleClass="errors"/> > </f:facet> > <div class="errors" align="center"> > <h:messages globalOnly="true"/> > </div> > <s:validateAll> > <div class="entry"> > <div class="label">#{messages['Firstname']}:</div> > <div class="input"> > <s:decorate> > <h:inputText size="32" required="true" > value="#{register.user.firstname}"/> > </s:decorate> > </div> > </div> > <div class="entry"> > <div class="label">#{messages['Lastname']}:</div> > <div class="input"> > <s:decorate> > <h:inputText size="32" required="true" > value="#{register.user.lastname}"/> > </s:decorate> > </div> > </div> > <div class="entry"> > <div class="label">#{messages['Email']}:</div> > <div class="input"> > <s:decorate> > <h:inputText size="32" required="true" > value="#{register.user.email}"/> > </s:decorate> > </div> > </div> > <div class="entry"> > <div class="label"> </div> > <div class="input"> > <h:commandButton value="#{messages['PrevPage']}" styleClass="button" > action="register"/> > <h:commandButton value="#{messages['NextPage']}" styleClass="button" > action="#{register.enterProfile}"/> > </div> > </div> > </s:validateAll> > </h: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

19 years, 3 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-432) Support @IfInvalid functionality without @IfInvalid

by Norman Richards (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-432?page=comments#action_12348877 ] Norman Richards commented on JBSEAM-432: ---------------------------------------- I don't understand this request. Why does immediate="true" not work? That will allow you to trigger a back action without applying the values. Is there the desire is to keep the input fields populated with the potentially invalid data? You certainly don't want to push these values to the model without validation. That defeats the whole purpose of having validation in the first place. Even if you did skip validation, how would you handle an error when updating the model from the input value that wasn't validated? Am I missing something here? If immediate="true" is really insufficient, I think the solution would be to simply not bounce between different views. If you stay within the same view, you can preserve the invalid state in the view without corrupting the model. The easiest way that I know of to accomplish this is to put all the panels one one view and only render the active panel. You are free to move between panels with validation and model updates or between panels with no validation and only updating the UI component data, which will still be there if a panel is re-rendered later. > Support @IfInvalid functionality without @IfInvalid > --------------------------------------------------- > > Key: JBSEAM-432 > URL: http://jira.jboss.com/jira/browse/JBSEAM-432 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Affects Versions: 1.1.0.BETA1 > Reporter: Christian Bauer > Assigned To: Norman Richards > Fix For: 1.1.1.GA > > > The "Previous Page" button has to Update Model Values, but not Process Validations: > <h:form> > <f:facet name="beforeInvalidField"> > <h:graphicImage value="/img/attention.gif" > width="18" height="18" > styleClass="attentionImage"/> > </f:facet> > <f:facet name="afterInvalidField"> > <s:message/> > </f:facet> > <f:facet name="aroundInvalidField"> > <s:span styleClass="errors"/> > </f:facet> > <div class="errors" align="center"> > <h:messages globalOnly="true"/> > </div> > <s:validateAll> > <div class="entry"> > <div class="label">#{messages['Firstname']}:</div> > <div class="input"> > <s:decorate> > <h:inputText size="32" required="true" > value="#{register.user.firstname}"/> > </s:decorate> > </div> > </div> > <div class="entry"> > <div class="label">#{messages['Lastname']}:</div> > <div class="input"> > <s:decorate> > <h:inputText size="32" required="true" > value="#{register.user.lastname}"/> > </s:decorate> > </div> > </div> > <div class="entry"> > <div class="label">#{messages['Email']}:</div> > <div class="input"> > <s:decorate> > <h:inputText size="32" required="true" > value="#{register.user.email}"/> > </s:decorate> > </div> > </div> > <div class="entry"> > <div class="label"> </div> > <div class="input"> > <h:commandButton value="#{messages['PrevPage']}" styleClass="button" > action="register"/> > <h:commandButton value="#{messages['NextPage']}" styleClass="button" > action="#{register.enterProfile}"/> > </div> > </div> > </s:validateAll> > </h: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

19 years, 3 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-180) navigation-rules.xml to allow redirection with parameters

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-180?page=all ] Gavin King closed JBSEAM-180. ----------------------------- Resolution: Done Done, finally, but only the parameters > navigation-rules.xml to allow redirection with parameters > --------------------------------------------------------- > > Key: JBSEAM-180 > URL: http://jira.jboss.com/jira/browse/JBSEAM-180 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.1.1.GA > > > We need to enhance JSF's navigation rules facility to support the following: > <navigation-case> > <from-action>#{searchAction.search}</from-action> > <to-view-id>searchResults.jsp</to-view-id> > <redirect> > <param name="searchPattern">#{searchAction.searchPattern}</param> > </redirect> > </navigation-case> > What I propose to do is introduce a navigation-rules.xml file and reproduce the functionality of JSF navigation rules in Seam (yuck!). -- 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

19 years, 3 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-605) navigation-rules.xml to allow outcome expression

by Gavin King (JIRA)

navigation-rules.xml to allow outcome expression ------------------------------------------------ Key: JBSEAM-605 URL: http://jira.jboss.com/jira/browse/JBSEAM-605 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1.1.GA jPDL allows us to make navigation decisions in EL instead of the Java code. This allows a lot of loose coupling and transparency. We should also support this for stateless navigation, ie: <page view-id="/loadCustomer.jsp"> <from-action expression="#{customerHome.load}" outcome="#{customerHome.found}"> <from-outcome value="true"> <render view-id="/displayCustomer.jsp"/> </from-outcome> <from-outcome value="false"> <render view-id="/notFound.jsp"/> </from-outcome> </from-action> </page> It can reduce to: <page view-id="/loadCustomer.jsp"> <from-action expression="#{customerHome.load}"> <from-outcome value="success"> <render view-id="/displayCustomer.jsp"/> </from-outcome> <from-outcome value="not-found"> <render view-id="/notFound.jsp"/> </from-outcome> </from-action> </page> to emulate a normal JSF navigation rule. -- 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

19 years, 3 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-180) navigation-rules.xml to allow redirection with parameters

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-180?page=all ] Gavin King updated JBSEAM-180: ------------------------------ Fix Version/s: 1.1.1.GA > navigation-rules.xml to allow redirection with parameters > --------------------------------------------------------- > > Key: JBSEAM-180 > URL: http://jira.jboss.com/jira/browse/JBSEAM-180 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.1.1.GA > > > We need to enhance JSF's navigation rules facility to support the following: > <navigation-case> > <from-action>#{searchAction.search}</from-action> > <to-view-id>searchResults.jsp</to-view-id> > <redirect> > <param name="searchPattern">#{searchAction.searchPattern}</param> > </redirect> > </navigation-case> > What I propose to do is introduce a navigation-rules.xml file and reproduce the functionality of JSF navigation rules in Seam (yuck!). -- 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

19 years, 3 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-603) <page requires-conversation="true" no-conversation-view-id="..."/>

by Gavin King (JIRA)

<page requires-conversation="true" no-conversation-view-id="..."/> ------------------------------------------------------------------ Key: JBSEAM-603 URL: http://jira.jboss.com/jira/browse/JBSEAM-603 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Gavin King Assigned To: Gavin King Priority: Minor Fix For: 1.1.1.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

19 years, 3 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-179) Redirect component

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-179?page=all ] Gavin King closed JBSEAM-179. ----------------------------- Resolution: Done > Redirect component > ------------------ > > Key: JBSEAM-179 > URL: http://jira.jboss.com/jira/browse/JBSEAM-179 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.0 > > > We need to allow easy redirection to urls with parameters. The "redirect" component will have the following operations: > Redirect.setParameter(String, Object) > Redirect.setViewId(String) > Redirect.captureCurrentRequest() > Redirect.push() > Redirect.pop() > Redirect.redirect() > Redirect is a conversation-scope component that has a stack of viewId+parameters, so you can, for example, easily redirect to a login page from a Seam page action, and then redirect back to the requested 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

19 years, 3 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-471) Method getUserPrincipal() in UserPrincipal has NullPointerException

by Crayton OSteen (JIRA)

Method getUserPrincipal() in UserPrincipal has NullPointerException ------------------------------------------------------------------- Key: JBSEAM-471 URL: http://jira.jboss.com/jira/browse/JBSEAM-471 Project: JBoss Seam Issue Type: Patch Components: Core Affects Versions: 1.1.0.BETA1 Reporter: Crayton OSteen Assigned To: Gavin King Priority: Trivial Fix For: 1.1.0.BETA1 -- 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

19 years, 3 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-579) Component creation restriction for Component-driven events

by Ciro Cavani (JIRA)

Component creation restriction for Component-driven events ---------------------------------------------------------- Key: JBSEAM-579 URL: http://jira.jboss.com/jira/browse/JBSEAM-579 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Ciro Cavani Priority: Optional Actually, the raising of an event create new instance of component that isn't found in conversation (or context below). Sometimes, the behavior waited is that the event raising just touch observer components that were already in conversation (or context below). Other possibility is set on Observer annotation if that component must be or not created when there isn't found. Suggestion on forum! -- 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

19 years, 3 months

2
2
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 December 2006