Jacek Wiślicki wrote:
Wiadomosc od David Sean Taylor z 2006-01-23 09:50 brzmiala:
A portlet isn't really supposed to know about its 'unique id' as that
is an implementation detail of the portal.
However, when I managed to get the current fragment ID, I was able to
create a universal portlet class whose behaviour, displayed contents and
some security features are determined by some data stored in the
database (fragment preferences were not enough for storing large amounts
of data).
What if you stored a unique key in the preference, say "content-id"
This unique is portlet instance specific.
From there, you can map to your large amounts of data
If you want to write portlets specific to Jetspeed-2, have a look at
the j2-admin app which accesses portal services in the
jetspeed-portlet.xml
By the way, is the bug concerning service access fixed?
You mean this one:
https://issues.apache.org/jira/browse/JS2-464
I'll try to get a look at it tonight
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
