[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3007) no error message when component cannot be properly created on startup
by Sebastian Hennebrueder (JIRA)
no error message when component cannot be properly created on startup
---------------------------------------------------------------------
Key: JBSEAM-3007
URL: http://jira.jboss.com/jira/browse/JBSEAM-3007
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.0.2.GA, 2.0.1.GA
Environment: Mac OSX JDK 1.5
Tomcat 6
Reporter: Sebastian Hennebrueder
When a component implements an interface which is not deployed to the application server, the component is not created but silently ignored.
At least an error message during startup would be fine.
I run into this problem when using Groovy components. When the groovy classes are compiled to java classes they implement a groovy interface. If I do not deploy the groovy jars, the component is not loaded.
I reproduced the problem with a class implementing an interface. The interface was part of a jar which was only available at compile time but not deployed to Tomcat. Same problem happens on JBoss 4.2.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, 8 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2882) Hard dependency on org.hibernate.ejb.event.EntityCallbackHandler just added (non-JPA environment)
by Przemyslaw Jaskierski (JIRA)
Hard dependency on org.hibernate.ejb.event.EntityCallbackHandler just added (non-JPA environment)
-------------------------------------------------------------------------------------------------
Key: JBSEAM-2882
URL: http://jira.jboss.com/jira/browse/JBSEAM-2882
Project: Seam
Issue Type: Bug
Environment: Pure Tomcat + Hibernate (no JPA), Seeam 2.1 nightly 08/04/12
Reporter: Przemyslaw Jaskierski
Fix For: 2.1.0.BETA1
I've just checked out fresh Seam 2.1 snapshot and apparently someone added direct dependency to Hibernate PersistenceManger.
+- 10 days ago no such dependency existed.
Apr 12, 2008 4:43:08 PM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener
java.lang.RuntimeException: Could not create Component: org.jboss.seam.persistence.hibernatePersistenceProvider
at org.jboss.seam.init.Initialization.addComponent(Initialization.java:1008)
at org.jboss.seam.init.Initialization.installComponents(Initialization.java:924)
at org.jboss.seam.init.Initialization.init(Initialization.java:602)
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.start(ContainerBase.java:1045)
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:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: java.lang.NoClassDefFoundError: org/hibernate/ejb/event/EntityCallbackHandler
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2427)
at java.lang.Class.getDeclaredMethods(Class.java:1791)
at org.jboss.seam.Component.initMembers(Component.java:542)
at org.jboss.seam.Component.<init>(Component.java:258)
at org.jboss.seam.Component.<init>(Component.java:219)
at org.jboss.seam.init.Initialization.addComponent(Initialization.java:992)
... 18 more
Caused by: java.lang.ClassNotFoundException: org.hibernate.ejb.event.EntityCallbackHandler
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
... 25 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, 8 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2713) Bean Annotated with @Destroy Fails on any JEE5 Certified Platform.
by Burt Prior (JIRA)
Bean Annotated with @Destroy Fails on any JEE5 Certified Platform.
------------------------------------------------------------------
Key: JBSEAM-2713
URL: http://jira.jboss.com/jira/browse/JBSEAM-2713
Project: JBoss Seam
Issue Type: Bug
Components: EJB3
Affects Versions: 2.1.0.A1
Environment: Any.
Reporter: Burt Prior
Fix For: 2.1.0.A1
Hi Seam Team,
Per Gavin's suggestion and response to my post on the Seam Users Forum (http://seamframework.org/Community/Seam2JEE5CompliantWithTheTCKRequirements), I am submitting the following bug.
Also, please note that I collaborated with the Apache Geronimo engineers on identifying the source of the issue and the best approach to finding a resolution as well.
The following bug occurs when running the 'booking' example on the Geronimo 2.1 AS: (please see the Users Forum entry above for the stack trace).
... 11:25:05,179 ERROR OpenEJB The bean instance business method encountered a system exception: Callback methods cannot access parameters java.lang.IllegalStateException: Callback methods cannot access parameters ...
The code in the 'booking' example that appears to cause the issue is: (on any Bean)
...
@Destroy @Remove public void destroy() {}
...
It appears that running the 'booking' (any?) Seam (2.1.0.A1) app on the Geronimo/OpenEJB (any?) JEE5 Certified container results in the stack trace and that allowing the InvocationContext to supply the parameters during a lifecycle call results in TCK failures.
The Geronimo Engineers mentioned that if OpenEJB did not throw this exception in these circumstances it would fail the TCK.
It appears that any bean using Seam's@Destroy annotation fails on *any* JEE5 certified platform, in our case Geronimo 2.1. We surmise, but have not verified, that this must occur on GlassFish as well. (Jboss 5 beta 4?)
As a test, we removed @Destroy, and still received the error.
Resolution of this error is very important to us. I have detailed stack traces of the Geronimo log should you need them, and I would be happy to help in any way to get this issue resolved quickly. Please don't hesitate to contact me with any questions.
Thank you for your time,
Burt Prior
IT Engineer
Cisco Systems, San Jose, CA
bprior(a)cisco.com
408.853.4199
--
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, 8 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2799) Overridden components with @Install(value = false) ignores precedence.
by Shane Bryzak (JIRA)
Overridden components with @Install(value = false) ignores precedence.
----------------------------------------------------------------------
Key: JBSEAM-2799
URL: http://jira.jboss.com/jira/browse/JBSEAM-2799
Project: JBoss Seam
Issue Type: Bug
Components: Core
Reporter: Shane Bryzak
Assigned To: Shane Bryzak
Priority: Critical
Fix For: 2.1.0.BETA1
An easy way to reproduce this - take the JpaIdentityStore as an example:
@Name("org.jboss.seam.security.management.jpaIdentityStore")
@Install(precedence=Install.BUILT_IN, value = false)
@Scope(APPLICATION)
@BypassInterceptors
public class JpaIdentityStore implements IdentityStore, Serializable
Overriding it with a component with a higher precedence fails:
@Name("org.jboss.seam.security.management.jpaIdentityStore")
@Install(precedence = Install.APPLICATION)
@Scope(APPLICATION)
@BypassInterceptors
public class CustomJpaIdentityStore extends JpaIdentityStore
With the following stack trace:
java.lang.IllegalStateException: Two components with the same name and precedence: org.jboss.seam.security.management.jpaIdentityStore
at org.jboss.seam.init.Initialization.addComponentDescriptor(Initialization.java:484)
at org.jboss.seam.init.Initialization.installScannedComponentAndRoles(Initialization.java:755)
at org.jboss.seam.init.Initialization.scanForComponents(Initialization.java:702)
at org.jboss.seam.init.Initialization.init(Initialization.java:567)
at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3856)
--
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, 8 months