[seam-dev] SAF (aka Entity Framework) idea in Seam 3

[Jason Porter]

The Home idea
https://github.com/seam/seam-example-confbuzz/blob/develop/src/main/java/seam/example/confbuzz/ConferenceInstance.java

The Query idea
https://github.com/seam/seam-example-confbuzz/blob/develop/src/main/java/seam/example/confbuzz/TodaysConferencesQuery.java

The main thing that I would change with the Query class above is to use
named queries, thus espousing the generally accepted best practice in
default applications. I understand this doesn't fill all the gaps of the
older SAF from Seam 2, but I think it works for the majority of cases, and
it also helps people understand the best way to do things instead of relying
on the magic of SAF from Seam 2 (which I have found to be a major problem in
projects and teams I have worked with over the last three years).

I've spoken with Lincoln about this and there are two JIRAs (
https://issues.jboss.org/browse/SEAMFORGE-280 and
https://issues.jboss.org/browse/SEAMFORGE-279) to have Forge generate this
via the JPA plugin or perhaps Seam Persistence plugin.

Discuss.
-- 
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp

Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling

PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20110919/89283608/attachment.html