After this change, do you also see the other error that you had mentioned in your first post? Also, are you placing your log4j.properties or log4j.xml in your application(war file)? If yes remove this file and try adding the contents to the log4j.xml file present in %JBOSS_HOME%/server/default/conf folder(However, i dont think placing the xml or properties file in your application should have caused this error). Try it once. Also, please post the contents of the log4j.xml or log4j.properties that you are using.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979273#3979273
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979273
just a comment regarding error handling, i am using the same way for handling of errors:
for each node where some kind of error can happen, i make a transition to an "AdminNode" and the admin node has transitions to each of all other node so that via a web interface an "admin" can view all process variables etc, and decide on which transition the workflow should go (or terminate the process completely)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979272#3979272
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979272
I had some problems with the MyFacesGenericPortlet placing the non-serializable facesContext in the session but have come up with a possible solution. Maybe somebody has another and better solution.
In the processAction method of the MyFacesGenericPortlet the FacesContext is placed as an attribute in the session. Then later in the facesRender method this attribute is read again. Since I only knew of using Parameters to transfer request information from an ActionRequest to the RenderRequest my simple solution was to keep the facesContext in the session but doing this by wrapping the facesContext in a wrapper bean on which the facesContext is a transient field. This makes my portlet run in the Portal cluster.
Is there a better solution?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979270#3979270
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979270
Hello,
After installing 2.4 release ( I was working with the Beta one), I have problem with the role management of my portal.
I created a specific Nav bar based on the original one, (very similar) and my allowed method is :
private boolean allowed(JBossPortalNode node, int type) throws Exception
{
PortalObjectPermission perm = new PortalObjectPermission(node.getRef(), PortalObjectPermission.VIEW_MASK);
return portalAuthorizationManagerFactory.getManager().checkPermission(perm);
}
But this returns always false.
The code was working fine with the 2.4 beta release of the portal.
Any idea?
Thanks,
Yv
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979266#3979266
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979266