Peter Royal's answer is correct, but also ...
See www.enterpriseobjectbroker.org is the home of the most complex usage of AltRMI. sourceforge.net/projects/marathonman will shortly commit some simple but concrete usage of AltRMI.
You are best to parcel all interfaces plus serializable exceptions and value-objects into a single jar and have that on client and server side. At the moment, the client will only prng across proxies from the server, not the interfaces themselves etc.
Regards,
- Paul
Hi,
I generate proxy classes using the Altrmi Ant task
org.apache.excalibur.altrmi.generator.ant.ProxyGenerationTask for a
component interface. Now that component interface has methods that return
some other object. When I look into the generated sources for the proxies
(AltrmiGenerated*.java) I see that there is a proxy class with methods for
each method in the interface but the objects returned by that interface
are there just as before. That might not work sometime, as in my case
using JNI, if these proxy classes are used on the client side maybe on a
different machine. At lest that is how I understood it.
I would have to jar up the proxy classes, and add them to the classpath of
the client (only also server?). But then I would get such a JNI-wrapping
Java class back and *%$§! exceptions. So how can one create proxy classes
for these returned objects as well? Just adding the interface to the
altrmiproxies task somehow merged the two interface and definitely did not
produce what was intended.
And finally is there some real life example of how to use client-side and
server-side factories. In the jakarta-avalon-app demo there is a
server-side and in some test program deep in excalibur-altrmi there is
client-side example but there are so overwhelmingly many classes there
that it would be godd to get some more explanation.
.. because Altrmi looks really wonderful!
:-)
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
