Yep, that's it! Silly me (of course). Boo Resin/Nexenta, too at least
a little.
Thanks!
On Jun 23, 2009, at 11:16:15, Joseph Dane wrote:
> exceptions like these pretty much always (in fact always?) indicate a
> mismatch between the compilation and runtime environments. A method
> that existed
While your argument is perfectly correct, I don't see how that's the
case here. I build all of the libraries into the webapp WEB-INF/lib
directory. It is the exact same set of libraries in all environments.
However, you got me to thinking: what if my webapp build is including
multiple versio
exceptions like these pretty much always (in fact always?) indicate a
mismatch between the compilation and runtime environments. A method
that existed when the code was compiled doesn't exist when the code is
run.
in this case, that method
(ReflectionUtils.makeAccessible(Constructor)) exi
Serge, thanks for the reply. Unfortunately, it doesn't appear to be
the Mac's fault:
I just checked out the sources and built them on the Solaris machine,
and I still have issues. Thing is, it's never the same issue. Now it's.
java.lang.NoSuchMethodError:
org.springframework.util.ReflectionU
Rick Mann wrote:
> I run resin 4.0 on a Mac with Java 6. I build my app here, and then I
> rsync it to resin running on an OpenSolaris machine also running Java
> 6. More often than not, I end up with weird Java link issues, like
> NoSuchMethodError or AbstractMethodError.
>
> I've written a
I run resin 4.0 on a Mac with Java 6. I build my app here, and then I
rsync it to resin running on an OpenSolaris machine also running Java
6. More often than not, I end up with weird Java link issues, like
NoSuchMethodError or AbstractMethodError.
I've written about this before but never go
