|
Home > Archive > WebSphere Portal Server > March 2004 > Portlet Development
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Portlet Development
|
|
| nhargro 2004-03-29, 6:37 pm |
| A NASA customer sent me this information for Portlet Devleopment advise. A=
ny help (documentation and/or points to examples) you can provide would be =
most appreciated. =20
I had a question specific to portlet development I am hoping you could help=
me with.=A0 I am currently working on a portlet application that will requ=
ire portlet GUI elements (e.g.: edit boxes, labels, drop-downs) to be speci=
fied at runtime (not the data in them, but actually the elements and types =
of elements).=A0 Specifically, when a user logs into the portal and the vie=
w is being created by the portal, I will be running a query that will deter=
mine how many edit boxes, labels, drop-down boxes I will need at runtime an=
d build the data collection portlet from that information.=A0 The beauty of=
this model makes the presentation completely data driven.=A0 If I want to =
add a new piece of data to an object that needs to be collected or displaye=
d, I simply add it in the data tier and the next time a user renders a view=
, a new edit box will appear (for example).=A0 Now, can this be done in the=
portal?=A0 With a servlet, this is not really a problem since I can essent=
ially build the html elements I need in the servlet request handler and wri=
te those out to the view.=A0 In the portal on the other hand, I=92m not qui=
te sure what my options are since I have only used tags so far.=A0 Any thou=
ghts?=A0 Maybe we can arrange a call when you get some free time so we can =
discuss my options.=A0 Thanks and look forward to hearing from you.=A0=20
Thanks! Cole
| |
|
| Have you ever seen Portal InfoCenter?
The section titled "Portlet Development Basics" has Example Hello World
Portlet, in which Portlet writes part of html to PortletResponse.
I think this provides enough hints for you.
One thing, you might want to notice, is that in case of Portlet, doView
will be called more often than you expect for servlet, because the state
change of other portlets (such as maximize another portlet then restore
it) or portal (visit different page and come back to previous page, for
example) will require your portlet to produce your part of html.
So you might want to cache your html.
One idea is to split your logic to one part to handle user input and
(action part) and another part to return output (render part).
url
| |
|
| I didn't notice at first, but you also work for IBM, don't you?
Why don't you look for help in IBM, rather than asking
question on the internet?
url
|
|
|
|
|