Getting the jar files into the classpath is indeed a disadvantage, which
can be a big one depending on your installation process. Rather than just
dropping a directory full of classfiles into the servlets directory, you
need to explicitly add the jar file(s) to the runtime classpath. Also be
aware that some servletrunners won't automagically reload new versions
when you update them, as they do with servlets in their servlets
directory.
> Jaman,
>
> You can indeed use jar files with servlets. It depends on the servlet
> engine, but putting things into jar files may be faster because the
> servlet engine doesn't have to check the class files each time to see if
> they need to be dynamically reloaded. I would think that this completely
> depends on the servlet engine (how it implements dynamic reloading) and
> I'm not sure how each one of them does it. Putting things into jar files
> can also make servlets easier to manage.
>
> If you do decide to use a jar file, you just need to put it in
> a directory that is in the classpath of the servlet engine. I would
> check
> documentation for whatever platform you're using.
>
> Good luck!
> -Matt Tucker
...
> > [EMAIL PROTECTED] wrote:
> >
> > > Sorry, if this is a newbie question, but are there advantages
> to
> > > placing packages in Jar files rather than just leaving them in
> .class
> > > files sorted by directories? Are there disadvantages?
> > >
> > > Thanks, Jaman
--
Jim Tomlinson [EMAIL PROTECTED] 206.217.7927
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
