I'm not sure I understand what you're trying to do, but I just noticed
that at the top of ServletTagHandler.java there's a comment that says
this:
/* TODO:
* (from Tim Williams, [EMAIL PROTECTED]:)
* - Support "CODEBASE" servlet tag, allowing remote loading of servlets
* - Make "NAME" parameter work for symbolic names, not just "CODE"
* - Integrate functionality with James' modifications
([EMAIL PROTECTED])
*/
So I guess CODEBASE isn't supported yet.
-Nissim
"Marche, Marie-Odile" wrote:
>
> Hello
>
> Here is a little mail concerning a slightly different subject than session
> and JSSI (although it is certainly very useful, but I don't use the Session
> object yet).
>
> You seem to be very much involved in the JSSI development, so I take this
> opportunity to ask you a very specific question about the <servlet> tag:
> - is it possible to specify a target servlet zone inside this tag (I
> want to call a servlet which exists in several servlet zones and would like
> to be able to give the servlet zone in addition to the servlet path
> -> is there a way to do this?
> Another JSSI user advised me to use the "CODEBASE" attribute of the SERVLET
> tag , but it gave me no result.
>
> Thanks for your attention,
>
> Marie-odile, France.
>
> > -----Message d'origine-----
> > De: Nissim Karpenstein [SMTP:[EMAIL PROTECTED]]
> > Date: mardi 24 ao�t 1999 23:03
> > �: [EMAIL PROTECTED]
> > Objet: Passing Session to JSSI included servlets
> >
> > Hi,
> >
> > I want to add a feature to JSSI, and I want to know if it's a bad idea.
> > I want to be able to access the session from a servlet that's called
> > through the <SERVLET> tag. I've found that since the SSI servlet
> > already wrote output to the response, request.getSession() always
> > returns a new session in such servlets.
> >
> > Here's my idea for a solution...please comment.
> >
> > I was thinking that we can have the SSI servlet get the Session before
> > writing any output. Then, when calling a servlet from the <SERVLET> tag
> > it can check (through reflection) if there's a method
> > service(ServletRequest, ServletResponse, HttpSession), and if there is,
> > call that, and pass it the session, otherwise, call the standard
> > service() method. It could also be done by making an abstract class
> > which extends GenericServlet, and has the additional method, and then we
> > can check with instanceOf rather than using reflection.
> >
> > Let me know if this is an OK idea as I will implement it.
> >
> > Cheers,
> >
> > -Nissim
> >
> >
> > ------------------------------------------------------------
> > To subscribe: [EMAIL PROTECTED]
> > To unsubscribe: [EMAIL PROTECTED]
> > Problems?: [EMAIL PROTECTED]
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
