This is very urgent one. I am expecting any ones reply.
I think, its default not allowed. Use this:
<session-config> <distributed>true</distributed> </session-config>
in the jboss-portlet.xml.
i found this in the jboss portal reference guide, so iam not sure if it solve the problem.
First, as an FYI: it usually doesn't help get responses to your forum requests by explaining the urgency of your problem. If someone has time to help, they will.
Second, the problem you're seeing is a result of setting a session attribute in the portal-server.war web application and trying access it from your custom portlet WAR web application. These sessions aren't implicitly shared.
Also, I'm not sure if you'd want to write custom code (especially setting session values in a JSP) to store/access user information. Is there a problem with using the standard JAAS principal?
Note that Fuchs's solution mentioned below enables session-replication for setting up JBoss Portal in a clustered environment; it does not solve the problem of attempting to access session attributes across web applications.
Excuse me, you right apemberton. I didnt saw, that the session-config is only for cluster environments.
I also use the JAAS principal.
No worry, fuchs - just trying to be helpful. =)
Hi friends , I got the solution from your help
renderRequest.getUserPrincipal() - this code is solved my problem
but previously I used
"Principal principal = (Principal)request.getAttribute"org.jboss.portal.header.PRINCIPAL");" , so I got only null value.
Fuchs - I tried using
in the jboss-portlet.xml, but i cant get the session attributes across web applications.
Thankyou apemberton and Fuchs..