>
> 1. In the ejb-jar.xml file, why do we need to the
> <home> and <remote> tags for every ejb-ref section?
> Wouldn't <ejb-link> provides a unique "key" to look up
> those information from the xml file? It seems to make
> more sense to make <ejb-link> mandatory and remove the
> <home> and <remote> tags from this section.
I'll second the question. I've just started using links, and it bothers me.
A workaround I've thought of is to put the entire shebang into an XML
general entity, and reuse it in multiple references to the same EJB.
>
> 2. Is there any restriction on what I can do in the
> EJB bean's default constructor?
Yes there are. I don't remember them, but the spec states exactly what you
can do in each and every method. Basically you can't do much in the
constructor, you should perform instance initialization in
set{Entity,Session}Context.
>
> 3. Can I have multiple remote interfaces and homes for
> a single remote bean implementation? For example,
> Remote1 will expose method "getData", Remote2 will
> expose method "checkBalance", etc. Under the cover,
> there is only one bean implementation which implements
> both "getData" and "checkBalance". Is it a common
> practice?
I don't think the spec prohibits it in any way (except that you can't have
different primary key types in the case of entity beans), but I don't think
I'd do it that way.
===========================================================================
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".
