At 09:04 24/07/2001 -0700, you wrote: > > However, as soon as I use RequestDispatcher.include(...) > > methods in my > > servlet, to redirect the output toward a JSP, > > I receive an exception in Jetspeed's log, which is displayed on the > > jetspeed screen... > >So if I understand you correctly (my apologies if I do not), you have a >portlet, which includes a servlet, which then includes another another >servlet (a JSP). Exactly. The traditionnal servlet-JSP scenario. > Jetspeed shouldn't impose any limits there. Could you send >us some small code examples? Yes; there you are. content of the archive: /src --> contains the source code of the "faulty" servlet. /conf --> contains the local-portlets.xreg file, with an entry for my portlet. /psml/anon/html --> contains the "default.psml" file, modified to include my portlet. ( in a "tab" called "ProblemPortlet") / --> contains a .jsp file, very simple. >Are you using the cvs head or the 1.3a1 release? latest CVS ( made an "update" two days ago) ( If my example works in the latest stable release (which is?), I would switch with pleasure... thanks a lot for helping, NOTE: something amazing: I made the test under Resin, just for the fun, and it actually worked!!!!! May it be a Tomcat-3.2.2 bug???? Or is resin handling badly the servlets specs??? I am confused. Tomcat-3.2.2 is supposed to be a stable release, isn't it? It could be interesting to test that sample with the latest tomcat release... Stan.
servletinvoker_problem_example.zip
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
