December 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1387) Support for overriding .cfg.xml properties in HibernateFactory (patch included)

by Przemyslaw Jaskierski (JIRA)

Support for overriding .cfg.xml properties in HibernateFactory (patch included) -------------------------------------------------------------------------------- Key: JBSEAM-1387 URL: http://jira.jboss.com/jira/browse/JBSEAM-1387 Project: JBoss Seam Issue Type: Feature Request Environment: Microcontainer Reporter: Przemyslaw Jaskierski Fix For: 1.3.0.ALPHA Attachments: HibernateFactory-patch.diff.zip Currently HibernateFactory supports only one type of configuration at a time: .cfg.xml file or "programmatic" one passed by the cfgProperties property. It would be great to have the ability to override individual properties from the specified .cfg.xml file using cfgProperties property. For example, when you want to have special value for hibernate.hbm2ddl.auto in case of tests only, and normal one in case of production environment. Applying my patch makes the following thing possible (instead of maintaing two almost identicall hibernate.cfg.xml files): <bean name="pecpHibernateSessionFactoryFactory" class="pecp.core.seam.HibernateFactory"> <property name="cfgResourceName"> <inject bean="pecpHibernateConfigurationLocation"/> </property> <property name="namingStrategy"> <inject bean="underscoreAwareNamingStrategy"/> </property> <property name="cfgProperties"> <map class="java.util.Hashtable" keyClass="java.lang.String" valueClass="java.lang.String"> <entry> <key>hibernate.hbm2ddl.auto</key> <value>create-drop</value> </entry> </map> </property> </bean> I've kept original logical code flow intact, so when there is no cfgResourceName and no cfgProperties set, Seam (as in original case) tries to call configuration.configure() and try to configure from hibernate.cfg.xml file. To make override functionality work you need to specify cfgResourceName property. -- 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

15 years, 11 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1961) ConversationEntry.isCurrent returns incorrect value when the ConversationEntry represents a temporary conversation

by Chris Rudd (JIRA)

ConversationEntry.isCurrent returns incorrect value when the ConversationEntry represents a temporary conversation ------------------------------------------------------------------------------------------------------------------ Key: JBSEAM-1961 URL: http://jira.jboss.com/jira/browse/JBSEAM-1961 Project: JBoss Seam Issue Type: Bug Reporter: Chris Rudd ConversationEntry.isCurrent always returns false for the CE that represents the current conversaion if that conversation is not long running. This was discovered when attempting to to work around JBSEAM-1901. I would expect the CE to return true if it represents the current conversation reguarless of the longRunning/temporary state of the conversation. -- 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

15 years, 11 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2321) only generate-entities creates views that begin with uppercase

by Dan Allen (JIRA)

only generate-entities creates views that begin with uppercase -------------------------------------------------------------- Key: JBSEAM-2321 URL: http://jira.jboss.com/jira/browse/JBSEAM-2321 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 2.0.0.GA Reporter: Dan Allen Fix For: 2.0.x This is a blaring bug that has someone been overlooked up until now. The generate-entities command (now generate-ui) creates pages using the naming pattern FooBar.xhtml whereas all of the other commands use the naming pattern fooBar.xhtml. We should definitely bring generate-entities in line with the rest of the crowd. It is very unconventional to start pages with uppercase characters (going by experience) -- 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

15 years, 11 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2431) Finish of StyleResource

by Pete Muir (JIRA)

Finish of StyleResource ----------------------- Key: JBSEAM-2431 URL: http://jira.jboss.com/jira/browse/JBSEAM-2431 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 2.0.1.CR1 Reporter: Pete Muir Assigned To: Pete Muir Priority: Minor Fix For: 2.0.x Split out the id prefixing stuff and merge back into wiki. Document the style resource stuff. -- 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

15 years, 11 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2250) Listing returns no records found if current page number is higher than expected results

by Terry (JIRA)

Listing returns no records found if current page number is higher than expected results --------------------------------------------------------------------------------------- Key: JBSEAM-2250 URL: http://jira.jboss.com/jira/browse/JBSEAM-2250 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.1.GA Environment: Win XP, JDK 6, JBoss AS 4.2.2. Reporter: Terry Priority: Minor When browsing search results based on EntityQuery, and current results page number is higher than results based on further search criteria entered. Then seam returns no records found. See Forum issue for further details. -- 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

15 years, 11 months

2
3
0 / 0

[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

15 years, 11 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

15 years, 11 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

15 years, 11 months

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

15 years, 11 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

15 years, 11 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2007