Paul, absolutely no problem with that. I'm glad to see jo! work as component in Avalon. If you have something specific about Sevak on your website I should point to, please send me the URL.
Cheers, -hendrik > -----Ursprüngliche Nachricht----- > Von: Paul Hammant [mailto:[EMAIL PROTECTED] > Gesendet: Sonntag, 22. September 2002 05:47 > An: Hendrik Schreiber > Cc: Avalon Applications Developers List > Betreff: Re: [Fwd: [ANN] jo! 1.0 as sar] > > > Hendrik, > > I have just committed changes to the Sevak application in Avalon-Apps > that means it has two ways of launching webapps under phoenix control. > The first was Catalina (now 4.1.10), and the new one is Jo! capability. > Catalina still only partly works in that it really only does static > pages well. Jo!, of course, works perfectly. Which of the two is now a > assembler's choice. > > What I have done is taken the three 'integration' classes from your CVS, > changed them a little, and booked them into Apache's CVS. I have > changed the license for the three files from LGPL to Apache license.... > I think you'd agreed to this. It is a small thing, and only three > files, but if there is a problem we could back port the changes to your > CVS (basically, this is Sevak compatability). > > Regards, > > - Paul > > >Paul, > > > >it seems the interface consists of only two methods. That should > be a piece > >of cake to implement. It seems that only the already existing > method names > >of the current implementation have to be adjusted... > > > >I wouldn't mind having the stuff in your CVS. Maybe someone in the > >avalon-phoenix community could pay some attention to it? I have more than > >enough to do to keep jo! in shape. Although I could provide the initial > >code. > > > >-hendrik > > > > > > > > > > > >>-----Ursprüngliche Nachricht----- > >>Von: Paul Hammant [mailto:[EMAIL PROTECTED] > >>Gesendet: Samstag, 27. Juli 2002 12:20 > >>An: Avalon Applications Developers List; [EMAIL PROTECTED] > >>Betreff: Re: [Fwd: [ANN] jo! 1.0 as sar] > >> > >> > >>Hendrik, > >> > >>Great news! > >> > >>Is there any chance you could help out with the Sevak service ( > >>http://cvs.apache.org/viewcvs/jakarta-avalon-apps/sevak/src/java/o > >>rg/apache/avalon/apps/sevak/ > >>) > >>The Sevak app in avalon-apps is about trying have Catalina mountable as > >>a Phoenix block. It mostly works. The service that the Catalina block > >>implements is probably implementable by the Jo! block. > >>What would having Jo! implement that service give us ? Well > >>comoditization for a start. The developer develops for an arbitary > >>webserver and the assembler/deployer chooses which to use > >>(Catalina or Jo!). > >> > >>This sounds like it could be bad for Jo!, but it is not really on two > >>counts : > >> > >>1) A widely implemented API yields a larger overall userbase. > >>2) Jo! is smaller than Catalina - it is going to be the first choice for > >>many assemblers. > >> > >>If you're happy with this idea we could make a sevak-api.jar for you to > >>import. Or we could host the block for of jo! here (we have your jars > >>in our CVS). > >> > >>What do you think? > >> > >>Regards, > >> > >>- Paul > >> > >> > >> > >>>-----Forwarded Message----- > >>> > >>>From: Hendrik Schreiber <[EMAIL PROTECTED]> > >>>To: Avalon-Phoenix <avalon-phoenix-dev@jakarta.apache.org> > >>>Subject: [ANN] jo! 1.0 as sar > >>>Date: 26 Jul 2002 12:49:33 +0200 > >>> > >>>hey, > >>> > >>>thought you might be interested. there is a new jo! release - > >>> > >>> > >>yeah, finally > >> > >> > >>>it's 1.0! > >>> > >>>jo! is a small webserver supporting servlet api 2.2 and jsp 1.1. > >>> > >>> > >>It's open > >> > >> > >>>source and free and can be used as webserver component in > avalon-phoenix. > >>> > >>>I built a SAR (which contains the block etc.), which you can > >>> > >>> > >>download from: > >> > >> > >>>http://prdownloads.sourceforge.net/tagtraum-jo/avalon-jo1.0.sar ?download >>> >>>I will now concentrate on 1.1 (servlet 2.3/jsp1.2). >>> >>>cheers, >>> >>>-hendrik >>> >>>http://www.tagtraum.com/ >>> >>> >>>-- >>>To unsubscribe, e-mail: >>> >>> >><mailto:[EMAIL PROTECTED]> >> >> >>>For additional commands, e-mail: >>> >>> >><mailto:[EMAIL PROTECTED]> >> >> >>> >>> >>> >>>-- >>>To unsubscribe, e-mail: >>> >>> >><mailto:[EMAIL PROTECTED]> >> >> >>>For additional commands, e-mail: >>> >>> >><mailto:[EMAIL PROTECTED]> >> >> >>> >>> >>> >>> >>> >> >> >> > > >
