Menu
▾
▴
[Springframework-cvs] spring/docs/reference/src xsd-configuration.xml,NONE,1.1 index.xml,1.71,1.72 new-in-2.0.xml,1.6,1.7
|
From: Rick E. <spr...@us...> - 2006-04-20 16:24:34
|
Update of /cvsroot/springframework/spring/docs/reference/src In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv21526/docs/reference/src Modified Files: index.xml new-in-2.0.xml Added Files: xsd-configuration.xml Log Message: [SPR-1907] Added skeleton; to be fleshed out later. Index: index.xml =================================================================== RCS file: /cvsroot/springframework/spring/docs/reference/src/index.xml,v retrieving revision 1.71 retrieving revision 1.72 diff -C2 -d -r1.71 -r1.72 *** index.xml 20 Apr 2006 01:45:34 -0000 1.71 --- index.xml 20 Apr 2006 16:24:28 -0000 1.72 *************** *** 29,33 **** <!ENTITY testing SYSTEM "testing.xml"> <!ENTITY scripting SYSTEM "scripting.xml"> ! <!ENTITY dynamic-languages SYSTEM "dynamic-languages.xml"> <!ENTITY schema-beans SYSTEM "spring-beans.xsd.xml"> <!ENTITY dtd SYSTEM "dtd.xml"> --- 29,34 ---- <!ENTITY testing SYSTEM "testing.xml"> <!ENTITY scripting SYSTEM "scripting.xml"> ! <!ENTITY dynamic-languages SYSTEM "dynamic-languages.xml"> ! <!ENTITY xsd-configuration SYSTEM "xsd-configuration.xml"> <!ENTITY schema-beans SYSTEM "spring-beans.xsd.xml"> <!ENTITY dtd SYSTEM "dtd.xml"> *************** *** 298,301 **** --- 299,303 ---- </part> <!-- back matter --> + &xsd-configuration; &schema-beans; &dtd; Index: new-in-2.0.xml =================================================================== RCS file: /cvsroot/springframework/spring/docs/reference/src/new-in-2.0.xml,v retrieving revision 1.6 retrieving revision 1.7 diff -C2 -d -r1.6 -r1.7 *** new-in-2.0.xml 20 Apr 2006 11:07:01 -0000 1.6 --- new-in-2.0.xml 20 Apr 2006 16:24:28 -0000 1.7 *************** *** 52,57 **** the new tags that Spring provides (and the Spring team certainly suggest that you do because they make one's configuration much less verbose and ! just plain easier to read), then do read the section entitled [TODO : ! link to the new schema-based configuration section]</para> </section> --- 52,57 ---- the new tags that Spring provides (and the Spring team certainly suggest that you do because they make one's configuration much less verbose and ! just plain easier to read), then do read the section entitled ! <xref linkend="xsd-config"/>.</para> </section> *************** *** 71,76 **** <para>This feature may not be of interest to every single application developer or enterprise architect using Spring in their own projects, ! and so it is detailed separately in the [appendix] entitled [TODO : link ! to the 'Write your own namespace handler' section]</para> </section> --- 71,80 ---- <para>This feature may not be of interest to every single application developer or enterprise architect using Spring in their own projects, ! and so it is not (as yet) detailed in this reference documentation. If ! you are interested in writing your own Spring configuration tags, then ! having a look at the source code for the current Spring tags is your ! starting point (it would be wrong to say that the process is trivial, ! but it isn't exactly hard either... one Java class and one XSD schema ! document is what you're looking at having to write).</para> </section> *************** *** 145,148 **** --- 149,158 ---- <title>Middle tier (data access)</title> + <section id="new-in-2-middle-tier-transaction-configuration"> + <title>Easier configuration of declarative transactions in XML</title> + + <para>[TODO : coverage of the new XML transaction configuration]</para> + </section> + <section id="new-in-2-middle-tier-jpa"> <title>JPA</title> *************** *** 176,181 **** <title>JDBC</title> - <para>[TODO : coverage of the new XML transaction configuration]</para> - <para>There are some notable new classes in the area of Spring's JDBC abstraction framework. The first, --- 186,189 ---- --- NEW FILE: xsd-configuration.xml --- <?xml version="1.0" encoding="UTF-8" ?> <appendix id="xsd-config"> <title>XML Schema-based configuration</title> <section> <title>Introduction</title> <para>This section of the reference documentation details the XML Schema based configuration that was introduced in Spring 2.0.</para> <sidebar> <title>DTD?</title> <para>Authoring Spring configuration files using the older DTD style is still totally supported.</para> <para>Nothing will break if you forego the use of the new XML Schema-based approach to authoring Spring XML configuration files. All that you lose out on is more succinct and clearer configuration... in the end all of the XML configuration, be it DTD- or Schema-based all boils down to the same object model in the container.</para> </sidebar> <para>The central motivation for moving to XML Schema based configuration files was to enable easier Spring (unsurprisingly). The <emphasis>'classic'</emphasis> <literal><bean/></literal>-based approach is good (and it still continues to be good), but it does suffer from being a tad generic.</para> <para>From the Spring IoC containers point of view, <emphasis>everything</emphasis> is a bean. Thats great news for the Spring IoC container, because if everything is a bean then everything can be treated the same. The same is not true for developers... the objects (or classes rather) that one defines in a Spring XML configuration file are not all generic, vanilla beans.</para> <para>Spring 2.0's new XML Schema-based configuration addresses this issue. The <literal><bean/></literal> element is still present, and if one wanted to one could continue to write the <emphasis>exact same</emphasis> style of Spring XML configuration using only <literal><bean/></literal> elements. The new XML Schema-based configuration does however result in Spring XML configuration files that are substantially clearer to read, and that allow one to express the intent of what a bean definition is. </para> <para>The examples included below will hopefully convince you that the inclusion of XML Schema support in Spring 2.0 was a good idea. The Spting team certainly thinks so, and the reception in the community has been encouraging; something that is not covered in this section (at least not right now) is the fact that this new configuration mechanism is totally customisable and extensible. This means that one can write one's own domain specific configuration that allows one to more succinctly express one's domain.</para> </section> <section id="xsd-config-body"> <title>XML Schema-based configuration</title> <section id="xsd-config-body-referencing"> <title>Referencing the schemas</title> <para>[TODO : explain how to locate and reference the correct schemas at the top of ones configuratio file]</para> </section> <section id="xsd-config-body-schemas-util"> <title>The <literal>util</literal> schema</title> <para>[TODO : provide examples or links to examples (with screenshots)]</para> </section> </section> <section id="xsd-config-setup"> <title>Setting up your IDE</title> <para>This final section documents the steps involved in setting up a number of popular Java IDEs to effect the easier editing of Spring's XML Schema-based configuration files.</para> <para>If your favourite Java IDE or editor is not included in the list of documented IDEs, then please do raise an issue (or ticket) on the Spring Framework <ulink linkend="http://opensource.atlassian.com/projects/spring/secure/Dashboard.jspa">JIRA</ulink> and the oversight <emphasis>may</emphasis> well be addressed in the next release.</para> <section id="xsd-config-setup-eclipse"> <title>Setting up Eclipse</title> <para>[TODO : document setting up Eclipse (with screenshots)]</para> </section> <section id="xsd-config-setup-idea"> <title>Setting up IDEA</title> <para>[TODO : document setting up IDEA (with screenshots)]</para> </section> </section> </appendix> |
