AW: controlling portlet caching in jetspeed 1.5

2005-02-11 Thread Sven Thiergen
Hi,

I have got some further questions about caching strategy regarding Portlets
and Portals. BTW, I use J2.

When multiple Portlets get displayed on a page, it would speed up the Portal
if only the portlet whereupon a user interaction happened gets updated. The
other Portlets may cache their state in that simply their HTML fragment (or
whatever the output format is) gets stored in a persistence layer. The
Portal may take responsibility for this (and should, in fact, if one thinks
about it more deeply) by providing a configurable framework to do this.

Rendering all Portlets on a page, even though only one got updated,
obviously costs performance. On the other hand, all Portlets get displayed
in their current state when the rendering request gets delegated to each of
them.

But then again, we often have the nasty situation that the user enters data
in different Portlets, one Portlet gets updated, all Portlets render but the
entered data may be lost in some or all of them, since the Portlets did not
cache the user input properly.

Hint: I found a WebSphere White Paper which introduced a thing called
Dynacache which is able to store HTML snippets from Portlets/Servlets.

Here my questions:

1. Are there any resources available, where the raised problems are
discussed on a general based. I.e. is it a helpful thing to cache Portlet
states at all? If not: Why?

2. What does the portlet specification says about this, or does it leave
this subject open to the concrete Portal implementation?

3. How does J2 supports Portlet caching? Are there any cache strategies in
control, already? Is there anything planned in the near or far future, or:
Is there a certain strategy J2 developers and users should have in mind to
comply with what's already there or planned?


So this quite a lot asked, I know. Any help is very welcome.
Thank you, Sven.


 Hi folks,

 I am looking into portlet caching a bit in Jetspeed 1.5.  We have some
 portlets, all subclasses of VelocityPortlet.  The data they pull (from
 an oracle database) is mostly static, but there are some times where
 data changes, and we'd like the portlets to reflect that.  All of these
 portlets are marked as cacheOnValue, cacheOnName in the registry.

 I can tell that the data layer is getting the new data because we have
 a search portlet and the results correspond to the changed data.
 However, other display portlets don't reflect the changed data until
 the server is restarted.

 I spend some time in the js1.5 source (thanks, koders.com) and found
 that VelocityPortlets are cacheable by default.

 A couple of questions:

 1.  Can I refresh the portlet cache without restarting my servlet
 container?

 2.  I was able to find reference to an expiration time in millisecods
 (in AbstractPortlet) but didn't see that in the configuration files,
 and couldn't find a default value.  Is there one?

 3.  I think that all that happens after portlets are stale (epxired) is
 that their refresh method is called.  Is that true?

 4.  I'm thinking that turning off cacheOnValue might be a fix for our
 situation.  Does that make sense?

 Thanks,
 Dan


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Problem in creating the Users

2005-02-11 Thread Pradeep

Hello
 
I have configured Jboss 4.0.1 and Jetspeed 2.0 and I was able to login and
view my administrative portlets, but if I create
some new users and try to login with the new user, it is telling invalid
user name and password, but I could see the new user in the database.It
accepts only the default users i.e admin,manager, user. but not the new
users created, I have checked the AUTH_FAILURES in the table
SECURITY_CREDENTIAL it is '0' only.
 
If I try to change the admin password ,it shows that password is changed but
if I try to login with new password it shows invalid password but it takes
my old password.
 
kindly show the way out from this problem
 
regards,
 
Pradeep




Confidentiality Notice 

The information contained in this electronic message and any attachments to 
this message are intended
for the exclusive use of the addressee(s) and may contain confidential or 
privileged information. If
you are not the intended recipient, please notify the sender at Wipro or [EMAIL 
PROTECTED] immediately
and destroy all copies of this message and any attachments.

RE: controlling portlet caching in jetspeed 1.5 (2.0)

2005-02-11 Thread Frank Villarreal
Hi Sven,


 -Original Message-
 From: Sven Thiergen [mailto:[EMAIL PROTECTED]
 Subject: AW: controlling portlet caching in jetspeed 1.5

 When multiple Portlets get displayed on a page, it would speed up
 the Portal if only the portlet whereupon a user interaction happened gets
 updated. The other Portlets may cache their state in that simply their
HTML
 fragment (or whatever the output format is) gets stored in a persistence
layer. The
 Portal may take responsibility for this (and should, in fact, if
 one thinks about it more deeply) by providing a configurable framework to
do this.

Before working with Jetspeed, I had written my own non-compliant portal,
and what you describe is EXACTLY the strategy I took for implementing
caching ... it seemed to make the most sense ... at least performance wise.

 Here my questions:

 1. Are there any resources available, where the raised problems are
 discussed on a general based.

http://community.java.net/portlet/


 2. What does the portlet specification says about this, or does it leave
 this subject open to the concrete Portal implementation?

I'm not an expert ... but to the best of my knowledge, I think it leaves it
open.  If someone else knows otherwise, please correct me ...


 3. How does J2 supports Portlet caching? Are there any cache strategies in
 control, already? Is there anything planned in the near or far future, or:
 Is there a certain strategy J2 developers and users should have in mind to
 comply with what's already there or planned?

There is a setting in the portlet application deployment descriptor (from
the spec) named expiration-cache/ ... I think this is supposed to be a
timer setting to specify the length a portal implementation may or may not
cache the content of a given portlet.  I'm not sure if Jetspeed2 has
implemented this or not ... any J2 developers out there know if this is
functional yet???  If so, does a value of -1 indicate that content should
not be cached at all?


- Frank


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Using three column layout in Jetspeed 2

2005-02-11 Thread Satyabrata.Dash
I am trying to configure a 3 column layout in Jetspeed-2. I am attaching my 
psml file here. I would expect to see three columns in the page layout, but it 
still renders the page with two columns 50% each. Is there any other 
configuration that i need to take care of?

Does the fragment id has any significance or it just need to be an unique id? 

--
?xml version=1.0 encoding=UTF-8?
page id=/default-page.psml hidden=false
security-constraints
security-constraints-refpublic-view/security-constraints-ref
/security-constraints
titleWelcome to Dashboard/title
short-titleWelcome to Dashboard/short-title
defaults skin=orange layout-decorator=simple 
portlet-decorator=tigris/
fragment id=dp-1 type=layout name=jetspeed::VelocityThreeColumns
fragment id=dp-3 type=portlet name=pam::LocaleSelector
property name=row value=0 layout=ThreeColumns/
property name=column value=0 layout=ThreeColumns/
/fragment
fragment id=dp-12 type=portlet name=security::LoginPortlet
property name=row value=0 layout=ThreeColumns/
property name=column value=1 layout=ThreeColumns/
/fragment
fragment id=dp-7 type=portlet name=demo::PickANumberPortlet
property name=row value=0 layout=ThreeColumns/
property name=column value=2 layout=ThreeColumns/
/fragment
fragment id=dp-16 type=portlet name=demo::RoleSecurityTest
property name=row value=1 layout=ThreeColumns/
property name=column value=0 layout=ThreeColumns/
/fragment
fragment id=dp-9 type=portlet name=demo::IFramePortlet
property name=row value=1 layout=ThreeColumns/
property name=column value=1 layout=ThreeColumns/
/fragment
fragment id=dp-17 type=portlet name=demo::UserInfoTest
property name=row value=1 layout=ThreeColumns/
property name=column value=2 layout=ThreeColumns/
/fragment
fragment id=dp-18 type=portlet name=demo::BookmarkPortlet
property name=row value=2 layout=ThreeColumns/
property name=column value=0 layout=ThreeColumns/
/fragment
fragment id=dp-23 type=portlet name=dashboard::DashboardPortlet
property name=row value=2 layout=ThreeColumns/
property name=column value=1 layout=ThreeColumns/
/fragment
/fragment
/page
--

Regards
Satya

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: JFreeChart and JetSpeed2

2005-02-11 Thread Satyabrata.Dash
I figured this out. CeWolf tag library creates an image tag like img 
src=/context/..., and then a new request is made to tomcat to render the 
chart. My portlet and chart tag libraries are packaged in a different webapp 
and therefore, the sessions are also different.

One solution is perhaps to deploy my portlet and JetSpeed in one webapp, but I 
think I will keep them separate just to keep them clean and then figure out an 
inter webapp communication mechanism to render the chart.

Regards
Satya

-Original Message-
From: Satyabrata Dash 
Sent: Thursday, February 10, 2005 10:14 PM
To: jetspeed-user@jakarta.apache.org
Subject: JFreeChart and JetSpeed2


Hi,

I am trying to use CeWolf and JFreeChart packages within JetSpeed2 Portlets. 
The image never gets rendered and I get The Chart has expired and please 
reload error. When I debugged this error message, I found that somehow the 
session object used by renderer is different. So the image is never found in 
session object in the renderer code.

Has anyone else ever run into similar issues?

Regards
-Satya

-
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]