-
1. Re: setting a security for individual portlet instances
antoine_h Apr 23, 2007 8:28 AM (in response to mohan_chaudhari)use rather the descriptor file to set it (as you did).
it may be also helpfull to reset the portal instances tables in the database.
so you make sure you are using the exact new definition (sometime it may mess with the definition from the manager and the one from the file).
look at posts about reseting the portal database, to clear the instance definition (becarefull, you will loose all the changes that are not in the descriptor file).
if this is the pb.
if not : I don't see why.
these things you want to do works perfectly.
may be a small detail that goes wrong in what you have done (you know, bugs we don't see until they appear "so simple"). -
2. Re: setting a security for individual portlet instances
sandeepjha18 May 24, 2007 2:39 AM (in response to mohan_chaudhari)I am also using jboss-portal 2.6 beta1 and facing the same issue.
Has anyone got a solution?
Is this a bug?
Mohan were u able to figure out any solution for this? -
3. Re: setting a security for individual portlet instances
mohan_chaudhari May 25, 2007 1:08 AM (in response to mohan_chaudhari)
Yes, the update button is missing in beta-1 i use cr2 .
But cr2 is having some problem with IPC (inter portlet communication).
Mohan -
4. Re: setting a security for individual portlet instances
theute May 25, 2007 1:36 AM (in response to mohan_chaudhari)what problem with IPC ?
Did you try this page:
http://localhost:8080/portal/portal/default/Test/event+test/
It works fine in trunk, i didn't try it in CR2 -
5. Re: setting a security for individual portlet instances
mohan_chaudhari May 25, 2007 2:54 AM (in response to mohan_chaudhari)Thanks thomas,
I already posted about IPC on following link
http://jboss.org/index.html?module=bb&op=viewtopic&p=4048580#4048580
Mohan