I tried putting my shared.jar in the /lib, but to no avail. Do you need to put a copy of the ejb-jar file in the /lib also?
Also, Orion has never generated a default orion-web.xml for my app (it does generate orion-ejb-jar.xml). But there are no errors on deployment either. Is there some way to turn on verbose error logging? -----Original Message----- From: Lachezar Dobrev [mailto:[EMAIL PROTECTED]] Sent: Monday, April 01, 2002 11:44 PM To: Orion-Interest Subject: Re: Newbie Orion question - webapp problem Like always the ClassPath is a server-specific setting. On orion you might want to check orion-web.xml in the war file. For the template you might want to use the one created by orion when the app is first deployed. Then you should add <classpath path="./path/to/classes/" /> to the xml file. However due to many class-path issues emerging from the deployment-redeployment/dynamic-proxy-generation and more, I would offer you to put your library files in the lib directory of Orion. Thus you will have no class-loading issues (unless you decide to use dedicated.connection). Have a nice try. Lachezar > I'm trying to get Orion to run a web app that's part of an ear. > > I made the following changes: > IN SERVER.XML > <application name="Majordomo" path="C:\orion\autodeploy\Majordomo.ear" > auto-start="true" /> > > IN DEFAULT-WEB-SITE.XML > <web-app application="Majordomo" name="MajordomoWeb.war" > root="/MajordomoWeb" /> > > IN THE EAR'S APPLICATION.XML > <module> > <web> > <web-uri>MajordomoWeb.war</web-uri> > <context-root>/MajordomoWeb</context-root> > </web> > </module> > > But when I hit http://localhost/MajordomoWeb/index, I get a "500: Internal > Server Error" and I can't find any output as to what the error is in any of > the log files. > > The EJB portion of the app, which I accessed with an Application Client, > works fine. > > One other clue: I'm referencing other JAR files, and using the Manifest > Class-Path attribute in the WAR file. I tried putting the external JAR into > the /lib directory of the War, but that didn't work either. Same error. > > Any help here? > > PS the EAR deploys into Sun's RI 1.3, and also into WebSphere 4.01. It > works fine there, so it must be an Orion configuration problem. > ------------------- > Kenneth DeLong > Senior Consultant > Direct: 510-517-5839 (Cell) > Fax: 972.789.1340 > > Valtech Technologies, Inc. > 5080 Spectrum Drive > Suite 1010 West > Addison, Texas 75001 > www.valtech.com <http://www.valtech.com> > > transforming technology skills > into sustainable business value > >