A Question

2001-02-23 Thread Richard Doust 

I'm not sure if I'm doing this right, but since I'm receiving e-mails from
this address, I'll try sending a question to it.
I am developing server side code that is using JAXP 1.0. The jaxp download
from sun includes a DocumentBuilderFactoryImpl class that comes from apache
that is in the crimson.jar file. Orion requires the same class and loads the
one provided by sun in parser.jar which does not implement the same methods
as the one in crimson.jar. I want to use the one in crimson.jar. I cannot
figure out how to get Orion to use this one. According to the docs on the
DocumentBuilderFactory interface, this can be established via System
Properties. I don't know what those are. I have looked at the .properties
files in Orion's distribution and I don't see anything that looks like it
would specify this.
Any help?
Thanks

RE: deployment

2001-02-23 Thread Richard Doust 

There's more to deploying the servlet than just setting the correct values
in the FORM tag, here's some thoughts:
Use "POST" as the method for processing the FORM. That's basically what it's
meant for.
The ACTION attribute should be the name of your servlet. If you've
configured your servlet in the .xml files that Orion uses for that purpose,
there's more to it than if you simply deploy your Servlet.class file to the
default directory which I think is /orion/default-web-app/WEB-INF/Classes.
Assuming you put it in the default directory, your servlet should get
invoked when you click on the form's submit button.
Try:
ACTION="/servlet/MyServlet"
/servlet is set up as the default servlet-webdir in the
global-web-application.xml file.
Rich

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Siling Zhang
Sent: Friday, February 23, 2001 3:11 PM
To: Orion-Interest
Cc: [EMAIL PROTECTED]
Subject: deployment


Does anyone know how to deploy a servlet and html form page on orion? What
should go into the Action=" " on the html form?
FROM METHOD = "get" ACTION = "??.."

Siling

RE: Debugging and orion

2001-02-23 Thread Richard Doust 

There are lots of posts in the archive available in the Orion Support
web-site on how to do this.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
[EMAIL PROTECTED]
Sent: Friday, February 23, 2001 4:55 PM
To: Orion-Interest
Subject: RE: Debugging and orion


Is it possible to debug JSP using JBuilder with Orion?

Thanks in advance!

-Original Message-
From: Edoardo Comar [mailto:[EMAIL PROTECTED]]
Sent: February 23, 2001 7:13 AM
To: Orion-Interest
Subject: RE: Debugging and orion


I've used jbuilder 4.0 (the free foundation version will be just fine) and
it is a great debugger.

you define a seprate project for orion server :
a project with no sources to compile but two libraries : one contains all
the orion binaries, one contains all your sources.
it has the orion server main class as main class, and the orion dir as
working dir.

select a source where you want to set a breakpoint (using the class
sleector, not the project pane because there you won't see your sources).
run the project in debug mode, use the browser or whatever client to invoke
your classes deployed in orion and jb will stop at your breakpoint.

BTW, exactly this same procedure works also with weblogic, jboss ... (well,
with wl6 you have to define a wrapper class that invokes weblogic server,
but apart form that it's the same).

Edo

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Kemp
 Randy-W18971
 Sent: 22 February 2001 20:07
 To: Orion-Interest
 Subject: RE: Debugging and orion


 Thanks, Mac.  I will give it a shot.

 -Original Message-
 From: Mac Ferguson [mailto:[EMAIL PROTECTED]]
 Sent: Thursday, February 22, 2001 12:20 PM
 To: Orion-Interest
 Subject: RE: Debugging and orion


 start orion with the following options:

 java -Xdebug -Xnoagent -Djava.compiler=NONE
 -Xrunjdwp:transport=dt_socket,se
 rver=y,suspend=y,address=whatever port you're going to use -jar
 orion.jar

 then create a new project in Bugseeker, selected Remote as the
 project type,
 and accepted all other default properties. Then set the
 Debug|Remote|Attach
 to type socket, Hostname=your server ip and Port=the port you specified
 above

 I like this setup, particularly for EJBs, but I'll be interested to see if
 Kawa will work any better.

 Cheers,
 Mac Ferguson
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED]]On Behalf Of Kemp
  Randy-W18971
  Sent: Wednesday, February 21, 2001 1:39 PM
  To: Orion-Interest
  Subject: RE: Debugging and orion
 
 
  Mac
 I would be interested in what steps you took to get Bugseeker
  connected to your remote VM, as would other people on the list.
  Are the steps short enough to include in an Orion Interest email?
  Randy
 
  -Original Message-
  From: Mac Ferguson [mailto:[EMAIL PROTECTED]]
  Sent: Wednesday, February 21, 2001 10:59 AM
  To: Orion-Interest
  Subject: RE: Debugging and orion
 
 
  I was in contact with Allaire's Kawa support recently and they
  told me that
  Kawa will support running/debugging Orion directly in it's IDE in an
  upcoming service pack, how soon it will be released is not certain, so
  caveat emptor. I found Kawa to be a pretty good basic IDE (I
  don't like lots
  of frills, I just want codesense and debugging), although in
  addition to not
  yet supporting Orion it was not a simple affair to add .class
 files to the
  CodeSense. If you want a decent step-thru remote debugger, check out
  Bugseeker (http://www.karmira.com) it was a bit tricky to get
 it connected
  to my remote JVM, but once I figured it out it was pretty good,
  it's *very*
  affordable, too. I also have recently become aware of JSwat
  (http://www.bluemarsh.com/java/jswat/), an open-source debugger. I am
  currently using the combination of Visual Slickedit for
 editing, Bugseeker
  for debugging and ANT for building, I occasionally fire up Forte (only
  because I have 256 MB memory and lots of time!) to do visual
 Swing stuff.
 
  Hope this helps,
  Mac Ferguson
 
   -Original Message-
   From: [EMAIL PROTECTED]
   [mailto:[EMAIL PROTECTED]]On Behalf Of Julian
   Richardson
   Sent: Wednesday, February 21, 2001 6:18 AM
   To: Orion-Interest
   Subject: Debugging and orion
  
  
   Hi,
  
   What tools / IDEs are people out there using to develop EJBs
  for use with
   Orion? At the moment we (as a project team, rather than company)
   are trying
   to standardise on an app server and IDE to use, requirements being the
   usual:
  
 cost
 speed
 flexibility
 resource usage
 debugging support from the IDE
  
   - I saw that someone mentioned using Kawa with Orion on the
 orionsupport
   website; has this combination been used by many people? (I'm new
   to the app
   server world, although I've been doing server-side Java work
 for several
   years now - I'm not used to environments where it's even possible
   to use an
   integrated debugger, but others

JAXP

2001-02-23 Thread Richard Doust 

I have been working on this problem all day. I have posted once before and
no one responded. I will try again.
I'm no Java expert and this is just my ignorance, but can anyone tell me if
I'm correct in my assumptions on this.
I am trying to develop server side code that runs under Orion that uses the
JAXP code that Sun has recently released. There are different versions of
parser.jar, xalan.jar and jaxp.jar distributed with Orion. Older ones. I
have tried replacing the older ones with the newer ones because my code
requires the newer ones and I guess that my code will be running in the same
image as Orion. Orion fails to start due to an exception while trying to
parse its configuration files. Putting the old .jar files back, it works
again. So, now it occurs to me that I'm basically stuck running with
whatever version of support code the tools I'm using are dependent on.
If I'm right, that means I can't use the latest version of JAXP until Orion
does? Is that right?
Anyone?
Thanks,
Rich

RE: JAXP

2001-02-23 Thread Richard Doust 

Tim,
Thanks for trying to help. I'll take a look in the mailing list archives. I
looked through the first set and didn't find anything, but I can look at
older stuff.
In the meantime, I'm replacing the jaxp.jar, parser.jar, and xalan.jar that
came with Orion (latest version) with crimson.jar, jaxp.jar and xalan.jar
from JAXP 1.1. After a thorough analysis of these jar files, I found that
xalan.jar and crimson.jar have most of what jaxp.jar and parser.jar have
plus a lot more.
One of the problems I have is that ant, jdk1.3, orion, and jaxp1.1 each come
with a different version of jaxp.jar. Orion, jdk1.3 and jaxp1.1 each comes
with a different version of xalan.jar. Orion and ant come with different
versions of parser.jar. (I have all four of these installed.) ant worked
okay after replacing its jaxp.jar and parser.jar with jaxp1.1's xalan.jar
and crimson.jar.
I start Orion with a classpath that includes the crimson.jar and xalan.jar
from jaxp 1.1. During the startup, when its trying to parse its config files
(I guess) I get a NoSuchMethodError at
org.apache.crimson.tree.AttributeSet.init(AttributeSet.java:139). I guess
I can't tell from this what method it's trying to call. It would be helpful
if I could. Somehow, it sounds internal to JAXP, and not like it's really a
problem of Orion.
Any more ideas now that I've given all these details? Love to hear from you
again!
Rich


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Tim Endres
Sent: Friday, February 23, 2001 8:33 PM
To: Orion-Interest
Subject: Re: JAXP


Hi Rich,

Could you narrow it down? Specifically which JAR breaks Orion. We have
replaced
the xalan.jar and xerces.jar files with version 1.2.2 and Orion is happy. Is
it
just the jaxp.jar file that is the issue?

Also, I believe that somewhere in the mailing list archives, you will find
posts
related to JAXP, but I do not know if they will address your specific
question.

tim.

 I have been working on this problem all day. I have posted once before and
 no one responded. I will try again.
 I'm no Java expert and this is just my ignorance, but can anyone tell me
if
 I'm correct in my assumptions on this.
 I am trying to develop server side code that runs under Orion that uses
the
 JAXP code that Sun has recently released. There are different versions of
 parser.jar, xalan.jar and jaxp.jar distributed with Orion. Older ones. I
 have tried replacing the older ones with the newer ones because my code
 requires the newer ones and I guess that my code will be running in the
same
 image as Orion. Orion fails to start due to an exception while trying to
 parse its configuration files. Putting the old .jar files back, it works
 again. So, now it occurs to me that I'm basically stuck running with
 whatever version of support code the tools I'm using are dependent on.
 If I'm right, that means I can't use the latest version of JAXP until
Orion
 does? Is that right?
 Anyone?
 Thanks,
 Rich

RE: JAXP

2001-02-23 Thread Richard Doust 

Here's some verbose output from java on the attempt to start Orion:

[Loaded org.apache.crimson.tree.DomEx]
[Loaded org.w3c.dom.DocumentType]
[Loaded org.apache.crimson.tree.XmlWriteContext]
[Loaded org.apache.crimson.tree.XmlDocument$ExtWriteContext]
[Loaded org.w3c.dom.ProcessingInstruction]
[Loaded org.apache.crimson.tree.PINode]
[Loaded org.w3c.dom.EntityReference]
[Loaded org.apache.crimson.tree.XmlDocument$EntityRefNode]
[Loaded org.w3c.dom.DocumentFragment]
[Loaded org.apache.crimson.tree.XmlDocument$DocFragNode]
[Loaded org.w3c.dom.Comment]
[Loaded org.apache.crimson.tree.CommentNode]
[Loaded org.w3c.dom.CDATASection]
[Loaded org.apache.crimson.tree.CDataNode]
[Loaded org.w3c.dom.Attr]
[Loaded org.apache.crimson.tree.AttributeNode]
[Loaded org.apache.crimson.tree.XmlDocument$Catalog]
[Loaded org.apache.crimson.tree.DataNode$NodeListImpl]
[Loaded org.apache.crimson.util.XmlChars]
[Loaded org.w3c.dom.DOMImplementation]
[Loaded org.apache.crimson.tree.DOMImplementationImpl]
[Loaded org.apache.crimson.tree.Doctype]
[Loaded org.w3c.dom.NamedNodeMap]
[Loaded org.w3c.dom.Notation]
[Loaded org.apache.crimson.tree.Doctype$NotationNode]
[Loaded org.w3c.dom.Entity]
[Loaded org.apache.crimson.tree.Doctype$EntityNode]
[Loaded org.apache.crimson.tree.Doctype$Nodemap]
[Loaded org.apache.crimson.tree.AttributeSet]
[Loaded java.lang.IncompatibleClassChangeError from C:\Program
Files\JavaSoft\JR
E\1.3\lib\rt.jar]
[Loaded java.lang.NoSuchMethodError from C:\Program
Files\JavaSoft\JRE\1.3\lib\r
t.jar]
java.lang.NoSuchMethodError
at
org.apache.crimson.tree.AttributeSet.init(AttributeSet.java:139)
at
org.apache.crimson.tree.XmlDocumentBuilder.startElement(XmlDocumentBu
ilder.java:463)
at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1449)
at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:499)
at org.apache.crimson.parser.Parser2.parse(Parser2.java:304)
at
org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)

at
org.apache.crimson.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl
.java:179)
at com.evermind.xml.e.getJavaxDocument(JAX)
at com.evermind.xml.XMLUtils.getDocument(JAX)
at com.evermind.xml.XMLConfig.ay(JAX)
at com.evermind.xml.XMLConfig.ay(JAX)
at com.evermind.server.hg.run(JAX)
at java.lang.Thread.run(Unknown Source)
at com.evermind.util.f.run(JAX)
[Loaded java.lang.Shutdown$Lock from C:\Program
Files\JavaSoft\JRE\1.3\lib\rt.ja
r]

Thanks again,
Rich
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Tim Endres
Sent: Friday, February 23, 2001 8:33 PM
To: Orion-Interest
Subject: Re: JAXP


Hi Rich,

Could you narrow it down? Specifically which JAR breaks Orion. We have
replaced
the xalan.jar and xerces.jar files with version 1.2.2 and Orion is happy. Is
it
just the jaxp.jar file that is the issue?

Also, I believe that somewhere in the mailing list archives, you will find
posts
related to JAXP, but I do not know if they will address your specific
question.

tim.

 I have been working on this problem all day. I have posted once before and
 no one responded. I will try again.
 I'm no Java expert and this is just my ignorance, but can anyone tell me
if
 I'm correct in my assumptions on this.
 I am trying to develop server side code that runs under Orion that uses
the
 JAXP code that Sun has recently released. There are different versions of
 parser.jar, xalan.jar and jaxp.jar distributed with Orion. Older ones. I
 have tried replacing the older ones with the newer ones because my code
 requires the newer ones and I guess that my code will be running in the
same
 image as Orion. Orion fails to start due to an exception while trying to
 parse its configuration files. Putting the old .jar files back, it works
 again. So, now it occurs to me that I'm basically stuck running with
 whatever version of support code the tools I'm using are dependent on.
 If I'm right, that means I can't use the latest version of JAXP until
Orion
 does? Is that right?
 Anyone?
 Thanks,
 Rich