[EMAIL PROTECTED] wrote:
Thanks for the confirmation, it was exactly what i asked for :).I think I understand what you're asking, and the answer is "no" -- @ejb.persistence has nothing to do with putting methods into your remote/local interfaces. It is used to tell the container what column to map the attribute to. Here's an example:
/** * @ejb.interface-method * @ejb.transaction type="Supports" * @ejb.persistence * column-name="birth_dt" */ public abstract Date getBirthDate ( ) ;
/** * @ejb.interface-method * @ejb.transaction type="Mandatory" */ public abstract void setBirthDate ( Date birthDate ) ;
@ejb.interface-method tells xdoclet to put both methods into the interfaces (remote cannot be default here because I am only generating the local interface [EMAIL PROTECTED] view-type="local" at the class level], and they appear there).
@ejb.persistence column-name="birth_dt" tells xdoclet to generate the XML to map "birthDate" to "birth_dt". It has no affect on the interfaces whatsoever. If you want this tag to force xdoclet to put the accessors into your interfaces, you'll need to modify the xdt template that generates the interfaces. I don't see any other way around that.
Is this what you were asking? If not, then I guess I'm still not
understanding you. ;) Let me know.
I don't understand why these methods aren't added to the interface espacially in case of relation. It's simpler to use the getRelation() than getting a value object and then a findById.
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
