Bugs item #610008, was opened at 2002-09-16 18:29 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=610008&group_id=22866
Category: JBossServer Group: v3.2 >Status: Closed Resolution: Fixed Priority: 5 Submitted By: Scott M Stark (starksm) Assigned to: Christian Riege (lqd) Summary: Verifier too strict for 2.0 cmp 1.1 home Initial Comment: The verifier is validating 2.0 EJBs that use 1.1 cmp as EJB 1.1 beans. This fails when the home includes method forms from the EJB 2.0 spec, which should be allowed. See the current failures to deploy the org.jboss.test.testbean.test.BeanUnitTestCase testbean.jar in either 3.2 or main. ---------------------------------------------------------------------- >Comment By: Christian Riege (lqd) Date: 2002-09-19 11:57 Message: Logged In: YES user_id=176671 OK; this is fixed now, CLOSING the bug. The BeanVerifier will now ignore *all* SpecViolations from a CMP 1.x Bean that is inside a 2.0 EJB Jar. However the (perceived) Violations will be logged at WARN level and an additional message is also logged at WARN level (a la "There were warning but this is CMP 1.x inside 2.0 bla bla" ) after the verification is done (only when a violation was encountered). ---------------------------------------------------------------------- Comment By: Christian Riege (lqd) Date: 2002-09-18 16:37 Message: Logged In: YES user_id=176671 Thanks for the clarification. I will see what I can do but this is a bit tricky with the current architecture. I think I have a solution but its not very elegant. Will commit later after I have banged it around a bit. ---------------------------------------------------------------------- Comment By: Scott M Stark (starksm) Date: 2002-09-18 13:52 Message: Logged In: YES user_id=175228 Yes, if you can, verifier the cmp 1.1 bean and if it fails, instead of failing the deployment issue a warning saying that the bean is suspect but allow it to deploy since there are valid constructs they verifier cannot handle currently. ---------------------------------------------------------------------- Comment By: Christian Riege (lqd) Date: 2002-09-18 10:08 Message: Logged In: YES user_id=176671 scott, i'm sorry but i don't get the direction you're leaning to. from my understanding you want the CMP 1.1 Bean to be verified but when there is an error condition encountered, the bean shouild still be marked as valid?! please clarify, i will fix this to your likings. ---------------------------------------------------------------------- Comment By: Scott M Stark (starksm) Date: 2002-09-17 19:00 Message: Logged In: YES user_id=175228 The let's change the verifier error to a warning if a 2.0 DTD is seen and the entity bean is using cmp 1.1 ---------------------------------------------------------------------- Comment By: Christian Riege (lqd) Date: 2002-09-17 17:48 Message: Logged In: YES user_id=176671 CMP 1.x Entity Beans are not checked anymore when encountered in a 2.0 JAR file. This is also noted in the logging infrastructure, although on a DEBUG level (see org.jboss.ejb.EJBDeployer for more info on this). This is certainly not the most elegant solution but its the most viable workaround I can see ATM w/o opening up too many construction sites in the current code. The whole Verifier infrastructure will undergo a rewrite for JBoss 4.0; once that is ready and tested a backport into 3.x Branch should be possible w/o many problems. I just need a quiet weekend to get that done :). Stay tuned. Oh yeah, this is in HEAD and 3.2; does it make sense to bring this into 3.0, too? ---------------------------------------------------------------------- Comment By: Christian Riege (lqd) Date: 2002-09-17 17:09 Message: Logged In: YES user_id=176671 The current Verifier doesn't have a notion of different levels of Spec Violations (i.e. Warning/Error). This is on my TODO for the next generation of the Verifier. I think what I will do is a work-around in the current incarnation. EJB 1.1 Beans inside a 2.0 jar won't get verified at all and a warning message will be issued. ---------------------------------------------------------------------- Comment By: Scott M Stark (starksm) Date: 2002-09-17 16:42 Message: Logged In: YES user_id=175228 The let's change the verifier error to a warning if a 2.0 DTD is seen and the entity bean is using cmp 1.1 ---------------------------------------------------------------------- Comment By: Christian Riege (lqd) Date: 2002-09-17 10:56 Message: Logged In: YES user_id=176671 I will have a look at this but from my memory the current architecture of the Verifier doesn't allow for an easy fix for this -- it's either 2.0 or 1.1 all the way. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=610008&group_id=22866 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
