Kent's book. All the developers here are using it. Bear in mind that the picture you should have is of components and objects. They are defined in three places, html, page/component specification (slightly complicated by possible annotation instead), java. These three are bound together in varying quantities, but always together. Note about annotation, it is telling you "I belong in here" in other words, the same binding together. A component is: a) acted upon by the framework which does a lot of work for you, but you must be aware of the services it provides. b) finds its place on an object graph tree through definitions in the T hivemodule.xml. So what does that mean? The services defined in hivemodule may be seen as arcs on a graph. For instance, if security is defined in hivemodule, then every component that *pulls* in that service is effectively a node on the security graph arc. There are several such arcs. They are connected to the application through their definition, for instance whether they are singletons thread local, or (many) other attributes. These conceptualisations are off the top of my head. Please shoot me down if anyone disagrees or can put it better. I hope there is nothing here misleading? Adam
On 16/12/05, John Coleman <[EMAIL PROTECTED]> wrote: > > Our developers also recommend Kents book. What they really liked is it > starts with setting up Eclipse from scratch, so you start the exercises > with > things looking exactly the same. > > Don't worry about the learning curve, I don't think it is much longer than > Struts to do the basic stuff. You'll get a form up and running in no time. > You hit the curve when you want to do something not so basic, then you can > use the support list. :) > > John > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
