>> The war project contains all web resources, jsps, etc. >> The core project contains all of our struts actions, >> service layer and data access layer.
> IMO that's broken--the S2 actions should be part of the web > project because... that's what S2 is--the web layer. That > solves your problem and (to me, anyway) seems a more logical approach. Ordinarily I would agree with you, but we have a constraint that I forgot to mention: our actions have to be usable in more than one web project. The system we are building is deployed to more than one customer. We customise the web project by overlaying customer-specific files in separate projects. I was thinking that another approach to this might be to keep all actions in the core project, along with the struts.xml file, then package these into a jar file. This page: http://struts.apache.org/2.0.11.2/docs/can-we-break-up-a-large-strutsxml -file-into-smaller-pieces.html says that this is possible, but doesn't give any details. Does anyone have any more details on getting this to work? Cheers Peter _______________________________________________________________________ The information contained in this e-mail is confidential and may be privileged. It is intended for the addressee only. If you are not the intended recipient, please delete this e-mail immediately. The contents of this e-mail must not be disclosed or copied without the sender's consent. The statements and opinions expressed in this message are those of the author and do not necessarily reflect those of the company. The company does not take any responsibility for the views of the author. Registered Office: IT-Freedom Limited, 9 Minster Court, Tuscam Way, Camberley, Surrey GU15 3YY Registered in England, Number: 04500346 _______________________________________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
