> When the Assembler is done there are no ejb-ref
>elements without a ejb-link child. So, now it is not
>optional although the DTD says it is. It is still
>syntactically optional, but semantically it is
>required after this step.
Actually the way I interpreted the spec is that
ejb-links are still optional because although ejb-refs
must
be resolved somehow, the spec does not mandate that
ejb-links must be used to do it ( the words 'may' and
'if' crop up a lot ). All it sets in stone is that the
Deployer must be able to bind the ejb-ref to the home
of a target bean...
Indeed IAS seems to provide another option for
specifying this where instead of using ejb-links to
specify the target bean via its ejb-name, you link the
ejb-ref directly to the JNDI name of the target.
This is specified in an Inprise-specific DD and of
course is vendor specific, however it seems to address
an issue I have with ejb-links:
Since ejb-links specify
the ejb-name of the target bean and ejb-names are
unique within a ejb-jar, it would seem to follow that
you can only use ejb-links to resolve ejb-refs to
beans that are in the same jar..
Indeed with IAS this seems to be a restriction and If
I wish to reference beans in another jar I must use
the inprise-specific mechanism mentioned above...
yet the spec specifically mentions that ejb-links can
be used to reference beans "in another ejb-jar file
within the same J2EE application unit"
am I missing something here?
__________________________________________________
Do You Yahoo!?
Yahoo! Photos - Share your holiday photos online!
http://photos.yahoo.com/
===========================================================================
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".
