December 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3758) NoClassDefFoundError: org/jboss/seam/intercept/Proxy when Seam Component is an EJB in another module

by Andre Rodrigues (JIRA)

NoClassDefFoundError: org/jboss/seam/intercept/Proxy when Seam Component is an EJB in another module ---------------------------------------------------------------------------------------------------- Key: JBSEAM-3758 URL: https://jira.jboss.org/jira/browse/JBSEAM-3758 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.0.SP1, 2.1.0.GA Environment: JBoss AS 4.2.2, Seam 2.0.2.GA, 2.0.2.SP1, 2.1.0.GA, 2.1.0.SP1 Reporter: Andre Rodrigues I have all my backing beans in the web application (java bean components). My business logic is inside EJBs in a module which has no reference to Seam whatsoever. So, the EAR class loader has no reference to Seam classes, Seam's jar are only in my web application (WEB-INF/lib). After some debugging, I saw that seam (2.0.2.SP1) passes an Array of interfaces to the ProxyFactory class. ProxyFactory gets the ClassLoader from the first class in the array. When the first class in the array is either Proxy or Instance, everything works fine. When the EJB interface is the first element on the array (happens after a few restarts of JBoss), ProxyFactory gets its ClassLoader, the EAR ClassLoader, which, as metioned before, doesn't "know" about Seam. I think a simple solution would be change the method createProxyFactory in the Component class to the following: Set<Class> interfaces = new TreeSet<Class>(); // instead of a HashSet, to guarantee the order of the elements // so these classes the first elements on the array interfaces.add(Instance.class); interfaces.add(Proxy.class); if ( type.isSessionBean() ) { interfaces.addAll(businessInterfaces); } else { interfaces.add(HttpSessionActivationListener.class); interfaces.add(Mutable.class); } ProxyFactory factory = new ProxyFactory(); // excluding this part, which was included in 2.1.0, but didn't really solved the problem /*{ @Override protected ClassLoader getClassLoader() { return beanClass.getClassLoader(); } };*/ A full description of the problem can be found at the forum location below. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

5
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3176) HotelSearchingAction not serializable

by Kurt Stam (JIRA)

HotelSearchingAction not serializable ------------------------------------- Key: JBSEAM-3176 URL: https://jira.jboss.org/jira/browse/JBSEAM-3176 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.3.CR1, 2.0.2.GA Reporter: Kurt Stam if you cluster HotelSearchingAction, in it hotels is not serializable, as the List.subList is not serializable. hotels = results.subList(0,pageSize); 13:03:00,270 ERROR [JBossCacheService] externalizeSession(): exception occurred externalizing session SessionBasedClusteredSession[id: cKrhNBCSg5KciOdaAiMQCA**.server2 lastAccessedTime: 1216227772088 version: 6 lastOutdated: 0] java.io.NotSerializableException: java.util.RandomAccessSubList at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302) at org.jboss.seam.jsf.ListDataModel.writeObject(ListDataModel.java:23) 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:585) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302) at java.util.concurrent.ConcurrentHashMap.writeObject(ConcurrentHashMap.java:1380) 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:585) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302) at org.jboss.web.tomcat.service.session.SessionBasedClusteredSession.writeExternal(SessionBasedClusteredSession.java:175) at org.jboss.web.tomcat.service.session.JBossCacheService.externalizeSession(JBossCacheService.java:1027) at org.jboss.web.tomcat.service.session.JBossCacheService.putSession(JBossCacheService.java:316) at org.jboss.web.tomcat.service.session.JBossCacheClusteredSession.processSessionRepl(JBossCacheClusteredSession.java:121) at org.jboss.web.tomcat.service.session.JBossCacheManager.processSessionRepl(JBossCacheManager.java:1097) at org.jboss.web.tomcat.service.session.JBossCacheManager.storeSession(JBossCacheManager.java:652) at org.jboss.web.tomcat.service.session.InstantSnapshotManager.snapshot(InstantSnapshotManager.java:49) at org.jboss.web.tomcat.service.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:98) at org.jboss.web.tomcat.service.session.JvmRouteValve.invoke(JvmRouteValve.java:84) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437) at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:366) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3777) A call to Manager.instance().initializeTemporaryConversation() doesn't play well with ServerConversationContext cache, addition, and removal maps

by Michael Youngstrom (JIRA)

A call to Manager.instance().initializeTemporaryConversation() doesn't play well with ServerConversationContext cache, addition, and removal maps ------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-3777 URL: https://jira.jboss.org/jira/browse/JBSEAM-3777 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.CR1 Reporter: Michael Youngstrom Assignee: Michael Youngstrom Fix For: 2.1.1.CR2 The situation is this. If I am in a conversation and I add and remove objects from a conversation and then call Manager.instance().initializeTemporaryConversation() then those recently added and removed beans will still be contained in the ServerConversationContext addiction and removal maps. It would seem that Manager.instance().initializeTemporaryConversation() should call ServerConversationContext.flush() prior to creating the new conversation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3780) Ability to evaluate custom EL on the debug page

by Ivan B (JIRA)

Ability to evaluate custom EL on the debug page ----------------------------------------------- Key: JBSEAM-3780 URL: https://jira.jboss.org/jira/browse/JBSEAM-3780 Project: Seam Issue Type: Feature Request Reporter: Ivan B Unfortunately debug page shows only top level context variables. It is not possible to see field value down the object path. Also, it may be useful to evaluate method values. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3393) Italian translation for default messases.properties

by Nicola Benaglia (JIRA)

Italian translation for default messases.properties --------------------------------------------------- Key: JBSEAM-3393 URL: https://jira.jboss.org/jira/browse/JBSEAM-3393 Project: Seam Issue Type: Feature Request Reporter: Nicola Benaglia I'd like to contribute with default messages.properties for italian language. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

4
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3779) Error while reading JPA XML file: META-INF/orm.xml when using SMPC with Seam Remoting

by Andreas Eriksson (JIRA)

Error while reading JPA XML file: META-INF/orm.xml when using SMPC with Seam Remoting ------------------------------------------------------------------------------------- Key: JBSEAM-3779 URL: https://jira.jboss.org/jira/browse/JBSEAM-3779 Project: Seam Issue Type: Bug Components: Remoting Affects Versions: 2.1.1.CR1 Environment: Microsoft Windows XP Professional SP3 JBoss 4.3.2.GA Reporter: Andreas Eriksson Assignee: Shane Bryzak When I package my EAR with the Seam Remoting JAR the orm.xml (contains my entity listener, i.e. EntitySecurityListener) JPA configuration file cannot be parsed. I also had to add the gwt-servlet dependency to in order to escape exception messages during deploy (even though I'm not using GWT). See attached Maven project (README.TXT inside) and stacktrace.txt. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3722) Find a way to break out of scan on hot-deploy on JBoss5

by Pete Muir (JIRA)

Find a way to break out of scan on hot-deploy on JBoss5 ------------------------------------------------------- Key: JBSEAM-3722 URL: https://jira.jboss.org/jira/browse/JBSEAM-3722 Project: Seam Issue Type: Feature Request Components: Documentation Issues Reporter: Pete Muir Fix For: 2.1.1.CR2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3725) Functional test related jar files need to be included in the distribution

by Jay Balunas (JIRA)

Functional test related jar files need to be included in the distribution ------------------------------------------------------------------------- Key: JBSEAM-3725 URL: https://jira.jboss.org/jira/browse/JBSEAM-3725 Project: Seam Issue Type: Task Components: Build Affects Versions: 2.1.1.CR1 Reporter: Jay Balunas Priority: Critical Fix For: 2.1.1.CR2 The 3 jar files that are currently in the /src/test/ftest/lib directory do get included when creating the dist of a seam release. We need to get this included so that end users can execute the functional tests using the distribution without requiring svn. If the jars can not exist in the src directory we should move them as needed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3775) xsd and config file validate should cause test failures, not build failures

by Jay Balunas (JIRA)

xsd and config file validate should cause test failures, not build failures --------------------------------------------------------------------------- Key: JBSEAM-3775 URL: https://jira.jboss.org/jira/browse/JBSEAM-3775 Project: Seam Issue Type: Task Components: Build, Test Harness Affects Versions: 2.1.1.CR1 Reporter: Jay Balunas Fix For: The future Currently if validate.xml is set to true during a seam testsuite run and an issue is found the build fails and stops. This should cause a test failure and the build should continue to run. Granted that the invalid xml/xsd files may cause collateral failures - it is still better that the build runs. This is needed in order to get xsd and file validation into hudson runs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3768) Conversational components should be able to hold bindings to JSF components.

by Francisco Jose Peredo Noguez (JIRA)

Conversational components should be able to hold bindings to JSF components. ----------------------------------------------------------------------------- Key: JBSEAM-3768 URL: https://jira.jboss.org/jira/browse/JBSEAM-3768 Project: Seam Issue Type: Feature Request Components: JSF Integration Reporter: Francisco Jose Peredo Noguez Conversational components have one minor limitation: they cannot be used to hold bindings to JSF components. Is it really impossible to remove this limitation? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2008