GF 3.1.2.2, JSF 2.1.29, RF4.5.1.Final, rich:tree, on tree node select produces the attached bug in richfaces.js. As you can see, no node 'form' in context. Should say, RF4.5.0 gives no errors here.
Any ideas?
Well, that's weird. Are you using a form with enctype="multipart/form-data"?
Yes, you are right: <h:form id ="dossierTreeForm" prependId="true" enctype="multipart/form-data">
Do you need to? None of our components require multipart/form-data.
I cannot reproduce this, are there some other actions attached to the tree? What version of JSF and what browser are you using?
Yes, I need multipart/form-data to submit binary data like attachments.
I use GF 3.1.2.2 with JSF 2.1.29.
<rich:tree id="dossierTree" value="#{dossierBean.rootNode}" var="node" nodeType="#{node.type}"
toggleType="client" selectionType="ajax"
selectionChangeListener="#{dossierBean.treeSelectionChanged}"
render="centerDetails">
I notice that listener works, but error appears in rendering of "centerDetails", as far I've understood.
Browsers: IE11, Chrome 39.0.2171.95 m
Most interesting thing: with RF4.5.0 there are no errors and everything works fine, and with RF4.5.1 I have the problem, so, I'm curious - what was changed?
Nifont Naumovich wrote:
…
Most interesting thing: with RF4.5.0 there are no errors and everything works fine, and with RF4.5.1 I have the problem, so, I'm curious - what was changed?
I've added the method that now throws the error. Ajax submissions do not work in multipart forms (RF-13828), at least not in Mojarra 2.2.6+ due to the way it's implemented. If it worked in 2.1.29 I will have to find a way around it.
EDIT: Yeah, the form was added to context in 2.2.0.
Thanks a lot, at least now it's clear what happened. Also, now I've a motivation to change architecture of application to reduce usage of multipart forms.
It would be nice, if you make this issue yourself to avoid misuse of terminology.
So, I'd prefer to delegate this work to expert.
If you need an additional info, please, ask.