I understand where I went wrong. Since it's worked for quite a while, I didn't realize it was something outside the specs. Didn't realize how rigid it was. Thanks for clarifying it for me.
-A. ----- Original Message ----- From: "Ben Souther" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Tuesday, January 20, 2004 1:17 PM Subject: Re: Tomcat 5 - jsp:useBean causing a compile time exception (not pilot error - long detailed post) On Tuesday 20 January 2004 01:01 pm, Andrew Schwimmer wrote: > That code was not written by me, it was generated out by Tomcat. I know you > can't do those things in code. I understand that you didn't write the generated code. > > To summarize: > If you try to access an abstract class (or an interface) with the > <jsp:useBean> tag, it will throw a compile time exception when you try to > access the jsp page. > This was not the behavior under Tomcat4. It looks like your code was written to specific features (or side effects) of Tomcat 4 instead of the JSP specs. The "class" attribute of the useBean tag was intended to point to a class that conforms with the definition of a javabean, not an array of collection objects or an interface. I don't think you'll have much luck getting anyone on the dev list to recognize this as a bug. Good-luck -Ben --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
