In my second-to-last project we had a JSR-168 portlet-based intranet app (plus IBM Process Server back-end) foisted on us by unknowing Enterprise Architects. This kind of sums up my experiences - sounds great on paper, but in reality we ended up building a standard web app by bolting together multiple portlets. Super hard (everything took three steps backward - build, test, deployment, simplicity, speed, etc.) and shocking tooling (this was a year ago and we used IBM's Rational software Architect).
It looked like it might have been getting better with JSR-286 but that could also have gone down the "far too complicated for its own good" route. I haven't had a chance to look at it. Regs, Andrew On Feb 26, 8:50 am, "Vince O'Sullivan" <[email protected]> wrote: > In the last podcast that I listened to, Dick asked who uses portlets > and suggested that they might be found on company intranets. > > That's exactly right. In "my" company we have an intranet that is > accessed daily by the majority of our 50,000 employees. We started > using portlets last years and they are spreading slowly across our > Intranet. > > Vince. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
