Yeah, that's what I did/meant. I should have been more clear. :)
Unfortunately, that never worked for me!  

However, there is nothing to preclude user error on my part, albeit that is
not a difficult or complex task.  I haven't had the opportunity to go back
and try again since then and the second WEB-INF has actually been useful for
us.  So, who knows, technology is weird! :D (hehe)

Chris

-----Original Message-----
From: Stephen Schaub [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 30, 2001 10:49 AM
To: [EMAIL PROTECTED]
Subject: Re: Struts and WebSphere


Don't add WEB-INF to the classpath; instead, add its parent
(/web) to the classpath. If you add WEB-INF to the
classpath, when a servlet looks for /WEB-INF/whatever, it
will try to find it in WEB-INF/WEB-INF/whatever.

Does that make sense?

Stephen

----- Original Message -----
From: "Assenza, Chris" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, April 30, 2001 9:03 AM
Subject: RE: Struts and WebSphere


Oops, sorry guys - missed your discussion below, ignore what
I just said! :P

BTW, I've had no success adding WEB-INF to the classpath.  I
guess it should probably be listed as an alternate method,
but not a guaranteed one.
:)

Chris

-----Original Message-----
From: Assenza, Chris [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 30, 2001 9:02 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Struts and WebSphere


Did you make sure to create a WEB-INF directory under the
servlets
directory, per step 5? :)

-Chris Assenza



-----Original Message-----
From: Stephen Schaub [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 27, 2001 5:57 PM
To: [EMAIL PROTECTED]
Subject: Re: Struts and WebSphere


> I'd appreciate it if someone else running WAS would
> give this a spin to  double-check me.

I'm running WAS 3.5.3 Advanced 60-day trial. I followed your
instructions and was able to get index.jsp from the
struts-example app to display. However, when I click on the
Register link, I get the following error:

Error 500
An error has occured while processing request:
http://localhost/struts-example/editRegistration.do
Message: Failed to load target servlet [action]

Target Servlet: action
StackTrace:
------------------------------------------------------------
--------------------
Root Error-1: Missing configuration resource for path
/WEB-INF/struts-config.xml


javax.servlet.UnavailableException: Missing configuration
resource for path /WEB-INF/struts-config.xml
 at
javax.servlet.ServletException.<init>(ServletException.java:
107)
 ...

I also notice that when the application is starting up, the
following messages appear in the log:

Loading servlet: "database"
[Servlet LOG]: "database: init"
[Servlet LOG]: "database: Initializing database servlet"
[Servlet LOG]: "database: Loading database from
'/WEB-INF/database.xml'"
[Servlet LOG]: "database: No such resource available -
loading empty database"
Servlet available for service: "database"

.

Seems like it's having difficulty finding resources in the
/WEB-INF folder. Any suggestions?

Stephen Schaub

----- Original Message -----
From: "Dan Miser" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, April 27, 2001 8:27 PM
Subject: Struts and WebSphere


I noticed the WAS installation instructions at the URLs
below needed to be  merged. At this point, there is no
reason to recompile the Struts source to  make things work
with WAS, so the second URL is a bit dated. I also
found  the key to making Struts work without resorting to
creating extra WEB-INF directories or moving files around.

I took the text from the first URL and modified it. I split
the doc up into  2 parts: general Struts config and getting
the struts-example to run under  WAS.

I'd appreciate it if someone else running WAS would give
this a spin to  double-check me. If it checks out OK, I
would suggest that this doc replace the other two.
.

Reply via email to