The reason I ask is that I was getting a similar error (to the
StateFieldMarker markup) when using the 1.2 branch, in the Portal Proof
of Concept environment, with some of my extension involved. But I
tracked this down to be an issue with the bridge I was using. I did NOT
see this behavior in 1.1 or when running outside of a Portal environment
in 1.2. As for the RenderingContext, I didn't mess with any of this
code as part of either of these patches.
So it doesn't seem like the issues are related to me.
Scott
Scott O'Bryan wrote:
Jeanne,
You're not using this in a Portal POC correct?
Scott
Jeanne Waldman wrote:
Hi,
I updated my trunk and I'm having problems, and I'm wondering if it
is because of one of these patches.
To reproduce:
- run a demo, like index.jspx
--- the page comes up fine, but this renders on the page:
"com.sun.faces.saveStateFieldMarker"
---- I see these warnings:
Feb 14, 2007 10:31:25 AM
org.apache.myfaces.trinidad.context.RenderingContext attach
WARNING: Trying to attach RenderingContext to a thread that already
had one.
Feb 14, 2007 10:31:25 AM
org.apache.myfaces.trinidadinternal.context.RequestContextImpl
_createChangeManager
INFO: Apache Trinidad is using HTTPSession for change persistence
Feb 14, 2007 10:31:26 AM
org.apache.myfaces.trinidadinternal.renderkit.core.CoreRenderKit
encodeFinally
WARNING: No AdfRenderingContext available
- I click on a link on the page, and it does not navigate
Does anyone know what the problem is? I doubled checked to make sure
I had <output-mode>portlet commented out in trinidad-config.xml.
Thanks,
- Jeanne
Scott O'Bryan wrote:
Can someone please take a look at the patches for the following JIRA
issues and give me your feedback so that we can get these merged
into the JSF 1.2 branch and trunk?
ADFFACES-374
ADFFACES-379
Thanks.
Scott O'Bryan
