cocoon-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject cvs commit: xml-cocoon2/documentation/xdocs/ctwig ctwig-gettingstarted.xml ctwig-installing.xml ctwig-why.xml
Date Thu, 22 Nov 2001 07:34:14 GMT
crossley    01/11/21 23:34:14

  Modified:    documentation/xdocs/ctwig ctwig-gettingstarted.xml
                        ctwig-installing.xml ctwig-why.xml
  Log:
  Removed references to specific C2 versions.
  Submitted by:	Jermey Aston <jez@pigbite.com>
  
  Revision  Changes    Path
  1.5       +2 -2      xml-cocoon2/documentation/xdocs/ctwig/ctwig-gettingstarted.xml
  
  Index: ctwig-gettingstarted.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon2/documentation/xdocs/ctwig/ctwig-gettingstarted.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- ctwig-gettingstarted.xml	2001/11/09 05:17:06	1.4
  +++ ctwig-gettingstarted.xml	2001/11/22 07:34:14	1.5
  @@ -24,8 +24,8 @@
   			</s2>
   
   			<s2 title="Where do I get it from?">
  -				<p>Go to <fork href="http://xml.apache.org/cocoon2/">http://www.apache.org/cocoon2/</fork>
and download it from there.  The latest distribution for any operating system
  -				<fork href="http://xml.apache.org/cocoon2/dist/Cocoon-2.0rc1a.zip">Cocoon 2 Release
Candidate 1a</fork>.  This file contains the Cocoon code, samples, documentation and
the Java libraries that enable the Cocoon to work such as Xerces and Xalan.</p>
  +				<p>Go to <fork href="http://xml.apache.org/cocoon2/">http://www.apache.org/cocoon2/</fork>
and download it from there.  The latest distribution for any operating system can be found
in the 
  +				<fork href="http://xml.apache.org/cocoon2/dist/">Cocoon 2 distribution folder</fork>.
 The distribution that you can download from there contains the Cocoon code, samples, documentation
and the Java libraries that enable the Cocoon to work such as Xerces and Xalan.</p>
   			</s2>
   
   			<s2 title="What assumptions have you made?">
  
  
  
  1.5       +6 -6      xml-cocoon2/documentation/xdocs/ctwig/ctwig-installing.xml
  
  Index: ctwig-installing.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon2/documentation/xdocs/ctwig/ctwig-installing.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- ctwig-installing.xml	2001/11/09 05:17:06	1.4
  +++ ctwig-installing.xml	2001/11/22 07:34:14	1.5
  @@ -12,13 +12,13 @@
   	<body>
   		<s1 title="Installing Cocoon 2">
   			<s2 title="Introduction">
  -				<p>Installing C2 is not a complete nightmare.  I found that following the instructions
in the documentation worked just fine.  The only issue here is that by following the instructions
you end up with a WAR file and this is no good for development because you cannot add your
own code or make changes to existing files without repackaging it all up.</p>
  +				<p>Installing C2 is straight-forward.  I found that following the instructions
in the documentation worked just fine.  The only issue here is that by following the instructions
you end up with a WAR file and this is no good for development because you cannot add your
own code or make changes to existing files without repackaging it all up.</p>
   				<p>To get around these problems you need to install it as an unpacked application
and get your servlet engine to recognise it as such.</p>
  -				<p>Please note the assumptions about platform, user knowledge and existing applications
in the <link href="ctwig-why.html">Why?</link> section and also note thatw herever
{TOMCAT_HOME}, {COCOON_HOME} or {APACHE_HOME} appears it should be replaced with the path
it is installed into on your machine (e.g. d:\java\cocoon\2.02rc1a for {COCOON_HOME}).</p>
  -				<p><strong>I'm really sorry, but at the moment these examples relate to
C2rc1a, Tomcat 3.2.3 and Apache 1.3.19 on Windows 2000.</strong> It is probably all
the same for any operating system (remember, that is the promise of Java and XML). I would
like to do TC4/Unix notes but do not have the time at the momement.  If you can help then
please <link href="ctwig-contributing.html">contribute</link>.</p>
  +				<p>Please note the assumptions about platform, user knowledge and existing applications
in the <link href="ctwig-why.html">Why?</link> section and also note thatw herever
{TOMCAT_HOME}, {COCOON_HOME} or {APACHE_HOME} appears it should be replaced with the path
it is installed into on your machine (e.g. d:\java\cocoon for {COCOON_HOME}).</p>
  +				<p><strong>I'm really sorry, but at the moment these examples relate to
the latest distribution, Tomcat 3.2.3 and Apache 1.3.19 on Windows 2000.</strong> It
is probably all the same for any operating system (remember, that is the promise of Java and
XML). I would like to do TC4/Unix notes but do not have the time at the momement.  If you
can help then please <link href="ctwig-contributing.html">contribute</link>.</p>
   			</s2>
   			<s2 title="Download Cocoon 2">
  -				<p>The latest distribution for any operating system is <fork href="http://xml.apache.org/cocoon2/dist/Cocoon-2.0rc1a.zip">Cocoon
2 release candidate 1a</fork>.  This file contains the Cocoon code, samples, documentation
and the Java libraries that enable the Cocoon to work such as Xerces and Xalan.  The file
is in ZIP format.  When you have downloaded it then extract it to somewhere.  This path becomes
your {COCOON_HOME}.</p>
  +				<p>The latest distribution for any operating system can be found in the <fork
href="http://xml.apache.org/cocoon2/dist/">Cocoon 2 distribution folder</fork>. 
This file contains the Cocoon code, samples, documentation and the Java libraries that enable
the Cocoon to work such as Xerces and Xalan.  When you have downloaded it then extract it
to somewhere.  This path becomes your {COCOON_HOME}.</p>
   			</s2>
   			<s2 title="Basic Configuration">
   				<p>Follow the instructions on building C2 as per the installation guide that
comes with C2.  It can also be found <fork href="http://xml.apache.org/cocoon2/install.html">here</fork>
as well.  Obviously since you have got the ZIP distribution you do not have to do the CVS
bit thus you can start at the Building Apache Cocoon 2 section.  Do each of the following
steps:</p>
  @@ -37,9 +37,9 @@
   				<p>Next, copy the xerces_xxx.jar to {TOMCAT_HOME}\lib, delete the tomcat jaxp
jar and rename the parser.jar as instructuted.</p>
   				<p>An important point is that if you are running Tomcat as an NT service then
you will need to change {TOMCAT_HOME}\conf\wrapper.properties to reflect the classpath changes.
 Make sure xerces is first in line, remove (or comment out) the jaxp and rename the parser.jar
reference.  This is all done with the wrapper.class_path bit.</p>
   				<p>If you did run the second build.bat command above or if you copy cocoon.war
into {TOMCAT_HOME}\webapps then you can check that C2 is working.  Restart Tomcat and http://localhost:8080/cocoon
should work.  Note at this point Apache is doing nowt - Tomcat is doing the http serving.
 If there are any problems then check that the tomcat classpath in wrapper.properties is correct
and you have done the work in {TOMCAT_HOME}\lib as descibed above.</p>
  -				<p>One other situation that came to light in C2 RC1 (as opposed to RC1a) was
that the build file was including a reference to the LDAP transformer classes and since the
JAR is not included then you would see an error when starting C2 along the lines of:</p>
  +				<p>One other situation that came to light in C2 RC1 (and resolved in RC1a) was
that the build file was including a reference to the LDAP transformer classes and since the
JAR is not included then you would see an error when starting C2 along the lines of:</p>
   				<p>org.apache.cocoon.ProcessingException: Exception in Handler: org.apache.avalon.framework.component.ComponentException:
Could not set up Component for hint: org\apache\cocoon\www\sitemap_xmap</p>
  -				<p>This has been resolved in C2 RC1a by making changing the offending include
line in build.xml.  Have a look and see.  You will need to change this line if you want to
use the LDAP transformer as per the instructions in the RC1a build.xml file.</p>
  +				<p>This was resolved in C2 RC1a by making changing the offending include line
in build.xml.  Have a look and see.  You will need to change this line if you want to use
the LDAP transformer as per the instructions in the build.xml file.</p>
   				<p>One other good point about testing, especially if you are upgrading, is to
delete the Cocoon working files in {TOMCAT_HOME}\work.  If left in between upgrades, you can
easily get precompiled code sent instead of the new pages being compiled and served.</p>
   			</s2>
   			<s2 title="Configure C2 to run in Unpackaged Mode">
  
  
  
  1.5       +2 -2      xml-cocoon2/documentation/xdocs/ctwig/ctwig-why.xml
  
  Index: ctwig-why.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon2/documentation/xdocs/ctwig/ctwig-why.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- ctwig-why.xml	2001/11/09 05:17:06	1.4
  +++ ctwig-why.xml	2001/11/22 07:34:14	1.5
  @@ -12,11 +12,11 @@
   	<body>
   		<s1 title="Why?">
   			<p>If nothing else these pages form my own personal documentation of how to use
C2 from the ground up.  I run a team of developers and as much as I encourage them to jump
into technology and problem solve themselves, I also want them to know when to ask for help
and to do it before they have wasted hours of time banging their heads against brick walls.
 With a technology that is new to them, which C2 is, these pages can help them get more productive
more quickly.  I am learning C2 too so I don't want to fall into the same trap.</p>
  -			<p>I installed C2 for the first time on Thursday 20th September 2001 and I wanted
to write down what I did so my team could benefit.  In the course of asking questions on the
xml-cocoon-users mail list I realised that others were having the same problems and, more
importantly, the answers were all there via the generous nature of more experienced list users.
 To support my team, the wider development community and pay back in kind the support of others
I wanted to make my notes available.</p>
  +			<p>When I installed C2 for the first time I wanted to write down what I did so
my team could benefit.  In the course of asking questions on the xml-cocoon-users mail list
I realised that others were having the same problems and, more importantly, the answers were
all there via the generous nature of more experienced list users.  To support my team, the
wider development community and pay back in kind the support of others I wanted to make my
notes available.</p>
   			<p>Given that I am still getting some basic stuff running these pages are going
to be like a diary of my work for the first few weeks but I hope that something good comes
out of it.  If you find ways of doing things better, have your own notes, want to put me right
on something or just want to stop it being a one man ego trip then please <link href="ctwig-contributing.html">contribute</link>.</p>
   			<p>As a bit of technical background...  I have been working for almost the past
five years developing web based e-learning solutions, firstly a learning mangement system
(Solstra - <fork href="http://www.solstra.com">www.solstra.com</fork>), then an
e-learning portal (easycando.com - <fork href="http://www.easycando.com">easycando.com</fork>)
and more recently content for <fork href="http://www.knowledgepool.com">KnowledgePool</fork>.
 Right from day one, after trying and discarding ASP and Cold Fusion, we saw the need to use
templates that could seperate logic from layout.  We built our own Java based architecture
then moved it from templates to servlets as that technology progressed.  By using a property
file based system along with classes that abstracted the HTML coding side, we built configurable,
multi-lingual solutions.  The basic method still contains weaknesses and I was keen to see
how XML/XSL could help.</p>
   			<p>About a year ago we developed some prototype code that used JSP, beans, XML
and XSL.  It worked quite well but then things changed, I moved jobs and did not do anything
more other than mull things over in my head.  More recently I have had to start architecting
tools to help my company develop learning content and I revisited my earlier thoughts.  I
was reading a "Java and XML" by Brett McLaughlin (published by O'Reilly) and it talked about
Cocoon.  When I saw the taglib (logicsheet) idea I realised here was a platform I could work
with.  I tried 1.8 as it was production code and then moved to 2 because I saw the internationalisation
capabilities and thought it is probably close to becoming a fully released product.</p>
  -			<p>I am now trying to build some prototype code and realising that sharing my
experiences might help others.  At worst it'll be how not to do it!</p>
  +			<p>I am now building more and more code and realising that sharing my experiences
might help others.  At worst it'll be how not to do it!</p>
   		</s1>
   	</body>
   </document>
  
  
  

----------------------------------------------------------------------
In case of troubles, e-mail:     webmaster@xml.apache.org
To unsubscribe, e-mail:          cocoon-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-cvs-help@xml.apache.org


Mime
View raw message