June 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1678) @Begin(flushMode=MANUAL) takes effect AFTER method call instead of before it.

by Frits Jalvingh (JIRA)

@Begin(flushMode=MANUAL) takes effect AFTER method call instead of before it. ----------------------------------------------------------------------------- Key: JBSEAM-1678 URL: http://jira.jboss.com/jira/browse/JBSEAM-1678 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.BETA1 Environment: J2SE 1.5, Tomcat 6.0.10, Hibernate 3.2.3, HibEM 3.3.1 Reporter: Frits Jalvingh (See also the end of thead at http://jboss.com/index.html?module=bb&op=viewtopic&p=4064502#4064502) I have a method marked: @Begin(flushMode=FlushModeType.MANUAL) public String createNewTarget() This method is meant as the start of a 2-screen conversation. This conversation should be rolled back if a user presses cancel so flushmode=MANUAL is used to prevent the persistence context from flushing db changes. The method starts by creating a new entity and persist()s it. The problem is that this causes an immediate "insert" by Hibernate regardless of the flushmode. I debugged the code and found that the flushmode gets set AFTER Seam calls the method, not before (ConversationInterceptor). This seems to be wrong, so I placed an extra call to set the mode in aroundInvoke(): setFlushMode(method); // JAL FlushMode should be set BEFORE we call the method!? Object result = invocation.proceed(); beginConversationIfNecessary(method, result); endConversationIfNecessary(method, result); return result; (flushMode in the original code is set in beginConversation()). This at least fixes part of the problem; the other part of the problem is a bug in Hibernate where it always forces an insert even if it is not needed. I fixed that too which fixes the entire problem. -- 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
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1457) ui example doesnt work in tomcat 5.5.23

by Bieth Bruno (JIRA)

ui example doesnt work in tomcat 5.5.23 --------------------------------------- Key: JBSEAM-1457 URL: http://jira.jboss.com/jira/browse/JBSEAM-1457 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.2.1.GA Environment: Tomcat 5.5.23 Reporter: Bieth Bruno Can't run the ui example with tomcat 5.5.23 : After clicking one of the link on the main page I get : 15:10:49,124 ERROR [ExceptionFilter] could not roll back transaction javax.naming.NamingException: Local server is not initialized at org.jnp.interfaces.LocalOnlyContextFactory.getInitialContext(LocalOnlyContextFactory.java:45) ... 15:10:50,265 ERROR [SeamPhaseListener] uncaught exception javax.faces.el.EvaluationException: Cannot set value for expression '#{personHome.id}' to a new valu e of type java.lang.Integer at org.apache.myfaces.el.ValueBindingImpl.setValue(ValueBindingImpl.java:310) -- 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-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-1000) Propagation of conversations with pageflow in testing environment.

by Denis Karpov (JIRA)

Propagation of conversations with pageflow in testing environment. ------------------------------------------------------------------ Key: JBSEAM-1000 URL: http://jira.jboss.com/jira/browse/JBSEAM-1000 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.0.GA Environment: windows 2000 jboss-4.0.5.GA Reporter: Denis Karpov I think there is bug in testing environment (propagation of conversations with pageflow does not work) In this test there is 2 requests . In the first I start conversation and pageflow In the second conversation is lost. If I do not start pageflow then conversation propagates. Code: public class TOrdTest extends SeamTest{ private static final Log log = LogFactory.getLog( TOrdTest.class ); @Test public void Test1() throws Exception { String id = new FacesRequest(){ @Override protected void invokeApplication() throws Exception { Conversation.instance().begin(); Pageflow.instance().begin("val_buy"); // uses start-state setOutcome("browse"); log.info("##### 1 Conversation_ID "+ Conversation.instance().getId()); assert isLongRunningConversation(); } @Override protected void renderResponse() throws Exception { } }.run(); id = new FacesRequest("/exchange/buy_readonly.xhtml",id){ @Override protected void beforeRequest() { log.info("#####beforeRequest Conversation_ID "+ getConversationId()); } @Override protected void applyRequestValues() throws Exception { log.info("##### 2 Conversation_ID "+ Conversation.instance().getId()+" "+getConversationId()); } @Override protected void invokeApplication() throws Exception { //Conversation.instance().beginNested(); log.info("##### 3 Conversation_ID "+ Conversation.instance().getId()+" "+getConversationId()); assert isLongRunningConversation(); } }.run(); } } -- 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-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-3036) xstream*.jar needed for Drools is missing from Seam distribution package.

by Earl Baugh (JIRA)

xstream*.jar needed for Drools is missing from Seam distribution package. ------------------------------------------------------------------------- Key: JBSEAM-3036 URL: http://jira.jboss.com/jira/browse/JBSEAM-3036 Project: Seam Issue Type: Patch Components: Drools Affects Versions: 2.0.2.GA, 2.0.2.CR1, 2.0.1.GA Reporter: Earl Baugh Priority: Minor The xstream*.jar file that is part of the Drools package has been omitted from the Seam distribution. It's fairly trivial to hit a class not found error when using Drools in the Seam environment because of 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

17 years, 8 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3007) no error message when component cannot be properly created on startup

by Sebastian Hennebrueder (JIRA)

no error message when component cannot be properly created on startup --------------------------------------------------------------------- Key: JBSEAM-3007 URL: http://jira.jboss.com/jira/browse/JBSEAM-3007 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.0.2.GA, 2.0.1.GA Environment: Mac OSX JDK 1.5 Tomcat 6 Reporter: Sebastian Hennebrueder When a component implements an interface which is not deployed to the application server, the component is not created but silently ignored. At least an error message during startup would be fine. I run into this problem when using Groovy components. When the groovy classes are compiled to java classes they implement a groovy interface. If I do not deploy the groovy jars, the component is not loaded. I reproduced the problem with a class implementing an interface. The interface was part of a jar which was only available at compile time but not deployed to Tomcat. Same problem happens on JBoss 4.2.2 -- 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
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2985) Page param with Exception paages.

by Tom Goring (JIRA)

Page param with Exception paages. --------------------------------- Key: JBSEAM-2985 URL: http://jira.jboss.com/jira/browse/JBSEAM-2985 Project: Seam Issue Type: Bug Affects Versions: 2.0.1.CR2 Environment: NA Reporter: Tom Goring Page Parameters in exception pages cause seam to stack trace. Work around is not not include a page param and use some other way. Bit of a pain as I was holding state in a param global to my site but it broke my exceptions pages. Easy to reproduce : http://www.seamframework.org/Community/BugInExceptionHandling. Or: 1) Create a excepetion page /error.xhtml 2) Add a error.page.xml to define a page param 3) in pages.xml map NullPtr to that page 4) thro a nullptr somewhere -- 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
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2984) end-conversation must be in pages.xml exception element for it to function properly

by Matthew Lieder (JIRA)

end-conversation must be in pages.xml exception element for it to function properly ----------------------------------------------------------------------------------- Key: JBSEAM-2984 URL: http://jira.jboss.com/jira/browse/JBSEAM-2984 Project: Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.0.1.GA Environment: Java 1.5, Tomcat 5.5 Reporter: Matthew Lieder If there is no end-conversation element inside the exception element in the pages.xml file, if an exception is thrown in a jPDL pageflow page transition action I get hundreds of KB of stack traces in my log all saying "pageflow has not yet started" and no error message is shown on my error page. If I do put that in however, everything works great. -- 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
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2882) Hard dependency on org.hibernate.ejb.event.EntityCallbackHandler just added (non-JPA environment)

by Przemyslaw Jaskierski (JIRA)

Hard dependency on org.hibernate.ejb.event.EntityCallbackHandler just added (non-JPA environment) ------------------------------------------------------------------------------------------------- Key: JBSEAM-2882 URL: http://jira.jboss.com/jira/browse/JBSEAM-2882 Project: Seam Issue Type: Bug Environment: Pure Tomcat + Hibernate (no JPA), Seeam 2.1 nightly 08/04/12 Reporter: Przemyslaw Jaskierski Fix For: 2.1.0.BETA1 I've just checked out fresh Seam 2.1 snapshot and apparently someone added direct dependency to Hibernate PersistenceManger. +- 10 days ago no such dependency existed. Apr 12, 2008 4:43:08 PM org.apache.catalina.core.StandardContext listenerStart SEVERE: Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener java.lang.RuntimeException: Could not create Component: org.jboss.seam.persistence.hibernatePersistenceProvider at org.jboss.seam.init.Initialization.addComponent(Initialization.java:1008) at org.jboss.seam.init.Initialization.installComponents(Initialization.java:924) at org.jboss.seam.init.Initialization.init(Initialization.java:602) at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4350) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:578) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) Caused by: java.lang.NoClassDefFoundError: org/hibernate/ejb/event/EntityCallbackHandler at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2427) at java.lang.Class.getDeclaredMethods(Class.java:1791) at org.jboss.seam.Component.initMembers(Component.java:542) at org.jboss.seam.Component.<init>(Component.java:258) at org.jboss.seam.Component.<init>(Component.java:219) at org.jboss.seam.init.Initialization.addComponent(Initialization.java:992) ... 18 more Caused by: java.lang.ClassNotFoundException: org.hibernate.ejb.event.EntityCallbackHandler at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) ... 25 more -- 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
2
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 June 2008