User: pathoss 
  Date: 02/04/28 15:24:23

  Modified:    core/docs Tag: MODULE_REFACTORING_BRANCH architecture.html
  Log:
  Changed package xdoclet.tags to xdoclet.tagshandler.
  
  Revision  Changes    Path
  No                   revision
  
  
  No                   revision
  
  
  1.5.4.1   +8 -8      xdoclet/core/docs/architecture.html
  
  Index: architecture.html
  ===================================================================
  RCS file: /cvsroot/xdoclet/xdoclet/core/docs/architecture.html,v
  retrieving revision 1.5
  retrieving revision 1.5.4.1
  diff -u -w -r1.5 -r1.5.4.1
  --- architecture.html 7 Feb 2002 22:38:00 -0000       1.5
  +++ architecture.html 28 Apr 2002 22:24:23 -0000      1.5.4.1
  @@ -36,7 +36,7 @@
     new class for each tag you write. For example a template tag like 
<XDtClass:classTagValue 
     tagName="ejb:bean" paramName="name"/> is simply 
implemented as a "public 
     String classTagValue( Properties attributes ) throws XDocletException" 
method 
  -  in xdoclet.tags.ClassTagsHandler class. Many templates tags could be defined 
  +  in xdoclet.tagshandler.ClassTagsHandler class. Many templates tags could be 
defined 
     in a single class, that single class is like a tag library in JSP all in 
     itself! Note that it does not mean that template tags in XDoclet are 
     stateless, you can store state in the handler class as normal attributes of 
  @@ -161,7 +161,7 @@
   <p>All template tag implementation methods throw XDocletException, which is 
   itself derived from TemplateException.</p>
   <p>The following code snippet shows how a content tag className is implemented 
  -in xdoclet.tags.ClassTagsHandler:</p>
  +in xdoclet.tagshandler.ClassTagsHandler:</p>
   <pre>/**
   * Returns the not-full-qualified name of the current class without the
   * package name.
  @@ -178,7 +178,7 @@
   instance of com.sun.javadoc.ClassDoc (the current class, the one XDoclet is 
   processing) and use name() method to return short class name of current class.</p>
   <p>The following code snippet shows how a block tag ifIsClassAbstract is 
  -implemented in xdoclet.tags.ClassTagsHandler:</p>
  +implemented in xdoclet.tagshandler.ClassTagsHandler:</p>
   <pre>/**
   * Evaluate the body block if current class is abstract.
   *
  @@ -201,7 +201,7 @@
   processed. So if current class is abstract the body is evaluated, if not nothing 
   happens and control returns to containing elements.</p>
   <p>The following code snippet shows how a block tag ifHasClassTag is implemented 
  -in xdoclet.tags.ClassTagsHandler:</p>
  +in xdoclet.tagshandler.ClassTagsHandler:</p>
   <pre>/**
   * Evaluates the body if current class has at least one tag with the specified
   * name.
  @@ -268,7 +268,7 @@
   will be processed and output written to output!</p>
   
   <p>But how TemplateEngine know when it sees a &lt;XDtClass:className/&gt; it should 
  -call className() method of xdoclet.tags.ClassTagsHandler?</p>
  +call className() method of xdoclet.tagshandler.ClassTagsHandler?</p>
   
   <p>It's easy, you register a instance of type TemplateTagHandler with 
   TemplateEngine to handler all tags of a namesapce and it's done using 
  @@ -280,9 +280,9 @@
   in XDolcet's jar root. Here is how it looks like:</p>
   
   <pre>#General namespaces
  -Type=xdoclet.tags.TypeTagsHandler
  -Class=xdoclet.tags.ClassTagsHandler</pre>
  -<p>And easily Class is mapped to xdoclet.tags.ClassTagsHandler. Note that 
  +Type=xdoclet.tagshandler.TypeTagsHandler
  +Class=xdoclet.tagshandler.ClassTagsHandler</pre>
  +<p>And easily Class is mapped to xdoclet.tagshandler.ClassTagsHandler. Note that 
   TemplateTagHandler classes should have a no argument public constructor, so that 
   TemplateEngine be able to create an instance of it.</p>
   <p>The rest is rather easy to guess, TemplateEngine extracts the namespace name, 
  
  
  

_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel

Reply via email to