Sorry, I did see that Pete replied...
Thanks,
M
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4119391#4119391
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4119391
___
jbos
Can someone from the Seam team, comment on this. There is too much ambiguity
here.
Thanks,
M
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4119388#4119388
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4119388
Yes, that's how I fixed my error. I pulled down the latest CVS and saw that.
What I don't understand is why it was enabled by default? What advantages does
it bring, and why did it break my old deployments?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=40627
>From the latest (post release) migration guide:
anonymous wrote : * replace with
|
|
| Note: Seam transaction management is now enabled by default. If you want
| to disable use of Seam-managed transactions, use the following:
|
|
View the o
I was receiving this in SEAM 2.0b1.
I had to add:
transaction-management-enabled="false"
to the core:init
as well as:
to my components.xml file. This has me nearly up and running again.
I'm not clear on why yet though.
View the original post :
http://www.jboss.com/index.html?module=bb&op=v
Ooops, I meant this: ;)
| @In(create=true)
| @Out(required=false)
| private Product product;
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062725#4062725
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=
This pretty much always points at an earlier problem (exception, that might
have been caught and not rethrown for some reason) that has casued the
transaction to end when it shouldn't have.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062718#4062718
Reply
I got that error when I had a member variable without (create=true)
| @In @Out
| private Product product
|
So, once I put in
| @In(create=true) @Out
| private Product product
|
It fixed the intermittent problem.
View the original post :
http://www.jboss.com/index.html?module=bb
Did you find a solution to this issue?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062558#4062558
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062558
___
jboss-user maili
Yeah, eclipse has been kindly trimming some important lines from stacktraces
for me too from time to time. I've had to go in with a debugger and manually
inspect to find the root cause. Wish I knew what caused this.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewto
Here is the mapped property for which the lazyloading appear to fail:
@OneToMany(cascade={CascadeType.PERSIST, CascadeType.MERGE})
| public List getKriterien() {
| return kriterien;
| }
|
| public void setKriterien(List kriterien) {
| this.k
I've isolated the cause if this to a call to an entitybean method, which
accesses mapped property (A list mapped to another table). If I call this
method from an action, it works. But when I call it during rendering, it fails
with the above Exception. Appearantly this is a problem with lazy load
I should have mentioned that I've got this error from time to time before, but
it has gone away without my intervention, (which makes it a bit scary). A
previous post on this error mentions its random appearance. I would be curious
to know ith there has been any progress on nailing down its caus
13 matches
Mail list logo
