cvs commit: cocoon-2.1/src/documentation/xdocs/installing updating.xml
cziegeler2003/08/18 05:29:31 Modified:src/documentation/xdocs/installing updating.xml Log: This is currently not true Revision ChangesPath 1.17 +5 -0 cocoon-2.1/src/documentation/xdocs/installing/updating.xml Index: updating.xml === RCS file: /home/cvs/cocoon-2.1/src/documentation/xdocs/installing/updating.xml,v retrieving revision 1.16 retrieving revision 1.17 diff -u -r1.16 -r1.17 --- updating.xml 13 Jul 2003 15:21:20 - 1.16 +++ updating.xml 18 Aug 2003 12:29:31 - 1.17 @@ -145,6 +145,10 @@ /s2 s2 title=XSLT Processor p +There are some issues related to JDK 1.4 +/p +!-- +p The default XSLT processor has changed, and there are some issues related to JDK 1.4 /p s3 title=Xalan vs. XSLTC @@ -166,6 +170,7 @@ that gives errors. /p /s3 +-- s3 title=XML/XSLT with JDK 1.4 pAnother serious issue is the presence of the Xalan and Xerces package in the JDK 1.4. For general information on this please read the
cvs commit: cocoon-2.1/src/documentation/xdocs/installing updating.xml
cziegeler2003/08/18 05:34:28 Modified:src/documentation/xdocs/installing updating.xml Log: Adding a little bit about Cacheable Revision ChangesPath 1.18 +16 -0 cocoon-2.1/src/documentation/xdocs/installing/updating.xml Index: updating.xml === RCS file: /home/cvs/cocoon-2.1/src/documentation/xdocs/installing/updating.xml,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- updating.xml 18 Aug 2003 12:29:31 - 1.17 +++ updating.xml 18 Aug 2003 12:34:28 - 1.18 @@ -209,6 +209,22 @@ WEB-INF/ directory. /p /s2 + s2 title=Caching +pAlthough the basic caching mechanism is still the same (each sitemap component + in the pipeline is queried), the interface for a component have been + improved as well./p +pThe old interface emCacheable/em is deprecated in favour of the new + emCacheableProcessingComponent/em interface. The basic behaviour of this + interface has been preserved, however the method names and the signatures + have changed a little bit. + /p +pSome other interfaces, like the validity of the cached information has + moved to the source packacke in Avalon Excalibur./p +pThe old interfaces are still support but deprecated, so it's advisable to + update your components. However, you can support both interfaces at the + same time, making your component runable in old and new Cocoon installations + at the same time./p + /s2 s2 title=Stores pThe Store and StoreJanitor components and implementations have been moved to Avalon Excalibur./p
RE: cvs commit: cocoon-2.1/src/documentation/xdocs/installing updating.xml
Vadim Gritsenko wrote: [EMAIL PROTECTED] wrote: + pIt's also advisable to change your implementations from using emLogEnabled/em + instead of emLoggable/em when it comes to logging in your components. + /p ... to change ... from using emLogEnabled/em ... instead of emLoggable/em Is it me or wording is confusing? You know the answer and you have commit access, so you can change it, right? Ok, I just changed the wording myself. Thanks Carsten
Re: cvs commit: cocoon-2.1/src/documentation/xdocs/installing updating.xml
Carsten Ziegeler wrote: Vadim Gritsenko wrote: [EMAIL PROTECTED] wrote: + pIt's also advisable to change your implementations from using emLogEnabled/em + instead of emLoggable/em when it comes to logging in your components. + /p ... to change ... from using emLogEnabled/em ... instead of emLoggable/em Is it me or wording is confusing? You know the answer and you have commit access, so you can change it, right? Ok, I just changed the wording myself. No offence intended, and I'm no writer either. Thanks. Vadim
Re: cvs commit: cocoon-2.1/src/documentation/xdocs/installing updating.xml
[EMAIL PROTECTED] wrote: + pIt's also advisable to change your implementations from using emLogEnabled/em + instead of emLoggable/em when it comes to logging in your components. + /p ... to change ... from using emLogEnabled/em ... instead of emLoggable/em Is it me or wording is confusing? Vadim
cvs commit: cocoon-2.1/src/documentation/xdocs/installing updating.xml
cziegeler2003/07/11 08:10:21 Modified:src/documentation/xdocs/installing updating.xml Log: Updating the update doc Revision ChangesPath 1.15 +11 -0 cocoon-2.1/src/documentation/xdocs/installing/updating.xml Index: updating.xml === RCS file: /home/cvs/cocoon-2.1/src/documentation/xdocs/installing/updating.xml,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- updating.xml 2 Jul 2003 07:21:03 - 1.14 +++ updating.xml 11 Jul 2003 15:10:20 - 1.15 @@ -120,6 +120,9 @@ Due to some interface changes in the Cocoon logging components, custom java components (generators,transformers or actions for example) compiled for Cocoon 2.0.x will not run under Cocoon 2.1 unless recompiled./p + pIt's also advisable to change your implementations from using emLogEnabled/em + instead of emLoggable/em when it comes to logging in your components. + /p /s1 s1 title=Components p @@ -237,6 +240,14 @@ emorg.apache.cocoon.servlet.multipart.Part/em, and the emgetFilePath()/em has been renamed emPart.getUploadName()./em /p + /s2 + s2 title=RequestLifeCycleComponent +pIf you are using the marker interface emRequestLifeCycleComponent/em for your +own components, you have to make sure that your implementations still implement +the emComponent/em interface. The emRequestLifeCycleComponent/em does no +longer extend the emComponent/em interface, so you have to declare it in your +own components together with emRequestLifeCycleComponent/em. Otherwise you +will get a emClassCastException/em as soon as you access your component./p /s2 /s1 s1 title=Components from the scratchpad
