Ergaenzung zu 264: einige fehlende jars und etwas Dokumentation

git-svn-id: https://svn.libreccm.org/ccm/trunk@258 8810af33-2d31-482b-a856-94f89814c4df

tools-ng/ecdc/eclipseConnector/aplaws-tomcat-6.0.18.launch

@@ -17,5 +17,5 @@
 <stringAttribute key="org.eclipse.jdt.launching.MAIN_TYPE" value="org.apache.catalina.startup.Bootstrap"/>
 <stringAttribute key="org.eclipse.jdt.launching.PROGRAM_ARGUMENTS" value="start"/>
 <stringAttribute key="org.eclipse.jdt.launching.PROJECT_ATTR" value="aplaws"/>
-<stringAttribute key="org.eclipse.jdt.launching.VM_ARGUMENTS" value="-Djava.protocol.handler.pkgs=com.arsdigita.util.protocol&#13;&#10;-Dccm.home=${workspace_loc:aplaws}/runtime/apache-tomcat-6.0.18&#13;&#10;-Dcatalina.config=file:///${workspace_loc:aplaws}/runtime/apache-tomcat-6.0.18/conf/catalina.properties&#13;&#10;-Djava.endorsed.dirs=${workspace_loc:aplaws}/runtime/apache-tomcat-6.0.18/common/endorsed&#13;&#10;-Dcatalina.base=${workspace_loc:aplaws}/runtime/apache-tomcat-6.0.18&#13;&#10;-Dcatalina.home=${workspace_loc:aplaws}/runtime/apache-tomcat-6.0.18&#13;&#10;-Xms256m&#13;&#10;-Xmx512m&#13;&#10;-XX:PermSize=128m&#13;&#10;-XX:MaxPermSize=128m&#13;&#10;-server&#13;&#10;-Dccm.conf=${workspace_loc:aplaws}/runtime/apache-tomcat-6.0.18/conf/registry&#13;&#10;-Dcom.arsdigita.util.Assert.enabled=true&#13;&#10;-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl&#13;&#10;-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl&#13;&#10;-Djavax.xml.transform.TransformerFactory=com.icl.saxon.TransformerFactoryImpl&#13;&#10;-Djava.ext.dirs=${env_var:JAVA_HOME}/jre/lib/ext;${env_var:JAVA_HOME}/lib/ext;${workspace_loc:aplaws}/runtime/apache-tomcat-6.0.18/webapps/WEB-INF/system&#13;&#10;-Dlog4j.configuration=file:///${workspace_loc:aplaws}/runtime/apache-tomcat-6.0.18/conf/log4j.xml&#13;&#10;-Dcom.sun.management.jmxremote.port=7105&#13;&#10;-Dcom.sun.management.jmxremote.authenticate=false&#13;&#10;-Dcom.sun.management.jmxremote.ssl=false"/>
+<stringAttribute key="org.eclipse.jdt.launching.VM_ARGUMENTS" value="-Xms256m&#13;&#10;-Xmx512m&#13;&#10;-XX:PermSize=128m&#13;&#10;-XX:MaxPermSize=128m&#13;&#10;-Djava.endorsed.dirs=${workspace_loc:aplaws}/runtime/apache-tomcat-6.0.18/lib/endorsed&#13;&#10;-Djavax.xml.transform.TransformerFactory=com.icl.saxon.TransformerFactoryImpl&#13;&#10;-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl&#13;&#10;-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl&#13;&#10;-Dcatalina.home=${workspace_loc:aplaws}/runtime/apache-tomcat-6.0.18&#13;&#10;-Dcatalina.base=${workspace_loc:aplaws}/runtime/apache-tomcat-6.0.18&#13;&#10;-Dcatalina.config=file:///${workspace_loc:aplaws}/runtime/apache-tomcat-6.0.18/conf/catalina.properties&#13;&#10;-Djava.protocol.handler.pkgs=com.arsdigita.util.protocol&#13;&#10;-Djava.ext.dirs=${env_var:JAVA_HOME}/jre/lib/ext;${env_var:JAVA_HOME}/lib/ext;${workspace_loc:aplaws}/runtime/apache-tomcat-6.0.18/lib/system"/>
 </launchConfiguration>

tools-ng/ecdc/local.ccm.properties

@@ -5,6 +5,7 @@
 ## Usually you will define your own specific bundle!
 #ccm.bundle.folder=${ccm.project.dir}/ccm-ldn-aplaws/bundles/devel
 
+
 ccm.upgrade.package=ccm-xxx
 ccm.upgrade.from.version=x.x.x
 ccm.upgrade.to.version=y.y.y

tools-ng/ecdc/scriptlib/build-ccm.xml

@@ -19,14 +19,6 @@
 		    <sysproperty key="ccm.home" value="${ccm.home}" />
 		    <arg line="load ${applications} --parameter-file ${ccm.bundle.folder}/cfg/integration.properties" />
 		</java>
-        <!--   
-            <sysproperty key="log4j.configuration"
-                         value="file:runtime/${app.server.bundles.name}/conf/log4j.xml" />
-        -->
-        <!--
-			<sysproperty key="java.protocol.handler.pkgs"
-                         value="${java.protocol.handler.pkgs}" />
-        -->
 	</target>
 
     <target name="load-bundle-config" depends="prepare-load">
@@ -79,11 +71,6 @@
 		<tstamp>
 			<format pattern="yyyymmddhhmmss" property="timestamp" />
 		</tstamp>
-		<!-- nolonger in use
-		<move file="${app.server.conf.dir}/registry"
-                      tofile="${app.server.conf.dir}/registry.${timestamp}" preservelastmodified="yes"
-			  failonerror="no" verbose="true" />
-		-->
 
 		<!-- classpath used by command line tools load-bundle, update, ...        -->
 		<path id="ccm.classpath">
@@ -94,6 +81,7 @@
 			<fileset dir="${app.server.webapp.dir}/ROOT/WEB-INF/lib" includes="**/*.jar" />
 		</path>
 	</target>
+
  
    <target name="upgrade" description="Upgrade">
         <fail message="Configure the package being upgraded using the ccm.upgrade.package property">

tools-ng/ecdc/templates/new-app/etc/placeholder.txt

@@ -0,0 +1,13 @@
+   
+Originally, this directory was meant to hold any custom fragments 
+a package will need to add to the system initializer file,
+"enterprise.init", in a file called "enterprise.init.in". When 
+building a project, one of the steps to take was to run a task that 
+concatenates all the appropriate fragments together into one master 
+configuration file.
+
+The enterprise.init file is gone and replaced by a newer
+initialization system.
+                    
+The etc/ directory might also contain custom libraries or other 
+special files a package relies on.

tools-ng/ecdc/templates/new-app/lib/placeholder.txt

@@ -0,0 +1 @@
+   

tools-ng/ecdc/templates/new-app/pdl/placeholder.txt

@@ -0,0 +1,6 @@
+   
+This directory contains the PDL files for custom data objects 
+an application creates and uses. It is organized like Java packages, 
+with directories following a package hierarchy. Like Java, PDL code 
+is organized in packages (called "models"), and PDL objects can extend
+other PDL objects.

tools-ng/ecdc/templates/new-app/sql/placeholder.txt

@@ -0,0 +1,10 @@
+   
+This directory contains the custom SQL files that create, drop,
+aand upgrade the database schema for an application, and a single 
+custom create script ("oracle-se-create.sql", for example) for each 
+supported database. 
+
+SQL files are organized by package and by the database they are 
+appropriate for. Note that auto generated sql, which is what most of 
+your sql will be, only appears in the build and deployment directories,
+not in this sql/ directory!

tools-ng/ecdc/templates/new-app/src/README.txt

@@ -0,0 +1,2 @@
+Folds the Java source code for your package. It is organized according to the 
+standard Java package directory hierarchy.

tools-ng/ecdc/templates/new-app/src/overview.html

@@ -0,0 +1,84 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<html>
+<head>
+<!--
+  Copyright (C) 
+
+  This library is free software; you can redistribute it and/or
+  modify it under the terms of the GNU Lesser General Public License
+  as published by the Free Software Foundation; either version 2.1 of
+  the License, or (at your option) any later version.
+
+  This library is distributed in the hope that it will be useful,
+  but WITHOUT ANY WARRANTY; without even the implied warranty of
+  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+  Lesser General Public License for more details.
+
+  You should have received a copy of the GNU Lesser General Public
+  License along with this library; if not, write to the Free Software
+  Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+
+  Author:  Peter Boy (pboy@users.source forge .net)
+  Since:   2009-05-23
+  Version: $Revision: #1 $ $Date: 2009/05/23 $
+-->
+
+<title>Package: com.arsdigita.util.parameter</title>
+</head>
+
+<body bgcolor="white">
+<!-- Summary (one sentence!) -->
+<p>
+Provides for ...
+</p>
+<p>
+<!-- Description (one or more paragraphs), describe what the package contains
+     and state its purpose                                                      -->
+
+</p>
+<!-- Package Specification if applicable -->
+<!-- - description of / links to any package-wide spec not included in the 
+       rest of javadoc
+     - link to specifications written outside of doc comments, if they contain 
+       assertions not present in the javadoc-generated files.
+-->
+<!--
+<h3>Package Specification</h3>
+<p>
+</p>
+-->
+
+<!-- Related Documentation if applicable 
+     - references to documents like overview, tutorials, examples, demos    -->
+<!--
+<h3>Related Documentation</h3>
+<p>
+</p>
+-->
+
+
+<!-- Class & Interface Summary if applicable
+     describes logical groupings of classes & interfaces  -->
+<!--
+<h3>Class & Interface Summary</h3>
+<p>
+</p>
+-->
+
+
+<!-- Developers Comment if applicable
+     lists possible problems & pitfalls, future plannings  -->
+<!--
+<div style="background-color: #FFFFCC;">
+<h3>Developers Comment</h3>
+<p>
+</p>
+</div>
+-->
+
+<!-- Put @see and @since tags down here. -->
+
+
+</body>
+</html>
+

tools-ng/ecdc/templates/new-app/test/README.txt

@@ -0,0 +1,5 @@
+This holds "Junit" and other test classes for the application.
+Directory "test/" will have at least a "src/" directory underneath 
+it, and it may have other directories holding non-Java files 
+necessary for running your application tests.
+

tools-ng/ecdc/templates/new-app/web/README.txt

@@ -0,0 +1,23 @@
+(Some information here may be outdated.)
+
+This holds files from your application that should be deployed directly
+to the servlet container's "webapp" directory (like the document root
+for a web server, the webapp root is the directory where the servlet 
+container looks for Java classes, and for JSPs and any static files it 
+needs to serve). Under "web/" you will find a "packages/" directory; 
+in a complete application, you might also see a "STATIC/" or 
+"assets/" directory for static files like graphics or CSS.
+
+The "packages/" directory under "web/" deserves a few special words.
+"packages/" is the location for the XSL for an application, and also 
+for any JSPs you may want to include. Note that a ccm package is
+*not* the same thing as a Java package; a CCM application can contain 
+many CCM packages, which can contain many Java packages. The 
+distinction is that a CCM package is represented by a row in a CCM 
+system table, can be mounted at site nodes and can have its own 
+dispatcher. A Java package is simply a unit of code organization, and 
+is not tracked by CCM in any way.
+
+XSL stylesheets for a package go under the "packages/package-name/xsl/"
+directory. Custom JSPs go under the "packages/package-name/www/
+directory.

tools-ng/sql/oracle-se/create_tablespace.sql

@@ -5,10 +5,3 @@ create tablespace aplaws
   autoextend on 
   next 32m maxsize 2048m
   extent management local;
-create tablespace aplaws
-  logging
-  datafile 'aplaws.dbf' 
-  size 32m 
-  autoextend on 
-  next 32m maxsize 2048m
-  extent management local;

tools-ng/sql/oracle-se/create_user.sql

@@ -18,23 +18,3 @@ PROMPT Creating USER ccm
     REVOKE RESOURCE FROM ccm;
 	
 QUIT;
-PROMPT Dropping USER ccm
-
-    DROP USER ccm CASCADE;
-
-PROMPT Creating USER ccm
-
-    CREATE USER ccm
-    IDENTIFIED BY ccm
-    DEFAULT TABLESPACE APLAWS
-    TEMPORARY TABLESPACE TEMP PROFILE DEFAULT
-    QUOTA UNLIMITED ON APLAWS
-    QUOTA 0 ON USERS;
-
-    GRANT CONNECT, RESOURCE, QUERY REWRITE, CTXAPP, CREATE PROCEDURE, CREATE TRIGGER, CREATE TABLE, CREATE VIEW, CREATE SEQUENCE TO ccm;
-
-    REVOKE UNLIMITED TABLESPACE FROM ccm;
-
-    REVOKE RESOURCE FROM ccm;
-	
-QUIT;