This has to do with how the FCKEditor component itself works. Will review for 1.7.1 to see if we can make it support partialSubmit, etc. as per other input components.

Back in early 2007 I sent y'all a plain-old JSF (non D2D) component that I wrote for the FCKEditor, in hopes that ICE-1240 would be come a reality. While this component had no understanding of partialSubmit, its "value" did indeed get submitted when a SUBMIT button was clicked. So even if partialSubmit is not possible, then perhaps just making the "value" attribute get submitted on the form submit would be good. I'd be happy to send it to you again. Actually its available in the new PortletFaces project if you want to look at it there:
http://lportal.svn.sourceforge.net/viewvc/lportal/incubation/portletfaces/

Adnan, can you comment on how feasible this change is? I was under the impression that the underlying FCKEditor component was wired to only save with the save button, but is there a way we could make this work?

Yes its possible to save the value of the FCKEditor on the partialSubmit. In fact when the component was designed, it was causing the more then one instances of the inputRichTexts to be saved on a "save" action. Please see the following case.
http://jira.icefaces.org/browse/ICE-2719

To fix this the above case we had to put the check, that the inputRichText should only save the value when the save button clicked on it.

trunk: revision16738
branch 1.7.1: revision 16739

• The following new attribute added to the inputRichText component.
  *saveOnSubmit

Default to false. Setting this attribute to "true", will cause the inputRichText component to participate in the form submission.

The saveOnSubmit="true" attribute isn't working in 1.7.1

I confirm the saveOnSubmit option added to the 1.7.1 is not working for me too, or at least, not every times...

I use icefaces 1.7.1 + Seam.

If I try to submit my form using :

<ui:define name="contentData">
<s:validateAll>
<table class="splitPane_70_30">
<tr>
<td>
<ice:inputRichText id="axisDescription" height="400px"
value="#

" language="fr" skin="silver"
saveOnSubmit="true" toolbar="Athena Simple" customConfigPath="/js/athena/fckConfig.js" />
</td>
</tr>
</table>
</s:validateAll>
</ui:define>

<ice:commandLink id="validate" action="#

" type="submit"
onclick="Athena.commons.icefaces.saveRichInputText();">
<ice:outputText value="#

" />
<s:conversationId />
</ice:commandLink>

with the given java script function (extracted from the fckeditor javascript code):

/**

• Trigger a submit for all rich input text editors on the page.
  */
  Athena.commons.icefaces.saveRichInputText = function()
  {
  var all = Ice.Repository.getAll();

for (i=0; i < all.length; i++)
{
var instanceName = all[i].thirdPartyObject.InstanceName;
var editIns = FCKeditorAPI.GetInstance(instanceName);

if (editIns != null)

}

var form = Ice.util.findForm(element);
iceSubmit(form,element,new Object());

return false;
}

When doing this, I force twice the submission for the richInputText and my backing bean setter searchAxisCreate.newSearchAxis.description is called as well. Nevertheless, it works but it is not the way it should work... The saveOnSubmit should already does this job (and, I repeat, it does not every times).

At that point, I have a problem with my workaround. I have a form with required input texts and I want to add a Cancel button with a popup message to confirm or not this cancelation. With my workaround, I also have to submit the form with ice:commandLink because, if I don't do it and choose not to cancel and go back to my page (using s:link for example), I lose the text I typed in the richInputText... No problem, I use the commandLink : but it means I have to fill in all the required fields just to have the possibility to make the cancel button work!!! (if not all the required fields are filled in, the submission is not performed indeed...)

Today, I'm quite stuck because I have two possibilities :

• I keep going on with the buggy saveonSubmit that submit "when it wants to" and my cancel mechanism works fine
• I use my workaround, but, in case of presence of required fields, I have to fill in the fields just to allow the cancel button to work... which is crazy...

Thanks for your help.