Hi Buchi, I took a first look into your proposal and it's pretty much the same I intended to do and it looks really promising. Later on I will go deeper and try it out. But it really saved a lot of work (at least for me) so I can concentrate on writing the webadmin-interface. I think why I was running into problems is because I tried to write an independent block, which was not that integrated in james (like yours). I have to say that I'm not that experienced with avalon/phoenix so that I really appreciate your approach and work. I hope the james guys like it too and integrate it into james.
Later on more about that, thanks, pero -----Original Message----- From: Gabriel Bucher [mailto:[EMAIL PROTECTED]] Sent: Sunday, October 21, 2001 2:40 PM To: [EMAIL PROTECTED] Subject: Re: adding Blocks to James Hi Pero, I started around 3 month ago an implementation of a rmi-based admin-interface. I posted today a new proposal! I had never problems like you described! Please check out what I have done and im really interesting in feedback. Thanks, Buchi pero wrote: > Hi, > > I'm trying to implement a RMI-based admin-interface for James. Therefor I > wrote a new Block called 'JamesRMIServer'. Now I am trying to add this thing > to james. I managed it to include it into the james.sar-file and it is > executing fine (the JamesRMIManager has access to all important > James-Resources like Userstore etc.) But when I try to bind the class to the > RMI-Naming-Service (with Naming.rebind("//localhost/JamesRMIServer", > this); ) the SecurityManager denies to connect to the RMI-Port (1099). > Running the thing from command-line works fine. > After looking into the james-server.xml I found the policy-constraints which > say that every block should have full access. But, actually this is not the > case. > > Has anybody written a working RMI-interface for james? And how can I bundle > my Block without adding it to the james.sar-file? Or should I write the > JamesRMIServer within the james-package making it a part of james? > > confused, > pero > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
