The problem here is, I use the same tag in Tomcat and
IBM WebSphere, it works ..... So ....
Actually it should be pretty easy for orion to fix the
bug in the <@page extends="....">
-Jiuyun
--- Randahl Fink Isaksen <[EMAIL PROTECTED]> wrote:
> Hi Juan
>
>
> I absolutely aggree, and it probably will be
> implemented at some point -
> giving us the chance to use it if necessary (and
> with causion).
> Having looked deeper into spec I think filters are
> definately a better
> solution - its just like the old debate about
> inheritance vs. delegation,
> the obvious idea is to use inheritance, but when you
> take all the details
> into account, you end up with using delegation
> (filters). One advantage
> being that the filters you develop can easily be
> combined or used in later
> projects. A nice feature it is!
>
>
> Randahl
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On
> Behalf Of Juan Lorandi
> (Chile)
> Sent: 31. maj 2001 17:06
> To: Orion-Interest
> Subject: RE: bugs in <@page extends="...."> in Orion
> implementation?
>
>
> take a look at the generated .java file created with
> your servlet
> template(JSP)
> you'll see that many of the features orion
> implements (session, page,
> context var) is made at this time.
> what you propose is walking around the spec, so your
> jsp pages will depend
> on how orion translates them into a servlet, thus
> rendering them not
> portable across web servers. Anything you can
> accomplish by using this new
> base class, can be accomplished by either using
> filters or by implementing
> your own security and session management thru Orion
> UserManager and
> HTTPSessionManager. Tough the earlier can be plugged
> in seamlessly, the
> latter doesn't have a configuration tag that allows
> it. The interface,
> however, is available since version 1.4.5 at least,
> and Orion uses it
> internally with two implementations, normal session
> and clustered sessions.
>
> I agree with you that the feature should be there,
> but it would be necessary
> only to work around (transient) web server
> limitations, and render the code
> unportable. It should be in orion, but must be used
> wisely.
>
> JP
>
> > -----Original Message-----
> > From: Randahl Fink Isaksen
> [mailto:[EMAIL PROTECTED]]
> > Sent: Mi�rcoles, 30 de Mayo de 2001 3:29
> > To: Orion-Interest
> > Subject: RE: bugs in <@page extends="...."> in
> Orion implementation?
> >
> >
> > Hi Juan
> >
> > I get your point about multiple inheritance, but
> say the web
> > server would
> > like all JSP pages to extend from class
> WebServerXYZPage,
> > then one could
> > just create a class which extends this web server
> class so that
> >
> > The JSP page EXTENDS MyClass which EXTENDS
> WebServerXYZPage
> >
> > This way, the web server has got room for its
> callbacks. Of
> > course, this
> > gives you a very tight coupling to the web server
> product
> > (wherefore I for
> > one would not use it), but I still don't see why
> this is not
> > possible with
> > Orion - I have been told that other EJB servers
> support this.
> >
> >
> > Yours
> > Randahl
> >
> >
> >
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On
> Behalf Of Juan Lorandi
> > (Chile)
> > Sent: 29. maj 2001 22:45
> > To: Orion-Interest
> > Subject: RE: bugs in <@page extends="...."> in
> Orion implementation?
> >
> >
> > I believe this could be better modeled
> differently, because
> > it leaves no
> > room for the web server to implement its callbacks
> and java
> > doesn't support
> > multiple inheritance.
> >
> > > -----Original Message-----
> > > From: Randahl Fink Isaksen
> [mailto:[EMAIL PROTECTED]]
> > > Sent: Martes, 29 de Mayo de 2001 3:01
> > > To: Orion-Interest
> > > Subject: RE: bugs in <@page extends="...."> in
> Orion implementation?
> > >
> > >
> > > Well, can anyone confirm that JSP pages can
> extend your own
> > > class when using
> > > Orion??? Or has noone been able to use "@page
> extends"?
> > >
> > > I see many good reasons for implementing your
> own super class
> > > for your JSP
> > > pages. For instance, such a superclass could do
> logging of
> > all client
> > > activities or it could do security checking.
> > >
> > >
> > > Randahl
> > >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED]]On
> Behalf Of Robert
> > > Nicholson
> > > Sent: 25. maj 2001 21:15
> > > To: Orion-Interest
> > > Subject: RE: bugs in <@page extends="...."> in
> Orion implementation?
> > >
> > >
> > > It's doing you a favour.Please elaborate on why
> you want to extend
> > > that class.
> > >
> > >
> > > > -----Original Message-----
> > > > From: [EMAIL PROTECTED]
> > > >
> [mailto:[EMAIL PROTECTED]]On
> Behalf Of
> > > Jiuyun Wang
> > > > Sent: Friday, May 25, 2001 9:20 AM
> > > > To: Orion-Interest
> > > > Subject: Re: bugs in <@page extends="...."> in
> Orion
> > implementation?
> > > >
> > > >
> > > > It doesnot work, not matter which one
> (servlet/jspbase) I
> > extends my
> > > > jsp, orion jsp compiler just don't support
> extends....
> > > >
> > > > -Jiuyun
> > > > --- SCOTT FARQUHAR
> <[EMAIL PROTECTED]> wrote:
> > > > > It looks like your page should extend
> servlet and not jsppage.
> > > > >
> > > > > Just change JSPBase to extend servlet (and
> make the required
> > > > > changes).
> > > > >
> > > > > I haven't read the spec, but I imagine that
> extending
> > > > > OrionHttpJspPage is proprietary, and would
> not
=== message truncated ==
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/
