Never mind, I think I figured out! You can specify struts-config.xml etc in the web.xml itself. And ANT war task allows to specify required web.xml. Guess I am good to go now...

- Manish

----- Original Message ----- From: "Manish" <[EMAIL PROTECTED]>
To: "Velocity Users List" <[EMAIL PROTECTED]>
Sent: Thursday, September 06, 2007 3:30 PM
Subject: Creating tools from existing application


We have this huge application and we have identified that we can isolate some of its functionality and build tools from it. Now - I need to come up with some prototype in a week's time or so. I have identified core classes, actions etc here - some of the things that I am trying to figure out here are -

(1) How can I have multiple struts-cofig.xml in WEB-INF (is it even possible, using different names?) and include appropriate struts-cofig.xml in the deployable war such that my application will be in app.war and tools would be in tools.war and they both would use different struts-config.xml file. I can see that "war" task of ant allows using differnt web.xml but not differnt struts-config.xml. How can it be done?

(2) We use Velocity with struts, so another thing I am trying to figure out is how to use different layout for these two different wars?

(3) What other approach I can use in this case? We do not want to duplicate source code, any enhancement to main application must be propagated to tools if tools include those features. Thus, we are keen on using the *same* source code, but need to create two different wars from it where tools.war would be subset of app.war. How do I achieve this?

Any pointers, help would be highly appreciated. I am already digging into relevant docs to figure out things here.

TIA,
- Manish


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to