AIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 05, 2000 7:25 AM To: [EMAIL PROTECTED]
Subject: Re: Performance & Scalability Concern
Tom Wnuk wrote:
> I just migrated some ejb's from a Weblogic 5.1 installation to
Orion. The > version
of those gray areas I think.
At least I don't have to 'hack' the jar files and Orion has provided
a
switch.
Tom
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 05, 2000 7:25 AM
To: [EMAIL PROTECTED]
Subject: Re: Performance &am
Oops, forgot to post to the list.
Sorry Tom.
Original Message
Subject: Re: Performance & Scalability Concern
Date: Wed, 05 Jul 2000 07:24:32 -0700
From: Eric Richardson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
References: <[EMAIL PROTECTED]>
Tom Wnuk wrote:
&
First, a few clarificatons
Orion does not default to Sun's parser. By default Orion uses Sun's JAXP
Optional package, which by default uses Sun's XML Parser. Orion uses this
parser mainly for two things:
1. Accessing all xml config/deployment files
2. Used by the XSLServlet
Hello Tom,
Tom Wnuk wrote:
> I just migrated some ejb's from a Weblogic 5.1 installation to Orion. The
> version I'm using is whatever was available from the web site about a week
> ago -- orion.jar dated 6-5-2000, v1.xx.
>
Try the latest one by doing a java -jar autoupdate.jar or get
http://
