forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thorsten Scherler <thorsten.scherler....@juntadeandalucia.es>
Subject [HeadsUp] next steps for dispatcher integration - please test
Date Thu, 09 Oct 2008 12:26:00 GMT
Hi all,

after an extended rewrite of the dispatcher I am happy to say that my
first tests are all passing now.

The upgrade steps for custom dispatcher projects are straightforward:
1) Renaming extension of the contracts from *.ft to *.contracts.xml
demonstrated with http://svn.apache.org/viewcvs?view=rev&rev=701113

2) Renaming elements from view to structurer
demonstrated with http://svn.apache.org/viewcvs?view=rev&rev=701117

3) Renaming structurer file and adding new extension
demonstrated with http://svn.apache.org/viewcvs?view=rev&rev=701325

4) The path of the defaultVariables has changed a bit. Removing one
level
demonstrated with http://svn.apache.org/viewcvs?view=rev&rev=703149

5) [optional] Renaming extensions for contracts and structurer in
properties files.
demonstrated with http://svn.apache.org/viewcvs?view=rev&rev=701119

Step 5 is optional since in the normal use case one is using the default
configuration. However our fresh site sadly added the
"dispatcher.theme-ext" property. Just do:
-  <property name="dispatcher.theme-ext" value=".fv"/>


On my todo list still are two open points:
1) Merge the cocoon-2.2 block dispatcher into the current plugin. This
needs extending the normal build of plugins since cocoon 2.2 needs
additional files in the resulting jar. 
2) Small document of the new features and how we can use them.

I hope to finish this point within the next days.

Since I have done the whole work in a branch I need to merge it ASAP. I
suspect that the merge will not be fully conflict free since there has
been some commits to the trunk of contracts that are not in the branch.

Before I merge I like to ask all dispatcher user to test the new code. 

Preparation for testing:
cd $FORREST_HOME/whiteboard
svn switch
https://svn.apache.org/repos/asf/forrest/branches/dispatcher_rewrite .

Now you can test a fresh seed which should work without any problem. If
you try to use your custom dispatcher that you may have make sure you
followed above upgrade instructions.

What are the additional steps you needed to do to update your custom
dispatcher project to the new version?

Is it working for you? 

TIA for any feedback.

salu2
-- 
Thorsten Scherler                                 thorsten.at.apache.org
Open Source Java                      consulting, training and solutions


Mime
View raw message