May 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2936) Icefaces seam-gen build scripts need to be updated for mvel.jar changes

by Jay Balunas (JIRA)

Icefaces seam-gen build scripts need to be updated for mvel.jar changes ----------------------------------------------------------------------- Key: JBSEAM-2936 URL: http://jira.jboss.com/jira/browse/JBSEAM-2936 Project: Seam Issue Type: Bug Components: ICE Faces Integration Affects Versions: 2.0.2.CR2 Reporter: Jay Balunas Assigned To: judy guglielmin Fix For: 2.0.2.GA Attachments: icefaces-access-error-server.log Icefaces seam-gen ear application is showing a seam debug/error page. See the attached file for full stack trace. The error's root cause appears to be: "NoClassDefFoundError: org/mvel/integration/impl/LocalVariableResolverFactory". Because this is similiar to an error you can get if using jars that have had testing modifications made I have have done the following (always clearing both the JBoss deployment and project for each step): - cleaned and rebuilt 2.0.2.CR2 dist then recreated project - No change - copied original 2.0.2.CR2 dist for backup then cleaned the tagged source code - cleared my .m2 cache - and rebuilt the whole dist. - recreated the icefaces app - got the same error. I also tested seam gen with EAR and WAR projects that did not use icefaces and there were no 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, 10 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2924) session dropped by exception handler redirect if using url rewriting

by Dan Allen (JIRA)

session dropped by exception handler redirect if using url rewriting -------------------------------------------------------------------- Key: JBSEAM-2924 URL: http://jira.jboss.com/jira/browse/JBSEAM-2924 Project: Seam Issue Type: Bug Components: Exception Handling Reporter: Dan Allen Assigned To: Dan Allen The ExceptionFilter works outside of the JSF FacesContext and therefore must instantiate a MockFacesContext and MockExternalContext to allow JSF messages to be appended and to issue the redirect. However, the ExternalContext does not properly implement the encodeActionURL() method (it merely returns the value passed into the method). Therefore, if url rewriting is active, the session is dropped upon redirect. The ExternalContext needs to delegate to the HttpServletRequest object if present to properly encode the url. -- 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, 10 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2897) externalize list of deployable jars in seam-gen projects

by Dan Allen (JIRA)

externalize list of deployable jars in seam-gen projects -------------------------------------------------------- Key: JBSEAM-2897 URL: http://jira.jboss.com/jira/browse/JBSEAM-2897 Project: Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.1.0.A1, 2.0.2.CR1, 2.0.1.GA Reporter: Dan Allen Assigned To: Dan Allen Priority: Minor Fix For: 2.0.2.CR2, 2.1.0.BETA1 Adding a new JAR to be included a seam-gen project deployment is a huge pain. You have to dive down into the middle of the build.xml file and find the inclusion list nested within the copy-libs target. Try explaining that to a newbie. Despite plans to redesign the dependency mechanism in seam-gen projects, I think it is important to fix the smaller issue at hand. Let's externalize the list of deployed jars and use <includesfile name="deployed-jars.list"/> to include them. -- 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, 10 months

2
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2895) Callout bugs for Seam Framework docbooks

by Cheyenne Weaver (JIRA)

Callout bugs for Seam Framework docbooks ---------------------------------------- Key: JBSEAM-2895 URL: http://jira.jboss.com/jira/browse/JBSEAM-2895 Project: Seam Issue Type: Task Reporter: Cheyenne Weaver Assigned To: Cheyenne Weaver Create callout bugs for Seam Framework community documentation support in .svg, .png, .gif, from master .ai file Working with Pete Muir and Mark Newton -- 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, 10 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2888) Calling Session.invalidate() leads to an explosion of new sessions

by Dan Allen (JIRA)

Calling Session.invalidate() leads to an explosion of new sessions ------------------------------------------------------------------ Key: JBSEAM-2888 URL: http://jira.jboss.com/jira/browse/JBSEAM-2888 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.0.A1, 2.0.2.CR1, 2.0.1.GA Reporter: Dan Allen There appears to be a pretty nasty bug in Seam during the post-session invalidation routine. If you call #{session.invalidate} (which is also called by #{identity.logout}) a new session is created each time the conversation is referenced for the duration of the request. To observe this behavior, install an HttpSessionListener that watches for session creation. Then run one of these two action listener methods. You will observe the many hits to the sessionCreated() method during the request that terminates the session with Session.invalidate(). public class SessionNotifier implements HttpSessionListener { public void sessionCreated(HttpSessionEvent e) { System.out.println("created session with id: " + e.getSession().getId()); } public void sessionDestroyed(HttpSessionEvent e) {} } You can run Thread.dumpStack() in the listener to see that it is happening as a result of attribute reads on the ServerConversationContext. I guess because the session was invalidated, Seam attempts to recreate the session over and over as it works with the conversation within that request. I consider this a pretty serious bug because it leads to significant growth of the HTTP session. -- 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, 10 months

3
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2817) Chinese translation of 2.0.0.GA docs

by Pete Muir (JIRA)

Chinese translation of 2.0.0.GA docs ------------------------------------ Key: JBSEAM-2817 URL: http://jira.jboss.com/jira/browse/JBSEAM-2817 Project: JBoss Seam Issue Type: Task Components: Documentation Translation Reporter: Pete Muir Assigned To: Jay Balunas -- 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, 10 months

2
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2784) Backport of Alex's code about portlet support (From 2.1.0.A1)

by Thomas Heute (JIRA)

Backport of Alex's code about portlet support (From 2.1.0.A1) ------------------------------------------------------------- Key: JBSEAM-2784 URL: http://jira.jboss.com/jira/browse/JBSEAM-2784 Project: JBoss Seam Issue Type: Feature Request Components: Portal Reporter: Thomas Heute Assigned To: Pete Muir Priority: Blocker As per our discussion, we would like to have the JBoss Portlet Bridge being able to work with Seam 2.0.2.GA. Hopefully you know what's needed to be backported. Thanks ! -- 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, 10 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2837) JBDS EAR project unit test failed because it was missing core.jar

by Jay Balunas (JIRA)

JBDS EAR project unit test failed because it was missing core.jar ----------------------------------------------------------------- Key: JBSEAM-2837 URL: http://jira.jboss.com/jira/browse/JBSEAM-2837 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 2.0.2.CR1 Environment: JBDS 1.0 Reporter: Jay Balunas Priority: Minor Fix For: 2.0.2.CR2 Using JBDS 1.0 I added Seam 2.0 runtime (using 2.0.2.CR1) and created an EAR project following the instructions in the release-process.txt. When running the testNG unit tests it throws NoClassDefFoundError on a class from the "seam/lib/core.jar" file. After adding it to the build path of the project I was able to move beyond this 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, 10 months

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

17 years, 10 months

2
4
0 / 0

[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

17 years, 10 months

3
11
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 May 2008