It's a standard JSF problem: 1. Try to communicate directly between the two beans. Resolve them over the faces context and then call getters / setters. [Answer: Content of a HtmlDialog in my javabean][1] 2. The other possible (but not recommended way) would be to access the setter in an el-expression within the view: `#{data.setMyString(javaBean.evaluateString())}`. This is possible since within ivy expression language 2.2 is supported (which brought method calls for el-expressions) [1]: http://answers.xpertivy.ch/answer_link/46http://answers.xpertivy.ch/questions/40/content-of-a-htmldialog-in-my-javabean/46

It's a standard JSF problem: 1. Try to communicate directly between the two beans. Resolve them over the faces context and then call getters / setters. [answer46][1][Answer: Content of a HtmlDialog in my javabean][1] 2. The other possible (but not recommended way) would be to access the setter in an el-expression within the view: `#{data.setMyString(javaBean.evaluateString())}`. This is possible since within ivy expression language 2.2 is supported (which brought method calls for el-expressions) [1]: http://answers.xpertivy.ch/answer_link/46

It's a standard JSF problem: 1. Try to communicate directly between the two beans. Resolve them over the faces context and then call getters / setters. [answer46][1] 2. The other possible (but not recommended way) would be to access the setter in an el-expression within the view: `#{data.setMyString(javaBean.evaluateString())}`. This is possible since within ivy expression language 2.2 is supported (which brought method calls for el-expressions)el-expressions) [1]: http://answers.xpertivy.ch/answer_link/46

It's a standard JSF problem: 1. Try to communicate directly between the two beans. Resolve them over the faces context and then call getters / setters. 2. The other possible (but not recommended way) would be to access the setter in an el-expression within the view: `#{data.setMyString(javaBean.evaluateString())}`. This is possible since within ivy expression language 2.2 is supported (which brought method calls for el-expressions)

It's a standard JSF problem: 1. Try to communicate directly between the two beans. Resolve them over the faces context and then call getters / setters. ( as described here: http://answers.xpertivy.ch/answer_link/46/ ) 2. The other possible (but not recommended way) would be to access the setter in an el-expression within the view: `#{data.setMyString(javaBean.evaluateString())}`. This is possible since within ivy expression language 2.2 is supported (which brought method calls for el-expressions)

It's a standard JSF problem: 1. Try to communicate directly between the two beans. Resolve them over the faces context and then call getters / setters. ( as described here: [http://answers.xpertivy.ch/answer_link/46/][1] http://answers.xpertivy.ch/answer_link/46/ ) 2. The other possible (but not recommended way) would be to access the setter in an el-expression within the view: `#{data.setMyString(javaBean.evaluateString())}`. This is possible since within ivy expression language 2.2 is supported (which brought method calls for el-expressions) [1]: http://answers.xpertivy.ch/answer_link/46/el-expressions)

It's a standard JSF problem: 1. Try to communicate directly between the two beans. Resolve them over the faces context and then call getters / setters. (as ( as described here: [http://answers.xpertivy.ch/answer_link/46/][1])[http://answers.xpertivy.ch/answer_link/46/][1] ) 2. The other possible (but not recommended way) would be to access the setter in an el-expression within the view: `#{data.setMyString(javaBean.evaluateString())}`. This is possible since within ivy expression language 2.2 is supported (which brought method calls for el-expressions) [1]: http://answers.xpertivy.ch/answer_link/46/

It's a standard JSF problem: 1. Try to communicate directly between the two beans. Resolve them over the faces context and then call getters / setters. (as described here: [http://answers.xpertivy.ch/answer_link/46/][1]) 2. The other possible (but not recommended way) would be to access the setter in an el-expression within the view: `#{data.setMyString(javaBean.evaluateString())}`. This is possible since within ivy expression language 2.2 is supported (which brought method calls for el-expressions) [1]: http://answers.xpertivy.ch/answer_link/46/

It's a standard JSF problem: 1. Try to communicate directly between the two beans. Resolve them over the faces context and then call getters / setters. (as described here: [http://answers.xpertivy.ch/answer_link/46/][1]) 2. The other possible (but not recommended way) would be to access the setter in an el-expression within the view: `#{data.setMyString(javaBean.evaluateString())}`. <br/>`#{data.setMyString(javaBean.evaluateString())}`. This is possible since within ivy expression language 2.2 is supported (which brought method calls for el-expressions) [1]: http://answers.xpertivy.ch/answer_link/46/

It's a standard JSF problem: 1. Try to communicate directly between the two beans. Resolve them over the faces context and then call getters/setters. getters / setters. (as described here: [http://answers.xpertivy.ch/answer_link/46/][1]) 2. The other possible (but not recommended way) would be to access the setter in an el-expression within the view: `#{data.setMyString(javaBean.evaluateString())}`. <br/> This is possible since within ivy expression language 2.2 is supported (which brought method calls for el-expressions) [1]: http://answers.xpertivy.ch/answer_link/46/

It's a standard JSF problem: 1. Try to communicate directly between the two beans. Resolve them over the faces context and then call getters/setters. (as described here: [http://answers.xpertivy.ch/answer_link/46/][1]) 2. The other possible (but not recommended way) would be to access the setter in an el-expression within the view: `#{data.setMyString(javaBean.evaluateString())}`. <br/> This is possible since within ivy expression language 2.2 is supported (which brought method calls for el-expressions) [1]: http://answers.xpertivy.ch/answer_link/46/