Thanks Patrick. I think I was recompiling as the system administrator was changing things, or that we were already at 0.49 but I still had an old config with 0.44 in it. We downgraded to 1.4.2_10 and that seemed to straighten things out.
Could you please post a reference on the directories and files that are created when one compiles? I think I have some old, unused files lying around, and an extra _Inline directory. I didn't locate a .jdat file, but will look again. Candace Quoting Patrick LeBoutillier <[EMAIL PROTECTED]>: > Candace, > > On 1/24/06, Candace Holman <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I've been happily using Inline::Java since 2002, but we've run far > > behind in our version. We recently upgraded to java runtime > > environment 1.5.0_06 and it's causing run time problems with the 0.44 > > Inline::Java, namely: > > > > Report version mismatch (class RequestDirectoryListing java.lang.Object > > != V2). Delete your '_Inline' and try again. at LDAPQuery.pl line 0 > > INIT failed--call queue aborted. > > If you look somewhere under the proper _Inline directory, you should > find one or more .jdat files. At some point in the past, I introduced > a version number on the first line of the file to allow the format to > change and preserve compatibility, i.e.: > > V2 > class t15 org.perl.inline.java.InlineJavaPerlCaller > constructor () > method instance t15 add(int, int) > .. > > It seems that in your case an old .jdat file still exists somewhere > that doesn't have a version line, thereby confusing the validating > system. Basically what you need to do is locate this file and delete > it. The next build will recreate the .jdat file and all should be > good. > > Note: This problem would have been caused by an upgrade of > Inline::Java, not by and upgrade of Java. The check for the version in > the .jdat file appeared in Inline::Java 0.49. It did not exist in > 0.44. Looks like your a trying to read a 0.44 jdat file using version > 0.49 or above... > > > > > Deleting the _Inline didn't make this error go away. Actually I renamed > > it so there are still copies of old, working builds in there. Assuming > > I can't get this to work today, is there any way to revert to the old > > build or is it gone forever? The problem only cropped up when I made a > > change, which I later reverted, so it would work okay to revert to an > > old build.... > > That's very strange. Make sure you are not using 2 different versions > of Inline::Java (one when you build and a different one when you run > maybe?). > > Patrick > > > > with thanks, > > Candace > > > > > > > > > -- > ===================== > Patrick LeBoutillier > Laval, Québec, Canada >
