My question is more of design practice for those that just use standard Actions. How do you design your packages? For example...
EmployeeUpdateAction: 1) package com.acme.ui.action.employee; or 2) package com.acme.ui.employee.action; or just put them all in one package: 3) package com.acme.ui.action;
I'm leaning towards option 1 myself. Other thoughts?
-- Rick
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]