Hi all,
I have an action bean that receieves user input from a web browser and stores 
the data in another remote application server.
The remote server contains the entity beans. To persist the data, what i am 
doing is creating wrappers around the entity beans to avoid the client 
modifying some parts which i dont want to expose. I also want to make the data 
presentable, so i dont use the entity bean directly in my action bean. When the 
data passes validation, i copy the data maually even though the front bean is 
just a replica of the entitybean (even if the property names are different.)
 
After three forms my structure is becoming very redundant, mundane and 
completely BORING.
 
My question is, how do i implement data persistence in stripes in a way that 
will decouple the client from the client from the entity bean. i know this will 
be very easy to use the entity bean directly in the action bean, but because of 
security i dont want to do this, or i want to know how best to do it.
_________________________________________________________________

http://clk.atdmt.com/UKM/go/msnnkmgl0010000009ukm/direct/01/
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users

Reply via email to