I think that your problem is the ajaxSingle="true attribute. This attribute means that, even if all the input elements in the form are submitted, only the input the one that triggered the submit will be processed.
I think that your problem is the ajaxSingle="true" attribute. This attribute means that, even if all the input elements in the form are submitted, only the input the one that triggered the submit will be processed. If this is the problem, you can try any of the following (I assume that the a prefix is the common a4j prefix?): Add the id of the h:inputText, to the processed attribute to .
This will force the input of the specific row to be processed. For example (not tested): Remove the ajaxSingle and instead surround the in a a4j:region (analogous to ajaxSingle with processed, here all the inputs in the closest/enclosing region are processed): Remove the ajaxSingle. This will cause all the elements in your form to be processed.
Will take more time. Enter code here.
Still no luck. That detOrdComp is an iterator (Ctrl+click takes me to public abstract interface java.util. Iterator), does that something to do with this?
I even tried to put that inputText control inside a s:decorate (with seam-gen's edit. Xhtml template), and nope, no luck. I tried rich:inplace input, it doesn't work either.
Any other suggestion? Thanks in advance. – jpangamarca Nov 12 '10 at 20:17.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.