Re: problem with feeder plugin

2009-11-03 Thread Vicent Mas
 2009/11/2 Vicent Mas uve...@gmail.com:
 
 ...
 
  This was wrong. The file has not xdoc format. Simply
 
  feedDescriptor
feed id=BBCSport_UK
   urlhttp://news.bbc.co.uk/rss/sportonline_uk_edition/front_page/rss.xml
 /url /feed
  /feedDescriptor
 
  in a file named feedDescriptor.xml works.
 
 You mean exactly as documented in
 http://forrest.apache.org/pluginDocs/plugins_0_80/org.apache.forrest.plugin
 .input.feeder/samples/singleFeed.html (which you linked to)


Yes, the key word is *exactly* :-)

 Thanks for following up onlist, this makes it easier for those coming
 after you. Clearly the documentation is not very clear, if you can
 provide a patch for the plugins documentation that would be very much
 appreciated.
 
 Ross
 

Well, I cannot do it for the pluginS but I can for the feeder plugin :-). When 
doing it I've realized that in page

http://forrest.apache.org/pluginDocs/plugins_0_90/index.html

most of plugin links (including the feeder plugin) are pointing to 0_80 docs. 
I've done a patch for the current revision of trunk, r832303. The patch has to 
be applied to feeder_dir/src/documentation/content/xdocs/index.xml

I also dowloaded the current official release tarball for linux but I cannot 
find 
the plugin sources there. So I've not pached it for the 0.80 version.

Vicent 
::

Share what you know, learn what you don't

--- index.xml	2009-11-03 08:27:20.0 +0100
+++ index_new.xml	2009-11-03 08:49:14.0 +0100
@@ -53,6 +53,13 @@
 /feedDescriptor
 ]]
 /source
+
+p
+  Note that the codefeedDescriptor/code file has strongnot/strong
+  xdoc format. A file named codefeedDescriptor.xml/code with exactly the
+  above content should just work.
+/p
+
 p
   In order to embed the data from the codeplanetApache/code feed you
   create a link in the following form:
@@ -66,9 +73,9 @@
   want the feed to be delivered in (i.e. html, pdf etc.)
 /p
   ul
-lia href=samples/singleFeed.rssAs RSS/a/li
-lia href=samples/singleFeed.rss.xmlAs XDoc/a/li
-lia href=samples/singleFeed.rss.htmlAs HTML/a/li
+lia href=samples/singleFeed.rssAs RSS/a (no EXTENSION)/li
+lia href=samples/singleFeed.rss.xmlAs XDoc/a (xml EXTENSION)/li
+lia href=samples/singleFeed.rss.htmlAs HTML/a (html EXTENSION)/li
   /ul
 /section
   /section


signature.asc
Description: This is a digitally signed message part.


Re: problem with feeder plugin

2009-11-03 Thread David Crossley
Vicent Mas wrote:
  Vicent Mas wrote: 
  
  Thanks for following up onlist, this makes it easier for those coming
  after you. Clearly the documentation is not very clear, if you can
  provide a patch for the plugins documentation that would be very much
  appreciated.
 
 Well, I cannot do it for the pluginS but I can for the feeder plugin :-). 
 When 
 doing it I've realized that in page
 
 http://forrest.apache.org/pluginDocs/plugins_0_90/index.html

That is a generated page.

 most of plugin links (including the feeder plugin) are pointing to 0_80 docs. 

Yes, only plugins that require 0.9-dev (trunk) functionality are
deployed to the 0_90 space. Otherwise the 0_80 will work
with both.

See the forrestVersion attribute in
$FORREST_HOME/plugins/plugins.xml
$FORREST_HOME/whiteboard/plugins/whiteboard-plugins.xml
which is reflected in Minimum Forrest version required rows
in the table at http://forrest.apache.org/pluginDocs/plugins_0_90/

 I've done a patch for the current revision of trunk, r832303. The patch has 
 to 
 be applied to feeder_dir/src/documentation/content/xdocs/index.xml
 
 I also dowloaded the current official release tarball for linux but I cannot 
 find 
 the plugin sources there. So I've not pached it for the 0.80 version.

That is because code for all plugins is in the SVN trunk,
and installations based on releases will download the plugins from
apache.org as required.

So you did patch the correct source. When the changes are applied
and the plugin deployed, then that will update the plugin docs
at the 0_80 space (as explained above).

-David


Re: problem with feeder plugin

2009-11-02 Thread Vicent Mas
 Hi,
 
 In a recent post I've been suggested to have a look to the feeder plugin
 (among others) as it could help me to deal with problems in a customised
 contract. I've done it, but I cannot manage to get the plugin working in my
 website. Following the instructions in the feeder plugin site,
 http://forrest.apache.org/pluginDocs/plugins_0_80/org.apache.forrest.plugin
 .input.feeder/index.html:
 
 - I've created a feedDescriptor.xml with the content
 
 document
   head
 titleTest/title
   /head
   body
 feedDescriptor
   feed id=BBCSport_UK

  urlhttp://news.bbc.co.uk/rss/sportonline_uk_edition/front_page/rss.xml/
 url /feed
 /feedDescriptor
   /body
 /document
 
 Nothing is said in the webpage about filename extension or format. I'm
  assuming it has to be a xdoc document with .xml extension. The file lives
  in the xdocs directory of my project (i.e.
  src/documentation/content/xdocs)
 

This was wrong. The file has not xdoc format. Simply 

feedDescriptor
   feed id=BBCSport_UK
  
urlhttp://news.bbc.co.uk/rss/sportonline_uk_edition/front_page/rss.xml/url 
/feed
/feedDescriptor

in a file named feedDescriptor.xml works.

Vicent
::

Share what you know, learn what you don't



signature.asc
Description: This is a digitally signed message part.


Re: problem with feeder plugin

2009-11-02 Thread Ross Gardler
2009/11/2 Vicent Mas uve...@gmail.com:

...

 This was wrong. The file has not xdoc format. Simply

 feedDescriptor
   feed id=BBCSport_UK
  urlhttp://news.bbc.co.uk/rss/sportonline_uk_edition/front_page/rss.xml/url
 /feed
 /feedDescriptor

 in a file named feedDescriptor.xml works.


You mean exactly as documented in
http://forrest.apache.org/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.feeder/samples/singleFeed.html
(which you linked to)

Thanks for following up onlist, this makes it easier for those coming
after you. Clearly the documentation is not very clear, if you can
provide a patch for the plugins documentation that would be very much
appreciated.

Ross