Dave Bettin wrote:
> Before I start formulating my design ideas, what are
> some of the design goals(you had in mine) regarding
> the XPath, DOM, and JDBC issues?
>
I have not thought out design plans in detail, but the following goals
would be high on my list:
* For the existing custom bean tags, such as <bean:define>
or <bean:write>, the page designer should not know or care
whether the underlying data is JavaBeans (the currently supported
property lookup mechanism), a DOM object (where attributes and
nested elements look like "properties"), or a JDBC ResultSet
or RowSet (which appear to be a collection of beans, where each
row is a bean and each column is a property).
* For existing tags that take "name", "property", and "scope"
arguments, define an "xpath" attribute that uses an XPath
expression to access properties. This would be an alternative
to the existing name/property/scope access, extended as
defined in the previous point.
The basic idea is we want to make the presentation pages as independent
as possible of the actual architecture of the data that is provided by
the business logic. In addition, transparent support for DOM and JDBC
objects will enable simple applications that require little or no
processing to be created.
>
> Regards,
> Dave Bettin
>
Craig McClanahan
