wolfc wrote : Please try the following:
|
hello wolfc, i did what you say, but on flush i got this error :
| 10:08:19,946 ERROR [STDERR] javax.persistence.TransactionRequiredException:
no transaction is in progress
| 10:08:19,947 ERROR [STDERR] at
Post the entire stack trace please.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4075399#4075399
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4075399
___
jboss-user mailing list
When you use bean manage transaction, you have to begin and commit transaction
by yourself:
| @Resource UserTransaction ut;
| ...
| ut.begin();
| ...
| ut.commit();
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4074695#4074695
Reply to the post :
Hello Ta
Great Thanks for your post, i tried to this for couple of moth and could not
resolve this problem.
and ok, i did what you say i got another problem when i tried to persist in one
method whats ok, there is no information persisted in database, but when i
tried to flush on other method i
Please try the following:
@Stateful
| @Remote(TestFasade.class)
| public class TestFasadeBean implements TestFasade {
|
| @PersistenceContext(type = PersistenceContextType.EXTENDED)
| EntityManager oracleManager;
| Test test;
|
| @TransactionAttribute(NEVER)
i could not resolve this problem yet:(
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4074658#4074658
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4074658
___
jboss-user
Maybe you can try to use a bean manage transaction:
@TransactionManagement(TransactionManagementType.BEAN)
|
Then you will have to begin and commit transaction by yourself.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4073839#4073839
Reply to the post :
jc7442 wrote : Maybe you can try to use a bean manage transaction:
| @TransactionManagement(TransactionManagementType.BEAN)
| |
|
| Then you will have to begin and commit transaction by yourself.
View the original post :
yes it is possible to do this, but i don't want bean managed transactions.
is it possible what i did ?
i think that extended persistence context disables automatic flash on database,
maybe i will use bean managed transaction if i will not resolve this problem.
Thanks jc7442 anyway.
View
Hi All!
I haven't read everything in this thread but a good idea might be to take a
look in the Java EE tutorial. It has a whole chapter discussing transactions.
Whole tutorial: http://java.sun.com/javaee/5/docs/tutorial/doc/
Transactions:
Sorry everyone for the delayed response, I must not have set this Thread to
send emails when updated.
The Extended Persistence Context is 1/2 the equation, because if your EM is
flushing automatically on any select/update/insert/delete events or when the Tx
is committed, you're still going to
Looks like you'd just like an Extended Persistence Context, so that your EM
isn't flushed to the DB automatically at JTA Commit.
http://docs.jboss.org/ejb3/app-server/tutorial/extended_pc/extended.html
S,
ALR
View the original post :
ALRubinger wrote : Looks like you'd just like an Extended Persistence
Context, so that your EM isn't flushed to the DB automatically at JTA Commit.
|
| http://docs.jboss.org/ejb3/app-server/tutorial/extended_pc/extended.html
|
| S,
| ALR
Great Thanks for your posts,
i did what you
any idea???
i need it so much :(.
did i something incorrect ? :(
Thanks In Advance.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4073811#4073811
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4073811
14 matches
Mail list logo
