Hello Adrian,
Thank you for your advice.
I solved my problem finally.
I thought we did not implement isModified() method, but that method was
implemented in super class of our original framework. The default
implementation of the isModified() was just return false. That is why
ejbStore() was not
Hi Adrian,
Here is current environment info and configuration.
JDK: 1.3.1_08 ( Because a crypto library does not work in 1.4+)
OS: Windows Server 2000, Windows XP Pro
JBoss: 3.2.1, 3.2.2RC3
DB: Microsoft SQL Server 2000(SP3)
JDBC: The driver Microsoft made
Bean: BMP Entity Bean (EJB 1.1 spec)
You haven't posted your User Configuration 0
Also the logs don't show enough, I don't see the finder or the commit.
I do see it registering the context for synchronization at transaction
end.
You didn't answer my question about isModified()
Finally, what is happening with your key?
TRACE
Do you implement isModified()?
Perhaps you can enable TRACE logging for org.jboss.ejb
(see the example in conf/log4j.xml) and post the log
snippet from log/server.log
Your configurations would also help.
Regards,
Adrian
On Thu, 2003-09-25 at 03:54, Yasuhiro Takahashi wrote:
I wrote wrong.
Hello,
I am converting a system from Weblogic 6.1(sp3) to JBoss 3.2.1.
I got a strange phenomenon about BMP Entity Bean.
The process is like followings;
1. Create a entity bean E1 by calling home.create();
2. Set Object O1 to E1 by calling E1.setXXX(O1);
3. Get entity bean E1 by calling
I wrote wrong.
(Wrong)
Here is the problem.
In stem 3(or after step3), ejbStore() of E1 is never called.
(Correct)
Here is the problem.
In step *4* (or after step *4*), ejbStore() of E1 is never called.
Thanks,
Taka
---
This sf.net
