Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Forrest: Dev

[jira] [Commented] (FOR-1234) Dispatcher caches too eagerly

 

 

Forrest dev RSS feed   Index | Next | Previous | View Threaded


jira at apache

Jul 15, 2012, 12:03 PM

Post #1 of 4 (444 views)
Permalink
[jira] [Commented] (FOR-1234) Dispatcher caches too eagerly

[ https://issues.apache.org/jira/browse/FOR-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414738#comment-13414738 ]

Brian M Dube commented on FOR-1234:
-----------------------------------

There is a workaround mentioned in the dispatcher quickstart documentation. That is, in your structurer file, to remove the cache settings from:

<forrest:structurer xmlns:forrest="http://apache.org/forrest/templates/1.0"
xmlns:jx="http://apache.org/cocoon/templates/jx/1.0"
jx:cache-key="#{$cocoon/parameters/getRequest}"
jx:cache-validity="${Packages.org.apache.excalibur.source.impl.validity.NOPValidity()}">

to:

<forrest:structurer xmlns:forrest="http://apache.org/forrest/templates/1.0"
xmlns:jx="http://apache.org/cocoon/templates/jx/1.0">


> Dispatcher caches too eagerly
> -----------------------------
>
> Key: FOR-1234
> URL: https://issues.apache.org/jira/browse/FOR-1234
> Project: Forrest
> Issue Type: Bug
> Components: Whiteboard: Dispatcher (stax)
> Affects Versions: 0.9, 0.10-dev
> Reporter: Børre Gaup
>
> When editing content pages in forrest I can't see the changes in the web browser when refreshing the page. I have to restart forrest to see any changes of the content in the browser.
> Here are two threads on the issue:
> http://thread.gmane.org/gmane.text.xml.forrest.user/5034
> http://thread.gmane.org/gmane.text.xml.forrest.devel/27855

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


jira at apache

Jul 15, 2012, 1:11 PM

Post #2 of 4 (417 views)
Permalink
[jira] [Commented] (FOR-1234) Dispatcher caches too eagerly [In reply to]

[ https://issues.apache.org/jira/browse/FOR-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414760#comment-13414760 ]

Børre Gaup commented on FOR-1234:
---------------------------------

Thank you very much for the tip, works like a charm! (Should have read the fine manual, though ;) )

> Dispatcher caches too eagerly
> -----------------------------
>
> Key: FOR-1234
> URL: https://issues.apache.org/jira/browse/FOR-1234
> Project: Forrest
> Issue Type: Bug
> Components: Whiteboard: Dispatcher (stax)
> Affects Versions: 0.9, 0.10-dev
> Reporter: Børre Gaup
>
> When editing content pages in forrest I can't see the changes in the web browser when refreshing the page. I have to restart forrest to see any changes of the content in the browser.
> Here are two threads on the issue:
> http://thread.gmane.org/gmane.text.xml.forrest.user/5034
> http://thread.gmane.org/gmane.text.xml.forrest.devel/27855

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


bdube at apache

Jul 15, 2012, 7:14 PM

Post #3 of 4 (413 views)
Permalink
Re: [jira] [Commented] (FOR-1234) Dispatcher caches too eagerly [In reply to]

On 07/15/2012 12:03 PM, Brian M Dube (JIRA) wrote:
>
> [ https://issues.apache.org/jira/browse/FOR-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414738#comment-13414738 ]
>
> Brian M Dube commented on FOR-1234:
> -----------------------------------
>
> There is a workaround mentioned in the dispatcher quickstart documentation. That is, in your structurer file, to remove the cache settings from:
>
> <forrest:structurer xmlns:forrest="http://apache.org/forrest/templates/1.0"
> xmlns:jx="http://apache.org/cocoon/templates/jx/1.0"
> jx:cache-key="#{$cocoon/parameters/getRequest}"
> jx:cache-validity="${Packages.org.apache.excalibur.source.impl.validity.NOPValidity()}">
>
> to:
>
> <forrest:structurer xmlns:forrest="http://apache.org/forrest/templates/1.0"
> xmlns:jx="http://apache.org/cocoon/templates/jx/1.0">

It seems the documentation for this plugin is not available on the
Forrest website. Is 'ant deploy-docs' from the plugin directory the
correct thing to do?

Brian


crossley at apache

Jul 17, 2012, 5:55 PM

Post #4 of 4 (410 views)
Permalink
Re: [jira] [Commented] (FOR-1234) Dispatcher caches too eagerly [In reply to]

Brian M Dube wrote:
> >
> > [ https://issues.apache.org/jira/browse/FOR-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414738#comment-13414738 ]
> >
> > Brian M Dube commented on FOR-1234:
> > -----------------------------------
> >
> > There is a workaround mentioned in the dispatcher quickstart documentation. That is, in your structurer file, to remove the cache settings from:
> >
> > <forrest:structurer xmlns:forrest="http://apache.org/forrest/templates/1.0"
> > xmlns:jx="http://apache.org/cocoon/templates/jx/1.0"
> > jx:cache-key="#{$cocoon/parameters/getRequest}"
> > jx:cache-validity="${Packages.org.apache.excalibur.source.impl.validity.NOPValidity()}">
> >
> > to:
> >
> > <forrest:structurer xmlns:forrest="http://apache.org/forrest/templates/1.0"
> > xmlns:jx="http://apache.org/cocoon/templates/jx/1.0">
>
> It seems the documentation for this plugin is not available on the
> Forrest website. Is 'ant deploy-docs' from the plugin directory the
> correct thing to do?

I do not know the state of Dispatcher. There was a big review
of all plugins deployment recently-ish. See the mailing list and
$FORREST_HOME/etc/review-plugin-deployment.txt
The last time it was deployed was back in forrest-0.8

Following on from that review there was supposed to be a
re-assessment of how we handle all plugins. However no-one
has found the energy yet.

In the meantime, people who use un-released whiteboard stuff
would be better off to use the current head of SVN and recognise
that they are being a "developer".

-David

Forrest dev RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.