A
Ashton
Seems like the more time I spend with XDoclet, the more I appreciate it.
(If the documentation actually explained things rather than just listing
them that would be nice too, but one can't have everything.
)
What it's made me consider is how much time I spend writing code that's
essentially a re-expression of information that already exists in some
other machine-readable form. For example, many applications start with
a database schema...maybe it already exists, maybe it's part of the
spec....
It should be possible to derive reasonable starting points for data
entry and reports as HTML or JSP/Struts pages by analyzing the DB meta
information. Since I can remember FoxPro doing it about a dozen years
ago, I'm assuming there's not a great deal of magic involved.
Before I get sidetracked into writing my own, are there existing tools
that do this?
(If the documentation actually explained things rather than just listing
them that would be nice too, but one can't have everything.
What it's made me consider is how much time I spend writing code that's
essentially a re-expression of information that already exists in some
other machine-readable form. For example, many applications start with
a database schema...maybe it already exists, maybe it's part of the
spec....
It should be possible to derive reasonable starting points for data
entry and reports as HTML or JSP/Struts pages by analyzing the DB meta
information. Since I can remember FoxPro doing it about a dozen years
ago, I'm assuming there's not a great deal of magic involved.
Before I get sidetracked into writing my own, are there existing tools
that do this?