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. ContactJsonAction.java ??
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.contact - com.afs.web.action.accounts - com.afs.web.action.xactions - com.afs.web.action.help - com.afs.web.action.json <-- this is a catch-all for json actions - .... --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
