On Jul 31, 2006, at 6:28 AM, Venkata Krishnan wrote:
Hi Jeremy,
It seems you have implemented the RMI Binding :-).
Not really, I just did some of the conversion to the new SPIs. There
is still quite a bit to do.
I am looking at it
to get an understanding of it. Please help me with the following: -
- Is there a testcase or a sample that I can try out using this RMI
binding.?
Nope.
- From another discussion that you folks are having in the context
of the
JSContainer, I understand that there must be a default.scdl for the
RMI
Extension. I don't find it if there must exist one. Am I missing
something
here?
Nope.
- From the implementation I observe that the service interface must be
extended from 'java.rmi.Remote'. Does this mean that if I have
some POJO
implementations that I wish to expose as RMI services, then I must
rewrite
the interfaces and implementations or atleast wrap the existing
implementation. Making use of the service interface, can we not
dynamically
create a RMI interfaces as part of the binding implementation?
I made the simplification for now that the user must specify an RMI-
compatible interface in the <service> but ultimately they should be
able to use any interface contract they want (e.g. wsdl). To support
that we are likely to need to be able to generate a Java interface on
the fly.
Both of these are separate from the interface used by the component
(which is necessary given the component may not be Java at all). The
binding does by mapping methods in the service and the reference
invokers.
Do let me know if I can help you do any or all of these if they are
supposed
to be done. Thanks.
There is still quite a bit to be done. I think this is a good one to
get going as it is a fairly simple binding.
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
