March 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1173) HibernateSessionProxy ClassCastException

by dazhu tang (JIRA)

HibernateSessionProxy ClassCastException ---------------------------------------- Key: JBSEAM-1173 URL: http://jira.jboss.com/jira/browse/JBSEAM-1173 Project: JBoss Seam Issue Type: Bug Components: Framework Affects Versions: 1.2.0.GA Reporter: dazhu tang Priority: Critical 1. i want to inject the hibernate session in seam,so i config the component.xml as follows: <core:hibernate-session-factory name="hibernateSessionFactory" /> <core:managed-hibernate-session name="session" auto-create="true" session-factory-jndi-name="java:/HibernateSessionFactory" /> 2. Inside managed Bean , i use @in to inject the Hibernate Session, but when i am using DetachedCriteria in my application DetachedCriteria criteria = DetachedCriteria.forClass(Smartform.class); criteria.getExecutableCriteria(session) i got the HibernateSessionProxy ClassCastException,i debug the application and found that seam injected HibernateSessionProxy not the real HibernateSession object . So DetachedCriteria can't work. -- 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

17 years, 8 months

2
5
0 / 0

[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

17 years, 8 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2713) Bean Annotated with @Destroy Fails on any JEE5 Certified Platform.

by Burt Prior (JIRA)

Bean Annotated with @Destroy Fails on any JEE5 Certified Platform. ------------------------------------------------------------------ Key: JBSEAM-2713 URL: http://jira.jboss.com/jira/browse/JBSEAM-2713 Project: JBoss Seam Issue Type: Bug Components: EJB3 Affects Versions: 2.1.0.A1 Environment: Any. Reporter: Burt Prior Fix For: 2.1.0.A1 Hi Seam Team, Per Gavin's suggestion and response to my post on the Seam Users Forum (http://seamframework.org/Community/Seam2JEE5CompliantWithTheTCKRequirements), I am submitting the following bug. Also, please note that I collaborated with the Apache Geronimo engineers on identifying the source of the issue and the best approach to finding a resolution as well. The following bug occurs when running the 'booking' example on the Geronimo 2.1 AS: (please see the Users Forum entry above for the stack trace). ... 11:25:05,179 ERROR OpenEJB The bean instance business method encountered a system exception: Callback methods cannot access parameters java.lang.IllegalStateException: Callback methods cannot access parameters ... The code in the 'booking' example that appears to cause the issue is: (on any Bean) ... @Destroy @Remove public void destroy() {} ... It appears that running the 'booking' (any?) Seam (2.1.0.A1) app on the Geronimo/OpenEJB (any?) JEE5 Certified container results in the stack trace and that allowing the InvocationContext to supply the parameters during a lifecycle call results in TCK failures. The Geronimo Engineers mentioned that if OpenEJB did not throw this exception in these circumstances it would fail the TCK. It appears that any bean using Seam's@Destroy annotation fails on *any* JEE5 certified platform, in our case Geronimo 2.1. We surmise, but have not verified, that this must occur on GlassFish as well. (Jboss 5 beta 4?) As a test, we removed @Destroy, and still received the error. Resolution of this error is very important to us. I have detailed stack traces of the Geronimo log should you need them, and I would be happy to help in any way to get this issue resolved quickly. Please don't hesitate to contact me with any questions. Thank you for your time, Burt Prior IT Engineer Cisco Systems, San Jose, CA bprior(a)cisco.com 408.853.4199 -- 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

17 years, 8 months

3
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2799) Overridden components with @Install(value = false) ignores precedence.

by Shane Bryzak (JIRA)

Overridden components with @Install(value = false) ignores precedence. ---------------------------------------------------------------------- Key: JBSEAM-2799 URL: http://jira.jboss.com/jira/browse/JBSEAM-2799 Project: JBoss Seam Issue Type: Bug Components: Core Reporter: Shane Bryzak Assigned To: Shane Bryzak Priority: Critical Fix For: 2.1.0.BETA1 An easy way to reproduce this - take the JpaIdentityStore as an example: @Name("org.jboss.seam.security.management.jpaIdentityStore") @Install(precedence=Install.BUILT_IN, value = false) @Scope(APPLICATION) @BypassInterceptors public class JpaIdentityStore implements IdentityStore, Serializable Overriding it with a component with a higher precedence fails: @Name("org.jboss.seam.security.management.jpaIdentityStore") @Install(precedence = Install.APPLICATION) @Scope(APPLICATION) @BypassInterceptors public class CustomJpaIdentityStore extends JpaIdentityStore With the following stack trace: java.lang.IllegalStateException: Two components with the same name and precedence: org.jboss.seam.security.management.jpaIdentityStore at org.jboss.seam.init.Initialization.addComponentDescriptor(Initialization.java:484) at org.jboss.seam.init.Initialization.installScannedComponentAndRoles(Initialization.java:755) at org.jboss.seam.init.Initialization.scanForComponents(Initialization.java:702) at org.jboss.seam.init.Initialization.init(Initialization.java:567) at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3856) -- 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

17 years, 8 months

3
5
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

17 years, 8 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

17 years, 8 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2740) Container issue - documentation migration issues

by Pete Muir (JIRA)

Container issue - documentation migration issues ------------------------------------------------ Key: JBSEAM-2740 URL: http://jira.jboss.com/jira/browse/JBSEAM-2740 Project: JBoss Seam Issue Type: Task Components: Documentation Issues Reporter: Pete Muir Assigned To: Shane Bryzak Container issue for documentation migration issues. -- 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

17 years, 8 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2771) XSL for PDF output doesn't support using callouts and code highlighting.

by Pete Muir (JIRA)

XSL for PDF output doesn't support using callouts and code highlighting. ------------------------------------------------------------------------ Key: JBSEAM-2771 URL: http://jira.jboss.com/jira/browse/JBSEAM-2771 Project: JBoss Seam Issue Type: Bug Components: Documentation Issues Affects Versions: 2.0.1.GA Reporter: Pete Muir Assigned To: Mark Newton Priority: Minor -- 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

17 years, 8 months

1
2
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

17 years, 8 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

17 years, 8 months

5
7
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 March 2008