February 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-807) Support Seam-managed HttpSessionBindingListeners

by Stuart Robertson (JIRA)

Support Seam-managed HttpSessionBindingListeners ------------------------------------------------ Key: JBSEAM-807 URL: http://jira.jboss.com/jira/browse/JBSEAM-807 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.1.6.GA Environment: Any Reporter: Stuart Robertson Priority: Optional HttpSessionBindingListeners can be extremely useful if an application needs to do something when a user enters or leaves an application. It would be nice if these could be Seam managed so they could support DI and have access to other Seam managed application components. http://tomcat.apache.org/tomcat-5.0-doc/servletapi/javax/servlet/http/Htt... -- 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, 1 month

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-690) Allow calling of org.jboss.seam.core.redirect.execute() in pages.xml

by Christian Bauer (JIRA)

Allow calling of org.jboss.seam.core.redirect.execute() in pages.xml -------------------------------------------------------------------- Key: JBSEAM-690 URL: http://jira.jboss.com/jira/browse/JBSEAM-690 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Christian Bauer Priority: Minor Instead of <redirect> I'd like to call redirect.execute() to jump to some saved location. This is useful eg. after Delete: <page view-id="/docEdit.xhtml"> <navigation from-action="#{documentHome.delete}"> <end-conversation before-redirect="true"/> <redirect-to-captured-request/> </navigation> ... -- 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, 1 month

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-398) @Redirect, @HttpError, etc, break when the occur inside EL evaluation

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-398?page=all ] Gavin King closed JBSEAM-398. ----------------------------- Fix Version/s: 1.1.6.GA Resolution: Done Already fixed in 1.1.6. > @Redirect, @HttpError, etc, break when the occur inside EL evaluation > --------------------------------------------------------------------- > > Key: JBSEAM-398 > URL: http://jira.jboss.com/jira/browse/JBSEAM-398 > Project: JBoss Seam > Issue Type: Bug > Components: Core > Affects Versions: 1.1.0.BETA1 > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.1.6.GA > > > Not sure if this can be fixed, but when a component calls another component via EL, and an exception occurs that Seam is supposed to handle, it instead gets wrapped in one of those awful ELExceptions. -- 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, 1 month

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-195) Per-variable setting of client-vs-server state saving

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-195?page=all ] Gavin King closed JBSEAM-195. ----------------------------- Resolution: Rejected Upon reflection, I think this is useless. Anyway we have page parameters. > Per-variable setting of client-vs-server state saving > ----------------------------------------------------- > > Key: JBSEAM-195 > URL: http://jira.jboss.com/jira/browse/JBSEAM-195 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > > Currently, all conversation state gets saved to the same place. This should be configurable at a finer grain. -- 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, 1 month

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-274) More flexible mapping of URLs to view ids

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-274?page=all ] Gavin King updated JBSEAM-274: ------------------------------ Fix Version/s: 1.1.8.GA It seems that the url rewriting stuff that christian uses in the wiki is a great solution to this, but maybe we can provide some built-in integration, and support for flexible configration of it.... > More flexible mapping of URLs to view ids > ----------------------------------------- > > Key: JBSEAM-274 > URL: http://jira.jboss.com/jira/browse/JBSEAM-274 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.1.8.GA > > > For example, I want to be able to use a URL like this: > http://mydomain.com/myblog/archive/200306 > To get me to archive.xhtml with a request parameter 200306 (not really a request parameter, but we could try to abstract that so that it can be used with @RequestParameter). > Not sure if this is possible without changing the JSF implementation. -- 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, 1 month

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-185) WebWork-style "result types"

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-185?page=all ] Gavin King closed JBSEAM-185. ----------------------------- Resolution: Out of Date Seam has kinda gone in a different direction to this, I guess.... > WebWork-style "result types" > ---------------------------- > > Key: JBSEAM-185 > URL: http://jira.jboss.com/jira/browse/JBSEAM-185 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF > Reporter: Gavin King > Priority: Optional > > Would it be useful to provide functionality to make it easier to do file downloads, redirection, forwards, etc? > Does it make sense to model these things as some kind of "Result" as in WebWork? So redirects/downloads/forwards could all be externalized to navigation-rules.xml. > http://www.opensymphony.com/webwork/wikidocs/Result%20Types.html -- 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, 1 month

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-604) "stackable" Redirect

by Gavin King (JIRA)

"stackable" Redirect -------------------- Key: JBSEAM-604 URL: http://jira.jboss.com/jira/browse/JBSEAM-604 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Gavin King Assigned To: Gavin King Priority: Minor This would let the user redirect to login page, then redirect back. Keep a stack of viewIds + parameters. -- 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, 1 month

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-129) JSF SelectItems automatic Converter creation using a @Selectable annotation

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-129?page=all ] Gavin King closed JBSEAM-129. ----------------------------- Resolution: Out of Date Assignee: Pete Muir Pete Muir's stuff supercedes this old issue. > JSF SelectItems automatic Converter creation using a @Selectable annotation > --------------------------------------------------------------------------- > > Key: JBSEAM-129 > URL: http://jira.jboss.com/jira/browse/JBSEAM-129 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF > Environment: Jboss Application Server using Myfaces jsf and Seam from CVS > Reporter: James Salt > Assigned To: Pete Muir > Original Estimate: 1 week > Remaining Estimate: 1 week > > The entity class annotated with @Selectable would have to have an @Id attribute and a attribute annotated with something like @SelectionName for the displayed name of the object in the selectItems. > The converters for each @Selectable entity could be created and cached at seam scanner time for each entity component that had @Selectable annotation. This scanner task would also need to dynamically register the converters with jsf/myfaces which I believe is possible using the myfaces Application class (don't know about the RI implementation). > The user would be responsible for the creation of the list of objects (Seam supplying a static method to convert a list of objects to a list of select items), then the converters would deal with converting the selected item back to the object using a direct database lookup. > As mentioned in the below thread, the object marked as @Selectable would need to implement a custom equals operation (being careful about @Datamodel update issues), so that myfaces could validate it correctly. > For reverese engineering purposes, anything that has a field of a certain object would infer that that object is selectable, then the user could customise which field is used for the @Selectionname annotation. This would be very valuable when reverse engineering, and would remove a significant coding burden from the Seam developer. -- 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, 1 month

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-331) NPE in PageContext.getCurrentReadableMap() and PageContext.getCurrentWritableMap(), using others PhaseListeners

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-331?page=all ] Gavin King closed JBSEAM-331. ----------------------------- Resolution: Out of Date Assignee: Gavin King > NPE in PageContext.getCurrentReadableMap() and PageContext.getCurrentWritableMap(), using others PhaseListeners > --------------------------------------------------------------------------------------------------------------- > > Key: JBSEAM-331 > URL: http://jira.jboss.com/jira/browse/JBSEAM-331 > Project: JBoss Seam > Issue Type: Patch > Components: JSF > Environment: JBoss 4.0.4-GA, JBoss Seam 1.0.1-GA, Ajax4Jsf 1.0 rc4 > Reporter: Luiz Augusto Ruiz > Assigned To: Gavin King > > SeamPhaseListener.afterPhase() invokes Lifecycle.setPhaseId(null) after the phase INVOKE_APPLICATION(5). If exists other PhaseListener that is called after SeamPhaseListener, and use a variable, when the methods PageContext.getCurrent [Readable/Writeble] Map() are called the Null Pointer Exception occurs. > The patch checks for null PhaseId before use it. > ---------------------------- > private Map getCurrentReadableMap() > { > PhaseId phaseId = Lifecycle.getPhaseId(); > if (null == phaseId) { > return nextPageMap; > } > return phaseId.compareTo(PhaseId.INVOKE_APPLICATION) > 0 ? > nextPageMap : previousPageMap; > } > private Map getCurrentWritableMap() > { > PhaseId phaseId = Lifecycle.getPhaseId(); > if (null == phaseId) { > return nextPageMap; > } > return phaseId.compareTo(PhaseId.INVOKE_APPLICATION) < 0 ? > previousPageMap : nextPageMap; > } > ------------------------------------- -- 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, 1 month

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-144) Display validation messages on components for validation issues on child objects

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-144?page=all ] Gavin King updated JBSEAM-144: ------------------------------ Fix Version/s: 1.1.8.GA > Display validation messages on components for validation issues on child objects > -------------------------------------------------------------------------------- > > Key: JBSEAM-144 > URL: http://jira.jboss.com/jira/browse/JBSEAM-144 > Project: JBoss Seam > Issue Type: Patch > Components: JSF > Affects Versions: 1.0 beta 2 > Reporter: Andrew > Assigned To: Gavin King > Fix For: 1.1.8.GA > > Attachments: JBSEAM-144.diff > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > I have submitted a patch to hibernate-annotations: ANN-208 (http://opensource2.atlassian.com/projects/hibernate/browse/ANN-208) > This patch creates validation issues for child objects. The format is: > mbean.collection[collection-index].childProperty > Example: > user.addresses[1].street > This patch allows the ValidationInterceptor to attempt to find the "street" UIComponent. It does this by using the "dataTable" naming: > addresses:1:street > Which would be produced by: > <t:dataTable var="address" value="#{user.addresses}"> > <t:column> > <t:inputText value="#{addresss.street}" /> > ... -- 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, 1 month

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 February 2007