xml-xmlbeans-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From daver...@apache.org
Subject cvs commit: xml-xmlbeans/website/src/documentation/resources/images built-with-forrest-button.png group-logo.gif group.svg icon.png project-logo.gif project.svg
Date Thu, 25 Sep 2003 00:47:31 GMT
daveremy    2003/09/24 17:47:31

  Added:       website  forrest-targets.ent forrest.properties status.xml
               website/src/documentation README.txt skinconf.xml
               website/src/documentation/content/xdocs index.xml site.xml
                        tabs.xml
               website/src/documentation/content/xdocs/community index.xml
               website/src/documentation/content/xdocs/documentation
                        index.xml
               website/src/documentation/content/xdocs/projectManagement
                        index.xml
               website/src/documentation/content/xdocs/sourceAndBinaries
                        index.xml
               website/src/documentation/resources/images
                        built-with-forrest-button.png group-logo.gif
                        group.svg icon.png project-logo.gif project.svg
  Log:
  Initial forrest website source.  Contains basic structure of the xmlbeans website
  with content however missing some key things:
  1.  No link to a binary distribution.  Need to work out where and how to
  do this distribution.  Pointing users to CVS for now.
  2.  User doc and javadoc not available from website yet (although they are
  in the source distribution).  Need to create good process for copying the
  doc to the website/documentation/content directory.
  
  Still a lot of other things to do.
  
  This check-in will not result in a new xmlbeans website yet.
  The next step is to get the forrest build into the apache cvs site module.
  
  Revision  Changes    Path
  1.1                  xml-xmlbeans/website/forrest-targets.ent
  
  Index: forrest-targets.ent
  ===================================================================
  <!--
  This build.xml snippet contains Forrest targets for Ant 1.5+.  It checks that
  the user has set ${forrest.home}, either in one of:
    build.properties
    project.properties
    ant.properties
    .ant.properties
  or with the FORREST_HOME environment variable, and prints an informative error
  message if not found.
  
  Usage:
  1) Copy this file to somewhere in your project.
  2) Add the following to the top of your project's Ant build.xml script
  (adjusting the path):
  
    <!DOCTYPE project [
      <!ENTITY forrest-targets SYSTEM "file:./forrest-targets.ent">
    ]>
  
  3) Before the closing '</project>' in your build.xml, add this:
  
    &forrest-targets;
    
  This is like expanding a macro: it pulls in the contents of this file.
  
  A minimal build.xml would thus be:
  
  <!DOCTYPE project [
  <!ENTITY forrest-targets SYSTEM "file:./forrest-targets.ent">
  ]>
  
  <project default="site">
      &forrest-targets;
  </project>
  -->
  
    <target name="site" depends="forrest.init" description="Generates static HTML documentation">
      <ant antfile="${forrest.home}/forrest.antproxy.xml" target="site"/>
    </target>
  
    <target name="webapp" depends="forrest.init" description="Generates an unpackaged webapp of the website">
      <ant antfile="${forrest.home}/forrest.antproxy.xml" target="webapp"/>
    </target>
  
    <target name="war" depends="forrest.init" description="Generates a .war file containing the website">
      <ant antfile="${forrest.home}/forrest.antproxy.xml" target="war"/>
    </target>
  
    <target name="validate" depends="forrest.init" description="Validates XML documentation files">
      <ant antfile="${forrest.home}/forrest.antproxy.xml" target="validate"/>
    </target>
  
    <target name="forrest.init" depends="forrest.sethome, forrest.home.defined"/>
  
    <target name="forrest.sethome" depends="forrest.loadenv,
    forrest.checkenv, forrest.checkhome, forrest.check-build.properties,
    forrest.check-project.properties, forrest.check-ant.properties,
    forrest.check-.ant.properties"/>
  
    <target name="forrest.loadenv" unless="forrest.home.present">
      <property environment="env"/>
      <echo level="verbose">Forrest: Got ${env.FORREST_HOME}</echo>
    </target>
  
    <target name="forrest.checkenv" if="env.FORREST_HOME">
      <echo level="verbose">Found $FORREST_HOME..</echo>
      <property name="forrest.home" location="${env.FORREST_HOME}"/>
      <echo level="verbose">forrest.home set to ${forrest.home}</echo>
      <available file="${forrest.home}" type="dir" property="forrest.home.present"/>
    </target>
  
  
    <target name="forrest.checkhome">
      <available file="${forrest.home}" type="dir" property="forrest.home.present"/>
      <available file="build.properties" type="file" property="build.properties.present"/>
      <available file="project.properties" type="file" property="project.properties.present"/>
      <available file="ant.properties" type="file" property="ant.properties.present"/>
      <available file=".ant.properties" type="file" property=".ant.properties.present"/>
    </target>
  
    <!-- No we can't extract the commonalities below into an antcall'ed target,
    because it wouldn't be able to set forrest.home -->
    <target name="forrest.check-build.properties" unless="forrest.home.present"
    if="build.properties.present">
      <echo level="verbose">Forrest: Checking build.properties..</echo>
      <loadproperties srcfile="build.properties">
        <filterchain>
          <linecontains>
            <contains value="forrest.home"/>
          </linecontains>
        </filterchain>
      </loadproperties>
      <available file="${forrest.home}" type="dir" property="forrest.home.present"/>
  
    </target>
  
    <target name="forrest.check-project.properties" unless="forrest.home.present"
    if="project.properties.present">
      <echo level="verbose">Forrest: Checking project.properties..</echo>
      <loadproperties srcfile="project.properties">
        <filterchain>
          <linecontains>
            <contains value="forrest.home"/>
          </linecontains>
        </filterchain>
      </loadproperties>
      <available file="${forrest.home}" type="dir" property="forrest.home.present"/>
    </target>
  
    <target name="forrest.check-ant.properties" unless="forrest.home.present"
    if="ant.properties.present">
      <echo level="verbose">Forrest: Checking ant.properties..</echo>
      <loadproperties srcfile="ant.properties">
        <filterchain>
          <linecontains>
            <contains value="forrest.home"/>
          </linecontains>
        </filterchain>
      </loadproperties>
      <available file="${forrest.home}" type="dir" property="forrest.home.present"/>
    </target>
  
    <target name="forrest.check-.ant.properties" unless="forrest.home.present"
    if=".ant.properties.present">
      <echo level="verbose">Forrest: Checking .ant.properties..</echo>
      <loadproperties srcfile=".ant.properties">
        <filterchain>
          <linecontains>
            <contains value="forrest.home"/>
          </linecontains>
        </filterchain>
      </loadproperties>
      <available file="${forrest.home}" type="dir" property="forrest.home.present"/>
    </target>
  
    <target name="forrest.home.defined" depends="forrest.sethome" unless="forrest.home.present">
      <property name="path" value="${user.home}/xml-forrest/build/dist/shbat"/>
      <pathconvert targetos="windows" property="winpath">
        <path>
          <pathelement location="${path}"/>
        </path>
      </pathconvert>
      <pathconvert targetos="unix" property="unixpath">
        <path>
          <pathelement
            location="${path}"/>
        </path>
      </pathconvert>
  
      <echo>
        ----------------------------------------------
        To run this target, you need Forrest installed.
        Please do the following:
  
        export CVSROOT=:pserver:anoncvs@cvs.apache.org:/home/cvspublic
        cvs checkout xml-forrest
        cd xml-forrest
        build      (Windows)
        ./build.sh (Unix)
  
        Then either:
  
        - Set FORREST_HOME as the Forrest build instructions describe
        - Create a build.properties, with the forrest.home property pointing to
          the forrest shbat directory, eg:
  
          forrest.home=${winpath}  (Windows)
          forrest.home=${unixpath}  (Unix)
  
          (adjusting the path according to where your xml-forrest is)
        ----------------------------------------------
      </echo>
      <fail message="Need to define $${forrest.home}"/>
    </target>
  
  
  
  1.1                  xml-xmlbeans/website/forrest.properties
  
  Index: forrest.properties
  ===================================================================
  ##############
  # Properties used by forrest.build.xml for building the website
  ##############
  
  # Prints out a summary of Forrest settings for this project
  #forrest.echo=true 
  
  # Project name (used to name .war file)
  #project.name=xmlbeans
  
  # Specifies name of Forrest skin to use
  #project.skin=forrest-site
  #project.skin=forrest-css
  #project.skin=avalon-tigris
  #project.skin=krysalis-site
  
  
  ##############
  # behavioural properties
  #project.menu-scheme=tab_attributes
  #project.menu-scheme=directories
  
  ##############
  # layout properties
  
  # Properties that must be set to override the default locations
  #
  # Parent properties must be set. This usually means uncommenting
  # project.content-dir if any other property using it is uncommented
  
  #project.status=status.xml
  #project.content-dir=src/documentation
  #project.conf-dir=${project.content-dir}/conf
  #project.sitemap-dir=${project.content-dir}
  #project.xdocs-dir=${project.content-dir}/content/xdocs
  #project.resources-dir=${project.content-dir}/resources
  #project.stylesheets-dir=${project.resources-dir}/stylesheets
  #project.images-dir=${project.resources-dir}/images
  #project.schema-dir=${project.resources-dir}/schema
  #project.skins-dir=${project.content-dir}/skins
  #project.skinconf=${project.content-dir}/skinconf.xml
  #project.lib-dir=${project.content-dir}/lib
  #project.classes-dir=${project.content-dir}/classes
  
  
  ##############
  # Cocoon catalog entity resolver properties
  
  # A local OASIS catalog file to supplement the default Forrest catalog
  #project.catalog=${project.schema-dir}/catalog.xcat
  
  # The verbosity level for the entity resolver (1..10)
  #forrest.catalog.verbosity=1
  
  
  ##############
  # validation properties
  
  # These props determine if validation is performed at all
  # Values are inherited unless overridden.
  # Eg, if forrest.validate=false, then all others are false unless set to true.
  #forrest.validate=true
  #forrest.validate.xdocs=${forrest.validate}
  #forrest.validate.skinconf=${forrest.validate}
  #forrest.validate.sitemap=${forrest.validate}
  #forrest.validate.stylesheets=${forrest.validate}
  #forrest.validate.skins=${forrest.validate}
  #forrest.validate.skins.stylesheets=${forrest.validate.skins}
  
  
  # Key:
  # *.failonerror=(true|false)    stop when an XML file is invalid
  # *.includes=(pattern)         Comma-separated list of path patterns to validate
  # *.excludes=(pattern)         Comma-separated list of path patterns to not validate
  
  #forrest.validate.failonerror=true
  #forrest.validate.includes=**/*
  #forrest.validate.excludes=
  #
  #forrest.validate.xdocs.failonerror=${forrest.validate.failonerror}
  #
  #forrest.validate.xdocs.includes=**/*.x*
  #forrest.validate.xdocs.excludes=site.xml
  #
  #forrest.validate.skinconf.includes=${skinconf-file}
  #forrest.validate.skinconf.excludes=
  #forrest.validate.skinconf.failonerror=${forrest.validate.failonerror}
  #
  #forrest.validate.sitemap.includes=${sitemap-file}
  #forrest.validate.sitemap.excludes=
  #forrest.validate.sitemap.failonerror=${forrest.validate.failonerror}
  #
  #forrest.validate.stylesheets.includes=**/*.xsl
  #forrest.validate.stylesheets.excludes=
  #forrest.validate.stylesheets.failonerror=${forrest.validate.failonerror}
  #
  #forrest.validate.skins.includes=**/*
  #forrest.validate.skins.excludes=**/*.xsl
  #forrest.validate.skins.failonerror=${forrest.validate.failonerror}
  #
  #forrest.validate.skins.stylesheets.includes=**/*.xsl
  #forrest.validate.skins.stylesheets.excludes=
  #forrest.validate.skins.stylesheets.failonerror=${forrest.validate.skins.failonerror}
  
  ##############
  # General Forrest properties
  
  # The URL to start crawling from
  #project.start-uri=index.html
  # Set logging level for messages printed to the console
  # (DEBUG, INFO, WARN, ERROR, FATAL_ERROR)
  #project.debuglevel=ERROR
  # Max memory to allocate to Java
  #forrest.maxmemory=64m
  # Any other arguments to pass to the JVM. For example, to run on an X-less
  # server, set to -Djava.awt.headless=true
  #forrest.jvmargs=
  #project.bugtracking-url=http://nagoya.apache.org/bugzilla/show_bug.cgi?id=
  
  
  
  1.1                  xml-xmlbeans/website/status.xml
  
  Index: status.xml
  ===================================================================
  <?xml version="1.0"?>
  <status>
  
    <developers>
      <person name="Joe Bloggs"      email="joe@joescompany.org"      id="JB" />
      <!-- Add more people here -->
    </developers>
  
    <todo>
      <actions priority="high">
        <action context="docs" dev="JB">
          Customize this template project with your project's details.  This
          TODO list is generated from 'status.xml'.
        </action>
        <action context="docs" dev="JB">
          Add lots of content.  XML content goes in
          <code>src/documentation/content/xdocs</code>, or wherever the
          <code>${project.xdocs-dir}</code> property (set in
          <code>forrest.properties</code>) points.
        </action>
        <action context="feedback" dev="JB">
          Mail <link
            href="mailto:forrest-dev@xml.apache.org">forrest-dev@xml.apache.org</link>
          with feedback.
        </action>
      </actions>
      <!-- Add todo items. @context is an arbitrary string. Eg:
      <actions priority="high">
        <action context="code" dev="SN">
        </action>
      </actions>
      <actions priority="medium">
        <action context="docs" dev="open">
        </action>
      </actions>
      -->
    </todo>
  
    <changes>
      <!-- Add new releases here -->
      <release version="0.1" date="2002">
        <!-- Some action types have associated images. By default, images are
        defined for 'add', 'fix', 'remove' and 'update'. If you add
        src/documentation/resources/images/<foo>.jpg images, these will
          automatically be used for entries of type <foo>. -->
  
            <action dev="JB" type="add" context="admin">
              Initial Import
            </action>
            <!-- Sample action:
            <action dev="JB" type="fix" due-to="Joe Contributor"
              due-to-email="joec@apache.org" fixes-bug="123">
              Fixed a bug in the Foo class.
            </action>
            -->
          </release>
        </changes>
      </status>
  
  
  
  1.1                  xml-xmlbeans/website/src/documentation/README.txt
  
  Index: README.txt
  ===================================================================
  This is the base documentation directory. It usually contains two files:
  
  skinconf.xml     # This file customizes Forrest for your project. In it, you
                   # tell forrest the project name, logo, copyright info, etc
  
  sitemap.xmap     # Optional. This sitemap overrides the default one bundled
                   # with Forrest. Typically, one would copy a sitemap from
                   # xml-forrest/src/resources/conf/sitemap.xmap, and customize
                   # it.
  
  
  
  
  1.1                  xml-xmlbeans/website/src/documentation/skinconf.xml
  
  Index: skinconf.xml
  ===================================================================
  <?xml version="1.0"?>
  <!--
  Skin configuration file. This file contains details of your project, which will
  be used to configure the chosen XMLBeans skin.
  -->
  <!DOCTYPE skinconfig [
  	<!ENTITY % links.att 'name CDATA #REQUIRED'>
  	<!ENTITY % link.att 'name CDATA #REQUIRED href CDATA #REQUIRED'>
  	<!ELEMENT skinconfig (disable-search?, disable-print-link?, disable-pdf-link?, disable-xml-link?, disable-compliance-links?, searchsite-domain?, searchsite-name?, project-name, project-url, project-logo, group-name?, group-url?, group-logo?, host-url?, host-logo?, year?, vendor?, trail?, toc?, credits?)*>
  	<!ELEMENT credits (credit*)>
  	<!ELEMENT credit (name, url, image?, width?, height?)>
  	<!-- id uniquely identifies the tool, and role indicates its function -->
  	<!ATTLIST credit
  	id CDATA #IMPLIED
  		role CDATA #IMPLIED
  >
  	<!ELEMENT disable-search (#PCDATA)>
  	<!ELEMENT disable-print-link (#PCDATA)>
  	<!ELEMENT disable-pdf-link (#PCDATA)>
  	<!ELEMENT disable-xml-link (#PCDATA)>
  	<!ELEMENT disable-compliance-links (#PCDATA)>
  	<!ELEMENT searchsite-domain (#PCDATA)>
  	<!ELEMENT searchsite-name (#PCDATA)>
  	<!ELEMENT project-name (#PCDATA)>
  	<!ELEMENT project-url (#PCDATA)>
  	<!ELEMENT project-logo (#PCDATA)>
  	<!ELEMENT group-name (#PCDATA)>
  	<!ELEMENT group-url (#PCDATA)>
  	<!ELEMENT group-logo (#PCDATA)>
  	<!ELEMENT host-url (#PCDATA)>
  	<!ELEMENT host-logo (#PCDATA)>
  	<!ELEMENT year (#PCDATA)>
  	<!ELEMENT vendor (#PCDATA)>
  	<!ELEMENT trail (link1, link2, link3)>
  	<!ELEMENT link1 EMPTY>
  	<!-- Seems we can't use param entity refs until this is DTDified -->
  	<!ATTLIST link1
  	name CDATA #REQUIRED
  		href CDATA #IMPLIED
  >
  	<!ELEMENT link2 EMPTY>
  	<!ATTLIST link2
  	name CDATA #REQUIRED
  		href CDATA #IMPLIED
  >
  	<!ELEMENT link3 EMPTY>
  	<!ATTLIST link3
  	name CDATA #REQUIRED
  		href CDATA #IMPLIED
  >
  	<!ELEMENT name (#PCDATA)>
  	<!ELEMENT url (#PCDATA)>
  	<!ELEMENT image (#PCDATA)>
  	<!ELEMENT width (#PCDATA)>
  	<!ELEMENT height (#PCDATA)>
  	<!ELEMENT toc EMPTY>
  	<!ATTLIST toc
  	level CDATA #IMPLIED
  >
  ]>
  <skinconfig>
  	<!-- Do we want to disable the Google search box? -->
  	<disable-search>false</disable-search>
  	<!-- Do we want to disable the print link? -->
  	<disable-print-link>true</disable-print-link>
  	<!-- Do we want to disable the PDF link? -->
  	<disable-pdf-link>false</disable-pdf-link>
  	<!-- Do we want to disable the xml source link? -->
  	<disable-xml-link>true</disable-xml-link>
  	<!-- Do we want to disable w3c compliance links? -->
  	<disable-compliance-links>false</disable-compliance-links>
  	<searchsite-domain>xml.apache.org</searchsite-domain>
  	<searchsite-name>Apache XML</searchsite-name>
  	<!-- mandatory project logo
         skin: XMLBeans-site renders it at the top -->
  	<project-name>XMLBeans</project-name>
  	<project-url>http://xml.apache.org/xmlbeans/</project-url>
  	<project-logo>images/project-logo.gif</project-logo>
  	<!-- optional group logo
         skin: XMLBeans-site renders it at the top-left corner -->
  	<group-name>Apache XML</group-name>
  	<group-url>http://xml.apache.org/</group-url>
  	<group-logo>images/group-logo.gif</group-logo>
  	<!-- optional host logo (e.g. sourceforge logo)
         skin: XMLBeans-site renders it at the bottom-left corner -->
  	<host-url/>
  	<host-logo/>
  	<!-- The following are used to construct a copyright statement -->
  	<year>2002-2003</year>
  	<vendor>The Apache Software Foundation.</vendor>
  	<!-- Some skins use this to form a 'breadcrumb trail' of links. If you don't
    want these, set the attributes to blank. The DTD purposefully requires them.
    -->
  	<trail>
  		<link1 name="apache" href="http://www.apache.org/"/>
  		<link2 name="xml.apache" href="http://xml.apache.org/"/>
  		<link3 name="xmlbeans" href="http://xml.apache.org/xmlbeans"/>
  	</trail>
  	<!-- Configure how many "section" levels need to be included in the
    generated Table of Contents (TOC). By default, if no toc element is provided
    below, then 2 levels are included. Level 0 does not generate any TOC at all.
    -->
  	<toc level="2"/>
  	<!-- Credits are typically rendered as a set of small clickable images in the
    page footer -->
  	<credits>
  		<credit>
  			<name>Built with Forrest</name>
  			<url>http://xml.apache.org/forrest/</url>
  			<image>images/built-with-forrest-button.png</image>
  			<width>88</width>
  			<height>31</height>
  		</credit>
  	</credits>
  </skinconfig>
  
  
  
  1.1                  xml-xmlbeans/website/src/documentation/content/xdocs/index.xml
  
  Index: index.xml
  ===================================================================
  <?xml version="1.0" encoding="UTF-8"?>
  <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "document-v12.dtd">
  <document>
  	<header>
  		<title>Welcome to XMLBeans</title>
  	</header>
  	<body>
  		<section>
  			<title>Introduction to XMLBeans</title>
  			<p>XMLBeans is a tool that allows you to access the <em>full</em> power of XML in a Java friendly way.  It is an XML-Java binding tool.  The idea is that you can 
  			take advantage the richness and features of XML and XML Schema and have these features mapped as naturally as possible to the equivalent Java language and typing 
  			constructs.  XMLBeans uses XML Schema to <em>compile</em> Java interfaces and classes that you can then use to access and modify XML instance data.  
  			Using XMLBeans is similar to using any other Java interface/class, you will see things like <code>getFoo</code> or <code>setFoo</code> just as 
  			you would
  			expect when working with Java.  While a major use of XMLBeans is to access your XML instance data with strongly typed Java classes there are also
  			API's that allow you access to the full XML infoset (XMLBeans keeps full XML Infoset fidelity) as well as to allow you to <em>reflect</em> into the XML schema
  			itself through an XML Schema Object model.</p>
  			<p>For more details on XMLBeans see the <link href="http://nagoya.apache.org/wiki/apachewiki.cgi?XmlBeansExplanation">XMLBeans Explanation</link> Wiki page. 
  			As well as the XMLBeans documentation (see the Documentation tab on this website as well as the docs directory in the XMLBeans Source).</p>
  			<section>
  				<title>What makes XMLBeans Different</title>
  				<p>There are at least two major things that make XMLBeans unique from other XML-Java binding options.</p>
  				<ol>
  					<li>
  						<strong>Full XML Schema support.</strong> XMLBeans fully supports XML Schema and the corresponding java classes provide constructs
        					for all of the major functionality of XML Schema.  This is critical since often times you do not have control over the features of XML Schema
        					that you need to work with in Java.  Also, XML Schema oriented applications can take full advantage of the power of XML Schema and not
        					have to restrict themselvs to a subset.</li>
  					<li>
  						<strong>Full XML Infoset fidelity.</strong>When unmarshalling an XML instance the full XML infoset is kept and is available to the developer.  This is
        					critical because because of the subset of XML that is not easily represented in java.   For example, order of the elements or comments might
        					be needed in a particular application.</li>
  				</ol>
  				<p>A major objective of XMLBeans has been to be applicable in <em>all</em> non-streaming (in memory) XML programming situations.  You should be
        				able to compile your XML Schema into a set of java classes and know that 1) you will be able to use XMLBeans for all of the schemas you encounter
        				(even the warped ones) and 2) that you will be able to get to the XML at whatever level is necessary - and not have to resort to multple
        				tools to do this.</p>
  				<p>To accomplish this XMLBeans provides three major APIs:</p>
  				<ul>
  					<li>
  						<strong>XmlObject</strong>  The java classes that are generated from an XML Schema are all derived from XmlObject.  These provide strongly
        					typed getters and setters for each of the elements within the defined XML.  Complex types are in turn XmlObjects.  For example getCustomer
        					might return a CustomerType (which is an XmlObject).  Simple types turn into simple getters and setters with the correct java type.  For
        					example getName might return a String.</li>
  					<li>
  						<strong>XmlCursor</strong> From any XmlObject you can get an XmlCursor.  This provides efficient, low level access to the XML Infoset.  A cursor 
        					represents a position in the XML instance.  You can move the cursor around the XML instance at any level of granularity you need
        					from individual characters to Tokens.</li>
  					<li>
  						<strong>SchemaType</strong>  XMLBeans provides a full XML Schema object model that you can use to reflect on the underlying schema meta information.
        					For example, you might want to generate a sample XML instance for an XML schema or perhaps find the enumerations for an element
        					so that you can display them.</li>
  				</ul>
  				<p>All of this was built with performance in mind.   Informal benchmarks and user feedback indicate that XMLBeans is extremely fast.</p>
  			</section>
  		</section>
  		<section>
  			<title>History</title>
  			<p>XMLBeans was submitted to Apache by BEA Systems in September 2003 and is currently in the Apache incubation process.  
  			XMLBeans was originally created because of the need seen by developers, in particular David Bau 
  			(<link href="http://nagoya.apache.org/eyebrowse/ReadMsg?listName=xmlbeans-dev@xml.apache.org&amp;msgNo=93">David's about me post</link>),  
  			need for a more XML centric Java binding model that nothing on the market offered.   XMLBeans 1.0 has been successfully used as an underlying technology for several
  			products as well as by a growing number of large users including some of the largest companies in the world.</p>
  		</section>
  		<section>
  			<title>Future</title>
  			<p>The future of XMLBeans is exciting and you are invited to contribute.  XMLBeans Version 1 is a great, stable technology that will continue to 
  			improve going forward.  Its emphasis on full support for XML Schema and the XML Infoset along with it's performance
  			charactaristics make it a great choice for in-memory XML-Java programming. </p>
  			<p>Work has begun on planning XMLBeans 2.0.  At this point it appears that the major emphasis for XMLBeans 2.0 are new use cases that expand
  			the breadth of XMLBeans.  The observation is that XML-Java binding occurs in situations that XMLBeans could be optimized for, areas
  			such as Web Services (XMLBeans works well now in many Web Services situations) and Java to XML Schema scenarios .  
  			See the <link href="http://nagoya.apache.org/wiki/apachewiki.cgi?XmlBeansRoadMap">XMLBeans Roadmap</link> and the 
  			<link href="http://nagoya.apache.org/wiki/apachewiki.cgi?XmlBeansFeaturePlan">XMLBeans Feature Plan</link> wiki page for
  			more information.  XMLBeans is actively looking for contributors and committers so, if you are interested, please join in.</p>
  		</section>
  	</body>
  </document>
  
  
  
  1.1                  xml-xmlbeans/website/src/documentation/content/xdocs/site.xml
  
  Index: site.xml
  ===================================================================
  <?xml version="1.0"?>
  <!--
  Forrest site.xml
  
  This file contains an outline of the site's information content.  It is used to:
  - Generate the website menus (though these can be overridden - see docs)
  - Provide semantic, location-independent aliases for internal 'site:' URIs, eg
  <link href="site:changes"> links to changes.html (or ../changes.html if in
    subdir).
  - Provide aliases for external URLs in the external-refs section.  Eg, <link
    href="ext:cocoon"> links to http://xml.apache.org/cocoon/ 
  
  See http://xml.apache.org/forrest/linking.html for more info
  -->
  <site label="XMLBeans" href="" xmlns="http://apache.org/forrest/linkmap/1.0" tab="">
  	<about label="About">
  		<index label="Index" href="index.html" description="Welcome to XMLBeans"/>
  		<proposal label="Proposal" href="http://nagoya.apache.org/wiki/apachewiki.cgi?XmlBeansProposal" description="The original XMLBeans Project Proposal"/>
  		<todo label="To Do" href="http://nagoya.apache.org/wiki/apachewiki.cgi?XMLBeansToDo" description="Action items, mostly regarding incubation exit criteria"/>
  		<!--
  		<all_site label="Full HTML" href="site.html" />
  		<all_sitePDF label="Full PDF" href="site.pdf" />
  		-->
  	</about>
  	<sourceAndBinaries label="Source and Binaries" href="sourceAndBinaries/" tab="sourceAndBinaries">
  		<version1 label="Version 1 Binaries and Dev Kit" href="index.html#XMLBeans Version 1 Binary and Development Kit" description="XMLBeans Development Kit provides binaries as well as utilities and doc"/>
  		<source label="Source Access" href="index.html#XMLBeans+Source" description="Information on getting XMLBeans source"/>
  	</sourceAndBinaries>
  	<documentation label="Documentation" href="documentation/" tab="documentation">
  		<faq label="XMLBeans FAQ" href="index.html#FAQ" description="XMLBeans Frequently Asked Questions"/>
  		<userdoc label="Version 1 User Documentation" href="index.html#XMLBeans+Version+1+User+Documentation" description="XMLBeans Version 1 User Documentation"/>
  		<userdoc label="Version 1 JavaDoc" href="index.html#XMLBeans+Version+1+JavaDoc" description="XMLBeans Version 1 JavaDoc"/>
  	</documentation>
  	<community label="Community" href="community/" tab="community">
  		<mailingLists label="Mailing Lists" href="index.html#Mailing+Lists" description="Mailing List Information"/>
  		<whoWeAre label="Who we are" href="index.html#Who+we+are" description="List of committers"/>
  	</community>
  	<projectManagement label="Project Managment" href="projectManagement/" tab="projectManagement">
  		<version1 label="Version 1 Project Management" href="index.html#XMLBeans+Version+1+Project+Management" description="Information on the progress of XMLBeans Version 1"/>
  		<version2 label="Version 2 Project Management" herf="index.html#XMLBeans+Version+2+Project+Management" description="Information on the progress of XMLBeans Version 2"/>
  		<bugs label="XMLBeans Bug Tracking" href="index.html#XMLBeans+Bug+Tracking" description="Where to find or log bugs for XMLBeans"/>
  	</projectManagement>
  	<all>
  		<whole_site_html label="Whole Site HTML" href="site.html"/>
  		<whole_site_html label="Whole Site PDF" href="site.pdf"/>
  	</all>
  	<external-refs>
  		<xml.apache.org href="http://xml.apache.org/">
  			<forrest href="forrest/">
  				<validation href="validation.html"/>
  				<webapp href="your-project.html#webapp"/>
  				<document-v12 href="document-v12.html"/>
  			</forrest>
  			<cocoon href="cocoon/"/>
  		</xml.apache.org>
  		<mailsubuser label="XmlBeans User List Subscribe" href="mailto:xmlbeans-user-subscribe@xml.apache.org"/>
  		<mailunsubuser label="XmlBeans User List UnSubscribe" href="mailto:xmlbeans-user-unsubscribe@xml.apache.org"/>
  		<mailsubdev label="XmlBeans Dev List Subscribe" href="mailto:xmlbeans-dev-subscribe@xml.apache.org"/>
  		<mailunsubdev label="XmlBeans Dev List UnSubscribe" href="mailto:xmlbeans-dev-unsubscribe@xml.apache.org"/>
  		<mailsubcvs label="XmlBeans CVS List Subscribe" href="mailto:xmlbeans-cvs-subscribe@xml.apache.org"/>
  		<mailunsubcvs label="XmlBeans CVS List UnSubscribe" href="mailto:xmlbeans-cvs-unsubscribe@xml.apache.org"/>
  		<userlistarchive label="XmlBeams User List Archive" href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=152"/>
  		<devlistarchive label="XmlBeans Dev List Archive" href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=151"/>
  		<cvslistarchive label="XmlBeans CVS List Archive" href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=150"/>
  	</external-refs>
  </site>
  
  
  
  1.1                  xml-xmlbeans/website/src/documentation/content/xdocs/tabs.xml
  
  Index: tabs.xml
  ===================================================================
  <?xml version="1.0" encoding="UTF-8"?>
  <!DOCTYPE tabs PUBLIC "-//APACHE//DTD Cocoon Documentation Tab V1.0//EN" "http://apache.org/forrest/dtd/tab-cocoon-v10.dtd">
  <tabs software="MyProj" title="MyProj" copyright="Foo" xmlns:xlink="http://www.w3.org/1999/xlink">
  	<!-- The rules are:
      @dir will always have '/@indexfile' added.
      @indexfile gets appended to @dir if the tab is selected. Defaults to 'index.html'
      @href is not modified unless it is root-relative and obviously specifies a
      directory (ends in '/'), in which case /index.html will be added
      If @id's are present, site.xml entries with a matching @tab will be in that tab.
       -->
  	<tab id="" label="Home" dir="" indexfile="index.html"/>
  	<tab id="sourceAndBinaries" label="Source and Binaries" dir="sourceAndBinaries"/>
  	<tab id="documentation" label="Documentation" dir="documentation"/>
  	<tab id="community" label="Community" dir="community"/>
  	<tab id="projectManagement" label="Project Management" dir="projectManagement"/>
  </tabs>
  
  
  
  1.1                  xml-xmlbeans/website/src/documentation/content/xdocs/community/index.xml
  
  Index: index.xml
  ===================================================================
  <?xml version="1.0" encoding="UTF-8"?>
  <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "http://apache.org/forrest/dtd/document-v12.dtd">
  <document>
  	<header>
  		<title>XMLBeans Community</title>
  	</header>
  	<body>
  		<section>
  			<title>Mailing Lists</title>
  			<section>
  				<title>User Mailing List</title>
  				<p>Low Traffic <jump href="ext:mailsubuser">Subscribe</jump>&nbsp;<jump href="ext:mailunsubuser">Unsubscribe</jump>
  				</p>
  				<p>Search the the <jump href="ext:userlistarchive">XMLBeans User List Archive</jump> for answers to your questions on <em>using</em>
  				XMLBeans.  Post questions, issues, feedback, on the using XMLBeans to this list.</p>
  				<p>Archives of the XMLBeans Users mailing list are available <jump href="ext:userlistarchive">here in eybrowse</jump>.</p>
  			</section>
  			<section>
  				<title>Developer Mailing List</title>
  				<p>Medium Traffic <jump href="ext:mailsubdev">Subscribe</jump>&nbsp;<jump href="ext:mailunsubdev">Unsubscribe</jump>
  				</p>
  				<p>Use this mailing list for questions and/or issues related to development and coding of XMLBeans.  You may want to 
  				<jump href="ext:devlistarchive">search the archive</jump> or the XMLBeans FAQ before posting your question/feedback.</p>
  				<p>Archives of the XMLBeans Dev mailing list are available <jump href="ext:devlistarchive">here in eybrowse</jump>.</p>
  			</section>
  			<section>
  				<title>CVS Mailing List</title>
  				<p>Low-Medium-HIgh Traffic (just depends) <jump href="ext:mailsubcvs">Subscribe</jump>&nbsp;<jump href="ext:mailunsubcvs">Unsubscribe</jump>
  				</p>
  				<p>This list is used for CVS checkin emails and similar CVS type issues.</p>
  				<p>Archives of the XMLBeans CVS mailing list are available <jump href="ext:cvslistarchive">here in eybrowse</jump>.</p>
  			</section>
  		</section>
  		<section>
  			<title>Who we are</title>
  			<p>
  				<strong>XMLBeans Shepherd:</strong>&nbsp;Ted Leung</p>
  			<p>
  				<strong>XMLBeans Committers</strong>
  			</p>
  			<table>
  				<tr>
  					<th>Committer</th>
  					<th>Email</th>
  					<th>Bio</th>
  				</tr>
  				<tr>
  					<td>Cezar Andrei</td>
  					<td>cezar.andrei@nospam.bea.com</td>
  					<td>&nbsp;</td>
  				</tr>
  				<tr>
  					<td>David Bau</td>
  					<td>david.bau@nospam.bea.com</td>
  					<td>
  						<link href="http://nagoya.apache.org/eyebrowse/ReadMsg?listName=xmlbeans-dev@xml.apache.org&amp;msgNo=93">about me</link>
  					</td>
  				</tr>
  				<tr>
  					<td>Ken Kress</td>
  					<td>ken@nospam.kress.org</td>
  					<td>&nbsp;</td>
  				</tr>
  				<tr>
  					<td>Laurence Moroney</td>
  					<td>laurence.moroney@nospam.reuters.com</td>
  					<td>&nbsp;</td>
  				</tr>
  				<tr>
  					<td>David Remy</td>
  					<td>david.remy@nospam.bea.com</td>
  					<td>&nbsp;</td>
  				</tr>
  				<tr>
  					<td>Cliff Schmidt</td>
  					<td>cliff.schmidt@nospam.bea.com</td>
  					<td>&nbsp;</td>
  				</tr>
  				<tr>
  					<td>Eric Vasilik</td>
  					<td>eric.vasilik@nospam.bea.com</td>
  					<td>&nbsp;</td>
  				</tr>
  				<tr>
  					<td>Robert Wyrick</td>
  					<td>rob@nospam.wyrick.org</td>
  					<td>&nbsp;</td>
  				</tr>
  				<tr>
  					<td>Scott Ziegler</td>
  					<td>scott.ziegler@nospam.bea.com</td>
  					<td>&nbsp;</td>
  				</tr>
  			</table>
  			<note label="Emailing Committers">It is recommended that you use the mailing lists above to communicate about the XMLBeans project rather than emailing the committers directly.</note>
  			<note>The nospam. prefix on the email addresses above was put there as an attempt to thwart automatic email harvesting by spammers.  To email someone on this 
  			list remove the nospam from the email address.</note>
  		</section>
  	</body>
  </document>
  
  
  
  1.1                  xml-xmlbeans/website/src/documentation/content/xdocs/documentation/index.xml
  
  Index: index.xml
  ===================================================================
  <?xml version="1.0" encoding="UTF-8"?>
  <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "http://apache.org/forrest/dtd/document-v12.dtd">
  <document>
  	<header>
  		<title>XMLBeans Documentation</title>
  	</header>
  	<body>
  		<section>
  			<title>XMLBeans FAQ</title>
  			<p>Coming soon ... Until then you can find documentation in the CVS download</p>
  		</section>
  		<section>
  			<title>XMLBeans Version 1 User Documentation</title>
  			<p>Coming soon ... Until then you can find documentation in the CVS download</p>
  		</section>
  		<section>
  			<title>XMLBeans Version 1 JavaDoc</title>
  			<p>Coming soon ... Until then you can find documentation in the CVS download</p>
  		</section>
  	</body>
  </document>
  
  
  
  1.1                  xml-xmlbeans/website/src/documentation/content/xdocs/projectManagement/index.xml
  
  Index: index.xml
  ===================================================================
  <?xml version="1.0" encoding="UTF-8"?>
  <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "http://apache.org/forrest/dtd/document-v12.dtd">
  <document>
  	<header>
  		<title>XMLBeans Project Management</title>
  	</header>
  	<body>
  		<section>
  			<title>Incubation Exit Criteria</title>
  			<p>A major Apache sub project goal for XMLBeans is exiting from incubation.  Here is a link to the exit criteria post on general@incubator.apache.org
  			(<link href="http://nagoya.apache.org/eyebrowse/ReadMsg?listName=general@incubator.apache.org&amp;msgId=1055888">XMLBeans Exit Criteria</link>).</p>
  			<note>Need to change this link over to a Wiki page so we can show/update the status on each item.</note>
  		</section>
  		<section>
  			<title>XMLBeans Version 1 Project Management</title>
  			<p>XMLBeans Version 1 is the current stable <em>incubated</em> release</p>
  		</section>
  		<section>
  			<title>XMLBeans Version 2 Project Management</title>
  			<p>You can find information about XMLBeans 2.0 planning at  <link href="http://nagoya.apache.org/wiki/apachewiki.cgi?XmlBeansFeaturePlan">XMLBeans Feature Plan</link> 
  			if you want to provide ideas or feedback on this planning it is best to post it to either xmlbeans-dev@xml.apache.org or
  			xmlbeans-user@xml.apache.org.</p>
  		</section>
  		<section>
  			<title>XMLBeans Bug Lists</title>
  			<p>Open XMLBeans bugs (from Bugzilla): <link href="http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;email1=&amp;emailtype1=substring&amp;emailassigned_to1=1&amp;email2=&amp;emailtype2=substring&amp;emailreporter2=1&amp;bugidtype=include&amp;bug_id=&amp;changedin=&amp;votes=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;product=XMLBeans&amp;version=unspecified&amp;short_desc=&amp;short_desc_type=allwordssubstr&amp;long_desc=&amp;long_desc_type=allwordssubstr&amp;bug_file_loc=&amp;bug_file_loc_type=allwordssubstr&amp;keywords=&amp;keywords_type=anywords&amp;field0-0-0=noop&amp;type0-0-0=noop&amp;value0-0-0=&amp;cmdtype=doit&amp;order=%27Importance%27">BugZilla</link>
  			</p>
  		</section>
  	</body>
  </document>
  
  
  
  1.1                  xml-xmlbeans/website/src/documentation/content/xdocs/sourceAndBinaries/index.xml
  
  Index: index.xml
  ===================================================================
  <?xml version="1.0" encoding="UTF-8"?>
  <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "http://apache.org/forrest/dtd/document-v12.dtd">
  <document>
  	<header>
  		<title>XMLBeans Source and Binaries</title>
  	</header>
  	<body>
  		<section>
  			<title>XMLBeans Version 1 Binary and Development Kit</title>
  			<note>Incubated Build.  XMLBeans is in the incubation process at Apache and the build provided here is not sanctioned as 
  			an official Apache Release.</note>
  			<p>Link to the Incubated XMLBeans binary and development kit will go here as soon as we figure out how to get it on the mirrors</p>
  		</section>
  		<section>
  			<title>XMLBeans Source</title>
  			<section>
  				<title>Source via CVSView</title>
  				<p>XMLBeans source via CVSView: <link href="http://cvs.apache.org/viewcvs.cgi/xml-xmlbeans/">Here</link>
  				</p>
  			</section>
  			<section>
  				<title>Source via CVS checkout</title>
  				<p>If you have CVS installed on your machine you can issue the following commands to get XML Beans source:</p>
  				<source>
  cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic login
  password: anoncvs
  				</source>
  				<source>cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic checkout xml-xmlbeans</source>
  			</section>
  			<section>
  				<title>Building XMLBeans Version 1.0</title>
  				<section>
  					<title>Windows</title>
  					<p>From the xml-xmlbeans directory:</p>
  					<source>
  cd v1
  xbeanenv
  ant
  					</source>
  					<p>This will create a build directory containing the executables.  The <code>xbeans.jar</code> is in the <code>xml-beans\v1\ar</code> directory.  Try
  					<code>ant -projecthelp</code> to see other build options.</p>
  				</section>
  				<section>
  					<title>Unix</title>
  					<p>need blurb here on building in Unix, very simiilar to above Windows build</p>
  				</section>
  			</section>
  		</section>
  	</body>
  </document>
  
  
  
  1.1                  xml-xmlbeans/website/src/documentation/resources/images/built-with-forrest-button.png
  
  	<<Binary file>>
  
  
  1.1                  xml-xmlbeans/website/src/documentation/resources/images/group-logo.gif
  
  	<<Binary file>>
  
  
  1.1                  xml-xmlbeans/website/src/documentation/resources/images/group.svg
  
  Index: group.svg
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  
  <!--
         SVG Anteater logo
          jefft@apache.org
  
  To get started with SVG, I'd recommend getting the Adobe SVG plugin, and the
  xml-batik CVS module. Then have a look at the xml-batik/samples files. Use the
  SVG spec (http://www.w3.org/TR/SVG/) as a reference.
  -->
  
  <!--
  <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.0//EN"
  "http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd">
  -->
  <svg xmlns="http://www.w3.org/2000/svg"
       xmlns:xlink="http://www.w3.org/1999/xlink"
       xmlns:for="http://xml.apache.org/forrest" width="220" height="65" >
    <title>Anteater logo</title>
  
    <defs>
  
      <!--
      <radialGradient id="radialGradient">
        <stop style="stop-color:gold" offset="0"/>
        <stop style="stop-color:orange" offset=".5"/>
        <stop style="stop-color:crimson" offset="1"/>
      </radialGradient>
      <linearGradient id="linearGradient">
        <stop style="stop-color:gold" offset="0"/>
        <stop style="stop-color:orange" offset=".5"/>
        <stop style="stop-color:crimson" offset="1"/>
      </linearGradient>
      -->
  
      <linearGradient id="gradient" x1="0" y1="0" x2="0" y2="1">
        <stop style="stop-color:white" offset="0"/>
        <stop style="stop-color:lightgreen" offset="1"/>
      </linearGradient>
  
      <filter id="shadowFilter"  filterUnits="objectBoundingBox">
        <!-- Takes the alpha channel (black outline of the text), blurs it and saves as 'blur' -->
        <feGaussianBlur in="SourceAlpha" stdDeviation="2 2" result="blur"/>
        <!-- Takes saved 'blur' and offsets it by 4 pixels, saves as 'offsetBlur' -->
        <feOffset in="blur" dx="4" dy="4" result="offsetBlur"/>
        <!-- Merges SourceGraphic (original image) and 'offsetBlur', putting the
        former 'over' the latter, and using the merged result as the finished
        image -->
        <feComposite in="SourceGraphic" in2="offsetBlur" operator="over"/>
      </filter>
  
    </defs>
  
    <g filter="url(#shadowFilter)" fill="url(#gradient)">
      <text x="40%" y="60%" style="font-size:24pt; font-family:Verdana ; text-anchor: middle">
      <for:group-name />
      </text>
    </g>
  </svg>
  
  
  
  
  
  1.1                  xml-xmlbeans/website/src/documentation/resources/images/icon.png
  
  	<<Binary file>>
  
  
  1.1                  xml-xmlbeans/website/src/documentation/resources/images/project-logo.gif
  
  	<<Binary file>>
  
  
  1.1                  xml-xmlbeans/website/src/documentation/resources/images/project.svg
  
  Index: project.svg
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  
  <!--
         SVG Anteater logo
          jefft@apache.org
  
  To get started with SVG, I'd recommend getting the Adobe SVG plugin, and the
  xml-batik CVS module. Then have a look at the xml-batik/samples files. Use the
  SVG spec (http://www.w3.org/TR/SVG/) as a reference.
  -->
  
  <!--
  <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.0//EN"
  "http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd">
  -->
  <svg xmlns="http://www.w3.org/2000/svg"
       xmlns:xlink="http://www.w3.org/1999/xlink"
       xmlns:for="http://xml.apache.org/forrest" width="220" height="65" >
    <title>Anteater logo</title>
  
    <defs>
  
      <!--
      <radialGradient id="radialGradient">
        <stop style="stop-color:gold" offset="0"/>
        <stop style="stop-color:orange" offset=".5"/>
        <stop style="stop-color:crimson" offset="1"/>
      </radialGradient>
      <linearGradient id="linearGradient">
        <stop style="stop-color:gold" offset="0"/>
        <stop style="stop-color:orange" offset=".5"/>
        <stop style="stop-color:crimson" offset="1"/>
      </linearGradient>
      -->
  
      <linearGradient id="gradient" x1="0" y1="0" x2="0" y2="1">
        <stop style="stop-color:white" offset="0"/>
        <stop style="stop-color:lightgreen" offset="1"/>
      </linearGradient>
  
      <filter id="shadowFilter"  filterUnits="objectBoundingBox">
        <!-- Takes the alpha channel (black outline of the text), blurs it and saves as 'blur' -->
        <feGaussianBlur in="SourceAlpha" stdDeviation="2 2" result="blur"/>
        <!-- Takes saved 'blur' and offsets it by 4 pixels, saves as 'offsetBlur' -->
        <feOffset in="blur" dx="4" dy="4" result="offsetBlur"/>
        <!-- Merges SourceGraphic (original image) and 'offsetBlur', putting the
        former 'over' the latter, and using the merged result as the finished
        image -->
        <feComposite in="SourceGraphic" in2="offsetBlur" operator="over"/>
      </filter>
  
    </defs>
  
    <g filter="url(#shadowFilter)" fill="url(#gradient)">
      <text x="51%" y="75%" style="font-size:32pt; font-family:Verdana ; text-anchor: middle" >
      <for:project-name />
      </text>
    </g>
  </svg>
  
  
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: xmlbeans-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: xmlbeans-cvs-help@xml.apache.org


Mime
View raw message