> Do you have anything in the ejbCreate method in your bean class? In the inherited BMP class I, by now, load the bean with the client created dto (using setData). The corresponing bean methods is abstract. I clearly see your point of moving this to the super.bean, its better - i'll do that.
The other problem i discovered, as i describe in som prev. email, was that the pk of the newly generated bean is never set in ejbcreate. My understanding is that the pk fields needs to be loaded after the dao call in situations where the bean is created and modified in the same transaction context. I couldn't figure out to do this in the BMP file using templates, so i added a method in the dao implementation setting the beans pkfields after sql returns the created key. I would imagine that the best is to let the BMP impl. do this pk field setting; but as i said, i haven't figured out how to do it - some template functions won't do want i want them to do. :-) > I figure doing it this way makes it less effort to switch between BMP+DAO > and CMP in the future, since the ejbCreate's code stays the same (which is > also the reason the finder methods are added to the DAO automatically in > 1.2 beta 1, by the way). I agree. > Of course, if you're doing this already and the super call isn't being > added in the BMP subclass, then that's a bug and you should raise an issue > for it in JIRA. The super call isn't added by the BMP subclass - i'll report it. -Jon ------------------------------------------------------- This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
