September 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4411) jPDL re-installing its first seam object

by Tony Herstell (JIRA)

jPDL re-installing its first seam object ---------------------------------------- Key: JBSEAM-4411 URL: https://jira.jboss.org/jira/browse/JBSEAM-4411 Project: Seam Issue Type: Bug Components: BPM Affects Versions: 2.2.0.GA Environment: WinXP64 MyEclipse JBoss latest RF Reporter: Tony Herstell Priority: Critical Given this snippit <start-state name="entry"> <transition name="start" to="getUsersDetails"> <action expression="#{risingstars.registrationController.initUpdateRegistrationDetails}"></action> </transition> </start-state> <page name="getUsersDetails" view-id="/pages/user/updateUserDetails.xhtml" redirect="true" no-conversation-view-id="/home.xhtml"> <description>Updating of User (#{risingstars.user.lastname}, #{risingstars.user.firstname})</description> <transition name="cancel" to="end" /> <transition name="next" to="evaluateDetails"/> </page> I enter the jPDL and the bean has a User in scope... say (say id 123) auto created by @In(create=true) @Out(required=true) private User user; I then do this in initUpdateRegistrationDetails : this.user = (User) entityManager.createQuery("from User u where u.email = :email").setParameter("email", credentials.getUsername()).getSingleResult(); Which forces the user in scope to now point to this new user (say id 456) What happens if by the time we get to the next page we have switched back to the original User (123). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4237) Support message-driven POJO's

by Nikolay Elenkov (JIRA)

Support message-driven POJO's ----------------------------- Key: JBSEAM-4237 URL: https://jira.jboss.org/jira/browse/JBSEAM-4237 Project: Seam Issue Type: Feature Request Components: Async Reporter: Nikolay Elenkov Currently, if you want to use JMS in a Seam project, you have to deploy it as an EAR in a JEE application server, and use MessageDriven beans. However, JMS messaging is sometimes required in web (WAR) projects as well, and changing the application to and EAR and/or the application server is not possible. Seam should make it easy to use message-driven POJO's (POJO's that act as asynchronous receivers for JMS messages) in a web project, supporting all Seam features (injection, transaction management, etc.). It could be implemented by integrating Jencks (http://jencks.codehaus.org/) for example or built on top of ActiveMQ. Cf. Spring support for message-driven POJO's: http://static.springframework.org/spring/docs/2.5.x/reference/jms.html#jm... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3349) LDAPIdentityStore generates invalid filter on listUsers method

by Vinicius Carvalho (JIRA)

LDAPIdentityStore generates invalid filter on listUsers method -------------------------------------------------------------- Key: JBSEAM-3349 URL: https://jira.jboss.org/jira/browse/JBSEAM-3349 Project: Seam Issue Type: Bug Components: Security Affects Versions: 2.1.0.BETA1 Reporter: Vinicius Carvalho The Filter generated by the component is creating an invalid query, the format is this: (objectClass={0})(objectClass={1}) Where it should be: (&(objectClass={0})(objectClass={1})) We've fixed it by overriding the method with our own ldapidentitystore, below is just the minimal chage: StringBuilder userFilter = new StringBuilder(); userFilter.append("(&"); Object[] filterArgs = new Object[getUserObjectClasses().length]; for (int i = 0; i < getUserObjectClasses().length; i++) { userFilter.append("("); userFilter.append(getObjectClassAttribute()); userFilter.append("={"); userFilter.append(i); userFilter.append("})"); filterArgs[i] = getUserObjectClasses()[i]; } userFilter.append(")"); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3685) Add "rendered" attribute to s:decorate

by Chris Simons (JIRA)

Add "rendered" attribute to s:decorate -------------------------------------- Key: JBSEAM-3685 URL: https://jira.jboss.org/jira/browse/JBSEAM-3685 Project: Seam Issue Type: Feature Request Affects Versions: 2.1.0.SP1, 2.1.0.GA, 2.1.0.CR1, 2.1.0.BETA1, 2.1.0.A1, 2.0.3.CR1, 2.0.2.SP1, 2.0.2.GA, 2.0.2.CR2, 2.0.2.CR1, 2.0.1.GA, 2.0.1.CR2, 2.0.1.CR1, 2.0.0.GA Reporter: Chris Simons Add an optional "rendered" attribute to s:decorate, if possible. If evaluated to false, this would preclude rendering of the template/component. I haven't seen a request like this in the past (I hope I didn't miss anything). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

6
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4417) login-required overriding

by Uros Majeric (JIRA)

login-required overriding ------------------------- Key: JBSEAM-4417 URL: https://jira.jboss.org/jira/browse/JBSEAM-4417 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.2.0.GA Environment: Seam 2.2 JBoss 5.1 Java 6 Reporter: Uros Majeric Priority: Minor If I add <page view-id="*" login-required="true" /> in pages.xml I can't override this with <page view-id="/some-other-page.xhtml" login-required="false" />. I need login-required="false" only for /some-other-page.xhtml page. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4349) Provide static injection option via @In

by asookazian (JIRA)

Provide static injection option via @In --------------------------------------- Key: JBSEAM-4349 URL: https://jira.jboss.org/jira/browse/JBSEAM-4349 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.2.0.GA Environment: n/a Reporter: asookazian Currently injection in Seam via @In is dynamic only. By dynamic, we mean that the instance variable that is associated with the @In annotation is refreshed with the latest value from the specified context every time a business method is invoked (specifically prior to the invocation). Request is to add a facility to allow developer to specify static injection only for that particular @In annotation instance. Add an optional element named "type" to @In. example: @In(type=static) private String foo; The default type or behavior will be dynamic. The purpose of this request is to support use case implementations that do not require dynamic injections but merely one-time static injections like Spring DI setter or constructor injections. This will help with performance as well as there will not be unnecessary "refreshing" of the instance variables via dynamic injection in those cases that are not needed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4344) testreport target does not pick up all test results on Windows

by Jozef Hartinger (JIRA)

testreport target does not pick up all test results on Windows -------------------------------------------------------------- Key: JBSEAM-4344 URL: https://jira.jboss.org/jira/browse/JBSEAM-4344 Project: Seam Issue Type: Bug Components: Test Harness Affects Versions: 2.2.0.GA Environment: Windows Server 2003 R2 Ant 1.7.0 Reporter: Jozef Hartinger Assignee: Norman Richards Fix For: 2.2.1.CR1 1.) Run the testall target 2.) Run the test-report target The generated test report contains only 54 testcases however more 200 tests are run during the testsuite execution. For instance, all the unit tests are missing as well as dvdstore, etc The faster way to reproduce is to directly call "ant test" in examples/dvdstore and then test-report in {seam.dir} Looks like removing colons from the name of each test in testng.xml fixes the problem -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2852) Scan for @WebRemote on extended Interfaces

by Alessandro Di Pasquale (JIRA)

Scan for @WebRemote on extended Interfaces ------------------------------------------- Key: JBSEAM-2852 URL: http://jira.jboss.com/jira/browse/JBSEAM-2852 Project: JBoss Seam Issue Type: Feature Request Components: Remoting Environment: 2.0.1.GA Reporter: Alessandro Di Pasquale Assigned To: Shane Bryzak Priority: Minor Class org.jboss.seam.remoting.InterfaceGenerator does not scan for WebRemote.class-Annotation in extended Business-Interfaces -- 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

14 years, 8 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4410) EntityIdentifier does not support @IdClass annotated entities ( composite keys )

by Timur Junussov (JIRA)

EntityIdentifier does not support @IdClass annotated entities ( composite keys ) --------------------------------------------------------------------------------- Key: JBSEAM-4410 URL: https://jira.jboss.org/jira/browse/JBSEAM-4410 Project: Seam Issue Type: Feature Request Components: Framework Reporter: Timur Junussov Priority: Minor EntityIdentifier does not support @IdClass annotated entities, suppose if entity has more than one @Id ( composite keys ) it's due to org.jboss.seam.Entity scans ( mergeAnnotationAndOrmXml ) for the first occurance of @Id annotated field or getter -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4121) pages.xml not hot deploying in 2.1.1 GA

by Cody Lerum (JIRA)

pages.xml not hot deploying in 2.1.1 GA --------------------------------------- Key: JBSEAM-4121 URL: https://jira.jboss.org/jira/browse/JBSEAM-4121 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Environment: JBAS 4.2.3 GA, Seam 2.1.1GA, JDK 6 Update 13 Reporter: Cody Lerum pages.xml do not seem to be getting hot deployed after a change. I have debug mode true and facelets.DEVELOPMENT=true. All my view pages are hot deploying fine but updating the navigation rules in pages.xml requires a server restart. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues September 2009