Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Discussion" <users@myfaces.apache.org>
Received-SPF: pass (herse.apache.org: local policy)
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C73F1E.E7E0FB95"
Subject: Tomahawk 1.1.5 
Date: Tue, 23 Jan 2007 12:47:17 -0600
Content-Transfer-Encoding: 7bit
Message-ID: 
 <67FE6100D1F7F9409E788F55281503DD0185DC3B@itomae2km08.AD.QINTRA.COM>
Thread-Topic: Tomahawk 1.1.5 
thread-index: Acc/HufLc8cTMbXQQKKb1O4scjYg7g==
Importance: normal
Priority: normal
From: "Sanghavi, Shubhra" <Shubhra.Sanghavi@qwest.com>
To: <users@myfaces.apache.org>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C73F1E.E7E0FB95
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I have implemented tree2 (tomahawk 1.1.5 snapshot) using server side
toggling for my application. The application is working fine on tomcat.
But when the same application is being deployed on weblogic, the session
scoped bean is not maintaining the state. In other words , whenever I
click the node on the tree to see the expanded nodes, the constructor of
backing bean gets called even though it is defined with session scope.
As a result , I am unable to get the expanded tree.
=20
Has anybody faced this issue on weblogic ?
=20
Thanks,
Shubhra

=20


This communication is the property of Qwest and may contain confidential =
or
privileged information. Unauthorized use of this communication is =
strictly=20
prohibited and may be unlawful.  If you have received this communication =

in error, please immediately notify the sender by reply e-mail and =
destroy=20
all copies of the communication and any attachments.

------_=_NextPart_001_01C73F1E.E7E0FB95
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE id=3DridTitle>Blank</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<STYLE>BODY {
	MARGIN-TOP: 25px; FONT-SIZE: 10pt; MARGIN-LEFT: 25px; COLOR: #000000; =
FONT-FAMILY: Arial, Helvetica; BACKGROUND-COLOR: #ffffff
}
P.msoNormal {
	MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-LEFT: 0px; COLOR: #ffffcc; =
FONT-FAMILY: Helvetica, "Times New Roman"
}
LI.msoNormal {
	MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-LEFT: 0px; COLOR: #ffffcc; =
FONT-FAMILY: Helvetica, "Times New Roman"
}
</STYLE>

<META content=3D"MSHTML 6.00.2800.1561" name=3DGENERATOR></HEAD>
<BODY id=3DridBody style=3D"BACKGROUND-COLOR: #ffffff" bgColor=3D#ffffff =

background=3D"">
<DIV><SPAN class=3D788034018-23012007><FONT face=3D"Courier New">I have =
implemented=20
tree2 (tomahawk 1.1.5 snapshot) using server side toggling for my =
application.=20
The application is working fine on tomcat. But when the same application =
is=20
being deployed on weblogic, the session scoped bean is not maintaining =
the=20
state. In other words , whenever I click the node on the tree&nbsp;to =
see=20
the&nbsp;expanded nodes, the constructor of backing bean gets called =
even though=20
it is defined&nbsp;with session scope. As a result , I am unable to get =
the=20
expanded tree.</FONT></SPAN></DIV>
<DIV><SPAN class=3D788034018-23012007></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D788034018-23012007><FONT face=3D"Courier New">Has =
anybody faced=20
this issue on weblogic ?</FONT></SPAN></DIV>
<DIV><SPAN class=3D788034018-23012007><FONT=20
face=3D"Courier New"></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D788034018-23012007><FONT=20
face=3D"Courier New">Thanks,</FONT></SPAN></DIV>
<DIV><SPAN class=3D788034018-23012007><FONT=20
face=3D"Courier New">Shubhra</FONT></SPAN></DIV>
<P><SPAN class=3D788034018-23012007><FONT=20
face=3D"Courier New"></FONT></SPAN>&nbsp;</P><br>
<br>
This communication is the property of Qwest and may contain confidential =
or=20
privileged information. Unauthorized use of this communication is =
strictly=20
prohibited and may be unlawful.  If you have received this communication =

in error, please immediately notify the sender by reply e-mail and =
destroy=20
all copies of the communication and any attachments.</BODY></HTML>

------_=_NextPart_001_01C73F1E.E7E0FB95--