February 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-796) Seam does not recognise the @Role annotation when the component is loaded via xml rather than scanning

by Mike Quilleash (JIRA)

Seam does not recognise the @Role annotation when the component is loaded via xml rather than scanning ------------------------------------------------------------------------------------------------------ Key: JBSEAM-796 URL: http://jira.jboss.com/jira/browse/JBSEAM-796 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.1.0.GA Environment: Any Reporter: Mike Quilleash The @Role and @Roles annotations are checked in Initialization.installScannedComponentAndRoles() which is not called when components are specified in components.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

16 years, 5 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1977) Add reflection bytecode optimization in JBoss EL

by Mikhail Grushinskiy (JIRA)

Add reflection bytecode optimization in JBoss EL ------------------------------------------------ Key: JBSEAM-1977 URL: http://jira.jboss.com/jira/browse/JBSEAM-1977 Project: JBoss Seam Issue Type: Feature Request Reporter: Mikhail Grushinskiy Add reflection bytecode optimization in JBoss EL. It could be done optional (as in Hibernate) Even on JDK 5 cglib FastClass performs reflection calls faster. EL is used heavily during render phase and it is critical that it is optimized for performance. -- 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, 5 months

4
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2475) @Remove method called instead of @Destroy.

by Sanne Grinovero (JIRA)

@Remove method called instead of @Destroy. ------------------------------------------ Key: JBSEAM-2475 URL: http://jira.jboss.com/jira/browse/JBSEAM-2475 Project: JBoss Seam Issue Type: Bug Environment: N/A Reporter: Sanne Grinovero After some discussions at http://www.jboss.com/index.html?module=bb&op=viewtopic&t=127257 Pete Muir gets interested and discovers that, in lack of a @Destroy method, a @Remove could be called. That looks terribly wrong. Also, the JBoss Tools shows an error at the presence of multiple methods annotated as @Remove; that's another problem but it could depend on this one. -- 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, 5 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1226) Ability to upload ZIP/JAR archives with automatic unarchiving

by Christian Bauer (JIRA)

Ability to upload ZIP/JAR archives with automatic unarchiving ------------------------------------------------------------- Key: JBSEAM-1226 URL: http://jira.jboss.com/jira/browse/JBSEAM-1226 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Priority: Minor I'd like to be able to upload a ZIP with pictures and have it uncompressed and unarchived into a new directory with the name of the archive. Or a bunch of docbook.xml files that are rendered as documents in a new directory. This feature probably needs some abstraction of file handling (better than the little hashmap we have right now). -- 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, 5 months

1
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1526) Support selective validation with a:region

by Christian Bauer (JIRA)

Support selective validation with a:region ------------------------------------------ Key: JBSEAM-1526 URL: http://jira.jboss.com/jira/browse/JBSEAM-1526 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Christian Bauer In complex forms I'd like to be able to customize validation per region: <h:form> <a:region> <h:inputText value="#{foo.bar}"/> <a:region> <h:inputText value="#{bar.foo}"/> <a:commandButton action="#{bar.baz}"/> </a> <a:commandButton action="#{foo.baz}"/> </a> </h:form> If the nested button is pressed, I only want #{bar.foo} validated (there is an <s:validateAll> around it). If the outer button is pressed, I want both properties validated. I realize that this is a major issue regarding model updates, however, I don't need to update the model for any non-validated property because a) it is not decoded on the server anyway (? I don't understand the a:region docs) b) i don't need an updated model because my action doesn't expect it c) i don't need an updated model because i am re-rendering an area that doesn't expect it -- 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, 6 months

5
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2325) ejb3/seam-gwt-remoting/gwt security integration

by darren hartford (JIRA)

ejb3/seam-gwt-remoting/gwt security integration ----------------------------------------------- Key: JBSEAM-2325 URL: http://jira.jboss.com/jira/browse/JBSEAM-2325 Project: JBoss Seam Issue Type: Task Components: Remoting, Security Affects Versions: 2.0.0.GA Environment: jboss 4.2.1 seam 2.0.0.GA win2k Any security-domain will work with name 'SpringPoweredRealm' with a user having 'security_role' role. Reporter: darren hartford Assigned To: Shane Bryzak Attachments: ejb3-gwt-security-sample.zip Attached is a sample project showing a problem related to Seam-GWT-Remoting integration with a GWT app, and security integration challenge. Error is detailed in forum link, top level server-side error is "[[/sample-ejb3-gwt-client]] Exception while dispatching incoming RPC call org.jboss.seam.security.NotLoggedInException " Not sure what integration method would be the best approach for secured methods for Seam-GWT-Remoting on the server side to the GWT client side. Expectations: *Once logged into web application, use of secured method/services to succeed automatically with appropriate roles without additional login (role based security assumed with Seam @Restrict annotation). *Once logged into web application, use of secured method/services to fail for insufficient role authorization, with sufficient information to determine it was a security failure instead of a service failure. *Anonymous web application login with a GWT widget requesting a secured Seam Remoting service/method would require either re-routing to web-app login page, or login to ONLY use the requested secured Seam service/method. This could be managed with GWT code to meet this expectation. thanks, learning as best as I can with available documentation. Permission given under LGPL license to use as an example in future documentation/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, 6 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2062) Consider changing s:link default to propagation=none

by Stuart Douglas (JIRA)

Consider changing s:link default to propagation=none ---------------------------------------------------- Key: JBSEAM-2062 URL: http://jira.jboss.com/jira/browse/JBSEAM-2062 Project: JBoss Seam Issue Type: Feature Request Reporter: Stuart Douglas Priority: Minor the reason to consider this change is that foo?cid=123 links are confusing for search engine crawlers. -- 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, 6 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2390) fileUpload doesn't work with Trinidad

by Robert Morse (JIRA)

fileUpload doesn't work with Trinidad ------------------------------------- Key: JBSEAM-2390 URL: http://jira.jboss.com/jira/browse/JBSEAM-2390 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.1.CR1, 2.0.0.GA Environment: Mac OS X 10.5, Java 1.5 Reporter: Robert Morse fileUpload stops working when Trinidad is integrated with a project. See: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=120188&postdays=... for further details and discussion. -- 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, 6 months

5
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1052) seam-dev.properties, seam-prod.properties

by Pete Muir (JIRA)

seam-dev.properties, seam-prod.properties ----------------------------------------- Key: JBSEAM-1052 URL: http://jira.jboss.com/jira/browse/JBSEAM-1052 Project: JBoss Seam Issue Type: Feature Request Components: Tools Affects Versions: 1.2.0.GA Reporter: Pete Muir Priority: Optional In the same way you have persistence-dev.xml, there should be seam-dev.properties to allow you to configure your application differently when in dev/prod (e.g. disable random password generation). AFAICS seam.properties must be in WEB-INF/classes/seam.properties for it to be read (it isn't read in ejb-jar/seam.properties as it's not in the classloader) -- 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, 6 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2662) Map Spring transaction status codes back to JTA status codes in SpringTransaction.JtaSpringSynchronizationAdapter

by Michael Youngstrom (JIRA)

Map Spring transaction status codes back to JTA status codes in SpringTransaction.JtaSpringSynchronizationAdapter ----------------------------------------------------------------------------------------------------------------- Key: JBSEAM-2662 URL: http://jira.jboss.com/jira/browse/JBSEAM-2662 Project: JBoss Seam Issue Type: Bug Components: Spring Affects Versions: 2.1.0.A1 Reporter: Michael Youngstrom Assigned To: Michael Youngstrom Fix For: 2.1.x SpringTransaction.JtaSpringSynchronizationAdapter doesn't map SpringTransaction status codes back to JTA codes when adapting Spring synchronization to JTA Synchornization -- 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, 6 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 February 2008