I believe the best thing to do is run "appfuse:full-source". This
allows you to customize everything. In a future release, I'm thinking
of moving the common-web module into each web module and creating
architetypes with all the web artifacts included. This will make it
difficult to upgrade, but will allow more flexibility for users.
Matt
On Wed, Jul 2, 2008 at 4:05 PM, Tuncay A. <
tuncayxx@...> wrote:
>
> Hi,
>
> I hope some can answer my question.
>
> I'm using the modular version of AppFuse 2.0.2 + Struts 2 + JPA.
>
> There is a tutorial about how to export "AppFuse Core Classes" at
>
http://www.appfuse.org/display/APF/AppFuse+Core+Classes, but thats only for
> model beans.
>
> I'm going to change some code in the SignupAction and other actions too.
> What should I do ?
>
> 1. Create a SignupAction.java inside my own package (my domain) and extend
> the AppFuse SignupAction
> or ?
>
> 2. Export Appfuse Web Classes like when you do for AppFuse Core Classes ?
>
> 3. Other ?
>
> Is there any guide for that or could some give a best way to do.
>
>
> - tuncay
>
> --
> View this message in context:
http://www.nabble.com/Best-Practices-for-AppFuse-Web-Core-Classes-tp18247888s2369p18247888.html> Sent from the AppFuse - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
users-unsubscribe@...
> For additional commands, e-mail:
users-help@...
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail:
users-unsubscribe@...
For additional commands, e-mail:
users-help@...
