RE: Displaying errors in JSP

2001-10-03 Thread Michael Laccetti 

System.out.print() - server console
out.print() - HTML page

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of EXT-Vaze,
Vinay G
Sent: Wednesday, October 03, 2001 12:09
To: Orion-Interest
Subject: Displaying errors in JSP


If I have a code block such as


%
  try {


  }
  catch (Exception e) {

 }
%


inside a JSP, how do I output error to either the browser or
to the server console ?

--
Vinay Vaze

M/S : 7H-80
Phone  : (425)-865-2929
Email   : [EMAIL PROTECTED]

RE: Orion and Toghether or JBuilder

2001-09-05 Thread Michael Laccetti 
Title: Message



I 
thought I sent this message yesterday, but at the same time, it appears that I'm 
wrong. Try checking this article out for using JBuilder to debug 
applications through Orion: http://www.orionsupport.com/articles/jbuilder-debugging.html

I'm 
using JBuilder 5 Ent, and it works perfectly.

  
  -Original Message-From: 
  [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED]] On Behalf Of Cristian 
  DonciulescuSent: Wednesday, September 05, 2001 04:35To: 
  Orion-InterestSubject: Orion and Toghether or 
  JBuilder
  
  Is 
  there a way to integrate Orion Application Server with Together 5.2 or 
  JBuilder 5? We would be interested to know whether we can use the debugger 
  included with Together (JBuilder) for debugging applications deployed on Orion 
  Application Server.
  
  Thanks!
  
  Get your FREE download of MSN Explorer at http://explorer.msn.com

Orion and Sax/JDom

2001-09-04 Thread Michael Laccetti 
Title: Message



I've 
recently installed Orion 1.5.2 on a linux test machine, and installed our app on 
it. It worked fine under 1.4.6, but for some reason, when I dump it under 
1.5.2 I keep getting a SAX2 exception: SAX2 driver class not found. 
Has anybody seen this before, and better yet, fixed it? I've tried 
everything that I can think of. I even grabbed the latest version of JDom 
and installed that. Please help!

-Michael LaccettiDeveloper, Eldan 
Software[EMAIL PROTECTED]

RE: Orion and Sax/JDom

2001-09-04 Thread Michael Laccetti 
Title: Message



I 
did a fresh install, downloaded the latest zip and installed it. I've 
tried downloading the latest version of xerces and replacing the version with 
1.5.2 with that. Again, still getting the SAX2 not found exception. 
Is there a specific order to setin the classpath?

  
  -Original Message-From: 
  [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED]] On Behalf Of The 
  elephantwalkerSent: Tuesday, September 04, 2001 12:04To: 
  Orion-InterestSubject: RE: Orion and Sax/JDom
  Michael,
  
  We 
  use jdom b7 and orion 1.5.2 all of the timewith no problems.We use 
  jdom with crimson, which is the default parser with jdom and orion version 
  1.5.2.Orion 1.4.6 used an old version of xerces. Did you use 
  autoupdate.jar to install 1.5.2 or did you use a fresh install? Autoupdate.jar 
  is a little unreliable, so I would do a fresh install.
  
  regards,
  
  the 
  elephantwalker
  
  
-Original Message-From: 
[EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED]]On Behalf Of Michael 
LaccettiSent: Tuesday, September 04, 2001 8:33 AMTo: 
Orion-InterestSubject: Orion and Sax/JDom
I've recently installed Orion 1.5.2 on a linux test machine, and 
installed our app on it. It worked fine under 1.4.6, but for some 
reason, when I dump it under 1.5.2 I keep getting a SAX2 exception: 
SAX2 driver class not found. Has anybody seen this before, and better 
yet, fixed it? I've tried everything that I can think of. I even 
grabbed the latest version of JDom and installed that. Please 
help!

-Michael LaccettiDeveloper, Eldan 
Software[EMAIL PROTECTED]