andrew cooke | 25 May 15:43

Endpoint Properties for 2.0 (in RMI and more generally).


I just realised that there's no way to send endpoint properties in the XML
config.  Thinking back, I think I've always switched to connector
properties (which are now typically named attributes).  However, RMI has
some endpoint properties which are not configurable on the connector - the
method argument types used in the call.

Now it makes sense for this to be an endpoint, rather than a connector
property (as I think Ross explained to me a while back in the discussion
on endpoints).  But how should we configure such things in the new schema?

- Add these properties to the connector and force the user to use
different connector instances.

- Write a transport specific endpoint schema

- Extend the generic endpoint schema to include properties.

The second of these seems best, but I'm worried I am missing something here.

Comments?

Thanks,
Andrew

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

(Continue reading)

andrew cooke | 25 May 15:52

Re: Endpoint Properties for 2.0 (in RMI and more generally).


*set* endpoint properties.  I have no idea why I regularly use the wrong
word in emails.  It annoys me as much as it must everyone else...  Andrew

> I just realised that there's no way to send endpoint properties in the XML
> config.  Thinking back, I think I've always switched to connector
> properties (which are now typically named attributes).  However, RMI has
> some endpoint properties which are not configurable on the connector - the
> method argument types used in the call.
>
> Now it makes sense for this to be an endpoint, rather than a connector
> property (as I think Ross explained to me a while back in the discussion
> on endpoints).  But how should we configure such things in the new schema?
>
> - Add these properties to the connector and force the user to use
> different connector instances.
>
> - Write a transport specific endpoint schema
>
> - Extend the generic endpoint schema to include properties.
>
> The second of these seems best, but I'm worried I am missing something
> here.
>
> Comments?
>
> Thanks,
> Andrew
>
>
(Continue reading)


Gmane