Hey
"Castro, David" wrote:
> details:
> Declare a marshalling wrapper exception. Throw it from the marshalled
> invoke and invokeHome methods. Catch it in the calling methods and throw
> the wrapped exception.
>
> It is still necessary to catch and unwrap the exception in the other callers
> (in interfaces):
> 2x HomeProxy
> 1x EntityProxy, StatelessSessionProxy, StatefulSessionProxy
>
> He makes the marshalling exception an inner class of JRMPContainerInvoker.
> Is that appropriate, since it needs to be used by callers from interfaces?
> Or should it just be put in interfaces as an outer class?
>
> Otherwise this seems like the right approach. Appreciate comments, I am
> happy to implement and test if no one else wants to.
The approach is right, but hey, why not use UndeclaredThrowableException
*as* the container? :-) No need to introduce another class that does the
same thing.
> ALSO: ?????. in HomeProxy, line 186, we call the marshalled version of
> invoke but do not unmarshall the result. Here we are just calling remove
> (in place of removeByPrimaryKey) so I don't know what kind of return value
> we would be getting - maybe it will always be null and this is ok. It
> seemed strange though so I thought I would point it out.
It looks strange, but the result is null, so we're ok anyway.
regards,
Rickard
--
Rickard Öberg
Email: [EMAIL PROTECTED]
