> -----Original Message-----
> From: Marc Portier [mailto:[EMAIL PROTECTED]
> Sent: Dienstag, 1. Juli 2003 07:37
> To: [EMAIL PROTECTED]
> Subject: [woody] binding the forms to data
>
...
>
> The actual binding definition file could be filled with:
> <bnd:field id="widget-name"
> path="xpath expression into model" />
I don't see the added value of putting the binding definition into
a separate file. It should be inside the woody-definition file to
avoid yet another maintenance nightmare of joining two XML files by
an id.
> Using JXPath there should be a fairly easy way to have this
> binding work for a backend producing either javabeans or XML files.
>
> what do people think?
The possibility to define constant initial values in <wd:datatype>
is urgently needed. To have an easy way to set it dynamically would
be really cool.
<wd:field id="widget-name">
<wd:datatype base="string">
<wd:initial>constant value</wd:initial>
<!-- or -->
<wd:initial path="'constant value'"/>
<!-- dynamic -->
<wd:initial path="xpath expression into model"/>
</wd:datatype>
</wd:field>
A general load/save binding specification in XML can get pretty
nasty for real-world examples with one-to-many and many-to-one
mappings between external form and model attributes.
I'd say Woody should stick to the rule to have a simple solution
for simple problems and provide hooks for solving difficult problems
in Java.
Cheers, Alfred.
This message is for the named person's use only. It may contain
confidential, proprietary or legally privileged information. No
confidentiality or privilege is waived or lost by any mistransmission.
If you receive this message in error, please notify the sender urgently
and then immediately delete the message and any copies of it from your
system. Please also immediately destroy any hardcopies of the message.
You must not, directly or indirectly, use, disclose, distribute, print,
or copy any part of this message if you are not the intended recipient.
The sender's company reserves the right to monitor all e-mail
communications through their networks. Any views expressed in this
message are those of the individual sender, except where the message
states otherwise and the sender is authorised to state them to be the
views of the sender's company.
