Re: Setting codebase on a per entry basis....

Ewan Silver wrote:
> I am having a little codebase issue and am looking for some
> alternative viewpoints. My situation is as follows:

> The issue
> is: how does the Generic process set the codebase for the new Entrys
> that were created by the FactoryEntry?
>
> One solution would be to ensure that the codebase of the generic
> process always contains the details of any entry that it will ever
> potentially see. This is not really feasible because it will involve
> updating the codebase of many different generic processes everytime a
> new Entry type is created. This will be an administrative nightmare.
>
> What I really need is a way to programmatically set the codebase on a
> per Entry basis as it is written into the Space.

The RMIClassLoaderSPI mechanism is the primary mechanism for arbitrary
annotations for Class based control.  By overriding getClasssAnnotation(Class),
you can look at the annotations that are being returned.  You can call
super.getClassAnnotation(Class) and just log it before returning it.  This will
help you to see what is actually happening, more directly.

Gregg Wonderly

===========================================================================
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