Re: Beanform: Nested Beanforms with Binding Overrides

2007-01-11 Thread DJ Gredler

Well, I'm glad you sorted it out :-)

On 1/11/07, Steve Wells [EMAIL PROTECTED] wrote:


ok, after rolling back to just a simple one-off Beanform on its own and it
still failing ,cleaning the hell out of everything, the problem seems to
have (most unbelievably) been an empty left-over .page file; it only had
the
page-specification...

Serve me right for leaving mess around.

On 10/01/07, Steve Wells [EMAIL PROTECTED] wrote:

 Hi Daniel,

 None of them print correctly.

 I meant the only thing printed is the name of the property surrounded by
 '[]' eg: [PASSWORD]:

 text=literal:possibility was me experimenting trying to remove
 uncertainties.  I found when you use a resource bundle for the page with
 BeanForm and use  _title=ognl: messages.getMessage(
 components.bf.property.name + '_title' ) :

 1. the field prompt text is taken from a properties file property with
the
 same name as the Bean property and
 2. the field label is taken from property_name
 So if I have a bean property text and in my page properties file
 text=Enter some text
 text_title=This is where you type stuff

 you will get:
 td class=bf_Left id=informal_0label for=nameEnter some
 text/label:/td

 td class=bf_Right id=informal_1input type=text name=name
 value= id=name title=This is where you type stuff class=text
//td

  I've tried removing: _title=ognl:messages.getMessage(
 components.bf.property.name + '_title' ) and other combinations but
 nothing quite works...yet.

  On 10/01/07, DJ Gredler [EMAIL PROTECTED] wrote:
 
  I'm not sure why this would cause a problem. So looking at your code,
  you're
  saying that the titles for BeanForm bf print correctly, but the
title
  for
  BeanForm bf_inner doesn't? Or neither of them work?
 
  What do you mean by all I see is the [PROPERTY_NAME] coming out?
 
  As an aside, what is the following binding on bf_inner supposed to
be
  doing?
 
text=literal:possibility
 
 
  On 1/11/07, Steve Wells [EMAIL PROTECTED] wrote:
  
   Hi,
  
   Bit of extreme BF'ing here.  Titles are not printing; be it
  dynamically or
   literally when I do something of the form:
  
   form
   beanform1
   for (iterate over a list)
   new beanform from each list item
  
   All I see is the [PROPERTY_NAME] coming out.
  
   Detailed Code as follows:
  
   form jwcid=[EMAIL PROTECTED] delegate=bean:delegate
   clientValidationEnabled=ognl:false
  
   table jwcid= [EMAIL PROTECTED]:BeanForm bean=prop:vote
  
  
properties=literal:question=TextArea,explaination=TextArea,expiresOn
   _title=ognl:messages.getMessage(
components.bf.property.name+
   '_title' )
   /table
  
   span jwcid=@For source=ognl:vote.possibilityList
   value=prop:possibility
table jwcid=[EMAIL PROTECTED]:BeanForm bean=prop:possibility
   properties=text
   text=literal:possibility
   text_title=literal:possibility text
  /table
   /span
   input jwcid=[EMAIL PROTECTED] value=literal:create Vote
   listener=listener:createVote/
   /form
  
   Any ideas?
  
   Thanks,
  
   Steve
  
  
 
 





Beanform: Nested Beanforms with Binding Overrides

2007-01-10 Thread Steve Wells

Hi,

Bit of extreme BF'ing here.  Titles are not printing; be it dynamically or
literally when I do something of the form:

form
   beanform1
   for (iterate over a list)
   new beanform from each list item

All I see is the [PROPERTY_NAME] coming out.

Detailed Code as follows:

form jwcid=[EMAIL PROTECTED] delegate=bean:delegate
   clientValidationEnabled=ognl:false

   table jwcid=[EMAIL PROTECTED]:BeanForm bean=prop:vote

properties=literal:question=TextArea,explaination=TextArea,expiresOn
   _title=ognl:messages.getMessage(components.bf.property.name +
'_title' )
   /table

   span jwcid=@For source=ognl:vote.possibilityList
value=prop:possibility
table jwcid=[EMAIL PROTECTED]:BeanForm bean=prop:possibility
   properties=text
   text=literal:possibility
   text_title=literal:possibility text
  /table
   /span
   input jwcid=[EMAIL PROTECTED] value=literal:create Vote
listener=listener:createVote/
/form

Any ideas?

Thanks,

Steve


Re: Beanform: Nested Beanforms with Binding Overrides

2007-01-10 Thread DJ Gredler

I'm not sure why this would cause a problem. So looking at your code, you're
saying that the titles for BeanForm bf print correctly, but the title for
BeanForm bf_inner doesn't? Or neither of them work?

What do you mean by all I see is the [PROPERTY_NAME] coming out?

As an aside, what is the following binding on bf_inner supposed to be
doing?

  text=literal:possibility


On 1/11/07, Steve Wells [EMAIL PROTECTED] wrote:


Hi,

Bit of extreme BF'ing here.  Titles are not printing; be it dynamically or
literally when I do something of the form:

form
beanform1
for (iterate over a list)
new beanform from each list item

All I see is the [PROPERTY_NAME] coming out.

Detailed Code as follows:

form jwcid=[EMAIL PROTECTED] delegate=bean:delegate
clientValidationEnabled=ognl:false

table jwcid=[EMAIL PROTECTED]:BeanForm bean=prop:vote

properties=literal:question=TextArea,explaination=TextArea,expiresOn
_title=ognl:messages.getMessage(components.bf.property.name +
'_title' )
/table

span jwcid=@For source=ognl:vote.possibilityList
value=prop:possibility
 table jwcid=[EMAIL PROTECTED]:BeanForm bean=prop:possibility
properties=text
text=literal:possibility
text_title=literal:possibility text
   /table
/span
input jwcid=[EMAIL PROTECTED] value=literal:create Vote
listener=listener:createVote/
/form

Any ideas?

Thanks,

Steve




Re: Beanform: Nested Beanforms with Binding Overrides

2007-01-10 Thread Steve Wells

ok, after rolling back to just a simple one-off Beanform on its own and it
still failing ,cleaning the hell out of everything, the problem seems to
have (most unbelievably) been an empty left-over .page file; it only had the
page-specification...

Serve me right for leaving mess around.

On 10/01/07, Steve Wells [EMAIL PROTECTED] wrote:


Hi Daniel,

None of them print correctly.

I meant the only thing printed is the name of the property surrounded by
'[]' eg: [PASSWORD]:

text=literal:possibility was me experimenting trying to remove
uncertainties.  I found when you use a resource bundle for the page with
BeanForm and use  _title=ognl: messages.getMessage(
components.bf.property.name + '_title' ) :

1. the field prompt text is taken from a properties file property with the
same name as the Bean property and
2. the field label is taken from property_name
So if I have a bean property text and in my page properties file
text=Enter some text
text_title=This is where you type stuff

you will get:
td class=bf_Left id=informal_0label for=nameEnter some
text/label:/td

td class=bf_Right id=informal_1input type=text name=name
value= id=name title=This is where you type stuff class=text //td

 I've tried removing: _title=ognl:messages.getMessage(
components.bf.property.name + '_title' ) and other combinations but
nothing quite works...yet.

 On 10/01/07, DJ Gredler [EMAIL PROTECTED] wrote:

 I'm not sure why this would cause a problem. So looking at your code,
 you're
 saying that the titles for BeanForm bf print correctly, but the title
 for
 BeanForm bf_inner doesn't? Or neither of them work?

 What do you mean by all I see is the [PROPERTY_NAME] coming out?

 As an aside, what is the following binding on bf_inner supposed to be
 doing?

   text=literal:possibility


 On 1/11/07, Steve Wells [EMAIL PROTECTED] wrote:
 
  Hi,
 
  Bit of extreme BF'ing here.  Titles are not printing; be it
 dynamically or
  literally when I do something of the form:
 
  form
  beanform1
  for (iterate over a list)
  new beanform from each list item
 
  All I see is the [PROPERTY_NAME] coming out.
 
  Detailed Code as follows:
 
  form jwcid=[EMAIL PROTECTED] delegate=bean:delegate
  clientValidationEnabled=ognl:false
 
  table jwcid= [EMAIL PROTECTED]:BeanForm bean=prop:vote
 
  properties=literal:question=TextArea,explaination=TextArea,expiresOn
  _title=ognl:messages.getMessage( components.bf.property.name+
  '_title' )
  /table
 
  span jwcid=@For source=ognl:vote.possibilityList
  value=prop:possibility
   table jwcid=[EMAIL PROTECTED]:BeanForm bean=prop:possibility
  properties=text
  text=literal:possibility
  text_title=literal:possibility text
 /table
  /span
  input jwcid=[EMAIL PROTECTED] value=literal:create Vote
  listener=listener:createVote/
  /form
 
  Any ideas?
 
  Thanks,
 
  Steve