I have done something similar however instead of binding the object directly to JNDI I have made it a stateless session bean on the server.
I don't think I can do what I need (a logger) with a bean. I need a "live" object to keep track of events in an application (the application will notify the logger) and to notify clients (Remote Objects too) about those events.
Couldn't you just say that Message-Driven Beans are meant for that??? :P :D
I feel so ashamed.
OK.... a little update. I realized that Message Driven beans wouldn't be able to achieve everything I needed, so I went back to the "lab". ;)
After reading a little about RMI-IIOP (from Ed Roman's book on EJBs) I realized I was making a mistake. I have to use RMI-IIOP and not just RMI to get in touch with the Remote Object (the logger client).
So instead of extending RemoteObject on the client, I extended PortableRemoteObject. Then I was able to recieve the client instance on the server side (and be able to make remote calls on it).
Hope this information is of any use to anybody.
Thnaks for reading anyway! ;)