Jon Stevens <[EMAIL PROTECTED]> wrote:
>
> FYI, I just *mostly* implemented the J2EE extensions for Turbine's
> Connection pool (the classes now at least implement the interfaces). It took
> me all of about 30 minutes.
>
> Have fun.
Thank you :) :) :)
Pier
--
Pier Fumagalli
on 2/1/01 5:54 PM, "Craig R. McClanahan" <[EMAIL PROTECTED]>
wrote:
> * JDBC Connections - javax.sql.DataSource and
> * JMS Connections - javax.jms.QueueConnectionFactory
> or javax.jms.TopicConnectionFactory
> * JavaMail connections - javax.mail.Session
> * URL connections - java.net.URL
>
> Th
on 2/2/01 12:27 PM, "Peter Donald" <[EMAIL PROTECTED]> wrote:
> At 11:10 2/2/01 -0800, Jon Stevens wrote:
>> Ok, I'm seeing other people discuss this without any sort of final decision
>> here, so I think we need to get back on topic. So far, top level package
>> names are expressly reserved for
Jon Stevens wrote:
>
> on the JAMES list: 2/2/01 3:07 AM, "Charles Benett"
> <[EMAIL PROTECTED]> wrote:
>
> > (FYI - Avalon is splitting, probably, into 3 packages: org.apache.avalon
> > - the design framework and utilities, org.apache.phoenix - the server
> > kernel based on avalon designs, a
On 2/3/2001 at 8:13 AM Peter Donald wrote:
> We can't force projects - especially new ones - to reuse existing
codebases but overtime we should encourage it.
Thanks for saying this better than I did, Peter. +1.
I'd like to be a good Apache scientist some day, but sometimes it's
hard to understan
At 11:10 2/2/01 -0800, Jon Stevens wrote:
>Ok, I'm seeing other people discuss this without any sort of final decision
>here, so I think we need to get back on topic. So far, top level package
>names are expressly reserved for top level projects.
Well not every one seems to obey it. Examples inc
At 08:33 2/2/01 -0500, Sam Ruby wrote:
>Now it irritates me that one has to have separate database pools for
>Struts, JetSpeed, and Cocoon. I don't honestly care how beautiful the
>internal APIs are, or compatible with some corporate strategy the solution
>is, I just want to be able to share dat
At 07:41 2/2/01 -0500, Ted Husted wrote:
>When considering the merits of a product, it is important to consider
>the human factor of both our users and developers. It's no secret the
>teams working on competiting solutions often "hate each other". Maybe
>that's a good thing. It may not be as effi
At 10:52 2/2/01 +0100, Ceki Gülcü wrote:
>
>Sorry. I inadvertently pressed Ctrl-e which made Eudora forward my
incomplete note. Here is the complete note.
>
>At 19:19 01.02.2001 -0800, you wrote:
>>on 2/1/01 6:45 PM, "Sam Ruby" <[EMAIL PROTECTED]> wrote:
>>
>>> [ Running, ducking, and grinning ;-
on the JAMES list: 2/2/01 3:07 AM, "Charles Benett"
<[EMAIL PROTECTED]> wrote:
> (FYI - Avalon is splitting, probably, into 3 packages: org.apache.avalon
> - the design framework and utilities, org.apache.phoenix - the server
> kernel based on avalon designs, and org.apache.cornerstone - commonly
on 2/2/01 1:34 AM, "Ceki Gülcü" <[EMAIL PROTECTED]> wrote:
> Sun is doing a great job at convincing people to use their technology. This is
> truly a Herculean task and imho constitutes a major achievement for Sun.
Nope. Sun is doing a great job emulating M$. JSP is only better than ASP
simply b
Hi,
Since there seemed to be wide support, all e-mails are now listed in "x at y.z" form.
If you are unhappy about this them give me a shout and I will change the e-mail
address relative to your entry. Ceki
At 09:27 02.02.2001 -0800, you wrote:
>Ceki Gülcü wrote:
>
>> Hello,
>>
>> Daniel Sava
Title: RE: Listing your e-mail address
+1
Ceki, is there a call for names/email addresses implied here? I know that mine isn't on the site, and it seems that you're contemplating making us all famous. :) :) :)
- Morgan
> -Original Message-
> From: Craig R. McClanahan [mailto:[E
Ceki Gülcü wrote:
> Hello,
>
> Daniel Savarese suggested that e-mail addresses on the "Who we are" page should not
>be listed directly as mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED] but as "foo at
>bar.com".
>
> This is will make it harder for spam robots to collect our e-mail addresses. For an
My 2c:
Instead of talking it would be easier to create another repository, say
"jakarta-utils" ( or just use jakarta-tool since it's there :-), and start
organizing the reusable code in avalon, turbine, tomcat, etc.
I don't see any problem with having 2 connection pools - as long as both
are s
>On 2/2/2001 at 8:33 AM Sam Ruby wrote:
In Jakarta, some of us have worked hard to produce something different
- a community centered around the building of related software. Perhaps
we are deluding ourselves. You tell me.
I would venture that if the goal of each Jakarta product were to be the
d
Ted Husted wrote:
>
> > The desire to work together is core to my thesis that
> > there is a Jakarta community here.
>
> There often seems to be an assumption that our resources,
> or community, is limited. There are a great number of
> Java developers in the world, and our numbers grow every
> da
Do not try to resist.
We must use Turbine.
JSP is futile.
Turbine is the only solution.
We are Borg.
Only Turbine knows the way.
We will assimilate you.
"Choose your enemies wisely ... for you will become them."
> Needless to say, I think that I'm going to star
> The desire to work together is core to my thesis that there is a
Jakarta community here.
There often seems to be an assumption that our resources, or community,
is limited. There are a great number of Java developers in the world,
and our numbers grow every day. A project like Struts, with a cl
Thanks!
Sam Ruby wrote:
> Tod Thomas wrote:
> >
> > Could anyone point me in the direction of some documentation
> > that describes implementation of xml push technology ?
>
> Here's a few:
>
> http://msdn.microsoft.com/msdnmag/issues/01/01/xml/xml.asp
> http://msdn.microsoft.com/net/ecma/main.a
> reaches almost 5'11"... And 4 inches are _something_ :)
>
> Pier (thinking: Tomcat is higher than anything else, I'm 6'0")
Which tomcat ? i'm about 6'7" :-)
Saludos ,
Ignacio J. Ortega
PS: Sorry for waste of bandwidth :)
-
At 20:47 02.02.2001 +1100, you wrote:
>At 09:22 2/2/01 +0100, Ceki Gülcü wrote:
>>
>>Hello,
>>
>>Daniel Savarese suggested that e-mail addresses on the "Who we are" page
>should not be listed directly as href="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED] but as "foo at bar.com".
>
>good idea. Oh
Sorry. I inadvertently pressed Ctrl-e which made Eudora forward my incomplete note.
Here is the complete note.
At 19:19 01.02.2001 -0800, you wrote:
>on 2/1/01 6:45 PM, "Sam Ruby" <[EMAIL PROTECTED]> wrote:
>
>> [ Running, ducking, and grinning ;-) ]
>>
>> - Sam Ruby
>
>
>
>Do not try to r
At 09:22 2/2/01 +0100, Ceki Gülcü wrote:
>
>Hello,
>
>Daniel Savarese suggested that e-mail addresses on the "Who we are" page
should not be listed directly as mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED] but as "foo at bar.com".
good idea. Oh and just in case no one saids it - You rock.
Chee
At 19:19 01.02.2001 -0800, Jon Stevens wrote:
>on 2/1/01 6:45 PM, "Sam Ruby" <[EMAIL PROTECTED]> wrote:
>
>
>
>Do not try to resist.
>We must follow Sun standards.
>Resistance is futile.
>J2EE is the only solution.
>We are Borg.
>JSP, XML and EJB is the only way.
>We
Ceki Gülcü <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> Daniel Savarese suggested that e-mail addresses on the "Who we are" page
> should not be listed directly as mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]
> but as "foo at bar.com".
>
> This is will make it harder for spam robots to collect our
Hello,
Daniel Savarese suggested that e-mail addresses on the "Who we are" page should not be
listed directly as mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED] but as "foo at
bar.com".
This is will make it harder for spam robots to collect our e-mail addresses. For an
example of how this will
27 matches
Mail list logo
