On Sun, 2002-02-24 at 10:30, Ted Husted wrote:
> Leo Simons wrote:
> > 2) a statement of intent in important places on the website.
> > I'm guessing that putting "we would like to see tomcat
> > integrate with avalon" on the projects' respective websites
> > would mean that such will happen sooner.
> 
> My concern would be that this promotes a "We are Borg" attitude.
> 

+1 That looks like the kind of statement that cannot be reached by
consensus.  I'm sure there are two sides to that idea..  

> Why would "we" like to see Avalon integrate with Tomcat? Why not Jetty
> or Resin? 
> 

*shrugs* if the Avalon folks want to see it then I guess they'd
contribute to Tomcat..  

> If our committers are choosing to use Tomcat because it meets their
> real-life needs, then why would "we" have to tell them that. Won't they
> just do it because they need it?
> 

IMHO, there should be a *slant* towards inter-Apache-community
cross-breeding.  Not Nazi enforcement...

> IMHO, committers should decide what is best for their product first. If
> we all do that, and we all create best-of-breed products, then
> interoperability will be a natural occurance. 
> 

+1

> If it is not a natural occurance, then we are mixing politics with
> technology ... We would simply be replacing the Dark Lords with a Dark
> Lady.
> 

*shrugs* Ladies are prettier 

> AFAIK, we don't tell Jakarta committers to use Ant. They choose Ant
> because it is a great tool. The same should go for every Jakarta or ASF
> product.
> 

+1 - Ant RULEZ!  Make SUCKS!

> Meanwhile, I do think documenting how J2SE (Standard Edition)
> technologies can provide an end-to-end solution is a great idea. For
> example, jGuru is running on Resin, Lucene, James, and JSPs. Scales
> great, and not an EJB to be found. 
> 

+1

> So, should we (meaning I) write that up as a case study and post it on
> the site? Or, pass because they are not using Tomcat?
> 

I think they should be using SOME jakarta technologies otherwise it
kinda doesn't look like the right site, but *shrugs*.

> AFAIK, Apache is part of the JS2E group, rather than the J2EE group, so
> it seems to me that promoting J2SE solutions is a natural thing for us
> to do, regardless of who provides the underlying product.
> 

IMHO: g/Apache/s//Jakarta/g

(Httpd has little to do with J2-anything)

Right, but I think providing "server-side" alternatives to J2EE is a
good thing.  Whether Jakarta should do it *shrug*...I think its a good
idea...  But its already happening -- Thanks Paul Hammant..  That seems
like the best way to show the "Jakarta Position" to the JSPA..  There is
nothing like doing something better to really make the point sink.  Will
it be better *shrugs* hope so..  It will certainly be more open.  I
applaud Paul et al's efforts and I'll come around as soon as my plate
clears some (I mean it).

Oh the amazing power of those who do.

-Andy

> -- Ted Husted, Husted dot Com, Fairport NY US
> -- Developing Java Web Applications with Struts
> -- Tel: +1 585 737-3463
> -- Web: http://husted.com/struts
> 
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
> 
-- 
http://www.superlinksoftware.com
http://jakarta.apache.org - port of Excel/Word/OLE 2 Compound Document 
                            format to java
http://developer.java.sun.com/developer/bugParade/bugs/4487555.html 
                        - fix java generics!
The avalanche has already started. It is too late for the pebbles to
vote.
-Ambassador Kosh


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to