Update of /cvsroot/xdoclet/xdoclet/xdocs
In directory sc8-pr-cvs1:/tmp/cvs-serv21056/xdoclet/xdocs

Modified Files:
        using.xml 
Log Message:
Fixed some typos and replaced & by & so the generated html isn't fucked up.

Index: using.xml
===================================================================
RCS file: /cvsroot/xdoclet/xdoclet/xdocs/using.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -C2 -r1.10 -r1.11
*** using.xml   18 Nov 2002 16:08:50 -0000      1.10
--- using.xml   1 Dec 2002 15:45:20 -0000       1.11
***************
*** 172,180 ****
                  Here the compile target depends on the ejbdoclet target. This means 
that before compiling
                  anything all home/local/remote interfaces, primary key, data-objects 
and deployment descriptors
!                 are generated. The first thing you have to do is define ejbdoclet 
task for Ant.<br/>
                  To do so you use taskdef, where you specify 
<code>xdoclet.modules.ejb.EjbDocletTask</code>
                  as the class implementing ejbdoclet task. Note that classpath 
parameter has xdoclet.jar,
                  xjavadoc.jar, commons-logging.jar, log4j.jar and ant.jar (Ant 1.5 or 
higher) in it.
!                 These 5 jars are all needed.
              </p>
              <p>
--- 172,180 ----
                  Here the compile target depends on the ejbdoclet target. This means 
that before compiling
                  anything all home/local/remote interfaces, primary key, data-objects 
and deployment descriptors
!                 are generated. The first thing you have to do is define the 
ejbdoclet task for Ant.<br/>
                  To do so you use taskdef, where you specify 
<code>xdoclet.modules.ejb.EjbDocletTask</code>
                  as the class implementing ejbdoclet task. Note that classpath 
parameter has xdoclet.jar,
                  xjavadoc.jar, commons-logging.jar, log4j.jar and ant.jar (Ant 1.5 or 
higher) in it.
!                 These these jars are all needed.
              </p>
              <p>
***************
*** 183,187 ****
                  you can see there's an inheritance mechanisms also, you can override 
this
                  destdir parameter for each nested element (or as we call it 
sub-task).<br/>
!                 &lt;deploymentdescriptor/&gt; does exactly that to put the generated
                  ejb-jar.xml file somewhere else than where generated java sources for
                  home/remote/pk/etc are placed. For a complete list of configurable 
parameters
--- 183,187 ----
                  you can see there's an inheritance mechanisms also, you can override 
this
                  destdir parameter for each nested element (or as we call it 
sub-task).<br/>
!                 &amp;lt;deploymentdescriptor/&amp;gt; does exactly that; put the 
generated
                  ejb-jar.xml file somewhere else than where generated java sources for
                  home/remote/pk/etc are placed. For a complete list of configurable 
parameters
***************
*** 190,202 ****
              <p>
                  By default each task has some built-in sub-tasks. Some of them are 
mandatory,
!                 for example &lt;remoteinterface/&gt; and &lt;localinterface/&gt;, 
can you imagine an
!                 EJB without a remote or local (EJB 2.0 only) interface? Some other 
tasks may be
!                 optional, for example &lt;jboss/&gt; is optional if you're not using 
JBoss Application
!                 Server.
              </p>
              <p>
!                 There's even a third form of sub-tasks: &lt;template/&gt;. This is 
useful for cases
                  where you want to design your own template file and generate a 
customized file.
!                 So, you need a simple way to let xdoclet use your template file. 
Here is an
                  example:
              </p>
--- 190,202 ----
              <p>
                  By default each task has some built-in sub-tasks. Some of them are 
mandatory,
!                 for example &amp;lt;remoteinterface/&amp;gt; and
!                 &amp;lt;localinterface/&amp;gt;, can you imagine an EJB without a 
remote or
!                 local (EJB 2.0 only) interface? Some other tasks may be optional, 
for example
!                 &amp;lt;jboss/&amp;gt; is optional if you're not using JBoss 
Application Server.
              </p>
              <p>
!                 There's even a third form of sub-tasks: &amp;lt;template/&amp;gt;. 
This is useful for cases
                  where you want to design your own template file and generate a 
customized file.
!                 So, you need a simple way to let XDoclet use your template file. 
Here is an
                  example:
              </p>
***************
*** 206,210 ****
      name="templatedoclet"
      classname="xdoclet.DocletTask"
!     classpath="${xdoclet.jar.path};${log4j.jar.path};${ant.jar.path}"
  />
  
--- 206,210 ----
      name="templatedoclet"
      classname="xdoclet.DocletTask"
!     
classpath="${xdoclet.jar.path};${commons-logging.jar.path};${log4j.jar.path};${ant.jar.path}"
  />
  
***************
*** 225,230 ****
  
              <p>
!                 So you put a &lt;template/&gt; element in the task, specify the path 
to your
!                 template file and output file name (which will we stored in the 
directory
                  specified in destdir parameter). This is very useful for those 
creative people
                  who want to easily take advantage of XDoclet's framework-like 
capabilities and
--- 225,230 ----
  
              <p>
!                 So you put a &amp;lt;template/&amp;gt; element in the task, specify 
the path to
!                 your template file and output file name (which will we stored in the 
directory
                  specified in destdir parameter). This is very useful for those 
creative people
                  who want to easily take advantage of XDoclet's framework-like 
capabilities and
***************
*** 233,241 ****
              </p>
              <p>
!                 So whenever you do a build, ejbdoclet (or whatever other task) is 
run and you
!                 have always up-to-date files generated by XDoclet.
              </p>
              <p>
!                 A checklist of things you will need to do to get XDoclet running:
              </p>
              <ul>
--- 233,241 ----
              </p>
              <p>
!                 So whenever you build, ejbdoclet (and/or whatever other task) is run 
and generates
!                 up-to-date files.
              </p>
              <p>
!                 Quick checklist of things to get XDoclet running:
              </p>
              <ul>
***************
*** 243,247 ****
                  <a href="http://jakarta.apache.org/ant";>Jakarta Ant</a> website for 
details).</li>
                  <li>Add <a href="tags/ejb-tags.html">XDoclet tags</a> to your source 
code.</li>
!                 <li>Stop worrying about all that boring code you use to have to 
write! XDoclet does it for you now.</li>
              </ul>
              <p>
--- 243,247 ----
                  <a href="http://jakarta.apache.org/ant";>Jakarta Ant</a> website for 
details).</li>
                  <li>Add <a href="tags/ejb-tags.html">XDoclet tags</a> to your source 
code.</li>
!                 <li>Stop worrying about all that boring code you used to write! 
XDoclet does it all for you now.</li>
              </ul>
              <p>



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel

Reply via email to