> How could I reproduce it? Do you have a testcase?
I'll try to make a small test case tonight or tomorrow.
/Markus
>
> Thanks.
>
> Markus Härnvi wrote:
>
> >>Please, try with fresh Branch_3_2 in 24 hours. I fixed a bug that could
> >>be the cause of your problem. Thanks.
> >
> >
> >
The same way as in 3.2.2: by increasing log level to DEBUG for category
org.jboss.ejb.plugins.cmp.
How could I reproduce it? Do you have a testcase?
Thanks.
Markus Härnvi wrote:
Please, try with fresh Branch_3_2 in 24 hours. I fixed a bug that could
be the cause of your problem. Thanks.
I g
> Please, try with fresh Branch_3_2 in 24 hours. I fixed a bug that could
> be the cause of your problem. Thanks.
I got the same error as with 3.2.2.
If I set log4j to DEBUG (in Branch_3_2) I don't get the SQL statements from the
CMP engine any longer. Maybe they could shed som light on my pr
> Please, try with fresh Branch_3_2 in 24 hours. I fixed a bug that could
> be the cause of your problem. Thanks.
Ok, I'll try that in the weekend. Thanks!
/Markus
> Markus Härnvi wrote:
>
> > Thanks Scott for the answer about SSL/Tomcat!
> >
> > Next one: :)
> >
> > I'm using cascade-
Please, try with fresh Branch_3_2 in 24 hours. I fixed a bug that could
be the cause of your problem. Thanks.
Markus Härnvi wrote:
Thanks Scott for the answer about SSL/Tomcat!
Next one: :)
I'm using cascade-delete between a few CMP beans. My test cases that works in
3.2.2RC4 now fails in 3.2.
Yes, sorry. Of course, sync-on-commit-only must be false if you have
foreign key contraints.
Could you, please, submit a bug report with the detailed info? Thank you.
Markus Härnvi wrote:
Hi again!
It's set to false in both environments. I tried setting it to true in 3.2.2 but
that didn't help.
Hi again!
It's set to false in both environments. I tried setting it to true in 3.2.2 but
that didn't help.
/Markus
> Is sync-on-commit-only set to true in RC4? I guess, it is false in final
> and, hence, is the expected behaviour.
>
> Markus Härnvi wrote:
>
> > Hi!
> >
> >
> >>Could
Is sync-on-commit-only set to true in RC4? I guess, it is false in final
and, hence, is the expected behaviour.
Markus Härnvi wrote:
Hi!
Could you post a stacktrace, please? And some description of what was
going to be cascade-deleted?
Sure.
SearchCriteria has zero or more children called
Hi!
> Could you post a stacktrace, please? And some description of what was
> going to be cascade-deleted?
Sure.
SearchCriteria has zero or more children called HostCriteria. Deleting a
SearchCriteria should delete all related HostCriteria.
The key fields in the database looks like this:
Could you post a stacktrace, please? And some description of what was
going to be cascade-deleted?
Thanks.
Markus Härnvi wrote:
Thanks Scott for the answer about SSL/Tomcat!
Next one: :)
I'm using cascade-delete between a few CMP beans. My test cases that works in
3.2.2RC4 now fails in 3.2.2
Thanks Scott for the answer about SSL/Tomcat!
Next one: :)
I'm using cascade-delete between a few CMP beans. My test cases that works in
3.2.2RC4 now fails in 3.2.2 with the following message:
javax.ejb.RemoveException: Could not remove 16 at
org.jboss.ejb.plugins.cmp.jdbc.JDBCRemoveEntityComma
Hello Ionel,
cascade-delete, if set, should be on the many side. So,
cascade-delete.
alex
Wednesday, July 16, 2003, 9:38:14 AM, Ionel Gardais wrote:
IG> Hi,
IG> Considere three beans A, B and C. (B and C are two instance of the same
IG> kind)
IG> B and C knows A but A does not know B or C (un
Hi,
Considere three beans A, B and C. (B and C are two instance of the same
kind)
B and C knows A but A does not know B or C (unidirectionnal relationship
from B/C to A)
When A is deleted, B and C should be deleted too *but* when B or C are
deleted, A shouldn't be deleted.
In the relationship
thanks Alex..
Alexey Loubyansky wrote:
Hello Maykel,
the only way to workaround it is to have foreign key fields mapped
to NOT NULL CMP fields. I.e. you have to introduce additional NOT NULL
CMP fields and map foreign key fields to them.
And if you use cascade-delete, don't forget to set sync-on-
Hello Maykel,
the only way to workaround it is to have foreign key fields mapped
to NOT NULL CMP fields. I.e. you have to introduce additional NOT NULL
CMP fields and map foreign key fields to them.
And if you use cascade-delete, don't forget to set sync-on-commit-only
to true.
alex
Thursday, J
Hello Nicholas,
How can I create my method to receive CMR(Foreign Keys) and JBoss don't
create exceptions when It perform ejb-create?
I have NOT NULL foreign keys but when I call methods with CMR as
attributes, JBoss only set this CMRs in ejb-postcreate. This generate a
exception because my fo
Hello Nicholas,
if you have NOT NULL foreign keys and want to use cascade-delete, you
should use a custom container configuration with sync-on-commit-only
set true:
Sync On Commit Only CMP2.x Container
true
alex
Wednesday, June 11, 2003, 3:58:10 PM, Nicholas Nicholas wrote
We just figured this one out, but we are using 3.2.0.
The foregin key in the child table was defined as NOT
NULL and JBoss was trying to set it to null so it was
failing right there.
Once we set it to NULLABLE, it appears that JBoss sets
the foregin keys to null, then deletes them. I am sure
there
Hi,
We have configured oracle for cascade delete, works fine from doing
delete via sqlplus, other clients, but if we do a remove() from an
Entity bean, the cascade is not happening. Anyone else experiencing
this?, using jboss-3.0.4
Thanks
Warren
Hi,
I found this strange behaviour
on cascade delete: Say you have ParentBean and ChildBean where ParentBean
has many ChildBeans. When removing ParentBean on cascade delete JBoss
first tries to set the FK on ChildBean to NULL and then do the removals.
All this anyway fails if your F
Hi,
I found this recent post in the archives regarding cascading deletes:
http://www.mail-archive.com/jboss-user@lists.sourceforge.net/msg25404.ht
ml
And I have been trying to figure out how to get jboss to cascade deletes
in postgresql. Playing with standardjbosscmp-jdbc.xml, it is definitely
po
In JBoss 3.0.x, deletes child entities one at a time.
This makes sense when an in-memory cache needs to be maintained -- you
need to know which entities to remove from the cache.
But when there is no cache (e.g., commit option C), there are several
more efficient approaches:
a. delete all chi
22 matches
Mail list logo
