Menu
▾
▴
springframework-developer
|
From: <jue...@we...> - 2003-06-23 20:32:25
|
S2VuLCBSb2QsDQogDQpUbyBjbGFyaWZ5IHRoZSBjdXJyZW50IGJ1aWxkIHByb2Nlc3M6DQogDQot IFNwcmluZyBpdHNlbGYgc3RpbGwgaGFzIGl0cyBvd24gYnVpbGQueG1sLiBUaGUgcmVsZWFzZSBk aXN0cmlidXRpb24gd2lsbCBub3QgY29udGFpbiB0aGlzIGJ1dCBqdXN0IHRoZSBzb3VyY2VzIGFu ZCBwcmVidWlsdCBqYXJzLiBObyBuZWVkIGZvciBhIHJlbGVhc2UgdXNlciB0byBidWlsZCB0aGUg ZW50aXJlIFNwcmluZyBmcmFtZXdvcmsgLSB0aGF0J3MgYSBtaXNhcHByZWhlbnNpb24uDQogDQot IFRoZSBzYW1wbGVzIGhhdmUgdGhlaXIgb3duIGJ1aWxkLnhtbCBmaWxlcywgYnVpbGRpbmcgdGhl IHNhbXBsZSBqYXJzIGZyb20gdGhlIHNvdXJjZXMsIGFuZCBjb3B5aW5nIHRoZSByZXNwZWN0aXZl IFNwcmluZyBkaXN0IGphcnMgdG8gdGhlaXIgV0VCLUlORlxsaWIuIFRoZXkgZG8gbm90IHJlcXVp cmUgU3ByaW5nJ3MgbWFpbiBidWlsZC54bWwgYnV0IGp1c3QgaXRzIHByZWJ1aWx0IGphcnMgYW5k IHNvbWUgb2YgdGhlIHRoaXJkLXBhcnR5IGxpYnMgaW4gdGhlIG1haW4gbGliIGRpcmVjdG9yeS4g V2l0aCB0aGUgY3VycmVudCBsYXlvdXQsIHRoaXMgd29ya3MgYm90aCB3aXRoIGEgU3ByaW5nIENW UyBzbmFwc2hvdCBhbmQgYSByZWxlYXNlIGRpc3RyaWJ1dGlvbi4NCiANCi0gU28gY3VycmVudGx5 IGEgcmVsZWFzZSBkaXN0cmlidXRpb24gY29udGFpbnMgcHJlYnVpbHQgU3ByaW5nIGphcnMgYnV0 IGp1c3QgdGhlIHNvdXJjZXMgb2YgdGhlIHNhbXBsZXMuIEdvaW5nIGluIHRoZSAic2FtcGxlcy9w ZXRjbGluaWMiIHJlc3AuICJzYW1wbGVzL3BhZ2VkbGlzdCIgZGlyZWN0b3J5IGFuZCBpbnZva2lu ZyAiYW50IGJ1aWxkIiBvciAiYW50IHdhcmZpbGUiIGdlbmVyYXRlcyBhIGRlcGxveWFibGUgdmVy c2lvbiwgaW4gYW55IGNhc2Ugd2l0aCBjdXJyZW50IFNwcmluZyBqYXJzLg0KIA0KLSBUaGVyZSBh cmUgMiBtYWluIGFkdmFudGFnZXMgdG8gdGhlIGN1cnJlbnQgd2F5OiBUaGUgc2FtcGxlcyB3aWxs IGFsd2F5cyBiZSBidWlsdCB3aXRoIGN1cnJlbnQgU3ByaW5nIGphcnMsIGFuZCB0aGVyZSdzIG5v IHRyaXBsaWNhdGlvbiBvZiBTcHJpbmcgb3IgdGhpcmQtcGFydHkgamFycyAtIHRodXMgdGhlIDUg TUIgZG93bmxvYWQuIA0KIA0KLSBUaGUgYWx0ZXJuYXRpdmUgd291bGQgYmUgdG8gcHJlcGFja2Fn ZSB0aGUgc2FtcGxlcyBhcyB3YXJzLiBUaGUgZGlzYWR2YW50YWdlcyBhcHBseTogdHJpcGxpY2F0 ZWQgU3ByaW5nIGphcnMgYW5kIHRoaXJkIHBhcnR5IGxpYnMgdGhhdCBtYXkgYmUgb3V0IG9mIHN5 bmMuIFRoYXQgbWlnaHQgc3RpbGwgYmUgYW4gYWNjZXB0YWJsZSB0cmFkZW9mZiBmb3IgYSByZWxl YXNlIGRpc3RyaWJ1dGlvbjogZXh0cmEgMiBNQiBmb3IgcHJlZ2VuZXJhdGVkIHdhcnMgb2YgYm90 aCBzYW1wbGVzLiBJZiBhIG1ham9yaXR5IHZvdGVzIGZvciBpdCwgZmluZSAtIGZvciBhIHJlbGVh c2UuDQogDQotIEluIGFueSBjYXNlLCBJJ2QgbGlrZSB0byBrZWVwIHRoZSBjdXJyZW50IGJ1aWxk aW5nIGZyb20gQ1ZTIGFzIGl0IGlzLiBHZW5lcmF0aW5nIG5ldyBTcHJpbmcgamFycyBhbGwgdGhl IHRpbWUgYW5kIGNvbW1pdHRpbmcgdGhlbSB0byB0aGUgc2FtcGxlcycgV0VCLUlORi9saWIgZGly ZWN0b3JpZXMgaXMgdmVyeSB1bmhhbmR5LiBXZSdyZSB0YWxraW5nIGFib3V0IHRoZSBldm9sdmlu ZyBmcmFtZXdvcmsgaGVyZSwgd2l0aCBmcmVxdWVudCBjaGFuZ2VzIHRvIGJlIGV4cGVjdGVkLiBB bmQgQ1ZTIHNuYXBzaG90IHVzZXJzIGhhdmUgdG8gYmUgZmFtaWxhciB3aXRoIEFudCBhbnl3YXku DQogDQotIExldCdzIG5vdCBmb3JnZXQgdGhhdCBvdXIgY3VycmVudCBkZW1vcyBhcmVuJ3QgcGFy dGljdWxhcmx5IGNvbnZpbmNpbmcgaW4gdGVybXMgb2YgVUkgYXBwZWFyYW5jZS4gVGhlaXIgdmFs dWUgaXMgaW4gdGhlaXIgc291cmNlcyBhbmQgdGhlaXIgY29uZmlndXJhdGlvbiwgdG8gbGVhcm4g dHlwaWNhbCBTcHJpbmcgcGF0dGVybnMuIEluIG15IHZpZXcsIGRlcGxveWluZyB0aGVtIGlzIG5v dCB0aGVpciBwcmltYXJ5IHB1cnBvc2UsIHRodXMgd29ydGggYW4gZXh0cmEgc3RlcC4NCiANCk9m IGNvdXJzZSwgSSdtIG9wZW4gZm9yIGNoYW5nZXMgdG8gdGhlIGJ1aWxkIHByb2Nlc3MuIEl0J3Mg anVzdCB0aGF0IHdlIGhhdmVuJ3QgbXVjaCB0aW1lIGxlZnQgYmVmb3JlIHRoZSBUU1MgU3ltcG9z aXVtLCBzbyB3ZSBzaG91bGQgaHVycnkgYSBiaXQuDQogDQpCVFcsIFJvZDogV2UgYXJlIHJ1bm5p bmcgb3V0IG9mIHRpbWUgaW4gdGVybXMgb2YgZ2V0dGluZyBhIHJlbGVhc2UgcGx1cyBhIHByb3Bl ciB3ZWJzaXRlIG91dCBvbiBXZWRuZXNkYXkuIEJ1dCB3ZSBzaG91bGRuJ3QgZGVsYXkgaXQsIGEg cmVsZWFzZSBpcyBfcmVhbGx5XyBpbXBvcnRhbnQgbm93LiBVbmZvcnR1bmF0ZWx5LCBhIHJlbGVh c2Ugd2l0aCB0aGUgY3VycmVudCB3d3cuc3ByaW5nZnJhbWV3b3JrLm9yZyB3ZWJzaXRlIHdvdWxk IGxlYXZlIGEgc2hhbGxvdyBmaXJzdCBpbXByZXNzaW9uLCBzbyBJIGNvbnNpZGVyIGEgbmljZS1s b29raW5nIHdlYnNpdGUgaW1wb3J0YW50IHRvby4gSSdtIG5vdCBnZXR0aW5nIHRoaXMgc3RyYWln aHQgY3VycmVudGx5LiBXaGF0IGRvIHlvdSBzdWdnZXN0Pw0KIA0KUmVnYXJkcywNCkp1ZXJnZW4N CiANCiANCg0KCS0tLS0tVXJzcHLDvG5nbGljaGUgTmFjaHJpY2h0LS0tLS0gDQoJVm9uOiBSb2Qg Sm9obnNvbiBbbWFpbHRvOnJvZC5qb2huc29uQGludGVyZmFjZTIxLmNvbV0gDQoJR2VzZW5kZXQ6 IE1vIDIzLjA2LjIwMDMgMjE6MzQgDQoJQW46IEtlbiBLcmViczsgasO8cmdlbiBow7ZsbGVyIFt3 ZXJrM0FUXSANCglDYzogJ3NwcmluZy1kZXYtbGlzdCcgDQoJQmV0cmVmZjogUmU6IFtTcHJpbmdm cmFtZXdvcmstZGV2ZWxvcGVyXSBTYW1wbGUgQXBwbGljYXRpb24gYnVpbGQgcHJvY2Vzcw0KCQ0K CQ0KDQoJSSBhZ3JlZSB3aXRoIEtlbi4NCgkNCglJdCBzaG91bGQgYmUgKnBvc3NpYmxlKiwgYnV0 IG5vdCBuZWNlc3NhcnksIHRvIGRvd25sb2FkIGFuZCBidWlsZCBhbGwgb2YNCglTcHJpbmcgd2l0 aCB0aGUgZGVtb3MuIEl0IHNob3VsZCBiZSBlYXN5IHRvIGdldCBzdGFydGVkIHdpdGggYSBtaW5p bXVtIG9mDQoJZnVzcy4NCgkNCglSZWdhcmRzLA0KCVJvZA0KCQ0KCS0tLS0tIE9yaWdpbmFsIE1l c3NhZ2UgLS0tLS0NCglGcm9tOiAiS2VuIEtyZWJzIiA8a2tAa2t0ZWMuY29tPg0KCVRvOiAiasO8 cmdlbiBow7ZsbGVyIFt3ZXJrM0FUXSIgPGp1ZXJnZW4uaG9lbGxlckB3ZXJrM2F0LmNvbT4NCglD YzogIidzcHJpbmctZGV2LWxpc3QnIiA8c3ByaW5nZnJhbWV3b3JrLWRldmVsb3BlckBsaXN0cy5z b3VyY2Vmb3JnZS5uZXQ+DQoJU2VudDogTW9uZGF5LCBKdW5lIDIzLCAyMDAzIDc6MjYgUE0NCglT dWJqZWN0OiBbU3ByaW5nZnJhbWV3b3JrLWRldmVsb3Blcl0gU2FtcGxlIEFwcGxpY2F0aW9uIGJ1 aWxkIHByb2Nlc3MNCgkNCgkNCgk+IEp1ZXJnZW4sDQoJPg0KCT4gVGhlIGNoYW5nZXMgeW91IG1h ZGUgdG8gdGhlIFBldGNsaW5pYyBidWlsZCBmaWxlcyBoYXZlIHJhaXNlZCBhbg0KCT4gaW50ZXJl c3RpbmcgaXNzdWUgd2hpY2ggYXBwbGllcyB0byBhbGwgc2FtcGxlIHByb2dyYW1zOg0KCT4NCgk+ IFRoZSBjaGFuZ2VzIG1hZGUgbm93IHJlcXVpcmUgYSB1c2VyIG9mIHRoZSBzYW1wbGUgYXBwIHRv IGRvd25sb2FkIGFuZA0KCT4gYnVpbGQgdGhlIGVudGlyZSBTcHJpbmcgZnJhbWV3b3JrLiBJdCB3 YXMgc3BlY2lmaWNhbGx5IG15IGludGVudCB3aXRoDQoJPiBQZXRjbGluaWMgdG8gbm90IHJlcXVp cmUgdGhpcy4gSSBoYWQgZW52aXNpb25lZCBhIHNlcGFyYXRlbHkNCgk+IGRvd25sb2FkYWJsZSBk aXN0cmlidXRpb24gb2YgdGhlIHNhbXBsZS4gTWFueSBpZiBub3QgbW9zdCBkZXZlbG9wZXJzIGFy ZQ0KCT4ganVzdCBnb2luZyB0byB3YW50IHRvIHVzZSB0aGUgZnJhbWV3b3JrIHJ1bnRpbWUgamFy cywgYXQgbGVhc3QgYXQgZmlyc3QNCgk+IHdoZW4gdGhleSdyZSB0YWtpbmcgaXQgb3V0IGZvciBh IHRlc3QgZHJpdmUuDQoJPg0KCT4gVGhlIHByanppcCBhbnQgdGFyZ2V0IGlzIG9ubHkgbmVlZGVk IHRvIGNyZWF0ZSBhIGRpc3RyaWJ1dGlvbiBzbyBpdA0KCT4gcHJvYmFibHkgYmUgaW4gYSBzZXBh cmF0ZSBmaWxlIHdoaWNoIHdpbGwgbm90IGJlIGluY2x1ZGVkIGluIHRoZQ0KCT4gZGlzdHJpYnV0 aW9uLiBUaGlzIHByanppcCB0YXJnZXQgd2lsbCBuZWVkIHRvIGdyYWIgYSBjdXJyZW50IHNuYXBz aG90IG9mDQoJPiB0aGUgbGlicyBmb3IgaW5jbHVzaW9uIGluIHRoZSBkaXN0cmlidXRpb24uIEkg aGF2ZW4ndCBxdWl0ZSB3b3JrZWQgb3V0DQoJPiB0aGUgYmVzdCB3YXkgdG8gaW1wbGVtZW50IHRo aXMgeWV0Lg0KCT4NCgk+IFdoYXQgYXJlIHlvdXIgdGhvdWdodHMgb24gdGhpcyA/DQoJPg0KCT4g UmVnYXJkcywNCgk+DQoJPiBLZW4NCgk+DQoJPg0KCT4NCgk+IC0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCgk+IFRoaXMgU0YuTmV0IGVtYWls IGlzIHNwb25zb3JlZCBieTogSU5ldFUNCgk+IEF0dGVudGlvbiBXZWIgRGV2ZWxvcGVycyAmIENv bnN1bHRhbnRzOiBCZWNvbWUgQW4gSU5ldFUgSG9zdGluZyBQYXJ0bmVyLg0KCT4gUmVmZXIgRGVk aWNhdGVkIFNlcnZlcnMuIFdlIE1hbmFnZSBUaGVtLiBZb3UgR2V0IDEwJSBNb250aGx5IENvbW1p c3Npb24hDQoJPiBJTmV0VSBEZWRpY2F0ZWQgTWFuYWdlZCBIb3N0aW5nIGh0dHA6Ly93d3cuaW5l dHUubmV0L3BhcnRuZXIvaW5kZXgucGhwDQoJPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fXw0KCT4gU3ByaW5nZnJhbWV3b3JrLWRldmVsb3BlciBtYWlsaW5n IGxpc3QNCgk+IFNwcmluZ2ZyYW1ld29yay1kZXZlbG9wZXJAbGlzdHMuc291cmNlZm9yZ2UubmV0 DQoJPiBodHRwczovL2xpc3RzLnNvdXJjZWZvcmdlLm5ldC9saXN0cy9saXN0aW5mby9zcHJpbmdm cmFtZXdvcmstZGV2ZWxvcGVyDQoJPg0KCQ0KCQ0KCQ0KDQo= |
|
From: <jue...@we...> - 2003-06-24 07:36:33
|
Let's go for it for the moment, it looks nice enough. It doesn't leave a = shallow first impression, my main goal is reached :-) Thomas, can you update the PetClinic to the current CVS version, and add = the PagedList sample? Additional benefit: You would test the new build = processes of the current versions too ;-) Regarding future updates of = the samples: Let's try to avoid direct manipulation on the web servre, = instead keep as much as possible in CVS, and update the website from = there. I suggest to add a "Documentation" section between "Downloads" and = "Demo/Tutorial", providing a page with links to our Javadoc, and to = introductory essays. Thomas, can you generate current Javadocs and put = them there? I'll try to come up with application skeletons today, and with two draft = essays: on Spring web MVC vs Struts, and on resource/transaction = handling with focus on Hibernate. Can't guarantee that they will be = ready for tomorrow, though - but if they do, let's just put them on the = website. BTW, I've been discussing Spring's Hibernate handling on the Hibernate = forum, on the occasion that someone else started a thread on respective = issues there. I've been invited to put a basic outline and code samples = on Hibernate's Wiki, so I will try to reuse the respective essay for = both the Spring website and the Hibernate community area. Juergen -----Original Message----- From: Rod Johnson [mailto:rod...@in...] Sent: Monday, June 23, 2003 11:49 PM To: tri...@tr... Cc: spr...@li... Subject: Re: [Springframework-developer] Sample Application build process Thomas, I like this. The only issue is how to put in more functional navigation without cluttering it, as simplicity is part of its appeal. What does everyone else think? I'm no graphics expert. Regards, Rod ----- Original Message ----- From: <tri...@tr...> To: "j=C3=BCrgen h=C3=B6ller [werk3AT]" <jue...@we...> Cc: "Rod Johnson" <rod...@in...>; "Ken Krebs" = <kk...@kk...>; "spring-dev-list" <spr...@li...> Sent: Monday, June 23, 2003 10:40 PM Subject: Re: [Springframework-developer] Sample Application build = process > Juergen, Rod, Ken, All > > > > > BTW, Rod: We are running out of time in terms of getting a release = plus a > > proper website out on Wednesday. But we shouldn't delay it, a = release is > > _really_ important now. Unfortunately, a release with the current > > www.springframework.org website would leave a shallow first = impression, so I > > consider a nice-looking website important too. I'm not getting this straight > > currently. What do you suggest? > > > > I agree - whatever happened to the logo discussion? It just died = somehow. > Anyway, I did a quick rework of the current website - any suggestions = are > welcome (I'm not an expert web designer :-). If you want the password = for FTP > access let me know. > > Thomas > ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: <rod...@in...> - 2003-06-24 09:30:51
|
Thomas, the "News" section looks a bit small on my browser (1280x1024 on a 19" monitor with default IE font size). Good idea though! Regards, Rod |
|
From: <jue...@we...> - 2003-06-24 15:53:43
|
I've just added 4 web application skeletons to "samples/skeletons": - "webapp-minimal": DispatcherServlet + defaults + simple Controller; - "webapp-typical": Log4J configuration + Root context + DataSource + = transaction manager + data access object + business object + = DispatcherServlet + SimpleUrlHandlerMapping + ResourceBundleViewResolver = + simple Controller + SimpleFormController + MultiActionController; - "webapp-hibernate": Hibernate configuration + Root context + = SessionFactory + transaction manager + data access object + business = object; - "webapp-aop": Root context + DataSource + transaction manager + data = access object + transaction interceptor + business object. All of them are extensively documented, with various hints regarding = alternatives, including mentioning of container environments vs test = environments, etc. I believe that these skeletons can provide a good = starting point for Spring web projects, when additionally leveraging our = Javadocs for details. I expect many developers to benefit more from such = skeletons than from any classical step-by-step instructions. Regards, Juergen -----Original Message----- From: j=FCrgen h=F6ller [werk3AT]=20 Sent: Tuesday, June 24, 2003 9:35 AM To: Rod Johnson; tri...@tr... Cc: spr...@li... Subject: RE: [Springframework-developer] Sample Application build process Let's go for it for the moment, it looks nice enough. It doesn't leave a = shallow first impression, my main goal is reached :-) Thomas, can you update the PetClinic to the current CVS version, and add = the PagedList sample? Additional benefit: You would test the new build = processes of the current versions too ;-) Regarding future updates of = the samples: Let's try to avoid direct manipulation on the web servre, = instead keep as much as possible in CVS, and update the website from = there. I suggest to add a "Documentation" section between "Downloads" and = "Demo/Tutorial", providing a page with links to our Javadoc, and to = introductory essays. Thomas, can you generate current Javadocs and put = them there? I'll try to come up with application skeletons today, and with two draft = essays: on Spring web MVC vs Struts, and on resource/transaction = handling with focus on Hibernate. Can't guarantee that they will be = ready for tomorrow, though - but if they do, let's just put them on the = website. BTW, I've been discussing Spring's Hibernate handling on the Hibernate = forum, on the occasion that someone else started a thread on respective = issues there. I've been invited to put a basic outline and code samples = on Hibernate's Wiki, so I will try to reuse the respective essay for = both the Spring website and the Hibernate community area. Juergen -----Original Message----- From: Rod Johnson [mailto:rod...@in...] Sent: Monday, June 23, 2003 11:49 PM To: tri...@tr... Cc: spr...@li... Subject: Re: [Springframework-developer] Sample Application build process Thomas, I like this. The only issue is how to put in more functional navigation without cluttering it, as simplicity is part of its appeal. What does everyone else think? I'm no graphics expert. Regards, Rod ----- Original Message ----- From: <tri...@tr...> To: "j=C3=BCrgen h=C3=B6ller [werk3AT]" <jue...@we...> Cc: "Rod Johnson" <rod...@in...>; "Ken Krebs" = <kk...@kk...>; "spring-dev-list" <spr...@li...> Sent: Monday, June 23, 2003 10:40 PM Subject: Re: [Springframework-developer] Sample Application build = process > Juergen, Rod, Ken, All > > > > > BTW, Rod: We are running out of time in terms of getting a release = plus a > > proper website out on Wednesday. But we shouldn't delay it, a = release is > > _really_ important now. Unfortunately, a release with the current > > www.springframework.org website would leave a shallow first = impression, so I > > consider a nice-looking website important too. I'm not getting this straight > > currently. What do you suggest? > > > > I agree - whatever happened to the logo discussion? It just died = somehow. > Anyway, I did a quick rework of the current website - any suggestions = are > welcome (I'm not an expert web designer :-). If you want the password = for FTP > access let me know. > > Thomas > ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: <tri...@tr...> - 2003-06-24 16:57:20
|
Rod, All, What is the future plan for package names? Are we sticking with 'com.interface21'. A co-worker just commented on the javadoc, asking what is com.interface21 - he did not associate this name with Spring for some reason :-) Have you thought about this at all? To me it is not that important, but it could be down the road. When someone is looking at a piece of code that has some Spring imports, would it be confusing with the current package naming? Thomas P.S. The javadoc is on the website now. |
|
From: Ken K. <kk...@kk...> - 2003-06-24 17:36:22
|
"org.springframework" does seem more appropriate but if we change this it should be done IMO prior to the 1st official release to minimize trouble later. If we do it later, confusion will be in abundance and manually produced documentation will also have to be updated. Sounds like a lot of work to get it done in a short amount of time but better now than later. Have we set a time target for the actual production of the initial release distribution ??? Ken tri...@tr... wrote: >Rod, All, > >What is the future plan for package names? Are we sticking with >'com.interface21'. A co-worker just commented on the javadoc, asking what is >com.interface21 - he did not associate this name with Spring for some reason :-) > >Have you thought about this at all? To me it is not that important, but it >could be down the road. When someone is looking at a piece of code that has >some Spring imports, would it be confusing with the current package naming? > >Thomas > >P.S. The javadoc is on the website now. > > >------------------------------------------------------- >This SF.Net email is sponsored by: INetU >Attention Web Developers & Consultants: Become An INetU Hosting Partner. >Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! >INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > |
|
From: Rod J. <rod...@in...> - 2003-06-24 18:04:38
|
Thomas, All, My original plan was to keep interface21 for the following reasons: 1. to avoid confusion with the package names in the book. However, as Spring is now a lot more than the initial release with the book, that objection probably doesn't apply now. 2. in case anyone sued us over the name Spring. However, that may be a bit paranoid. So I don't have any strong feelings on the issue. It may be better to go springframework, especially as you've already reserved the domain. I guess it gives more credibility for a true open source project. I'm a bit reluctant to delay the release of 0.9 for this. So can we vote please on whether to: - stay as we are for the time being - migrate now - migrate for 1.0 If we're in favour of migrating, I'd probably say do it now, but it would probably blow away our release plans. If we do migrate I would really like to keep the revision history, without needing to navigate back to the old (deleted) file + package. This might mean renaming the directories in CVS (would need SF to do this, I think); we would probably need to do a global replace in the text. Anyone have a bright idea on this? At least with CVS it's easy enough to migrate directory names. Btw, Hibernate changed package names with release 2! Regards, Rod > What is the future plan for package names? Are we sticking with > 'com.interface21'. A co-worker just commented on the javadoc, asking what is > com.interface21 - he did not associate this name with Spring for some reason :-) > > Have you thought about this at all? To me it is not that important, but it > could be down the road. When someone is looking at a piece of code that has > some Spring imports, would it be confusing with the current package naming? |
|
From: Ken K. <kk...@kk...> - 2003-06-24 18:49:07
|
I vote to migrate for 1.0. We should add a warning in the production release notes and installation instructions. Sourceforge support does provide the capability to preserve the revision history when files or dirs need to be moved or renamed. Ken, Rod Johnson wrote: >Thomas, All, > >My original plan was to keep interface21 for the following reasons: > >1. to avoid confusion with the package names in the book. However, as Spring >is now a lot more than the initial release with the book, that objection >probably doesn't apply now. >2. in case anyone sued us over the name Spring. However, that may be a bit >paranoid. > >So I don't have any strong feelings on the issue. It may be better to go >springframework, especially as you've already reserved the domain. I guess >it gives more credibility for a true open source project. > >I'm a bit reluctant to delay the release of 0.9 for this. So can we vote >please on whether to: >- stay as we are for the time being >- migrate now >- migrate for 1.0 > >If we're in favour of migrating, I'd probably say do it now, but it would >probably blow away our release plans. > >If we do migrate I would really like to keep the revision history, without >needing to navigate back to the old (deleted) file + package. This might >mean renaming the directories in CVS (would need SF to do this, I think); we >would probably need to do a global replace in the text. Anyone have a bright >idea on this? At least with CVS it's easy enough to migrate directory names. > >Btw, Hibernate changed package names with release 2! > >Regards, >Rod > > > >>What is the future plan for package names? Are we sticking with >>'com.interface21'. A co-worker just commented on the javadoc, asking what >> >> >is > > >>com.interface21 - he did not associate this name with Spring for some >> >> >reason :-) > > >>Have you thought about this at all? To me it is not that important, but >> >> >it > > >>could be down the road. When someone is looking at a piece of code that >> >> >has > > >>some Spring imports, would it be confusing with the current package >> >> >naming? > > > > > >------------------------------------------------------- >This SF.Net email is sponsored by: INetU >Attention Web Developers & Consultants: Become An INetU Hosting Partner. >Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! >INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > |
|
From: <tri...@tr...> - 2003-06-23 21:40:39
|
Juergen, Rod, Ken, All > > BTW, Rod: We are running out of time in terms of getting a release plus a > proper website out on Wednesday. But we shouldn't delay it, a release is > _really_ important now. Unfortunately, a release with the current > www.springframework.org website would leave a shallow first impression, so I > consider a nice-looking website important too. I'm not getting this straight > currently. What do you suggest? > I agree - whatever happened to the logo discussion? It just died somehow. Anyway, I did a quick rework of the current website - any suggestions are welcome (I'm not an expert web designer :-). If you want the password for FTP access let me know. Thomas |
|
From: Rod J. <rod...@in...> - 2003-06-23 21:52:23
|
Thomas, I like this. The only issue is how to put in more functional navigation without cluttering it, as simplicity is part of its appeal. What does everyone else think? I'm no graphics expert. Regards, Rod ----- Original Message ----- From: <tri...@tr...> To: "jürgen höller [werk3AT]" <jue...@we...> Cc: "Rod Johnson" <rod...@in...>; "Ken Krebs" <kk...@kk...>; "spring-dev-list" <spr...@li...> Sent: Monday, June 23, 2003 10:40 PM Subject: Re: [Springframework-developer] Sample Application build process > Juergen, Rod, Ken, All > > > > > BTW, Rod: We are running out of time in terms of getting a release plus a > > proper website out on Wednesday. But we shouldn't delay it, a release is > > _really_ important now. Unfortunately, a release with the current > > www.springframework.org website would leave a shallow first impression, so I > > consider a nice-looking website important too. I'm not getting this straight > > currently. What do you suggest? > > > > I agree - whatever happened to the logo discussion? It just died somehow. > Anyway, I did a quick rework of the current website - any suggestions are > welcome (I'm not an expert web designer :-). If you want the password for FTP > access let me know. > > Thomas > |
|
From: Ken K. <kk...@kk...> - 2003-06-23 22:02:54
|
Thomas, You're doing just fine :-) . I would like to get the FTP access so I can update the Petclinic documentation. BTW, I see a lot of German messages on the wiki. Also there should be a link back to home from the wiki. Ken tri...@tr... wrote: >Juergen, Rod, Ken, All > > > >> >>BTW, Rod: We are running out of time in terms of getting a release plus a >>proper website out on Wednesday. But we shouldn't delay it, a release is >>_really_ important now. Unfortunately, a release with the current >>www.springframework.org website would leave a shallow first impression, so I >>consider a nice-looking website important too. I'm not getting this straight >>currently. What do you suggest? >> >> >> > >I agree - whatever happened to the logo discussion? It just died somehow. >Anyway, I did a quick rework of the current website - any suggestions are >welcome (I'm not an expert web designer :-). If you want the password for FTP >access let me know. > >Thomas > > > > |
|
From: Rod J. <rod...@in...> - 2003-06-24 07:03:30
|
> BTW, I see a lot of German messages on the wiki. Also there should be a > link back to home from the wiki. This is puzzling. When I accessed the Wiki from work yesterday there were lots of German link names and no real content. From home it's all English and has the content. I wonder if it's because at work I have EN GB locale and at home US? Or is it just random? Rod |
|
From: <tri...@tr...> - 2003-06-24 11:21:31
|
Rod, The Wiki's configuration file must have gotten wacked while I was starting and stopping the server trying to fix the connection pool. I could not figure out how to set it back to English, so I removed the version that that was out there (2.5 RC2) and installed the new release version 2.5. As soon as I pointed it to the directory with our content it was fine again. Thomas > > BTW, I see a lot of German messages on the wiki. Also there should be a > > link back to home from the wiki. > > This is puzzling. When I accessed the Wiki from work yesterday there were > lots of German link names and no real content. From home it's all English > and has the content. I wonder if it's because at work I have EN GB locale > and at home US? Or is it just random? > > Rod > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: INetU > Attention Web Developers & Consultants: Become An INetU Hosting Partner. > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
|
From: Ken K. <kk...@kk...> - 2003-06-23 21:52:30
|
It seems to me that the current process as Juergen describes it is the correct one. It makes sense to distribute the sample sources with the spring jars. I don't see any need to distribute war files as developers who are not just browsing are going to build them themselves. If they just want to see them in action and browse the accompanying tutorial documentation, we should have the samples running on the website. The fact that the samples are becoming part of the framework means they will need good tests that are run as part of any production release. Petclinic definitely needs work in this area. I agree that the website should be high priority. I won't say much about what's there because I see it is changing a lot right now, though it would be nice to see the themes sample deployed there. As for myself, I'm going stop tweaking Petclinic code for now and focus on tutorial text :-( . I think we at a bare minimum need design notes and installation/setup instructions for Wednesday. Ken jürgen höller [werk3AT] wrote: >Ken, Rod, > >To clarify the current build process: > >- Spring itself still has its own build.xml. The release distribution will not contain this but just the sources and prebuilt jars. No need for a release user to build the entire Spring framework - that's a misapprehension. > >- The samples have their own build.xml files, building the sample jars from the sources, and copying the respective Spring dist jars to their WEB-INF\lib. They do not require Spring's main build.xml but just its prebuilt jars and some of the third-party libs in the main lib directory. With the current layout, this works both with a Spring CVS snapshot and a release distribution. > >- So currently a release distribution contains prebuilt Spring jars but just the sources of the samples. Going in the "samples/petclinic" resp. "samples/pagedlist" directory and invoking "ant build" or "ant warfile" generates a deployable version, in any case with current Spring jars. > >- There are 2 main advantages to the current way: The samples will always be built with current Spring jars, and there's no triplication of Spring or third-party jars - thus the 5 MB download. > >- The alternative would be to prepackage the samples as wars. The disadvantages apply: triplicated Spring jars and third party libs that may be out of sync. That might still be an acceptable tradeoff for a release distribution: extra 2 MB for pregenerated wars of both samples. If a majority votes for it, fine - for a release. > >- In any case, I'd like to keep the current building from CVS as it is. Generating new Spring jars all the time and committing them to the samples' WEB-INF/lib directories is very unhandy. We're talking about the evolving framework here, with frequent changes to be expected. And CVS snapshot users have to be familar with Ant anyway. > >- Let's not forget that our current demos aren't particularly convincing in terms of UI appearance. Their value is in their sources and their configuration, to learn typical Spring patterns. In my view, deploying them is not their primary purpose, thus worth an extra step. > >Of course, I'm open for changes to the build process. It's just that we haven't much time left before the TSS Symposium, so we should hurry a bit. > >BTW, Rod: We are running out of time in terms of getting a release plus a proper website out on Wednesday. But we shouldn't delay it, a release is _really_ important now. Unfortunately, a release with the current www.springframework.org website would leave a shallow first impression, so I consider a nice-looking website important too. I'm not getting this straight currently. What do you suggest? > >Regards, >Juergen > > > > -----Ursprüngliche Nachricht----- > Von: Rod Johnson [mailto:rod...@in...] > Gesendet: Mo 23.06.2003 21:34 > An: Ken Krebs; jürgen höller [werk3AT] > Cc: 'spring-dev-list' > Betreff: Re: [Springframework-developer] Sample Application build process > > > > I agree with Ken. > > It should be *possible*, but not necessary, to download and build all of > Spring with the demos. It should be easy to get started with a minimum of > fuss. > > Regards, > Rod > > ----- Original Message ----- > From: "Ken Krebs" <kk...@kk...> > To: "jürgen höller [werk3AT]" <jue...@we...> > Cc: "'spring-dev-list'" <spr...@li...> > Sent: Monday, June 23, 2003 7:26 PM > Subject: [Springframework-developer] Sample Application build process > > > > Juergen, > > > > The changes you made to the Petclinic build files have raised an > > interesting issue which applies to all sample programs: > > > > The changes made now require a user of the sample app to download and > > build the entire Spring framework. It was specifically my intent with > > Petclinic to not require this. I had envisioned a separately > > downloadable distribution of the sample. Many if not most developers are > > just going to want to use the framework runtime jars, at least at first > > when they're taking it out for a test drive. > > > > The prjzip ant target is only needed to create a distribution so it > > probably be in a separate file which will not be included in the > > distribution. This prjzip target will need to grab a current snapshot of > > the libs for inclusion in the distribution. I haven't quite worked out > > the best way to implement this yet. > > > > What are your thoughts on this ? > > > > Regards, > > > > Ken > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: INetU > > Attention Web Developers & Consultants: Become An INetU Hosting Partner. > > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! > > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php > > _______________________________________________ > > Springframework-developer mailing list > > Spr...@li... > > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > > > >?????????????????????????????????????????Ó+?^?éX???'???u?? ×P mz{b?u?l7?zZ)z????[Z????(??' ×Pz,?)?=????E?Þ¬7??ÆyÔ???1?Ú??zoØ¢á·]?2??\??i??Ȩ??z?yØj×1?Ú?G??b?m???? 0?)Þ¶??z??j?gz??×±??i???????????????????????????????????Ò¦????Ú?(?O?z�?????x%??R?????Ú?(?O?z�??X??????y?+???z?m?????b??????q?????Á¿?+-??b?ا~?즸???Ú?(?O?z�? > > > > |
