=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm working on offering several form handling macros for our Velocity and=20
=46reeMarker support, the first task of which is to offer equivalents to th=
e=20
existing <spring:bind> JSP tags.
Although a version of this is currently working for both Velocity and FM,=20
I'm not entirely happy with it since it uses tools offered by the=20
respective projects for expression evaluation and there are limitations in=
=20
the implementation that don't apply to our bind tag.
What I want to do is leverage the existing JSP code which would mean=20
refactoring the BindTag and BindStatus classes (moving the non-JSP specific=
=20
code from the one into the other) making BindStatus more intelligent, and=20
reusable across different view technologies. Does anyone see any potential=
=20
issues or pitfalls here?
Regards,
=2D --=20
Darren Davison
Public Key: http://www.davison.uk.net/pages/key.htm
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFA4ofMKLMLAN01aw0RAjFjAJ9uR/kbzkStme/2Z4LqKmp2sEOmKQCgjmdg
N5fYtckAKlq0ksfkFoBoUAI=3D
=3D4KKC
=2D----END PGP SIGNATURE-----
|
