An alternate approach that worked for me:
Add the web folder to the struts-example application
classpath:
C:\WebSphere\AppServer\hosts\default_host\struts-example\web
When I did this, the struts-example app worked flawlessly.
That might be a little simpler config than maintaining two
separate WEB-INF folders, especially when updating a
deployment.
I like your idea of putting the DTDs in the systemwide
classpath.
Stephen
----- Original Message -----
From: "Dan Miser" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, April 28, 2001 1:36 AM
Subject: Re: Struts and WebSphere
My fault. I was using an older version of struts.jar on that
machine. I have the revised instructions at work, but the
short of it is that the original article was right about
adding the XML files to servlets\WEB-INF and
the TLD files to web\WEB-INF.
I would still make the argument that putting the DTDs in
c:\websphere\appserver\classes is a good thing, since it can
be done once system-wide *and* it solved my problems where
the SYSTEM DTDs were not being registered properly. But that
looks like the only change on there now.
--
Dan Miser
http://www.distribucon.com
----- Original Message -----
From: "Stephen Schaub" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, April 27, 2001 4:56 PM
Subject: Re: Struts and WebSphere
> > I'd appreciate it if someone else running WAS would
> > give this a spin to double-check me.
>
..
