Hello,
Is this thread still alive ?
Has somebody had time to check this matter ?
Thanks.
Regards.
J&B
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869173#3869173
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=386917
I will look at it. Thanks.
It's possible that there was something wrong with 3.2.2 but I need to check.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3859991#3859991
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3859991
I have a similar problem. I have 3 Beans A1,A2 and B.
both A1 and A2 have a 1-1 relationship to B. B
has a 1-1 Relationship to both A1 and A2.
If I create a instance of B and call b-setA1(A1), everything
works, whereas b.setA2(A2) doesnt work. The Relationships
are defined identical. I get the fol
Hello,
I added it to jira.
Here is the KEY : JBAS-72
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3859417#3859417
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3859417
---
Ok I ll put it into jira.jboss.com.
I manage this morning to make a test app with 3 CMPs and a test class which is
successful in 3.2.2 but crash in 3.2.5.
I could mail you those files if needed ( ? )
One thing I m wondering, since I also believe that I m doing something wrong,
could it possibl
I need a simple testcase that shows the difference. So far I believe you are
doing something wrong. If you have enough information for me to reproduce this,
please, open a Jira issue on jira.jboss.com.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3859393#385
Hello,
No I don't really have any testcase.
Fact is that I m not an expert concerning transactions and so on, so I m
actually wondering if problem comes from something I did wrong. However same
code seems to behave differently in 3.2.2 and 3.2.5.
I could maybe send you couple of classes if that
Do you have a testcase that I can run on 3.2.2 and 3.2.5 and see what you are
talking about? Updates were always committed at the end of the tx in all
versions or other times when synchronization is required but not after adding
CMR value.
View the original post :
http://www.jboss.org/index.ht
Hi,
Thanks for your answer.
In JBoss 3.2.2, obviously the getB().add(relation) was commited immediately,
since when the loop was iterating the second round the unique constraint was
not triggered when creating a new B entity (Meaning that the foreign key had
been set)
Where it is clear that i
How did it work in 3.2.2?
Try http://www.jboss.org/wiki/Wiki.jsp?page=InsertAfterEjbPostCreate
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3859006#3859006
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3859006
--
10 matches
Mail list logo
