If you look through the archives there's a recent discussion with the
subject "Turbine.java in it's own package?"
Basically one nice thing is that you can do
localhost/servlets/Turbine instead of
localhost/servlets/org.apache.turbine.Turbine
without aliasing which seemed buggy in some cases
> on 4/17/00 4:17 PM, Jon Scarborough <[EMAIL PROTECTED]> wrote:
>
> > Is there any particular reason why the Turbine class isn't placed in the
> > org.apache.Turbine package? I don't have any overwhelming reason why it
> > should be, other than that it seems like a cleaner arrangement to me.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
