aspose file tools*
The moose likes Portals and Portlets and the fly likes [weblogic portal] Don't redeploy the whole portal application each time we change a portlet Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Java » Portals and Portlets
Bookmark "[weblogic portal] Don Watch "[weblogic portal] Don New topic
Author

[weblogic portal] Don't redeploy the whole portal application each time we change a portlet

Jeera Kamar
Greenhorn

Joined: Mar 10, 2011
Posts: 2
Hi folks,
I have around 50 struts portlets in my weblogic portal, following the struts portlet architecture in the documentation, so we have now one ear which ends up that whenever we change any portlet we will have to redeploy the whole portal !!!
I have read about federated portal, but it seems that its great advantage is when your portal wants to consume remote portlets deployed in remote producers, but this is not my case, since all my portlets are local ones, so I think there might be a simpler solution (*like in websphere where we have separate war for each portlet*)
any suggestions ? would be great if you can provide any resources or links document steps needed to accomplish this
Thanks a lot
Nadine Hossam
Greenhorn

Joined: Jun 19, 2005
Posts: 13
Jeera,

I'm having the same problem
Did you find a solution or a work around for that?
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: [weblogic portal] Don't redeploy the whole portal application each time we change a portlet