RE: [JBoss-dev] container-cache-conf 1/1

2001-07-05 Thread Vincent Harcq
PROTECTED] Objet : RE: [JBoss-dev] container-cache-conf 1/1 Hi, Please read this example. It is simpler that the previous one. I don't understand why I am the only one to complain on that. MyService is a SessionBean. It is a facade the the entity bean. Master is en EntityBean accessed

RE: [JBoss-dev] container-cache-conf 1/1

2001-07-05 Thread marc fleury
]]On Behalf Of |Vincent Harcq |Sent: Thursday, July 05, 2001 3:51 PM |To: [EMAIL PROTECTED] |Subject: RE: [JBoss-dev] container-cache-conf 1/1 | | |Wow it's an old one. |I solve my problem by adding a toString() method to the PK class. |I don't see the reason why it helped me but it does. |For some

RE: [JBoss-dev] container-cache-conf 1/1

2001-07-05 Thread Vincent Harcq
juillet 2001 22:14 À : [EMAIL PROTECTED] Objet : RE: [JBoss-dev] container-cache-conf 1/1 it's a really odd one, the only place we use toString is in the passivation engines (store to file) so you are looking at something else besides the cache. Find what's screwed up it is an interesting one

RE: [JBoss-dev] container-cache-conf 1/1

2001-07-05 Thread Vincent Harcq
juillet 2001 22:14 À : [EMAIL PROTECTED] Objet : RE: [JBoss-dev] container-cache-conf 1/1 it's a really odd one, the only place we use toString is in the passivation engines (store to file) so you are looking at something else besides the cache. Find what's screwed up it is an interesting one

RE: [JBoss-dev] container-cache-conf 1/1

2001-07-04 Thread marc fleury
]]On Behalf Of |Vincent Harcq |Sent: Wednesday, July 04, 2001 1:01 PM |To: [EMAIL PROTECTED] |Subject: RE: [JBoss-dev] container-cache-conf 1/1 | | |Hi, | |Test1: | |I have a servlet calling a sfsb calling a slsb calling a entity bean A on |which I run a setX().This setX() runs himself another setY

RE: [JBoss-dev] container-cache-conf 1/1

2001-07-04 Thread Vincent Harcq
4 juillet 2001 21:09 À : [EMAIL PROTECTED] Objet : RE: [JBoss-dev] container-cache-conf 1/1 honestly this doesn't really help, too complex a business scenario, bean a calls b calls c calls d calls e calls f then something goes wrong... can you minimize the repro case? like something simpler