On Sun, 4 Feb 2001, Michael Quinn wrote:
Just a little update..
I have completed benchmarks for the initial apache default index.html.en
with 4 different http servers on Redhat 6.2 with AMD Thunderbird 650 and
128MB Ram.
Apache 1.3.14
Tomcat 3.2
Weblogic 5.1
Orion 1.4.5
I couldn't
how many requests/responses were simulated?
- Original Message -
From: Michael Quinn [EMAIL PROTECTED]
To: Orion-Interest [EMAIL PROTECTED]
Sent: Sunday, February 04, 2001 3:52 AM
Subject: RE: Benchmarks should be better
Just a little update..
I have completed benchmarks for the
Hello Allen,
DataSources gives you one advantage on the client side: Security.
If you use a direct JDBC connection to a Database, your username,
password and URL have to be placed in your class. A Datasource hides
all those details, so if some one decompile your class (even JAXed
classes are not
there
was something like that in the original servlet spec, but it's deprecated now;
however, i think the (undocumented?) Administrator object(orionconsole says it's
in 'java:comp/Administrator') can do that.
-Original Message-From:
Reid Hartenbower [mailto:[EMAIL
Uhmmm, I agree, I was confused because someone said they still needed the
JDBC drivers on the client, and assuming you use the portable method of
DataSources, there should be no reason that they would need to have the JDBC
drivers, it is all handled container side with the datasource.
Al
sorry for the delay, I'll try and explain it again:
let's say I (Juan) am a bean developer. Let's say you (Eric) are the
application assembler, and let's say Lauren Commons is the deployer.
I build a bean. I package the bean in a jar, then pass it on to you. It has
some(but not all) of the info
Randahl look in $orion\applications\YOUREAR\YOURWAR\yourpage.jsp
if you edit a .jsp in that dir and browse it, orion will recon the change,
recompile for you, voila!
no need to rebuild anything
JP
-Original Message-
From: Randahl Fink Isaksen [mailto:[EMAIL PROTECTED]]
Sent:
I've got a pair of web applications hosted on my server, each hosting a
single stateless session bean. The intent of these two is to get two beans
talking between applications. To test this, one bean (Calc) returns the
square of a number passed to it by the other bean (EJBTest).
Using the Calc
