on 6/14/01 6:11 AM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> but it very
> important that business logic authors don't need to work about the
> mechanics of using one type of object over another and that they don't
> have to write boilerplate code.
That is why we follow a common specification...the JavaBean specification.
:-)
If Jython's objects are not following that specification, then that is
Jython's problem and Velocity should not be modified to support that.
:-)
Creating a wrapper around Jython's objects (by simply extending them) and
providing Bean methods seems like a pretty easy way to solve the problem.
You could even call the object FooBean, BarBean, etc...long term, it would
probably be preferable to fix Jython to follow the Bean standard.
:-)
Thanks,
-jon
