maybe take a look at
http://palab.blogspot.com/2007/01/tomahawk-bridge-091-released.html
This worked in our solution (which I didn't code, though, so I don't know the
exact details)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031376#4031376
Reply to the
I also experienced the same problem but figured that since the
NullPointerException is thrown when creating a uniqueId for a JSF component
with no id the solution would be to have all jsf components set the id
attribute explicitely. And this worked.
I think that the Namespace is null because of
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 attrib
Sorry I didn't get back to you in time. My solution is a bit simpler than yours
since my wrapper doesn't act as a FacesContext since I figured that no one else
would query the FacesContext from this particular attribute. But of course your
solution is much better.
I am no a bid further since I n
I was doing some other developing for some time but now found the time to go
further with the clustering. I got it working and have some comments:
One has to distinquish between traditional JSF-apps and JBoss SEAM apps
clustering is different depending on the platform used. JBoss SEAM keeps the
