Design approach for controller

What is the design approach if 3 war files sharing same se开发者_JAVA百科rvice and busniess logic layer.How i should use Controller here. if i am not using application server,I mean not packing into ear file.

What is the alternative for the controller?

Regards,

Raju komaturi

It's fine to keep your controller in their respective war file in the design phase, but your project putting these together needs to repack those wars into one common war file - which lets you map all paths in the same web.xml. If you're using Maven and its WAR plugin it can handle this task for you.

I'm not sure exactly what you define as Controller, but if you're referring to Springs, e.g., annotated Controllers, then they can most certainly be used this way. Same with regular servlets.