Lionel Siau wrote:
Hi,
I've recently installed a2 on a tomcat(3.2.2) with no other apps. The installation is
fine but over time, I have noticed the mem allocation for the JVM of tomcat serving
jetspeed seems to rise over time. The memory size required is a function of the
activity of the
I not sure how to resolve my error (same one as my original message - see
below). When I browse to the /build directory I can see all the files and
all are executable. I am looged in as 'root' and thus should be able to
execute any script. When trying to execute ./build.sh webapp it tells me
This whole area of security and customization is not yet completed.
I believe Santiago was interested in finishing the work there, right? :)
-Original Message-
From: Paul Spencer [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 08, 2001 9:11 AM
To: [EMAIL PROTECTED]
Subject:
How do you configure the portlets that are first displayed, before you login.
I'd like to display the login portlet when a user first hit's the portal.
Jim
See the following:
http://www.mail-archive.com/jetspeed-user@jakarta.apache.org/msg01087.html
Paul Spencer
Jim O'Connor wrote:
How do you configure the portlets that are first displayed, before you login.
I'd like to display the login portlet when a user first hit's the portal.
I was wondering if there is a way to set up user groups in Jetspeed? I would
like to set up different groups of users with different permissions(certain
groups view certain portlets), from what I have read in the docs groups
arent supported yet(if so is this because of turbines db limitations as
It means that we are still working on it. The security code is in place, we
just need to add some permission checks to the customizer, thats all.
1.3a1 has no security, so going back to it won't do you any good wrt
security
-Original Message-
From: Chris McDaniel [mailto:[EMAIL
Graham,
Within Jetspeed user have roles. Roles have permissions. Portlet and
parameters can be associated to roles via the element security
role=myRole. You can see an example of this in the RSS entry in
portlets.xreg. As you suspected, the implementation is complete.
Their has been some
While I see the value of portlet-level control, it exceeds my current
*needs* - not to mention my technical abilities to fix it myself ;) If I
could change the control's template, it would be sufficient.
The default layout seemed a bit busy to me - especially when the
action-icons will only
