if the container allows it. From the help -
"In a security conscious environment, the servlet container may return null
for a given URL"
I should have said 'to reliably achieve this'
Kevin Jones
DevelopMentor
www.develop.com
> -----Original Message-----
> From: A mailing list for discussion about Sun Microsystem's Java Servlet
> API Technology. [mailto:[EMAIL PROTECTED]]On Behalf Of Nic
> Ferrier
> Sent: 16 September 2000 17:14
> To: [EMAIL PROTECTED]
> Subject: Re: RequestDispatcher Function
>
>
> >>> Kevin Jones <[EMAIL PROTECTED]> 14-Sep-00 10:06:18 AM >>>
>
> >The simulation may work but this isn't going to work out
> >in the real world - you can't forward or include across
> >applications (sites as you call them). The RequestDispatcher
> >will only work between resources within the same application
> >(i.e. within the same ServletContext), you'll need to use some
> >other B2B technique to achieve this,
>
> RequestDispatcher WILL work across web-applications deployed under
> the same servlet container.
>
> You simply have to call getContext() first.
>
>
> Nic
>
> __________________________________________________________________
> _________
> To unsubscribe, send email to [EMAIL PROTECTED] and include
> in the body
> of the message "signoff SERVLET-INTEREST".
>
> Archives: http://archives.java.sun.com/archives/servlet-interest.html
> Resources: http://java.sun.com/products/servlet/external-resources.html
> LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
