User: rinkrank
Date: 02/05/28 16:17:53
Added: xdocs index.xml tull.xml
Log:
Merged MODULE_REFACTORING_BRANCH back to MAIN
Revision Changes Path
1.1 xdoclet/xdocs/index.xml
Index: index.xml
===================================================================
<?xml version="1.0"?>
<document>
<properties>
<author email="[EMAIL PROTECTED]">Jon S. Stevens</author>
<title>My Project</title>
</properties>
<body>
<section name="What is XDoclet?">
<p>
XDoclet is a code generation engine. It makes attribute oriented programming
possible in java.
XDoclet scans Java source code
and extracts information from special JavaDoc tags and the source code itself.
Based on this information it can generate more source code or other files
(such as xml-ish deployment descriptors) based on templates.
</p>
<p>
The broader goal of XDoclet is to let you apply
<a
href="http://www.martinfowler.com/articles/continuousIntegration.html";>Continuous
Integration</a> in component-oriented development. The idea is that the
developers can
work concentrate their editing on only one Java source file per component.
The component's meta data is included in the source file as special JavaDoc
tags, and XDoclet
will generate the rest of the files that make up the component.
</p>
<p>
This approach has several benefits:
<ol>
<li>
You don't have to worry about outdating deployment
meta-data whenever you touch the code. The deployment meta-data is
continuously
integrated.
</li>
<li>
Working with only one file per component gives you a better overview of
what you're doing.
If your component consists of several files, it's easy to lose track. If
you have ever written an
Enterprise Java Bean, you know what we mean. A single EJB can typically
consists of 7 or more files.
With XDoclet you only maintain one of them, and the rest of them are
generated.
</li>
<li>
You can dramatically reduce the development time. You concentrate on the
business logic, and you
can get up to 85% of the code generated for you.
</li>
</ol>
XDoclet is meant to be used as part of the build process utilizing <a
href="http://jakarta.apache.org/ant/";>Ant</a>
</p>
<p>
Although XDoclet originated as a tool for creating EJBs, it has evolved into a
general-purpose code
generation engine. XDoclet consists of a core and a constantly growing number
of modules. It is fairly
straightforward to write new modules if there is a need to cover a new kind of
component.
</p>
<p>
The generated code is based on templates.
XDoclet comes with a set of modules for generation of different kinds of files.
Users and contributors can write their own modules (or modify existing ones)
if they wish to extend the functionality of XDoclet.
</p>
</section>
</body>
</document>
1.1 xdoclet/xdocs/tull.xml
Index: tull.xml
===================================================================
<?xml version="1.0" encoding="ISO-8859-1"?>
<document>
<properties>
<author email="[EMAIL PROTECTED]">Aslak Helles�y</author>
<title>XDoclet</title>
</properties>
<body>
<section name="TULL">
<p>
XDoclet is a tool which makes attribute oriented programming possible in java.
It is
implemented as a generic code generation engine. XDoclet scans Java source code
and extracts information from special JavaDoc tags and the source code itself.
Based on this information it can generate more source code or other files
(such as xml-ish deployment descriptors) based on templates.
</p>
<p>
The broader goal of XDoclet is to let you apply
<a
href="http://www.martinfowler.com/articles/continuousIntegration.html";>Continuous
Integration</a> in component-oriented development. The idea is that the
developers can
work concentrate their editing on only one Java source file per component.
The component's meta data is included in the source file as special JavaDoc
tags, and XDoclet
will generate the rest of the files that make up the component.
</p>
<p>
This approach has several benefits:
<ol>
<li>
You don't have to worry about outdating deployment
meta-data whenever you touch the code. The deployment meta-data is
continuously
integrated.
</li>
<li>
Working with only one file per component gives you a better overview of
what you're doing.
If your component consists of several files, it's easy to lose track. If
you have ever written an
Enterprise Java Bean, you know what we mean. A single EJB can typically
consists of 7 or more files.
With XDoclet you only maintain one of them, and the rest of them are
generated.
</li>
<li>
You can dramatically reduce the development time. You concentrate on the
business logic, and you
can get up to 85% of the code generated for you.
</li>
</ol>
XDoclet is meant to be used as part of the build process utilizing <a
href="http://jakarta.apache.org/ant/";>Ant</a>
</p>
<p>
Although XDoclet originated as a tool for creating EJBs, it has evolved into a
general-purpose code
generation engine. XDoclet consists of a core and a constantly growing number
of modules. It is fairly
straightforward to write new modules if there is a need to cover a new kind of
component.
</p>
<p>
The generated code is based on templates.
XDoclet comes with a set of modules for generation of different kinds of files.
Users and contributors can write their own modules (or modify existing ones)
if they wish to extend the functionality of XDoclet.
</p>
</section>
</body>
</document>
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
