Skip to Content
author's profile photo Former Member
Former Member

Bean Persistance


IPortalComponentProfile Object can be used with beans to store values within the bean.

It is my understanding the scope of the bean would need to be APPLICATION, the persistancy is throughout the liftime of the portal. Though other users do not have access to this bean, the user having access to this bean can log of shut down his computer and get back later and access values stored within this Bean. Am I right in this thought.

If the bean is stored in the profile, how(as a file...) and where is it stored.

We have been thinking of Developing a custom application, where there would be a couple of input fields on the Initial Screen. The thought is to allow the user to fill in value in the fields and run their reports. When the user logs of and later next day logs back onto the application should be able to have the Initial Page Input Field values he had filled previously. Is this possible and would I store the bean within the profile to achieve the same.

Has anyone come across any documentation that explains how one would use beans with this IPortalComponentProfile Object.

Please advice any thought would be appreciated.


Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Posted on Feb 24, 2005 at 05:01 PM

    Hi NAC,

    > IPortalComponentProfile Object can be used

    > with beans to store values within the bean.

    The sentence is not very clear. "store values within the bean" means storing values within beans. If you want to store something persistently, you may think of storing it within IPortalComponentProfile. But there you can - persistantly - only store string (mybe your values of a bean?).

    > the scope of the bean would need to be APPLICATION

    This is right for "putValue()", also see

    Anyhow, putValue() is deprecated, see,%20java.lang.Object)

    Using IPortalComponentContext is not recommended, see note 802015 and is not persistent anyway.

    What stays?

    Define your properties within portalapp.xml, set personalization to dialog or no-dialog (with dialog you could use the personalization capabilities from portal standard) and use <i>setProperty(...)</i> and <i>store()</i>.

    With this, you can achieve what you want.

    Hope it helps


    PS: It would be kind if you would be a bit more responsive and say if after an answer a problem persists or, if not, that you mark the question as answered and reward points.

    This holds for the following threads: Viewing Portal Runtime Error Log and Portal Runtime Error: 0 >= 0.

    You can also reward <i>some</i> points for <i>some</i> help, even if it does not solve the issue. For example here: Connecting to BW System

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.