i have tried to use option (b) above.
so in the code, i simply modified the entity bean hoping that the changes would
get commited without explicitly invoking the entity manager, but this did not
happen.
i also annotated the method as @Destroy @Remove -- how can i cause the SFSB to
be
i would assume that when a method annotated with @Remove @Destroy is executed
(SFSB), the persistent context is flushed and changes commited to the DB when
this method is invoked ?
i dont see the modifications to the entity beans being commited to the DB after
the execution of the above
i can always change an object graph as i want and eventually invoke merge as
against updating the attached objects in an extended persistence context.
what specific advantage does extended persistence offer over merge.
thanks
View the original post :
for me to use extended persistence context, is is required to use seam managed
transactions as mentioned in the manual like so:
phase-listener
org.jboss.seam.jsf.SeamExtendedManagedPersistencePhaseListener
/phase-listener
the booking example does use extended peristence but i dont see the
as per the documentation, entity beans may never be bound to stateless context.
why is this so ? if i want to update an entity bean on a per-request basis then
i could create a SLSB and inject the entity bean and update it from the action
method of the SLSB. ?
View the original post :
thanks. are the cached entity beans (in the session /conversation context)
attached to the underlying persistence session between requests. if not, does
the framework attach them for each call ? when the bean is changed (via a
form), does the framwork merge the changes automatically to the d/b.
is there a way to package a datasource file *-ds.xml as part of the EAR file ?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3955002#3955002
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3955002
Using Tomcat but need to do
i was having a similar problem.
try the 4.0.4 version (not the patches) , download and install ejb3 Rc8
separately as per the instructions. it worked for me
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3955174#3955174
Reply to the post :
