>From: James Mitchell <[EMAIL PROTECTED]> > > Assuming we move to 1.5 (with comparable -j4 bits), would we even > have a 'tiger' or an 'annotations' project? >
Now, that would be nice to be able to start migration to 1.5 but have 1.4 compatibility. There are some 1.5 ideas that I would like to experiment with for Clay but I don't want to create another project. It would be interesting to use annotations to define a Clay CRUD based form using the Clay runtime option. This would be a one-to-one mapping of a "entity" to a form. The widgets could be build from annotations on a JPA entity bean - just a simple/quick CRUD form. Gary > -- > James Mitchell > 678.910.8017 > > > > > On Oct 13, 2006, at 4:51 PM, Craig McClanahan wrote: > > > On 10/13/06, Matthias Wessendorf wrote: > >> > >> + 0.9 > >> > >> should tiger really be a tiger? > > > > > > C'mon, we gotta have at least *one* cool name :-). The original > > motivation > > here was that Tiger was the codename for Java SE 5. > > > > shale annotations ? > > > > > > My concern here would be that there's both annotations, and a bunch of > > functionality that processes those annotations, in the same module. > > > > Craig > > > > On 10/13/06, Craig McClanahan wrote: > >> > On 10/13/06, Rahul Akolkar wrote: > >> > > > >> > > Here's the abbreviated reactor summary on the framework build: > >> > > > >> > > [INFO] Shale Test Framework > >> > > [INFO] Shale Core Library > >> > > [INFO] Shale Application Controller Support > >> > > [INFO] Shale Clay Plugin > >> > > [INFO] Shale Dialog Manager Integration > >> > > [INFO] Shale Dialog Manager (Basic Implementation) > >> > > [INFO] Shale Dialog Manager (SCXML Implementation) > >> > > [INFO] Shale Remoting Support > >> > > [INFO] Shale-Spring Integration > >> > > [INFO] Shale View Controller Support > >> > > [INFO] Shale Tiger Extensions > >> > > [INFO] Shale Tiles Integration > >> > > [INFO] Shale Validator Support > >> > > > >> > > We have frameworks, libraries, supports, integrations, > >> extensions, > >> > > plugins. > >> > > * What in clay gives it a plugin status? > >> > > * What differentiates support from say, library? > >> > > * Integration means value-add based on an "outside" artifact, > >> but why > >> > > is shale-dialog an integration (we have a "native" impl)? > >> > > > >> > > Quibbling, but before someone asks me, I must ask you. > >> > > > >> > > How about ditching the library, support and plugin qualifiers? > >> How > >> > > does this look: > >> > > > >> > > [INFO] Shale Test Framework > >> > > [INFO] Shale Core > >> > > [INFO] Shale Application Controller > >> > > [INFO] Shale Clay > >> > > [INFO] Shale Dialog Manager > >> > > [INFO] Shale Dialog Manager (Basic Implementation) > >> > > [INFO] Shale Dialog Manager (SCXML Implementation) > >> > > [INFO] Shale Remoting > >> > > [INFO] Shale Spring Integration > >> > > [INFO] Shale View Controller > >> > > [INFO] Shale Tiger Extensions > >> > > [INFO] Shale Tiles Integration > >> > > [INFO] Shale Validator Integration > >> > > >> > > >> > These names work for me. +1. > >> > > >> > Craig > >> > > >> > > >> > -Rahul > >> > > > >> > > >> > > >> > >> > >> -- > >> Matthias Wessendorf > >> http://tinyurl.com/fmywh > >> > >> further stuff: > >> blog: http://jroller.com/page/mwessendorf > >> mail: mwessendorf-at-gmail-dot-com > >> >
