April 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2827) Tomcat DVD example fails deployment with NoClassDefFoundError: bsh/TargetError

by Jay Balunas (JIRA)

Tomcat DVD example fails deployment with NoClassDefFoundError: bsh/TargetError ------------------------------------------------------------------------------ Key: JBSEAM-2827 URL: http://jira.jboss.com/jira/browse/JBSEAM-2827 Project: JBoss Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.2.CR1 Environment: Fedora 8 Tomcat 6.0.16 Reporter: Jay Balunas Fix For: 2.0.2.CR1 When starting app get NoClassDefFoundError: bsh/TargetError SEVERE: Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener java.lang.RuntimeException: exception invoking: startup at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:135) 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.contexts.Contexts.startup(Contexts.java:304) at org.jboss.seam.contexts.Contexts.startup(Contexts.java:278) at org.jboss.seam.contexts.ServletLifecycle.endInitialization(ServletLifecycle.java:95) at org.jboss.seam.init.Initialization.init(Initialization.java:583) at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4350) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:829) at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:718) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1147) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:578) 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 org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) Caused by: java.lang.reflect.InvocationTargetException 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 org.jboss.seam.util.Reflections.invoke(Reflections.java:21) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:125) ... 32 more Caused by: java.lang.NoClassDefFoundError: bsh/TargetError at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2395) at java.lang.Class.getDeclaredMethods(Class.java:1763) at org.hibernate.property.BasicPropertyAccessor.getterMethod(BasicPropertyAccessor.java:317) at org.hibernate.property.BasicPropertyAccessor.getGetterOrNull(BasicPropertyAccessor.java:297) at org.hibernate.property.BasicPropertyAccessor.createGetter(BasicPropertyAccessor.java:280) at org.hibernate.property.BasicPropertyAccessor.getGetter(BasicPropertyAccessor.java:275) at org.hibernate.util.ReflectHelper.getter(ReflectHelper.java:80) at org.hibernate.util.ReflectHelper.reflectedPropertyClass(ReflectHelper.java:71) at org.hibernate.mapping.SimpleValue.setTypeUsingReflection(SimpleValue.java:276) at org.hibernate.cfg.HbmBinder.createProperty(HbmBinder.java:2174) at org.hibernate.cfg.HbmBinder.createClassProperties(HbmBinder.java:2151) at org.hibernate.cfg.HbmBinder.createClassProperties(HbmBinder.java:2041) at org.hibernate.cfg.HbmBinder.bindSubclass(HbmBinder.java:823) at org.hibernate.cfg.HbmBinder.handleSubclass(HbmBinder.java:2220) at org.hibernate.cfg.HbmBinder.bindRoot(HbmBinder.java:149) at org.hibernate.cfg.Configuration.add(Configuration.java:669) at org.hibernate.cfg.Configuration.processExtendsQueue(Configuration.java:1185) at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1122) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1286) at org.jbpm.persistence.db.DbPersistenceServiceFactory.getSessionFactory(DbPersistenceServiceFactory.java:91) at org.jbpm.persistence.db.DbPersistenceService.getSessionFactory(DbPersistenceService.java:95) at org.jbpm.persistence.db.DbPersistenceService.getSession(DbPersistenceService.java:99) at org.jbpm.persistence.db.DbPersistenceService.getGraphSession(DbPersistenceService.java:341) at org.jbpm.JbpmContext.getGraphSession(JbpmContext.java:571) at org.jbpm.JbpmContext.deployProcessDefinition(JbpmContext.java:173) at org.jboss.seam.bpm.Jbpm.deployProcess(Jbpm.java:274) at org.jboss.seam.bpm.Jbpm.installProcessDefinitions(Jbpm.java:252) at org.jboss.seam.bpm.Jbpm.startup(Jbpm.java:72) ... 38 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, 12 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2866) library commons-digester is in older version 1.5 instead of 1.8

by Marek Novotny (JIRA)

library commons-digester is in older version 1.5 instead of 1.8 --------------------------------------------------------------- Key: JBSEAM-2866 URL: http://jira.jboss.com/jira/browse/JBSEAM-2866 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.2.CR1 Reporter: Marek Novotny Assigned To: Pete Muir Priority: Minor I compared output from ant dependencyReport and real version information from manifest file of jars. In maven dependency report is defined version 1.8, but in lib directory is jar in version 1.5 -- 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, 12 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2867) xml-apis.jar is in older version 1.3.02 instead of 2.7.1

by Marek Novotny (JIRA)

xml-apis.jar is in older version 1.3.02 instead of 2.7.1 -------------------------------------------------------- Key: JBSEAM-2867 URL: http://jira.jboss.com/jira/browse/JBSEAM-2867 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.2.CR1 Reporter: Marek Novotny Priority: Minor I compared output from ant dependencyReport and real version information from manifest file of jars. In maven dependency report is defined version 2.7.1, but in lib directory is jar in version 1.3.02/2.0.2/1.0 -- 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, 12 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Work stopped: (JBSEAM-247) Inject microcontainer components

by Ales Justin (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-247?page=all ] Work on JBSEAM-247 stopped by Ales Justin. > Inject microcontainer components > -------------------------------- > > Key: JBSEAM-247 > URL: http://jira.jboss.com/jira/browse/JBSEAM-247 > Project: Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Ales Justin > > We should be able to set up components using JBoss MC, and inject them into Seam components. -- 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, 12 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-247) Inject microcontainer components

by Ales Justin (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-247?page=comments#action_12408547 ] Ales Justin commented on JBSEAM-247: ------------------------------------ With the new JBossXB.builder code finished, this is what you can now easily do: - have custom xml: http://anonsvn.jboss.org/repos/jbossas/trunk/testsuite/src/resources/hibe... - write matching metadata: http://anonsvn.jboss.org/repos/jbossas/trunk/hibernate-int/src/main/org/j... - provide deployer that understands that custom xml: http://anonsvn.jboss.org/repos/jbossas/trunk/hibernate-int/src/resources/... - have a deployer that understands that custom metadata: http://anonsvn.jboss.org/repos/jbossas/trunk/hibernate-int/src/main/org/j... Having custom parser should be just that jbossxb-parser element, need to look into why it doesn't work yet. Custom metadata deployer is not (always) needed, since it can be picked up inside existing MC beans (wildcard matching). For Seam this would mean that it could easily keep the existing components.xml, just requiring to write matching metadata, and then delegate work to MC. > Inject microcontainer components > -------------------------------- > > Key: JBSEAM-247 > URL: http://jira.jboss.com/jira/browse/JBSEAM-247 > Project: Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Ales Justin > > We should be able to set up components using JBoss MC, and inject them into Seam components. -- 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, 12 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2891) Error logging on seam startup

by Dupont Dupont (JIRA)

Error logging on seam startup ----------------------------- Key: JBSEAM-2891 URL: http://jira.jboss.com/jira/browse/JBSEAM-2891 Project: Seam Issue Type: Feature Request Affects Versions: 2.0.0.GA Environment: Websphere Reporter: Dupont Dupont SeamListener doesn't log when there's an error on startup. Seam just relies on appserver logging for that. On websphere, every error in a jvm is logged in one file SystemOut.log or SystemErr.log. This can be a problem for administrators when the same jvm host multiple seam enabled apps (from where did the log originated ?). It would be easier for WAS users if Seam logged the error with commons logging and propagated the exception (double logging, but at least we could configure log4j in each app to log to a different file). -- 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, 12 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2691) Getting started with Seam using JBoss Tools

by Pete Muir (JIRA)

Getting started with Seam using JBoss Tools ------------------------------------------- Key: JBSEAM-2691 URL: http://jira.jboss.com/jira/browse/JBSEAM-2691 Project: JBoss Seam Issue Type: Task Reporter: Pete Muir Priority: Critical Fix For: 2.0.2.GA, 2.1.0.GA We really need to add a page of instructions for getting started using JBoss Tools to the Seam reference, and link it from the Getting Started page. We should use the seam-gen chapter as a model. -- 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, 12 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2160) seam-gen templates use a mix of tabs and spaces

by Gavin King (JIRA)

seam-gen templates use a mix of tabs and spaces ----------------------------------------------- Key: JBSEAM-2160 URL: http://jira.jboss.com/jira/browse/JBSEAM-2160 Project: JBoss Seam Issue Type: Task Components: Tools Affects Versions: 2.0.0.GA Reporter: Gavin King Priority: Minor We need to pick one, and use it consistently in all templates. -- 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, 12 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2350) Content Compression with GWTService overriding Container (tomcat/jetty)

by darren hartford (JIRA)

Content Compression with GWTService overriding Container (tomcat/jetty) ----------------------------------------------------------------------- Key: JBSEAM-2350 URL: http://jira.jboss.com/jira/browse/JBSEAM-2350 Project: JBoss Seam Issue Type: Task Environment: jboss 4.2.1, Seam 2.0.0.GA (GWT 1.4.60) Reporter: darren hartford See forum reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110587 The GWTService class is doing Content Compression/HTTP. This is not documented in the normal reference/user guides. Discussion points: 1) Should Seam handle content compression (for GWT service remoting) that overrides the container (tomcat) settings. 2) If Seam does handle content compression, should it be configurable for different environments (Local LAN with poor desktops (set high), versus Dialup with fast desktop (set low)), and be able to disable content compression for wire debugging purposes. -- 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, 12 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2290) Tooling to create GWT Interface jar from @Name/@WebRemote annotations

by darren hartford (JIRA)

Tooling to create GWT Interface jar from @Name/@WebRemote annotations --------------------------------------------------------------------- Key: JBSEAM-2290 URL: http://jira.jboss.com/jira/browse/JBSEAM-2290 Project: JBoss Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.0.0.GA Environment: seam-remoting, GWT Reporter: darren hartford Create tooling support to automatically generate a separate GWT Interface jar. By default/convention, an interface class needs to be created for consumption by a GWT Web Application that conforms with the (ejb3, other?) implementation (for mapping purposes). Tooling support to automatically create this would reduce errors and improve maintenance and ease-of-integration of both server-side and GWT web app side. Recommend tooling support for: seam-gen ant maven2 For example: server impl: ============ package com.domain.app; @Stateless //seam/gwt remoting support - should be name of GWT Service class @Name("com.domain.app.gwt.client.QueryGwtService") public class QueryGwt implements QueryGwtLocal { public String gwtTest(){ return "test ok"; } } //-------------------- package com.domain.app; @Local public interface QueryGwtLocal { //Seam-gwt remoting through the interface, not the session bean @WebRemote public String gwtTest(); } ============== The above server implementation with SEAM annotations will always need the following interfaces for GWT: =================== package com.domain.app.gwt.client; public interface QueryGwtService extends RemoteService{ public String gwtTest(); } //---------------- package com.domain.app.gwt.client; public interface QueryGwtServiceAsync{ public void gwtTest(AsyncCallback callback); } ================== -- 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, 12 months

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