Hey
Jon Tirsen wrote:
> Agree 100%.
>
> We use this naming convention on the bean-side.
> That is:
> com.x.blah.people.Customer
> com.x.blah.beans.CustomerBean (containing business logic only)
> com.x.blah.beans.CustomerBeanCMP (container managed)
> com.x.blah.beans.CustomerBeanBMP (bean managed)
Do you ever have CustomerBeanBMP as a subclass of CustomerBeanCMP? (with
EJB1.1 I would *definitely* prefer that! I.e. even if you use BMP, put
the non-db stuff in a *CMP bean so that in the future when you do not
need the *BMP layer anymore, simply deploy the *CMP bean instead) (wow,
that was a long parenthesised comment.) (BTW, IMHO the J2EE RI example
project should be restructured to this strategy. There are lots of good
practice rules; why not put them into the example project?!)
How do you handle reuse of beans between projects?
Or do you consider this at all? (reuse between projects that is)
Or are reusable beans moved to a "neutral" project? (e.g. "se.itec.ejb"
or something)
So many questions...
/R
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
