Hey
Oleg Nitz wrote:
> R�> But it is never stated. And as a container developer I can only go by
> R�> the things that are explicitly stated. "Hunches" are not enough.
> The opposite is also never stated. The specification does not answer
> this question explicitly.
What about 14.3.4 then? I think this pretty clearly answers the
question.
> >> R�> The Assembler must specify the ejb-link, or the EJB reference is
> >> R�> considered incomplete (from a deployment point of view).
> >> Can you provide any proof of your statement?
>
> R�> Other way round: does it say anywhere that a EJB-reference is considered
> R�> valid if ejb-link is not specified? Also, 14.3.4 explicitly says that
> R�> the Container should inform the Deployer of any unresolved references.
> But what is "unresolved references"?
Am EJB-reference has two sides: one which should be presented to the
bean, and one which should be coupled to some other bean. If the latter
side has not been set, the reference is unresolved.
> >> spec> 14.3.3 Deployer�s responsibility
> >> spec> The Deployer is responsible for the following:
> >> spec> * The Deployer must ensure that all the declared EJB references
> >> spec> are bound to the homes of enterprise beans that exist in the
> >> spec> operational environment.
> I think that here is a definition of resolved references: ones bound
> to the homes. All others are unresolved.
Exactly, and the reason they're not bound is because noone has defined
what they should be set to.
> R�> See 14.3.4. The Deployer may use either ejb-link or a proprietary
> R�> mechanism (and jBoss supports both at this time). But if the Deployer
> R�> does not use either of these mechanisms, the reference is considered
> R�> incomplete, and the Container must (as is stated in 14.3.4) complain.
> Neither 14.3.3 nor 14.3.4 say that the Deployer can use ejb-link.
That is true, because any link that can be resolved by using ejb-link
should be resolved by the Assembler.
> Moreover, 14.3.4 says:
> spec> Container provider... Preserve the application assembly
> ^^^^^^^^
> spec> information in the ejb-link elements
> Here is explicitly said that ejb-link contains the assembly
> information, not the deployment one.
I never said anything else. The Container may use either this
information, or some other proprietary mechanism that is available to
the Deployer only.
> R�> Again: the Assembler *may* use ejb-links, and the Deployer *may* use
> R�> ejb-link *or* other mechanism, but if none of these two parties perform
> R�> this operation, the EJB-reference is, as is stated in 14.3.4, considered
> R�> incomplete, and the Container must complain.
>
> R�> QED. :-)
> Illegal proof ;-)
> 14.3.4 doesn't actually state that "if none of ejb-link or other
> mechanism is used, the EJB-reference is considered incomplete".
> It is just your understanding.
If so, please state your understanding of "unresolved". I can't see how
it can be interpreted in another way, so please tell me.
/Rickard
ps. In any case, the EJX GUI will automatically fill in the ejb-link if
possible...
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
