The same Struts Portlet, rendered multiple time on the same page

[Sven Thiergen <s....@itcampus.de>]

Hi,

what happens if I have the same Struts Portlet rendered multiple times on
just one page? We had some tests and both Portlets synchroniously changed
their state and called the same Struts action. So the Struts Bridge does not
hold a truly instantiated "Struts context" for each Struts Portlet called, I
suppose, but only one "Struts context" for each Struts application. Is that
right?

Furthermore, we did quite a hack to invoke a portlet while processing
another portlet (getting the suiting PortletInvoker for the portlet we want
to control. We delegate all incoming "action" and "render" requests). If the
so invoked portlet is a Struts Portlet, that is displayed "normally" a
second time somewhere else on the page, request attribute parameters set in
the servlet behind the Struts action get displayed correctly only in the
"invoked" portlet. In the "normally" displayed Struts Portlet they do not
exist.

All subsequent actions however, lead to correct behaviour. Set request
attributes were visible in all running instances of the Struts Portlet.

Thank you for any comment,
Sven.

PS: Hints and suggestions how to do all this in better way, are welcome.


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org

LDAP Authentication problem

[Sabine Winkler <wi...@oio.de>]

hi there,

we've tried out to configure J-2 (M3) working with LDAP.
We had to make some changes because the default configuration described
within the docs does not work.
the ldap.properties will not be loaded before loading the LDAP beans from
srping.
so we added the props to the jetspeed.properties.

within the security-spi-ldap-atn.xml also are some mistakes (wrong package
statements, maybe wrong class
defintion) see att to find out what we've changed.

after starting J-2 everything works fine until trying out to login with e.g.
manager and so on.
nothing happens. only an error message with "invalid user..." occures.

may be some of the developers or somebody else who tried it out can tell us
what is wrong ?

thx

Re: The same Struts Portlet, rendered multiple time on the same page

[Th...@nepatec.de]

hi !

to the first i can say following:

if you have 1 struts-portlet-appliactions rendered multiple times in 
portal-site you   will get always the same content. that is right.  the 
struts-context will be saved after the action request for all following 
render requests - in the session !!!  so both portlets will send a 
render-request, but the session-object from both will be equal - so both 
will get the  same rendercontext...

the second i have to read some times more....


thomas






Hi,

what happens if I have the same Struts Portlet rendered multiple times on
just one page? We had some tests and both Portlets synchroniously changed
their state and called the same Struts action. So the Struts Bridge does 
not
hold a truly instantiated "Struts context" for each Struts Portlet called, 
I
suppose, but only one "Struts context" for each Struts application. Is 
that
right?

Furthermore, we did quite a hack to invoke a portlet while processing
another portlet (getting the suiting PortletInvoker for the portlet we 
want
to control. We delegate all incoming "action" and "render" requests). If 
the
so invoked portlet is a Struts Portlet, that is displayed "normally" a
second time somewhere else on the page, request attribute parameters set 
in
the servlet behind the Struts action get displayed correctly only in the
"invoked" portlet. In the "normally" displayed Struts Portlet they do not
exist.

All subsequent actions however, lead to correct behaviour. Set request
attributes were visible in all running instances of the Struts Portlet.

Thank you for any comment,
Sven.

PS: Hints and suggestions how to do all this in better way, are welcome.


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org