RE: bugs in @page extends=.... in Orion implementation?
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 be part of the spec. Scott [EMAIL PROTECTED] 05/23/01 05:42am I create a class called JSPBase class which extends OrionHttpJspPage, and I put the @ page extends=packagename.JSPBase in my JSP file. however, orion give the following error: Superclass of the JSP page does not implement Servlet
RE: bugs in @page extends=.... in Orion implementation?
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
Re: bugs in @page extends=.... in Orion implementation?
Hi Robert,
Let's see, we follow two different aproaches to get to the XML. If we
are using Oracle, we pretty much always do, we produce XML directly from
PLSQL using some sentences like that:
...
for v_user in cursor_users(condition) loop
XMP.P('USER');
XMP.P(' CODE=' || v_user.Code || '');
XMP.P(' NAME=' || v_user.Name || '');
XMP.P('/');
end loop;
...
The result is then forwarded to an XSLT processor (TRaX API compatible)
that produces the HTML. Precompiled XSLT sheets are cached so
performance is greatly improved.
If we are not using Oracle, or we need to use some Java, then we format
the XML using JSPs like that:
%@ taglib uri=/leafTag.jar prefix=leaf %
leaf:XSLEval xsltSheetName=%= getXSLTName() %
...
%
for(int i = 0; i users.length; i++)
{
%
USER
CODE=%= users[i].getCode()%
NAME=%= users[i].getName()%
/
%
}
%
...
/leaf:XSLEval
After the XML has been produced, the XSLEval tag passes its body to the
same XSLT processor as above and then result is substituted by the HTML
result. PLSQL-generated XML can be also included inside the JSPs with
another tag, in case of need. As it uses the same XSLT processing
facilities, PLSQL-generated XML and JSP-generated share the XSLT cache.
That's basically how we do it. We are not using EJB as
programming/mantaining the database code in PLSQL is like heaven,
compared to programming it with Java. We might get to use them but if we
do, we will format them with JSPs or pseudo-generate it with
introspection.
It's not perfect and not every like it but we are quite happy with it
and we have implemented around a dozen applications with the system so
far.
If your question was specifically about the HTML produced from the XML,
it's exactly the same that it would be produced with a JSP, or by hand.
The result is exactly the same. It's the way to accomplish it that is
different. We though that, instead of creating a huge library of taglibs
that perform loops, conditionals, basic operations..., it would be much
simpler to use XSLT that already has all these features and allows you
to easily reuse them. And it is also a standard with several
implementations available so...
regards,
D.
Robert Nicholson wrote:
Can you elaborate on how you are using XSL and XSLT ... I assume you're
using Tag libraries but can you show an example of HTML markup derived from
XML?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Daniel Lopez
Sent: Wednesday, May 30, 2001 6:05 AM
To: Orion-Interest
Subject: Re: bugs in @page extends= in Orion implementation?
Hi,
I've also used filters, but in this case to filter requests by IP, as I
don't want certain IP's to be able to access certain URLs. On the other
hand, I implemented security, logging and other features inside my own
servlet Controller, following a Model 2 approach. I thought about
externalizing this services as filters, but that would mean that the
web.xml file will grow too much and that I would have to put too much
things in the request object each time. It's not that I've discarded the
idea, but I don't see any compelling reason to implement everything as
filters. We don't use servlets, but ONE controller servlet and action
classes and we use JSP as view-only, creatures (actually, we seldom use
them as we use XML/XSLT), so as anyway all the requests go through my
controller servlet... We implemented IP filtering as a filter because we
also wanted to use it in other applications, as well as with static
content.
Just my 2c,
D.
---
Daniel Lopez Janariz ([EMAIL PROTECTED])
Web Services
Computer Center
Balearic Islands University
---
Marcel Schutte wrote:
Hi Randahl,
I've used a filter to do gzip encoding for specific file types. Starting
with the tutorial at
http://www.orionserver.com/tutorials/filters/lesson5/,
I've changed some things to get the hang of it and also to
reduce the amount
of buffering used. It works fine, haven't had a problem with this
(intranet)site.
The beauty of filters is that they are completely independent from your
application, just edit your web.xml and you are set.
Let me know if you wnat some more info.
Marcel
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Randahl Fink
Isaksen
Sent: Wednesday, May 30, 2001 9:39 AM
To: Orion-Interest
Subject: RE: bugs in @page extends= in Orion implementation?
Hi Marcel
I looked it up, and I definately see your point about the
filter mechanism.
Have you any experience with this on Orion? Does it work
well? And what have
you used it for?
Of course if anyone else have tried it out, I would very much
like to hear
from you too.
Yours
Randahl
-Original Message
Re: bugs in @page extends=.... in Orion implementation?
Hi Joni, I agree it can be done. My situation is that I just don't log requests but I can log everything that happens in the environment, security settings, internationalization issues, XML/XSLT performance... so my logging code is tightly integrated with the framework and I can control it from a single point. I could use a filter to check things before the request is served, but as the rest of the parts are going to use it, what do I win by externalising it. Anyway, I hope to be able to discard this part of the environment as soon as JDK1.4 logging features become a reality. With security is more or less the same, we implemented our own security library because we are not satisfied with the standard and we don't want to get container specific. I agree I could externalise this as a filter but I wouldn't really win much, as it is also quite tightly integrated with the rest of the things. IMO, things that are standard and can be switched on/off and replaced with another implementation without a hitch are candidates to be externalised, otherwise, it's not that it cannot be done with filters, it's that I don't see a big win in doing so. Of course, that's my situation because I can control the MVC 2 implementation and I can tightly integrate these parts. Just a question. I thought JAAS was used to control if the OS user that was executing the Java code was/was not allowed to perform such execution. If the OS user that executes the servlet code is supposedly always the same, how is this thing related to the application user that performs the request? I didn't think this standard could be used for that, if it is, I might go for it ;). regards, Dan Joni Suominen wrote: Hi! I have implemented these features as externalized filters. The reason for this was that I use a MVC 2 product which is developed independently (Jakarta Struts http://jakarta.apache.org/struts/). Like Marcel said the beauty of filters is that they are independent from the rest of the application. The filters allow me to plug in these services to the application without any integration code. So, I have a LogFilter which logs the requests using log4j (http://jakarta.apache.org/log4j/). After that there's an AuthorizationFilter which checks if the current user has priviledges to execute the request. AuthorizationFilter utilizes the forthcoming Java Authentication and Authorization service (http://java.sun.com/products/jaas/). All in all, I have a pretty flexible system with a very little own code. Joni [EMAIL PROTECTED] Daniel López wrote: Hi, I've also used filters, but in this case to filter requests by IP, as I don't want certain IP's to be able to access certain URLs. On the other hand, I implemented security, logging and other features inside my own servlet Controller, following a Model 2 approach. I thought about externalizing this services as filters, but that would mean that the web.xml file will grow too much and that I would have to put too much things in the request object each time. It's not that I've discarded the idea, but I don't see any compelling reason to implement everything as filters. We don't use servlets, but ONE controller servlet and action classes and we use JSP as view-only, creatures (actually, we seldom use them as we use XML/XSLT), so as anyway all the requests go through my controller servlet... We implemented IP filtering as a filter because we also wanted to use it in other applications, as well as with static content. Just my 2c, D. --- Daniel Lopez Janariz ([EMAIL PROTECTED]) Web Services Computer Center Balearic Islands University --- Marcel Schutte wrote: Hi Randahl, I've used a filter to do gzip encoding for specific file types. Starting with the tutorial at http://www.orionserver.com/tutorials/filters/lesson5/, I've changed some things to get the hang of it and also to reduce the amount of buffering used. It works fine, haven't had a problem with this (intranet)site. The beauty of filters is that they are completely independent from your application, just edit your web.xml and you are set. Let me know if you wnat some more info. Marcel -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Randahl Fink Isaksen Sent: Wednesday, May 30, 2001 9:39 AM To: Orion-Interest Subject: RE: bugs in @page extends= in Orion implementation? Hi Marcel I looked it up, and I definately see your point about the filter mechanism. Have you any experience with this on Orion? Does it work well? And what have you used it for? Of course if anyone else have tried it out, I would very much like to hear from you too. Yours Randahl -Original Message- From: [EMAIL PROTECTED
Re: bugs in @page extends=.... in Orion implementation?
applications, as well as with static content. Just my 2c, D. --- Daniel Lopez Janariz ([EMAIL PROTECTED]) Web Services Computer Center Balearic Islands University --- Marcel Schutte wrote: Hi Randahl, I've used a filter to do gzip encoding for specific file types. Starting with the tutorial at http://www.orionserver.com/tutorials/filters/lesson5/, I've changed some things to get the hang of it and also to reduce the amount of buffering used. It works fine, haven't had a problem with this (intranet)site. The beauty of filters is that they are completely independent from your application, just edit your web.xml and you are set. Let me know if you wnat some more info. Marcel -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Randahl Fink Isaksen Sent: Wednesday, May 30, 2001 9:39 AM To: Orion-Interest Subject: RE: bugs in @page extends= in Orion implementation? Hi Marcel I looked it up, and I definately see your point about the filter mechanism. Have you any experience with this on Orion? Does it work well? And what have you used it for? Of course if anyone else have tried it out, I would very much like to hear from you too. Yours Randahl -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Marcel Schutte Sent: 30. maj 2001 00:22 To: Orion-Interest Subject: Re: bugs in @page extends= in Orion implementation? That's right, the two examples Randahl gives can be easily solved using the servlet2.3 filter mechanism, giving a very loose coupling of these features with your actual application. Marcel - Original Message - From: Juan Lorandi (Chile) [EMAIL PROTECTED] To: Orion-Interest [EMAIL PROTECTED] Sent: Tuesday, May 29, 2001 10:45 PM 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 be part of the spec. Scott [EMAIL PROTECTED] 05/23/01 05:42am I create a class called JSPBase class which extends OrionHttpJspPage, and I put the @ page extends=packagename.JSPBase in my JSP file. however, orion give the following error: Superclass of the JSP page does not implement Servlet, invalid extends attribute. Does orion implement @page extends correctly? Any clarification? -Jiuyun __ Do You Yahoo
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 be part of the spec. Scott [EMAIL PROTECTED] 05/23/01 05:42am I create a class called JSPBase class which extends OrionHttpJspPage, and I put the @ page extends=packagename.JSPBase in my JSP file. however, orion give the following error: Superclass of the JSP page does not implement Servlet, invalid extends attribute. Does orion implement @page extends correctly? Any clarification? -Jiuyun __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ = Jiuyun Wang M.Sc. of Computer Sciences Sun Certified Programmer for Java 2 Platform IBM Certified Solution Enterprise Developer Phone: 919-696-0419(cel) Email: [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
RE: bugs in @page extends=.... in Orion implementation?
Hi Marcel I looked it up, and I definately see your point about the filter mechanism. Have you any experience with this on Orion? Does it work well? And what have you used it for? Of course if anyone else have tried it out, I would very much like to hear from you too. Yours Randahl -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Marcel Schutte Sent: 30. maj 2001 00:22 To: Orion-Interest Subject: Re: bugs in @page extends= in Orion implementation? That's right, the two examples Randahl gives can be easily solved using the servlet2.3 filter mechanism, giving a very loose coupling of these features with your actual application. Marcel - Original Message - From: Juan Lorandi (Chile) [EMAIL PROTECTED] To: Orion-Interest [EMAIL PROTECTED] Sent: Tuesday, May 29, 2001 10:45 PM 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 be part of the spec. Scott [EMAIL PROTECTED] 05/23/01 05:42am I create a class called JSPBase class which extends OrionHttpJspPage, and I put the @ page extends=packagename.JSPBase in my JSP file. however, orion give the following error: Superclass of the JSP page does not implement Servlet, invalid extends attribute. Does orion implement @page extends correctly? Any clarification? -Jiuyun __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ = Jiuyun Wang M.Sc. of Computer Sciences Sun Certified Programmer for Java 2 Platform IBM Certified Solution Enterprise Developer Phone: 919-696-0419(cel) Email: [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
RE: bugs in @page extends=.... in Orion implementation?
Hi Randahl, I've used a filter to do gzip encoding for specific file types. Starting with the tutorial at http://www.orionserver.com/tutorials/filters/lesson5/, I've changed some things to get the hang of it and also to reduce the amount of buffering used. It works fine, haven't had a problem with this (intranet)site. The beauty of filters is that they are completely independent from your application, just edit your web.xml and you are set. Let me know if you wnat some more info. Marcel -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Randahl Fink Isaksen Sent: Wednesday, May 30, 2001 9:39 AM To: Orion-Interest Subject: RE: bugs in @page extends= in Orion implementation? Hi Marcel I looked it up, and I definately see your point about the filter mechanism. Have you any experience with this on Orion? Does it work well? And what have you used it for? Of course if anyone else have tried it out, I would very much like to hear from you too. Yours Randahl -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Marcel Schutte Sent: 30. maj 2001 00:22 To: Orion-Interest Subject: Re: bugs in @page extends= in Orion implementation? That's right, the two examples Randahl gives can be easily solved using the servlet2.3 filter mechanism, giving a very loose coupling of these features with your actual application. Marcel - Original Message - From: Juan Lorandi (Chile) [EMAIL PROTECTED] To: Orion-Interest [EMAIL PROTECTED] Sent: Tuesday, May 29, 2001 10:45 PM 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 be part of the spec. Scott [EMAIL PROTECTED] 05/23/01 05:42am I create a class called JSPBase class which extends OrionHttpJspPage, and I put the @ page extends=packagename.JSPBase in my JSP file. however, orion give the following error: Superclass of the JSP page does not implement Servlet, invalid extends attribute. Does orion implement @page extends correctly? Any clarification? -Jiuyun __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ = Jiuyun Wang M.Sc. of Computer Sciences Sun Certified Programmer for Java 2 Platform IBM Certified Solution Enterprise Developer Phone: 919-696-0419(cel) Email: [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
Re: bugs in @page extends=.... in Orion implementation?
Hi, I've also used filters, but in this case to filter requests by IP, as I don't want certain IP's to be able to access certain URLs. On the other hand, I implemented security, logging and other features inside my own servlet Controller, following a Model 2 approach. I thought about externalizing this services as filters, but that would mean that the web.xml file will grow too much and that I would have to put too much things in the request object each time. It's not that I've discarded the idea, but I don't see any compelling reason to implement everything as filters. We don't use servlets, but ONE controller servlet and action classes and we use JSP as view-only, creatures (actually, we seldom use them as we use XML/XSLT), so as anyway all the requests go through my controller servlet... We implemented IP filtering as a filter because we also wanted to use it in other applications, as well as with static content. Just my 2c, D. --- Daniel Lopez Janariz ([EMAIL PROTECTED]) Web Services Computer Center Balearic Islands University --- Marcel Schutte wrote: Hi Randahl, I've used a filter to do gzip encoding for specific file types. Starting with the tutorial at http://www.orionserver.com/tutorials/filters/lesson5/, I've changed some things to get the hang of it and also to reduce the amount of buffering used. It works fine, haven't had a problem with this (intranet)site. The beauty of filters is that they are completely independent from your application, just edit your web.xml and you are set. Let me know if you wnat some more info. Marcel -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Randahl Fink Isaksen Sent: Wednesday, May 30, 2001 9:39 AM To: Orion-Interest Subject: RE: bugs in @page extends= in Orion implementation? Hi Marcel I looked it up, and I definately see your point about the filter mechanism. Have you any experience with this on Orion? Does it work well? And what have you used it for? Of course if anyone else have tried it out, I would very much like to hear from you too. Yours Randahl -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Marcel Schutte Sent: 30. maj 2001 00:22 To: Orion-Interest Subject: Re: bugs in @page extends= in Orion implementation? That's right, the two examples Randahl gives can be easily solved using the servlet2.3 filter mechanism, giving a very loose coupling of these features with your actual application. Marcel - Original Message - From: Juan Lorandi (Chile) [EMAIL PROTECTED] To: Orion-Interest [EMAIL PROTECTED] Sent: Tuesday, May 29, 2001 10:45 PM 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 be part of the spec. Scott [EMAIL PROTECTED] 05/23/01 05:42am I create a class called JSPBase class which extends OrionHttpJspPage, and I put the @ page
Re: bugs in @page extends=.... in Orion implementation?
Hi! I have implemented these features as externalized filters. The reason for this was that I use a MVC 2 product which is developed independently (Jakarta Struts http://jakarta.apache.org/struts/). Like Marcel said the beauty of filters is that they are independent from the rest of the application. The filters allow me to plug in these services to the application without any integration code. So, I have a LogFilter which logs the requests using log4j (http://jakarta.apache.org/log4j/). After that there's an AuthorizationFilter which checks if the current user has priviledges to execute the request. AuthorizationFilter utilizes the forthcoming Java Authentication and Authorization service (http://java.sun.com/products/jaas/). All in all, I have a pretty flexible system with a very little own code. Joni [EMAIL PROTECTED] Daniel López wrote: Hi, I've also used filters, but in this case to filter requests by IP, as I don't want certain IP's to be able to access certain URLs. On the other hand, I implemented security, logging and other features inside my own servlet Controller, following a Model 2 approach. I thought about externalizing this services as filters, but that would mean that the web.xml file will grow too much and that I would have to put too much things in the request object each time. It's not that I've discarded the idea, but I don't see any compelling reason to implement everything as filters. We don't use servlets, but ONE controller servlet and action classes and we use JSP as view-only, creatures (actually, we seldom use them as we use XML/XSLT), so as anyway all the requests go through my controller servlet... We implemented IP filtering as a filter because we also wanted to use it in other applications, as well as with static content. Just my 2c, D. --- Daniel Lopez Janariz ([EMAIL PROTECTED]) Web Services Computer Center Balearic Islands University --- Marcel Schutte wrote: Hi Randahl, I've used a filter to do gzip encoding for specific file types. Starting with the tutorial at http://www.orionserver.com/tutorials/filters/lesson5/, I've changed some things to get the hang of it and also to reduce the amount of buffering used. It works fine, haven't had a problem with this (intranet)site. The beauty of filters is that they are completely independent from your application, just edit your web.xml and you are set. Let me know if you wnat some more info. Marcel -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Randahl Fink Isaksen Sent: Wednesday, May 30, 2001 9:39 AM To: Orion-Interest Subject: RE: bugs in @page extends= in Orion implementation? Hi Marcel I looked it up, and I definately see your point about the filter mechanism. Have you any experience with this on Orion? Does it work well? And what have you used it for? Of course if anyone else have tried it out, I would very much like to hear from you too. Yours Randahl -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Marcel Schutte Sent: 30. maj 2001 00:22 To: Orion-Interest Subject: Re: bugs in @page extends= in Orion implementation? That's right, the two examples Randahl gives can be easily solved using the servlet2.3 filter mechanism, giving a very loose coupling of these features with your actual application. Marcel - Original Message - From: Juan Lorandi (Chile) [EMAIL PROTECTED] To: Orion-Interest [EMAIL PROTECTED] Sent: Tuesday, May 29, 2001 10:45 PM 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
Re: bugs in @page extends=.... in Orion implementation?
There is several good reason for using inheritance, for example, if you have a lot of utility methods you want to be included in every JSP in one specific Web Application. In JSP 1.1, it specifies that --- The JSP container should check (usually through reflection) that the provided superclass: · Implements HttpJspPage if the protocol is HTTP, or JspPage otherwise. Orion does not implement it correctly! -Jiuynu Jiuyun Wang M.Sc. of Computer Sciences Sun Certified Programmer for Java 2 Platform IBM Certified Solution Enterprise Developer Phone: 919-696-0419(cel) Email: [EMAIL PROTECTED] __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/
RE: bugs in @page extends=.... in Orion implementation?
Can you elaborate on how you are using XSL and XSLT ... I assume you're using Tag libraries but can you show an example of HTML markup derived from XML? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Daniel Lopez Sent: Wednesday, May 30, 2001 6:05 AM To: Orion-Interest Subject: Re: bugs in @page extends= in Orion implementation? Hi, I've also used filters, but in this case to filter requests by IP, as I don't want certain IP's to be able to access certain URLs. On the other hand, I implemented security, logging and other features inside my own servlet Controller, following a Model 2 approach. I thought about externalizing this services as filters, but that would mean that the web.xml file will grow too much and that I would have to put too much things in the request object each time. It's not that I've discarded the idea, but I don't see any compelling reason to implement everything as filters. We don't use servlets, but ONE controller servlet and action classes and we use JSP as view-only, creatures (actually, we seldom use them as we use XML/XSLT), so as anyway all the requests go through my controller servlet... We implemented IP filtering as a filter because we also wanted to use it in other applications, as well as with static content. Just my 2c, D. --- Daniel Lopez Janariz ([EMAIL PROTECTED]) Web Services Computer Center Balearic Islands University --- Marcel Schutte wrote: Hi Randahl, I've used a filter to do gzip encoding for specific file types. Starting with the tutorial at http://www.orionserver.com/tutorials/filters/lesson5/, I've changed some things to get the hang of it and also to reduce the amount of buffering used. It works fine, haven't had a problem with this (intranet)site. The beauty of filters is that they are completely independent from your application, just edit your web.xml and you are set. Let me know if you wnat some more info. Marcel -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Randahl Fink Isaksen Sent: Wednesday, May 30, 2001 9:39 AM To: Orion-Interest Subject: RE: bugs in @page extends= in Orion implementation? Hi Marcel I looked it up, and I definately see your point about the filter mechanism. Have you any experience with this on Orion? Does it work well? And what have you used it for? Of course if anyone else have tried it out, I would very much like to hear from you too. Yours Randahl -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Marcel Schutte Sent: 30. maj 2001 00:22 To: Orion-Interest Subject: Re: bugs in @page extends= in Orion implementation? That's right, the two examples Randahl gives can be easily solved using the servlet2.3 filter mechanism, giving a very loose coupling of these features with your actual application. Marcel - Original Message - From: Juan Lorandi (Chile) [EMAIL PROTECTED] To: Orion-Interest [EMAIL PROTECTED] Sent: Tuesday, May 29, 2001 10:45 PM 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
RE: bugs in @page extends=.... in Orion implementation?
Sure I will be happy to. The project I was involved in they factored a load of code in the JSP servlet superclass and I found that when I wanted access to this code via a servlet that it was impossible. Factoring code into the superclass is only useful if you've made the decision to only access this code from within your JSP pages at runtime. Sure there are many ways to architect this properly but reusing code factored into the superclass outside of a JSP pages is very difficult and putting such code in the superclasses encourages the use of scriptlets in the JSP code. Always a bad idea. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Randahl Fink Isaksen Sent: Tuesday, May 29, 2001 12:03 AM To: Orion-Interest Subject: RE: bugs in @page extends= in Orion implementation? Well, Robert, would you elaborate on those thoughts? R. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Robert Nicholson Sent: 23. maj 2001 04:51 To: Orion-Interest Subject: RE: bugs in @page extends= in Orion implementation? Factoring code into the jsppage superclass is a bad idea. You will regret this later. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of SCOTT FARQUHAR Sent: Tuesday, May 22, 2001 5:53 PM To: Orion-Interest Subject: Re: bugs in @page extends= in Orion implementation? 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 be part of the spec. Scott [EMAIL PROTECTED] 05/23/01 05:42am I create a class called JSPBase class which extends OrionHttpJspPage, and I put the @ page extends=packagename.JSPBase in my JSP file. however, orion give the following error: Superclass of the JSP page does not implement Servlet, invalid extends attribute. Does orion implement @page extends correctly? Any clarification? -Jiuyun __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
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 be part of the spec. Scott [EMAIL PROTECTED] 05/23/01 05:42am I create a class called JSPBase class which extends OrionHttpJspPage, and I put the @ page extends=packagename.JSPBase in my JSP file. however, orion give the following error: Superclass of the JSP page does not implement Servlet, invalid extends attribute. Does orion implement @page extends correctly? Any clarification? -Jiuyun __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ = Jiuyun Wang M.Sc. of Computer Sciences Sun Certified Programmer for Java 2 Platform IBM Certified Solution Enterprise Developer Phone: 919-696-0419(cel) Email: [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
RE: bugs in @page extends=.... in Orion implementation?
Well, Robert, would you elaborate on those thoughts? R. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Robert Nicholson Sent: 23. maj 2001 04:51 To: Orion-Interest Subject: RE: bugs in @page extends= in Orion implementation? Factoring code into the jsppage superclass is a bad idea. You will regret this later. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of SCOTT FARQUHAR Sent: Tuesday, May 22, 2001 5:53 PM To: Orion-Interest Subject: Re: bugs in @page extends= in Orion implementation? 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 be part of the spec. Scott [EMAIL PROTECTED] 05/23/01 05:42am I create a class called JSPBase class which extends OrionHttpJspPage, and I put the @ page extends=packagename.JSPBase in my JSP file. however, orion give the following error: Superclass of the JSP page does not implement Servlet, invalid extends attribute. Does orion implement @page extends correctly? Any clarification? -Jiuyun __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
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 be part of the spec. Scott [EMAIL PROTECTED] 05/23/01 05:42am I create a class called JSPBase class which extends OrionHttpJspPage, and I put the @ page extends=packagename.JSPBase in my JSP file. however, orion give the following error: Superclass of the JSP page does not implement Servlet, invalid extends attribute. Does orion implement @page extends correctly? Any clarification? -Jiuyun __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ = Jiuyun Wang M.Sc. of Computer Sciences Sun Certified Programmer for Java 2 Platform IBM Certified Solution Enterprise Developer Phone: 919-696-0419(cel) Email: [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
Re: bugs in @page extends=.... in Orion implementation?
That's right, the two examples Randahl gives can be easily solved using the servlet2.3 filter mechanism, giving a very loose coupling of these features with your actual application. Marcel - Original Message - From: Juan Lorandi (Chile) [EMAIL PROTECTED] To: Orion-Interest [EMAIL PROTECTED] Sent: Tuesday, May 29, 2001 10:45 PM 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 be part of the spec. Scott [EMAIL PROTECTED] 05/23/01 05:42am I create a class called JSPBase class which extends OrionHttpJspPage, and I put the @ page extends=packagename.JSPBase in my JSP file. however, orion give the following error: Superclass of the JSP page does not implement Servlet, invalid extends attribute. Does orion implement @page extends correctly? Any clarification? -Jiuyun __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ = Jiuyun Wang M.Sc. of Computer Sciences Sun Certified Programmer for Java 2 Platform IBM Certified Solution Enterprise Developer Phone: 919-696-0419(cel) Email: [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
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 be part of the spec. Scott [EMAIL PROTECTED] 05/23/01 05:42am I create a class called JSPBase class which extends OrionHttpJspPage, and I put the @ page extends=packagename.JSPBase in my JSP file. however, orion give the following error: Superclass of the JSP page does not implement Servlet, invalid extends attribute. Does orion implement @page extends correctly? Any clarification? -Jiuyun __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ = Jiuyun Wang M.Sc. of Computer Sciences Sun Certified Programmer for Java 2 Platform IBM Certified Solution Enterprise Developer Phone: 919-696-0419(cel) Email: [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
Orion JSP Container bugs in @page extends=.... in Orion implementation?
In JSP 1.1 spec it says, If the JSP page author uses extends, the generated class is identical to the one shown in CODE EXAMPLE 3-2, except that the class name is the one specified in the extends attribute. The contract on the JSP page implementation class does not change. The JSP container should check (usually through reflection) that the provided superclass: · Implements HttpJspPage if the protocol is HTTP, or JspPage otherwise. · All of the methods in the Servlet interface are declared final. Additionally, it is the responsibility of the JSP page author that the provided superclass satisfies: · The service() method of the Servlet API invokes the _jspService() method. · The init(ServletConfig) method stores the configuration, makes it available as getServletConfig, then invokes jspInit. · The destroy method invokes jspDestroy. A JSP container may give a fatal translation error if it detects that the provided superclass does not satisfy these requirements, but most JSP containers will not check them. It seems orion JSP container does not implement in this way, any insider or expert opinion? -Jiuyun --- Jiuyun Wang [EMAIL PROTECTED] wrote: I create a class called JSPBase class which extends OrionHttpJspPage, and I put the @ page extends=packagename.JSPBase in my JSP file. however, orion give the following error: Superclass of the JSP page does not implement Servlet, invalid extends attribute. Does orion implement @page extends correctly? Any clarification? -Jiuyun __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ Jiuyun Wang M.Sc. of Computer Sciences Sun Certified Programmer for Java 2 Platform IBM Certified Solution Enterprise Developer Phone: 919-696-0419(cel) Email: [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
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 be part of the spec. Scott [EMAIL PROTECTED] 05/23/01 05:42am I create a class called JSPBase class which extends OrionHttpJspPage, and I put the @ page extends=packagename.JSPBase in my JSP file. however, orion give the following error: Superclass of the JSP page does not implement Servlet, invalid extends attribute. Does orion implement @page extends correctly? Any clarification? -Jiuyun __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ = Jiuyun Wang M.Sc. of Computer Sciences Sun Certified Programmer for Java 2 Platform IBM Certified Solution Enterprise Developer Phone: 919-696-0419(cel) Email: [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
RE: bugs in @page extends=.... in Orion implementation?
Factoring code into the jsppage superclass is a bad idea. You will regret this later. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of SCOTT FARQUHAR Sent: Tuesday, May 22, 2001 5:53 PM To: Orion-Interest Subject: Re: bugs in @page extends= in Orion implementation? 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 be part of the spec. Scott [EMAIL PROTECTED] 05/23/01 05:42am I create a class called JSPBase class which extends OrionHttpJspPage, and I put the @ page extends=packagename.JSPBase in my JSP file. however, orion give the following error: Superclass of the JSP page does not implement Servlet, invalid extends attribute. Does orion implement @page extends correctly? Any clarification? -Jiuyun __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
