[Cocoon Wiki] Updated: GT2004Bertrand

[do...@cocoon.apache.org]

   Date: 2004-10-27T00:26:11
   Editor: RogierPeters <ro...@hivemind.nl>
   Wiki: Cocoon Wiki
   Page: GT2004Bertrand
   URL: http://wiki.apache.org/cocoon/GT2004Bertrand

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -1,7 +1,3 @@
-The purpose of this document is to try and keep up with people as they are speaking. Later the pages will be added to the wiki, so if you want to use markup, use wiki markup
-
-removed intro to another document.
-
 == Bertrand Delacretaz: Cocoon: what do yo need to know ==
 
 Overall structure of a cocoon app
@@ -44,7 +40,7 @@
   XSLT, Flow, CForms, Java biz logic, OJB for data access
 Not the only way
 
-4. Presentation Layer
+== 4. Presentation Layer ==
 
 You don't need to know java biz objects to use xml docs in cocoon.
 You need to know:
@@ -71,7 +67,7 @@
     Uses javascript syntax. yet another language, because it works. Only way to do continuations easily. Just a few lines of code. Get a component, error handling, send a page.
     Continuations are good to handle 'loose connections'.
 
-7. Cocoon Forms
+== 7. Cocoon Forms ==
 You need 3 def files
  * form model
  * binding 
@@ -81,10 +77,10 @@
 
 less code, but more time to find out where you need the five lines of code that will do the work. Need to take the time to find out where you have to put your code in cocoon. Usually application specific.
 
-8. Business Logic
+== 8. Business Logic ==
 Usually in Java. POJO. Ugo will later show even better way to separate business logic. 
 
-9. Database Access
+== 9. Database Access ==
 OJB rocks ( except the name... ). Simple for simple things. Only need to write xml mapping file to map objects to fields. Setup requires SQL/JDBC skills. This is one way to do it, works for him
 
 
@@ -97,11 +93,11 @@
 testing javacode with JUnit
 testing the front end via HTTPUnit or Anteater
 
-10. Cocoon Blocks
+== 10. Cocoon Blocks == 
 Can be scary. Nouvo uses only two blocks. Linkrewriter and Forms. Don't worry about the blocks. Most of them are exotic.
 You don't need most of them
 
-11. Skills -  Installation
+== 11. Skills -  Installation ==
 
 Not sure who cocoon is for. Should be easier, or not. It's better to fail early? 
 Command line is where you do the work. Don't expect buttons. No need to be a commandline guru, but basic skills are required. 
@@ -118,14 +114,14 @@
 No need for tomcat or apache httpd.
 Play with the samples and look at the logs (don't be shy)
 
-12. Where to start
+== 12. Where to start ==
 Supersonic tour block(written by Bertrand) is an overview of how cocoon works 
 Documentation tracks on the website that show you how to explore the samples.
 
 Explore explore explore!!!! Without this, you will not learn
 You have to be willing to be digging.
 
-13. Skills - Presentation
+== 13. Skills - Presentation ==
 
 Need to learn XSLT - very strange language for procedural programmers .... they need to change their mindset to work with the language
 XSLT is event based.
@@ -138,12 +134,12 @@
 
 HTTPUnit/Anteater - testing the front end behaviour
 
-14. Skills - Forms
+== 14. Skills - Forms ==
 You need to understand the forms concepts. These are simple for simple problems, but easy to customize if you need to do complex things.
 
 but you can do a lot without customisation
 
-15. Skills - Backend development
+== 15. Skills - Backend development ==
 
 Java coding, OJB, some SQL
 Creating and setting up your db
@@ -152,7 +148,7 @@
 
 Need to be able to test the code: JUnit
 
-16. Skills - Debugging
+== 16. Skills - Debugging ==
 
 Very important to debug, separate chapter. If you can pinpoint your problem it's easier to get help! You have to understand log-configuration.
 
@@ -162,12 +158,12 @@
 
 Screenshot of Chainsaw (comes with log4j) GUI tool for viewing and filtering logs in realtime
 
-17. Skills - Integration
+== 17. Skills - Integration ==
 If you remember one thing, remember this: The hard part is the integration. Many tools and libraries play a part in your application.
 
 Need someone who can have an overall view of the whole app, for integration and debugging, not everyone on the team needs to be able to do this.
 
-18. Will you make it?
+== 18. Will you make it? ==
 Of course - if you are willing to invest. 
 
 No one knows everything about Cocoon. 
@@ -177,20 +173,20 @@
 
 Need strong Architect/Integrator
 
-19 Will it be worth it?
+== 19. Will it be worth it? ==
 
 Yes, if you are comfortable with the command line, if you take the time to explore (the jungle). You need a long term vision for the complexity of cocoon to pay off. 
 
 Suitable for heavy lifting, but can be used for simple projects, especially if you are planning to take the project further in the future.
 Invest in your skills, learn learn learn.
 
-20. Conclusions
+== 20. Conclusions ==
 Cocoon is like the toolbox of a very rich man. Which tool do you need? Take time to select the right tool. Otherwise you get lost. Don't be distracted by what is all around you.
 Full blown apps need a wide range of skills. 
 
 Need to be an explorer, and be happy always learning
 
-21. Coda 
+== 21. Coda  ==
 Starting up? Look at supersonic tour.
 If you have the skills take the time to explore
 Usually people who take their time with cocoon like what they see