lly doesn't get you much but almost always requires you to bind
> >>>>>> yourself very closely with the specific implementation of the JSP
> >>>>>> engine.
> >>>>>>
> >>>>>> It would be far better to use typical M
ge class:
package dashboard.web.page;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.jsp.PageContext;
import org.petitecloud.util.PetiteCloudNullException;
// making this extend the right subclass plus working page
extends="" would mean zero in-line Java
// Copyrigh
to the request attributes. Then forward
> >>>> your request to your JSP to produce the response content. This will be
> >>>> much more straightforward and you will have fewer problems like this,
> >>>> where expected behavior is confused by all th
// the setAttributes in our ctx
new Page(pageContext);
%>
<%@include file="/widgets/scripts/scripts.jsp"%>
and the Page class:
package dashboard.web.page;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.jsp.PageContext;
use case which the following working
> > example below should make more clear:
> >
> >
> > <%@page import="dashboard.web.page.Page"%>
> > <%
> > // THIS WOULD NOT BE NEEDED if <%@page extends="..."%&g
ile="/widgets/scripts/scripts.jsp"%>
and the Page class:
package dashboard.web.page;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.jsp.PageContext;
import org.petitecloud.util.PetiteCloudNullException;
// making this extend the right subclass plus working page
exte
ile="/widgets/scripts/scripts.jsp"%>
and the Page class:
package dashboard.web.page;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.jsp.PageContext;
import org.petitecloud.util.PetiteCloudNullException;
// making this extend the right subclass plus working page
exte
ld make more clear:
<%@page import="dashboard.web.page.Page"%>
<%
// THIS WOULD NOT BE NEEDED if <%@page extends="..."%> worked
//
// for now we don't need to keep the page object just
// the setAttributes in our ctx
new
Aryeh,
On 9/9/23 19:36, Aryeh Friedman wrote:
On Sat, Sep 9, 2023 at 1:23 PM Mark Thomas wrote:
On 09/09/2023 11:52, Aryeh Friedman wrote:
Every other jsp in my webapp (and other webapps on the same tomcat
instance [9.0.75]) works and I am using a the default container but as
On Sat, Sep 9, 2023 at 1:23 PM Mark Thomas wrote:
>
> On 09/09/2023 11:52, Aryeh Friedman wrote:
> > Every other jsp in my webapp (and other webapps on the same tomcat
> > instance [9.0.75]) works and I am using a the default container but as
> > curl/catalina.out show BasePage is *NEVER* being
On 09/09/2023 11:52, Aryeh Friedman wrote:
Every other jsp in my webapp (and other webapps on the same tomcat
instance [9.0.75]) works and I am using a the default container but as
curl/catalina.out show BasePage is *NEVER* being called (either the
_jspService() or the getX()):
How have you
--Ursprüngliche Nachricht-
> > Von: Aryeh Friedman
> > Gesendet: Samstag, 9. September 2023 12:57
> > An: Tomcat Users List
> > Betreff: Re: page extends not working???
> >
> > Oops forgot to include the full log see below replaced inline
> >
>
Hello,
> -Ursprüngliche Nachricht-
> Von: Aryeh Friedman
> Gesendet: Samstag, 9. September 2023 12:57
> An: Tomcat Users List
> Betreff: Re: page extends not working???
>
> Oops forgot to include the full log see below replaced inline
>
> On Sat, Sep 9, 202
Oops forgot to include the full log see below replaced inline
On Sat, Sep 9, 2023 at 6:52 AM Aryeh Friedman wrote:
>
> Every other jsp in my webapp (and other webapps on the same tomcat
> instance [9.0.75]) works and I am using a the default container but as
> curl/catalina.out show BasePage is
Every other jsp in my webapp (and other webapps on the same tomcat
instance [9.0.75]) works and I am using a the default container but as
curl/catalina.out show BasePage is *NEVER* being called (either the
_jspService() or the getX()):
package dashboard.web.pages;
import java.io.IOException;
15 matches
Mail list logo
