You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Pochat Jerome <jp...@axway.com> on 2004/09/06 14:17:34 UTC
RE : CC/PP
Composite Capability/Preference Profiles ?
http://www.w3.org/TR/2004/REC-CCPP-struct-vocab-20040115/
-----Message d'origine-----
De : Pramod Jain [mailto:pramod@indent.org]
Envoyé : lundi 6 septembre 2004 14:09
À : Jetspeed Users List
Objet : RE: CC/PP
what is CC/PP?
-----Original Message-----
From: Federica Fantini [mailto:f.fantini@comune.re.it]
Sent: Monday, September 06, 2004 4:57 AM
To: jetspeed-user@jakarta.apache.org
Subject: CC/PP
Hi,
I'm a student in computer engineering at Parma University, in Italy.
For my degree thesis I'm trying to implement a basic support for CC-PP
for Jetspeed.
Do you have any suggestion?
Which files and classes do I have to modify or to examine?
Any help would be appreciated.
Thank you in advance
Federica Fantini
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
RE: Portlets execution flow
Posted by Oscar Ruiz <os...@gtd.es>.
Hi all,
guess you are talking about velocity templates here.
But, how can i do the same with a JSP template?, I cannot get the event
executed before any buildNormalContext of any portlet.
The following does not work:
<form method="post" action="<jetspeed:dynamicUri/>">
<input type="hidden" name="js_peid" value="<%=jspeid%>">
<input type="hidden" name="action" value="portlets.myJspPortletAction"/>
<input type="submit" name="eventSubmit_doUpdate" value="Save"/>
Thanks.
From: Bob Fleischman <bo...@mindspring.com>
Subject: Portlets execution flow
Date: Mon, 16 Aug 2004 00:17:56 -0400
Content-Type: text/plain;
charset="utf-8"
Ahh!! You've discovered one of the 'gotchas' of direct action calls.
When you call an action directly with $jslink.getAction("myaction",
$portlet) the context does not yet contain the portlet and so you can not
use it for getUser or any other Portlet specific call to save state. You
can, however, still impact services, or database connectivity. This approach
will fire the action BEFORE anything else, which seems to be its major
appeal.
I have found it much easier to use a form action of
$jslink.getPortletById($portlet.getID()) with a button name of
"eventSubmit_doUpdate" and then I send other parameters via hidden fields on
the form.
That way I am certain the correct instance of the correct portlet is being
referenced.
Bob
-----Original Message-----
From: Bjorn Vidar Remme [mailto:bjorn.vidar.remme@intentia.no]
Sent: Tuesday, August 10, 2004 4:18 AM
To: Jetspeed Users List
Subject: RE: Portlets execution flow
****Correction*****
The action event does call the public void doBrowse_refresh(RunData,
Context) method.
There was a Null pointer Exeption thrown in there when it tried to fetch
and use the portlet object in the Context .
Apparently this exception caused the rundata only method to be called.
Med vennlig hilsen/Kind regards,
Bjorn Vidar Remme
Application Engineer
Bjorn Vidar Remme
09.08.2004 20:52
To: "Jetspeed Users List" <je...@jakarta.apache.org>
cc:
Subject: RE: Portlets execution flow
Hi Bob,
What you are saying makes sense. The trouble was that I was using
qualified action names, but I still had major problems. I then reluctantly
came to the conclusion that there was something fundamentally wrong with
my code.
Looking over the code again I remember changing the form method from POST
to GET because my action event would not fire if I used POST. A major
mistake! Changing the method caused the action parameter in the URL to be
ignored. And the code executed as if I where using $jslink alone.
It took me a while to figure out what was going on. Overriding the
executeEvents() methods and logging any Exceptions thrown gave me the
answer. When I supply an action in the URL it looks for an event method
with the signature 'public void doBrowse_X(RunData rundata)' and not
'public void doBrowse_refresh(RunData, Context)'.
No wonder my event was not triggered because I used the Context variation.
I then changed my code and it worked just as you said. Brilliant!
The only consequence of removing the Context as a parameter is that we
must find an alternative way to get the portlet id. Probably submitting it
as a parameter.
Thanks, you really saved the day!!!
Kind regards,
Bjorn Vidar Remme
"Bob Fleischman" <bo...@mindspring.com>
06.08.2004 18:18
Please respond to "Jetspeed Users List"
To: "'Jetspeed Users List'" <je...@jakarta.apache.org>
cc:
Subject: RE: Portlets execution flow
Bjorn:
You can limit the impact of which class runs your method via the action by
qualifying the action.
That is: use action=Myportlet2.doUpdate rather than action=doUpdate. With
the second method any portlet which has a doUpdate method will fire.
As to having several Portlets share a current model. We have found that it
is best to have a separate action class that modifies the model. Then
using
the setAction style described in this thread you can update the common
model
first. That action will be called before any rendering.
Your portlet should then be limited to building up your context. Otherwise
you are duplicating your efforts by putting model update code in 2 places.
Bob
-----Original Message-----
From: Bjorn Vidar Remme [mailto:bjorn.vidar.remme@intentia.no]
Sent: Friday, August 06, 2004 10:41 AM
To: Jetspeed Users List
Subject: Re: Portlets execution flow
Hi all,
Well the trouble by using setAction() is that the action is executed for
all the portlets (if a suitable method exists). You can easily test this
by adding multiple instances of the same portlet to a page (same action
class) or multiple portlets with different action classes but the same
event name. You will then see that the action event is executed once for
all the portlets.
The pattern is thus (AE=action event, BNC=buildNormalContext):
AE for portlet A, BNC for portlet A, AE for portlet B, BNC for portlet B
etc..
Not what we want at all, we just want the action event to fire once.
This is why I specify the portlet ID in the action like this:
$jslink.getAction("myaction", $portlet)
The action event is then executed only once, but as I described in my
previous post the pattern is (clicking on portlet B): BNC-A, AE -B, BNC-B
and not the desired AE-B, BNC-A, BNC-B.
Note: I am using getAction() because setAction() is deprecated according
to the documentation. It does the same thing.
Kind regards,
Bjorn Vidar Remme
OlsonE@lakeviewtech.com
06.08.2004 15:54
Please respond to "Jetspeed Users List"
To: "Jetspeed Users List" <je...@jakarta.apache.org>
cc:
Subject: Re: Portlets execution flow
Bjorn, Oscar -
I have never seen the problems you are mentioning below - my action
handler methods ALWAYS execute before the build*() methods on the active
portlets. We are currently using Velocity-based portlets. When we
specify the action parameter in a form, we use the following code
template:
<form method="post" action="$jslink">
or
<form method="post" action="$jslink.setAction("portlets.FooAction")">
The first version uses the "default" action as specified in the xreg for
the portlet - this is what we use in most cases. The second version uses
any action you specify - as long as the action package you are using is
declared to Turbine using the "module.packages" key (see
TurbineResources.properties, and look for that key.)
For an example of the first version, look at the source in
/tutorial/tutorials/9/templates/vm/portlets/html/coffees-browser.vm
(directly from cvs) as well as the related xreg files. An example of the
second version is at:
http://portals.apache.org/jetspeed-1/tutorial/7/events.html.
Good luck,
Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org