Hmm...Javassist does have a couple static methods for things but I
hope that doesn't have anything to do with this.
For now, I would recommend trying out the new 3.6ga release of
javassist to see if that doesn't resolve the problem. I may try and
sneak that version in as a dependency for the 4.
well, yes and no.
Both Tapestry applications are deployed in a separate war file and they both
contain javaassist version 3.4.GA. The Spring Web Services application is
also deployed in a separate war file containing version 3.3. So yes, Jetty
has loaded different versions of javassist. And no, th
You may also want to try out whatever is in this new 3.6 javassist
release. Sounds like a bug in hibernate or javassist to me but it's
hard to tell for sure.
http://mirrors.ibiblio.org/pub/mirrors/maven2/jboss/javassist/3.6.ga/
On Thu, Jan 31, 2008 at 12:55 PM, Jesse Kuhnert <[EMAIL PROTECTED]>
Thanks for the in depth analysis. The EntityManager requiring
javassist does provide some hope.
Just to confirm things - is your app running with both javassist 3.3
and 3.4 on the classpath?
On Thu, Jan 31, 2008 at 11:21 AM, Marcel Schepers
<[EMAIL PROTECTED]> wrote:
> The problem occured on a
The problem occured on a dedicated production server, it never ever occured
on a development server.
The server runs 4 websites: a "normal" customer website, two redirection
websites whose only goal is to redirected the user to the normal website and
a webservices website. All these websites are
an be had.
>
> On Wed, Jan 30, 2008 at 1:47 PM, Marcel Schepers
> <[EMAIL PROTECTED]> wrote:
> > Hello,
> >
> > Tapestry (or more likely Javassist) generated scary error messages,
> such as
> > 'compile error: no such class: $StampCatalogue_23&
1:47 PM, Marcel Schepers
<[EMAIL PROTECTED]> wrote:
> Hello,
>
> Tapestry (or more likely Javassist) generated scary error messages, such as
> 'compile error: no such class: $StampCatalogue_23'. StampCatalogue is an
> abstract Tapestry page. In case these messages sho
Hello,
Tapestry (or more likely Javassist) generated scary error messages, such as
'compile error: no such class: $StampCatalogue_23'. StampCatalogue is an
abstract Tapestry page. In case these messages show up, Jetty has to be
restarted in order to restore from this chaos.
I am usin