After some further investigation, I have found some other interesting
facts.
CMP Bean details:
Three persisted fields: int, String, String.
One of the Strings is used as the primary key.
I defined ejipt.isCreateSilent=false, and I did the following 2 tests.
*********************************************************************************************************************************************
Test 1:
Shut down JRun server and re-start.
I create one entity. I stress one entity, because that is all that I can
create. If I leave the JRun server up and try to create another entity, I
get a DuplicateKeyException. This happens every time I tried this test.
As long as I shut down and re-start after every create the create will
work, but if I leave the server running I get the DuplicateKeyException.
***********************************************************************************************************************************************
Test 2:
Shut down JRun server and re-start.
This test I tried to create an entity that is in the database. I get a
RemoteException, because my database caught the error. This was expected
from database since the key already exists in the database. My question
is: What does the ejipt.createSQL statements do, if they are not going to
catch this situation?
*************************************************************************************************************************************************
For the next test I defined ejipt.isCreateSilent=true
**************************************************************************************************************************************************
Test 3:
Shut down JRun server and re-start.
I create an entity that does not exist in the database. The create does
not throw an exception and everything seems fine. I then try to create a
different entity. When I try and create the second entity it returns the
entity that was created first. Why this is happening I don't know, but
this really seems like a bug.
***************************************************************************************************************************************************
I don't know if I am doing something wrong to get these results, or if
these are bugs. I have looked over all of my code trying to see if there
was anything that could cause this behavior, but this is a very simple
Entity bean that really does nothing. I would suspect that they are bugs
in JRun. If these are bugs, then I think that this makes JRun an unusable
CMP EJB product.
Allaire guys: Am I missing something? If this is a bug, then are there
any work arounds?
Adam
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Your ad could be here. Monies from ads go to support these lists and provide more
resources for the community. http://www.fusionauthority.com/ads.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
