June 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2863) EntityStore assumes entity manager is named "entityManager"

by Clint Popetz (JIRA)

EntityStore assumes entity manager is named "entityManager" ----------------------------------------------------------- Key: JBSEAM-2863 URL: http://jira.jboss.com/jira/browse/JBSEAM-2863 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.2.CR1 Reporter: Clint Popetz EntityStore is returning a hardcoded string for the name of the persistenceContext component, which is making s:convertEntities fail for SMPCs that aren't named "entityManager," and the documented way to handle this: <component name="org.jboss.seam.ui.EntityConverter"> <property name="entityManager">#{yourEM}</property> </component> is no longer sufficient. -- 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, 7 months

3
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2838) JBDS EAR project unit test fails with IllegalStateException: could not locate rule file: /security.drl

by Jay Balunas (JIRA)

JBDS EAR project unit test fails with IllegalStateException: could not locate rule file: /security.drl ------------------------------------------------------------------------------------------------------ Key: JBSEAM-2838 URL: http://jira.jboss.com/jira/browse/JBSEAM-2838 Project: JBoss Seam Issue Type: Bug Components: Test Harness, Tools Affects Versions: 2.0.2.CR1 Environment: JBDS Reporter: Jay Balunas Priority: Minor Fix For: 2.0.2.CR2 After fixing JBSEAM-2837. With JBDS 1.0 set up with Seam 2.0.2.CR1 the unit tests for the EAR project fail with the error below. These test were for new-form and a new-action tests. [Parser] Running: /jboss/projects/workspace/jbdsEar-test/temp-testng-customsuite.xml WARN [org.jboss.seam.init.Initialization] Did not install PojoCache due to NoClassDefFoundError: org/jgroups/MembershipListener INFO [org.ajax4jsf.cache.CacheManager] Selected [org.ajax4jsf.cache.LRUMapCacheFactory] cache factory INFO [org.ajax4jsf.cache.LRUMapCacheFactory] Creating LRUMap cache instance using parameters: {} INFO [org.ajax4jsf.cache.LRUMapCacheFactory] Creating LRUMap cache instance of default capacity INFO [org.ajax4jsf.cache.CacheManager] Selected [org.ajax4jsf.cache.LRUMapCacheFactory] cache factory INFO [org.ajax4jsf.cache.LRUMapCacheFactory] Creating LRUMap cache instance using parameters: {} INFO [org.ajax4jsf.cache.LRUMapCacheFactory] Creating LRUMap cache instance of default capacity FAILED CONFIGURATION: @BeforeMethod begin org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.security.identity at org.jboss.seam.Component.newInstance(Component.java:1970) at org.jboss.seam.contexts.Contexts.startup(Contexts.java:304) at org.jboss.seam.contexts.Contexts.startup(Contexts.java:278) at org.jboss.seam.contexts.Lifecycle.beginSession(Lifecycle.java:191) at org.jboss.seam.contexts.ServletLifecycle.beginSession(ServletLifecycle.java:124) at org.jboss.seam.mock.BaseSeamTest.begin(BaseSeamTest.java:912) at org.jboss.seam.mock.SeamTest.begin(SeamTest.java:28) Caused by: java.lang.IllegalStateException: could not locate rule file: /security.drl at org.jboss.seam.drools.RuleBase.compileRuleBase(RuleBase.java:51) at org.jboss.seam.util.Reflections.invoke(Reflections.java:21) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:125) at org.jboss.seam.Component.callComponentMethod(Component.java:2082) at org.jboss.seam.Component.callCreateMethod(Component.java:2005) at org.jboss.seam.Component.newInstance(Component.java:1976) at org.jboss.seam.Component.getInstance(Component.java:1873) at org.jboss.seam.Component.getInstance(Component.java:1840) at org.jboss.seam.Namespace.getComponentInstance(Namespace.java:55) at org.jboss.seam.Namespace.getComponentInstance(Namespace.java:50) at org.jboss.seam.el.SeamELResolver.resolveBase(SeamELResolver.java:166) at org.jboss.seam.el.SeamELResolver.getValue(SeamELResolver.java:53) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) at org.jboss.el.parser.AstIdentifier.getValue(AstIdentifier.java:44) at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) at org.jboss.seam.core.Expressions$1.getValue(Expressions.java:111) at org.jboss.seam.Component$ELInitialValue.getValue(Component.java:2360) at org.jboss.seam.Component.initialize(Component.java:1389) at org.jboss.seam.Component.instantiateJavaBean(Component.java:1315) at org.jboss.seam.Component.instantiate(Component.java:1268) at org.jboss.seam.Component.newInstance(Component.java:1966) ... 30 more ... Removed 28 stack frames SKIPPED CONFIGURATION: @AfterMethod end SKIPPED CONFIGURATION: @AfterClass cleanup SKIPPED: test =============================================== org.domain.jbdsEar.test.HelloTest Tests run: 1, Failures: 0, Skips: 1 Configuration Failures: 1, Skips: 2 =============================================== =============================================== jbdsEar-test Total tests run: 1, Failures: 0, Skips: 1 Configuration Failures: 1, Skips: 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

16 years, 7 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2758) Update WebSphere chapter with a note about Seam specific EJB's

by Jay Balunas (JIRA)

Update WebSphere chapter with a note about Seam specific EJB's -------------------------------------------------------------- Key: JBSEAM-2758 URL: http://jira.jboss.com/jira/browse/JBSEAM-2758 Project: JBoss Seam Issue Type: Bug Components: Documentation Issues, Platform interoperability Affects Versions: 2.1.0.A1, 2.0.1.GA Reporter: Jay Balunas Assigned To: Jay Balunas Priority: Minor See comment on websphere blog for more details. http://in.relation.to/Bloggers/WebSphereRunningSeamsJEE5BookingExample#co... Basically just differentiate Seam internal EJBs from example EJBs so that users know that they are needed in any of there apps - not just the 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, 7 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2720) expose overrideable createRequest() and createResponse() methods in AbstractSeamTest.Request

by Matt Drees (JIRA)

expose overrideable createRequest() and createResponse() methods in AbstractSeamTest.Request -------------------------------------------------------------------------------------------- Key: JBSEAM-2720 URL: http://jira.jboss.com/jira/browse/JBSEAM-2720 Project: JBoss Seam Issue Type: Feature Request Components: Test Harness Reporter: Matt Drees Priority: Minor There are times when I'd like to substitute my own HttpServletResponse implementation in a SeamTest request. I might do this if I want to allow getOutputStream() to return a real output stream, so I can test actions that directly write to it (excel document generation, for example). It'd be handy if AbstractSeamTest made it convenient for me to do this; right now I'm relying on reflection tricks to get & set the private field. -- 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, 7 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2482) Possible work around for Weblogic "varargs" EJB issue

by Jay Balunas (JIRA)

Possible work around for Weblogic "varargs" EJB issue ----------------------------------------------------- Key: JBSEAM-2482 URL: http://jira.jboss.com/jira/browse/JBSEAM-2482 Project: JBoss Seam Issue Type: Task Components: Documentation, Examples Affects Versions: 2.0.1.CR1 Reporter: Jay Balunas Priority: Minor Attachments: full-stack-of-ejb-transient-error.txt There is a know issue with weblogic and support for EJBs that use variable arguments. This is documented in the reference guide for more details. I've attached the full stack trace from the console. The main errors revolve around EJB3 timers - there may be a way to disable timers through the weblogic.xml deployment descriptor, or perhaps a different file. There are other warnings around EJB synchronization, but they may still function. If solved the reference docs should be updated. -- 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, 7 months

3
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2657) Seam-mail fails when invoked from custom servlet bound with web:context-filter

by Przemyslaw Jaskierski (JIRA)

Seam-mail fails when invoked from custom servlet bound with web:context-filter ------------------------------------------------------------------------------ Key: JBSEAM-2657 URL: http://jira.jboss.com/jira/browse/JBSEAM-2657 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.0.1.GA Environment: Seam 2.0.1 and 2.0.2-SNAPSHOT from 13 feb 2008, plain Tomcat 6.0, JSF RI 1.2_07. Reporter: Przemyslaw Jaskierski (Reporting as FR as requested by Pete. Please, read linked thread for the full context). I try to send an email from one of services. The same code: renderer.render(/WEB-INF/emailTemplates/test.xhtml); invoked from application-scoped component with method annotated as @Observer(foo) 1. works when a synchronous event is invoked in JSF action using Events.instance().raiseEvent(foo) 2. fails when invoked using Events.instance().raiseAsynchronousEvent(foo) from the same JSF action 3. fails when invoked as both synchronous and asynchronous events from custom servlet bound with web:context-filter. Case 2. and 3. both lead to this exception: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.application.ApplicationFactory at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:267) at org.jboss.seam.mock.MockFacesContext.<init>(MockFacesContext.java:60) at org.jboss.seam.ui.facelet.FaceletsRenderer$RenderingContext.init(FaceletsRenderer.java:95) at org.jboss.seam.ui.facelet.FaceletsRenderer$RenderingContext.run(FaceletsRenderer.java:77) at org.jboss.seam.ui.facelet.FaceletsRenderer.render(FaceletsRenderer.java:169) Pete's response: (2) is untested and I wouldn't necessarily expect (3) to work. File a JIRA feature request for (3) please - but it will require some redesign on how we render mails (hopefully make it much more robust) -- 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, 7 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2491) Seam is still using Groovy 1.1 beta, Groovy 1.5 has been released

by Marcus Adair (JIRA)

Seam is still using Groovy 1.1 beta, Groovy 1.5 has been released ----------------------------------------------------------------- Key: JBSEAM-2491 URL: http://jira.jboss.com/jira/browse/JBSEAM-2491 Project: JBoss Seam Issue Type: Bug Components: Build Affects Versions: 2.0.1.CR1 Reporter: Marcus Adair According to the groovy-all.jar/META-INF/MANIFEST.MF file, Groovy 1.1 beta is still be used. 1.5 was released in 12/2007 and appears to solve some gotchas related to its use with Seam. See: http://docs.codehaus.org/display/GROOVY/2007/12/07/Groovy+1.5+released -- 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, 7 months

3
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2319) searchparents="true" required to properly detect Groovy in build

by Dan Allen (JIRA)

searchparents="true" required to properly detect Groovy in build ---------------------------------------------------------------- Key: JBSEAM-2319 URL: http://jira.jboss.com/jira/browse/JBSEAM-2319 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 2.0.0.GA Reporter: Dan Allen Priority: Minor Fix For: 2.0.x Attachments: JBSEAM-2319-v1.txt If you are using Ant >= 1.7.0, the check to determine if there are Groovy files present on the classpath will not work unless the attribute searchparents="true" is added to the <available> element that performs the check. This is an API change in Ant. Unfortunately, this attribute is not present in earlier versions of Ant and therefore throws an error. Can we just require Ant 1.7.0 or is there some way to work around an attribute that an older version of Ant does not recognize? Here is the check:  <available property="groovy.present" value="true" file="" searchparents="true"> <filepath> <fileset dir="${src.action.dir}"> <include name="**/*.groovy"/> </fileset> </filepath> </available> -- 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, 7 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2266) WLS doesn't support Servlet 2.5

by Pete Muir (JIRA)

WLS doesn't support Servlet 2.5 ------------------------------- Key: JBSEAM-2266 URL: http://jira.jboss.com/jira/browse/JBSEAM-2266 Project: JBoss Seam Issue Type: Task Components: Examples Affects Versions: 2.0.0.GA Reporter: Pete Muir Priority: Minor Fix For: 2.0.2.GA web.xml references 2.5, but WLS only supports servlet 2.4 (but examples still seem to 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, 7 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2408) Icefases inputFile breaks seam application, EJB's will remain associated with another transaction and cannot be reloaded from backupstore

by Indrek Altpere (JIRA)

Icefases inputFile breaks seam application, EJB's will remain associated with another transaction and cannot be reloaded from backupstore ----------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-2408 URL: http://jira.jboss.com/jira/browse/JBSEAM-2408 Project: JBoss Seam Issue Type: Bug Components: EJB3, ICE Faces Integration Affects Versions: 2.0.0.GA Environment: on Glassfish server Reporter: Indrek Altpere Priority: Blocker When turning on seams's ejb transaction with <transaction:ejb-transaction /> icefaces file upload fails. When I try to render the outputprogress in upload's progress listeners, I get exception right away NRU-org.jboss.seam.transaction.EjbSynchronizations: Cannot load from BACKUPSTORE FOR Key: <3e90c03b00a81f-ffffffffd01e540c-1> EJB5018: An exception was thrown during an ejb invocation on [EjbSynchronizations] javax.ejb.NoSuchObjectLocalException: The EJB does not exist. session-key: 3e90c03b00a81f-ffffffffd01e540c-1 and in the end there is exception: Caused by: javax.el.ELException: /inputfile.xhtml @22,93 value="File Name: #{inputFileBackerBean.fileName}": javax.ejb.EJBException: nested exception is: java.lang.IllegalStateException: EJB is already associated with an incomplete transaction at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.java:76) at javax.faces.component.UIOutput.getValue(UIOutput.java:173) ... 82 more When I turn off the progress thing for icefaces file upload and only set actionlistener (is called when file upload completes), then after first upload, whole application becomes unusable (clicking on any seam link or trying another uploads ends up at debug page with same exceptions in server log as shown before). It seems that EJB is not stored to because some transaction is still going on, and since it is not stored, it cannot be restored from storage and the above exceptions occur. I have posted full stacktraces to icefaces forums at http://www.icefaces.org/JForum/posts/list/6613.page Icefaces used is 1.7DR#3, seam used is Seam 2.0.0GA, Glassfish is v2 (v2ur1 does not make any difference) Example ear for glassfish deployment http://www.flamebox.org/fserver/soov.ear Source http://www.flamebox.org/fserver/soovexample.rar -- 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, 7 months

3
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 June 2008