December 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2050) reorganize modules

by Dan Allen (JIRA)

reorganize modules ------------------ Key: JBSEAM-2050 URL: http://jira.jboss.com/jira/browse/JBSEAM-2050 Project: JBoss Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.0.0.CR1 Reporter: Dan Allen Fix For: 2.0.x I would like to make "modules" a first order directory (renamed from "src") and also organize tests so they are per-module. This will encourage per-module tests and also prevent circular dependencies (because the folders are treated as modules and not one big lump of source code). The ui module also once again finds itself adjacent to the other modules. jboss-seam/ examples/ <-- showing this just as a reference point modules/ core/ main/java test/java ui/ main/java test/java (continue for debug, ioc, gen, pdf, mail, remoting) Although Eclipse doesn't know the first think about multi-modules, this will be idea for setting up a module-aware IDE like IntelliJ IDEA (and to some degree, NetBeans). -- 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, 3 months

4
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1710) Support multiple life cycle methods (per inheritance) on JavaBean classes

by Dan Allen (JIRA)

Support multiple life cycle methods (per inheritance) on JavaBean classes ------------------------------------------------------------------------- Key: JBSEAM-1710 URL: http://jira.jboss.com/jira/browse/JBSEAM-1710 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.BETA1, 2.0.0.CR1 Reporter: Dan Allen Priority: Minor EJB supports multiple life cycle methods for a bean, as long as two life cycle methods do not appear in the same class in the inheritance hierarchy. Thus, you can define a @PostConstruct method on the concrete class, and a different @PostConstruct method on its superclass. As per the EJB specification (with minor corrections for clarity): "Life cycle callback interceptor methods may be defined on super classes of the bean class, the bean class itself, or interceptor classes. However, a given class may not have more than one life cycle callback interceptor method for the same life cycle event." The following comment is found in Component.java regarding this issue: // TODO: check the EJB3 spec, I think you are allowed to have multiple life cycle methods on a bean! The comment is correct in that multiple life cycle methods are not allowed on a single bean class. However, through inheritance, it is possible to have two different life cycle methods for the same Seam component. Currently, Component#initMembers() works backwards up the inheritance chain while scanning methods. Therefore, the life cycle method on the highest member of the hierarchy currently wins. So, as it stands now, the handling of life cycle callbacks for JavaBeans is inconsistent with how they are handled by the EJB container on session and message-driven beans. I was able to verify this with a simple demonstration I conducted. This incompatibility shouldn't be too difficult to fix. Just switch the life cycle method properties to an array and ensure that superclass methods are called first. -- 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, 3 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1670) allow multiple scopes for @In annotation

by Dan Allen (JIRA)

allow multiple scopes for @In annotation ---------------------------------------- Key: JBSEAM-1670 URL: http://jira.jboss.com/jira/browse/JBSEAM-1670 Project: JBoss Seam Issue Type: Patch Components: Core Affects Versions: 2.0.0.BETA1 Reporter: Dan Allen Priority: Minor Fix For: 2.0.0.CR1, 2.0.0.GA, 2.0.1.GA Right now, your only option for the scope on the @In annotation is an explicit scope or a hierarchical search of all the scopes. I can imagine that there are times when you want to look in a handful of scopes, but not all of them. For instance, anything within a conversation, but not above. Additionally, by making this a multi-value attribute, the developer can override the order in which the scopes are searched. They are searched in the order specified. ScopeType[] scope() default {}; This would also eliminate the need for the UNSPECIFIED scope since no scopes would assume a hierarchical search. The logic that would have to change is Component#getValueToInject() -- 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, 3 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1389) Please make the methods parse and createPage protected instead of private.

by Chris Rudd (JIRA)

Please make the methods parse and createPage protected instead of private. -------------------------------------------------------------------------- Key: JBSEAM-1389 URL: http://jira.jboss.com/jira/browse/JBSEAM-1389 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Chris Rudd We have a dynamic routine that locates pages xml files from multiple locations. Since parse and createPage are private methods we cannot override and extend the Pages component without lifting the entire source and replicating it, or using reflection to get at those methods. Neither of these are good long term aproaches. In general it seems that lots of the core components that one might want to extend to hook in additional functionality cannot be due to the use of private instead of protected methods. The extended funtionality provided by the resolution to JBSEAM-715 does not rectify my issue as that relies on explitly defining the pages xml files. I believe there are several other people who are looking for a way to use an algorithm to locate them rather than a fixed list. Making those methods protected solves the problem as it allows anyone to extend the functionaliry of the Pages component to provide extended rules / algorithms for locating pages xml files, while not affecting the functionality of the core at all. -- 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, 3 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1194) Pageflow/Process documentation improvements

by Pete Muir (JIRA)

Pageflow/Process documentation improvements ------------------------------------------- Key: JBSEAM-1194 URL: http://jira.jboss.com/jira/browse/JBSEAM-1194 Project: JBoss Seam Issue Type: Bug Components: BPM, Documentation Reporter: Pete Muir Assigned To: Pete Muir The JBPM integration chapter is a constant source of confusion to me. -- 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, 3 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-664) transactionListener component should be implemented like Hibernate TMLookup

by Gavin King (JIRA)

transactionListener component should be implemented like Hibernate TMLookup --------------------------------------------------------------------------- Key: JBSEAM-664 URL: http://jira.jboss.com/jira/browse/JBSEAM-664 Project: JBoss Seam Issue Type: Bug Components: Core Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1.5.GA It would be MUCH better if we did not have an EJB sitting in jboss-seam.jar. -- 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, 3 months

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2766) Enable Security for POJO WebServices Endpoint

by Srinivasan Raguraman (JIRA)

Enable Security for POJO WebServices Endpoint --------------------------------------------- Key: JBSEAM-2766 URL: http://jira.jboss.com/jira/browse/JBSEAM-2766 Project: JBoss Seam Issue Type: Feature Request Components: Security, WS Affects Versions: 2.0.0.GA Environment: JBoss 4.2.1GA Reporter: Srinivasan Raguraman The @Restrict annotation on Seam component are never applied if they were exposed directly as web service end-point. This is probably because the y are not initialized as seam components, by the web service layer. Right now the workaround is to have facade layer over seam components and expose them as web service end-point. The security interceptor on POJO components could be enabled by AOP interception or by some other delegation. -- 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, 3 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2332) Enable Seam Security from external client

by Andreas Eriksson (JIRA)

Enable Seam Security from external client ----------------------------------------- Key: JBSEAM-2332 URL: http://jira.jboss.com/jira/browse/JBSEAM-2332 Project: JBoss Seam Issue Type: Feature Request Components: Security Environment: JavaSE 1.5.0_12, JBoss 4.2.1.GA, JBoss Seam 2.0.0.GA Reporter: Andreas Eriksson Attachments: seam-external-client-security.zip If a Seam component is annotated with the @Restrict annotation and accessed from a POJO (in my case a Quartz job initialized by a servlet) the SecurityInterceptor isn't executed. The same goes for the Seam Entity Security. -- 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, 3 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1465) Consider integrating jBPM Identity modulewith Security

by Gavin King (JIRA)

Consider integrating jBPM Identity modulewith Security ------------------------------------------------------- Key: JBSEAM-1465 URL: http://jira.jboss.com/jira/browse/JBSEAM-1465 Project: JBoss Seam Issue Type: Feature Request Components: BPM, Security Reporter: Gavin King Assigned To: Gavin King Fix For: 1.3.0.GA Maybe we can use that as our identity model.... -- 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, 3 months

7
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1032) Integration with JBoss SSO

by Shane Bryzak (JIRA)

Integration with JBoss SSO -------------------------- Key: JBSEAM-1032 URL: http://jira.jboss.com/jira/browse/JBSEAM-1032 Project: JBoss Seam Issue Type: Feature Request Components: Security Affects Versions: 1.2.0.GA Reporter: Shane Bryzak Assigned To: Shane Bryzak We should provide integration of Seam Security with JBoss SSO. -- 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, 3 months

8
31
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2008