[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [sca-j] NEW ISSUE: ejb binding @uri has the wrong schema
Some things that Henning Blohm said once are starting to come back to me about EJB3.
Here's more details of the problem, hopefully stated more clearly. The URI I'm looking at has two '#' characters:
<reference name="ejbReference">
<interface.java interface="packageName"/>
<binding.ejb uri="corbaname:iiop:localhost:2809/NameServiceServerRoot#ejb/componentName#packageName"/>
</reference>
Where componentName is a name that is used to uniquely identify the deployed EJB, and packageName is the Java package name of the Business Interface. The componentName is only needed if the Business interface is deployed twice. '#' was chosen because it's a character that would never be present in an EJB name.
This problem is self inflicted because the EJB 3.0 specs don't describe how to solve the "deploy it twice" problem. This is how IBM solved it. However, EJB3.1 looks to be solving the problem in a similar fashion.
To make this worse, in the course of further investigation today, I re-discovered that corbaName addressability for EJB is no longer required, so EJB3.1 has no impetus to avoid standardizing the '#' as a delimeter. We probably want to address this in the spec as well since we explicitly call out the use of corbaName.
I would like to continue supporting corbaName URLs for remote EJB3s, but that is becoming nearly impossible now if the binding.ejb @uri is an xs:anyURI. The assembly spec has a provision for bindings which can't use the @uri and suggests that such bindings would define their own mechanism for configuring endpoint information. I'd like to assert that the EJB binding as now arrived at that spot.
Direction for a proposal:
Given that EJB3 has backed away from corbaName, vendors are now free to invent all kinds of interesting schemes for addressing EJB3s remotely. If we think that anyURI might be too constraining (I do) then we should invent a new attribute or element to hold the endpoint configuration. My initial suggestion is something of type xs:string, but I'm open to other ideas.
Dave Booz
STSM, BPM and SCA Architecture
Co-Chair OASIS SCA-Policy TC and SCA-J TC
"Distributed objects first, then world hunger"
Poughkeepsie, NY (845)-435-6093 or 8-295-6093
e-mail:booz@us.ibm.com
David Booz---10/29/2008 03:16:35 PM---I am willing to believe I jumped the gun. Issues are easy to close if they don't get accepted.
From: | David Booz/Poughkeepsie/IBM@IBMUS |
To: | sca-j@lists.oasis-open.org |
Date: | 10/29/2008 03:16 PM |
Subject: | Re: [sca-j] NEW ISSUE: ejb binding @uri has the wrong schema |
From: | Anish Karmarkar <Anish.Karmarkar@oracle.com> |
To: | David Booz/Poughkeepsie/IBM@IBMUS |
Cc: | sca-j@lists.oasis-open.org |
Date: | 10/29/2008 02:45 PM |
Subject: | Re: [sca-j] NEW ISSUE: ejb binding @uri has the wrong schema |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]