Can anybody with portal/portlet experience explain....when would you choose portal as choice of implementation to typical javaEE application. Here is my company a consultant apparently recommended a portal as solution to web-enable parts of an enterprise application to public domain(people outside network enterprise). This seems to be the standard norm for ebusiness suite from oracle. Honestly I don't see a point ..why would you do that. Why a simple JavaEE application wouldn't suffice. Especially we have only one unified enterprise application and just need to expose part of it for public domain. Am I missing some thing here??? All I could find is justification which is of advertising in nature.
Portal servers and portlets in particular allow you to build and deploy each part of the page as an independent entity. Parts of this are possible in JEE applications but some parts are harder to accomplish than others.
Since each part is a stand alone entity it can be switched in and out, updated, reconfigured and a bunch of other actions without impacting the functionality rest of the web site.
Depending on the Portal server it is also possible to allow individual users to customise the display on their personal pages, but in my opinion it is more useful in that it allows the business users themselves to modify the web layout without requiring code changes or even developer assistance.
Joined: Mar 11, 2009
but many (all?) of these require developers to or enable changes and are not portable and largely custom solutions written from scratch each time.
Portlets conform to a specification (JSR 186 or JSR 268) and compliant portlets can be deployed to any Portal container.
The other problem that portlets solve is that web applications can 'collide' or interfere with each other. In Mashups etc each part is written so that it cannot impact another part of the application, but each Portlet can be written without knowledge of where it will be deployed.