aspose file tools
The moose likes JSF and the fly likes readonly inputtext could get bean property, while non-readonly(readonly=false) one could not. why? Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login
JavaRanch » Java Forums » Java » JSF
Reply Bookmark "readonly inputtext could get bean property, while non-readonly(readonly=false) one could not. why?" Watch "readonly inputtext could get bean property, while non-readonly(readonly=false) one could not. why?" New topic
Author

readonly inputtext could get bean property, while non-readonly(readonly=false) one could not. why?

ym feng
Ranch Hand

Joined: Mar 19, 2009
Posts: 31
one managed bean, 2 properties myBean(prop1, prop2)
2 <af:inputText>s (i use oracle adf faces)
<af:inputText value#{myBean.prop1} readonly="true">
<af:inputText value#{myBean.prop2}>

two inputText are placed on popup window(<af:popup>)

everything is ok when popup window startup at first time,
while the second inputtext could not get the value of myBean.prop2, at the second time startup

nothing changed during this whole process, but just got this strang result.

could anyone help me ?
any suggestion is welcome.

thanks!

Bauke Scholtz
Ranch Hand

Joined: Oct 08, 2006
Posts: 2458
The posted code doesn't even compile. I am not sure if it is actually a fault or that you typed/pasted quick'n'dirty code here (you should NEVER do that, post the ACTUAL code).


Code depot of a Java EE / JSF developer | JSF / Eclipse / Tomcat kickoff tutorial | DAO kickoff tutorial | I ♥ Unicode
ym feng
Ranch Hand

Joined: Mar 19, 2009
Posts: 31
Bauke Scholtz wrote:The posted code doesn't even compile. I am not sure if it is actually a fault or that you typed/pasted quick'n'dirty code here (you should NEVER do that, post the ACTUAL code).



here is the code


myBean.fetchListener()



please help to look into it, thanks!
>
ym feng
Ranch Hand

Joined: Mar 19, 2009
Posts: 31
if myBean is set to be session scoped, everything will be ok.
Bauke Scholtz
Ranch Hand

Joined: Oct 08, 2006
Posts: 2458

Start removing this line or replacing the HTML comments by JSP comments <%-- --%>.

The HTML comments are pure client side and doesn't stop this line being parsed by the JSP engine.
ym feng
Ranch Hand

Joined: Mar 19, 2009
Posts: 31
Bauke Scholtz wrote:
Start removing this line or replacing the HTML comments by JSP comments &lt;%-- --%&gt;.

The HTML comments are pure client side and doesn't stop this line being parsed by the JSP engine.


I do follow your suggestion, but problem remains,
it's not the point of my question, maybe. thank you all the same.
Bauke Scholtz
Ranch Hand

Joined: Oct 08, 2006
Posts: 2458
Uh, it was just to exclude problems step by step. I also explicitly said "Start", I just wanted to help you step by step.

Anyway, my motivation to help has gone. Good luck further.
ym feng
Ranch Hand

Joined: Mar 19, 2009
Posts: 31
Bauke Scholtz wrote:Uh, it was just to exclude problems step by step. I also explicitly said &amp;quot;Start&amp;quot;, I just wanted to help you step by step.

Anyway, my motivation to help has gone. Good luck further.


yes, i preciate for your help.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: readonly inputtext could get bean property, while non-readonly(readonly=false) one could not. why?
 
Similar Threads
about parameter passing
Using ADF and clientside form validation without alert box
Closing windows in JavaScript
Problem using convertNumber for decimal numbers
h:inputText readonly="true" not updating managed bean values