Patrick Huber <[EMAIL PROTECTED]> wrote:
Hi Lalit
I think it makes a lot of sense to deploy several portlets in the same
webapp when they share a lot of functionality/configuration or
especially when they logically belong together. Like when they
communicate with each other trough the session and one portlet
influences the other.
Another aspect of this whole thing is (re)deployment. If all portlets
are in one webapp, you can only re-deploy all portlets even if you've
changed only one of the portlets. If you can't afford a lot of
downtime and the portlets take some time for redeploment, I'd put each
portlet in its own webapp.
I put my portlets all in the same webapp, but each portlet has its own
disjoint spring framework config. I could easily put each portlet in
its own webapp. All I'd need to do is to edit my build.xml to work for
several webapps, make sure shared code is contained in all webapps and
work with different portlet.xml files...
I hope I can help you with these informations. In the end it doesn't
matter that much. Redeploment and downtimes may be a very important
aspect, depending on your environment/constraints.
Patrick
2006/4/18, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
> Hi All,
>
>
>
>
> What are the norms, if any, for packaging portlet(s) - not tied to a
> particular application server.
>
> What are the pros and cons of packaging all portlets in a single web
> application versus packaging portlets individually in a multiple web
> application? What do you do when only very little of the functionality is
> shared between two or more portlets but otherwise these portlets are
> unrelated?
>
> Look forward to all responses.
>
> Thanks.
> Lalit
>
>
> ________________________________
> Love cheap thrills? Enjoy PC-to-Phone calls to 30+ countries for just 2¢/min
> with Yahoo! Messenger with Voice.
>
>
--
"I love deadlines. I like the whooshing sound they make as they fly
by." -- Douglas Adams
How low will we go? Check out Yahoo! MessengerÂ’s low PC-to-Phone call rates.
