Menu
▾
▴
springframework-developer
|
From: <jue...@we...> - 2003-08-30 03:47:34
|
SGkgZXZlcnlib2R5LA0KIA0KU3ByaW5nIEZyYW1ld29yayAxLjAgTTEgaGFzIGp1c3QgYmVlbiBy ZWxlYXNlZC4gVGhpcyBmaXJzdCBtaWxlc3RvbmUgcmVsZWFzZSB0b3dhcmRzIDEuMCBpbnRyb2R1 Y2VzIG9yZy5zcHJpbmdmcmFtZXdvcmsgYXMgcGFja2FnZSBuYW1lLCBzdXBlcnNlZGluZyBjb20u aW50ZXJmYWNlMjEgd2hpY2ggc3RpbGwgZGF0ZWQgYmFjayB0byB0aGUgb3JpZ2luYWwgdmVyc2lv biBmcm9tIHRoZSBib29rLiBPZiBjb3Vyc2UsIGl0IG9mZmVycyBhIG15cmlhZCBvZiBpbXByb3Zl bWVudHMgYW5kIG5ldyBmZWF0dXJlcyAtIHNlZSB0aGUgY2hhbmdlIGxvZyBmb3IgZGV0YWlscy4N CiANCkluIGVuY291cmFnZSBldmVyeW9uZSB0byBtaWdyYXRlIGZyb20gMC45LnggdG8gMS4wIE0x LCB3aGljaCBzaG91bGQgdHlwaWNhbGx5IGp1c3QgaW52b2x2ZSBhIHNlYXJjaC1hbmQtcmVwbGFj ZSBmcm9tIGNvbS5pbnRlcmZhY2UyMSB0byBvcmcuc3ByaW5nZnJhbWV3b3JrIGluIGJvdGggc291 cmNlIGNvZGUgYW5kIFhNTCBiZWFuIGRlZmluaXRpb24gZmlsZXMuDQogDQpCVFcsIEkndmUgYWxz byBzaWduaWZpY2FudGx5IHJldmlzZWQgdGhlIFNwcmluZyBhcnRpY2xlIGluIHRoZSBIaWJlcm5h dGUgY29tbXVuaXR5IGFyZWEgdG9kYXkuIENoZWNrIGl0IG91dCBpZiB5b3UncmUgaW50ZXJlc3Rl ZC4NCiANCkFuZCBub3csIEknbSBsZWF2aW5nIGZvciBteSA0IHdlZWsgdHJpcCB0byBBdXN0cmFs aWEuIDUgaG91cnMgdG8gZ28gdW50aWwgbGlmdC1vZmYgOy0pDQogDQpSZWdhcmRzLA0KSnVlcmdl bg0KIA0KUC5TLjoNClRob21hcywgY2FuIHlvdSBwbGVhc2UgdXBkYXRlIG91ciB3ZWJzaXRlIGFj Y29yZGluZ2x5Pw0K |
|
From: Jean-Pierre <jp...@jp...> - 2003-08-30 10:54:03
|
<quote> Hi everybody, Spring Framework 1.0 M1 has just been released. This first milestone release towards 1.0 introduces org.springframework as package name, superseding com.interface21 which still dated back to the original version from the book. Of course, it offers a myriad of improvements and new features - see the change log for details. In encourage everyone to migrate from 0.9.x to 1.0 M1, which should typically just involve a search-and-replace from com.interface21 to org.springframework in both source code and XML bean definition files. BTW, I've also significantly revised the Spring article in the Hibernate community area today. Check it out if you're interested. And now, I'm leaving for my 4 week trip to Australia. 5 hours to go until lift-off ;-) Regards, Juergen </quote> It's a great date!!! Juergen, Once more, thanks for your great work into the team. Now, we will have to live a month without you :-(. I wish you a good trip :-))! <COUNTRIES AND LIGHT-COUNTRIES SAMPLES> The discussion of these last nays showed that one way of our efforts will to minimize the learning curve. For a first step, this give me the idea of 'light-countries' which is the Countries without any database use and therefore hassle as I would it primarily. But the actual implementation in the CVS is absolutely temporary as they are in most part redundant. So I will relatively quickly make the following changes. - Sharing the packages names - Have the 'Light-Countries' as basic project to allow the study of the Spring MVC without any database handling - Refactoring the "Countries" project to be an enhancement of "Light-Countries". * On the java part, it will add some Classes, subclass others and simply use the lasts from the "light" project. * On the web part, it will pick the common files from the "light" project and only define the changed and new ones. So, the new user will be able to study and understand our basic configuration scheme and internals with a first sample and go the jdbc handling in a second. The "Countries" will be very light and concentrated on the add of database support. By the way, the application subclassing by itself can light some possibilities. <GENERAL SAMPLES> Generally, as time pass, we will have more samples. For help at best users, I consider we will to have specialized samples that don't force the user to embrass too many aspects of the framework. And then samples considering the basics understood to go into an advanced area or all-together real life like ones. In this optic, concerning Petclinic, I don't advocate including Hibernate in it what would confuse the user. Instead, a Hibernate version could be added, maybe taking the same approach as 'light-Countries/Countries'. For now: an ascending learning order could be: 1) Step-by-step 2) Light-Countries 3) Petclinic and Countries 4) Upcoming Hibernate sample? 5) AOP and transactions samples, by the way, the "Spring" way to replace EJBs? And last but not least, in parallel, when time comes to create applications, the skeletons part of the samples. Regards, Jean-Pierre |
|
From: Colin S. <col...@ex...> - 2003-08-30 12:48:29
|
Juergen checked in a document I wrote about integrating Tapestry and Spring Framework. Of course using the normal approach you'd use with something like Struts, directly calling WebApplicationContextUtils.getWebApplicationContext will work fine. The document however describes a bit of a higher level way of integrating, where beans from the Spring context are added declaratively to a Tapestry page or component, maintaining the inversion of control approach all the way up the layer stack. I don't know if this belongs on the web site or not (you guys can decide), but I just wanted to let you know it existed. Regards, Colin |
|
From: JP P. <jp....@ti...> - 2003-08-30 13:01:50
|
Hi Colin, The document exists, good, but where? Maintaining the inversion of Control, good but I expected it ;-).=20 What about MVC as, if I well understood, Tapestry is more dot.net like and doesn't naturally use the MVC paradigm? Regards, Jean-Pierre -----Message d'origine----- De=A0: spr...@li... [mailto:spr...@li...] De la part de Colin Sampaleanu Envoy=E9=A0: samedi 30 ao=FBt 2003 14:48 =C0=A0: spr...@li...; spr...@li... Objet=A0: [Springframework-user] Integrating Tapestry and Spring = Framework Juergen checked in a document I wrote about integrating Tapestry and=20 Spring Framework. Of course using the normal approach you'd use with=20 something like Struts, directly calling=20 WebApplicationContextUtils.getWebApplicationContext will work fine. The=20 document however describes a bit of a higher level way of integrating,=20 where beans from the Spring context are added declaratively to a=20 Tapestry page or component, maintaining the inversion of control=20 approach all the way up the layer stack. I don't know if this belongs on the web site or not (you guys can=20 decide), but I just wanted to let you know it existed. Regards, Colin |
|
From: Colin S. <col...@ex...> - 2003-08-30 19:35:57
|
(First of all, I don't understand why your message below got to me, but apparently not to the lists...) The document I mentioned is in the .../docs/integration dir in the project. W/regards to the MVC aspect, I wouldn't say at all that Tapestry doesn't 'naturally' use the MVC paradigm. The main value add in Tapestry comes from the fact that it is component oriented, with a component object model similar to a traditional UI like Swing or SWT. This can make it tremendously easier in some cases (compared to more traditional web UI frameworks) to have pages and components with other components embedded within them, and have the framework maintain properties within these nested pages and components for you, with almost no effort. So programming in Tapestry can be much more like programming in a traditional client side UI, while still being able to work efficiently in a multi-user, web environment (as opposed to a few frameworks that directly try to translate Swing or something like Swing to the web). I think in this respect it can make it easier to do real MVC style apps than most web ui frameworks. Just as you can create a client side app in Swing or MFC that is somewhat more or less 'MVC style' than another app, most of the same options options are basically available you you in Tapestry. You can create a Tapestry app where everything is essentially handled by the pages themselves, that is, all links come back into the pages, and the pages decide how to process actions and what page to go next, etc. On the other hand, the callback or event style components are rich enough that you can easily do an app in which a 'controller' handles certain things. This is without having to get you involved in event/action processing just to handle the updating and the display of some piece of some component on the web page. To give you a more concrete example, something like Struts makes it relatively simple to handle a simple page which has a form on it, which on a submit comes into an action handler, which does processing, and you go somewhere else. You can even do simple validation, and go back to the same form and not ahve to work _too_ much to access the form properties. Now try to do a page which contains a component, embedded within it another component, and in that, another component, which has a list of three radio buttons, and when one of the radio buttons is pressed, you want to go back to the server to recalculate something that is displayed on the page, but still maintain state for all the components on the same page. You'll kill yourself trying to do this in most frameworks, while in Tapestry you don't even think about it. You worry about handling events that mean something to your app (or your page), but don't go through the incredible contortions that some other frameworks force you to go through to handle rich UIs. You can get an idea of what components are available here: http://jakarta.apache.org/tapestry/doc_frame.html The general docs are here: http://jakarta.apache.org/tapestry/doc_frame.html Be warned that unfortunately, while Tapestry 3 is very usable, the docs are somewhat out of date. The component reference is fairly complete, but most examples use the older style of defining page templates and definitions, which is more verbose (and more work). The User's Guide is accurate but still needs some work. The other documents are mostly fairly out of date. Now that that 3.0 is basically done, the documentation is slowly being worked on, and there is actually a book from Manning coming out in a couple of months written by Howard Lewis Ship, the original creator of Tapestry... Regards, Colin JP Pawlak wrote: >Hi Colin, > >The document exists, good, but where? > >Maintaining the inversion of Control, good but I expected it ;-). >What about MVC as, if I well understood, Tapestry is more dot.net like >and doesn't naturally use the MVC paradigm? > >Regards, >Jean-Pierre > >-----Message d'origine----- >De : spr...@li... >[mailto:spr...@li...] De la part de >Colin Sampaleanu >Envoyé : samedi 30 août 2003 14:48 >À : spr...@li...; >spr...@li... >Objet : [Springframework-user] Integrating Tapestry and Spring Framework > >Juergen checked in a document I wrote about integrating Tapestry and >Spring Framework. Of course using the normal approach you'd use with >something like Struts, directly calling >WebApplicationContextUtils.getWebApplicationContext will work fine. The >document however describes a bit of a higher level way of integrating, >where beans from the Spring context are added declaratively to a >Tapestry page or component, maintaining the inversion of control >approach all the way up the layer stack. > >I don't know if this belongs on the web site or not (you guys can >decide), but I just wanted to let you know it existed. > >Regards, >Colin > > > |
|
From: <tri...@tr...> - 2003-08-30 14:45:41
|
Colin, I have added a link to the documentation page on our website. Thanks, Thomas > Juergen checked in a document I wrote about integrating Tapestry and > Spring Framework. Of course using the normal approach you'd use with > something like Struts, directly calling > WebApplicationContextUtils.getWebApplicationContext will work fine. The > document however describes a bit of a higher level way of integrating, > where beans from the Spring context are added declaratively to a > Tapestry page or component, maintaining the inversion of control > approach all the way up the layer stack. > > I don't know if this belongs on the web site or not (you guys can > decide), but I just wanted to let you know it existed. > > Regards, > Colin > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Springframework-user mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-user > |
