OK!!!! Looks like I found my problem... I was deploying the WAR file as a part of an ear file. In this case, my ActionServlet was unable to find the struts.jar classes from the WAR's WEB-INF/lib directory. When I added the struts.jar to the ear file and added a "Class-Path" attribute to my WAR file's manifest.mf file, my web app started working. Thanks for your help. If my experience above sounds unusual to you or you can see some obvious flaw in the way i am deploying my app, please let me know asap.
Eagle On Mon, 7 Feb 2005 09:55:34 -0500, Soaring Eagle <[EMAIL PROTECTED]> wrote: > Hmm... I doubt if the xml is not well-formed or invalid. However, I > got the point. Looks like I will have to give better fodder (than what > I did) to this list. Let me try to get this or other apps working or > get better error descriptions. > > And no, I do not believe that Struts will lie - i.e. if there are > classloader problems, i do believe that I should get class not found > or something to that effect. > > thanks. > > > On Sat, 05 Feb 2005 19:46:45 -0800, Curtis Taylor <[EMAIL PROTECTED]> wrote: > > I agree with Christian. I've found an XML validation website/tool which > > is invaluable when you're brain-dead & still required to write code: > > > > http://www.stg.brown.edu/service/xmlvalid/ > > > > HTH, > > > > Curtis > > > > Christian Bollmeyer wrote: > > > On Friday 04 February 2005 22:53, Soaring Eagle wrote: > > > > > > Check the syntax of your struts-config.xml. The one you > > > posted is heavily mixed up. In fact it's not even well-formed > > > XML, with odd nestings, closing tags without a start tag, > > > illegal attributes and the like. I'd recommend to drop the > > > current version and rebuild it from scratch, using a > > > working version (like the one from the examples) as > > > a template. Keep special heed of proper nesting, the > > > cardinality of elements (0..1 <form-beans> or > > > <action-mappings> sections, for example), correct > > > attributes and the fact that order is important when it > > > comes to XML (top-down). > > > > > > HTH, > > > -- Chris. > > > > > > If it were a classloader problem, the server would > > > tell one by issuing ClassNotFoundException messages > > > and the like. It has no reason to lie, so missing jar > > > files are obviously not the cause here. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
