You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Mark Horgan <me...@markhorgan.com> on 2003/01/19 22:11:53 UTC

Logicsheet problems - global XSLT variables

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?

<xsl:stylesheet version="1.0"...

<xsl:variable name="datasource"><input:get-attribute module="global"
name="datasource" as="string"/></xsl:variable>

nor

<xsl:variable name="datasource">dkitCareers</xsl:variable>

work

<xsl:template match="mh:get-editable-region">
    <xmldb:collection uri="xmldb:xindice:///db/{$datasource}">
    ...
</xsl:template>

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.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>


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

Posted by Antonio Gallardo <ag...@agsoftware.dnsalias.com>.
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.
>>
>> <comment>
>> I think it will be fine to write a survival guide in wiki. :-)
>> </comment>
>>
>> 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:  dabbous@saxess.com
>
>
> ---------------------------------------------------------------------
> 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:     <co...@xml.apache.org>
> For additional commands, e-mail:   <co...@xml.apache.org>




---------------------------------------------------------------------
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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>


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

Posted by SAXESS - Hussayn Dabbous <da...@saxess.com>.
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.
> 
> <comment>
> I think it will be fine to write a survival guide in wiki. :-)
> </comment>
> 
> 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:  dabbous@saxess.com


---------------------------------------------------------------------
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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>


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

Posted by Antonio Gallardo <ag...@agsoftware.dnsalias.com>.
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 <Context/> 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.

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

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:  dabbous@saxess.com
>
>
> ---------------------------------------------------------------------
> 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:     <co...@xml.apache.org>
> For additional commands, e-mail:   <co...@xml.apache.org>




---------------------------------------------------------------------
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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>


RE: can't get browser selector working

Posted by Reinhard Pötz <re...@gmx.net>.
> -----Original Message-----
> From: Hans Thomas Nordeck [mailto:h.nordeck@juwimm.com] 
>
> I want to use the browser selector in a mounted sitemap. The 
> selector is well defined in the components part of the 
> sitemap. The Parameter "viewType" never gets a value. I can't 
> get it working.  Does anybody has an idea what the problem 
> is? (I'm working with cocoon 2.1 dev, do you think that could 
> be the problem? cause for me everything looks right)
> 
> Thanks a lot for help!


Selectors can't be used to selecet between parameters. Selectors are
sitemap components that enable to select between other components. An
example can be found here:
http://xml.apache.org/cocoon/userdocs/selectors/selectors.html

If you want to select between parameters of an action do it within your
action.

Regards,
Reinhard


> 
> <map:match pattern="*/**/content.html">
>  <map:act type="cms.actions.template">
>   <map:parameter name="parameters" value="true"/>
>   <map:parameter name="language" value="{1}"/>
>   <map:parameter name="path" value="{2}"/>
>  <map:select type="browser">
>          <map:when test="pocketexplorer">
>           <map:parameter name="viewType" value="browser"/>
>          </map:when>
>          <map:otherwise>
>           <map:parameter name="viewType" value="browser"/>
>          </map:otherwise>
>     </map:select>
>   <map:generate type="CmsContent">
>    <map:parameter name="parameters" value="true"/>
>    <map:parameter name="viewComponentId" value="{viewComponentId}"/>
>   </map:generate>
> 
>   <map:transform src="templates/{template}.xsl"/>
> 
>   <map:serialize type="html"/>
>  </map:act>
> </map:match>
> 
> 
> ---------------------------------------------------------------------
> 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:     <co...@xml.apache.org>
> For additional commands, e-mail:   <co...@xml.apache.org>
> 


---------------------------------------------------------------------
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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>


can't get browser selector working

Posted by Hans Thomas Nordeck <h....@juwimm.com>.
I want to use the browser selector in a mounted sitemap. The selector is
well defined in the components part of the sitemap.
The Parameter "viewType" never gets a value.
I can't get it working.  Does anybody has an idea what the problem is?
(I'm working with cocoon 2.1 dev, do you think that could be the problem?
cause for me everything looks right)

Thanks a lot for help!


<map:match pattern="*/**/content.html">
 <map:act type="cms.actions.template">
  <map:parameter name="parameters" value="true"/>
  <map:parameter name="language" value="{1}"/>
  <map:parameter name="path" value="{2}"/>
 <map:select type="browser">
         <map:when test="pocketexplorer">
          <map:parameter name="viewType" value="browser"/>
         </map:when>
         <map:otherwise>
          <map:parameter name="viewType" value="browser"/>
         </map:otherwise>
    </map:select>
  <map:generate type="CmsContent">
   <map:parameter name="parameters" value="true"/>
   <map:parameter name="viewComponentId" value="{viewComponentId}"/>
  </map:generate>

  <map:transform src="templates/{template}.xsl"/>

  <map:serialize type="html"/>
 </map:act>
</map:match>


---------------------------------------------------------------------
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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>


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

Posted by SAXESS - Hussayn Dabbous <da...@saxess.com>.
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:  dabbous@saxess.com


---------------------------------------------------------------------
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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>


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

Posted by Mark H <ma...@markhorgan.com>.
> Are you saying that Xerces doesn't deal with global XSLT variables
properly?

sorry, that should be Xalan

-----Original Message-----
From: Mark H [mailto:mailinglists@markhorgan.com]
Sent: 21 January 2003 13:58
To: cocoon-users@xml.apache.org
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:dabbous@saxess.com]
Sent: 20 January 2003 10:50
To: cocoon-users@xml.apache.org
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 <Context/> 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:  dabbous@saxess.com


---------------------------------------------------------------------
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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>






---------------------------------------------------------------------
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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>






---------------------------------------------------------------------
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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>


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

Posted by Mark H <ma...@markhorgan.com>.
> 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:dabbous@saxess.com]
Sent: 20 January 2003 10:50
To: cocoon-users@xml.apache.org
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 <Context/> 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:  dabbous@saxess.com


---------------------------------------------------------------------
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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>






---------------------------------------------------------------------
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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>


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

Posted by SAXESS - Hussayn Dabbous <da...@saxess.com>.
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 <Context/> 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:  dabbous@saxess.com


---------------------------------------------------------------------
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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>


RE: Logicsheet problems - global XSLT variables

Posted by Antonio Gallardo <ag...@agsoftware.dnsalias.com>.
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:agallardo@agsoftware.dnsalias.com]
> Sent: 20 January 2003 06:34
> To: cocoon-users@xml.apache.org
> 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:
>
> <sitemap reload-method="synchron" check-reload="yes"
> config="resource://org/apache/cocoon/components/treeprocessor/treeprocessor-
> builtins.xml"
> file="context://sitemap.xmap" logger="sitemap"/>
>
> Search for the <sitemap> 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:     <co...@xml.apache.org>
>> For additional commands, e-mail:   <co...@xml.apache.org>
>
>
>
>
> ---------------------------------------------------------------------
> 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:     <co...@xml.apache.org>
> For additional commands, e-mail:   <co...@xml.apache.org>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> 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:     <co...@xml.apache.org>
> For additional commands, e-mail:   <co...@xml.apache.org>




---------------------------------------------------------------------
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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>


RE: Logicsheet problems - global XSLT variables

Posted by Mark H <ma...@markhorgan.com>.
Thanks Antonio, I'll try it out. How does the reload-method="synchron"
improve things?

-----Original Message-----
From: Antonio Gallardo [mailto:agallardo@agsoftware.dnsalias.com]
Sent: 20 January 2003 06:34
To: cocoon-users@xml.apache.org
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:

<sitemap reload-method="synchron" check-reload="yes"
config="resource://org/apache/cocoon/components/treeprocessor/treeprocessor-
builtins.xml"
file="context://sitemap.xmap" logger="sitemap"/>

Search for the <sitemap> 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:     <co...@xml.apache.org>
> For additional commands, e-mail:   <co...@xml.apache.org>




---------------------------------------------------------------------
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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>






---------------------------------------------------------------------
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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>


Re: Logicsheet problems - global XSLT variables

Posted by Antonio Gallardo <ag...@agsoftware.dnsalias.com>.
> 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:

<sitemap reload-method="synchron" check-reload="yes"
config="resource://org/apache/cocoon/components/treeprocessor/treeprocessor-builtins.xml"
file="context://sitemap.xmap" logger="sitemap"/>

Search for the <sitemap> 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:     <co...@xml.apache.org>
> For additional commands, e-mail:   <co...@xml.apache.org>




---------------------------------------------------------------------
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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>