Hessian was extracted to a separate hessian.jar in the Resin dist a while back, which made it possible to upgrade Hessian without changing Resin version. For some reason hessian was moved back into resin.jar.
/Mattias Scott Ferguson wrote (2009-06-18 00:16): > On Jun 17, 2009, at 2:10 PM, Rick Mann wrote: > > >> On Jun 17, 2009, at 13:58:29, Scott Ferguson wrote: >> >> >>> On Jun 17, 2009, at 1:48 PM, Rick Mann wrote: >>> >>> >>>> If I download/build a separate Hessian library and drop it into my >>>> WEB- >>>> INF/lib directory, will it get used instead of the one built-in to >>>> Resin? >>>> >>> No, you need to put the replacement in the CLASSPATH (so it's loaded >>> before the resin.jar). >>> >>> In Java, the parent classloaders have priority (that order is needed >>> because of class cast issues.) So any hessian in WEB-INF/lib would >>> be >>> ignored. >>> >> Hmm. I've always tried to steer far clear of putting anything on the >> CLASSPATH when running servlet containers. I don't know if I learned >> that back when I used Tomcat, or if it was something Resin >> recommended. >> > > Well, it's normally not a good idea, but it's how you would override > hessian. > > >> A better alternative would be for me to get to a place where I build >> resin and run my build; this would allow me to insert logging to help >> me figure out problems when I run into them all across resin, let >> alone just Hessian. But Hessian is my most urgent need right now. >> >> Are there instructions for building Resin anywhere? >> > > You should be able to just download the source and use ant. I think > we cleared up the dependencies (with the exception of 'ant dist'). > > -- Scott > > -- </Mattias>
_______________________________________________ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
