I recently investigated this discrepancy between
compile-time/run-time classpaths in a message called
"Research on XSP compile-time/run-time classpaths",
but got no response. I'm pretty sure we're dealing
with a bug here. The only workaround I know of at
this point is the rather unpleasant $TOMC
ything further about this issue?
Can any Cocoon developers comment on this seeming
discrepancy?
--- Michael Bierenfeld
<[EMAIL PROTECTED]> wrote:
> Greg Merrill wrote:
> >
> > Does XSP use a different classpaths at
> compile-time
> > and run-time? The reason I a
Does XSP use a different classpaths at compile-time
and run-time? The reason I ask is because I'm seeing
the following strange behavior:
I have an XSP which imports/uses some utility classes
which live in a jar file within my war's WEB-INF/lib.
When I access this XSP, it compiles just fine. I c
