"Smith, Curt H." wrote: > - You don't want the application developer to have to catch and > re-bind/lookup the home, object, stub > and re-dispatch the method call, all inline code. The app server's code > should catch system failure > exceptions in the Stub/Handle and transparently re-bind and re-issue the > method call. How many times should the appvendor's stub do this, do you think? Just curious. Cheers, Laird =========================================================================== 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".
- Resiliency: method level failover, who provides this Smith, Curt H.
- Re: Resiliency: method level failover, who provid... Eric Sorensen
- Re: Resiliency: method level failover, who provid... Jean-Baptiste Nizet
- Re: Resiliency: method level failover, who provid... Laird Nelson
- Re: Resiliency: method level failover, who provid... James Cook
- Re: Resiliency: method level failover, who provid... Gene Chuang
- Re: Resiliency: method level failover, who pr... J. Matthew Pryor
- Re: Resiliency: method level failover, who provid... Smith, Curt H.
- Re: Resiliency: method level failover, who pr... Eric Sorensen
- Re: Resiliency: method level failover, who provid... Smith, Curt H.
- Re: Resiliency: method level failover, who provid... Chris Raber
- Re: Resiliency: method level failover, who provid... Gene Chuang
- Re: Resiliency: method level failover, who pr... Edward Barrett
- Re: Resiliency: method level failover, wh... Rob Woollen
