Thanks for the tip but I think the problem is the goDetails method is never
fired.
I add a line to debug on the jetspeed.log:
public class DominoViewSSO extends JspPortletAction {
....
public void goDetails(RunData data, Portlet portlet) throws Exception
{
Log.debug("Lancio il metodo");
setTemplate(data, "Contact.jsp");
}
and I can't find the "Lancio il metodo" string on the log....
This is my .xreg file:
<?xml version="1.0" encoding="UTF-8"?>
<registry>
<portlet-entry name="TestDomino" hidden="false" type="ref"
parent="JSP" application="false">
<meta-info>
<title>Lotus Domino View Example (JSP)</title>
<description>Lettura da una vista Domino via JSP</description>
</meta-info>
<classname>org.apache.jetspeed.portal.portlets.JspPortlet</classname>
<parameter name="template" value="View.jsp" hidden="true"
cachedOnName="true" cachedOnValue="true"/>
<parameter name="action" value="portlets.DominoViewSSO"
hidden="true" cachedOnName="true" cachedOnValue="true"/>
<media-type ref="html"/>
<media-type ref="wml"/>
<url cachedOnURL="true"/>
<category group="Jetspeed">Domino</category>
</portlet-entry>
</registry>
The Contact.jsp is in the same directory of the other template "View.jsp"
Thanks a lot for your help
Marco Fabbri
----- Original Message -----
From: "Gregory Joseph" <[EMAIL PROTECTED]>
To: "Jetspeed Users List" <[EMAIL PROTECTED]>
Sent: Monday, September 22, 2003 3:26 PM
Subject: RE: Link to a JSP page on a JSPPortlet
the setTemplate method call (or what is done behind the seems) seems to have
this tendency to silently ignore the fact that it could not find your
template. Try catching a NullPointerException after your setTemplate call,
or
do some debugging. If the npex is thrown, it's likely your template wasn't
found. Of course should leave this try/catch(NPEx) on production code, but
that's how I found out something was wrong with my templates names
greg
-----Original Message-----
From: Marco Fabbri [mailto:[EMAIL PROTECTED]
Sent: lundi 22 septembre 2003 15:25
To: Jetspeed Users List
Subject: Re: Link to a JSP page on a JSPPortlet
I removed it and this link is compiled:
http://<server>/jetspeed/portal/user/admin/page/default.psml/media-type/html?
js_peid=P-f7b3f134a5-10000&eventSubmit_goDetails=Save
But the page remains the same...
Where do I wrong?
----- Original Message -----
From: "Gregory Joseph" <[EMAIL PROTECTED]>
To: "Jetspeed Users List" <[EMAIL PROTECTED]>
Sent: Monday, September 22, 2003 2:33 PM
Subject: RE: Link to a JSP page on a JSPPortlet
remove the <input type="hidden" name="action"> from your form. The tutorial
is outdated.
http://www.mail-archive.com/[EMAIL PROTECTED]/msg09649.html
greg
-----Original Message-----
From: Marco Fabbri [mailto:[EMAIL PROTECTED]
Sent: lundi 22 septembre 2003 14:31
To: Jetspeed Users List
Subject: Re: Link to a JSP page on a JSPPortlet
----- Original Message -----
From: "Christophe Lombart" <[EMAIL PROTECTED]>
To: "Jetspeed Users List" <[EMAIL PROTECTED]>
Sent: Sunday, September 21, 2003 10:08 PM
Subject: Re: Link to a JSP page on a JSPPortlet
> Marco Fabbri wrote:
> >Can you send me a jsp action example to use the setTemplate?
> >
> See in the portlet demos, You can expect to find plenty of examples.
> in the action methods : setTemplate(rundata, "...jsp ref...") - more
> info in the javadoc
>
I've searched setTemplate on the jetspeed src and I haven't found many
examples to do it with JSP....
And I try in this way; on the JSP I placed a button (as reported on the
Jetspeed tutorial)
<form method="post" action="<jetspeed:dynamicUri/>">
<input type="hidden" name="js_peid" value="<%=jspeid%>">
<input type="hidden" name="action" value="portlets.DominoViewSSO"/>
<input type="submit" name="eventSubmit_goDetails" value="Save"/>
</form>
and in the DominoViewSSO I typed simply:
public void goDetails(RunData data, Portlet portlet)
{
setTemplate(data, "Contact.jsp");
}
But when I push the button "Save", the page is just reloaded and I see
always the same jsp not Contact.jsp
Can you help me again?
Thanks a lot
Marco Fabbri
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
