Dan OConnor wrote:
DO> I see what you are saying.  Of course, if the recommendations of
DO> the spec are followed, the ejb-ref-name will never match the 
DO> referenced bean name exactly... because one will be XXX, and one 
DO> will be ejb/XXX.
I don't think that the examples of ejb-link usage are
the recommendations of the spec.
I would prefer to set ejb-name to ejb/XXX. Why not?
But if it is a common understanding...

Rickard, could you provide support for this naming scheme in EJX?

DO> But we could have an option that trimmed the "ejb" off the name 
DO> and tried to find a matching bean.  This is spec-compliant, because 
DO> it falls under the case of "proprietary deployment tool."  :-)

DO> This is a "reasonable defaults" case that I think we should support. 
DO> Great idea, as far as I'm concerned.  So we would check (in the 
DO> following order):

DO> 1.  ejb-link, because we are mandated to respect this information 
DO> at deployment time by the spec.

DO> 2.  Any information in jBoss-specific deployment descriptors.  (This 
DO> is Rickard's "proprietary method," and should be checked second 
DO> to give the bean deployer the opportunity to override the information 
DO> programmed in the bean.)

DO> 3.  The ejb-ref-name, both trimmed and untrimmed (since putting it 
DO> in the "ejb" context is a recommendation, not a mandate, of the 
DO> spec.)  I think we should call this the "Oleg default."  :-)
It's yours idea, not mine. Better call it "Dan default" :-)
I proposed to check the untrimmed name.
I didn't mean any error hiding or proprietary defaults.
I just supposed that it is better to give the same name in ejb-name
and ejb-ref-name (namely, ejb/XXX) than to invent naming schemes.
And I supposed that in this case I can omit ejb-link and this would be
absolutely spec-compliant (I still think so).
But if people usually give different names - well, I'd better give up
in this discussion than vote for this dangerous "Oleg default."

Best regards,
 Oleg 




--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Problems?:           [EMAIL PROTECTED]

Reply via email to