RE: Logicsheet problems - global XSLT variables

[Antonio Gallardo]

Mark H dijo:
> Thanks Antonio, I'll try it out. How does the reload-method="synchron"
> improve things?

It will check if there are some changes before serving the request. For
development environment it is fine since we are always changing the
sources.

Antonio Gallardo.
>
> -Original Message-
> From: Antonio Gallardo [mailto:[EMAIL PROTECTED]]
> Sent: 20 January 2003 06:34
> To: [EMAIL PROTECTED]
> Subject: Re: Logicsheet problems - global XSLT variables
>
>
>> Also, do others find working with Cocoon very frustrating? When you
>> make a change it takes forever for the web-app to reload and
>> re-compile the java class, espcially when it takes up so much memory.
>
> You need to add in your cocoon.xconf file:
>
>  config="resource://org/apache/cocoon/components/treeprocessor/treeprocessor-
> builtins.xml"
> file="context://sitemap.xmap" logger="sitemap"/>
>
> Search for the  tag and add the attributes:
>
> reload-method="synchron"
> check-reload="yes"
>
> Antonio Gallardo
>
>>
>> Thx in advance,
>> Mark
>>
>>
>>
>> -
>> Please check that your question  has not already been answered in the
>> FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>>
>> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
>> For additional commands, e-mail:   <[EMAIL PROTECTED]>
>
>
>
>
> -
> Please check that your question  has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail:   <[EMAIL PROTECTED]>
>
>
>
>
>
>
> -
> Please check that your question  has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail:   <[EMAIL PROTECTED]>




-
Please check that your question  has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

RE: 10 basic survival tips for cocoon users (was: Logicsheet problems - global XSLT variables)

[Hunsberger, Peter]

>>4.) Proceed in "baby steps" when changing things in your cocoon app
>
> But it really slows up development

Doing incremental development will ultimately save you many many, days of
lost productivity.  The biggest roadblock is having sufficiently powerful
hardware that doing many compiles and redeploying Cocoon doesn't cost you a
lot of time. Splurging for the best hardware you can afford will likely pay
itself back very quickly in time savings...

For XSLT changes it's usually simple to proceed in baby steps since you can
usually edit the live sheets and resubmit the page and immediately see the
results.  In addition you can break your pipelines into pieces so that you
can capture the output XML and feed it into something like XML Spy or
Xselerator and debug your XSLT that way.

-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Re: 10 basic survival tips for cocoon users (was: Logicsheet problems- global XSLT variables)

[SAXESS - Hussayn Dabbous]

Hy

Mark H wrote:



For XSLT processing i have added Saxon-6.5.2.



Are you saying that Xerces doesn't deal with global XSLT variables properly?




NO. Of course xalan can handle globals and i am using this
feature with xalan too..
I say, that some aspects of xslt can be done with saxon,
which can't be done with xalan and vice versa, e.g. there
is a (possible) bug with entity resolving within style sheets,
that is (partially) solved when using saxon...

interested people can see:

http://www.saxess.com/JSPWiki/Wiki.jsp?page=EntityResolver

(last chapter focusses on saxon)




4.) Proceed in "baby steps" when changing things in your cocoon app



But it really slows up development



The survival tips adress newbies. expereinced users may
use different (more efficient) strategies...




8.) I started using the "coocon developers handbook"



I got "Cocoon - Building XML Applications" and "Coocoon 2 Programming" but
they don't get into the development site of things very deeply, especially
the first book. Might try out the book you mentioned.


i prefer the "cocoon developers handbook" because it really goes
into real life examples with code snippets and so on. It adresses
my programmers needs quite well. Of course it doesn't go into the
depest secrets of cocoon, but cocoon is anyway a running target,
hence using the book plus the cocoon wiki fits at least my basic
needs.

regards, hussayn

--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail:  [EMAIL PROTECTED]


-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

RE: 10 basic survival tips for cocoon users (was: Logicsheet problems - global XSLT variables)

[Mark H]

> Are you saying that Xerces doesn't deal with global XSLT variables
properly?

sorry, that should be Xalan

-Original Message-
From: Mark H [mailto:[EMAIL PROTECTED]]
Sent: 21 January 2003 13:58
To: [EMAIL PROTECTED]
Subject: RE: 10 basic survival tips for cocoon users (was: Logicsheet
problems - global XSLT variables)


> For XSLT processing i have added Saxon-6.5.2.

Are you saying that Xerces doesn't deal with global XSLT variables properly?

>4.) Proceed in "baby steps" when changing things in your cocoon app

But it really slows up development

>8.) I started using the "coocon developers handbook"

I got "Cocoon - Building XML Applications" and "Coocoon 2 Programming" but
they don't get into the development site of things very deeply, especially
the first book. Might try out the book you mentioned.

-Original Message-
From: SAXESS - Hussayn Dabbous [mailto:[EMAIL PROTECTED]]
Sent: 20 January 2003 10:50
To: [EMAIL PROTECTED]
Subject: 10 basic survival tips for cocoon users (was: Logicsheet
problems - global XSLT variables)



Mark Horgan wrote:

> Also, do others find working with Cocoon very frustrating? When you make a
> change it takes forever for the web-app to reload and re-compile the java
> class, espcially when it takes up so much memory. Also even when using the
> logs its very hard to track down bugs in ones code especially logicsheets.
> But generally I like Cocoon though I wish it was more straight-forward to
> develop with it.
>
> Thx in advance,
> Mark
>

Hy,

When i started with cocoon i got really mad with hunting errors
and understanding, how all this fits together. But after about
three months of working with the beast, i built up some
survival strategies. It is how I do it. It may help as a guide,
but it does not claim to be the "best approach":

1.) Instead of restarting the whole container, i only restart
 the cocoon app, when needed. This takes a few seconds with
 tomcat 4.1.* (~300 MHz sparc dual processor, solaris 2.8)
2.) During development i use tomcat and i set the reloadable="true"
 within the  of my webapp. By this any changes in the
 classpath causes an automatic webapp restart.
3.) use released versions if possible (cocoon-2.0.4 seems quite mature)
4.) Proceed in "baby steps" when changing things in your cocoon app
5.) follow KISS (keep it simple, stupid) i keep as much as possible
 with the basics of cocoon and don't use (yet) the more fancy stuff.
6.) Separate your app into subsitemaps and subdirs with related issues
7.) use the cocoon-wiki
 Especially the search function unhides
 interesting docs
8.) I started using the "coocon developers handbook"
 It's written from Lajos Moczar and some other active
 cocoon developers...

Here are two of my personal favorites. I have documented this in
our company wiki:

9.) For XSLT processing i have added Saxon-6.5.2. It's not
 straight forward to install, but sometimes it can be
 utilised with less pain, than xalan (just a matter of taste)
 Look into cocoon wiki for a quick description or look at
 http://www.saxess.com/JSPWiki/Wiki.jsp?page=Install
 for a quickinstall step by step instruction.
10.)use entity resolver wherever possible.
 look at the cocoon docs for the basics or at
 http://www.saxess.com/JSPWiki/Wiki.jsp?page=EntityResolver
 for a quickinstall description.

hope, that helps someone ...

regards, hussayn

--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail:  [EMAIL PROTECTED]


-
Please check that your question  has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>






-
Please check that your question  has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>






-
Please check that your question  has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

RE: 10 basic survival tips for cocoon users (was: Logicsheet problems - global XSLT variables)

[Mark H]

> For XSLT processing i have added Saxon-6.5.2.

Are you saying that Xerces doesn't deal with global XSLT variables properly?

>4.) Proceed in "baby steps" when changing things in your cocoon app

But it really slows up development

>8.) I started using the "coocon developers handbook"

I got "Cocoon - Building XML Applications" and "Coocoon 2 Programming" but
they don't get into the development site of things very deeply, especially
the first book. Might try out the book you mentioned.

-Original Message-
From: SAXESS - Hussayn Dabbous [mailto:[EMAIL PROTECTED]]
Sent: 20 January 2003 10:50
To: [EMAIL PROTECTED]
Subject: 10 basic survival tips for cocoon users (was: Logicsheet
problems - global XSLT variables)



Mark Horgan wrote:

> Also, do others find working with Cocoon very frustrating? When you make a
> change it takes forever for the web-app to reload and re-compile the java
> class, espcially when it takes up so much memory. Also even when using the
> logs its very hard to track down bugs in ones code especially logicsheets.
> But generally I like Cocoon though I wish it was more straight-forward to
> develop with it.
>
> Thx in advance,
> Mark
>

Hy,

When i started with cocoon i got really mad with hunting errors
and understanding, how all this fits together. But after about
three months of working with the beast, i built up some
survival strategies. It is how I do it. It may help as a guide,
but it does not claim to be the "best approach":

1.) Instead of restarting the whole container, i only restart
 the cocoon app, when needed. This takes a few seconds with
 tomcat 4.1.* (~300 MHz sparc dual processor, solaris 2.8)
2.) During development i use tomcat and i set the reloadable="true"
 within the  of my webapp. By this any changes in the
 classpath causes an automatic webapp restart.
3.) use released versions if possible (cocoon-2.0.4 seems quite mature)
4.) Proceed in "baby steps" when changing things in your cocoon app
5.) follow KISS (keep it simple, stupid) i keep as much as possible
 with the basics of cocoon and don't use (yet) the more fancy stuff.
6.) Separate your app into subsitemaps and subdirs with related issues
7.) use the cocoon-wiki
 Especially the search function unhides
 interesting docs
8.) I started using the "coocon developers handbook"
 It's written from Lajos Moczar and some other active
 cocoon developers...

Here are two of my personal favorites. I have documented this in
our company wiki:

9.) For XSLT processing i have added Saxon-6.5.2. It's not
 straight forward to install, but sometimes it can be
 utilised with less pain, than xalan (just a matter of taste)
 Look into cocoon wiki for a quick description or look at
 http://www.saxess.com/JSPWiki/Wiki.jsp?page=Install
 for a quickinstall step by step instruction.
10.)use entity resolver wherever possible.
 look at the cocoon docs for the basics or at
 http://www.saxess.com/JSPWiki/Wiki.jsp?page=EntityResolver
 for a quickinstall description.

hope, that helps someone ...

regards, hussayn

--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail:  [EMAIL PROTECTED]


-
Please check that your question  has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>






-
Please check that your question  has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

RE: Logicsheet problems - global XSLT variables

[Mark H]

Thanks Antonio, I'll try it out. How does the reload-method="synchron"
improve things?

-Original Message-
From: Antonio Gallardo [mailto:[EMAIL PROTECTED]]
Sent: 20 January 2003 06:34
To: [EMAIL PROTECTED]
Subject: Re: Logicsheet problems - global XSLT variables


> Also, do others find working with Cocoon very frustrating? When you make
> a change it takes forever for the web-app to reload and re-compile the
> java class, espcially when it takes up so much memory.

You need to add in your cocoon.xconf file:



Search for the  tag and add the attributes:

reload-method="synchron"
check-reload="yes"

Antonio Gallardo

>
> Thx in advance,
> Mark
>
>
>
> -
> Please check that your question  has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail:   <[EMAIL PROTECTED]>




-
Please check that your question  has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>






-
Please check that your question  has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Re: 10 basic survival tips for cocoon users (was: Logicsheet problems - global XSLT variables)

[Antonio Gallardo]

Its. OK.

Start an "XML-authoring tools".

Antonio Gallardo



SAXESS - Hussayn Dabbous dijo:
> hy Antonio;
>
> What about adding your contrib directly to
>
> http://wiki.cocoondev.org/Wiki.jsp?page=SurvivalTips
>
> or related pages ;-) ?
>
> Maybe you could contrib a link to jEdit.org ?
> Maybe it is even worthwhile to add a new wikipage for
> "XML-authoring tools" ...
> What do you mean ?
>
> regards, hussayn
>
>>
>> 9.01) I use jEdit.org to all my development in Cocoon. jEdit has a
>> plugins called XML and XSLT. The XML plugin helps writing XML stuff
>> checking the tags. The XSLT pluging helps to see the results of
>> applying 1 or more Stylesheets to a page. This is useful to check what
>> are the stylesheets doing.
>>
>> 
>> I think it will be fine to write a survival guide in wiki. :-)
>> 
>>
>> Antonio Gallardo
>>
>>
> --
> Dr. Hussayn Dabbous
> SAXESS Software Design GmbH
> Neuenhöfer Allee 125
> 50935 Köln
> Telefon: +49-221-56011-0
> Fax: +49-221-56011-20
> E-Mail:  [EMAIL PROTECTED]
>
>
> -
> Please check that your question  has not already been answered in the
> FAQ before posting. 
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail:   <[EMAIL PROTECTED]>




-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Re: 10 basic survival tips for cocoon users (was: Logicsheet problems- global XSLT variables)

[SAXESS - Hussayn Dabbous]

hy Antonio;

What about adding your contrib directly to

http://wiki.cocoondev.org/Wiki.jsp?page=SurvivalTips

or related pages ;-) ?

Maybe you could contrib a link to jEdit.org ?
Maybe it is even worthwhile to add a new wikipage for
"XML-authoring tools" ...
What do you mean ?

regards, hussayn



9.01) I use jEdit.org to all my development in Cocoon. jEdit has a plugins
called XML and XSLT. The XML plugin helps writing XML stuff checking the
tags. The XSLT pluging helps to see the results of applying 1 or more
Stylesheets to a page. This is useful to check what are the stylesheets
doing.


I think it will be fine to write a survival guide in wiki. :-)


Antonio Gallardo



--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail:  [EMAIL PROTECTED]


-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Re: 10 basic survival tips for cocoon users (was: Logicsheet problems - global XSLT variables)

[Antonio Gallardo]

SAXESS - Hussayn Dabbous dijo:
>
> Mark Horgan wrote:
>
>> Also, do others find working with Cocoon very frustrating? When you
>> make a change it takes forever for the web-app to reload and
>> re-compile the java class, espcially when it takes up so much memory.
>> Also even when using the logs its very hard to track down bugs in ones
>> code especially logicsheets. But generally I like Cocoon though I wish
>> it was more straight-forward to develop with it.
>>
>> Thx in advance,
>> Mark
>>
>
> Hy,
>
> When i started with cocoon i got really mad with hunting errors
> and understanding, how all this fits together. But after about
> three months of working with the beast, i built up some
> survival strategies. It is how I do it. It may help as a guide,
> but it does not claim to be the "best approach":
>
> 1.) Instead of restarting the whole container, i only restart
>  the cocoon app, when needed. This takes a few seconds with
>  tomcat 4.1.* (~300 MHz sparc dual processor, solaris 2.8)
> 2.) During development i use tomcat and i set the reloadable="true"
>  within the  of my webapp. By this any changes in the
> classpath causes an automatic webapp restart.
> 3.) use released versions if possible (cocoon-2.0.4 seems quite mature)
> 4.) Proceed in "baby steps" when changing things in your cocoon app 5.)
> follow KISS (keep it simple, stupid) i keep as much as possible
>  with the basics of cocoon and don't use (yet) the more fancy stuff.
> 6.) Separate your app into subsitemaps and subdirs with related issues
> 7.) use the cocoon-wiki
>  Especially the search function unhides
>  interesting docs
> 8.) I started using the "coocon developers handbook"
>  It's written from Lajos Moczar and some other active
>  cocoon developers...
>
> Here are two of my personal favorites. I have documented this in
> our company wiki:
>
> 9.) For XSLT processing i have added Saxon-6.5.2. It's not
>  straight forward to install, but sometimes it can be
>  utilised with less pain, than xalan (just a matter of taste)
>  Look into cocoon wiki for a quick description or look at
>  http://www.saxess.com/JSPWiki/Wiki.jsp?page=Install
>  for a quickinstall step by step instruction.

9.01) I use jEdit.org to all my development in Cocoon. jEdit has a plugins
called XML and XSLT. The XML plugin helps writing XML stuff checking the
tags. The XSLT pluging helps to see the results of applying 1 or more
Stylesheets to a page. This is useful to check what are the stylesheets
doing.


I think it will be fine to write a survival guide in wiki. :-)


Antonio Gallardo

> 10.)use entity resolver wherever possible.
>  look at the cocoon docs for the basics or at
>  http://www.saxess.com/JSPWiki/Wiki.jsp?page=EntityResolver
>  for a quickinstall description.
>
> hope, that helps someone ...
>
> regards, hussayn
>
> --
> Dr. Hussayn Dabbous
> SAXESS Software Design GmbH
> Neuenhöfer Allee 125
> 50935 Köln
> Telefon: +49-221-56011-0
> Fax: +49-221-56011-20
> E-Mail:  [EMAIL PROTECTED]
>
>
> -
> Please check that your question  has not already been answered in the
> FAQ before posting. 
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail:   <[EMAIL PROTECTED]>




-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Re: 10 basic survival tips for cocoon users (was: Logicsheet problems-global XSLT variables)

[SAXESS - Hussayn Dabbous]

I use the following tomcat definition for a cocoon based webapp
that restarts automatically, when classes or jars change:


 



interpretation:

docbasepoints to where the cocoon app resides
reloadable tells tomcat to restart on changes in webapp

the  tag is only needed, if your webapp directory
contains symbolic links or the docbase itself is a symbolic link.

NOT NOTE NOTE!!! caveat:

Your webapp MUST NOT BE DEPLOYED WITHIN THE webapps Directory,
if you use this approach. Otherwise your cocoon app would be
started twice !!!

Just another hint:

Befoire cocoon-2.0.4 the sitemap reloading had a bug, that
crashed cocoon under certain circumstances. This bug has
been fixed with cocoon-2.0.4.


regards, hussayn

Derek Hohls wrote:

Hussayn
 
These tips would be useful on the Cocoon Wiki too!
 
One question - just *how* do you restart only the cocoon app
without restarting tomcat (and do you delete the work files somewhere
in that process as well?)
 
Thanks
Derek

 >>> [EMAIL PROTECTED] 20/01/2003 12:50:26 >>>

Mark Horgan wrote:

 > Also, do others find working with Cocoon very frustrating? When you 
make a
 > change it takes forever for the web-app to reload and re-compile the java
 > class, espcially when it takes up so much memory. Also even when 
using the
 > logs its very hard to track down bugs in ones code especially 
logicsheets.
 > But generally I like Cocoon though I wish it was more straight-forward to
 > develop with it.
 >
 > Thx in advance,
 > Mark
 >

Hy,

When i started with cocoon i got really mad with hunting errors
and understanding, how all this fits together. But after about
three months of working with the beast, i built up some
survival strategies. It is how I do it. It may help as a guide,
but it does not claim to be the "best approach":

1.) Instead of restarting the whole container, i only restart
 the cocoon app, when needed. This takes a few seconds with
 tomcat 4.1.* (~300 MHz sparc dual processor, solaris 2.8)
2.) During development i use tomcat and i set the reloadable="true"
 within the  of my webapp. By this any changes in the
 classpath causes an automatic webapp restart.
3.) use released versions if possible (cocoon-2.0.4 seems quite mature)
4.) Proceed in "baby steps" when changing things in your cocoon app
5.) follow KISS (keep it simple, stupid) i keep as much as possible
 with the basics of cocoon and don't use (yet) the more fancy stuff.
6.) Separate your app into subsitemaps and subdirs with related issues
7.) use the cocoon-wiki
 Especially the search function unhides
 interesting docs
8.) I started using the "coocon developers handbook"
 It's written from Lajos Moczar and some other active
 cocoon developers...

Here are two of my personal favorites. I have documented this in
our company wiki:

9.) For XSLT processing i have added Saxon-6.5.2. It's not
 straight forward to install, but sometimes it can be
 utilised with less pain, than xalan (just a matter of taste)
 Look into cocoon wiki for a quick description or look at
 http://www.saxess.com/JSPWiki/Wiki.jsp?page=Install
 for a quickinstall step by step instruction.
10.)use entity resolver wherever possible.
 look at the cocoon docs for the basics or at
 http://www.saxess.com/JSPWiki/Wiki.jsp?page=EntityResolver
 for a quickinstall description.

hope, that helps someone ...

regards, hussayn

--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail:  [EMAIL PROTECTED]


-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>


--
This message has been scanned for viruses and dangerous content by
*MailScanner* , and is believed to be clean.

"The CSIR exercises no editorial control over E-mail messages and/or
attachments thereto/links referred to therein originating in the
organisation and the views in this message/attachments thereto are
therefore not necessarily those of the CSIR and/or its employees.
The sender of this e-mail is, moreover, in terms of the CSIR's Conditions
of Service, subject to compliance with the CSIR's internal E-mail and
Internet Policy."

--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail:  [EMAIL PROTECTED]


-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

10 basic survival tips for cocoon users (was: Logicsheet problems- global XSLT variables)

[SAXESS - Hussayn Dabbous]

Mark Horgan wrote:


Also, do others find working with Cocoon very frustrating? When you make a
change it takes forever for the web-app to reload and re-compile the java
class, espcially when it takes up so much memory. Also even when using the
logs its very hard to track down bugs in ones code especially logicsheets.
But generally I like Cocoon though I wish it was more straight-forward to
develop with it.

Thx in advance,
Mark



Hy,

When i started with cocoon i got really mad with hunting errors
and understanding, how all this fits together. But after about
three months of working with the beast, i built up some
survival strategies. It is how I do it. It may help as a guide,
but it does not claim to be the "best approach":

1.) Instead of restarting the whole container, i only restart
the cocoon app, when needed. This takes a few seconds with
tomcat 4.1.* (~300 MHz sparc dual processor, solaris 2.8)
2.) During development i use tomcat and i set the reloadable="true"
within the  of my webapp. By this any changes in the
classpath causes an automatic webapp restart.
3.) use released versions if possible (cocoon-2.0.4 seems quite mature)
4.) Proceed in "baby steps" when changing things in your cocoon app
5.) follow KISS (keep it simple, stupid) i keep as much as possible
with the basics of cocoon and don't use (yet) the more fancy stuff.
6.) Separate your app into subsitemaps and subdirs with related issues
7.) use the cocoon-wiki
Especially the search function unhides
interesting docs
8.) I started using the "coocon developers handbook"
It's written from Lajos Moczar and some other active
cocoon developers...

Here are two of my personal favorites. I have documented this in
our company wiki:

9.) For XSLT processing i have added Saxon-6.5.2. It's not
straight forward to install, but sometimes it can be
utilised with less pain, than xalan (just a matter of taste)
Look into cocoon wiki for a quick description or look at
http://www.saxess.com/JSPWiki/Wiki.jsp?page=Install
for a quickinstall step by step instruction.
10.)use entity resolver wherever possible.
look at the cocoon docs for the basics or at
http://www.saxess.com/JSPWiki/Wiki.jsp?page=EntityResolver
for a quickinstall description.

hope, that helps someone ...

regards, hussayn

--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail:  [EMAIL PROTECTED]


-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Re: Logicsheet problems - global XSLT variables

[Antonio Gallardo]

> Also, do others find working with Cocoon very frustrating? When you make
> a change it takes forever for the web-app to reload and re-compile the
> java class, espcially when it takes up so much memory.

You need to add in your cocoon.xconf file:



Search for the  tag and add the attributes:

reload-method="synchron"
check-reload="yes"

Antonio Gallardo

>
> Thx in advance,
> Mark
>
>
>
> -
> Please check that your question  has not already been answered in the
> FAQ before posting. 
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail:   <[EMAIL PROTECTED]>




-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Logicsheet problems - global XSLT variables

[Mark Horgan]

I'm having a hard time with logicsheets at the moment. I can't seem to get
global XSLT variables working. Am I doing something wrong?



nor

dkitCareers

work



...


I've looked at the generated java code and it's replacing {$datasource} with
nothing

Also, do others find working with Cocoon very frustrating? When you make a
change it takes forever for the web-app to reload and re-compile the java
class, espcially when it takes up so much memory. Also even when using the
logs its very hard to track down bugs in ones code especially logicsheets.
But generally I like Cocoon though I wish it was more straight-forward to
develop with it.

Thx in advance,
Mark



-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Logicsheet problems - global XSLT variables

[Mark H]

I'm having a hard time with logicsheets at the moment. I can't seem to get
global XSLT variables working. Am I doing something wrong?



nor

dkitCareers

work



...


I've looked at the generated java code and it's replacing {$datasource} with
nothing

Thx in advance,
Mark



-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>