Peter,
The Admin Console is fine except for the need for this to be automated from
deployment scripts and reproducible w/o manual intervention.
Our solution is going to be implementing an automated mapper for building out
our individual portlet-instances.xml permissions across the dozen or so p
Peter,
Is there any way to manage this outside of the portlet application's
portlet-instances.xml file? I.e. in our custom *-object.xml file? The
reasoning for us to need this is that our user roles may be dynamic and
redeploying our entire system's EAR just to update a single xml file in a
Antoine,
Nice...
I'm already doing some tweaks to jboss-service.xml, so this will just be
another tweak in our deployment scripts.
Thanks for getting back to me on it... would definitely be a great feature for
*-object.xml.
Along a similar path, I'm finding that I can't apply policy permissi
Oh yeah... I'm on JBoss Portal 2.6.5.GA...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169681#4169681
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169681
___
jboss-user m
"[EMAIL PROTECTED]" wrote : It is at context level, AFAIK you cannot modify it
with the XML descriptors.
|
| I don't think there is a Jira for this yet, so you can open one.
|
| (JSR 168, is defining the portlet container, so it has no notion of portals
neither page, it's vendor specifi
