-
1. Re: Register Pair 2/3 contains wrong type on ejbSelect
rinehart Mar 8, 2002 8:23 PM (in response to rinehart)I'm attaching server.log with stack trace for what it's worth. :)
-
2. Re: Register Pair 2/3 contains wrong type on ejbSelect
rinehart Mar 9, 2002 3:10 PM (in response to rinehart)This issue has a root cause in a java.lang.VerifierError, which is subclass of java.lang.LinkageError. JavaDoc says, "Subclasses of LinkageError indicate that a class has some dependency on another class; however, the latter class has incompatibly changed after the compilation of the former class."
The VerifierError comes up on several of the ejbSelect methods in my application. This was not a problem prior to Mar 7, and it's root cause may be in changes that were made to the org.jboss.proxy.compiler package on that day. I've snooped around the classes in that package, but am hesitant to touch anything. Hopefully someone else takes an interest in this issue who has more knowledge of the compiler package.
- Mac -
3. Re: Register Pair 2/3 contains wrong type on ejbSelect
rinehart Mar 9, 2002 3:26 PM (in response to rinehart)Here's a sample application that can be used to reproduce the error
-
4. Re: Register Pair 2/3 contains wrong type on ejbSelect
rinehart Mar 9, 2002 5:08 PM (in response to rinehart)Note, there is an unrelated EJB-QL syntax error in the ejb-jar file of the sample application. Appologies for that, I'm not getting those error reports because the deployment is failing before the issue is identified.
I'd repost the app, but I don't want to create a clutter of attachments on a program that I haven't been able to test. The fix is simple. Open the ejb-jar file, search for "owner.clientId = ?1 owner.createDate = ?2", and and the missing keyword "AND" in the middle. -
5. Re: Register Pair 2/3 contains wrong type on ejbSelect
user57 Apr 4, 2002 8:14 PM (in response to rinehart)I have briefly looked into this, but I can't tell where the root of the bug is. Could be something in org.jboss.proxy.compiler, or could be a bug in BCEL...
=(
--jason