On 4-Apr-08, at 9:43 AM, Henri Gomez wrote:
You can still use Apache, nothing stops you from doing that.
So thanks to activate ajp support in jetty.
We actually use mod_proxy with Jetty and it works great.
2) Many of IT manager don't want to have many instance to monitor
and
supervise and prefer having a single Servlet Container loaded with
many webapp/applications.
Not true. We have talked to a lot of IT people and we wouldn't be
taking
this course of action if it was going to sink us.
You known some IT people who want packaged solution, I know IT people
who want to have the choice of deployment. More choice, more
solutions.
More choice != more solutions. More fully supported choices == more
solutions. Very, very stark difference.
3) Sad to see an ASF member critics the Tomcat community. I'm not
sad
because I'm still commiter on Tomcat project and ASF member, but
because if it would be better to see your complains about Tomcat on
the tomcat list instead of Maven list.
Who if anyone is in a better position them an ASF member to
critique the
internals at Apache? No one else is going to do it. And like many
dealing
with people on the Tomcat mailing list I feel is a waste of time at
this
point after years of seeing what happens to people that do. I have
corporate
clients from very large organizations that have in not so many
words been
told to piss up a flagpole when a critical issue has been detected.
It's
just not the kind of environment I want to work in and many other
people
I've seen make many of the same comments.
An issue detected in Tomcat and not fixed ? Could you give me the
JIRAs ? May be I could take a look or ask some of the Tomcat experts
to help you, after all you're an ASF member.
I'm not interested anymore to be honest. I don't use Tomcat anymore
and I never will, and these particular instances the client can't be
disclosed anyway. But if you want to see the way the community
communicates people can just so look at the mailing lists and see how
people are treated. I think you have a couple people in particular who
are a problem but it spoils the whole Tomcat experience. This is why
Sun forked Tomcat, and why JBoss is even considering dumping Tomcat.
This is not an isolated incident.
At any rate I don't want to turn this into a Tomcat bashing session. I
don't use it anymore so it's not really an issue for me. I'm an
ecstatic Jetty user.
Everyone just thinks it's all well and good. My point is that I've
made my
decision and we decided Jetty is the choice for the future. Tomcat
has
benefited from Apache marketing, and natural selection has not been
able to
play out because of this. IMO Jetty should have been the standard.
Using
Tomcat for me is not a defensible position anymore.
Jetty is used by maven mojos for a long time (ie war test plugin).
What's your exact complains about Tomcat ?
With which release of Tomcat do you have problems ?
Do you heard about Costin works on Tomcat Light ?
For our commercial offering that's probably not going to happen,
and is not
going to hurt us as we know this from talking with clients already.
So no need for now to provide nexus as a standalone war.
But that doesn't stop you from helping us implement that mode of
operation.
Well I don't want to break anything in nexus. If it works for your
targeted clients with Plexus/Jetty, it's ok for me.
I don't have so many spare time for OSS and I think better to use it
to help 'the continually degrading Tomcat community'.
I want something sane to support in the long run.
I hope so.
Just a recommandation, activate the Jetty AJP support by default.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
Selfish deeds are the shortest path to self destruction.
-- The Seven Samuari, Akira Kirosawa
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
