click-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sa...@apache.org
Subject svn commit: r731552 [1/3] - in /incubator/click/trunk/click: build/ documentation/ documentation/docs/ documentation/docs/developer-guide/ documentation/docs/velocity/
Date Mon, 05 Jan 2009 13:09:59 GMT
Author: sabob
Date: Mon Jan  5 05:09:59 2009
New Revision: 731552

URL: http://svn.apache.org/viewvc?rev=731552&view=rev
Log:
migrated build and docs to Apache namespace

Modified:
    incubator/click/trunk/click/build/build.xml
    incubator/click/trunk/click/documentation/docs/best-practices.html
    incubator/click/trunk/click/documentation/docs/click-dtd-example.html
    incubator/click/trunk/click/documentation/docs/click-dtd.html
    incubator/click/trunk/click/documentation/docs/configuration.html
    incubator/click/trunk/click/documentation/docs/controls.html
    incubator/click/trunk/click/documentation/docs/developer-guide/contributing.html
    incubator/click/trunk/click/documentation/docs/error-npe.html
    incubator/click/trunk/click/documentation/docs/extras-overview.html
    incubator/click/trunk/click/documentation/docs/faq.html
    incubator/click/trunk/click/documentation/docs/introduction.html
    incubator/click/trunk/click/documentation/docs/javadoc.html
    incubator/click/trunk/click/documentation/docs/mock-overview.html
    incubator/click/trunk/click/documentation/docs/pages.html
    incubator/click/trunk/click/documentation/docs/quick-start.html
    incubator/click/trunk/click/documentation/docs/roadmap-changes.html
    incubator/click/trunk/click/documentation/docs/velocity/velocity.html
    incubator/click/trunk/click/documentation/toc.html

Modified: incubator/click/trunk/click/build/build.xml
URL: http://svn.apache.org/viewvc/incubator/click/trunk/click/build/build.xml?rev=731552&r1=731551&r2=731552&view=diff
==============================================================================
--- incubator/click/trunk/click/build/build.xml (original)
+++ incubator/click/trunk/click/build/build.xml Mon Jan  5 05:09:59 2009
@@ -285,7 +285,7 @@
       <jar destfile="dist/${click-extras}.jar">
          <manifest>
            <attribute name="Click-Version" value="${version}"/>
-           <attribute name="Package" value="net.sf.click.extras"/>
+           <attribute name="Package" value="org.apache.click.extras"/>
            <attribute name="Built-By" value="${user.name}"/>
          </manifest>
          <fileset dir="extras/classes"/>
@@ -326,7 +326,7 @@
    	  <jar destfile="dist/${click-nodeps}.jar">
          <manifest>
            <attribute name="Click-Version" value="${version}"/>
-           <attribute name="Package" value="net.sf.click"/>
+           <attribute name="Package" value="org.apache.click"/>
            <attribute name="Built-By" value="${user.name}"/>
          </manifest>
          <fileset dir="${dir.classes}"/>
@@ -355,7 +355,7 @@
       <jar destfile="dist/${click}.jar">
          <manifest>
            <attribute name="Click-Version" value="${version}"/>
-           <attribute name="Package" value="net.sf.click"/>
+           <attribute name="Package" value="org.apache.click"/>
            <attribute name="Built-By" value="${user.name}"/>
          </manifest>
          <fileset dir="${dir.classes}">
@@ -395,7 +395,7 @@
       <jar destfile="dist/${click-mock}.jar">
          <manifest>
            <attribute name="Click-Version" value="${version}"/>
-           <attribute name="Package" value="net.sf.click"/>
+           <attribute name="Package" value="org.apache.click"/>
            <attribute name="Built-By" value="${user.name}"/>
          </manifest>
          <fileset dir="mock/classes"/>
@@ -589,8 +589,8 @@
                     classpath="classpath.framework"
       	            overview="documentation/docs/core-overview.html"/>
 
-      <copy file="framework/src/net/sf/click/control/image-submit.gif"
-            todir="documentation/docs/click-api/net/sf/click/control"/>
+      <copy file="framework/src/org/apache/click/control/image-submit.gif"
+            todir="documentation/docs/click-api/org/apache/click/control"/>
    	
       <!-- Extras -->
       <delete quiet="false" failonerror="false">
@@ -617,35 +617,35 @@
     				overview="documentation/docs/mock-overview.html"/>
 
       <copy file="documentation/images/post-sequence-diagram.png"
-            todir="documentation/docs/click-api/net/sf/click/"/>
+            todir="documentation/docs/click-api/org/apache/click/"/>
       <copy file="documentation/images/control-post-sequence-diagram.png"
-            todir="documentation/docs/click-api/net/sf/click/"/>
+            todir="documentation/docs/click-api/org/apache/click/"/>
       <copy file="documentation/images/service-package.png"
-            todir="documentation/docs/click-api/net/sf/click/service/"/>
+            todir="documentation/docs/click-api/org/apache/click/service/"/>
       <copy file="documentation/images/service-package.png"
-            todir="documentation/docs/extras-api/net/sf/click/extras/service/"/>
+            todir="documentation/docs/extras-api/org/apache/click/extras/service/"/>
       <copy file="documentation/images/form-table.png"
-            todir="documentation/docs/extras-api/net/sf/click/extras/control"/>
+            todir="documentation/docs/extras-api/org/apache/click/extras/control"/>
       <copy file="documentation/images/menu.png"
-            todir="documentation/docs/extras-api/net/sf/click/extras/control"/>
+            todir="documentation/docs/extras-api/org/apache/click/extras/control"/>
       <copy file="documentation/images/link-decorator.png"
-          todir="documentation/docs/extras-api/net/sf/click/extras/control"/>
+          todir="documentation/docs/extras-api/org/apache/click/extras/control"/>
       <copy file="documentation/images/tabbed-form.png"
-            todir="documentation/docs/extras-api/net/sf/click/extras/control"/>
+            todir="documentation/docs/extras-api/org/apache/click/extras/control"/>
       <copy file="documentation/images/virtual-keyboard.gif"
-            todir="documentation/docs/extras-api/net/sf/click/extras/control"/>
+            todir="documentation/docs/extras-api/org/apache/click/extras/control"/>
       <copy file="documentation/images/table.png"
-            todir="documentation/docs/click-api/net/sf/click/control"/>
+            todir="documentation/docs/click-api/org/apache/click/control"/>
       <copy file="documentation/images/default-paginator.png"
-            todir="documentation/docs/click-api/net/sf/click/control"/>
+            todir="documentation/docs/click-api/org/apache/click/control"/>
       <copy file="documentation/images/inline-paginator.png"
-            todir="documentation/docs/extras-api/net/sf/click/extras/control"/>
+            todir="documentation/docs/extras-api/org/apache/click/extras/control"/>
       <copy file="extras/src/META-INF/web/click/colorpicker/images/color-picker.png"
-            todir="documentation/docs/extras-api/net/sf/click/extras/control/colorpicker"/>
+            todir="documentation/docs/extras-api/org/apache/click/extras/control/colorpicker"/>
       <copy file="documentation/images/tree.png"
-            todir="documentation/docs/extras-api/net/sf/click/extras/tree"/>
+            todir="documentation/docs/extras-api/org/apache/click/extras/tree"/>
       <copy file="documentation/images/checkbox-tree.png"
-            todir="documentation/docs/extras-api/net/sf/click/extras/tree"/>
+            todir="documentation/docs/extras-api/org/apache/click/extras/tree"/>
       <copy file="documentation/docs/javadoc-stylesheet.css"  
       	    overwrite="true"
       	    tofile="documentation/docs/click-api/stylesheet.css"/>
@@ -880,7 +880,7 @@
                version="true"
                verbose="false"
                windowtitle="@{windowtitle}"
-      	       packagenames="net.*"
+      	       packagenames="org.*"
          	     overview="@{overview}"
                doctitle="@{doctitle}">
             <classpath refid="@{classpath}"/>

Modified: incubator/click/trunk/click/documentation/docs/best-practices.html
URL: http://svn.apache.org/viewvc/incubator/click/trunk/click/documentation/docs/best-practices.html?rev=731552&r1=731551&r2=731552&view=diff
==============================================================================
--- incubator/click/trunk/click/documentation/docs/best-practices.html (original)
+++ incubator/click/trunk/click/documentation/docs/best-practices.html Mon Jan  5 05:09:59 2009
@@ -514,7 +514,7 @@
 
 <a name="menus" class="heading"></a><h2>6.&nbsp; Menus</h2>
 
-For many applications using the <a href="extras-api/net/sf/click/extras/control/Menu.html">Menu</a>
+For many applications using the <a href="extras-api/org/apache/click/extras/control/Menu.html">Menu</a>
 control to centralize application navigation is very useful. 
 Menus are defined in a <tt>WEB-INF/menu.xml</tt> file which is very easy to change.
 <p/>
@@ -533,7 +533,7 @@
 as it is automatically included by Click. 
 <p/>
 Using macros you can create dynamic menu behaviour such as only rendering menu items 
-a user is authorized to access with <a href="extras-api/net/sf/click/extras/control/Menu.html#isUserInRoles()">isUserInRoles()</a>.
+a user is authorized to access with <a href="extras-api/org/apache/click/extras/control/Menu.html#isUserInRoles()">isUserInRoles()</a>.
 
 <pre class="codeHtml">
 <span class="kw">#if</span> (<span class="red">$</span>menu.isUserInRoles())
@@ -610,7 +610,7 @@
 
 <a name="error-handling" class="heading"></a><h2>8.&nbsp; Error Handling</h2>
 
-In Click unhandled errors are directed to the <a href="click-api/net/sf/click/util/ErrorPage.html">ErrorPage</a>
+In Click unhandled errors are directed to the <a href="click-api/org/apache/click/util/ErrorPage.html">ErrorPage</a>
 for display. If applications require additional error handling they can create and
 register a custom error page in <tt>WEB-INF/click.xml</tt>. For example:
 
@@ -627,7 +627,7 @@
 <p/>
 For example if an application requires unhandled errors to be logged to an 
 application log (rather than System.out) then a custom 
-<a href="click-api/net/sf/click/util/ErrorPage.html">ErrorPage</a> could be
+<a href="click-api/org/apache/click/util/ErrorPage.html">ErrorPage</a> could be
 configured. An example <tt>ErrorPage</tt> error logging page is provided 
 below:
 
@@ -635,7 +635,7 @@
 <span class="kw">package</span> com.mycorp.page.ErrorPage;
 ..
 
-<span class="kw">public class</span> ErrorPage <span class="kw">extends</span> net.sf.click.util.ErrorPage {
+<span class="kw">public class</span> ErrorPage <span class="kw">extends</span> org.apache.click.util.ErrorPage {
 	
     <span class="kw">public void</span> onDestory() {
     	Logger.getLogger(getClass()).error(getError());
@@ -648,7 +648,7 @@
 Yahoo published a list of <a target="_blank" class="external" href="http://developer.yahoo.com/performance/rules.html">best practices</a>
 for improving web application performance.
 <p/>
-Click Framework provides a <a href="extras-api/net/sf/click/extras/filter/PerformanceFilter.html">PerformanceFilter</a>
+Click Framework provides a <a href="extras-api/org/apache/click/extras/filter/PerformanceFilter.html">PerformanceFilter</a>
 which caters for some of these rules. However not all rules can be easily automated.
 <p/>
 This section will outline ways to apply rules which are not covered by the PerformanceFilter namely, <a target="_blank" class="external" href="http://developer.yahoo.com/performance/rules.html#num_http">#1 - Minimize HTTP Requests (by combining files)</a>
@@ -703,13 +703,13 @@
 by the Page and its Controls. Then you can instruct Click to <em>only</em>
 include the two compressed files, home-page.css and home-page.js.
 <p/>
-Click makes use of the utility class  <a href="click-api/net/sf/click/util/PageImports.html">PageImports</a>
+Click makes use of the utility class  <a href="click-api/org/apache/click/util/PageImports.html">PageImports</a>
 to include the CSS and JavaScript. PageImports exposes the method
-<a href="click-api/net/sf/click/util/PageImports.html#setInitialized(boolean)">setInitialized(boolean)</a>,
+<a href="click-api/org/apache/click/util/PageImports.html#setInitialized(boolean)">setInitialized(boolean)</a>,
 which controls when PageImports are fully initialized. Once PageImports have been
 initialized, no other CSS and JavaScript will be included.
 <p/>
-Knowing this one can override <a href="click-api/net/sf/click/Page.html#getPageImports()">Page.getPageImports()</a>,
+Knowing this one can override <a href="click-api/org/apache/click/Page.html#getPageImports()">Page.getPageImports()</a>,
 and import the necessary JavaScript and CSS files and then set PageImports to <tt>initialized</tt>,
 forcing PageImports to skip other CSS and JavaScript files.
 <p/>

Modified: incubator/click/trunk/click/documentation/docs/click-dtd-example.html
URL: http://svn.apache.org/viewvc/incubator/click/trunk/click/documentation/docs/click-dtd-example.html?rev=731552&r1=731551&r2=731552&view=diff
==============================================================================
--- incubator/click/trunk/click/documentation/docs/click-dtd-example.html (original)
+++ incubator/click/trunk/click/documentation/docs/click-dtd-example.html Mon Jan  5 05:09:59 2009
@@ -66,19 +66,19 @@
       &lt;header name="Expires" value="1" type="Date"/&gt;
   &lt;/headers&gt;
 
-  &lt;!-- Setup alternative Format. Default Format is net.sf.click.util.Format --&gt;
+  &lt;!-- Setup alternative Format. Default Format is org.apache.click.util.Format --&gt;
   &lt;format classname="com.mycorp.util.Format"/&gt;
 
   &lt;!-- Mode values include: [production], [profile], [development], [debug], [trace] --&gt;
   &lt;mode value="production"/&gt;
 
   &lt;!-- Set Click internal Logger to Log4J instead of the default ConsoleLogService --&gt;
-  &lt;log-service classname="net.sf.click.extras.service.Log4JLogService"/&gt;
+  &lt;log-service classname="org.apache.click.extras.service.Log4JLogService"/&gt;
 
   &lt;!-- Set the template engine to use Freemarker instead of Velocity --&gt;
-  &lt;template-service classname="net.sf.click.extras.service.FreemarkerTemplateService"/&gt;
+  &lt;template-service classname="org.apache.click.extras.service.FreemarkerTemplateService"/&gt;
 
-  &lt;!-- Set the net.sf.click.service.CommonsFileUploadService properties: sizeMax and fileSizeMax. --&gt;
+  &lt;!-- Set the org.apache.click.service.CommonsFileUploadService properties: sizeMax and fileSizeMax. --&gt;
   &lt;file-upload-service&gt;
       &lt;!-- Set the total request maximum size to 10mb (10 x 1024 x 1024 = 10485760). The default request upload size is unlimited. --&gt;
       &lt;property name="sizeMax" value="10485760"/&gt;
@@ -88,7 +88,7 @@
   &lt;/file-upload-service&gt;
   &lt;!-- 
       The commented section below shows how to use the 'classname' attribute to specify
-      a custom net.sf.click.service.FileUploadService implementation.
+      a custom org.apache.click.service.FileUploadService implementation.
   --&gt;
   &lt;!--
   &lt;file-upload-service classname="com.mycorp.util.CustomFileUploadService"&gt;
@@ -99,7 +99,7 @@
 
   &lt;!-- List controls which will deploy their resources on application startup --&gt;
   &lt;controls&gt;
-      &lt;control classname="net.sf.click.examples.control.FilterPanel"/&gt;
+      &lt;control classname="org.apache.click.examples.control.FilterPanel"/&gt;
       
       &lt;!-- A control-set which refers to a third-party xml file specifying the list of controls to deploy --&gt;
       &lt;control-set name="mycorp-third-party-controls.xml"/&gt;

Modified: incubator/click/trunk/click/documentation/docs/click-dtd.html
URL: http://svn.apache.org/viewvc/incubator/click/trunk/click/documentation/docs/click-dtd.html?rev=731552&r1=731551&r2=731552&view=diff
==============================================================================
--- incubator/click/trunk/click/documentation/docs/click-dtd.html (original)
+++ incubator/click/trunk/click/documentation/docs/click-dtd.html Mon Jan  5 05:09:59 2009
@@ -67,7 +67,7 @@
   &lt;!-- Page template formatter class. An new format object added to
        the Velocity context under the key: "format". --&gt;
   &lt;!ELEMENT <span class="red">format</span> (#PCDATA)&gt;
-    &lt;!ATTLIST <span class="red">format</span> <span class="blue">classname</span> CDATA #FIXED "<span class="green">net.sf.click.util.Format</span>"&gt;
+    &lt;!ATTLIST <span class="red">format</span> <span class="blue">classname</span> CDATA #FIXED "<span class="green">org.apache.click.util.Format</span>"&gt;
  
   &lt;!-- Application mode, which configures logging and caching. --&gt;
   &lt;!ELEMENT <span class="red">mode</span> (#PCDATA)&gt;
@@ -86,7 +86,7 @@
 
   &lt;!-- File Upload Service. --&gt;
   &lt;!ELEMENT <span class="red">file-upload-service</span> (property*)&gt;
-    &lt;!ATTLIST <span class="red">file-upload-service</span> <span class="blue">classname</span> CDATA #FIXED "<span class="green">net.sf.click.service.FileUploadService</span>"&gt;
+    &lt;!ATTLIST <span class="red">file-upload-service</span> <span class="blue">classname</span> CDATA #FIXED "<span class="green">org.apache.click.service.FileUploadService</span>"&gt;
  
     &lt;!-- Property definition. --&gt;
     &lt;!ELEMENT <span class="red">property</span> (#PCDATA)&gt;
@@ -95,11 +95,11 @@
 
   &lt;!-- Log Service. --&gt;
   &lt;!ELEMENT <span class="red">log-service</span> (property*)&gt;
-    &lt;!ATTLIST <span class="red">log-service</span> <span class="blue">classname</span> CDATA #FIXED "<span class="green">net.sf.click.service.ConsoleLogService</span>"&gt;
+    &lt;!ATTLIST <span class="red">log-service</span> <span class="blue">classname</span> CDATA #FIXED "<span class="green">org.apache.click.service.ConsoleLogService</span>"&gt;
  
   &lt;!-- Template Service. --&gt;
   &lt;!ELEMENT <span class="red">template-service</span> (property*)&gt;
-    &lt;!ATTLIST <span class="red">template-service</span> <span class="blue">classname</span> CDATA #FIXED "<span class="green">net.sf.click.service.VelocityTemplateService</span>"&gt;
+    &lt;!ATTLIST <span class="red">template-service</span> <span class="blue">classname</span> CDATA #FIXED "<span class="green">org.apache.click.service.VelocityTemplateService</span>"&gt;
  
 </pre>
 </body>

Modified: incubator/click/trunk/click/documentation/docs/configuration.html
URL: http://svn.apache.org/viewvc/incubator/click/trunk/click/documentation/docs/configuration.html?rev=731552&r1=731551&r2=731552&view=diff
==============================================================================
--- incubator/click/trunk/click/documentation/docs/configuration.html (original)
+++ incubator/click/trunk/click/documentation/docs/configuration.html Mon Jan  5 05:09:59 2009
@@ -76,7 +76,7 @@
 <a name="servlet-configuration" class="heading"></a><h2>1.&nbsp; Servlet Configuration</h2>
 
 For a Click web application to function the 
-<a target="topic" href="click-api/net/sf/click/ClickServlet.html">ClickServlet</a>
+<a target="topic" href="click-api/org/apache/click/ClickServlet.html">ClickServlet</a>
 must be configured in the web application's <tt>/WEB-INF/web.xml</tt> file. 
 A simple web application which maps all <tt>*.htm</tt> requests to a ClickServlet 
 is provided below.
@@ -86,7 +86,7 @@
 
   &lt;servlet&gt;
     &lt;servlet-name&gt;<span class="blue">ClickServlet</span>&lt;/servlet-name&gt;
-    &lt;servlet-class&gt;<span class="red">net.sf.click.ClickServlet</span>&lt;/servlet-class&gt;
+    &lt;servlet-class&gt;<span class="red">org.apache.click.ClickServlet</span>&lt;/servlet-class&gt;
     &lt;load-on-startup&gt;<span class="red">0</span>&lt;/load-on-startup&gt;
   &lt;/servlet&gt;
   
@@ -165,7 +165,7 @@
   
   &lt;mode value="profile"/&gt;
   
-  &lt;log-service classname="net.sf.click.extras.service.Log4JLogService"/&gt;
+  &lt;log-service classname="org.apache.click.extras.service.Log4JLogService"/&gt;
   
 &lt;/click-app&gt; 
 </pre>
@@ -189,14 +189,14 @@
     <li class="items">Velocity templates</li>
     <li class="items">HttpServletRequest character encoding</li>
     <li class="items">Page Content-Type charset, see Page
-        <a href="click-api/net/sf/click/Page.html#getContentType()">getContentType()</a>
+        <a href="click-api/org/apache/click/Page.html#getContentType()">getContentType()</a>
     </li>
 </ul>
 
 The <span class="blue">locale</span> attribute defines the default application
 Locale. If this value is defined it will override Locale returned by the request. 
 Please see the Context  
-<a href="click-api/net/sf/click/Context.html#getLocale()">getLocale()</a>
+<a href="click-api/org/apache/click/Context.html#getLocale()">getLocale()</a>
 for details.
 <p/>
 
@@ -264,7 +264,7 @@
 <p/>
 The Click application will create a new Page instance for the given request using
 the configured page <span class="blue">classname</span>. All pages must subclass 
-<a target="topic" href="click-api/net/sf/click/Page.html">Page</a>  
+<a target="topic" href="click-api/org/apache/click/Page.html">Page</a>  
 and provide a public no arguments constructor, so they can be instantiated.
 <p/>
 Pages can also define <span class="blue">header</span> values which are discussed
@@ -391,7 +391,7 @@
 <li class="items">add any public controls to the page, after the page constructor has been invoked</li>
 <li class="items">if the public control's name is not defined, its name will be set to the the value its field name</li>
 <li class="items">bind any request parameters to public page fields, after page constructor has been invoked.
-See <a href="click-api/net/sf/click/ClickServlet.html#processPageRequestParams(net.sf.click.Page)">ClickServlet.processPageRequestParams(Page)</a>
+See <a href="click-api/org/apache/click/ClickServlet.html#processPageRequestParams(org.apache.click.Page)">ClickServlet.processPageRequestParams(Page)</a>
 for more details
 </li>
 <li class="items">add any public page fields to the page model, before rendering</li>
@@ -467,8 +467,8 @@
 
 Page headers are set after the Page has been constructed and before <tt>onInit()</tt> is called.
 Pages can then modify their 
-<a target="topic" href="click-api/net/sf/click/Page.html#headers">headers</a> property using
-the <a href="click-api/net/sf/click/Page.html#setHeader(java.lang.String, java.lang.Object)">setHeader()</a>
+<a target="topic" href="click-api/org/apache/click/Page.html#headers">headers</a> property using
+the <a href="click-api/org/apache/click/Page.html#setHeader(java.lang.String, java.lang.Object)">setHeader()</a>
 method.
 
 <h4>2.4.1&nbsp; Browser Caching</h4>
@@ -535,11 +535,11 @@
 
 <pre class="codeDtd">
 &lt;!ELEMENT <span class="blue">format</span> (#PCDATA)&gt;
-    &lt;ATTLIST format classname CDATA #FIXED "net.sf.click.util.Format"&gt; 
+    &lt;ATTLIST format classname CDATA #FIXED "org.apache.click.util.Format"&gt; 
 </pre>
 
 By default all Click pages are configured with a 
-<a target="topic" href="click-api/net/sf/click/util/Format.html">net.sf.click.util.Format</a>
+<a target="topic" href="click-api/org/apache/click/util/Format.html">org.apache.click.util.Format</a>
 object. The format object is made available in the Velocity page templates using the name 
 <tt>$<span class="blue">format</span></tt>.
 <p/>
@@ -648,9 +648,9 @@
 <a name="click-logging" class="heading"></a><h4>2.6.2&nbsp; Click and Velocity Logging</h4>
 
 The Click and Velocity runtimes use 
-<a target="topic" href="click-api/net/sf/click/service/LogService.html">LogService</a>
+<a target="topic" href="click-api/org/apache/click/service/LogService.html">LogService</a>
 for logging messages. The default LogService implementation is 
-<a target="topic" href="click-api/net/sf/click/service/ConsoleLogService.html">ConsoleLogService</a>
+<a target="topic" href="click-api/org/apache/click/service/ConsoleLogService.html">ConsoleLogService</a>
 which will send messages to the console [System.out]. 
 For example the following logging output is for a HomePage request when the application
 mode is <tt>trace</tt>: 
@@ -668,8 +668,8 @@
 
 Any unhandled <tt>Throwable</tt> errors are logged by the ClickServlet.
 <p/>
-Note that Click Extras also provide log adaptors for <a target="topic" href="extras-api/net/sf/click/extras/service/Log4JLogService.html">Log4J</a>
-and the <a target="topic" href="extras-api/net/sf/click/extras/service/JdkLogService.html">JDK Logging API</a>.
+Note that Click Extras also provide log adaptors for <a target="topic" href="extras-api/org/apache/click/extras/service/Log4JLogService.html">Log4J</a>
+and the <a target="topic" href="extras-api/org/apache/click/extras/service/JdkLogService.html">JDK Logging API</a>.
 <p/>
 When an application is not in <tt>production</tt> mode the error page displays
 detailed debugging information. When the application mode is <tt>production</tt>
@@ -688,9 +688,9 @@
 </pre>
 
 The <tt><span class="red">control</span></tt> registers 
-<a href="click-api/net/sf/click/Control.html">Control</a>
+<a href="click-api/org/apache/click/Control.html">Control</a>
 classes which
-will have their <a href="click-api/net/sf/click/Control.html#onDeploy(javax.servlet.ServletContext)">onDeploy()</a>
+will have their <a href="click-api/org/apache/click/Control.html#onDeploy(javax.servlet.ServletContext)">onDeploy()</a>
 method invoked when the click application starts.
 
 <pre class="codeDtd">
@@ -750,7 +750,7 @@
 stylesheets, JavaScript etc.) from a Jar to a web applications.
 <ol>
     <li>
-        Through a Control's <a href="click-api/net/sf/click/Control.html#onDeploy(javax.servlet.ServletContext)">onDeploy()</a>
+        Through a Control's <a href="click-api/org/apache/click/Control.html#onDeploy(javax.servlet.ServletContext)">onDeploy()</a>
         event handler. See the <a href="#application-controls">Controls</a> section above.
     </li>
     <li>

Modified: incubator/click/trunk/click/documentation/docs/controls.html
URL: http://svn.apache.org/viewvc/incubator/click/trunk/click/documentation/docs/controls.html?rev=731552&r1=731551&r2=731552&view=diff
==============================================================================
--- incubator/click/trunk/click/documentation/docs/controls.html (original)
+++ incubator/click/trunk/click/documentation/docs/controls.html Mon Jan  5 05:09:59 2009
@@ -64,7 +64,7 @@
 
 
 While this section provides an overview how Controls work please see the 
-<a target="topic" href="click-api/net/sf/click/control/package-summary.html">Javadoc</a>,
+<a target="topic" href="click-api/org/apache/click/control/package-summary.html">Javadoc</a>,
 which provides extensive information and examples.
 
 <a name="control-interface" class="heading"></a><h2>1.&nbsp; Control Interface</h2>
@@ -72,7 +72,7 @@
 display to the user. Controls are equivalent to Visual Basic Controls or Delphi Components.
 <p/>
 Controls handle the processing of user input in the 
-<a target="topic" href="click-api/net/sf/click/Control.html#onProcess()">onProcess</a>
+<a target="topic" href="click-api/org/apache/click/Control.html#onProcess()">onProcess</a>
 method and render their HTML display using the toString() method. The execution
 sequence for a Control being processed and rendered is illustrated below in Figure 1.
 <p/>
@@ -85,7 +85,7 @@
 
 
 In Click all control classes must implement the 
-<a target="topic" href="click-api/net/sf/click/Control.html">Control</a> interface.
+<a target="topic" href="click-api/org/apache/click/Control.html">Control</a> interface.
 The Control interface is depicted below in Figure 2.
 <p>
 <img src="../images/control-class-diagram.png"/>
@@ -96,41 +96,41 @@
 Methods on the Control interface include:
 <ul>
   <li>
-   <a href="click-api/net/sf/click/Control.html#getHtmlImports()">getHtmlImports()</a>
+   <a href="click-api/org/apache/click/Control.html#getHtmlImports()">getHtmlImports()</a>
    &nbsp; - &nbsp; defines the controls HTML header imports.
   </li>
   <li>
-   <a href="click-api/net/sf/click/Control.html#getMessages()">getMessages()</a>
+   <a href="click-api/org/apache/click/Control.html#getMessages()">getMessages()</a>
    &nbsp; - &nbsp; defines the controls localized messages map.
   </li>  
   <li>
-   <a href="click-api/net/sf/click/Control.html#getName()">getName()</a> /
-   <a href="click-api/net/sf/click/Control.html#setName(java.lang.String)">setName()</a>
+   <a href="click-api/org/apache/click/Control.html#getName()">getName()</a> /
+   <a href="click-api/org/apache/click/Control.html#setName(java.lang.String)">setName()</a>
    &nbsp; - &nbsp; defines the controls name in the Page model or Form fields.
   </li>
   <li>
-   <a href="click-api/net/sf/click/Control.html#getParent()">getParent()</a> /
-   <a href="click-api/net/sf/click/Control.html#setParent(java.lang.Object)">setParent()</a>
+   <a href="click-api/org/apache/click/Control.html#getParent()">getParent()</a> /
+   <a href="click-api/org/apache/click/Control.html#setParent(java.lang.Object)">setParent()</a>
    &nbsp; - &nbsp; defines the controls parent.
   </li>  
   <li>
-   <a href="click-api/net/sf/click/Control.html#onDeploy(javax.servlet.ServletContext)">onDeploy()</a>
+   <a href="click-api/org/apache/click/Control.html#onDeploy(javax.servlet.ServletContext)">onDeploy()</a>
    &nbsp; - &nbsp; deploy resources on startup.
   </li>
   <li>
-   <a href="click-api/net/sf/click/Control.html#onInit()">onInit()</a>
+   <a href="click-api/org/apache/click/Control.html#onInit()">onInit()</a>
    &nbsp; - &nbsp; on initialize event handler.
   </li>
   <li>
-   <a href="click-api/net/sf/click/Control.html#onProcess()">onProcess()</a>
+   <a href="click-api/org/apache/click/Control.html#onProcess()">onProcess()</a>
    &nbsp; - &nbsp; process request event handler.
   </li>
   <li>
-   <a href="click-api/net/sf/click/Control.html#onDestroy()">onDestroy()</a>
+   <a href="click-api/org/apache/click/Control.html#onDestroy()">onDestroy()</a>
    &nbsp; - &nbsp; on destroy event handler.
   </li>
   <li>
-   <a href="click-api/net/sf/click/Control.html#render(net.sf.click.util.HtmlStringBuffer)">render()</a>
+   <a href="click-api/org/apache/click/Control.html#render(org.apache.click.util.HtmlStringBuffer)">render()</a>
    &nbsp; - &nbsp; generate the control's HTML representation.
   </li>
 </ul>
@@ -196,11 +196,11 @@
 <a name="control-class" class="heading"></a><h2>3.&nbsp; Control Classes</h2>
 
 Core control classes are defined in the package 
-<a target="topic" href="click-api/net/sf/click/control/package-summary.html">net.sf.click.control</a>.
+<a target="topic" href="click-api/org/apache/click/control/package-summary.html">org.apache.click.control</a>.
 This package includes controls for the essential HTML elements.
 <p/>
 Extended control classes are provided in the Click Extras package
-<a target="topic" href="extras-api/net/sf/click/extras/control/package-summary.html">net.sf.click.extras.control</a>.
+<a target="topic" href="extras-api/org/apache/click/extras/control/package-summary.html">org.apache.click.extras.control</a>.
 Click Extras classes can contain dependencies to 3rd party frameworks.
 <p/>
 A subset of these control classes are depicted below in Figure 3.
@@ -215,19 +215,19 @@
 
 The key control classes include:
 <ul>
-<li><a href="click-api/net/sf/click/control/ActionLink.html">ActionLink</a>
+<li><a href="click-api/org/apache/click/control/ActionLink.html">ActionLink</a>
 - provides an anchor link which can invoke callback listeners. 
 <p></li>
-<li><a href="click-api/net/sf/click/control/Field.html">Field</a>
+<li><a href="click-api/org/apache/click/control/Field.html">Field</a>
 - provides the abstract form field control.
 <p></li>
-<li><a href="click-api/net/sf/click/control/Form.html">Form</a>
+<li><a href="click-api/org/apache/click/control/Form.html">Form</a>
 - provides a form control for processing, validation and rendering.   
 <p></li>
-<li><a href="click-api/net/sf/click/control/Submit.html">Submit</a>
+<li><a href="click-api/org/apache/click/control/Submit.html">Submit</a>
 - provides an input type submit control which can invoke callback listeners.  
 <p></li>
-<li><a href="click-api/net/sf/click/control/TextField.html">TextField</a>
+<li><a href="click-api/org/apache/click/control/TextField.html">TextField</a>
 - provides an input type text control which can invoke callback listeners.  
 <p></li>
 </ul> 
@@ -237,8 +237,8 @@
 accessor methods.
 <p/>
 You can also aggregate controls to build more complex controls. For example the 
-<a href="extras-api/net/sf/click/extras/control/CreditCardField.html">CreditCardField</a>
-uses a <a href="click-api/net/sf/click/control/Select.html">Select</a>
+<a href="extras-api/org/apache/click/extras/control/CreditCardField.html">CreditCardField</a>
+uses a <a href="click-api/org/apache/click/control/Select.html">Select</a>
 control to render the different credit card types. 
 
 <a name="message-properties" class="heading"></a><h2>4.&nbsp; Message Properties</h2>
@@ -361,12 +361,12 @@
 accessed through the Field methods:
 
 <ul>
- <li><a href="click-api/net/sf/click/control/AbstractControl.html#getMessage(java.lang.String)">getMessage(String)</a></li>
- <li><a href="click-api/net/sf/click/control/AbstractControl.html#getMessage(java.lang.String, java.lang.Object)">getMessage(String, Object)</a></li>
- <li><a href="click-api/net/sf/click/control/AbstractControl.html#getMessage(java.lang.String, java.lang.Object[])">getMessage(String, Object[])</a></li>
- <li><a href="click-api/net/sf/click/control/AbstractControl.html#getMessages()">getMessages()</a></li>
- <li><a href="click-api/net/sf/click/control/Field.html#setErrorMessage(java.lang.String)">setErrorMessage(String)</a></li>
- <li><a href="click-api/net/sf/click/control/Field.html#setErrorMessage(java.lang.String, java.lang.Object)">setErrorMessage(String, Object)</a></li>
+ <li><a href="click-api/org/apache/click/control/AbstractControl.html#getMessage(java.lang.String)">getMessage(String)</a></li>
+ <li><a href="click-api/org/apache/click/control/AbstractControl.html#getMessage(java.lang.String, java.lang.Object)">getMessage(String, Object)</a></li>
+ <li><a href="click-api/org/apache/click/control/AbstractControl.html#getMessage(java.lang.String, java.lang.Object[])">getMessage(String, Object[])</a></li>
+ <li><a href="click-api/org/apache/click/control/AbstractControl.html#getMessages()">getMessages()</a></li>
+ <li><a href="click-api/org/apache/click/control/Field.html#setErrorMessage(java.lang.String)">setErrorMessage(String)</a></li>
+ <li><a href="click-api/org/apache/click/control/Field.html#setErrorMessage(java.lang.String, java.lang.Object)">setErrorMessage(String, Object)</a></li>
 </ul>
 
 These methods use the <tt>Locale</tt> of the request to lookup the string resource
@@ -374,19 +374,19 @@
 
 
 <a name="container" class="heading"></a><h2>5.&nbsp; Container</h2>
-<a href="click-api/net/sf/click/control/Container.html">Container</a> is a
+<a href="click-api/org/apache/click/control/Container.html">Container</a> is a
 Control that can contain other Controls, thus forming a hierarchy of components.
 <p/>
 Container enables components to add, remove and retrieve other controls.
 <p/>
 Listed below are example Containers:
 <ul style="margin-top:0.5em;">
-   <li class="item"><a href="click-api/net/sf/click/control/Form.html">Form</a>
+   <li class="item"><a href="click-api/org/apache/click/control/Form.html">Form</a>
    - an HTML form which provides default layout of fields and error feedback.</li>
-   <li class="item"><a href="click-api/net/sf/click/control/Panel.html">Panel</a> - similar to
-   <a href="click-api/net/sf/click/Page.html">Page</a>, this Container provides
+   <li class="item"><a href="click-api/org/apache/click/control/Panel.html">Panel</a> - similar to
+   <a href="click-api/org/apache/click/Page.html">Page</a>, this Container provides
    its own template and model.</li>
-   <li class="item"><a href="click-api/net/sf/click/control/FieldSet.html">FieldSet</a> - draws
+   <li class="item"><a href="click-api/org/apache/click/control/FieldSet.html">FieldSet</a> - draws
    a legend (border) around its child Controls.</li>
 </ul>
 <br/>
@@ -402,8 +402,8 @@
 
 The following classes provides convenient extension points for creating custom Containers:
 <ul style="margin-top:0.5em;">
-  <li class="item"><a href="click-api/net/sf/click/control/AbstractContainer.html">AbstractContainer</a></li>
-  <li class="item"><a href="click-api/net/sf/click/extras/control/AbstractContainerField.html">AbstractContainerField</a></li>
+  <li class="item"><a href="click-api/org/apache/click/control/AbstractContainer.html">AbstractContainer</a></li>
+  <li class="item"><a href="click-api/org/apache/click/extras/control/AbstractContainerField.html">AbstractContainerField</a></li>
 </ul>
 
 Lets cover each of them here.
@@ -505,7 +505,7 @@
 
 <a name="layout" class="heading"></a><h2>6.&nbsp; Layouts</h2>
 
-Controls such as <a href="click-api/net/sf/click/control/Form.html">Form</a>
+Controls such as <a href="click-api/org/apache/click/control/Form.html">Form</a>
 takes care of layout and error reporting automatically, and for many use cases
 auto-layout is good enough.
 
@@ -526,7 +526,7 @@
 
 <a name="template-layout" class="heading"></a><h3>6.1&nbsp; Template layout</h3>
 
-Taking the <a href="click-api/net/sf/click/control/Form.html#manual-layout">Template</a>
+Taking the <a href="click-api/org/apache/click/control/Form.html#manual-layout">Template</a>
 approach works well and it separates the Page and layout logic. For example:
 <pre class="prettyprint">
 // EmployeePage.java
@@ -608,7 +608,7 @@
 
 <p>
 It is also possible to "generify" the layout using template engines.
-<a href="click-api/net/sf/click/control/Form.html#velocity-macros">Macro.vm</a>
+<a href="click-api/org/apache/click/control/Form.html#velocity-macros">Macro.vm</a>
 is an example of a generic form layout using Velocity.
 </p>
 
@@ -619,8 +619,8 @@
 layouts.
 <p/>
 Click extras provides two useful classes in this situation namely,
-<a href="click-api/net/sf/click/extras/control/HtmlForm.html">HtmlForm</a>
-and <a href="click-api/net/sf/click/extras/control/HtmlFieldSet.html">HtmlFieldSet</a>.
+<a href="click-api/org/apache/click/extras/control/HtmlForm.html">HtmlForm</a>
+and <a href="click-api/org/apache/click/extras/control/HtmlFieldSet.html">HtmlFieldSet</a>.
 <p/>
 Unlike Form and FieldSet which renders its controls using a Table layout, HtmlForm
 and HtmlFieldSet renders its controls in the order they were added and does not add

Modified: incubator/click/trunk/click/documentation/docs/developer-guide/contributing.html
URL: http://svn.apache.org/viewvc/incubator/click/trunk/click/documentation/docs/developer-guide/contributing.html?rev=731552&r1=731551&r2=731552&view=diff
==============================================================================
--- incubator/click/trunk/click/documentation/docs/developer-guide/contributing.html (original)
+++ incubator/click/trunk/click/documentation/docs/developer-guide/contributing.html Mon Jan  5 05:09:59 2009
@@ -78,7 +78,7 @@
         <p/>
         To enable your controls to deploy resources on startup either place the resources
         in the Click Extras JAR folder 'META-INF/web/' or use the Control
-        <a href="../click-api/net/sf/click/Control.html#on-deploy">onDeploy()</a> method.
+        <a href="../click-api/org/apache/click/Control.html#on-deploy">onDeploy()</a> method.
         Click extra controls which use the <tt>onDeploy</tt> method should be registered
         in Click Extras JAR <tt>extras-controls.xml</tt> file. See the section
         <a href="../configuration.html#deploying-custom-resources">Deploying Custom Resources</a>

Modified: incubator/click/trunk/click/documentation/docs/error-npe.html
URL: http://svn.apache.org/viewvc/incubator/click/trunk/click/documentation/docs/error-npe.html?rev=731552&r1=731551&r2=731552&view=diff
==============================================================================
--- incubator/click/trunk/click/documentation/docs/error-npe.html (original)
+++ incubator/click/trunk/click/documentation/docs/error-npe.html Mon Jan  5 05:09:59 2009
@@ -53,11 +53,11 @@
 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 	at java.lang.reflect.Method.invoke(Method.java:324)
-	at net.sf.click.util.ClickUtils.invokeListener(ClickUtils.java:188)
-	at net.sf.click.control.ActionLink.onProcess(ActionLink.java:510)
-	at net.sf.click.ClickServlet.processPage(ClickServlet.java:324)
-	at net.sf.click.ClickServlet.handleRequest(ClickServlet.java:210)
-	at net.sf.click.ClickServlet.doGet(ClickServlet.java:154)
+	at org.apache.click.util.ClickUtils.invokeListener(ClickUtils.java:188)
+	at org.apache.click.control.ActionLink.onProcess(ActionLink.java:510)
+	at org.apache.click.ClickServlet.processPage(ClickServlet.java:324)
+	at org.apache.click.ClickServlet.handleRequest(ClickServlet.java:210)
+	at org.apache.click.ClickServlet.doGet(ClickServlet.java:154)
 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)

Modified: incubator/click/trunk/click/documentation/docs/extras-overview.html
URL: http://svn.apache.org/viewvc/incubator/click/trunk/click/documentation/docs/extras-overview.html?rev=731552&r1=731551&r2=731552&view=diff
==============================================================================
--- incubator/click/trunk/click/documentation/docs/extras-overview.html (original)
+++ incubator/click/trunk/click/documentation/docs/extras-overview.html Mon Jan  5 05:09:59 2009
@@ -26,19 +26,19 @@
 Click Extras are packaged as a separated JAR which 
 you can deploy with your application. Extra packages include:
 <ul style="margin-top:0.75em;">
- <li><a href="net/sf/click/extras/cayenne/package-summary.html">Cayenne</a> 
+ <li><a href="org/apache/click/extras/cayenne/package-summary.html">Cayenne</a> 
  - provides Cayenne data aware controls</li>
- <li><a href="net/sf/click/extras/control/package-summary.html">Control</a> 
+ <li><a href="org/apache/click/extras/control/package-summary.html">Control</a> 
  - provides extra controls</li>
- <li><a href="net/sf/click/extras/filter/package-summary.html">Filter</a> 
+ <li><a href="org/apache/click/extras/filter/package-summary.html">Filter</a> 
  - provides GZIP compression Filter</li>
- <li><a href="net/sf/click/extras/graph/package-summary.html">Graphics</a>
+ <li><a href="org/apache/click/extras/graph/package-summary.html">Graphics</a>
  - provides graphic controls</li> 
- <li><a href="net/sf/click/extras/hibernate/package-summary.html">Hibernate</a>
+ <li><a href="org/apache/click/extras/hibernate/package-summary.html">Hibernate</a>
  - provides Hibernate data aware controls</li>
- <li><a href="net/sf/click/extras/panel/package-summary.html">Panel</a> 
+ <li><a href="org/apache/click/extras/panel/package-summary.html">Panel</a> 
  - provides Page Panel containers</li>
- <li><a href="net/sf/click/extras/spring/package-summary.html">Spring</a> 
+ <li><a href="org/apache/click/extras/spring/package-summary.html">Spring</a> 
  - provides Spring integration SpringClickServlet</li>
 </ul>
 </p>
@@ -46,7 +46,7 @@
 <p/>
 Please Note the Cayenne, Hibernate and Spring dependencies are only required if you use these particular features.
 For example if you are using Hibernate for your persistence framework, the
-<a href="../extras-api/net/sf/click/extras/cayenne/CayenneForm.html">CayenneForm</a>
+<a href="../extras-api/org/apache/click/extras/cayenne/CayenneForm.html">CayenneForm</a>
 control will not cause any issues as this class would never be loaded by your application.
 
 <p/>

Modified: incubator/click/trunk/click/documentation/docs/faq.html
URL: http://svn.apache.org/viewvc/incubator/click/trunk/click/documentation/docs/faq.html?rev=731552&r1=731551&r2=731552&view=diff
==============================================================================
--- incubator/click/trunk/click/documentation/docs/faq.html (original)
+++ incubator/click/trunk/click/documentation/docs/faq.html Mon Jan  5 05:09:59 2009
@@ -180,7 +180,7 @@
   not meet all your UI style requirements. 
   <p/>
   Please note the Forms control provides many 
-  <a href="click-api/net/sf/click/control/Form.html#auto-layout">auto layout</a> 
+  <a href="click-api/org/apache/click/control/Form.html#auto-layout">auto layout</a> 
   options, see the <a href="examples.html">click-examples</a> 'Form Properties' 
   for a demonstration. 
   <p/>
@@ -207,7 +207,7 @@
   <u>Use Panel to class to create reusable HTML blocks.</u> 
   <p/>
   The 
-  <a href="click-api/net/sf/click/control/Panel.html">Panel</a> 
+  <a href="click-api/org/apache/click/control/Panel.html">Panel</a> 
   control support custom Velocity templates, which is an ideal way
   to create reusable HTML sections which you can include in many pages.
   Panels also support nested controls, enabling your sections to support 
@@ -218,7 +218,7 @@
   This is easy to do and gives you good reuse across your web application.
   <p/>
   Please see the Form 
-  <a href="click-api/net/sf/click/control/Form.html#velocity-macros">velocity macros</a> 
+  <a href="click-api/org/apache/click/control/Form.html#velocity-macros">velocity macros</a> 
   example, and also see the <a href="examples.html">click-examples</a> 'Velocity Macro' 
   demonstration. 
   </li><li>
@@ -228,7 +228,7 @@
   across your web application. 
   <p/>
   Please see the Form
-  <a href="click-api/net/sf/click/control/Form.html#manual-layout">manual layout</a>
+  <a href="click-api/org/apache/click/control/Form.html#manual-layout">manual layout</a>
   example.
   </li>
   </ol>
@@ -284,7 +284,7 @@
   <dt><b>7.&nbsp; Can you exclude some fields from a Form?</b></dt>
   <dd>
    To exclude some fields from being displayed in a shared Form class use the
-   <a href="click-api/net/sf/click/control/Form.html#removeFields(java.util.List)">Form.removeFields()</a>
+   <a href="click-api/org/apache/click/control/Form.html#removeFields(java.util.List)">Form.removeFields()</a>
    method. 
    <p/>
    You can even do this in your page template. Just make sure you call you call 
@@ -308,7 +308,7 @@
 
    The Page class supports page specific string localisation bundles using the 
    method 
-   <a href="click-api/net/sf/click/Page.html#getMessage(java.lang.String)">getMessage(String)</a>.
+   <a href="click-api/org/apache/click/Page.html#getMessage(java.lang.String)">getMessage(String)</a>.
    For example a Login class with three locale string property files on the classpath:
 <pre class="codeConfig">
 /com/mycorp/pages/Login.properties
@@ -324,7 +324,7 @@
 } </pre>
 
    In your HTML page template you can also access the localize message using
-   the <a href="click-api/net/sf/click/util/MessagesMap.html">MessagesMap</a>
+   the <a href="click-api/org/apache/click/util/MessagesMap.html">MessagesMap</a>
    object which is added to the template using the name "messages". For example:
 
     <pre class="codeHtml">
@@ -335,19 +335,19 @@
    the Javadoc:
    <ul style="margin-top:1em;">
     <li>
-     <a href="click-api/net/sf/click/control/ActionLink.html#getLabel()">ActionLink.getLabel()</a>
+     <a href="click-api/org/apache/click/control/ActionLink.html#getLabel()">ActionLink.getLabel()</a>
     </li>
     <li>
-     <a href="click-api/net/sf/click/control/ActionLink.html#getTitle()">ActionLink.getTitle()</a>
+     <a href="click-api/org/apache/click/control/ActionLink.html#getTitle()">ActionLink.getTitle()</a>
     </li>
     <li>
-     <a href="click-api/net/sf/click/control/Field.html#getLabel()">Field.getLabel()</a>
+     <a href="click-api/org/apache/click/control/Field.html#getLabel()">Field.getLabel()</a>
     </li>
     <li>
-     <a href="click-api/net/sf/click/control/Field.html#getTitle()">Field.getTitle()</a>
+     <a href="click-api/org/apache/click/control/Field.html#getTitle()">Field.getTitle()</a>
     </li>
     <li>
-     <a href="click-api/net/sf/click/control/FieldSet.html#getLegend()">FieldSet.getLegend()</a>
+     <a href="click-api/org/apache/click/control/FieldSet.html#getLegend()">FieldSet.getLegend()</a>
     </li>
    </ul>
 
@@ -358,7 +358,7 @@
 /click-control.properties </pre>  
 
    The field class provides a number of 
-   <a href="click-api/net/sf/click/control/Field.html#getMessage(java.lang.String)">getMessage(String)</a>
+   <a href="click-api/org/apache/click/control/Field.html#getMessage(java.lang.String)">getMessage(String)</a>
    methods which support localized strings and message formatting.
    Please also see the Control topic <a href="controls.html#message-properties">Message Properties</a>.   
   </dd>
@@ -386,7 +386,7 @@
 &lt;/click&gt; </pre>
   This will set the pages <tt>HttpServletResponse</tt> "Content-Type" header to be 
   "text/html;charset=UTF-8". Alternatively you can override the Page 
-  <a href="click-api/net/sf/click/Page.html#getContentType()">getContentType()</a> method
+  <a href="click-api/org/apache/click/Page.html#getContentType()">getContentType()</a> method
   to this content type.
   </dd>
 
@@ -426,7 +426,7 @@
   <p/>
   To prevent users resubmitting a form with the browser back button use the
   Form 
-  <a href="click-api/net/sf/click/control/Form.html#onSubmitCheck(net.sf.click.Page, java.lang.String)">onSubmitCheck()</a>
+  <a href="click-api/org/apache/click/control/Form.html#onSubmitCheck(org.apache.click.Page, java.lang.String)">onSubmitCheck()</a>
   method:
   
 <pre class="codeJava">
@@ -495,7 +495,7 @@
   <dt><b>15.&nbsp; How can you integrate Click into Spring?</b></dt>
   <dd>
    To integrate Spring with Click configure the
-   <a href="extras-api/net/sf/click/extras/spring/SpringClickServlet.html">SpringClickServlet</a>
+   <a href="extras-api/org/apache/click/extras/spring/SpringClickServlet.html">SpringClickServlet</a>
    instead of the normal ClickServlet. The SpringClickServlet is contained in the 
    <a href="extras.html">Extras</a> library.
    <p/>
@@ -539,18 +539,18 @@
    the Servlet context path, e.g. <span class="">/mycorp</span>
   </li>  
   <li>format &nbsp; - &nbsp; 
-   the <a href="click-api/net/sf/click/util/Format.html">Format</a> 
+   the <a href="click-api/org/apache/click/util/Format.html">Format</a> 
     object for formatting the display of objects
   </li>
   <li>forward &nbsp; - &nbsp; 
    the page JSP resource (.jsp file)
   </li>
   <li>messages &nbsp; - &nbsp; 
-   the <a target="topic" href="click-api/net/sf/click/util/MessagesMap.html">MessagesMap</a> adaptor
-   for the Page <a href="click-api/net/sf/click/Page.html#getMessage(java.lang.String)">getMessage()</a>
+   the <a target="topic" href="click-api/org/apache/click/util/MessagesMap.html">MessagesMap</a> adaptor
+   for the Page <a href="click-api/org/apache/click/Page.html#getMessage(java.lang.String)">getMessage()</a>
    method
   </li>
-  <li>path &nbsp; - &nbsp; the mapped request <a href="click-api/net/sf/click/Page.html#path">path</a> 
+  <li>path &nbsp; - &nbsp; the mapped request <a href="click-api/org/apache/click/Page.html#path">path</a> 
     of the page. Note this will have a .htm not a .jsp extension
   </li>
    </ul>
@@ -612,8 +612,8 @@
   <p/>
   If you still need to write unit tests for your Click pages, please read the 
   <a href="mock-api/overview-summary.html">documentation</a> on the
-  <a href="mock-api/net/sf/click/MockContainer.html">MockContainer</a> and
-  <a href="mock-api/net/sf/click/MockContext.html">MockContext</a> classes.
+  <a href="mock-api/org/apache/click/MockContainer.html">MockContainer</a> and
+  <a href="mock-api/org/apache/click/MockContext.html">MockContext</a> classes.
   </dd>
 
 

Modified: incubator/click/trunk/click/documentation/docs/introduction.html
URL: http://svn.apache.org/viewvc/incubator/click/trunk/click/documentation/docs/introduction.html?rev=731552&r1=731551&r2=731552&view=diff
==============================================================================
--- incubator/click/trunk/click/documentation/docs/introduction.html (original)
+++ incubator/click/trunk/click/documentation/docs/introduction.html Mon Jan  5 05:09:59 2009
@@ -47,9 +47,9 @@
 and <a target="_blank" href="http://freemarker.sourceforge.net/">Freemarker</a> are also supported)
 <p>
 This framework uses a single servlet, called
-<a target="topic" href="click-api/net/sf/click/ClickServlet.html">ClickServlet</a>, to
+<a target="topic" href="click-api/org/apache/click/ClickServlet.html">ClickServlet</a>, to
 act as a request dispatcher. When a request arrives ClickServlet creates a 
-<a target="topic" href="click-api/net/sf/click/Page.html">Page</a> object to 
+<a target="topic" href="click-api/org/apache/click/Page.html">Page</a> object to 
 process the request and then uses the page's Velocity template to render the 
 results.
 <p>
@@ -85,7 +85,7 @@
 <span class="kw">package</span> <span class="red">examples.page</span>;
 
 <span class="kw">import</span> java.util.Date;
-<span class="kw">import</span> net.sf.click.Page;
+<span class="kw">import</span> org.apache.click.Page;
 
 <span class="kw">public</span> HelloWorld <span class="kw">extends</span> Page {
 
@@ -147,7 +147,7 @@
 provide user interface functionality. 
 <p/>
 One of the commonly used controls is the 
-<a target="topic" href="click-api/net/sf/click/control/ActionLink.html">ActionLink</a>,
+<a target="topic" href="click-api/org/apache/click/control/ActionLink.html">ActionLink</a>,
 which you can use to have a HTML link call a method on a Page object. For example:
 
 <pre class="codeJava">
@@ -240,7 +240,7 @@
 <a name="simple-table" class="heading"></a><h2>3.&nbsp; Simple Table Example</h2>
 
 One of the most useful Click controls is the 
-<a target="topic" href="click-api/net/sf/click/control/Table.html">Table</a>
+<a target="topic" href="click-api/org/apache/click/control/Table.html">Table</a>
 control.
 <p/>
 
@@ -274,7 +274,7 @@
 } </pre>
 
 In this Page code example a Table control is declared, we set the table's HTML class,
-and then define a number of table <a target="topic" href="click-api/net/sf/click/control/Column.html">Column</a>
+and then define a number of table <a target="topic" href="click-api/org/apache/click/control/Column.html">Column</a>
 objects. In the column definitions we specify the name of the column in the constructor,
 which is used for the table column header and also to specify the row object property 
 to render.
@@ -394,9 +394,9 @@
 } </pre>
 
 In this Page code example a Table control is declared and a number of 
-<a target="topic" href="click-api/net/sf/click/control/Column.html">Column</a>
+<a target="topic" href="click-api/org/apache/click/control/Column.html">Column</a>
 objects are added. A deleteLink 
-<a target="topic" href="click-api/net/sf/click/control/ActionLink.html">ActionLink</a>
+<a target="topic" href="click-api/org/apache/click/control/ActionLink.html">ActionLink</a>
 control is used as a decorator for the "Action" column. This control will invoke the
 Page <tt>onDeleteClick()</tt> method when it is clicked. Finally we have the 
 Page <tt>onRender()</tt> method which is used to populate the Table control with
@@ -440,15 +440,15 @@
 
 <a name="simple-form" class="heading"></a><h2>5.&nbsp; Simple Form Example</h2>
 
-The <a target="topic" href="click-api/net/sf/click/control/Form.html">Form</a> and 
-<a target="topic" href="click-api/net/sf/click/control/Field.html">Field</a> controls
+The <a target="topic" href="click-api/org/apache/click/control/Form.html">Form</a> and 
+<a target="topic" href="click-api/org/apache/click/control/Field.html">Field</a> controls
 are also some of the most commonly used controls in the Click Framework.
 <p/>
 The SimpleForm page below provides a demonstration of using these controls.
 <p/>
 In our example code we have the page's constructor adding a 
-<a target="topic" href="click-api/net/sf/click/control/TextField.html">TextField</a> field and a
-<a target="topic" href="click-api/net/sf/click/control/Submit.html">Submit</a> button to the form.
+<a target="topic" href="click-api/org/apache/click/control/TextField.html">TextField</a> field and a
+<a target="topic" href="click-api/org/apache/click/control/Submit.html">Submit</a> button to the form.
 A page method is also set as a control listener on the form.
 Also note in this example the page's public <span class="st">form</span> field is 
 automatically added to its list of controls.
@@ -621,10 +621,10 @@
 of using Form, Field and FielsSet controls.
 <p/>
 First we have an <tt>AdvancedForm</tt> class which setups up a 
-<a href="click-api/net/sf/click/control/Form.html">Form</a>
+<a href="click-api/org/apache/click/control/Form.html">Form</a>
 in its constructor. 
 The form's investment 
-<a href="click-api/net/sf/click/control/Select.html">Select</a> list is populated
+<a href="click-api/org/apache/click/control/Select.html">Select</a> list is populated
 in the page's <tt>onInit()</tt> method. At this point any page dependencies such
 as the CustomerService should be available.
 <p/>
@@ -785,7 +785,7 @@
 In this example when the OK button is clicked the <tt>onOkClicked()</tt> method is invoked.
 If the form is valid a new customer object is created and the forms field values are copied
 to the new object using the Form 
-<a href="click-api/net/sf/click/control/Form.html#copyTo(java.lang.Object)">copyTo()</a>
+<a href="click-api/org/apache/click/control/Form.html#copyTo(java.lang.Object)">copyTo()</a>
 method. The customer object is then saved, the form's field values are cleared and an
 info message is presented to the user.
 <p/>
@@ -801,7 +801,7 @@
 <p/>
 For fine grained page design you can specifically layout form and fields in 
 your page template. See the <a href="controls.html#template-layout">Template Layout</a>
-section and <a href="click-api/net/sf/click/control/Form.html#form-layout">Form</a>
+section and <a href="click-api/org/apache/click/control/Form.html#form-layout">Form</a>
 Javadoc for more details.
 <p/>
 An alternative approach to page template design is using a programmatic approach.

Modified: incubator/click/trunk/click/documentation/docs/javadoc.html
URL: http://svn.apache.org/viewvc/incubator/click/trunk/click/documentation/docs/javadoc.html?rev=731552&r1=731551&r2=731552&view=diff
==============================================================================
--- incubator/click/trunk/click/documentation/docs/javadoc.html (original)
+++ incubator/click/trunk/click/documentation/docs/javadoc.html Mon Jan  5 05:09:59 2009
@@ -51,7 +51,7 @@
         </p>
     </li>
     <li class="change" style="padding-bottom:0.25em;">
-        <a target='topic' href='click-api/net/sf/click/control/package-summary.html' title=' Controls Javadoc API'>Controls API</a>
+        <a target='topic' href='click-api/org/apache/click/control/package-summary.html' title=' Controls Javadoc API'>Controls API</a>
         &nbsp; - &nbsp;  <i>(click.jar)</i>
         <p> 
         Provides the Core Controls, and provides a short description of each control and corresponding HTML element. 
@@ -67,7 +67,7 @@
         </p>
     </li style="padding-bottom:0.25em;">
         <li class="change">
-        <a target='topic' href='mock-api/net/sf/click/package-summary.html' title=' Mock Javadoc API'>Mock API</a>
+        <a target='topic' href='mock-api/org/apache/click/package-summary.html' title=' Mock Javadoc API'>Mock API</a>
         &nbsp; - &nbsp;  <i>(click-mock.jar)</i>
         <p>
         Provides a library for testing Click Pages and Controls, independent of a Servlet container such as Tomcat or Jetty.

Modified: incubator/click/trunk/click/documentation/docs/mock-overview.html
URL: http://svn.apache.org/viewvc/incubator/click/trunk/click/documentation/docs/mock-overview.html?rev=731552&r1=731551&r2=731552&view=diff
==============================================================================
--- incubator/click/trunk/click/documentation/docs/mock-overview.html (original)
+++ incubator/click/trunk/click/documentation/docs/mock-overview.html Mon Jan  5 05:09:59 2009
@@ -19,21 +19,21 @@
 <body>
 
 	<p>
-    Click Mock provides a full <a href="net/sf/click/package-summary.html">Mock</a> stack which
+    Click Mock provides a full <a href="org/apache/click/package-summary.html">Mock</a> stack which
     allows you to test Controls and Pages without the need for a Servlet container such as Tomcat or Jetty.
     </p>
     <p/>
     The mock package is distributed as a separate jar and is available in the Click distribution you downloaded.
     Look under the <em>dist</em> folder for a jar called <em>click-mock-&lt;version&gt;.jar</em>.
     <p/>
-    For testing purposes there are two classes of interest: <a href="net/sf/click/MockContainer.html" >MockContainer</a>
-    and <a href="net/sf/click/MockContext.html" >MockContext</a>.
+    For testing purposes there are two classes of interest: <a href="org/apache/click/MockContainer.html" >MockContainer</a>
+    and <a href="org/apache/click/MockContext.html" >MockContext</a>.
     <p/><br>
     
     <b>MockContainer</b>
     
     <p/>
-    If you want to test your pages (functional tests) use <a href="net/sf/click/MockContainer.html" >MockContainer</a> 
+    If you want to test your pages (functional tests) use <a href="org/apache/click/MockContainer.html" >MockContainer</a> 
     which simulates a servlet container such as Tomcat or Jetty. With the
     container you can mock page requests, form submissions, file uploads,
     navigation etc.
@@ -56,14 +56,14 @@
         ...
     }
 } </pre>
-    Internally MockContainer creates an instance of <a href="net/sf/click/MockContext.html">MockContext</a>
+    Internally MockContainer creates an instance of <a href="org/apache/click/MockContext.html">MockContext</a>
     and a number of Servlet stubs. Below is the list of stubs created:
     <ul style="margin-top:0.5em;">
-     <li class="item"><a href="net/sf/click/servlet/MockRequest.html">MockRequest</a></li>
-     <li class="item"><a href="net/sf/click/servlet/MockResponse.html">MockResponse</a></li>
-     <li class="item"><a href="net/sf/click/servlet/MockServletContext.html">MockServletContext</a></li>
-     <li class="item"><a href="net/sf/click/servlet/MockServletConfig.html">MockServletConfig</a></li>
-     <li class="item"><a href="net/sf/click/servlet/MockSession.html">MockSession</a></li>
+     <li class="item"><a href="org/apache/click/servlet/MockRequest.html">MockRequest</a></li>
+     <li class="item"><a href="org/apache/click/servlet/MockResponse.html">MockResponse</a></li>
+     <li class="item"><a href="org/apache/click/servlet/MockServletContext.html">MockServletContext</a></li>
+     <li class="item"><a href="org/apache/click/servlet/MockServletConfig.html">MockServletConfig</a></li>
+     <li class="item"><a href="org/apache/click/servlet/MockSession.html">MockSession</a></li>
     </ul>
     <br>
     MockContainer provides various getters to for accessing the Servlet stubs.
@@ -73,8 +73,8 @@
     those instead of creating its own default instances.
     <p/>
     Once created you need to manage the container life cycle through
-    the methods <a href="net/sf/click/MockContainer.html#start()">start</a> and
-    <a href="net/sf/click/MockContainer.html#stop()">stop</a>.
+    the methods <a href="org/apache/click/MockContainer.html#start()">start</a> and
+    <a href="org/apache/click/MockContainer.html#stop()">stop</a>.
     <pre class="prettyprint">
 public class IntegrationTest extends TestCase {
     public void testFirstPage() {
@@ -90,13 +90,13 @@
     }
 } </pre>
     <p/>
-    Http request parameters can be set through <a href="net/sf/click/servlet/MockRequest.html">MockRequest</a>.
+    Http request parameters can be set through <a href="org/apache/click/servlet/MockRequest.html">MockRequest</a>.
     <p/>
     MockContainer also provides a number of convenience methods for this very purpose namely 
-    <a href="net/sf/click/MockContainer.html#setParameter(java.lang.String, java.lang.String)">MockContainer.setParameter(String, String)</a> and
-    <a href="net/sf/click/MockContainer.html#setParameter(java.lang.String, java.io.File, java.lang.String)">MockContainer.setParameter(String, File, String)</a>.
+    <a href="org/apache/click/MockContainer.html#setParameter(java.lang.String, java.lang.String)">MockContainer.setParameter(String, String)</a> and
+    <a href="org/apache/click/MockContainer.html#setParameter(java.lang.String, java.io.File, java.lang.String)">MockContainer.setParameter(String, File, String)</a>.
     <p/>
-    To set request attributes use <a href="net/sf/click/MockContainer.html#setAttribute(java.lang.String, java.lang.Object)">MockContainer.setAttribute(String, Object)</a>.
+    To set request attributes use <a href="org/apache/click/MockContainer.html#setAttribute(java.lang.String, java.lang.Object)">MockContainer.setAttribute(String, Object)</a>.
     <p/>
     The example below shows a complete test:
     <pre class="prettyprint">
@@ -131,13 +131,13 @@
     Form.FORM_NAME must be set to the Form's name, called "form" in this example.
     <p/>
     The Page output is available through
-    <a href="net/sf/click/MockContainer.html#getHtml()">MockContainer.getHtml()</a>.
+    <a href="org/apache/click/MockContainer.html#getHtml()">MockContainer.getHtml()</a>.
     <p/><br>
     
     <b>MockContext</b>
     
     <p/>
-    <a href="net/sf/click/MockContext.html" >MockContext</a> 
+    <a href="org/apache/click/MockContext.html" >MockContext</a> 
     is useful for testing custom controls (components).
     <p/>
     <b>Note</b> that it is not necessary to specify a web directory when using MockContext.
@@ -157,21 +157,21 @@
     MockContext provides a number of <em>initContext</em> that prepares and initializes the
     context:
     <ul style="margin-top:0.5em;">
-     <li class="item"><a href="net/sf/click/MockContext.html#initContext()">initContext()</a></li>
-     <li class="item"><a href="net/sf/click/MockContext.html#initContext(java.lang.String)">initContext(String servletPath)</a></li>
-     <li class="item"><a href="net/sf/click/MockContext.html#initContext(java.util.Locale)">initContext(Locale locale)</a></li>
-     <li class="item"><a href="net/sf/click/MockContext.html#initContext(java.util.Locale,%20java.lang.String)">initContext(Locale locale, String servletPath)</a></li>
-     <li class="item"><a href="net/sf/click/MockContext.html#initContext(net.sf.click.servlet.MockServletConfig,%20net.sf.click.servlet.MockRequest,%20net.sf.click.servlet.MockResponse,%20net.sf.click.ClickServlet)">initContext(MockServletConfig servletConfig, MockRequest request, MockResponse response, ClickServlet clickServlet)</a></li>
+     <li class="item"><a href="org/apache/click/MockContext.html#initContext()">initContext()</a></li>
+     <li class="item"><a href="org/apache/click/MockContext.html#initContext(java.lang.String)">initContext(String servletPath)</a></li>
+     <li class="item"><a href="org/apache/click/MockContext.html#initContext(java.util.Locale)">initContext(Locale locale)</a></li>
+     <li class="item"><a href="org/apache/click/MockContext.html#initContext(java.util.Locale,%20java.lang.String)">initContext(Locale locale, String servletPath)</a></li>
+     <li class="item"><a href="org/apache/click/MockContext.html#initContext(org.apache.click.servlet.MockServletConfig,%20org.apache.click.servlet.MockRequest,%20org.apache.click.servlet.MockResponse,%20org.apache.click.ClickServlet)">initContext(MockServletConfig servletConfig, MockRequest request, MockResponse response, ClickServlet clickServlet)</a></li>
     </ul>
     
     <br>
     The MockContext.initContext methods creates a number of Servlet stubs. Below is the list of stubs created:
     <ul style="margin-top:0.5em;">
-     <li class="item"><a href="net/sf/click/servlet/MockRequest.html">MockRequest</a></li>
-     <li class="item"><a href="net/sf/click/servlet/MockResponse.html">MockResponse</a></li>
-     <li class="item"><a href="net/sf/click/servlet/MockServletContext.html">MockServletContext</a></li>
-     <li class="item"><a href="net/sf/click/servlet/MockServletConfig.html">MockServletConfig</a></li>
-     <li class="item"><a href="net/sf/click/servlet/MockSession.html">MockSession</a></li>
+     <li class="item"><a href="org/apache/click/servlet/MockRequest.html">MockRequest</a></li>
+     <li class="item"><a href="org/apache/click/servlet/MockResponse.html">MockResponse</a></li>
+     <li class="item"><a href="org/apache/click/servlet/MockServletContext.html">MockServletContext</a></li>
+     <li class="item"><a href="org/apache/click/servlet/MockServletConfig.html">MockServletConfig</a></li>
+     <li class="item"><a href="org/apache/click/servlet/MockSession.html">MockSession</a></li>
     </ul>
     <br>
     The example below shows how MockContext can be used to test a custom Control called ValidationField:

Modified: incubator/click/trunk/click/documentation/docs/pages.html
URL: http://svn.apache.org/viewvc/incubator/click/trunk/click/documentation/docs/pages.html?rev=731552&r1=731551&r2=731552&view=diff
==============================================================================
--- incubator/click/trunk/click/documentation/docs/pages.html (original)
+++ incubator/click/trunk/click/documentation/docs/pages.html Mon Jan  5 05:09:59 2009
@@ -82,7 +82,7 @@
 <a name="page-class" class="heading"></a><h2>1.&nbsp; Classes</h2>
 
 All custom Click pages must subclass the
-<a target="topic" href="click-api/net/sf/click/Page.html">Page</a> base class.
+<a target="topic" href="click-api/org/apache/click/Page.html">Page</a> base class.
 The Page class and its associated companion classes, Context and Control, are depicted 
 below in Figure 1.
 
@@ -93,14 +93,14 @@
 - <span class="sparx">created with Enterprise Architect courtesy <a target="blank" href="http://www.sparxsystems.com.au">Sparx Systems</a></span>
 </p>
 
-The Page class provides a <a href="click-api/net/sf/click/Page.html#model">model</a>
+The Page class provides a <a href="click-api/org/apache/click/Page.html#model">model</a>
 attribute which is used to hold all the objects that are rendered in the page's 
 Velocity template. The model may also contain
-<a target="topic" href="click-api/net/sf/click/Control.html">Control</a> objects, which
+<a target="topic" href="click-api/org/apache/click/Control.html">Control</a> objects, which
 provide user interface controls on the Page.
 <p/>
 Pages also have an associated  
-<a target="topic" href="click-api/net/sf/click/Context.html">Context</a> object
+<a target="topic" href="click-api/org/apache/click/Context.html">Context</a> object
 which references all the javax.servlet objects associated with the request. When 
 programming in Click you use the Context object to access HttpServletRequest attributes, 
 parameters and the HttpSession object.
@@ -108,12 +108,12 @@
 The Page class provide a number of empty handler methods which subclasses can override to
 provide functionality:
 <ul>
-  <li><a href="click-api/net/sf/click/Page.html#onSecurityCheck()">onSecurityCheck()</a></li>
-  <li><a href="click-api/net/sf/click/Page.html#onInit()">onInit()</a></li>
-  <li><a href="click-api/net/sf/click/Page.html#onGet()">onGet()</a></li>
-  <li><a href="click-api/net/sf/click/Page.html#onPost()">onPost()</a></li>
-  <li><a href="click-api/net/sf/click/Page.html#onRender()">onRender()</a></li>
-  <li><a href="click-api/net/sf/click/Page.html#onDestroy()">onDestroy()</a></li>
+  <li><a href="click-api/org/apache/click/Page.html#onSecurityCheck()">onSecurityCheck()</a></li>
+  <li><a href="click-api/org/apache/click/Page.html#onInit()">onInit()</a></li>
+  <li><a href="click-api/org/apache/click/Page.html#onGet()">onGet()</a></li>
+  <li><a href="click-api/org/apache/click/Page.html#onPost()">onPost()</a></li>
+  <li><a href="click-api/org/apache/click/Page.html#onRender()">onRender()</a></li>
+  <li><a href="click-api/org/apache/click/Page.html#onDestroy()">onDestroy()</a></li>
 </ul>
 The ClickServlet relies on instantiating Pages using a public no arguments constructor, 
 so when you create Page subclasses you must ensure you don't add an incompatible
@@ -142,7 +142,7 @@
 after a Page's <tt>onInit()</tt> is called, each Control, available at that stage,
 will have their <tt>onInit()</tt> method called.
 <p/>
-The next step is the processing of the Page's <a href="click-api/net/sf/click/Page.html#controls">controls</a>.
+The next step is the processing of the Page's <a href="click-api/org/apache/click/Page.html#controls">controls</a>.
 The ClickSerlvet gets the list of 
 Controls from the page and then iterates through the list calling <tt>onProcess()</tt>. 
 If any of the Control's <tt>onProcess()</tt> methods return false, processing of 
@@ -162,29 +162,29 @@
   </li>  
   <li>cssImports &nbsp; - &nbsp; 
     the CSS imports and style blocks to include in the pages header. 
-    Please see <a href="../click-api/net/sf/click/util/PageImports.html">PageImports</a> 
+    Please see <a href="../click-api/org/apache/click/util/PageImports.html">PageImports</a> 
     for more details.
   </li>
   <li>format &nbsp; - &nbsp; 
-    the <a href="../click-api/net/sf/click/util/Format.html">Format</a> 
+    the <a href="../click-api/org/apache/click/util/Format.html">Format</a> 
     object for formatting the display of objects.
   </li>
   <li>imports &nbsp; - &nbsp; 
     the CSS and JavaScript imports to include in the pages header.
-    Please see <a href="../click-api/net/sf/click/util/PageImports.html">PageImports</a> 
+    Please see <a href="../click-api/org/apache/click/util/PageImports.html">PageImports</a> 
     for more details.
   </li>
   <li>jsImports &nbsp; - &nbsp; 
     the JavaScript imports and script blocks to include in the pages footer. 
-    Please see <a href="../click-api/net/sf/click/util/PageImports.html">PageImports</a> 
+    Please see <a href="../click-api/org/apache/click/util/PageImports.html">PageImports</a> 
     for more details.
   </li>
   <li>messages &nbsp; - &nbsp; 
-   the <a target="topic" href="click-api/net/sf/click/util/MessagesMap.html">MessagesMap</a> adaptor
-   for the Page <a href="click-api/net/sf/click/Page.html#getMessage(java.lang.String)">getMessage()</a>
+   the <a target="topic" href="click-api/org/apache/click/util/MessagesMap.html">MessagesMap</a> adaptor
+   for the Page <a href="click-api/org/apache/click/Page.html#getMessage(java.lang.String)">getMessage()</a>
    method
   </li>
-  <li>path &nbsp; - &nbsp; the <a href="click-api/net/sf/click/Page.html#path">path</a> 
+  <li>path &nbsp; - &nbsp; the <a href="click-api/org/apache/click/Page.html#path">path</a> 
     of the page template to render
   </li>
   <li>request &nbsp; - &nbsp; 
@@ -196,7 +196,7 @@
     object
   </li>
   <li>session &nbsp; - &nbsp; 
-   the <a href="click-api/net/sf/click/util/SessionMap.html">SessionMap</a> adaptor
+   the <a href="click-api/org/apache/click/util/SessionMap.html">SessionMap</a> adaptor
    for the users <a class="external" target="_blank" href="http://java.sun.com/products/servlet/2.3/javadoc/javax/servlet/http/HttpSession.html">HttpSession</a>
   </li>
 </ul>
@@ -285,9 +285,9 @@
 BigDecimal, String and the various Date classes. 
 <p/>
 By default type conversion is performed by the 
-<a target="topic" href="click-api/net/sf/click/util/RequestTypeConverter.html">RequestTypeConverter</a> class
+<a target="topic" href="click-api/org/apache/click/util/RequestTypeConverter.html">RequestTypeConverter</a> class
 which is used by the ClickServlet method
-<a target="topic" href="click-api/net/sf/click/ClickServlet.html#getTypeConverter()">getTypeConverter()</a>.
+<a target="topic" href="click-api/org/apache/click/ClickServlet.html#getTypeConverter()">getTypeConverter()</a>.
 <p/>
 If you need to add support for additional types, you would write your own type
 converter class and subclass the ClickSerlvet to use your custom converter.
@@ -351,7 +351,7 @@
 <a name="page-security" class="heading"></a><h2>4.&nbsp; Security</h2>
 
 Pages provide an 
-<a target="topic" href="click-api/net/sf/click/Page.html#onSecurityCheck()">onSecurityCheck</a> 
+<a target="topic" href="click-api/org/apache/click/Page.html#onSecurityCheck()">onSecurityCheck</a> 
 event handler which application pages can override to implement a programmatic security 
 model. 
 <p/>
@@ -527,7 +527,7 @@
 
 Page forwarding is another way of passing information between pages. In this case
 you create the page to be forwarded to using the Context
-<a href="click-api/net/sf/click/Context.html#createPage(java.lang.String)">createPage()</a> 
+<a href="click-api/org/apache/click/Context.html#createPage(java.lang.String)">createPage()</a> 
 method and then set properties directly on the Page.
 Finally set this page as the page to forward the request to. For example:
 
@@ -599,7 +599,7 @@
 Note how the <font color="red">customer</font> object is passed through to the template in the Page model. This
 approach of using the Page model is not available when you forward to another Page, as
 the first Page object is 
-"<a target="topic" href="click-api/net/sf/click/Page.html#onDestroy()">destroyed</a>"
+"<a target="topic" href="click-api/org/apache/click/Page.html#onDestroy()">destroyed</a>"
 before the second Page object is created and any model values would be lost.
 
 <a name="page-redirect" class="heading"></a><h3>5.3&nbsp; Redirect</h3>
@@ -728,7 +728,7 @@
 <p/>
 To implement templating define a border template base Page 
 which content Pages should extend. The template base Page class overrides the
-Page <a href="click-api/net/sf/click/Page.html#getTemplate()">getTemplate()</a>
+Page <a href="click-api/org/apache/click/Page.html#getTemplate()">getTemplate()</a>
 method, returning the path of the border template to render. For example:
 
 <pre class="codeJava"><span class="kw">public class</span> BorderedPage <span class="kw">extends</span> Page {
@@ -761,7 +761,7 @@
  
 Other pages insert their content into this template using the Velocity 
 <a href="velocity/vtl-reference-guide.html#parse">#parse</a> directive,
-passing it their contents pages <a href="click-api/net/sf/click/Page.html#path">path</a>.
+passing it their contents pages <a href="click-api/org/apache/click/Page.html#path">path</a>.
 The <span class="blue">$path</span> value is automatically added to 
 the VelocityContext by the ClickServlet.
 <p/>
@@ -902,7 +902,7 @@
 </ul>
 
 To make a page stateful you simply need to set the page
-<a target="topic" href="click-api/net/sf/click/Page.html#stateful">stateful</a> 
+<a target="topic" href="click-api/org/apache/click/Page.html#stateful">stateful</a> 
 property to true, have the page implement the <tt>Serializable</tt> interface
 and set the <tt>serialVersionUID</tt> indicator. For example:
 
@@ -911,7 +911,7 @@
 
 <span class="kw">import</span> java.io.Serializable;
 
-<span class="kw">import</span> net.sf.click.Page;
+<span class="kw">import</span> org.apache.click.Page;
  
 <span class="kw">public class</span> SearchPage <span class="kw">extends</span> Page <span class="kw">implements</span> Serializable {
 
@@ -960,18 +960,18 @@
 methods are invoked, and then the Page's <tt>onDestroy()</tt> method is invoked. This
 is your opportunity to de-reference any large sets or graphs. For example the Table 
 control by default de-references its rowList in its
-<a target="topic" href="click-api/net/sf/click/control/Table.html#onDestroy()">onDestory()</a>
+<a target="topic" href="click-api/org/apache/click/control/Table.html#onDestroy()">onDestory()</a>
 method.
 
 <a name="page-error-handling" class="heading"></a><h2>9.&nbsp; Error Handling</h2>
 
 If an Exception occurs processing a Page object or rendering a template the error
 is delegated to the registered handler. The default Click error handler is the
-<a target="topic" href="click-api/net/sf/click/util/ErrorPage.html">ErrorPage</a>,
+<a target="topic" href="click-api/org/apache/click/util/ErrorPage.html">ErrorPage</a>,
 which is automatically configured as:
 
 <pre class="codeConfig">
-&lt;page path="<span class="blue">click/error.htm</span>" classname="<span class="red">net.sf.click.util.ErrorPage</span>"/&gt; 
+&lt;page path="<span class="blue">click/error.htm</span>" classname="<span class="red">org.apache.click.util.ErrorPage</span>"/&gt; 
 </pre>
 
 To register an alternative error handler you must subclass ErrorPage and define
@@ -1007,7 +1007,7 @@
 The Click not found page is automatically configured as:
 
 <pre class="codeConfig">
-&lt;page path="<span class="blue">click/not-found.htm</span>" classname="<span class="red">net.sf.click.Page</span>"/&gt; 
+&lt;page path="<span class="blue">click/not-found.htm</span>" classname="<span class="red">org.apache.click.Page</span>"/&gt; 
 </pre>
 
 You can override the default configuration and specify your own class, but you cannot change the path.
@@ -1021,8 +1021,8 @@
 <a name="page-messages" class="heading"></a><h2>11.&nbsp; Message Properties</h2>
 
 The Page class provides a 
-<a href="click-api/net/sf/click/Page.html#messages">messages</a> property which
-is a <a href="click-api/net/sf/click/util/MessagesMap.html">MessagesMap</a>
+<a href="click-api/org/apache/click/Page.html#messages">messages</a> property which
+is a <a href="click-api/org/apache/click/util/MessagesMap.html">MessagesMap</a>
 of localized messages for the page. These messages are made available
 in the VelocityContext when the page is rendered under the key <tt>messages</tt>.
 So for example if you had a page title message you would access it in your page template as:

Modified: incubator/click/trunk/click/documentation/docs/quick-start.html
URL: http://svn.apache.org/viewvc/incubator/click/trunk/click/documentation/docs/quick-start.html?rev=731552&r1=731551&r2=731552&view=diff
==============================================================================
--- incubator/click/trunk/click/documentation/docs/quick-start.html (original)
+++ incubator/click/trunk/click/documentation/docs/quick-start.html Mon Jan  5 05:09:59 2009
@@ -106,7 +106,7 @@
 
   &lt;servlet&gt;
     &lt;servlet-name&gt;ClickServlet&lt;/servlet-name&gt;
-    &lt;servlet-class&gt;net.sf.click.ClickServlet&lt;/servlet-class&gt;
+    &lt;servlet-class&gt;org.apache.click.ClickServlet&lt;/servlet-class&gt;
     &lt;load-on-startup&gt;0&lt;/load-on-startup&gt;
   &lt;/servlet&gt;
   
@@ -165,7 +165,7 @@
 <pre class="codeJava">
 <span class="kw">package</span> com.quickstart.page;
 
-<span class="kw">import</span> net.sf.click.Page;
+<span class="kw">import</span> org.apache.click.Page;
 
 <span class="kw">public class</span> HomePage <span class="kw">extends</span> Page {
 
@@ -295,7 +295,7 @@
 <pre class="codeJava">
 <span class="kw">package</span> com.quickstart.page;
 
-<span class="kw">import</span> net.sf.click.Page;
+<span class="kw">import</span> org.apache.click.Page;
 
 <span class="kw">public class</span> BorderPage <span class="kw">extends</span> Page {
 



Mime
View raw message