November 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3757) TypeNotPresentException: Type javax.ejb.Stateful not present in POJO mode (ie non ejb3..)

by Denis Forveille (JIRA)

TypeNotPresentException: Type javax.ejb.Stateful not present in POJO mode (ie non ejb3..) ----------------------------------------------------------------------------------------- Key: JBSEAM-3757 URL: https://jira.jboss.org/jira/browse/JBSEAM-3757 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.CR1 Environment: WebSphere v6.1.0.17 in POJO mode (ie non EJB3) Reporter: Denis Forveille Priority: Critical The application does not start with seam v2.1.1.CR1 due to a "java.lang.TypeNotPresentException: Type javax.ejb.Stateful not present" exception It seems that seams tries to locate (again...) some ejb3 classes not present when seam is used in pojo mode in a non-ejb3 environnement See the attached traceback -- 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

17 years, 4 months

4
19
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3764) Update ICEfaces jars to 1.7.2.SP1 release on maven repository

by judy guglielmin (JIRA)

Update ICEfaces jars to 1.7.2.SP1 release on maven repository ------------------------------------------------------------- Key: JBSEAM-3764 URL: https://jira.jboss.org/jira/browse/JBSEAM-3764 Project: Seam Issue Type: Feature Request Components: ICE Faces Integration Affects Versions: 2.1.1.CR2 Reporter: judy guglielmin Assignee: Shane Bryzak Please update these to maven repository and I will update the build scripts for icefaces example as well as seam-gen build for icefaces -- 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

17 years, 4 months

2
7
0 / 0

[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

17 years, 4 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

17 years, 4 months

4
4
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

17 years, 4 months

4
8
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

17 years, 4 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

17 years, 4 months

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

17 years, 4 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3766) examples is not working under tomcat 6.0

by Alexey Kakunin (JIRA)

examples is not working under tomcat 6.0 ---------------------------------------- Key: JBSEAM-3766 URL: https://jira.jboss.org/jira/browse/JBSEAM-3766 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.0.SP1 Environment: CentOs 5.2, java 1.6.10_u10, tomcat 6.0.18 Reporter: Alexey Kakunin Priority: Minor just following to documentation, configured tomcat.home in build.properties,switched to example project folder (for example registration) and called ant tomcat.deploy Project built and deployed to tomcat, but during initialization followed error generated: java.lang.NoClassDefFoundError: javassist/util/proxy/MethodFilter at org.jboss.seam.contexts.Contexts.destroy(Contexts.java:243) at org.jboss.seam.contexts.Lifecycle.endApplication(Lifecycle.java:56) at org.jboss.seam.contexts.ServletLifecycle.endApplication(ServletLifecycle.java:135) at org.jboss.seam.servlet.SeamListener.contextDestroyed(SeamListener.java:39) at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:3882) at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4523) Looks like javassist should be added into depepndencies -- 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

17 years, 4 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3457) Use dynamic proxies to implement delegation in persistence

by Emmanuel Bernard (JIRA)

Use dynamic proxies to implement delegation in persistence ---------------------------------------------------------- Key: JBSEAM-3457 URL: https://jira.jboss.org/jira/browse/JBSEAM-3457 Project: Seam Issue Type: Feature Request Components: Search Reporter: Emmanuel Bernard Fix For: 2.1.1.CR1 Today, when someone throw the new Hibernate Search version or a new Hibernate Core version having more methods in (FullText)Session, Seam blows up as (FullText)HibernateSessionProxy and (FullText)EntityManagerProxy directly implement those interfaces. An alternative approach could be to reimplement those proxies as dynamic proxies passing through unknown methods. Either the JDK dynamic proxy approach or the Javassist equivalent can be used. -- 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

17 years, 4 months

2
3
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 November 2008