UUP: um:getProperty caching results?

Question

I've set up a UUP to access some data in an external database,
and I'm getting some interesting effects when the external data
changes. Am I missing something obvious here?
When the UUP is first accessed, all of the information is
returned correctly by the
<um:getProperty propertyName="<myProp>"/> tag. If that data
then changes in the external data store, the tag still returns
the original data.
I assumed this was due to the profile not reloading the
information, but it does in fact as I can retrieve it using
either the explicit getter method, or the getProperty method on
the profile.
Just to make it a bit clearer, if I do:
<um:getProfile profileType="myType" profileKey="<user>" profileId="myProfile"
scope="request"/>
<%myProfileType mp=(myProfileType)myProfile;%>
<um:getProperty propertyname="<property>"/>
<%=mp.get<property>%>
<%=mp.getProperty(null, "<property>", null, null)%>
Then I get cached data displayed on the first line, and current
data on the other two, until I restart the server.
I'd assumed the <um:getProperty> tag was just calling the
getProperty method on the bean rather than caching anything
itself.
Any suggestions?
David

Answer 1

Hi David,
<um:getPropery> gets the property value from the cache, not directly from a
ConfigurableEntity EJB. If you have first called <um:getProfile> with session
scope, then it uses the CachedProfileBean that the <um:getProfile> tag put into
the session. If you don't call <um:getProfile> with session scope, then it uses
the AnonymousProfileBean.
You could experiment with calling <um:getProfile> with session scope and check
out the session to see the cached profile show up.
You are calling the <um:getProfile> tag with request scope, not session scope.
Also, I see that you are testing your application using
ConfigurableEntity.getProperty() directly (with your mp.getProperty() call). In
a real application you will want to use CachedProfileBean for speed. Search this
newsgroup and check out the javadoc for hints about using the CachedProfileBean.
Here are some links that may be useful:
<um:getProfile> docs for WLCS 3.5 at
http://edocs.bea.com/wlcs/docs35/p13ndev/jsptags.htm#1058056
<um:getProperty> docs at
http://edocs.bea.com/wlcs/docs35/p13ndev/jsptags.htm#1058056
Anonymous profile documentation at
http://edocs.bea.com/wlcs/docs35/p13ndev/users.htm#1092004
CachedProfileBean javadoc
http://edocs.bea.com/wlcs/docs35/javadoc/wlps/com/beasys/commerce/user/jsp/beans/CachedProfileBean.html
David Marston wrote:
I've set up a UUP to access some data in an external database,
and I'm getting some interesting effects when the external data
changes. Am I missing something obvious here?
When the UUP is first accessed, all of the information is
returned correctly by the
<um:getProperty propertyName="<myProp>"/> tag. If that data
then changes in the external data store, the tag still returns
the original data.
I assumed this was due to the profile not reloading the
information, but it does in fact as I can retrieve it using
either the explicit getter method, or the getProperty method on
the profile.
Just to make it a bit clearer, if I do:
<um:getProfile profileType="myType" profileKey="<user>" profileId="myProfile"
scope="request"/>
<%myProfileType mp=(myProfileType)myProfile;%>
<um:getProperty propertyname="<property>"/>
<%=mp.get<property>%>
<%=mp.getProperty(null, "<property>", null, null)%>
Then I get cached data displayed on the first line, and current
data on the other two, until I restart the server.
I'd assumed the <um:getProperty> tag was just calling the
getProperty method on the bean rather than caching anything
itself.
Any suggestions?
David--
Ture Hoefner
BEA Systems, Inc.
2590 Pearl St.
Suite 110
Boulder, CO 80302
www.bea.com