Thanks for the response. Here is some basic info about the bean.
(The one thing I did not mention is that this Bean was working just as it should until the upgrade to 2.1!)
The transactional attribute is none.
Using RMI.
Client is an applet.
Normally the first place I go is the code. The way ejbStore and ejbLoad fire off under 2.1 seems to be much different than 2.0.
The problem is the following. (And this is with just one user on the system) I log into the application. There is a button to create a new story in the system. You click on it and you get what you would expect: A blank story screen. On the back end, ejbCreate has been called on the entity and a minimal entry is placed into the database. There are basically 5-6 columns of information in the db that the entity maps too. If you leave one of those columns blank, through successive passivate and ejbLoad calls, one of the fields mysteriously get filled in with data from another record in the DB. It is like the primary key is screwed up or something. Below is the PK code for reference.
public class StoryPK implements Serializable
{
public StoryPK()
{
}
public int hashCode()
{
return storyId;
}
public boolean equals(Object other)
{
boolean isEqual = false;
if (other instanceof StoryPK)
{
isEqual = (storyId == ((StoryPK)other).storyId);
}
return(isEqual);
}
public int storyId;
}
John
| Philippe Durieux <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 10/16/2000 02:40 AM
|
To: [EMAIL PROTECTED] cc: [EMAIL PROTECTED] Subject: Re: Very Weird Behavior in a BMP Entity Bean |
[EMAIL PROTECTED] wrote:
>
> We have an application for a large newspaper company that performs website
> publishing. We are currently using Jonas 2.1 (We just upgraded) After the
> upgrade
> we began to experience behavior where a new instance of an entity (a Story
> in the
> application) mysteriously, after the first passivation of the bean, had two
> fields of
> information that were from another DB record that had not even been
> referenced by
> the user up to that point. ? Clear? We have checked everything. One thing
> that we
> did do is to initialize all of the instance variables of the Entity to ""
> (The ones that are
> strings) and that cleared it up for all but one field.
>
> Any thoughts?
>
> John
Hi John,
I'm not sure that I understand quite well your problem.
Can you explain a little more please?
And could you give us a little more information:
What are the transactional attributes of your entity bean (see .xml
file) ?
Do you use the standard rmi or Jeremie ?
What is the client part of your entity bean (applet, java program, jsp,
another bean, ...?) ?
I see that you manage the persistence in the bean (Bean Managed
Persistence).
Are you sure that this code is correct ?
Thanks for information...
--
Philippe Durieux ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Bull - 1 rue de Provence - 38432 Echirolles Cedex France
[EMAIL PROTECTED]
-> Download our EJBServer at http://www.evidian.com/ejb <-
