> -----Original Message-----
> From: Cameron Taggart [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, January 03, 2006 1:49 AM
> To: [email protected]
> Subject: Re: [Wicket-user] Wicket outside of servlet container
> 
> Which version of Jetty are you using?  Are you thinking of 
> replacing Jetty with MINA?  Why?  I'm very interested in 
> hearing more about your setup.
> 

Yup.  I'm trying to get completely away from J2EE.  Jetty's great, don't
get me wrong.  Best servlet container out there in terms of performance,
footprint, embeddability.  I've been a Jetty fan for years.  But... It's
still a servlet container.

One thing that makes Wicket so fresh IMO is the potential it brings to
do web development outside the fat J2EE app server.  Wicket may be the
only thing that can save Java from the coming Ruby on Rails revolution
in the web application space.

And there's still a need for a small footprint, highly performant and
scalable web application solutions for small and embeddable devices.

With Wicket we can say goodbye to JSP forever (thank God!).  It's just
POJO's, and that's a beautiful thing IMO.  Makes it very flexible and
reusable, especially how the Wicket developers have abstracted the
servlet and http protocol away into a nice separation of concerns
architecture.

Now.. MINA is an awesome network protocol development framework.
Extremely performant and very robust.  Handles connection sessions,
provides codec and business logic abstraction, protocol handler plugins,
and filter injections both at the IO and protocol handler layer -- which
gives me the same thing servlet filters gives me.  Anyway, there's work
afoot on a MINA-based webserver that is reported to significantly
outperform Apache2 with massive simultaneously connections.  It'll be a
cinch to drop this web server in an OSGi runtime along with my Wicket
application, and I'm good to go both on a big server box or on a small
device like a router or a media device box.  And if I'm building servers
(like an Identity Management/AuthZ/AuthN server like Safehaus, or an
LDAP server, or whatever) why should I have to embed a frickin' servlet
container just to host an remote server admin web application?

With Wicket, I can easily package by web application to deploy as a WAR
in a traditional servlet container, or package an OSGi bundle for
embedded deployment in a non-J2EE runtime.  I'm already doing this.
It's a simple Maven2 build switch.  That's a powerful option I have with
Wicket.  Now with the OSGi architecture, and it's hot-swappable
plugin/bundle capabilities, and the component nature of the Wicket POJO
architecture together, I *could* deploy my Wicket based application as a
series of decoupled bundles or plugins.  Reusability and de-coupleness
at the compile time is a great thing, but reusability and de-coupleness
at runtime is a really beautiful thing.  Imagine adding new pages to my
web application, by simply pushing down an new bundle to my OSGi
runtime?  Think something like what Eclipse has done to the desktop IDE
for web application.  Plugin functionality for the web application.
J2EE and servlet container was not architected for this kind of
robustness -- OSGi completely is -- which is why Eclipse settled on OSGi
as a runtime platform.  With Wicket as the web app framework, I just
need a HTTP protocol pipe input/output stream and some session
management, and throw it over to a handler to let Wicket process the
request and generate the HTML response.  MINA is perfect for this.

I'm going to be embarking on a proof-of-principal.  Safehaus will mostly
like host the project, and I'll try to use my blog as sort of an
electronic developer notebook...

-- timothy


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to