---- Forwarded Message ----
The best solution is to let you define the suffix for xdoclet. By
default Ejb/EJB/Bean are used but you should be able to provide your
own. It's in EjbTagsHandler.getEjbNameFor(), and easy to implement (just
a matter of getConfigParam()/StringTokenizer, note that it's only used
for cooking the generated class names). Instead of hardcoding it we may
provide an ejbClassNameSuffix parameter:
<ejbdoclet ejbClassNameSuffix="Bean,Ejb,EJB,Entity"/>
<To Andrew>
Andrew, are you interested in implementing it? I have some CVS access
problems atm. Also when will we release 1.1.2? I think we can fix it for
next week.
</To Andrew>
Ara.
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:xdoclet-user-
> [EMAIL PROTECTED]] On Behalf Of Daniel Bratell
> Sent: Wednesday, February 13, 2002 4:42 PM
> To: [EMAIL PROTECTED]
> Subject: [Xdoclet-user] Naming beans with the "Entity" suffix
>
> We have as standard to name entity beans with the suffix Entity
> (ForeignAccountEntity, CustomerEntity,....), but XDoclet seems to
assume
> that the suffix Bean is used for all beans when naming the generated
> classes.
>
> Our classes gets named ForeignAccountEntityLocalHome instead of just
> ForeignAccountLocalHome, as it would be named had we called it
> ForeignAccountBean instead.
>
> So, my question is, is there a way to tell XDoclet that we use Entity
as
> the suffix, or could "Entity" be an allowed default suffix for a bean?
I
> would prefer to not have to hardcode the names of the generated
classes
> inte every entity bean.
>
> /Daniel
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
