struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Newton <>
Subject Re: How to organize "regular" Actions and "ajax/json" Actions
Date Fri, 08 Jun 2012 14:05:47 GMT
I wouldn't have a package just for "JSON actions", because that separates
them from what they actually are.

I'm not sure what is meant by "spanning multiple pages"; in general
wouldn't they still be associated with specific data types, or


On Fri, Jun 8, 2012 at 10:03 AM, Burton Rhodes <>wrote:

> I have a web application that originally mapped only one action per
> page (for the most part).  Little by little it's grown to incoporate
> ajax/json actions (using Struts json plugin) that populate different
> parts of pages or update the database.  My question is how best to
> organize these new actions in packages with the rest of the web
> application. First I started with a simple json package, but realized
> this probably isn't manageable as I add more "json" actions.  Then I
> thought to move these "json" actions in with other packages but
> hesistate since they tend to span multiple pages. Or perhaps this is
> the best way and use a naming convension for these, e.g.
> ??
> Just curious if any of you have found a good way to do this and stay
> logical and organized...
> My current layout is something like:
> com.afs.web.action
>  -
>  - com.afs.web.action.accounts
>  - com.afs.web.action.xactions
>  -
>  - com.afs.web.action.json             <-- this is a catch-all for json
> actions
>  - ....
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message