Re: [Webwork-devel] WW/JavaOne get together

[<ma...@sm...>]

My comparison with Jetty is not based on a web
container but the fact that it is a standalone project
that has hooked up with JBoss. JBoss has expanded to
provide additional offerings such as JBoss.Net which
uses Apache Axis another separate project. I believe
that WW could be independent but work closely with
JBoss to deliver some unique things. Obviously, this is
at a conceptual level but there is possibility. Maybe,
Rickard could enlighten us on some possibilities.

Has Jetty lost user base because they are working with
JBoss? I don't think so. I think either directions for
WW is a win, but I disagree with your analysis.

-Matt

On Tue, 02 April 2002, "Victor Salaman" wrote

> 
> >I think OS has done a good job and working with them
would be good, but
> >throwing in a new opportunity such as JBoss adds a
new twist. For instance,
> >Jetty is a separate project that is embedded in
JBoss so why not WW? I
> >believe JBoss could use a good web tier framework,
and I think its coat
> >tails have grown since it won best app server from
JavaWorld. In addition, 
> >I
> >know Jakarta solicited them to come aboard but Marc
set them straight. So,
> >my vote is JBoss. I think WW has the greatest
potential to grow under
> >JBoss's umbrella.
> >
> 
> Matt,
> 
> With all due respect, What are you smoking? The
reason for Jetty being 
> integrated with jBoss is because jBoss has no web
container. And that being 
> the case, jboss needed to be integrated to a web
container to avoid being 
> chewed up by the competition. That is all well and
understandable.
> 
> JBoss is an excellent revolutionary product which has
a lot of potential, 
> but it's still an appserver, and WW is a framework to
be used on any 
> appserver  (with webcontainer or not). I really don't
see what could be 
> gained technically by integrating WW to jBoss (and I
really don't know what 
> there is to integrate, as WW already works flawlessly
in most 
> environments... if you do, please enlighten me!).
> 
> WW is also decoupled technology that is meant to be a
multi-purpose 
> framework not only for web but for any type of
application. By focusing on 
> integration we're just diluting the original intent
of the product.
> 
> <rant>
> And if what you're suffering is Struts envy,
everytime you feel that way, 
> write a JavaWorld article :) ... The only reason it
has a strong userbase is 
> because of marketing merits not technical ones.
> </rant>
> 
> By even thinking on integrating to a specific vendor,
we're already loosing 
> userbase, as a lot of people using WW are not
jBoss/Jetty, jBoss/Tomcat 
> users and some will never be.
> 
> 
>
_________________________________________________________________
> Send and receive Hotmail on your mobile device:
http://mobile.msn.com
> 
> 
> _______________________________________________
> Webwork-devel mailing list
> Web...@li...
>
https://lists.sourceforge.net/lists/listinfo/webwork-devel