My friend, there are no dumb questions. There are only dumb people, and the dumb people are the ones that never ask questions.
I actually meant to post a reply to this, but got sidetracked. It's a good question.
As an author of a book on JSR168 programming, I'd like to tell you that all of your time is spent developing portlets, and that you really need to buy multiple copies of my books, and do my
free online portlet development tutorials relentlessly, but that wouldn't quite be the whole truth.
I think initially, as a traditional website gets 'portalized', a fair bit of time is consumed taking functionality in PL\SQL programs, or old Servlet/JSP programs, and wrapping them in a portlet paradigm. Usually a couple of developers get tasked with that, and in the prep stage, those developers will spend about 80% of their time developing using the Portlet API. But even then, many of the complex portlets leverage
JSF or
Struts, so even when apps are ported to the portal, quite a bit of time is often spent doing JSF programming, not direct portlet API programming.
But initially, I'd say your team would have a few programmers spending quite a bit of time doing portlet programming, or at least, messing around with the portlet API.
After that though, many portal sites tend to deliver updates through content management mechanisms. This gets you away from direct API work, and throws you a bit more into contennt management arenas. So, maybe 50% of your time is working with various Stellant or LWCCM APIs or something and maybe 30% fighting with the portlet API.
I'd say after a site gets up and running, most of your work then hinges around content management and even personalization techniques. Your portlet API skills come in handy about 20% of the time, and it's usually advanced skills you need at this point, but you're certainly not spending all of your time doing portlets.
On the other hand, I spent a fair bit of time as a 'Portlet Programmer for Hire' when the portal was hot, and probably spent 80% of my time doing pretty direct API stuff, while the other 20% was in meetings or mentoring my fellow programmers. I just went from lucrative contract to lucrative contract, so the API pretty much consumed my life. I assume the same thing will happen when JSR-286 comes out and those skills are needed again. By the way, if you know of any 'lucrative portal' contracts in Canada, let me know.
Does that make a bit of sense for you?
I totally understand why you asked the question. I think it's a question
alot of developers ask. I'd love to know why you're asking the question, or what your experience with the API is, so please, continue the
thread with some of your own personal experience.