December 2006 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-418) Allow reloading of resource bundles without AS restart

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-418?page=all ] Gavin King closed JBSEAM-418. ----------------------------- Resolution: Won't Fix That blog is wrong. In JBoss the resource bundle reloads after restarting the ear. > Allow reloading of resource bundles without AS restart > ------------------------------------------------------ > > Key: JBSEAM-418 > URL: http://jira.jboss.com/jira/browse/JBSEAM-418 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Christian Bauer > Priority: Minor > > http://technology.amis.nl/blog/?p=1360 -- 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-135) Patch to allow pluggable validation implementations

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-135?page=all ] Gavin King closed JBSEAM-135. ----------------------------- Resolution: Out of Date No longer relevant since @IfInvalid was deprecated > Patch to allow pluggable validation implementations > --------------------------------------------------- > > Key: JBSEAM-135 > URL: http://jira.jboss.com/jira/browse/JBSEAM-135 > Project: JBoss Seam > Issue Type: Patch > Components: Core > Affects Versions: 1.0 beta 2 > Reporter: Marvin van Schalkwyk > Attachments: pluggable-validator.patch, validation-(a)ifValid.patch > > > I needed to replace the Hibernate Validator implementation with my own. I also needed to allow invalid values that were not associated with a particular property. > Summary of changes: > - New package, org.jboss.seam.validator, that defines interfaces for Component Validator Factories, Component Validators, and Invalid Values. Also in here are the default Hibernate Validator implementations of each. > - New built-in component, org.jboss.seam.core.Validator, that provides the ComponentValidatorFactory instances. Exposes a factoryClass attribute for seam.properties to replace the default Hibernate Validator factory implementation. > - Changes to Component for obvious reasons, and also to lazily initialize validators, since validation now depends on a component in application scope. > - Changes to Initialization to init new Validator component. > - Changes to the InterceptorTest to get it working with the changes. -- 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-80) Allow @In("#{jstl expression}")

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-80?page=all ] Gavin King closed JBSEAM-80. ---------------------------- Resolution: Done > Allow @In("#{jstl expression}") > ------------------------------- > > Key: JBSEAM-80 > URL: http://jira.jboss.com/jira/browse/JBSEAM-80 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.0 beta 2 > > -- 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-589) no-conversation-view-id doesn't redirect if cid isn't transmitted as request parameter

by adsf adsf (JIRA)

no-conversation-view-id doesn't redirect if cid isn't transmitted as request parameter -------------------------------------------------------------------------------------- Key: JBSEAM-589 URL: http://jira.jboss.com/jira/browse/JBSEAM-589 Project: JBoss Seam Issue Type: Bug Components: BPM Affects Versions: 1.1.0.GA Reporter: adsf adsf Seam ignores 'no-conversation-view-id' attributes / tags in pages.xml & pageflow files if 'cid' & 'clr' parameters aren't transmitted. I.e. I have a 'editStuff.xhtml' page within a pageflow. The 'no-conversation-view-id' attribute is set to 'home.xhtml'. When I call editStuff without a running conversation with something like 'editStuff.xhtml?cid=7&clr=true' I get redirected - as expected - to 'home.xhtml'. But when I call only 'editStuff.xhtml' - again without a running conversation - the page is shown but makes no sense because the conversation is missing. IMHO one should get redirected because a pageflow relies on a conversation - if there is no conversation the page probably makes no sense. Further it doesn't really matter if I transmit a wrong or none conversation id - the result is the same: no conversation is restored, therefore one should get redirected. PS: I am not sure if BPM is the right category - please move it to a more fitting one if it's wrong! -- 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
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-539) Add in support for enterprisedb

by gregorypierce (JIRA)

Add in support for enterprisedb ------------------------------- Key: JBSEAM-539 URL: http://jira.jboss.com/jira/browse/JBSEAM-539 Project: JBoss Seam Issue Type: Feature Request Components: Tools Affects Versions: 1.1.0.CR1 Reporter: gregorypierce EnterpriseDB is a Postgres dialect database with coolness in tools and support. The following conditions, when put in the appropriate locations, will give you support for this database out of the box. <property name="database.type.default" value="hsql"/> <input addproperty="database.type.new" message="What kind of database are you using? [${database.type.default}] " validargs="hsql,mysql,oracle,postgres,mssql,db2,sybase,enterprisedb" defaultvalue="${database.type.default}"/> <condition property="hibernate.dialect.default" value="org.hibernate.dialect.PostgreSQLDialect"> <equals arg1="${database.type.new}" arg2="enterprisedb"/> </condition> <condition property="hibernate.connection.driver_class.default" value="com.edb.Driver"> <equals arg1="${database.type.new}" arg2="enterprisedb"/> </condition> <condition property="hibernate.connection.url.default" value="jdbc:edb://localhost:5444/edb"> <equals arg1="${database.type.new}" arg2="enterprisedb"/> </condition> -- 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
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-401) Contexts.destroy(BusinessProcessContext) hits the database after the seam managed transaction ends

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-401?page=all ] Gavin King updated JBSEAM-401: ------------------------------ Fix Version/s: 1.2.0.BETA1 (was: 1.1.1.GA) slip until jBPM improves JTA support > Contexts.destroy(BusinessProcessContext) hits the database after the seam managed transaction ends > -------------------------------------------------------------------------------------------------- > > Key: JBSEAM-401 > URL: http://jira.jboss.com/jira/browse/JBSEAM-401 > Project: JBoss Seam > Issue Type: Bug > Components: Core > Affects Versions: 1.1.0.BETA1 > Reporter: Gavin King > Assigned To: Gavin King > Priority: Minor > Fix For: 1.2.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

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-477) real search screens for entities

by Gavin King (JIRA)

real search screens for entities -------------------------------- Key: JBSEAM-477 URL: http://jira.jboss.com/jira/browse/JBSEAM-477 Project: JBoss Seam Issue Type: Feature Request Components: Tools Affects Versions: 1.1.0.BETA2 Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1.0.BETA2 Currently, we can gen list screens, but not proper search screens, -- 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] Created: (JBSEAM-602) sorting for list screens in seam-gen

by Gavin King (JIRA)

sorting for list screens in seam-gen ------------------------------------ Key: JBSEAM-602 URL: http://jira.jboss.com/jira/browse/JBSEAM-602 Project: JBoss Seam Issue Type: Feature Request Components: Tools Reporter: Gavin King Assigned To: Gavin King 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] Updated: (JBSEAM-374) Normalize the event model

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-374?page=all ] Gavin King updated JBSEAM-374: ------------------------------ Fix Version/s: (was: 1.1.1.GA) Maybe someday ... not in the 1.1 series ;-) > Normalize the event model > ------------------------- > > Key: JBSEAM-374 > URL: http://jira.jboss.com/jira/browse/JBSEAM-374 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Gavin King > > Currently some events can be handled by either an @Observer method, or a method binding in events.xml. Ideally we would like this to be true for ALL events, but for now our integration with JSF and jBPM is not quite that deep. Nevertheless, there are some things we could do to allow a more consistent model where everything can be handled by either a method binding or an annotated method: > (1) Rebuild the page actions functionality on top of the Seam event bus - defining standard org.jboss.seam.page.<viewId> events that can be handled via @Observer("org.jboss.seam.page./myViewId.xhtml") > (2) Introduce "outcome observers" for JSF: if I have <h:commandButton action="myOutcome"/>, allow us to handle it using @Observer("org.jboss.seam.outcome.myOutcome") > (3) Ditto for jBPM: if I have <transition name="myTransition" ... />, allow us to handle it using @Observer("org.jboss.seam.transition.myTransition") > (4) Finally, introduce annotations layered over @Observer: @RenderPage("/myViewId.xhtml"), @Outcome("myOutcome"), @Transition("myTransition") -- 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-599) SeamRedirectFilter cuts extension

by Michael Schuetz (JIRA)

SeamRedirectFilter cuts extension --------------------------------- Key: JBSEAM-599 URL: http://jira.jboss.com/jira/browse/JBSEAM-599 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.1.0.GA Environment: JBoss 4.0.5, Seam1.1.0GA, MyFaces 1.1.4, JavaServer Facelets 1.1.11, ajax4jsf 1.0.5 Reporter: Michael Schuetz I use a Servlet which reacts on *.gge. When I now try to redirect, SeamRedirectFilter (as defined in web.xml) always cuts my extension and adds the defined one. There is no possibility to define an extension-exclude paramter for the SeamRedirectFilter in web.xml. -- 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
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 December 2006