hey all, writing to see if anyone has done work with versioning on top of entity beans. I've been given a requirement to have a particular entity versioned, _and_ retain previous versions (so a simple version field, a la soft locking, wont suffice).
The issues I've identified are: a) ensuring that old versions are not changed, but instead new ones created b) maintaining a list of versions c) allowing a version to be modified whilst it is being created, ie - for a user to create an entity using a web interface (with multiple round trips), without creating a new version for each round trip. ok, for (a) I see that I should ensure all access goes through a SLSB, and not to the EB itself. Pretty happy with that. for (b) I had been thinking of keeping a reference to the previous version, so I have a chain of entities. this would make creating the entire list of versions difficult, but would allow some level of access to previous versions. for (c) the obvious solution is a value-object, and create it all at once. but I've been given the requirement that work must not be lost when a session times out. Which _could_ involve using a stateful session bean, but I'm not sure. I'm thinking I'll try and bump the requirement. if anyone's already been down this road, I'd welcome any opinions/input. one last point - it may of course turn out that these requirements mean ejb just isn't right. My #1 requirement is that this is done asap (how unusual :), but if anyone wants to point me elsewhere as well, that too would be good. cheers dim =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
