Well,
If you analyze the code generated by andromda you'll see that after executing the method in the Impl class the program returns to the SessionBean class (The one extended by the Impl Class) where the actual create method is declared and the abstract handleSomething Method, in the finally section the program makes a session.close() (forcing a session.flush() as One can figure out from your comment) IF the session != null.
So this session.flush() wont work either as a session.close() is already been executed by the application.
My partner (Javier Adorno) pointed out the following after analyzing my project,
Session Beans and Entity Beans are declared in diferent packages,
ce.sb (For Session beans), and
ce.eb (For Entity Beans)
Could this be an issue?
Thanks in advance!
Diego Bendlin
_________________________________________________________________
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
- Re: [Andromda-user] AndroMDA + Hibernate problem (Generate... diego . bendlin
- Re: [Andromda-user] AndroMDA + Hibernate problem (Gen... diego . bendlin
- Re: [Andromda-user] AndroMDA + Hibernate problem (Gen... diego . bendlin
- Re: [Andromda-user] AndroMDA + Hibernate problem (Gen... diego . bendlin
