Re: Glyph project announced and initial release

> I do have one question, however.  What is the purpose
> of the parent interface in the @Exportable annotation?  From the description
> in the blog, it sounds as if the 'Administrable' interface would have been
> picked up anyway so I'm not sure what purpose it serves (although I'm sure
> it serves some purpose).

Hi Tom-

Currently @Exportable will only add in an interface declaration to the
'implements ...' portion of  a class, if it extends java.rmi.Remote,
otherwise it would attempt to
a) Tag the Smart proxy as implementing all interfaces, which is not
necessarily what you want
b) If an interface has some remote methods (i.e. throwing
RemoteException) and some non-remote methods, it wouldn't be able to
fill in the client side methods on the smart proxy.

I'm trying to put together some thoughts on how to ease this conflict,
perhaps by merging 'snippets' of code into the smart proxy so that it
can create a proper smart proxy i.e. does some remote and some client
work. As a preliminary thought Glyph could always get the check if the
@Expotable class also has @Service and then adds in the Administrable
interface.

Although the parentInterfaces attribute works, it's is by no means
perfect, and addressing it does have some issues.

Thanks for your feedback

--Calum

BTW: I was saddened to hear of the closure of the Mayflower project.

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff JAVASPACES-USERS".  For general help, send email to
[email protected] and include in the body of the message "help".

To view past JAVASPACES-USERS postings, please see:
http://archives.java.sun.com/archives/javaspaces-users.html