Bugs item #603788, was opened at 2002-09-03 03:33 Message generated for change (Comment added) made by eisber You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=603788&group_id=22866
Category: JBossServer Group: CVS HEAD Status: Closed Resolution: Wont Fix Priority: 5 Submitted By: David Jencks (d_jencks) Assigned to: Christian Riege (lqd) Summary: Can't verify app twice. Initial Comment: The ejb verifier apparently can't verify an application twice. To reproduce, start jboss (4, cvs head), remove jbossweb-ejb.jar from server/all/deploy, and replace it. The verifier complains on the second deployment. Linux x86 kernel 2.4.18 sun jdk 1.3.1-03 I haven't tried other jboss versions. Here's the verifier complaint: 2002-09-02 21:22:47,729 DEBUG [org.jboss.ejb.EJBDeployer] Verifying file:/usr/java/jboss/co15/jboss-all/build/output/jboss-4.0.0alpha/server/all/deploy/jbossweb-ejb.jar 2002-09-02 21:22:47,809 WARN [org.jboss.ejb.EJBDeployer.verifier] EJB spec violation: Bean : CMPState Method : public abstract CMPState create(String, String, int, int) throws CreateException, RemoteException Section: 12.2.9 Warning: The return type for a create(...) method must be the entity bean's local interface type. 2002-09-02 21:22:47,819 WARN [org.jboss.ejb.EJBDeployer.verifier] EJB spec violation: Bean : CMPState Method : public abstract CMPState findByPrimaryKey(CMPStatePK) throws FinderException, RemoteException Section: 10.6.10 Warning: The return type for a find<METHOD> method must be the entity bean's remote interface type (single-object finder) or a collection thereof (for a multi-object finder). 2002-09-02 21:22:47,844 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.parentTraceEnabled=true ---------------------------------------------------------------------- Comment By: eisber arktis (eisber) Date: 2003-11-28 17:00 Message: Logged In: YES user_id=263400 I got the same problem. the verifier fails on redeploy I got 5+ beans and it happens only to one of them. here's my trace. 16:54:49,784 WARN [verifier] EJB spec violation: Bean : mediaminer.Episode Method : public abstract Episode create(FileManagerProxy) throws RemoteException, CreateException Section: 12.2.9 Warning: Each create(...) method in the entity bean's home interface must have a matching ejbCreate(...) method in the entity bean's class. 16:54:49,784 WARN [verifier] EJB spec violation: Bean : mediaminer.Episode Method : public abstract Episode create(FileManagerProxy, Boolean) throws RemoteException, CreateException Section: 12.2.9 Warning: Each create(...) method in the entity bean's home interface must have a matching ejbCreate(...) method in the entity bean's class. 16:54:49,864 WARN [verifier] EJB spec violation: Bean : mediaminer.Episode Method : public abstract Episode create(FileManagerProxy, Boolean, Boolean) throws RemoteException, CreateException Section: 12.2.9 Warning: Each create(...) method in the entity bean's home interface must have a matching ejbCreate(...) method in the entity bean's class. ---------------------------------------------------------------------- Comment By: Christian Riege (lqd) Date: 2002-09-03 19:16 Message: Logged In: YES user_id=176671 I agree, this is definitely a packaging issue related to the way the UCL works. Possibly repackaging something of the org.mortbay.j2ee.session stuff would do the job?! Marking CLOSED, WONTFIX. ---------------------------------------------------------------------- Comment By: David Jencks (d_jencks) Date: 2002-09-03 18:58 Message: Logged In: YES user_id=60525 I strongly suspect this problem comes from having the ejb interface classes in 2 jars: jbossweb-ejb.jar (with the dd's) and jbossweb.sar/org.mortbay.j2ee.jar (without the dd's, but with the ejb bean implementations). I don't think there is any way to support this kind of packaging with the unified class loaders. ---------------------------------------------------------------------- Comment By: Christian Riege (lqd) Date: 2002-09-03 18:48 Message: Logged In: YES user_id=176671 This is actually a ClassLoader issue. It seems that on this particular .jar file upon redeploy the home interface is still being loaded from the old jar while the remote interface and bean class are taken from the newly created ClassLoader. Using some other .jar file the classes and interfaces are always loaded from the newly deployed JAR. Very odd. Need to dig deeper. ---------------------------------------------------------------------- Comment By: Christian Riege (lqd) Date: 2002-09-03 18:07 Message: Logged In: YES user_id=176671 I can reproduce this behaviour on 3.2 and HEAD; however up until now this only occurs on the jbossweb-ejb.jar that you mentioned. I can deploy several of my own jar files multiple times just fine. Will investigate this further; it seems to be closely related to that specific jar file. ---------------------------------------------------------------------- Comment By: Christian Riege (lqd) Date: 2002-09-03 11:29 Message: Logged In: YES user_id=176671 hm, nasty. i'll take a look at it today. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=603788&group_id=22866 ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
