"Andy L. Czerwonka" wrote:
> Suggestion: in order to use the type checking that interface
> implementation gives you, you should divide the interface into two: one
> which only contains the business methods, and one which extends the
> first interface and EJBObject. Your bean implementation may now
> implement the business interface without risk of using "this" properly,
> and you do not need to implement dummy methods for EJBObject method
> declarations.
>
> [ALC] There's the answer to that. I think that (or similar) approach
> should be used in the spec. This was the point of my original post.
Note: in my post, change "of using "this" properly" to "of using "this"
improperly". Ehm.
Anyway, I don't think this is a spec thing. It's more related to "best
practices", but some note regarding this might be appropriate in the APM
or something. In those cases beans are created through a tool (more than
often), the tool should minimally support the synchronization of
interface and bean automatically.
/Rickard
--
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".
