Gerhard, >>>when I extend the my class from a some >>>object and not from AbstractLogger, how >>>can I get the Logger??? >>> >>That's really cool dude. As you say we've lost loggable, be there is an >>interface we can impl for that to get it back. >> >Great to have it back... > Look at the source for AbstractLoggable and see that it only implements Loggable ..
However Berin and others have been working on a replacement. I guess in time all blocks hosted here will migrate to the new API. >>A few problems: >> >>1) Can't call it glue as it clashes with the SOAP service of the same name. >> >Ok, then I can name it different. I just took the same name as the SOAP >service (didn't thought much...). >Hmm copy and paste isn't always best... > he he. >Ok I see, this proposal needs some more thoughts as a 30min hack :). But >it was just a proposal and for me a exercise to get familar with phoenix, >cornerstore, blocks and stuff. I'm more that kind of dev who try, fail >and learn (ask the people from the cocoon2 project :)). >Of course it is not a valid cornerstore block and I only wanted some >new impressions to get behind the scene. And I got it, thanx for the >patience, mate. > No problem. Your grasp of Phoenix blocks only days after first landing here is excellent. >Let's put that RMI stuff, as you proposed, in our AvalonDB packages. >And maybe we can indentify a more generic solution later. > Indeed. You'll see the RemoteException problem immediately. We'll have to extend the DatabaseManager interface into a second RMIDatabaseManager interface add add the appropriate throws clause. I await your revised submission :-) As it's POETS day, I'm signing off shortly. Regards, - Paul H -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>