You can subscribe to this list here.
| 2003 |
Jan
|
Feb
(55) |
Mar
(100) |
Apr
(203) |
May
(330) |
Jun
(190) |
Jul
(302) |
Aug
(323) |
Sep
(197) |
Oct
(245) |
Nov
(490) |
Dec
(330) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(194) |
Feb
(400) |
Mar
(416) |
Apr
(415) |
May
(359) |
Jun
(381) |
Jul
(491) |
Aug
(311) |
Sep
(291) |
Oct
(273) |
Nov
(355) |
Dec
(266) |
| 2005 |
Jan
(306) |
Feb
(303) |
Mar
(520) |
Apr
(346) |
May
(255) |
Jun
(221) |
Jul
(171) |
Aug
(247) |
Sep
(147) |
Oct
(125) |
Nov
(165) |
Dec
(65) |
| 2006 |
Jan
(90) |
Feb
(53) |
Mar
(121) |
Apr
(103) |
May
(113) |
Jun
(103) |
Jul
(104) |
Aug
(67) |
Sep
(78) |
Oct
(82) |
Nov
(78) |
Dec
(70) |
| 2007 |
Jan
(77) |
Feb
(76) |
Mar
(63) |
Apr
(30) |
May
(47) |
Jun
(41) |
Jul
(44) |
Aug
(44) |
Sep
(49) |
Oct
(33) |
Nov
(25) |
Dec
(21) |
| 2008 |
Jan
(45) |
Feb
(13) |
Mar
(15) |
Apr
(12) |
May
(9) |
Jun
(33) |
Jul
(30) |
Aug
(7) |
Sep
(20) |
Oct
(17) |
Nov
(20) |
Dec
(10) |
| 2009 |
Jan
(8) |
Feb
(5) |
Mar
(12) |
Apr
(17) |
May
(19) |
Jun
(97) |
Jul
(77) |
Aug
(33) |
Sep
(24) |
Oct
(41) |
Nov
(16) |
Dec
(32) |
| 2010 |
Jan
(24) |
Feb
(14) |
Mar
(50) |
Apr
(71) |
May
(70) |
Jun
(64) |
Jul
(45) |
Aug
(62) |
Sep
(32) |
Oct
(4) |
Nov
(12) |
Dec
(2) |
| 2011 |
Jan
(1) |
Feb
(3) |
Mar
(4) |
Apr
(3) |
May
(6) |
Jun
(1) |
Jul
(4) |
Aug
(3) |
Sep
(4) |
Oct
(6) |
Nov
(3) |
Dec
(3) |
| 2012 |
Jan
(4) |
Feb
(8) |
Mar
(6) |
Apr
(10) |
May
(2) |
Jun
(3) |
Jul
(11) |
Aug
(10) |
Sep
(4) |
Oct
|
Nov
(1) |
Dec
(1) |
| 2013 |
Jan
(4) |
Feb
(1) |
Mar
(9) |
Apr
(1) |
May
(8) |
Jun
(2) |
Jul
(5) |
Aug
(2) |
Sep
|
Oct
(3) |
Nov
(10) |
Dec
(8) |
| 2014 |
Jan
(3) |
Feb
(12) |
Mar
(9) |
Apr
(12) |
May
(2) |
Jun
|
Jul
(3) |
Aug
(1) |
Sep
(1) |
Oct
(4) |
Nov
|
Dec
(2) |
| 2015 |
Jan
(1) |
Feb
(3) |
Mar
(4) |
Apr
(9) |
May
(2) |
Jun
(2) |
Jul
|
Aug
(2) |
Sep
(7) |
Oct
(9) |
Nov
(7) |
Dec
(9) |
| 2016 |
Jan
(7) |
Feb
(5) |
Mar
(5) |
Apr
(5) |
May
(8) |
Jun
(4) |
Jul
(5) |
Aug
(4) |
Sep
(6) |
Oct
(7) |
Nov
(2) |
Dec
(3) |
| 2017 |
Jan
(7) |
Feb
(8) |
Mar
(7) |
Apr
(3) |
May
(4) |
Jun
(3) |
Jul
(5) |
Aug
(8) |
Sep
(4) |
Oct
(2) |
Nov
(3) |
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2019 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2021 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
(5) |
Sep
(2) |
Oct
|
Nov
|
Dec
(1) |
| 2026 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <tri...@tr...> - 2003-05-20 05:21:13
|
To All,
I went back to modify Ken's demo app to use Jürgen's JndiDataSourceBean and to
run with the latest version of the framework code from CVS.
Again, I had to make just a few changes, but this time I did not touch any of
Ken's original Java code. I only modified three of the deployment xml files.
This really shows how valuable a well designed framework is.
These are the changes I made to the original code from Ken's Petclinic1.zip
(Steps 2, 3 and 6 are the same as last time):
1. Removed the <servlet> entry for ContextLoaderServlet from web.xml. This
class has recently been removed from CVS. Replaced it with a <listener> entry.
<listener>
<listener-class>com.interface21.web.context.ContextLoaderListener</listener-class>
</listener>
2. Added a 'resource-ref' entry to web.xml. It goes at the end after
the <taglib> entries.
<resource-ref>
<description>The default DS</description>
<res-ref-name>jdbc/SpringDS</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
3. Created a jboss-web.xml file with the corresponding 'resource-ref'
entry pointing to the HSQL default datasource.
<jboss-web>
<resource-ref>
<res-ref-name>jdbc/SpringDS</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<jndi-name>java:/DefaultDS</jndi-name>
</resource-ref>
</jboss-web>
4. Changed the "bean" entry for "dataSource" in the
applicationContext.xml - it now uses the new JndiDataSourceBean.
<beans>
<!-- ===========================================================-->
<!-- Global Message source. For all servlets. -->
<!-- ===========================================================-->
<bean name="messageSource"
class="com.interface21.context.support.ResourceBundleMessageSource">
<property name="basename">messages</property>
</bean>
<bean name="dataSource"
class="com.interface21.jdbc.datasource.JndiDataSourceBean" >
<property name="name">jdbc/SpringDS</property>
</bean>
</beans>
5. Replaced the WEB-INF/lib/spring-full-0.8.jar with the latest version.
6. Created a "petclinic.war" directory under the
"c:\jboss-3.2.1\server\default\deploy" directory and deployed the application there.
That's it for this time.
I have attached a zip file with the changed xml files.
--Thomas
|
|
From: <tri...@tr...> - 2003-05-19 21:04:40
|
For publicity, maybe we could write an article or two for O'Reilly's OnJava.com. They also have an Open Source Directory http://www.onjava.com/pub/q/java_os_directory where we should be listed. --Thomas > We also need a proper publicity campaign for our first release: posting to > TSS and any other forums (application-servers.com etc.); word-of-mouth to > colleagues, email signatures... This is very important: a lot of good > technologies don't get adopted because people don't hear of them. Ideas > welcome. |
|
From: Rod J. <rod...@in...> - 2003-05-19 16:55:22
|
I've removed the Attrib4j dependency until source-level attribute support is implemented properly. |
|
From: Rod J. <rod...@in...> - 2003-05-19 16:48:38
|
I forgot: for 1.0 I want to decide what to do about source-level metadata attributes (Attrib4j/whatever) and have a working solution, with examples. Rod |
|
From: Rod J. <rod...@in...> - 2003-05-19 16:47:04
|
I think we're approaching the point where we need a feature freeze for 0.8. And even for 0.9 and 1.0 I don't think we should be adding a lot more features. I think Spring has a lot in it already: people will be more likely to be irritated by bugs than disappointed about what it doesn't yet do. Working backwards from 1.0 I see the additions being as follows (divided into essential, desirable, nice to have): 0.9/1.0 - JDO support (desirable) - SOAP remoting (essential) - Mature JMS support with proper tests (desirable) - ResultSets from StoredProcedure (essential) 0.8 - Documentation - Website - All bugs in SF addressed - RJ to remove Attrib4j dependency until I've decided to make it ahead properly. (I'll try to do this now.) I'm sure I've missed some things... Juergen, I partly based this on your suggestions, does this sound OK to you? Basically, I think we are just about there for 0.8, codewise. I think we need to set a target date (perhaps the end of this week?) to do a CVS tag and build distribution units. In the meantime, we have to deploy all our apps etc, to make sure we have broken anything. We also need a proper publicity campaign for our first release: posting to TSS and any other forums (application-servers.com etc.); word-of-mouth to colleagues, email signatures... This is very important: a lot of good technologies don't get adopted because people don't hear of them. Ideas welcome. Regards, Rod > Hi everyone, > > What features are we missing for 0.8, .09 and 1.0? It would help having an idea of what remains to be done by when. I also suggest we give ourselves some target dates (soft deadlines) in order to avoid slippage as much as possible. If Rod could propose dates and features, then every member could respond with "possible" or "impossible" as far as he/she is concerned. > Personally, I hope to have the web and JNDI chapters done next week. Next on the list is EJB. Then AOP and transactions, which I'm afraid are going to take me some time to do as I have to figure out the code first and do some background reading. And ditto for the ORM stuff. What features are absolutely necessary for the different releases? > I also feel that the website is a major priority, even if it's a first draft. And we need to get the download sections and docs sections on the sourceforge site set up. The sf site is our public face right now, and sorry to say it doesn't look like much. > > Isabelle > > -- > Isabelle Muszynski > Software Engineer > Zandweellaan 4 > 2660 Antwerpen > Belgium > Tel. 32-(0)3-830 18 54 > Mobile: 32-(0)485 49 50 89 > Email: isa...@me... > Website: www.meta-logix.com > > > ------------------------------------------------------- > This SF.net email is sponsored by: If flattening out C++ or Java > code to make your application fit in a relational database is painful, > don't do it! Check out ObjectStore. Now part of Progress Software. > http://www.objectstore.net/sourceforge > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
|
From: Rod J. <rod...@in...> - 2003-05-19 15:54:01
|
Guys, A few more changes to get rid of deprecated classes/usage before 0.8 - I've removed DynamicProxy (better to use an AOP ProxyFactory with an anonymous inner class for pre/post processing). This is very easy. - I've replaced the classes in the ejb.access package with classes using AOP underneath. They're very similar to use, but they're factory beans, not custom bean definitions. All you need to do is replace your custom bean definition syntax in the XML with an ordinary bean definition, the class being the corresponding FactoryBean in the ejb.access package. This approach is no longer XML-only: you can use it with a properties file (or any other) bean factory as well. - XmlBeanFactory no longer uses "custom bean definitions". The new FactoryBean approach is simpler and cleaner. - AbstractBeanDefinition is now internal, so I've made it package-visible. Apologies if this is a pain if you're using CustomBeanDefinitions, but I'm sure you'll find the FactoryBean approach simpler and more elegant. And I didn't want there to be a confusing set of alternatives when we release. Regards, Rod |
|
From: Travis C. <tra...@le...> - 2003-05-19 15:51:05
|
I will start on a prototype of the website this week. I will just chose = a logo to go with for now and hopefully make it easy to change the color = scheme, etc. to match whatever logo the group chooses. I think though = we should pick the logo soon as we can start incorporating on all = documentation, tutorials, etc. This will also allow Rod to have a very = visible spring presence at the TSS conference (which is very important, = we need to give developers a graphic that they can associate mentally = with Spring and make it stand out as something they should check out). Any thoughts? -thanks Travis -----Original Message----- From: Isabelle Muszynski [mailto:isa...@me...] Sent: Saturday, May 17, 2003 4:46 AM To: spr...@li... Subject: [Springframework-developer] release plan Hi everyone, What features are we missing for 0.8, .09 and 1.0? It would help having = an idea of what remains to be done by when. I also suggest we give = ourselves some target dates (soft deadlines) in order to avoid slippage = as much as possible. If Rod could propose dates and features, then every = member could respond with "possible" or "impossible" as far as he/she is = concerned.=20 Personally, I hope to have the web and JNDI chapters done next week. = Next on the list is EJB. Then AOP and transactions, which I'm afraid are = going to take me some time to do as I have to figure out the code first = and do some background reading. And ditto for the ORM stuff. What = features are absolutely necessary for the different releases? I also feel that the website is a major priority, even if it's a first = draft. And we need to get the download sections and docs sections on the = sourceforge site set up. The sf site is our public face right now, and = sorry to say it doesn't look like much. Isabelle --=20 Isabelle Muszynski Software Engineer Zandweellaan 4 2660 Antwerpen Belgium Tel. 32-(0)3-830 18 54 Mobile: 32-(0)485 49 50 89 Email: isa...@me... Website: www.meta-logix.com ------------------------------------------------------- This SF.net email is sponsored by: If flattening out C++ or Java code to make your application fit in a relational database is painful,=20 don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Rod J. <rod...@in...> - 2003-05-19 15:32:00
|
All,
You may have seen the recent changes making JndiServices (formerly static)
an object called JndiTemplate. This is consistent with other templates, and
much better for testing. (Statics are the enemy of unit testing.)
Although you won't have noticed unless you've tried to do anything fancy
with JNDI, this means that a number of classes now expose JndiTemplate bean
properties. The default is new InitialContext() behaviour, as you'd expect.
However, it's now possible to use separate JNDI environments for different
beans: e.g. EJB proxies that access different remote servers.
I've made this easier to configure by adding a JndiTemplate property editor.
Thus you should be able to do this for any bean that uses a JndiTemplate:
<property name="jndiTemplate">
myJndiEnvironmentProperty1=whatever
allTheStandardOrVendorSpecificKeys=values
</property>
Rregards,
Rod
|
|
From: Luke T. <luk...@fr...> - 2003-05-19 15:27:00
|
Isabelle Muszynski wrote: > Hi Thomas, > > I got Ken's demo working in Jboss using your changes. However, there > is one thing I don't understand. In jboss-web, the JNDI name is > java:/DefauldDS. So why is the datasource lookup done using > jdbc/SpringDS? The way you do it in Weblogic is that whatever JNDI > name you specify, that's waht you use for the lookup. > > Isabelle > It's a standard J2EE thing - jdbc/SpringDS is the container-independent name you use in your code to provide a layer of indirection, and you map it to an actual named container resource (in the JBoss case by supplying a jboss-web file). You can do the same in Weblogic: http://edocs.bea.com/wls/docs60/programming/web_xml.html#1017834 An explicit lookup would work too but would require code changes every time you change to use a different "physical" datasource or if you move to a different container. There's an equivalent syntax for use in EJBs, in the ejb-jar.xml file. Luke. -- Luke Taylor. Monkey Machine Ltd. PGP Key ID: 0x57E9523C http://www.monkeymachine.ltd.uk |
|
From: Ken K. <kk...@kk...> - 2003-05-19 14:37:57
|
Isabelle, I don't see any update methods in SqlUpdate that take a KeyBinder. Ken Isabelle Muszynski wrote: >Hi Ken, > >It's all hidden under update. There are some new update methods that take a KeyBinder, those are the ones that use key auto-generation and return you the value of the generated key. >For an insert without auto key generation, you can just use the update, passing it an INSERT INTO ... > > >Isabelle > >On Mon, May 19, 2003 at 09:01:29AM -0500, Ken Krebs wrote: > > >>Isabelle, >> >>Is there any high level (com.interface21.jdbc.object) support for Insert >>functionality ??? >> >>I've seen some comments about it being incorporated while browsing the >>CVS for SqlUpdate rev 1.4 and SqlOperation rev 1.4 but I see no actual >>differences supporting it. >> >>Is this planned for later ? >> >>Ken >> >> >> >> >> >> > > > |
|
From: Isabelle M. <isa...@me...> - 2003-05-19 14:16:58
|
Hi Ken, It's all hidden under update. There are some new update methods that take a KeyBinder, those are the ones that use key auto-generation and return you the value of the generated key. For an insert without auto key generation, you can just use the update, passing it an INSERT INTO ... Isabelle On Mon, May 19, 2003 at 09:01:29AM -0500, Ken Krebs wrote: > Isabelle, > > Is there any high level (com.interface21.jdbc.object) support for Insert > functionality ??? > > I've seen some comments about it being incorporated while browsing the > CVS for SqlUpdate rev 1.4 and SqlOperation rev 1.4 but I see no actual > differences supporting it. > > Is this planned for later ? > > Ken > > > > -- Isabelle Muszynski Software Engineer Zandweellaan 4 2660 Antwerpen Belgium Tel. 32-(0)3-830 18 54 Mobile: 32-(0)485 49 50 89 Email: isa...@me... Website: www.meta-logix.com |
|
From: Ken K. <kk...@kk...> - 2003-05-19 14:06:38
|
Isabelle, Is there any high level (com.interface21.jdbc.object) support for Insert functionality ??? I've seen some comments about it being incorporated while browsing the CVS for SqlUpdate rev 1.4 and SqlOperation rev 1.4 but I see no actual differences supporting it. Is this planned for later ? Ken |
|
From: Isabelle M. <isa...@me...> - 2003-05-19 13:37:55
|
Hi Thomas, I got Ken's demo working in Jboss using your changes. However, there is one thing I don't understand. In jboss-web, the JNDI name is java:/DefauldDS. So why is the datasource lookup done using jdbc/SpringDS? The way you do it in Weblogic is that whatever JNDI name you specify, that's waht you use for the lookup. Isabelle -- Isabelle Muszynski Software Engineer Zandweellaan 4 2660 Antwerpen Belgium Tel. 32-(0)3-830 18 54 Mobile: 32-(0)485 49 50 89 Email: isa...@me... Website: www.meta-logix.com |
|
From: Ken K. <kk...@kk...> - 2003-05-19 13:16:14
|
Juergen, I'll incorporate your suggestions into what I'm doing. Thanks for the heads up on the JndiDataSourceBean. Ken jürgen höller [werk3AT] wrote: >Ken, Isabelle, > >First of all, thanks for your efforts - they're very welcome :-) > >Some quick remarks after a brief look at the code (and also the web tutorial): > >- You don't need to specify the contextClass param for ContextLoaderServlet, as XmlWebApplicationContext is the default. > >- Let's omit the debug param declaration for ControllerServlet, it's rather confusing. > >- UrlHandlerMapping aren't sorted by bean name anymore but can specify an "order" value, so let's use a nicer name than "a.urlMap". > >- We should show Log4J web configuration too, i.e. starting Log4jConfigServlet with a lower startup number than ContextLoaderServlet, and using some webAppRootKey like "petclinic.root" in log4j.properties (see Log4jConfigServlet). > >- Separating the DataSource configuration as separate bean is fine, but are you aware that MysqlConnectionPoolDataSource is just a pool-supporting DataSource that doesn't pool itself (like with any JDBC driver)? Let's use a correctly pooling container datasource, configured in Spring as JndiDataSourceBean with name "jdbc/petdb" or the like. Of course, a non-pooling DataSource can be used in a test or standalone environment without drawbacks. > >I'm also keen on both transaction support and Hibernate support in a higher-end version of the demo. > >Regards, >Juergen > > > > -----Ursprüngliche Nachricht----- > Von: Rod Johnson [mailto:rod...@in...] > Gesendet: Do 15.05.2003 10:38 > An: Ken Krebs; Isabelle Muszynski; jürgen höller [werk3AT] > Cc: 'spring-dev-list' > Betreff: Re: Petclinic demo app prototype > > > > Thanks Ken. This looks like a nice example. The fact that the code is so > simple tends to show that Spring does what it claims! > > It would be good to use the JdbcTemplate at least once for a query / update. > This is an important part of the API. > > "Stage D & later" - ???, suggestions wanted; JNDI, internationalization > support, support for reference data in AbstractFormController, > AbstractWizardFormController, simple transactions, non-JSP views, > authentication/authorization, fancier display pages possibly with a > header/footer/menu and maybe a stylesheet, etc. > > Transaction support: we'd need to come up with a requirement, and show the > TransactionTemplate and the AOP declarative approach. I have an example of > the declarative approach, which I'll send when I'm accessing the net over > something faster than my mobile phone. > > A Hibernate version of the present demo might be interesting to do later, as > well, showing the new Hibernate integration. > > Regards, > Rod > > > > ----- Original Message ----- > From: "Ken Krebs" <kk...@kk...> > To: "Isabelle Muszynski" <isa...@me...>; "jürgen höller > [werk3AT]" <jue...@we...>; "Rod Johnson" > <rod...@in...> > Cc: "'spring-dev-list'" <spr...@li...> > Sent: Thursday, May 15, 2003 3:29 AM > Subject: Petclinic demo app prototype > > > > To All, > > > > I am pleased to announce that I now have ready for download a PROTOTYPE > > of the Petclinic demo app > > <http://www.globaldialog.com/%7Ekkrebs/files/Petclinic1.zip>, approx. > > 1.25MB. > > > > Be sure to read the file, petclinic.txt. This file contains my notes > > about the design and implementation and also raises key issues that need > > to be resolved. > > > > I very much welcome all comments, suggestions, ideas, and criticisms. I > > look forward to hearing from you. > > > > Ken > > > > > > >?????????????????????????????????????????Ä׫???x???h?é¢wÞ??{?1??ɺw?????M?I??h)Z???z????Þ?^v'??m?+,??+zV?y?h.)????z?k?Ǭ?[??????z{^????b??_?????&???????????????????????????????????Ò¦????Ú?(?O?z�?????x%??R?????Ú?(?O?z�??X??????y?+???z?m?????b??????q?????Á¿?+-??b?ا~?즸???Ú?(?O?z�? > > > > |
|
From: Ken K. <kk...@kk...> - 2003-05-19 13:02:08
|
Oops, forgot to copy to list.
Ken
Thomas,
Thanks for the HSQL/JBoss stuff. I think it's advantageous for the
demo-app to support Mysql/Hsql/Tomcat/Jboss in the first version.
Has anybody done any work on supporting the JDBC Insert functionality
for HSQL ???
I intend to add use cases that need the JDBC Insert functionality in the
first version of the demo-app.
Ken
Thomas Risberg wrote:
>Ken,
>
>I got the app running on JBoss. Had to make a few changes:
>
>1. Changed the petclinic\support\ClinicImpl.java class to do a JNDI
>lookup in the afterPropertiesSet() method. Also added an import
>statement for DataSourceUtils.
>
>import com.interface21.jdbc.datasource.DataSourceUtils;
>
> public void afterPropertiesSet() throws java.lang.Exception {
> dataSource = DataSourceUtils.getDataSourceFromJndi
>("jdbc/SpringDS");
> //if(dataSource == null) {
> // throw new ApplicationContextException("Must set
>dataSource bean property on " + getClass());
> //}
>
>
>2. Added a 'resource-ref' entry to web.xml. It goes at the end after
>the <taglib> entries.
>
> <resource-ref>
> <description>The default DS</description>
> <res-ref-name>jdbc/SpringDS</res-ref-name>
> <res-type>javax.sql.DataSource</res-type>
> <res-auth>Container</res-auth>
> </resource-ref>
>
>3. Created a jboss-web.xml file with the corresponding 'resource-ref'
>entry pointing to the HSQL default datasource.
>
><jboss-web>
> <resource-ref>
> <res-ref-name>jdbc/SpringDS</res-ref-name>
> <res-type>javax.sql.DataSource</res-type>
> <jndi-name>java:/DefaultDS</jndi-name>
> </resource-ref>
></jboss-web>
>
>4. Commented out the "bean" entry for "dataSource" in the
>applicationContext.xml - this is not needed since we do a JNDI lookup
>for the datasource.
>
><beans>
>
> <!-- ===========================================================-->
> <!-- Global Message source. For all servlets.
> -->
> <!-- ===========================================================-->
> <bean name="messageSource"
>class="com.interface21.context.support.ResourceBundleMessageSource">
>
> <property name="basename">messages</property>
>
> </bean>
>
> <!--
> <bean name="dataSource"
>class="com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource" >
> <property name="URL">jdbc:mysql://localhost/petclinic</property>
> <property name="user">pc</property>
> <property name="password">pc</property>
> </bean>
> -->
>
></beans>
>
>
>5. Commented out the corresponding "property" entry for "dataSource"
>under the "clinic" bean entry in "petclinic-servlet.xml".
>
> <bean name="clinic" class="petclinic.support.ClinicImpl" >
> <!--<property name="dataSource"
>beanRef="true">dataSource</property> -->
> </bean>
>
>6. Created a "petclinic.war" directory under the "c:\jboss-3.2.1
>\server\default\deploy" directory and deployed the application there.
>
>That's it - it works like a charm. You can view all the Log4j
>messages in "c:\jboss-3.2.1\server\default\log\server.log". I have
>attached a zip file with the changed code.
>
>
>--Thomas
>
>
>
>
>>To All,
>>
>>I am pleased to announce that I now have ready for download a
>>
>>
>PROTOTYPE
>
>
>>of the Petclinic demo app
>><http://www.globaldialog.com/%7Ekkrebs/files/Petclinic1.zip>,
>>
>>
>approx.
>
>
>>1.25MB.
>>
>>Be sure to read the file, petclinic.txt. This file contains my notes
>>about the design and implementation and also raises key issues that
>>
>>
>need
>
>
>>to be resolved.
>>
>>I very much welcome all comments, suggestions, ideas, and
>>
>>
>criticisms. I
>
>
>>look forward to hearing from you.
>>
>>Ken
>>
>>
>>
>>
>
>
>
|
|
From: Ken K. <kk...@kk...> - 2003-05-19 12:47:31
|
Isabelle, What you have described sounds like a good plan to me. I definitely want to separate the persistence stuff from the business layer, it's just a matter of when and where in the staging. It looks like I have enough feedback now to complete Version 1 and break it down into stages. As for the demo-app accompanying text, I'll probably start fleshing it out in an outline form. Ken Isabelle Muszynski wrote: >Hi everyone, > >I've been thinking about how to coordinate Ken's and my efforts to avoid unnecessary duplication. I'm basically showing bits and pieces, and intend to cover all packages. What I don't intend to do is to show how to put it all together and get a real application out. >So it seems to me this is where Ken comes in. >I'm currently working on the UML model of the web stuff, which forces me to study the sources. Once that's done, I will expand the web trail of the tutorial a bit more (for ex. validators). Then it's on to JNDI. By the way, Ken, I have a datasource definition for MySQL and Tomcat, I'm attaching it to this mail. >My suggestion for the web demo is : > >(1) Describe the use cases that will be handled in the demo. If Ken sends me a text description, I can generate a use case diagram and send him back a jpeg. Mybe also indicate which use cases will be implemented in a later version of the demo. >(2) Do the business model (which you already have), but I would separate out the persistence stuff. >(3) Do the data access layer. > >Note that up to now there is nothing web-related. > >(4) Explain the flow of the pages which leads you to explain how you set up your controllers. We are now starting the web stuff. You could do this use case by use case, so the users can follow your logic. > >(5) Code the views. > >What do you think? > >Isabelle > > > > > |
|
From: Ken K. <kk...@kk...> - 2003-05-19 12:20:39
|
Rod, I'll show a JdbcTemplate example in the code. I look forward to seeing your transaction samples. Ken Rod Johnson wrote: >Thanks Ken. This looks like a nice example. The fact that the code is so >simple tends to show that Spring does what it claims! > >It would be good to use the JdbcTemplate at least once for a query / update. >This is an important part of the API. > >"Stage D & later" - ???, suggestions wanted; JNDI, internationalization >support, support for reference data in AbstractFormController, >AbstractWizardFormController, simple transactions, non-JSP views, >authentication/authorization, fancier display pages possibly with a >header/footer/menu and maybe a stylesheet, etc. > >Transaction support: we'd need to come up with a requirement, and show the >TransactionTemplate and the AOP declarative approach. I have an example of >the declarative approach, which I'll send when I'm accessing the net over >something faster than my mobile phone. > >A Hibernate version of the present demo might be interesting to do later, as >well, showing the new Hibernate integration. > >Regards, >Rod > > > >----- Original Message ----- >From: "Ken Krebs" <kk...@kk...> >To: "Isabelle Muszynski" <isa...@me...>; "jürgen höller >[werk3AT]" <jue...@we...>; "Rod Johnson" ><rod...@in...> >Cc: "'spring-dev-list'" <spr...@li...> >Sent: Thursday, May 15, 2003 3:29 AM >Subject: Petclinic demo app prototype > > > > >>To All, >> >>I am pleased to announce that I now have ready for download a PROTOTYPE >>of the Petclinic demo app >><http://www.globaldialog.com/%7Ekkrebs/files/Petclinic1.zip>, approx. >>1.25MB. >> >>Be sure to read the file, petclinic.txt. This file contains my notes >>about the design and implementation and also raises key issues that need >>to be resolved. >> >>I very much welcome all comments, suggestions, ideas, and criticisms. I >>look forward to hearing from you. >> >>Ken >> >> >> > > > > >------------------------------------------------------- >Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara >The only event dedicated to issues related to Linux enterprise solutions >www.enterpriselinuxforum.com > >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > |
|
From: Isabelle M. <isa...@me...> - 2003-05-19 09:52:25
|
New versions on my web site. UML : added web stuff tutorial : incorporated Juergen's changes and added some UML diagrams to the web chapters. Isabelle -- Isabelle Muszynski Software Engineer Zandweellaan 4 2660 Antwerpen Belgium Tel. 32-(0)3-830 18 54 Mobile: 32-(0)485 49 50 89 Email: isa...@me... Website: www.meta-logix.com |
|
From: Rod J. <rod...@in...> - 2003-05-19 08:03:48
|
>Rod's book may become unavailable Fortunately not. Wiley have taken over the Wrox brand the best selling Wrox books, including mine. So Expert 1:1 will definitely stay in print. There are currently some delays while it's being reprinted, but it should be back on any shelves it's disappeared from very soon. A manual sounds like a good idea. I'll try to check out the Struts user guide and any other possible examples. Rod ----- Original Message ----- From: "Isabelle Muszynski" <isa...@me...> To: <spr...@li...> Sent: Saturday, May 17, 2003 11:11 AM Subject: [Springframework-developer] documentation > Hi everyone, > > I agree with Jean-Pierre that poor documentation is a stumbling block for potential users of the framework. Rod's book may become unavailable, and on top of that the framework has evolved quite a bit with respect to what's described in the book. I feel that, on top of the tutorial and the demo, we also need a manual. The Struts user guide is a nice example. I'm willing to take on the job, but it isn't going to get done by june for sure :-(. The tutorial takes precedence. > > What are your thoughts? > > Isabelle > > -- > Isabelle Muszynski > Software Engineer > Zandweellaan 4 > 2660 Antwerpen > Belgium > Tel. 32-(0)3-830 18 54 > Mobile: 32-(0)485 49 50 89 > Email: isa...@me... > Website: www.meta-logix.com > > > ------------------------------------------------------- > This SF.net email is sponsored by: If flattening out C++ or Java > code to make your application fit in a relational database is painful, > don't do it! Check out ObjectStore. Now part of Progress Software. > http://www.objectstore.net/sourceforge > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
|
From: Isabelle M. <isa...@me...> - 2003-05-19 06:46:17
|
Hello Kees, In the current framework, you indeed should use update for inserts. And the special overloaded forms of update with a KeyBinder argument for the key generation. Isabelle On Sun, May 18, 2003 at 11:16:18AM +0200, kees jan voogd wrote: > Hi Isabelle, > > > For what it's worth I agree with you. You just can't put everything in > stored procedures. Omission of inserts from the framework was a mistake and > an omission in an ohterwise very readable book. > > For your solotion I would not look into pk (or guid) generation right away. > This is just a part of the inserts. And a very nasty issue one at that too. > > I've been using the JdbcTemplate's update methods for inserts. The only iffy > thing there is that the method call is update instead of insert (logged as > update aswell). A change there would be sufficient (imho). > > As for pk generation i've been using the select SEQ.nextval from dual bit. I > built numbergeneratator class doing these selects. (based on just table name > SEQ_PK_table and SEQ_table_colum for other sequences). > > Complete integration of pk generatation into the framwork would provide > quite a lot of problems (more then they would solve ??). > > > > anyway, > > > > Goodluck ! > > > > KJ > > > > > > > > "Isabelle Muszynski" <isa...@me...> wrote in message > news:<200...@lu...>... > > Will have a look at how we could best incorporate insert functionality and > will get back to you. > > > > Isabelle > > > > > > On Wed, Apr 16, 2003 at 02:10:56PM +0100, Rod Johnson wrote: > > > Isabelle, > > > > > > You make a valid point about not wanting to need another product for > just > > > one problem. > > > > > > My view is that > > > - we don't want to get into full-blown O/R mapping > > > - BUT there is scope in building more JDBC-based functionality and > > > abstractions on top of the Spring JDBC way of doing things. To my mind > the > > > central value proposition of Spring JDBC is the exception hierarchy and > way > > > it frees developers of the tedious and error-prone tasks of raw JDBC. > > > Additional features can validly be layered on top. > > > > > > So I think you should propose how you think we should add the insert > > > functionality, perhaps even implement it, so we can discuss it and > > > incorporate it if we're all comfortable with it. I think it's > > > - important that any abstraction shouldn't impose potential > inefficiency, > > > and should allow the use of efficient RDBMS functions like Oracle > sequences > > > - important that it should be compatible with JDBC 3.0 moving forward. > > > > > > Thomas, do you have any thoughts on this? > > > > > > Regards, > > > Rod > > > > > > > Personally, I don't think I'd want to commit to yet another framework > such > > > as hibernate for ex. in the project at work we're planning to do with > > > spring. Most of what we need for jdbc is in spring, except for the > insert > > > functionality. Even with oracle, I don't like the idea of having to > write a > > > stored procedure for every single insert, I'd probably opt for the > > > additional cost of a select next_val from dual in jdbc code (i.e. > instead of > > > just doing an insert, first retrieve the key val then do the insert). > The > > > main problem is with db's that don't have sequences, and if we agree to > live > > > with holes in the primary key sequences we can implement an algorithm > where > > > some sort of key manager per VM reserves a range of key values per > table. > > > > > > > > Isabelle > > > > > > > > > > > > > > > > > > > -- > > Isabelle Muszynski > > Software Engineer > > Zandweellaan 4 > > 2660 Antwerpen > > Belgium > > Tel. 32-(0)3-830 18 54 > > Mobile: 32-(0)485 49 50 89 > > Email: isa...@me... > > Website: www.meta-logix.com > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.481 / Virus Database: 277 - Release Date: 13/05/03 > > > -- Isabelle Muszynski Software Engineer Zandweellaan 4 2660 Antwerpen Belgium Tel. 32-(0)3-830 18 54 Mobile: 32-(0)485 49 50 89 Email: isa...@me... Website: www.meta-logix.com |
|
From: Chris A. <ca...@ya...> - 2003-05-19 01:28:58
|
Thomas,
Works great!
--- Thomas Risberg <tri...@tr...> wrote:
> Ken,
>
> I got the app running on JBoss. Had to make a few
> changes:
>
> 1. Changed the petclinic\support\ClinicImpl.java
> class to do a JNDI
> lookup in the afterPropertiesSet() method. Also
> added an import
> statement for DataSourceUtils.
>
> import
> com.interface21.jdbc.datasource.DataSourceUtils;
>
> public void afterPropertiesSet() throws
> java.lang.Exception {
> dataSource =
> DataSourceUtils.getDataSourceFromJndi
> ("jdbc/SpringDS");
> //if(dataSource == null) {
> // throw new
> ApplicationContextException("Must set
> dataSource bean property on " + getClass());
> //}
>
>
> 2. Added a 'resource-ref' entry to web.xml. It
> goes at the end after
> the <taglib> entries.
>
> <resource-ref>
> <description>The default DS</description>
> <res-ref-name>jdbc/SpringDS</res-ref-name>
> <res-type>javax.sql.DataSource</res-type>
> <res-auth>Container</res-auth>
> </resource-ref>
>
> 3. Created a jboss-web.xml file with the
> corresponding 'resource-ref'
> entry pointing to the HSQL default datasource.
>
> <jboss-web>
> <resource-ref>
> <res-ref-name>jdbc/SpringDS</res-ref-name>
> <res-type>javax.sql.DataSource</res-type>
> <jndi-name>java:/DefaultDS</jndi-name>
> </resource-ref>
> </jboss-web>
>
> 4. Commented out the "bean" entry for "dataSource"
> in the
> applicationContext.xml - this is not needed since we
> do a JNDI lookup
> for the datasource.
>
> <beans>
>
> <!--
>
===========================================================-->
> <!-- Global Message source. For all servlets.
>
> -->
> <!--
>
===========================================================-->
> <bean name="messageSource"
>
class="com.interface21.context.support.ResourceBundleMessageSource">
>
> <property name="basename">messages</property>
>
> </bean>
>
> <!--
> <bean name="dataSource"
>
class="com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource"
> >
> <property
>
name="URL">jdbc:mysql://localhost/petclinic</property>
> <property name="user">pc</property>
> <property name="password">pc</property>
> </bean>
> -->
>
> </beans>
>
>
> 5. Commented out the corresponding "property" entry
> for "dataSource"
> under the "clinic" bean entry in
> "petclinic-servlet.xml".
>
> <bean name="clinic"
> class="petclinic.support.ClinicImpl" >
> <!--<property name="dataSource"
> beanRef="true">dataSource</property> -->
> </bean>
>
> 6. Created a "petclinic.war" directory under the
> "c:\jboss-3.2.1
> \server\default\deploy" directory and deployed the
> application there.
>
> That's it - it works like a charm. You can view all
> the Log4j
> messages in
> "c:\jboss-3.2.1\server\default\log\server.log". I
> have
> attached a zip file with the changed code.
>
>
> --Thomas
>
>
> >
> >
> > To All,
> >
> > I am pleased to announce that I now have ready for
> download a
> PROTOTYPE
> > of the Petclinic demo app
> >
>
<http://www.globaldialog.com/%7Ekkrebs/files/Petclinic1.zip>,
>
> approx.
> > 1.25MB.
> >
> > Be sure to read the file, petclinic.txt. This file
> contains my notes
> > about the design and implementation and also
> raises key issues that
> need
> > to be resolved.
> >
> > I very much welcome all comments, suggestions,
> ideas, and
> criticisms. I
> > look forward to hearing from you.
> >
> > Ken
> >
> >
>
>
> ATTACHMENT part 2 application/x-zip-compressed
name=petclinic1_jboss_hsql.zip
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
|
|
From: Thomas R. <tri...@tr...> - 2003-05-18 19:34:21
|
Ken,
I got the app running on JBoss. Had to make a few changes:
1. Changed the petclinic\support\ClinicImpl.java class to do a JNDI
lookup in the afterPropertiesSet() method. Also added an import
statement for DataSourceUtils.
import com.interface21.jdbc.datasource.DataSourceUtils;
public void afterPropertiesSet() throws java.lang.Exception {
dataSource = DataSourceUtils.getDataSourceFromJndi
("jdbc/SpringDS");
//if(dataSource == null) {
// throw new ApplicationContextException("Must set
dataSource bean property on " + getClass());
//}
2. Added a 'resource-ref' entry to web.xml. It goes at the end after
the <taglib> entries.
<resource-ref>
<description>The default DS</description>
<res-ref-name>jdbc/SpringDS</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
3. Created a jboss-web.xml file with the corresponding 'resource-ref'
entry pointing to the HSQL default datasource.
<jboss-web>
<resource-ref>
<res-ref-name>jdbc/SpringDS</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<jndi-name>java:/DefaultDS</jndi-name>
</resource-ref>
</jboss-web>
4. Commented out the "bean" entry for "dataSource" in the
applicationContext.xml - this is not needed since we do a JNDI lookup
for the datasource.
<beans>
<!-- ===========================================================-->
<!-- Global Message source. For all servlets.
-->
<!-- ===========================================================-->
<bean name="messageSource"
class="com.interface21.context.support.ResourceBundleMessageSource">
<property name="basename">messages</property>
</bean>
<!--
<bean name="dataSource"
class="com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource" >
<property name="URL">jdbc:mysql://localhost/petclinic</property>
<property name="user">pc</property>
<property name="password">pc</property>
</bean>
-->
</beans>
5. Commented out the corresponding "property" entry for "dataSource"
under the "clinic" bean entry in "petclinic-servlet.xml".
<bean name="clinic" class="petclinic.support.ClinicImpl" >
<!--<property name="dataSource"
beanRef="true">dataSource</property> -->
</bean>
6. Created a "petclinic.war" directory under the "c:\jboss-3.2.1
\server\default\deploy" directory and deployed the application there.
That's it - it works like a charm. You can view all the Log4j
messages in "c:\jboss-3.2.1\server\default\log\server.log". I have
attached a zip file with the changed code.
--Thomas
>
>
> To All,
>
> I am pleased to announce that I now have ready for download a
PROTOTYPE
> of the Petclinic demo app
> <http://www.globaldialog.com/%7Ekkrebs/files/Petclinic1.zip>,
approx.
> 1.25MB.
>
> Be sure to read the file, petclinic.txt. This file contains my notes
> about the design and implementation and also raises key issues that
need
> to be resolved.
>
> I very much welcome all comments, suggestions, ideas, and
criticisms. I
> look forward to hearing from you.
>
> Ken
>
>
|
|
From: Thomas R. <tri...@tr...> - 2003-05-18 15:44:16
|
Ken, I have attached some database scripts for HSQL and some instructions for running these scripts on JBoss/HSQL. Next step is to get the application running on JBoss/HSQL :-) I'll keep you posted. --Thomas > > > To All, > > I am pleased to announce that I now have ready for download a PROTOTYPE > of the Petclinic demo app > <http://www.globaldialog.com/%7Ekkrebs/files/Petclinic1.zip>, approx. > 1.25MB. > > Be sure to read the file, petclinic.txt. This file contains my notes > about the design and implementation and also raises key issues that need > to be resolved. > > I very much welcome all comments, suggestions, ideas, and criticisms. I > look forward to hearing from you. > > Ken > > |
|
From: Isabelle M. <isa...@me...> - 2003-05-18 14:55:08
|
Thnaks Juergen, I should have caught that. I don't understand how the error crept back in, I had it after copying Rod's sample and fixed it. Must be the pressure...
Anyway, thanks a bunch, it saves me some time.
Isabelle
On Fri, May 16, 2003 at 07:29:45PM +0200, jürgen höller [werk3AT] wrote:
> Hi Isabelle,
>
> It seems that the following class specification is wrong:
>
> <bean name="helloController" class="simple.HelloController" >
>
> HelloController is in tutorial.web.skeleton, not in simple, according to your zip contents.
>
> That fits the exception in your log file:
>
> com.interface21.context.ApplicationContextException: Cannot load configuration: problem instantiating or initializing beans (com.interface21.beans.FatalBeanException: Error creating bean with name [helloController]: class 'simple.HelloController' not found; nested exception is:
> java.lang.ClassNotFoundException: simple.HelloController)
>
> BTW, a "configUrl" context-param shouldn't have any effect, as the parameter is now called "contextConfigLocation" ("/WEB-INF/applicationContext.xml" by default).
>
> If there are further problems, don't hesitate to ask, I'll read my mail regularly over the weekend.
>
> Juergen
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Isabelle Muszynski [mailto:isa...@re...]
> Gesendet: Fr 16.05.2003 18:31
> An: jürgen höller [werk3AT]
> Cc: isa...@me...; spr...@li...
> Betreff: Re: [Springframework-developer] Web app and Log4J initialization
>
>
>
> Hi Juergen,
>
> After implementing your changes, my tutorial app no longer works. If I leave in the configUrl parameter, I get a lifecycle exception and cannot deploy. If I put it in comment, the application deploys but gives an internal error when trying to run it. I'd appreciate some help, I'm totally stumped. I've included the tomcat log file as well.
>
> TIA,
>
> Isabelle
>
> --
> Isabelle Muszynski
> Software Engineer
> B. Rekencentra NV
> Kromstraat 50
> 2520 Ranst
> T. : 32-(0)3-470 14 00
> F. : 32-(0)3-470 14 01
> E. : im...@re...
>
>
--
Isabelle Muszynski
Software Engineer
Zandweellaan 4
2660 Antwerpen
Belgium
Tel. 32-(0)3-830 18 54
Mobile: 32-(0)485 49 50 89
Email: isa...@me...
Website: www.meta-logix.com
|
|
From: Isabelle M. <isa...@me...> - 2003-05-18 13:59:39
|
Hi Rod, I like your idea of everyone chipping in, saves me work :-(. It's been my intent to have skeletons for everything, this is also why every chapter will stand on its own. Isabelle On Sat, May 17, 2003 at 10:48:57AM +0100, Rod Johnson wrote: > I've just taken a quick look at Isabelle's tutorial document. Great work, > Isabelle. > > I'm sure I will have comments, which I'll feed back early next week. It > would be great if everyone else could do likewise. > > (Quick note: Thomas has changed the name of ManualExtractSqlQuery to > MappingSqlQuery.) > > I might contact Wiley, who now own the rights and are reprinting, for a PDF > of chapter 4 from the book (and possibly chapter 9), to put on the site. > > Having a skeleton is a great idea... this will be very helpful to users. > > Maybe we could extend this idea to skeletons showing certain features, such > as AOP, declarative transactions, Hibernate integration etc. Once everyone > is happy with the basis (Isabelle's first skeleton zip) we could all chip in > to provide additional skeletons for specific areas--e.g. I could do > declarative transactions and AOP. > > Regards, > Rod > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: If flattening out C++ or Java > code to make your application fit in a relational database is painful, > don't do it! Check out ObjectStore. Now part of Progress Software. > http://www.objectstore.net/sourceforge > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > -- Isabelle Muszynski Software Engineer Zandweellaan 4 2660 Antwerpen Belgium Tel. 32-(0)3-830 18 54 Mobile: 32-(0)485 49 50 89 Email: isa...@me... Website: www.meta-logix.com |