> -----Original Message----- > From: Ross Gardler [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 4 April 2006 2:11 AM > To: [email protected] > Subject: Re: Working - RE: Glossary Plugin FOR-755 - was RE: [jira] > Updated: (FOR-639) define terminology for the various aspects of > Dispatcher > > Gav.... wrote: > > > >>-----Original Message----- > >>From: Ross Gardler [mailto:[EMAIL PROTECTED] > >>Sent: Monday, 3 April 2006 8:00 PM > >>To: [email protected] > >>Subject: Re: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) > >>define terminology for the various aspects of Dispatcher > >> > >>Thorsten Scherler wrote: > >> > >>>El lun, 03-04-2006 a las 17:00 +0800, Gav.... escribió: > >>>... > >>> > >>> > >>>>Definitely something wrong I think. I can put in deliberate mistakes, > >>>>jargon, delete tags, close tags twice and it makes not a bit of > >> > >>difference. > >> > >>>>I can delete the input.xmap file altogether and it cares not, no > >> > >>difference, > >> > >>>>the site still builds fine and the glossary.xml file still displays > only > >>>>menus & tabs and no content. > >>> > >>> > >>>Well that sounds like you should do a build clean (on forrest and your > >>>plugin), since if you can have an invalid input.xmap that raises the > >>>suspicion that an old (valid) one is being used (the already deployed > >>>one). > >> > >>Yes, that sounds possible, you need to do "ant local-deploy" inside the > >>plugin dir every time you make a change to the plugin code, otherwise > >>you will be using the old code. See the plugin How To doc. > >> > >>(actually, to be totally accurate you don't need to do "ant > >>local-deploy" after a you clean build Forrest, as if the plugin is not > >>present it will auto deploy) > > > > > > Blimey, it does seem as though it helps, but to do it every time I made > a > > change was a bit tedious. However I found if I did not, some changes I > made > > would not be effective. > > It is not necessary to build Forrest after every change, only to do a > local-deploy of the plugin you have changed. Thorsten recommended a > clean build (as a one off) because it would mean we knew what state you > were in with respect to builds etc. > > You should also note there is also no need to restart Forrest after each > local-deploy the plugin for most changes. Some changes, just locationmap > and java I think, do require a restart, but most do not. > > There is an issue to use plugins in-place, when complete this will > remove the need to do the local-deploy, but it is a work in progress at > this point. > > > I also had to ant local-deploy the projectInfo > > plugin each time. > > There should be no need for this, plugins should be auto-deployed on the > first run. The requirement for local-deploy is only for plugins you have > changed > > ... > > > Well, I have had some success now :) > > > > I have the plugin working now and the sample glossary.html file works > just > > fine. :) > > Wooo Hooo! Well done. > > > But, (and there usually is a 'but' with me!), I have had to it using > > workarounds otherwise I just could not get it to go. > > > > 1. Mentioned previously, 'glossary-v10.dtd' and 'glossary-v10.mod' MUST > be > > in the /xdocs/directory otherwise they are not found and it will not > work. > > If not there, error message is saying they are not found and is pointing > to > > the xdocs directory. > > David hinted at the solution to this earlier on. For an example of what > to do see: > > http://svn.apache.org/viewcvs.cgi/forrest/trunk/plugins/org.apache.forrest > .plugin.input.listLocations/resources/schema/ > > In particular look at the catalog.xcat file, just copy the setup here > (with obvious changes) and it should all work. Don't forget to remove > the DTD's from the XDoc directory or Forrest will continue to pick those > up.
I have added back in the catalog.xcat file, containing :- <!DOCTYPE catalog PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN" "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd";> <!-- OASIS XML Catalog for Forrest Documents --> <catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog" prefer="public"> <public publicId="-//Apache Forrest//DTD Glossary V1.0//EN" uri="glossary-v10.dtd"/> </catalog> And removed the .dtd and .mod files from /xdocs/ I am now getting different errors, Recursive entity reference "%glossary". (Reference path: %glossary -> %glossary -> %glossary), >From a forrest run and similar in an Ant Test failure report. The glossary-v10.dtd has :- <!ENTITY % document PUBLIC "-//APACHE//ENTITIES Documentation V1.2//EN" "document-v12.mod"> %document; <!-- =============================================================== --> <!-- Include the Common ISO Character Entity Sets --> <!-- =============================================================== --> <!ENTITY % common-charents PUBLIC "-//APACHE//ENTITIES Common Character Entity Sets V1.0//EN" "common-charents-v10.mod"> %common-charents; <!-- =============================================================== --> <!-- Document Type Definition --> <!-- =============================================================== --> <!ENTITY % glossary PUBLIC "-//Apache Forrest//DTD Glossary V1.0//EN" "glossary-v10.mod"> %glossary; Gav... > > This should really be documented in the plugins howto if you get the > opportunity to do so whilst working out what to do. > > > 2. To get rid of another resource not found error message, I had to put > > copyover.xsl into the /resources/stylesheets/ directory. > > > > Workaround 2. may be a necessity I don't know. > > Leave that in for now. I have solution in mind, but involves some > (minor) work on core, so we'll eave it for now. > > > Should I maybe send in a patch for what I have so you guys arent > working > > blind? > > The solution to 1 is easy (once you know how). I'm confident that you'll > understand from the above comments, if not then by all means submit a > patch with what you have done it is the majority of the work and you no > know how to create a plugin ;-) > > Ross > > > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.1.385 / Virus Database: 268.3.4/299 - Release Date: 31/03/2006
