Ok, after looking at testStrutsAction.jsp, I realized that testAction.do is not doing exactly what I thought it was, and invoking it standalone was never going to work anyway.
I'm now beginning to think that what I really need is a Controller, so I'm going to focus my efforts there for now. The docs mention that a Controller could be implemented as a Struts action. Does that require the Action to implement the Controller interface or is there some Tiles magic that occurs merely by setting the controllerClass attribute in the definition? Sorry to be a pest, but I'm trying to get up to speed quickly and the docs are a bit overwhelming (I'm not complaining, mind you :-). -- Jim Jim Crossley <[EMAIL PROTECTED]> writes: > Cedric Dumoulin <[EMAIL PROTECTED]> writes: > > > tiles-doc.jar is shipped with Struts1.1 previous than 15 jan, and is > > ready to run. So you can try the mentioned url test directly on it, > > and it should run. If not, let me know. > > This runs: > http://localhost:8080/tiles-doc/test/testStrutsAction.jsp > > This does not: > http://localhost:8080/tiles-doc/test/testAction.do > > It doesn't because the call to ComponentContext.getContext(request) in > org.apache.struts.example.tiles.test.TestActionTileAction returns > null. > > So I'm still not sure how to overload definition attributes (specified > in an XML file) in a Struts action. :-( > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
