geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dain Sundstrom <>
Subject Re: [XML Parsing]
Date Fri, 05 Sep 2003 07:36:51 GMT
The reflective mapping is build inside the running container on the 
server side during startup and is private to the container.  Clients 
never see it, so you have nothing to worry about.


On Friday, September 5, 2003, at 01:03 AM, Sagenschneider, Daniel A 

> Hi all,
> I've just joined the mailing list and have read the last few messages 
> relating to matching to target methods (I assume this to be the client 
> calls on the EJB interfaces to matching target methods of the EJBs - 
> please correct me if I'm wrong).
> To put a vote against reflective mapping, Sun specs indicate that the 
> EJBs are to be referenced via their interfaces for extended periods of 
> times (it indicates potentially years).  If a reflective mapping were 
> to be utilised, it would allow the loose coupling to have the EJBs 
> upgraded on the server (with potentially changing interfaces) thus 
> allowing the client to continuously access the EJBs.
> The other potential is to formulate a naming system that can cater to 
> versioning of the EJB interfaces, which will ultimately require having 
> to uniquely identify overloaded methods (i.e. complete method 
> signatures) - this may be as expensive to decode as it would take the 
> lookup reflectively.
> NOTE: if tight coupling between Server EJB version and Client EJB 
> version is required then this will not be an issue.
> Regards,
> Daniel Sagenschneider

  * Dain Sundstrom
  * Partner
  * Core Developers Network

View raw message