January 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-653) Form errors at top of page, with field names in the messages, and links to the field

by Gavin King (JIRA)

Form errors at top of page, with field names in the messages, and links to the field ------------------------------------------------------------------------------------ Key: JBSEAM-653 URL: http://jira.jboss.com/jira/browse/JBSEAM-653 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Gavin King Errors should be nicely displayable at the top of the form, as well as beside the fields. JSF is not so good for this ootb. -- 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, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-622) Organize the wiki for the blogs / articles etc.

by Michael Yuan (JIRA)

Organize the wiki for the blogs / articles etc. ----------------------------------------------- Key: JBSEAM-622 URL: http://jira.jboss.com/jira/browse/JBSEAM-622 Project: JBoss Seam Issue Type: Feature Request Reporter: Michael Yuan 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, 11 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2085) Documentation for deploying Seam on WAS

by Pete Muir (JIRA)

Documentation for deploying Seam on WAS --------------------------------------- Key: JBSEAM-2085 URL: http://jira.jboss.com/jira/browse/JBSEAM-2085 Project: JBoss Seam Issue Type: Task Components: Documentation Reporter: Pete Muir Fix For: 2.0.x Needs documentation for this. I'm going to use this issue as a place to put links to useful snippets of info until we can get them onto a wiki/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, 11 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2541) Seam-gen generated build.properties file should also go into the created project's build.properties file

by Mark Schmatz (JIRA)

Seam-gen generated build.properties file should also go into the created project's build.properties file -------------------------------------------------------------------------------------------------------- Key: JBSEAM-2541 URL: http://jira.jboss.com/jira/browse/JBSEAM-2541 Project: JBoss Seam Issue Type: Feature Request Components: Tools Environment: Generating Seam projects with Seam-gen Reporter: Mark Schmatz Priority: Minor Each Seam project has the build.properties file underneath the root folder consisting of the following line of code: jboss.home = /your/path/to/jboss-as This is not that much data. In particular not when you take a look at the Seam-gen generated build.properties file carrying something like this: #Generated by seam setup #Sun Jan 27 16:20:01 CET 2008 hibernate.connection.password=xyz workspace.home=/home/schmatz/my/projects/business/citypics model.package=org.tztz.citypics.model driver.jar=/opt/jdbc-root/postgresql-8.2-505.jdbc3.jar action.package=org.tztz.citypics.action test.package=org.tztz.citypics.test database.type=postgres richfaces.skin=blueSky hibernate.default_catalog.null= hibernate.default_schema.null= database.drop=y project.name=citypics hibernate.connection.username=citypics hibernate.connection.driver_class=org.postgresql.Driver hibernate.cache.provider_class=org.hibernate.cache.HashtableCacheProvider project.type=ear icefaces.home= database.exists=n jboss.home=/your/path/to/jboss-as hibernate.dialect=org.hibernate.dialect.PostgreSQLDialect hibernate.connection.url=jdbc\:postgresql\:citypics Well, this complete Seam-gen generated data should also go into the project's build.properties file in order that you can restore all relevant information after you've changed them because of another Seam project requiring the seam setup with other inputs. Additionally, this would increase coherence because the build properties are bundled with the respective project. -- 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, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-513) Contextual Events for Seam Framework

by Peter Muir (JIRA)

Contextual Events for Seam Framework ------------------------------------ Key: JBSEAM-513 URL: http://jira.jboss.com/jira/browse/JBSEAM-513 Project: JBoss Seam Issue Type: Feature Request Components: Framework Affects Versions: 1.1.0.BETA2 Reporter: Peter Muir It would be good if the framework raised events when actions occurred e.g.org.jboss.seam.framework.persist.<myEntityHomeName> org.jboss.seam.framework.update.<myEntityHomeName> My use case is a 'Activity History' which records a text-history performed by users. -- 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, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-439) Allow nested conversations when navigating between CRUD entities

by James Salt (JIRA)

Allow nested conversations when navigating between CRUD entities ---------------------------------------------------------------- Key: JBSEAM-439 URL: http://jira.jboss.com/jira/browse/JBSEAM-439 Project: JBoss Seam Issue Type: Feature Request Components: Framework Environment: All Reporter: James Salt Priority: Minor Enhance the current entityHome pattern to allow the navigation between entities (i.e. linked entities customer to order link), via a navigation commandlink/slink etc. This would then allow you to navigate through a graph of interalated entities and to simply close the current entity editor and POP back to the entity editor you navigated from. This would allow a conversation tree effect so that you could go down three levels of links and then slowly pop back up to the original object, as you press each close button. would need two extra functions in the entityHome: close -> Closes current entity (ends conversation) and pop back to the parent conversation. You could also extend the close to remember any page that called via the view id, and return to that (i.e. customer list page). navigate -> invokes the entityHome for the linked entity (i.e. order), and begins the nested 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

16 years, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-404) Improved exception handling rules

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-404?page=all ] Pete Muir closed JBSEAM-404. ---------------------------- Resolution: Out of Date This was done a while back > Improved exception handling rules > --------------------------------- > > Key: JBSEAM-404 > URL: http://jira.jboss.com/jira/browse/JBSEAM-404 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Louis Coetzee > > Seam provides the @Redirect annotation for use on Exception classes. It provides an attribute to specify the target viewId to redirect to once the exception has been thrown. It would be good if this view Id can be specified dynamically. > e.g. > @Name("napException") > @ApplicationException(rollback=true) > @Redirect(viewId = "#{napException.viewId}") > public class NAPException extends Exception implements Serializable { > or in xml > <from-view-id>/xxx.jsp</from-view-id> > <from-exception>com.myapp.NAPException</from-exception> > <to-view-id>/error.jsp</to-view-id> > <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

16 years, 11 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-373) create context events

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-373?page=all ] Pete Muir closed JBSEAM-373. ---------------------------- Resolution: Out of Date We now have events for both pre and post destroy. > create context events > --------------------- > > Key: JBSEAM-373 > URL: http://jira.jboss.com/jira/browse/JBSEAM-373 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Gavin King > > We have events for context destruction, we also need them for creation of contexts. -- 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, 11 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-357) Add support in Seam for intra portlet communication.

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-357?page=all ] Pete Muir reassigned JBSEAM-357: -------------------------------- Assignee: (was: Gavin King) > Add support in Seam for intra portlet communication. > ----------------------------------------------------- > > Key: JBSEAM-357 > URL: http://jira.jboss.com/jira/browse/JBSEAM-357 > Project: JBoss Seam > Issue Type: Feature Request > Components: Portal > Reporter: jarkko Lietolahti > Priority: Critical > > When using Seam in Portal environment make it possible to specify which PortletSession context is used to storage attributes. See forum thread for more information. -- 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, 11 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-340) Streamline use of i18n validation error messages

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-340?page=all ] Pete Muir closed JBSEAM-340. ---------------------------- Resolution: Out of Date Yes, we have solved this IIRC. > Streamline use of i18n validation error messages > ------------------------------------------------- > > Key: JBSEAM-340 > URL: http://jira.jboss.com/jira/browse/JBSEAM-340 > Project: JBoss Seam > Issue Type: Bug > Components: Core > Affects Versions: 1.0.1 > Environment: Seam 1.0.1.GA > Reporter: Manfred Moser > Assigned To: Emmanuel Bernard > > As described in the forum post referenced introducing i18n error message from validation of an entity bean does not have an example anywhere and actually only works nicely with a bit of a work around. The situation is that the hibernate validation needs the error message in ValidatorMessages_*.properties and Seam has its properties in messages_*.properties. For the entity bean to work without Seam (e.g. in a unit test that verifies the validation settings) the messages have to exist in the hibnerate resource bundle. For usage in Seam they have to exist in the Seam bundle. For a Seam app to actually start up all properties related to exist in the Hibnerate and the Seam bundles .. which leads to ugly duplication. A fix is to keep all properties in the seam bundles and copy them into the hibernate bundle at build time. The forum post has a ant task. It would however be better if Seam could somehow manage to pass the resources to hibernate or otherwise just automatically include the hibernate bundle. An example of the i18n of the validation message and other annotation based messages should be included in the examples. -- 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, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2008