I don't know if this is your problem, but I would consider putting your class in package and specifying the type with the fully-qualified class name.
Put something like this at the top of dbopsAction.java: package com.mycompany.myapp; and make sure the class file ends up as WEB-INF/classes/com/mycompany/myapp/dbopsAction.class Then specify the fully-qualified class name in struts-config.xml like this: <action path="/dbopsAction" type="com.mycompany.myapp.dbopsAction" scope="request"> </action> I am not sure that will help, but I suspect it might and it is a good idea anyway. -Max ----- Original Message ----- From: "slickdev" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Tuesday, August 27, 2002 9:52 PM Subject: No Action Instance > I developed a simple Struts app named "ecapp" on win2k, then dropped it's war file into Tomcat 3.3.1 running on a Sun box. > > When requesting this action: > http://thesunbox.com:8080/ecapp/dbopsAction.do;jsessionid=9fimfkovb1?action= listusers > I get this reply: > "Status code: 500 request:R( /ecapp + /dbopsAction.do + null) msg:No action instance for path /dbopsAction could be created" > > I figure this is a path problem. However, the dbopsAction class is in ecapp/WEB-INF/classes, as it should be. > > The struts-config has this for the action mapping, which works fine in w2K: > <action > path="/dbopsAction" > type="dbopsAction" > scope="request"> > </action> > > On the Sun box, I also set up an apps-ecapp.xml file to explicitly inform tomcat about the context for the ecapp app: > <webapps> > <Context path="/ecapp" > codeBase="webapps/ecapp" > --- // realm stuff here > --- // log stuff here (works fine) > </Context> > </webapps> > > In sum: the ecapp jsp's are callable, but just the app can't find the dbopsAction class. > > Suggestions? > > Thanks! > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
