Glenn Nielsen wrote:
> "Craig R. McClanahan" wrote:
> >
> > [EMAIL PROTECTED] wrote:
> >
> > > When Jasper is run in a servlet
> > > container it no longer puts the class files in a package, they are now
> > > in the default package.
> > >
> >
> > As was discussed earlier on TOMCAT-DEV, this is going to cause
> > portability problems for people who use beans that are not in packages.
> > With this
> > change, such beans will work in Tomcat but not when the app is moved to
> > a different container that *does* put JSP-generated servlets into a
> > package.
> >
> > The previous behavior (Jasper-generated servlets go into a package)
> > avoided this, because it essentially disallowed non-packaged beans.
> > Therefore, I prefer it.
> >
> > (Also, I seem to remember a discussion on the expert group for JSP 1.2
> > that non-packaged beans and generarted classes should be disallowed, but
> > I have not yet located any reference to this in the 1.2 spec.)
> >
>
> If you check the code for JasperLoader you will find that it requires
> all classes to be in a package, the only class that does not have to
> be in a package is the JSP page itself.
>
That's true, but Steve Downey also found the spec reference I couldn't find (in
Section 8.2 of the JSP 1.2 Proposed Final Draft). The JSP page class is
required to be in a package for 1.2.
>
> Regards,
>
> Glenn
>
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
