February 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2128) annotations on components installed by default can't be overriden

by Matt Drees (JIRA)

annotations on components installed by default can't be overriden ----------------------------------------------------------------- Key: JBSEAM-2128 URL: http://jira.jboss.com/jira/browse/JBSEAM-2128 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.CR2 Reporter: Matt Drees Priority: Minor This may actually be intended; I can't tell for sure. Certain annotation shouldn't be overrideable, like @Install or @Name. But it seems to me some should ( like @Scope or @JndiName). I'll attach a test case with more comments inline. It'd be helpful if a seam dev could look it over and say "Yes, it's behaving correctly", or "Something's broken". -- 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
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1690) Errors wrapped by ServletExceptions are not logged by ExceptionFilter

by Matt Drees (JIRA)

Errors wrapped by ServletExceptions are not logged by ExceptionFilter --------------------------------------------------------------------- Key: JBSEAM-1690 URL: http://jira.jboss.com/jira/browse/JBSEAM-1690 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.BETA1 Reporter: Matt Drees Priority: Minor Errors (in particular, OutOfMemoryErrors), are not logged when they're wrapped by a servletException. ExceptionFilter.java (line 66) has this: log.error( "exception root cause", EJB.getCause(e) ); But EJB.getCause(e) returns null if e is a ServletException whose rootCause is not an Exception (like an OutOfMemoryError). -- 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
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-905) Using the debug page without exceptions

by Christian Bauer (JIRA)

Using the debug page without exceptions --------------------------------------- Key: JBSEAM-905 URL: http://jira.jboss.com/jira/browse/JBSEAM-905 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Christian Bauer Priority: Minor I'd like to call /debug.seam manually to look into my conversations. I usually don't enable it because I don't like being redirected to it from an exception. Why? It hides the URL that caused the exception and it fills my log with hundreds of lines after the exception stacktrace. -- 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
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2590) EntityQuery components hold the whole untruncated resultset if maxResults property is set and the underlying dialect does not support limits

by vargadan (JIRA)

EntityQuery components hold the whole untruncated resultset if maxResults property is set and the underlying dialect does not support limits --------------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-2590 URL: http://jira.jboss.com/jira/browse/JBSEAM-2590 Project: JBoss Seam Issue Type: Bug Components: Framework Affects Versions: 2.0.1.GA Reporter: vargadan If the dialect supports limits then query objects only hold the number of rows set by the maxResults property. So i.e. if the search results 10000 rows but the page size is 10, only 10 objects are kept. But if the dialect does not support limits (like derby) then truncation of the result list in done in EntityQuery.getResultList() which in the previous example results in the following: - 10000 objects are kept in EntityQuery.resultList - only 10 of them is displayed in one page - EntityQuery.getResultList() returns EntityQuery.resultList the sublist every time when invoked - when paginating the query is executed for every page, so there is no point in holding all the rows. It causes quite a big overhead when query components are kept in conversation scope, which is the case most of the times. If the truncation was done just after querying against the DB, there would not be such an overhead. I.e. Query.truncResultList gets invoked in EntityQuery.initResultList and EntityQuery.resultList holds only the truncated list of results. -- 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
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2524) Exceptions ending conversations

by Alessandro Lazarotti (JIRA)

Exceptions ending conversations ------------------------------- Key: JBSEAM-2524 URL: http://jira.jboss.com/jira/browse/JBSEAM-2524 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.GA Environment: Windows Vista, Jboss APPServer 4.2, InternetExplorer 7 - FireFox 2.0.0 Reporter: Alessandro Lazarotti If any exception is thrown, objects in long-running conversation are discarded. I described how to simulate this in the forum: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=127694&postdays=... -- 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
18
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2430) JNDI lookup error when injecting a stateful bean into a stateful bean in glassfish

by Richard Hoffman (JIRA)

JNDI lookup error when injecting a stateful bean into a stateful bean in glassfish ---------------------------------------------------------------------------------- Key: JBSEAM-2430 URL: http://jira.jboss.com/jira/browse/JBSEAM-2430 Project: JBoss Seam Issue Type: Bug Reporter: Richard Hoffman Per Pete's request (http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4115521#4115521) I'm making a ticket about the problem I'm facing: Using glassfish, I'm trying to inject a stateful bean into a stateful bean...instead of describing my specific app and trying to explain exactly what I'm doing and why, I figured I'd demonstrate how to duplicate my problem using the jee5/booking example provided with Seam 2: 1.) Add the following to the top of HotelSearchingAction: import org.jboss.seam.annotations.In; . . @In(create=true) private HotelBooking hotelBooking; 2.) Redeploy and run the booking app. 3.) Navigate to the Search page. You should receive a "Could not instantiate Seam component: hotelBooking" error, which is caused by: "javax.naming.NameNotFoundException: No object bound to name java:comp/env/jboss-seam-jee5/HotelBookingAction/local" Now, granted, in this particular case, there really isn't any functional reason to do this injection, but it demonstrates the same problem I'm having on my particular application (where this kind of injection makes sense). It is also worth noting that if you do the opposite injection (HotelSearching into HotelBookingAction), you have no problems. One way I found to get around this problem is to put a @Startup at the top of the HotelBookingAction bean, but I'm not sure why this is necessary. --- My theory as to what's going on is as follows...my apologies if I'm way off, heh: The page flow of the booking app is Login -> Search (which uses HotelSearchingAction) -> Book Hotel (which uses HotelBookingAction). So, HotelSearchingAction gets (instantiated?) put in the JNDI tree first, as the user progresses through the app. The problem is, when you inject HotelBookingAction into HotelSearchingAction, HotelBookingAction needs to be created when HotelSearchingAction is first used, but it hasn't been put in the JNDI tree yet, so we get a lookup error. And of course, if you put @Startup on HotelBookingAction, HotelBookingAction is now in the JNDI tree way before HotelSearchingAction needs it, so the error is gone. But again, I'm not sure why @Startup should be necessary to inject a not-yet-used stateful bean into a stateful bean. Thanks in advance to anyone who works on this ticket. :-) -- 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
4
0 / 0

[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

16 years, 5 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

16 years, 5 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

16 years, 5 months

3
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

16 years, 5 months

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