Stateless Sessions Bean - CMT

Question

I have an application running under Oracle 9ias and has been configured to use the external transaction controller. I am running into a problem with transactions and was hoping someone can help me out.
The scenario is as follows
Stateless Session Bean A {
int addAttachment(String data) {
uow = session.getActiveUnitOfWork();
Attachment attachment = uow.registerNewObject(new Attachment());
attachment.setData(data);
uow.assignSequenceNumber(attachment);
return attachment.getId();
Stateless Session Bean B {
void getAttachments() {
int id = beanA.addAttachment("sfsf");
uow = session.getActiveUnitOfWork();
Attachment attachment = uow.readObject(id, Attachment.class);
The call from getAttachments() to read the object fails. It doesn't find the object.
Since both of these are running within the same transaction (the transaction attribute on both methods are set to "Required") shouldn't getAttachments() on Bean B be able to see the object that was created in Session Bean A?
By setting the transaction level on the addAttachment() to RequiresNew works but that isn't what I want as everything should be in one transaction.

Answer 1

If keeping method names a reasonable length were not an issue, the method “registerNewObject” might be better called “registerThisNewObjectAsIfItWasAClone”. The “registerNewObject” method registers the new object as if it was a clone. At commit time, TopLink creates another instance of the object to be the cache version of that business object. You use “registerNewObject” in situations where you do not need a handle to the cache version of the object after the unit of work commits and you do not want to work with clones of new objects. You also use “registerNewObject” in situations where you must pass a clone into the constructor of a new object and then need to register the new object.
You use registerNewObject when you have to pass clones into a constructor -- i.e., where there clones will be associated with the new object created by the constructor... But generally you use registerObject for new Objects.
- Don