Passing an object from a JSPContainer content page to edit page

Question

I am using the ldap tag library from the DS ResourceKit to populate details for a custom User Info JSP channel. Having created the content page, I want to make the appropriate ldap query result object available to the edit page. I have tried various mechanisms, e.g. putting it in the pageContext (via tags and directly), putting in the session object - but I cannot seem to be able to get at it from the edit page.
So in the code below, from the contents page, I need to know how to make userentry (or possibly results) available to the edit page and how then to access it from the edit page.
The stuff below the table in the code below is my attempts to put variables into various contexts to see if I could access them from the edit page.
<jx:declare id="userentry" type="com.sun.ldaptl.beans.EntryBean"/>
<ldap:search...
<jx:when test="$results.size == 1">
<!-- If single match display details -->
<jx:forEach var="userentry" items="$results">
<table border="0">
<tr>
<td>
<font face="<%=fontFace%>" size="+0">
<ldap:attr default="�" entry="$userentry" name="cn"/>
</font>
</td>
</tr>
</table>
[the following stuff all seems to work within the contents page, but nothing seems to be available via the edit page]
<jx:set var="dn" scope="session" value="$userentry.dn" />
From expr dn = <jx:expr value="$dn"/>
<jx:set var="curr_entry" scope="session" value="$userentry"/
>
From pageContext object directly ...
<%
com.sun.ldaptl.beans.EntryBean bah = (com.sun.ldaptl.beans.
EntryBean)pageContext.getAttribute("userentry");
out.write(bah.getDn());
String theDN = (String)pageContext.getAttribute("dn");
out.write("2nd dn = " + theDN);
%>
<%
//HttpSession session = request.getSession(true);
out.write("From session " + session.getAttribute("dn"));
%>
</jx:forEach>
</jx:when>

Answer 1

Maybe this might help you:
My problem:
Retrieve data at runtime in the main channel (desktop container) which were available in external systems, and should be stored "somewhere", retrieved 1 time (during login time) and made available for any other channel that wants to use them.
My Solution:
Writeing a customer container and including there any data set/get methods + data structures I needed then using the desktopprovidercontext (dtpc) to get access to the desktopcontext object.
This was the hard way ..
There might be some addtional methods for linking data objects to the desktop context. this context is unique to each user (and session) and accessible from any channel by using the tags.
HTHT,
/Ulf