Geert,
Thanks for the support... the problems are solved now; it had to with
classpath issues: I traced it down to the <pathelement
location="${build.classes}" /> directive.
Both tomcat and jetty now work off the same deployment, and for jetty
deployment the derby.jar can work from either the web-inf/lib folder
(which is how I have left it now) or the jetty/lib folder
Thanks,
Emmanuel
On 11/1/05, Geert Bevin <[EMAIL PROTECTED]> wrote:
> > OK ... scrap the output problem... everything works as expected on
> > tomcat... I was missing a "print(template)" statement at the end of
> > the doXXX method. So tomcat is fine now.
> >
> > Jetty is still problematic ... but i'm still testing... i'll let u
> > know.
>
> Ok, let me know if there's something we can help with.
>
> --
> Geert Bevin Uwyn bvba
> "Use what you need" Avenue de Scailmont 34
> http://www.uwyn.com 7170 Manage, Belgium
> gbevin[remove] at uwyn dot com Tel +32 64 84 80 03
>
> PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9
> Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net
>
>
> _______________________________________________
> Rife-users mailing list
> [email protected]
> http://www.uwyn.com/mailman/listinfo/rife-users
>
_______________________________________________
Rife-users mailing list
[email protected]
http://www.uwyn.com/mailman/listinfo/rife-users
