Proxy persistence class

[Former Member]

Hi,

I have a proxy persistence class created with a flat structure that does not have any DB operation, I am creating a persistence by key using the business key of the application and OS_GUID all the time. Is there any implication if I use it this way?

Rgds,

MM

[Former Member]

Can you explain more detail on the way you using persistence class?

[Former Member]

Hi,

I have changed my design. Thanks for ur reply.

I wanted to create a generic proxy class for all application objects that use notification (PPF requires a persistent application class). That is why I wanted to create a persistent class. Since this is proxy class it does not have any BD operation involved.

Everytime, the application links PPF through this class, a persistence will be created for the business key.

My worry was the system will generate a new guid everytime I create a persistence for the same business key.. waste of resource.. i guess.. unless I am missing something...

Anyways thanks for ur response.

Regards,

MM

[Former Member]

Hi, I almost get your problem. You populate a common resource through Persistence Class, but you don't need the Persistent Class be instanted repeatly, right?

I think maybe you can set your persistent class to be a share object, there is a check box'shared-memory enable' in the properties tab of se24. You can find it.

Have a configuration in SHMA & SHMM, then this persistent class field memeber can be shared between applications.

After that, before you access the common resource, first you can try to get the shared object, if failed, then create a instant of Persistant Class. If all application access resource in this way, then redundant instant can be reduced.

(about the detail of the share object, you can search in the SDN and other site. of course, your question is welcome.)

But in addition, allow me to ask a question, what's PPF and BD operation in your conception? Can you explain it for me? And I really interesting in this sentence of yours: "That is why I wanted to create a persistent class.". Can you explain why you have to create a persistent class?

thanks a lot

[Former Member]

Hi, That is too much. Don't think big. I am trying to build a persistence application reference for the Post processing framework to work on. Also the persistence service will throw an exception/program dump if we try to create persistence for the same key again (in other words instantiated repeatedly).

PPF is similar to output control. But in ABAP Objects.

You have to have a persistent class in order to work with PPF objects (Prerequisite).

Regards,

MM

[Former Member]

Hi, you close this topic?

Then can you tell me how you resolve this problem in your application?

If you don't want to use share object, maybe you can make the PPF memeber object in your Persistence Class to be a static one.

Then others can access it without instance.

Thanks

[Former Member]

Hi Zhenglin,

Thanks a lot for your comments and suggestions.I have to change the design as per the requirement.

I think I mislead you in my first mail. Creating a common persistence class. I was talking from the detail design standpoint. I am sure that is (common persistent class) what made you to think about share object etc...

I am having PPF member object as an instance attribute in my application class.

Thanks again..

Regards,

Marichand.M

[Former Member]

Hi, interesing.

Then it looks that the 'Persistent Class' word make me a misunderstanding.

So you can see I have asked you why you insist using 'Persistent Class'. I thought the 'Persistent Class' is the one we create in the SE24. hehe

Ok, thanks for you explain its real meaning for me.

Regards