Turbine looks for action modules defined in your
TurbineResources.properties - in the "module.packages=" field. If you have a
package under a directory defined in "module.packages", you'll need to
specify the package name in your setAction parameter.
For example, if you have "module.packages=com.yourcompany.modules.action" in
TR.prop and your action component is
"com.yourcompany.modules.action.test.FooAction"
Your form will need to specify the package under what was defined in
module.packages:
<form name="form" action="<%= link.setAction("test.FooAction") %>">
<input name="name" value="">
<input type="submit" name="eventSubmit_doCreate" value="Create a Foo!">
</form>
----- Original Message -----
From: "Craig McDaniel" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, April 12, 2002 10:35 AM
Subject: Sub-packages for Actions?
> Should sub-packages for actions behave the same as for screens? IOW, I
> have set the action to be "admin,AddUser". However, Turbine is not
> finding my action class. Do actions not work this way, or is the
> problem somewhere else (or am I the problem)? My classes that are in
> the main actions package are working just fine.
>
> Later,
> --
> \ Craig Patrick McDaniel
> /_\ Software Engineer
> /_/_\ n + 1, Inc.
> /_/_/_\ [EMAIL PROTECTED]
> /_/_/_/_\ (502) 479-5557
>
> --
> 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]>
