November 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3741) It is now invalid to write an an EL expression inside view-id!

by Francisco Jose Peredo Noguez (JIRA)

It is now invalid to write an an EL expression inside view-id! -------------------------------------------------------------- Key: JBSEAM-3741 URL: https://jira.jboss.org/jira/browse/JBSEAM-3741 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.SP1 Reporter: Francisco Jose Peredo Noguez I am hitting this issue JBIDE-3248, at first I thougth it was an incompatiblity problem between JBoss Tools 2.1.2, and Seam 2.1.x, but now I think it is an error in http://jboss.com/products/seam/pages-2.1.xsd. In pages-2.1.xsd we have this code (that didnt exist in 2.0): <xs:simpleType name="view-id"> <xs:restriction base="xs:string"> <xs:pattern value="(/.*)|\*"/> </xs:restriction> </xs:simpleType> That is limiting view-id by preventing it from using EL expressions inside it, but EL expression do work inside view-id: <navigation from-action="#{someEntityHome.persist}"> <rule if-outcome="persisted" if="#{not empty someEntityFrom}"> <end-conversation/> <redirect view-id="{#someEntityFrom}"/> </rule> <rule if-outcome="persisted" if="#{empty someEntityFrom}"> <end-conversation/> <redirect view-id="/Crud/SomeEntityList.xhtml"/> </rule> </navigation> The line <redirect view-id="{#someEntityFrom}"/> is being reported as an error, but it is perfectly fine. I think the <xs:pattern value="(/.*)|\*"/> specified for view-id in pages-2.1.xsd is an error. -- 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
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3713) Drop the OC4J chapter from the Reference Guide

by Jay Balunas (JIRA)

Drop the OC4J chapter from the Reference Guide ---------------------------------------------- Key: JBSEAM-3713 URL: https://jira.jboss.org/jira/browse/JBSEAM-3713 Project: Seam Issue Type: Task Components: Documentation Issues, Platform interoperability Affects Versions: 2.1.0.SP1 Reporter: Jay Balunas Fix For: 2.1.1.CR2 The OC4J reference guide chapter was written for OC4J 11g. This has been dropped by Oracle because they acquired BEA and are shipping WebLogic now. OC4J 10.X is effectively an end of life phase product and so we will not be updating the reference guide chapter for it. We will drop the OC4J chapter from the reference guide. -- 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
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3745) org.jboss.seam.util.Strings improvements

by Anthony Whitford (JIRA)

org.jboss.seam.util.Strings improvements ---------------------------------------- Key: JBSEAM-3745 URL: https://jira.jboss.org/jira/browse/JBSEAM-3745 Project: Seam Issue Type: Patch Components: Core Affects Versions: 2.1.1.CR1 Reporter: Anthony Whitford I noticed some improvements that could be made to the core Strings utility class. 1. The isEmpty method is inefficient: public static boolean isEmpty(String string) { return string == null || string.trim().length() == 0; } See http://pmd.sourceforge.net/rules/strings.html#InefficientEmptyStringCheck I think you really want something closer to Apache Commons Lang StringUtils.isBlank: - http://commons.apache.org/lang/api-release/org/apache/commons/lang/String... - http://svn.apache.org/viewvc/commons/proper/lang/trunk/src/java/org/apach... 2. Consider the code: public static String toString(String sep, Object... objects) { if (objects.length==0) return ""; StringBuilder builder = new StringBuilder(); for (Object object: objects) { builder.append(sep).append(object); } return builder.substring(2); } The magic number 2 passed to the substring looks suspicious. I think this assumes that sep has a length of 2. This utility should avoid making assumptions. A similar function avoids the assumption by using sep.length: public static String toString(String sep, Class... classes) { if (classes.length==0) return ""; StringBuilder builder = new StringBuilder(); for (Class clazz: classes) { builder.append(sep).append( clazz.getName() ); } return builder.substring(sep.length()); } Overall, the hard-coded 2's should be replaced with sep.length. 3. StringBuilder is used, but some StringBuffer remains -- those could be replaced. 4. Some appends on one character strings could be replaced with char versions. (See http://pmd.sourceforge.net/rules/strings.html#AppendCharacterWithChar ). -- 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
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3588) seamspace example needs to use @Begin(join=true) for some actions

by Jay Balunas (JIRA)

seamspace example needs to use @Begin(join=true) for some actions ----------------------------------------------------------------- Key: JBSEAM-3588 URL: https://jira.jboss.org/jira/browse/JBSEAM-3588 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.0.CR1 Environment: JDK6 AS 5 CR2 Reporter: Jay Balunas Assignee: Shane Bryzak Priority: Minor Fix For: 2.1.1.CR1 If you click on create user or create role twice you get the exception below in the log Caused by: java.lang.IllegalStateException: begin method invoked from a long-running conversation, try using @Begin(join=true) on method: createRole at org.jboss.seam.core.ConversationInterceptor.aroundInvoke(ConversationInterceptor.java:47) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44) -- 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
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3749) login-required should support EL

by Przemyslaw Jaskierski (JIRA)

login-required should support EL -------------------------------- Key: JBSEAM-3749 URL: https://jira.jboss.org/jira/browse/JBSEAM-3749 Project: Seam Issue Type: Feature Request Reporter: Przemyslaw Jaskierski There is a lot of scenarios which are impossible to accomplish without EL support in login-required attribute. Example: some pages should be freely accessed by recognized users (users who have e.g. you cookie set in it), but require login or registration from unrecognized users. Conditional check against e.g. session-scoped bean in login-required would be clean an elegant way to achieve this. -- 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
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3720) Extending functionality of Equality Validator with Operation (<, <=, ==, >=, >)

by Tomas Cerny (JIRA)

Extending functionality of Equality Validator with Operation (<, <=, ==, >=, >) ------------------------------------------------------------------------------- Key: JBSEAM-3720 URL: https://jira.jboss.org/jira/browse/JBSEAM-3720 Project: Seam Issue Type: Feature Request Reporter: Tomas Cerny Priority: Optional Fix For: 2.0.3.GA Referring to the Equality Validator in Seam 2.1.0, it would be cool to have there another parameter that specifies operation <, <=, ==, >=, > I think either Trinidad or Tomahawk has something that. People would like that. ref: http://lists.jboss.org/pipermail/seam-commits/2008-October/002056.html -- 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

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3765) @Observer should support array arguments like Object... args

by Ron Thijssen (JIRA)

@Observer should support array arguments like Object... args ------------------------------------------------------------ Key: JBSEAM-3765 URL: https://jira.jboss.org/jira/browse/JBSEAM-3765 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.0.SP1 Reporter: Ron Thijssen The signature for raising an event with parameters is: public void raiseEvent(String type, Object... parameters); Passing multiple parameters to the event is possible, but it requires the Observer method to contain all passed parameters in its method signature. raisEvent("test", "Test", Boolean.FALSE) requires the following observer method signature: public void catchTest(String s, Boolean b); Wouldn't it be practical to add support to the following method signature also? public void catchTest(Object... args); -- 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
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3754) PermissionResolver description - opposite behaviour of filterSetByAction

by Edward Edkowski (JIRA)

PermissionResolver description - opposite behaviour of filterSetByAction ------------------------------------------------------------------------ Key: JBSEAM-3754 URL: https://jira.jboss.org/jira/browse/JBSEAM-3754 Project: Seam Issue Type: Bug Components: Documentation Issues Affects Versions: 2.1.0.SP1, 2.1.0.CR1 Reporter: Edward Edkowski The documentation of PermissionReolver.filterSetByAction is opposite to what the method really does. -- 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
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3121) EJB Session Bean Injection using @In weblogic server

by Leonardo Bernardelli (JIRA)

EJB Session Bean Injection using @In weblogic server ---------------------------------------------------- Key: JBSEAM-3121 URL: http://jira.jboss.com/jira/browse/JBSEAM-3121 Project: Seam Issue Type: Bug Components: EJB3 Affects Versions: 2.0.2.SP1 Environment: Weblogic application server 10.0 Reporter: Leonardo Bernardelli Priority: Critical I have 2 statefull ebjs, I am trying to inject OrganizacaoFacadeImpl e UsuarioGerenciador. I am trying to inject UsuarioGerenciador using @In annotation. I got the below exception: javax.ejb.EJBTransactionRolledbackException: EJB Exception: ; nested exception is: org.jboss.seam.InstantiationException: Could not instantiate Seam component: usuarioGerenciador at weblogic.ejb.container.internal.BaseLocalObject.handleSystemException(BaseLocalObject.java:791) at weblogic.ejb.container.internal.BaseLocalObject.postInvoke1(BaseLocalObject.java:483) at weblogic.ejb.container.internal.BaseLocalObject.postInvokeTxRetry(BaseLocalObject.java:421) at weblogic.ejb.container.internal.StatefulLocalObject.postInvokeTxRetry(StatefulLocalObject.java:86) at com.milestone.cop.action.OrganizacaoFacadeImpl_ldfou8_OrganizacaoFacadeImpl.listaOrganizacoesPorEstadoEmCriacao(OrganizacaoFacadeImpl_ldfou8_OrganizacaoFacadeImpl.java:167) at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source) at jrockit.reflect.InitialMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source) at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source) at org.jboss.seam.util.Reflections.invoke(Reflections.java:21) at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31) at org.jboss.seam.intercept.ClientSideInterceptor$1.proceed(ClientSideInterceptor.java:76) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) at org.jboss.seam.ejb.RemoveInterceptor.aroundInvoke(RemoveInterceptor.java:41) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) at org.jboss.seam.intercept.ClientSideInterceptor.invoke(ClientSideInterceptor.java:54) at org.javassist.tmp.java.lang.Object_$$_javassist_2.listaOrganizacoesPorEstadoEmCriacao()V(Object_$$_javassist_2.java:???) at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source) at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source) 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:2092) at org.jboss.seam.Component.getInstanceFromFactory(Component.java:1929) at org.jboss.seam.Component.getInstance(Component.java:1866) at org.jboss.seam.Component.getInstance(Component.java:1843) at org.jboss.seam.Namespace.getComponentInstance(Namespace.java:55) I have tried to inject with @In(create = true) and I got the same error. I managed to put it to work with @EBJ annotation, but seam components injected in UsuarioGerenciador like @Logger didn't work. I think tihis problem is similar to http://jira.jboss.org/jira/browse/JBSEAM-3034 -- 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, 4 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2485) NoClassDefFound when a service bean interface is in an outside .jar

by Adam Warski (JIRA)

NoClassDefFound when a service bean interface is in an outside .jar ------------------------------------------------------------------- Key: JBSEAM-2485 URL: http://jira.jboss.com/jira/browse/JBSEAM-2485 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.1.CR1, 2.0.0.GA Environment: JBoss AS 4.2.2, 4.2.1, Seam 2.0.0.GA, 2.0.1.CR1 Reporter: Adam Warski My deployment is as follows: - MyApi.jar, which contains the local an interface for a stateless session bean - MyApp.ear, which is a normal Seam application, and has an implementation of the interface The api is in a separate jar so that I can use the SLSB in other applications. On some occasions, I got weird exceptions, like: Caused by: java.lang.RuntimeException: by java.lang.NoClassDefFoundError: org/jboss/seam/intercept/Proxy at org.jboss.seam.util.ProxyFactory.createClass(ProxyFactory.java:190) or Caused by: java.lang.RuntimeException: by java.lang.NoClassDefFoundError: org/jboss/seam/Instance at org.jboss.seam.util.ProxyFactory.createClass(ProxyFactory.java:190) (full example stack trace below). I think the reason is as follows: in org.jboss.seam.Component.createProxyFactory(...) - lines 2234-2254, a set of interfaces is created. It is a HashSet, so the first element may differ on each invocation of the method (that's why the exception is thrown only sometimes). This set contains both the business interfaces, as well as org/jboss/seam/Instance, org/jboss/seam/intercept/Proxy. Then, in org.jboss.seam.util.ProxyFactory.getClassLoader (lines 196-212) (which is invoked from the previously mentioned method), a classloader is obtained, which is later used to load all the interfaces classes and instantiate the proxy (in javassist). The classloader is taken to be the classloader of the first interface in the interfaces array (which is constructed from the set). So, the classloader may be that of: (1) the business interface (2) org/jboss/seam/Instance, org/jboss/seam/intercept/Proxy. If it is number (2), then it is the scoped classloader of the ear. However, if it is (1), then it is the unified class loader which was used to load the .jar, which contains the business interface. This classloader cannot load the org/jboss/seam/intercept/Proxy and org/jboss/seam/Component interfaces, as they are contained in a scoped deployment. Thus, an exception is thrown. A fix which I have right now is, in org.jboss.seam.Component.createProxyFactory: 1. replace HashSet with LinkedHashSet - then the first element will always be the same 2. move adding the org/jboss/seam/intercept/Proxy and org/jboss/seam/Component interfaces to the top, so that the scoped class loader is later obtained in org.jboss.seam.util.ProxyFactory.getClassLoader. I've tested it and it seems to fix the issue. And finally the promised stack trace: javax.el.ELException: /home.xhtml: Could not instantiate Seam component: serviceBean at com.sun.facelets.compiler.TextInstruction.write(TextInstruction.java:50) at com.sun.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:39) at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:280) at org.ajax4jsf.renderkit.RendererBase.renderChildren(RendererBase.java:262) at org.richfaces.renderkit.html.PanelRenderer.doEncodeChildren(PanelRenderer.java:199) at org.richfaces.renderkit.html.PanelRenderer.doEncodeChildren(PanelRenderer.java:194) at org.ajax4jsf.renderkit.RendererBase.encodeChildren(RendererBase.java:121) at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:812) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:886) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:892) at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:592) at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108) at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:216) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:106) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:68) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:141) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) 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.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:613) Caused by: org.jboss.seam.InstantiationException: Could not instantiate Seam component: serviceBean at org.jboss.seam.Component.newInstance(Component.java:1970) 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 com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:64) at org.jboss.el.parser.AstIdentifier.getValue(AstIdentifier.java:44) at org.jboss.el.parser.AstValue.getValue(AstValue.java:63) at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) at com.sun.facelets.el.ELText$ELTextVariable.writeText(ELText.java:184) at com.sun.facelets.el.ELText$ELTextComposite.writeText(ELText.java:108) at com.sun.facelets.compiler.TextInstruction.write(TextInstruction.java:45) ... 53 more Caused by: java.lang.RuntimeException: by java.lang.NoClassDefFoundError: org/jboss/seam/intercept/Proxy at org.jboss.seam.util.ProxyFactory.createClass(ProxyFactory.java:190) at org.jboss.seam.Component.createProxyFactory(Component.java:2260) at org.jboss.seam.Component.getProxyFactory(Component.java:1375) at org.jboss.seam.Component.wrap(Component.java:1366) at org.jboss.seam.Component.instantiateSessionBean(Component.java:1288) at org.jboss.seam.Component.instantiate(Component.java:1273) at org.jboss.seam.Component.newInstance(Component.java:1966) ... 67 more Caused by: javassist.CannotCompileException: by java.lang.NoClassDefFoundError: org/jboss/seam/intercept/Proxy at javassist.util.proxy.FactoryHelper.toClass(FactoryHelper.java:165) at org.jboss.seam.util.ProxyFactory.createClass(ProxyFactory.java:186) ... 73 more Caused by: java.lang.NoClassDefFoundError: org/jboss/seam/intercept/Proxy at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:620) at sun.reflect.GeneratedMethodAccessor264.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at javassist.util.proxy.FactoryHelper.toClass2(FactoryHelper.java:177) at javassist.util.proxy.FactoryHelper.toClass(FactoryHelper.java:159) ... 74 more -- 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, 4 months

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