November 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2241) testreport doesn't log failures in @BeforeClass etc. as test failures

by Pete Muir (JIRA)

testreport doesn't log failures in @BeforeClass etc. as test failures --------------------------------------------------------------------- Key: JBSEAM-2241 URL: http://jira.jboss.com/jira/browse/JBSEAM-2241 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA Reporter: Pete Muir Fix For: 2.0.1.GA This makes it harder to see when the tests are failing due to jboss embedded errors -- 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
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2201) include <generic-type> in components.xml

by Dan Hinojosa (JIRA)

include <generic-type> in components.xml ---------------------------------------- Key: JBSEAM-2201 URL: http://jira.jboss.com/jira/browse/JBSEAM-2201 Project: JBoss Seam Issue Type: Feature Request Reporter: Dan Hinojosa I would like a generic-type allowed in components.xml so that we can have genericized beans. For example <component name="productManagerBean" scope="SESSION" class="com.xyzcorp.session.SimplePersistenceManagementBean" generic-type="com.xyzcorp.entity.Product" /> This would be great so we could do some kick ass stuff like this @Stateful public class SimplePersistenceManagementBean<E> { private E entity; @PersistenceContext(....) private EntityManager em; public void setEntity(E entity) { this.entity = entity; } public void create() { em.persist(e); } public void update() { em.merge(e); } ....... } Now, ain't that sexy? -- 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-2202) Make all basic JSF Converters and Validators into Seam Components

by Dan Hinojosa (JIRA)

Make all basic JSF Converters and Validators into Seam Components ----------------------------------------------------------------- Key: JBSEAM-2202 URL: http://jira.jboss.com/jira/browse/JBSEAM-2202 Project: JBoss Seam Issue Type: Feature Request Reporter: Dan Hinojosa I was thinking though through this problem that all basic converters should be accessible as a seam components. The impetus for this idea came from a problem I was having of displaying prices in a drop down list, see forum link for details. -- 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-1856) Transaction Commit and Rollback events

by Moshe Immerman (JIRA)

Transaction Commit and Rollback events -------------------------------------- Key: JBSEAM-1856 URL: http://jira.jboss.com/jira/browse/JBSEAM-1856 Project: JBoss Seam Issue Type: Feature Request Reporter: Moshe Immerman It would be nice to have org.jboss.seam.transactionCommit and org.jboss.seam.transactionRollback events -- 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-1908) Booking example clones need updating to newer s:decorate

by Pete Muir (JIRA)

Booking example clones need updating to newer s:decorate -------------------------------------------------------- Key: JBSEAM-1908 URL: http://jira.jboss.com/jira/browse/JBSEAM-1908 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.0.BETA1 Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.0.0.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

16 years, 11 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1680) Have a way to "bootsrap" the seam engine for batch processes

by Denis Forveille (JIRA)

Have a way to "bootsrap" the seam engine for batch processes ------------------------------------------------------------ Key: JBSEAM-1680 URL: http://jira.jboss.com/jira/browse/JBSEAM-1680 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.0.0.BETA1, 1.2.1.GA Reporter: Denis Forveille It should be possible to write a "pure" batch processes that uses seam components. Seam should provide a way to "bootstrap" the "seam engine" outside any web/jee container to allow programmers to reuse seam components outside a war, typically from a standard "main" method, run with a standard j2se class. Typical scenario/usage for this: - an online application build around seam, POJOs and hibernate. - the business seam components ("managers" + "model" classes) are isolated into a separate jar file (common.jar) - the "view controllers", which are seam components (aka "backing beans") are directly held into the war module - the war module uses the business components held into the common.jar module. - a batch process, which is standard j2se class with a main method, performs some business process by calling the "business" seam components defined in the common.jar file. The high-level algorithm of this "batch" process is the following - bootstrap the seam engine - for each business item to process (maybe tens of thousand or more...): - begin transaction - do some business stuff by calling the seam components in common.jar that read/update the database - commit - shutdown the seam engine For this, we need a class or harness to "boostrap" the seam engine. This harness should not depends on any of the services provided by a typical web/ jee container, this includes: - naming/jndi - security - jsf/jsp/facelets - ...etc The harness should be able to manage injection/bijection of user defined components and also to provide the injection of some non-web dependent object like the hibernate session and the logger. Of course none of the "web" functions are required (Conversation managment, @DataModel etc...) At a minimun, this harness should be able to handle the @Name, @In, @Out, @Create, @Destroy, @Factory, @Transactional, @Logger annotations Big Thanks... -- 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-1612) adding default option in configuration files flush=MANUAL

by Krunoslav Samardzic (JIRA)

adding default option in configuration files flush=MANUAL --------------------------------------------------------- Key: JBSEAM-1612 URL: http://jira.jboss.com/jira/browse/JBSEAM-1612 Project: JBoss Seam Issue Type: Feature Request Reporter: Krunoslav Samardzic I belive it would be usefull to add such capability, so one does not have to apply it every time, if all of conversations in project are going to flush manualy -- 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

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-911) endAndRedirect() in jBPM pageflow

by Gavin King (JIRA)

endAndRedirect() in jBPM pageflow --------------------------------- Key: JBSEAM-911 URL: http://jira.jboss.com/jira/browse/JBSEAM-911 Project: JBoss Seam Issue Type: Feature Request Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1.8 GA Currently all jbpm pageflows and at a specific page. We want to be able to end the flow at the page of the parent conversation, by introducing something like an end-state element. Perhaps we should also have the ability to return to the starting page even when there was no parent 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
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1320) Seam Captcha component: clear response field before redisplaying

by Paul Milner (JIRA)

Seam Captcha component: clear response field before redisplaying ---------------------------------------------------------------- Key: JBSEAM-1320 URL: http://jira.jboss.com/jira/browse/JBSEAM-1320 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.2.1.GA Environment: Any Reporter: Paul Milner Priority: Minor As suggested on the Seam Forum, I am submitting this as a feature request: Hi using the captcha provided with Seam (and used as suggested in the Seam documentation), I have the following problem. If I submit a page which contains the captcha, and having filled in the catpcha response field, but validation fails due to a problem in another field on the page, the page is redisplayed but with a NEW captcha image. However the captcha response field is repopulated with what I previously put there, even though the image has now changed. I would like for the response text to be cleared when a new captcha image is generated. Is there a way to do this at the moment? Thanks in advance, Paul -- 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

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1312) Extend Compoent.initInterceptors to scan Annnotations on methods for additional interceptors

by Chris Rudd (JIRA)

Extend Compoent.initInterceptors to scan Annnotations on methods for additional interceptors -------------------------------------------------------------------------------------------- Key: JBSEAM-1312 URL: http://jira.jboss.com/jira/browse/JBSEAM-1312 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.2.1.GA Reporter: Chris Rudd It would be nice if the Component.initInterceptors method not only scanned the annotations on the class for additional interceptors but also scanned the methods / fields for additional interceptors. This would allow more flexability. EG the @LoggedIn from the examples could be extended so that it checked for a class level or method level @LoggedIn annotation to instruct it to do the check (instead of only the class level as it is now). Naturally you would want to remove the class level annotation and only put it on the methods that require being logged in. BUT if you do that, the auto-magic initInterceptor code wont know to add the LoggedInInterceptor. Altered initInterceptors: private void initInterceptors() { initDefaultInterceptors(); findInterceptors(new AnnotatedElement[] { component.getBeanClass() }); for (Class clazz = component.getBeanClass(); clazz != Object.class; clazz = clazz .getSuperclass()) { findInterceptors(clazz.getDeclaredFields()); findInterceptors(clazz.getDeclaredMethods()); } } Additional support method : protected void findInterceptors(AnnotatedElement[] aes) { for (AnnotatedElement ae : aes) { for (Annotation annotation : ae.getAnnotations()) { if ( annotation.annotationType().isAnnotationPresent(INTERCEPTORS) ) { Class[] classes = value( annotation.annotationType().getAnnotation(INTERCEPTORS) ); addInterceptor( new Interceptor(classes, annotation, this) ); } if ( annotation.annotationType().isAnnotationPresent(Interceptors.class) ) { Class[] classes = annotation.annotationType().getAnnotation(Interceptors.class).value(); addInterceptor( new Interceptor(classes, annotation, this) ); } } } } -- 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
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2007