David,
I don't know if I have missed something. I have assumed that when we add
a ServletInvokerPortlet entry into the registry and add it into the
layout, then everything runs with servlets, hence all the output comes
from out.println()s. If I have JSP or Velocity, then it no longer
becomes a servlet portlet, right?
If I have the following velocity template as a velocity portlet,
<form action="${jlink}/servlets/foobar" method="post">
Name: <input name="text" size="30" /><br/>
Email:<input name="text" size="30" /><br/>
<input type="submit" value="Submit" />
</form>
and click on submit, then the servlet portlet wouldn't replace this
velocity macro. It would only work if the servlet portlet is on the same
page with this velocity portlet.
I think only thing servlet developers must pay attention is how to
construct a servlet link which I believe should be like:
String jlink = request.getContextPath() + request.getServletPath();
String servlet = "/foo/bar";
String fullpath = jlink + "/servlets" + servlet;
out.println("<a href=\"" + fullpath + "\">another servlet</a>");
This must work for all the Jetspeed installations.
Ozgur
-----Original Message-----
From: David Sean Taylor [mailto:[EMAIL PROTECTED]]
Sent: Saturday, February 02, 2002 2:58 PM
To: Jetspeed Users List
Subject: Re: new ServletInvokerPortlet
> Maybe this would be a compromise right now. I think this is better
than
> the old ServletInvokerPortlet.
yes, ok. Lets see if anyone else wants to comment.
If no one objects then I'll merge the patch
Could you provide me an example using velocity or jsp (instead of
out.println)?
I will include it in the tutorial
Thanks,
David
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
