Hello heinrich,
I must admit that I don't understand exactly what you want to tell me.
But from my point of view persisting and/or merging an entity bean is not the
problem when working with a remote client. You just have to build a proper
remote method that covers that issue.
Example:
| CustomerOrder persistOrder(CustomerOrder custOrder)
| {
| // Do the persisting job and maybe something else
| }
|
It even is no problem to persist other objects that might come from the client
that are related to the custOrder bean.
Could you please explain your thoughts about that issue a bit more in detail?
If you think that it shouldn't be discussed here you can write me an email. You
already have my address. I am really interested in what you think about my
approach because it will be the base for my own EJB3 Framework.
Thank you
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3910644#3910644
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3910644
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
