Hi, I have replicated the problem with the following code. There are three files below an xhtml, a java and a js file.
As you can see I call the iceSubmitPartial function manually.

The postconstruct method is called if a selectInputDate is placed inside a tooltip and poup calendar button is pressed.
I've also found if you put a displaylistener on a panelTooltip the postconstruct method is called.

test.xhtml
[
<ice:form id="frmIndex1">
<ice:panelGrid>
<ice:panelGroup id="divIntelText" onmouseup="setSelectedText();" style="width: 630px; height: 350px; overflow: auto; border-style: solid; border-width: 1px; border-color: #D9D9D9;">
<f:verbatim>
#

</f:verbatim>
</ice:panelGroup>
<ice:inputText id="txtSelected"
value="#

"
onchange="iceSubmitPartial( form, this, event);"
style="display: none" />
</ice:panelGrid>
</ice:form>
]

TestBean.java
[
import javax.annotation.PostConstruct;
import javax.faces.bean.ManagedBean;
import javax.faces.bean.ViewScoped;

@ManagedBean
@ViewScoped
public class TestBean
{
private String selectedText;

private String bodyText = "Hello there";

@PostConstruct
public void init()

public String getBodyText()

public void setBodyText(String bodyText)
{
}

public void setSelectedText(String selectedText)

public String getSelectedText()

}

]

intel.js
[
var selectedText;

// Sets the selected text in the server code.
function setSelectedText()
{
var txt = '';

if(window.getSelection)

else if(document.getSelection)

else if(document.selection)

txt = new String(txt);

if(txt.length > 0)

}
]

I've been looking at this issue and have it narrowed down somewhat creating my own simplified test case in the process. Perhaps the reporter can confirm what I've discovered in his tests.

I can replicate the bean creation but it doesn't appear to use the new bean instances or put them in the the view attribute map. As I click on the button, I can see new view bean instances created and the PostConstruct method called but the Facelets Debug feature doesn't show them added to the view attribute map (just the original view bean is there) and the page also continues to use the bean that was created first.

The only item that seems to impact this (and why I couldn't replicate it earlier) is the use of the f:verbatim tag. I created two nearly identical pages that differed in only one aspect. One page uses f:verbatim like this:

with-verbatim.xhtml
--------------------------

<ice:form>

<h2>ICEfaces Compat Test App</h2>

<ice:panelGroup>
<f:verbatim> #

"/>
</ice:panelGroup>

<ice:panelGroup>
<ice:outputText value="#

"/>
</ice:panelGroup>

<ice:panelGrid columns="1">
<ice:commandButton id="actionButton"
value="Trigger action listener"
actionListener="#

"/>
</ice:panelGrid>

</ice:form>

The issue of the extra bean creation only occurs with the page that uses f:verbatim. I'm still investigating why this is the case but it would be helpful if the reporter could confirm this behaviour as well.

I converted the test case to a stock JSF 2 application (changed all the ice: tags to h: tags and removed the ICEfaces libraries). Mojarra on it's own appears to exhibit the same behaviour so it's not an ICEfaces issue.

Attaching a .zip file containing a pre-built .war file for Glassfish 3 running JSF 2 as well as the source code for the backing bean.

Resolving as Won't Fix as it appears to be a behaviour associated with JSF itself.

Hi, thanks for your work on this. I was wondering if you have raised this bug with Sun?

I have found a workaround by using <ice:outputText escape="false" />

Thanks again,

Simon

I've open a case in Sun's system and attached the test case there as well:

https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=1706