[kinjalsonpal]

Hi,

I have multiple struts module. I prefer developing each of the module as a separate web project and integrate them at a later stage. This allows me the flexibility to delegate developing a module to some other programmer as well.

Now coming to my problem. Say, I have 3 apps: Logon, Register, MainApp. Each of them is a full fledged web project and the MainApp also acts as the default module. While deploying and using the MainApp, how do I instruct ME to pick the struts config and related files from the respective projects?

One option that I’ve thought of is using VSS. But I would not like to rely on VSS for this purpose unless there’s no other solution available.

Other option is using an Ant script for deploying. But I’m not so conversant with Ant Scripting and I’m also not sure whether Ant script based deployment would comply with ME’s deployer and whether HotSync and debugging would work.

Please suggest me a path.

Thanks and regards,
Kinjal Sonpal

[Riyad Kalla]

Kinjal,
The ME deployment model is based around 1 Web App == 1 Deployed App, since you are working in a Many Web App == 1 Deployed App situation, the deployment tool may not work correctly in this case. Have you tried deploying all three projects in the exploded format to the same Web Context Root and see what happens? Do they all get overlapped?

Any time users need a custom deployment model, that almost always implies a custom Ant script. Most projects as they get more complex fall out of the scope of the MyEclipse deployment tool and into the scope of custom Ant scripts.

[kinjalsonpal]

Have you tried deploying all three projects in the exploded format to the same Web Context Root and see what happens? Do they all get overlapped?

Hmm.. I have not tried this, but I can try this on a POC basis and see what happens. I’ll post back my experience on this.

Any time users need a custom deployment model, that almost always implies a custom Ant script. Most projects as they get more complex fall out of the scope of the MyEclipse deployment tool and into the scope of custom Ant scripts.

I understand this. But if you look at the second part of my question, I’m also worried about hotsync and remote debugging being affected with ant based depolyment. As I said, I’m not thoroughly conversant with ant. So I just wanted to make sure that before I spend time in developing an ant script, it would not affect other issues. Please share your views on this.

Thanks and regards,
Kinjal Sonpal

[Riyad Kalla]

Sorry for not addressing your question initially:
Not using our deployment tool will break hotsync abilities but debugging will still work fine. Hotsync is performed via the Eclipse event notification framework + A valid deployment, in this situation you would be circumventing the deployment by using an Ant script, so ME is not going to be able to hotsync at all.

If my previous suggestion of setting the same WebContext for all of the projects works, then Hotsync will work. Ultimately it is up to you to decide what is important to your team. Developing 3 modules as 3 separate projects which theoretically nice may be more trouble than it is worth if your team really wants hotsync. It also makes testing/deployment/packaging more difficult… again all factors you would have to weigh.

[kinjalsonpal]

Riyad,

Thanks for your inputs. I’ll have discussions with my team and will decide accordingly.

Regards,
Kinjal Sonpal

[Author]

Posts