cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hunsberger, Peter" <Peter.Hunsber...@STJUDE.ORG>
Subject RE: [RT] Use of flowscript or the pyramid of contracts (was Re:[RT] Checked exceptions considered harmful)
Date Tue, 27 Apr 2004 21:46:06 GMT
Stefano Mazzocchi <> writes:

> Hunsberger, Peter wrote:
> > Stefano Mazzocchi <> writes:
> > 
> > <snip/>
> > 
> >>Now we made it easier to write flowscript than to write
> >>components, now 
> >>we have to focus on making it easier to write components than 
> >>flowscript.
> >>
> >>How?
> >>
> >>Chris' magic compiler classloader is the way to go, IMHO.
> > 
> > 
> > If so, then it's going to have to work in all environments.  It's 
> > still broken when deploying as an EAR under JBoss:
> > 
> >
> Fix it! ;-)

I spent some time trying to do just that. Got bogged down in finding the
source for parts of Avalon and the Rhino stuff, and then there's the
fact that it uses the Eclipse jdtcore libraries which I didn't even
attempt to locate source for (I don't know if I'd need it).  There is
one heck of a lot of complex dependencies in that chunk of the code.  

However, I closed the bug; it turns out that upgrading to JBoss 3.2.3
makes the problem go away.  I'd guess that Jboss EAR unwrapping was
somehow interfering with Cocoons source resolving, but whether the bug
is Jboss's or Cocoons's I don't know....

View raw message