But forgive me, but aren't you asking people to use third partyframeworks
that may not even work with some database implementations? As far as I
know, GRAILS is pretty much synced up with Spring and Hibernate; what if
you don't use those?
That's my point exactly! There is complexity in choosing frameworks
you can't simply pick-n-pack without doing thorough testing, and there in
lies some of Java's complexity.
What if there were cases where it didn't make sense to go through RPG
to get to the database because it was more of a reporting section of the
software? Would you consider an ORM solution like Hibernate in that case?
Note that I am well aware of Hibernates short comings, and that is where
it helps to have some experience with these "off the shelf" code sets.
Do you have an example implementation of your framework on the web
somewhere that we can review it?
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.