i am not using @rollback at all, enough problem trying to make seam work.
i think jboss seam team should put up some sort of general/common errors and
their solusions, since apparently there are a number of them.
View the original post :
You should see the SeamProblemsFAQ
http://wiki.jboss.org/wiki/Wiki.jsp?page=SeamProblemsFAQ.
I'm sure it's missing stuff, is there anything you can think of that should go
on there?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3994590#3994590
Reply to the
Yes, this use is the intended use, and is perfectly fine - but only as long as
you dont use an extended persistence context.
(I still havn't made up my mind on this one.)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3984957#3984957
Reply to the post :
That's the way I would use @Rollback too.
The problem is that the I have no chance of state refreshing after the rollback.
Actually I have got a page which displays a list of customers and one customer
in detail, so that I can create, update and delete customers on one page.
The update could
We are acutally using it as well.
We tend to do some of the more complex validations in our actionmethods, and if
they fail it´s quite convinient to just give a specific outcome to rollback
everything. I must admit though, that I don't know anything about
UserTransaction (yet), so maybe this
I use @Rollback the same.
Though I am not at all attached to it.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3984600#3984600
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3984600
[EMAIL PROTECTED] wrote : This is NOT the right way to implement atomic
conversations! You are supposed to either do your work outside a transaction,
or use @Begin(flushMode=FlushMode.MANUAL).
|
Wow I got an exclamation mark! AND capitals! We have been using Seam for a year
now and have
This is NOT the right way to implement atomic conversations! You are supposed
to either do your work outside a transaction, or use
@Begin(flushMode=FlushMode.MANUAL).
I didn't hear from anyone else who uses @Rollback yet
View the original post :
G'day
I do use it, but I will let you decide if the UserTransaction stuff would be
better.
I use it probably out of a bit of laziness, I will try and explain: I have an
Entity (lets call it mum) which I also use as a backing bean for a form. it
has a collection of objects (Entity as well)
I wasn't aware that it existed. The more control of UserTransaction that's
possible, the better -- though I imagine anyone using UserTransaction is
probably already controlling it through code and not declaratively, so
injection would probably suffice.
View the original post :
10 matches
Mail list logo
