You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "Gav...." <br...@brightontown.com.au> on 2006/04/01 13:34:03 UTC
Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Hi All,
> -----Original Message-----
> From: David Crossley [mailto:crossley@apache.org]
> Sent: Saturday, 1 April 2006 6:42 AM
> To: dev@forrest.apache.org; brightoncomputers@brightontown.com.au
> Subject: Re: [jira] Updated: (FOR-639) define terminology for the various
> aspects of Dispatcher
>
> Gav.... wrote:
> > Ok, Paul has also mentioned this so needs sorting, I'll see what I can
> come
> > up with in the next day or two.
> >
> > What we have so far it terms of Dispatcher Docs published:-
> >
> > dispatcher.html
> > howto-structurer-install.html
> > howto-dispatcher-quickstart.html
> > howto-structurer-dsl.html
> > howto-structurer-contracts.html
> >
> > The howto-structurer-install.html is actually describing how to
> > Install the "Dispatcher" so I think should be renamed to avoid
> > Further confusion.
>
> Yes, i have wondered about that too.
> Today i will 'svn move' the documents,
> amend all the links and references, and
> create .htaccess redirects for the website.
>
> > The howto-structurer-dsl is out of date and contains incorrect
> > Contract examples. Is there an upto date version of this or
> > Shall I attempt to correct the examples given.
> > Also, I would like an example of what is meant by
> > "Domain Specific" in this context (of -dsl)
> >
> > This FOR is about clarifying and defining terminology used. So do we
> > Want a new page called dispatcher-terminology.html or similar and how
> > Do we want the content presented - in example form, or in a strict
> > Dictionary type arrangement leaving the examples on the howto pages?
>
> There was a mailing list discussion about this.
> Need to find that.
>
> One really good idea was to create the new Glossary plugin
> http://issues.apache.org/jira/browse/FOR-755
> and use that.
Ok, I have started this, created the basic Glossary output plugin,
Now need to configure it.
I have questions (never done a plugin before so bear with me) :-
I'm referring to the attachments provided on FOR-755 here -
1. Does glossary.xmap get renamed to and therefore replace output.xmap ?
2.Where do the .dtd and .mod files need to go?
3a. I have put glossary2document.xsl in resources/stylesheets, is this
correct?
3b. And will I need to rename it to glossary-to-document.xsl ?
3c. If yes to 3b, anything else to change?
4. Glossary.xml is placed in the xdocs directory, this is the main file we
Need to add our Terminology. Looking quickly, its an A-Z arrangement, can we
and should we have a separate A-Z for Dispatcher Terminology, therefore a
separate dispatcher-glossary.xml file, or will ALL Forrest terminology
reside in the same Glossary.xml file?
I am doing this in Whiteboard at the moment, is this ok?
I am not creating samples, I could rename Ross's original Glossary.xml to
something else and use that as a sample ?
Anything else?
Lots of 'Q''s in there, sorry.
1 hour later ...
Ant Test - Build Failed die to could not validate Glossary.xml, I guess
that's because the .dtd and .mod files are in the wrong place.
Gav...
>
> Failing that, i reckon just use an ordinary document
> with concise definitions that link to examples in
> the other documents.
I have started this also, in fact started in when your idea of
Using the Glossary Plugin came through. Hmm, I wonder which I'll
Finish first :)
>
> However it gets done is good.
>
> -David
On it,
Gav...
Re: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
define terminology for the various aspects of Dispatcher
Posted by Ross Gardler <rg...@apache.org>.
David Crossley wrote:
> Gav.... wrote:
>
>>Ok, I have started this, created the basic Glossary output plugin,
>>Now need to configure it.
Great stuff. Thanks Gavin. One thing to bear in mind is that this code
was written against 0.5 of Forrest. There was no plugin infrastructure,
no locationmap, no XML config system, not dispatcher etc. etc.
We can improve on this plugin a great deal. But lets go one step at a time.
David has already addressed many of your questions. I'll just add what I
can.
>>4. Glossary.xml is placed in the xdocs directory, this is the main file we
>>Need to add our Terminology. Looking quickly, its an A-Z arrangement, can we
>>and should we have a separate A-Z for Dispatcher Terminology, therefore a
>>separate dispatcher-glossary.xml file, or will ALL Forrest terminology
>>reside in the same Glossary.xml file?
>
>
> No this doesn't happen in the plugin
> (apart from a simple example). The real data files
> go in whatever project that the user creates.
> For example the forrest project will use it
> in site-author/content/xdocs/**
>
> I expect that is better to allow separate glossary
> data files. They can be any filename because the input.xmap
> should respond on the Content Aware Pipeline, i.e. the
> source-type action responding on the document type declaration
> or namespace.
>
> The listLocations plugins uses a horrid workaround
> to match on the filename. It needs to be fixed to
> use the publicIdentifier in the XML instance document.
If I remember correctly the glossary code already uses the sourcetype
action to decide ow to process the file. This means there is not need to
add any code to create individual files for A, B, C etc. Just create the
file "glossary-a.xml", "glossary-b.xml" etc. Link to them as normal and
it will work.
>>I am doing this in Whiteboard at the moment, is this ok?
Yes, it should be in whiteboard until:
a) it works fully
b) it is documented
c) it has community support
>>I am not creating samples, I could rename Ross's original Glossary.xml to
>>something else and use that as a sample ?
>
>
> Use lowercase filenames.
>
> No, that datafile is Ross' example. I reckon
> create a really trivial example data file.
It's OK, at least in the short term, to use the example I have provided.
There are a few definitions from external sources, but the plugin gives
an appropriate credit in all cases.
> Say four entries, using very obvious terms, e.g.
> HTML = HyperText Markup Language
> CSS = Cascading Style Sheets
> ASF = Apache Software Foundation
> ... perhaps use one of those with an example
> link to another site.
Ultimately we will want to build a Forrest specific Glossary. So if you
get the time to do this then cool!
Ross
Re: Working - RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by David Crossley <cr...@apache.org>.
Please don't change the name of the email threads
unless it is a completely new topic. It stuffs up
the email archives.
More below ...
Ross Gardler wrote:
> Gav.... wrote:
> >>From: Ross Gardler
> >>Thorsten Scherler wrote:
> >>> 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
I see that howto-buildPlugin is a bit vague on the
need for local-deploy after making changes. I will
try to enhance that.
> >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.
The entity resolver, if properly configured via a catalog.xcat
will take precedence.
> This should really be documented in the plugins howto if you get the
> opportunity to do so whilst working out what to do.
I have updated the howto-buildPlugin doc.
-David
> >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 aren?t 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
>
RE: Working - RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by "Gav...." <br...@brightontown.com.au>.
> -----Original Message-----
> From: Ross Gardler [mailto:rgardler@apache.org]
> Sent: Wednesday, 5 April 2006 4:45 PM
> To: dev@forrest.apache.org
> Subject: Re: Working - RE: Glossary Plugin FOR-755 - was RE: [jira]
> Updated: (FOR-639) define terminology for the various aspects of
> Dispatcher
>
> David Crossley wrote:
>
> > So now everyone who was listening to this thread should
> > know a bit more about the important, yet mysterious,
> > Catalog Entity Resolver.
>
> That's exactly what I was waiting for. David is our expert on catalog
> resolution and related issues. They confuse me now end - becoming
> clearer though.
>
> Thanks Gavin and David.
>
> Ross
It has become clearer to me now too, and makes sense.
I think I misunderstood an earlier hint when I replaced a couple of
Things that should have been left alone.
Gav...
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.385 / Virus Database: 268.3.5/301 - Release Date: 4/04/2006
Re: Working - RE: Glossary Plugin FOR-755 - was RE: [jira] Updated:
(FOR-639) define terminology for the various aspects of Dispatcher
Posted by Ross Gardler <rg...@apache.org>.
David Crossley wrote:
> So now everyone who was listening to this thread should
> know a bit more about the important, yet mysterious,
> Catalog Entity Resolver.
That's exactly what I was waiting for. David is our expert on catalog
resolution and related issues. They confuse me now end - becoming
clearer though.
Thanks Gavin and David.
Ross
Re: Working - RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by David Crossley <cr...@apache.org>.
Gav.... wrote:
> A useful link for Catalogs.
>
> http://www.oasis-open.org/committees/entity/spec.html
Yes. Other references are here:
http://xml.apache.org/commons/components/resolver/
We use this as part of Forrest.
And of course see our own docs
http://forrest.apache.org/docs/dev/validation.html
http://forrest.apache.org/docs/dev/catalog.html
http://cocoon.apache.org/2.1/userdocs/concepts/catalog.html
-David
RE: Working - RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by "Gav...." <br...@brightontown.com.au>.
A useful link for Catalogs.
http://www.oasis-open.org/committees/entity/spec.html
> -----Original Message-----
> From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> Sent: Wednesday, 5 April 2006 5:23 PM
> To: dev@forrest.apache.org
> Subject: RE: Working - RE: Glossary Plugin FOR-755 - was RE: [jira]
> Updated: (FOR-639) define terminology for the various aspects of
> Dispatcher
>
>
>
> > -----Original Message-----
> > From: David Crossley [mailto:crossley@apache.org]
> > Sent: Wednesday, 5 April 2006 11:08 AM
> > To: dev@forrest.apache.org
> > Subject: Re: Working - RE: Glossary Plugin FOR-755 - was RE: [jira]
> > Updated: (FOR-639) define terminology for the various aspects of
> > Dispatcher
> >
> > Thanks for persiting Gavin. I now have your patch installed
> > and getting ready to commit it.
> >
> > See below for explanation of the trouble that
> > you were having.
> >
> > David Crossley wrote:
> > > Gav.... wrote:
> > > >
> > > > > -----Original Message-----
> > > > > From: David Crossley
> > > > > Sent: Tuesday, 4 April 2006 11:57 AM
> > > > > To: dev@forrest.apache.org
> > > > > Subject: Re: Working - RE: Glossary Plugin FOR-755 - was RE:
> [jira]
> > > > > Updated: (FOR-639) define terminology for the various aspects of
> > > > > Dispatcher
> > > > >
> > > > > Gav.... wrote:
> > > > > >
> > > > > > 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;
> > > > >
> > > > > That last part is not correct. It should be
> > > > > <!ENTITY % glossary PUBLIC
> > > > > "-//Apache Forrest//ENTITIES Glossary V1.0//EN"
> > > > > FIXME:...................^^^^^^^^
> > > > > "glossary-v10.mod">
> > > > > %glossary;
> > > >
> > > > Ok, changed that, I thought it had to match the rest.
> > > >
> > > > > Then your catalog.xcat needs to declare that as well.
> > > >
> > > > Hmm, changing the catalog.xcat to say ENTITIES instead of
> > > > DTD does not work for me, this has the effect of the dtd
> > >
> > > No. You have two resources: the glossary-v10.dtd and glossary-v10.mod
> > > They need separate Public Identifiers and separate
> > > entries in the catalog.xcat file.
> >
> > Sorry, i didn't previously pick up that
> > you were missing the second entry.
>
> That's ok, looking at other examples, mostly the .mod info was in the
> .dtd file. As this one needs to reference other .dtd files also I see
> The need for the .mod file. I thought that the .dtd file referencing the
> .mod file itself would have been enough.
>
> >
> > I did that at this end and now it works.
> > However, there was another mistake which was
> > causing it to look in the plugin for the document-v12.dtd
> >
> > See above where you show the original glossary-v10.dtd
> > which used the Public Identifier:
> > -//APACHE//ENTITIES Documentation V1.2//EN
> > That was correct and would have been resolved by
> > Forrest core entity resolver. However, then you must
> > have later changed it to be:
> > -//Apache Forrest//ENTITIES Documentation V1.2//EN
> > and so the resolver couldn't find a match.
> > Fixed now.
>
> Sorry, don't know why I changed that.
>
> >
> > So now everyone who was listening to this thread should
> > know a bit more about the important, yet mysterious,
> > Catalog Entity Resolver.
>
> Absolutely, an eye opener for me and now understand it more.
>
> Gav...
>
> >
> > > > And mod files being looked for in xdocs again. I changed
> > > > It back to DTD and with the above change it is all
> > > > Working again - with another workaround.
> > > >
> > > > Making the suggested changes alone was not enough for me,
> > > > I then had problems with document-v12.dtd and common-charents-
> v10.dtd
> > > > Not being found, I had to copy them into the schema directory.
> > >
> > > This is a side affect of not configuring the
> > > catalog.xcat properly. Due to that it will erroneously
> > > try to find the resources relative to the xml doc.
> >
> > Actually relative to the resource that declared it.
> >
> > -David
> >
> >
> > --
> > No virus found in this incoming message.
> > Checked by AVG Free Edition.
> > Version: 7.1.385 / Virus Database: 268.3.5/301 - Release Date: 4/04/2006
>
>
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.385 / Virus Database: 268.3.5/301 - Release Date: 4/04/2006
RE: Working - RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by "Gav...." <br...@brightontown.com.au>.
> -----Original Message-----
> From: David Crossley [mailto:crossley@apache.org]
> Sent: Wednesday, 5 April 2006 11:08 AM
> To: dev@forrest.apache.org
> Subject: Re: Working - RE: Glossary Plugin FOR-755 - was RE: [jira]
> Updated: (FOR-639) define terminology for the various aspects of
> Dispatcher
>
> Thanks for persiting Gavin. I now have your patch installed
> and getting ready to commit it.
>
> See below for explanation of the trouble that
> you were having.
>
> David Crossley wrote:
> > Gav.... wrote:
> > >
> > > > -----Original Message-----
> > > > From: David Crossley
> > > > Sent: Tuesday, 4 April 2006 11:57 AM
> > > > To: dev@forrest.apache.org
> > > > Subject: Re: Working - RE: Glossary Plugin FOR-755 - was RE: [jira]
> > > > Updated: (FOR-639) define terminology for the various aspects of
> > > > Dispatcher
> > > >
> > > > Gav.... wrote:
> > > > >
> > > > > 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;
> > > >
> > > > That last part is not correct. It should be
> > > > <!ENTITY % glossary PUBLIC
> > > > "-//Apache Forrest//ENTITIES Glossary V1.0//EN"
> > > > FIXME:...................^^^^^^^^
> > > > "glossary-v10.mod">
> > > > %glossary;
> > >
> > > Ok, changed that, I thought it had to match the rest.
> > >
> > > > Then your catalog.xcat needs to declare that as well.
> > >
> > > Hmm, changing the catalog.xcat to say ENTITIES instead of
> > > DTD does not work for me, this has the effect of the dtd
> >
> > No. You have two resources: the glossary-v10.dtd and glossary-v10.mod
> > They need separate Public Identifiers and separate
> > entries in the catalog.xcat file.
>
> Sorry, i didn't previously pick up that
> you were missing the second entry.
That's ok, looking at other examples, mostly the .mod info was in the
.dtd file. As this one needs to reference other .dtd files also I see
The need for the .mod file. I thought that the .dtd file referencing the
.mod file itself would have been enough.
>
> I did that at this end and now it works.
> However, there was another mistake which was
> causing it to look in the plugin for the document-v12.dtd
>
> See above where you show the original glossary-v10.dtd
> which used the Public Identifier:
> -//APACHE//ENTITIES Documentation V1.2//EN
> That was correct and would have been resolved by
> Forrest core entity resolver. However, then you must
> have later changed it to be:
> -//Apache Forrest//ENTITIES Documentation V1.2//EN
> and so the resolver couldn't find a match.
> Fixed now.
Sorry, don't know why I changed that.
>
> So now everyone who was listening to this thread should
> know a bit more about the important, yet mysterious,
> Catalog Entity Resolver.
Absolutely, an eye opener for me and now understand it more.
Gav...
>
> > > And mod files being looked for in xdocs again. I changed
> > > It back to DTD and with the above change it is all
> > > Working again - with another workaround.
> > >
> > > Making the suggested changes alone was not enough for me,
> > > I then had problems with document-v12.dtd and common-charents-v10.dtd
> > > Not being found, I had to copy them into the schema directory.
> >
> > This is a side affect of not configuring the
> > catalog.xcat properly. Due to that it will erroneously
> > try to find the resources relative to the xml doc.
>
> Actually relative to the resource that declared it.
>
> -David
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.385 / Virus Database: 268.3.5/301 - Release Date: 4/04/2006
Re: Working - RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by David Crossley <cr...@apache.org>.
Thanks for persiting Gavin. I now have your patch installed
and getting ready to commit it.
See below for explanation of the trouble that
you were having.
David Crossley wrote:
> Gav.... wrote:
> >
> > > -----Original Message-----
> > > From: David Crossley
> > > Sent: Tuesday, 4 April 2006 11:57 AM
> > > To: dev@forrest.apache.org
> > > Subject: Re: Working - RE: Glossary Plugin FOR-755 - was RE: [jira]
> > > Updated: (FOR-639) define terminology for the various aspects of
> > > Dispatcher
> > >
> > > Gav.... wrote:
> > > >
> > > > 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;
> > >
> > > That last part is not correct. It should be
> > > <!ENTITY % glossary PUBLIC
> > > "-//Apache Forrest//ENTITIES Glossary V1.0//EN"
> > > FIXME:...................^^^^^^^^
> > > "glossary-v10.mod">
> > > %glossary;
> >
> > Ok, changed that, I thought it had to match the rest.
> >
> > > Then your catalog.xcat needs to declare that as well.
> >
> > Hmm, changing the catalog.xcat to say ENTITIES instead of
> > DTD does not work for me, this has the effect of the dtd
>
> No. You have two resources: the glossary-v10.dtd and glossary-v10.mod
> They need separate Public Identifiers and separate
> entries in the catalog.xcat file.
Sorry, i didn't previously pick up that
you were missing the second entry.
I did that at this end and now it works.
However, there was another mistake which was
causing it to look in the plugin for the document-v12.dtd
See above where you show the original glossary-v10.dtd
which used the Public Identifier:
-//APACHE//ENTITIES Documentation V1.2//EN
That was correct and would have been resolved by
Forrest core entity resolver. However, then you must
have later changed it to be:
-//Apache Forrest//ENTITIES Documentation V1.2//EN
and so the resolver couldn't find a match.
Fixed now.
So now everyone who was listening to this thread should
know a bit more about the important, yet mysterious,
Catalog Entity Resolver.
> > And mod files being looked for in xdocs again. I changed
> > It back to DTD and with the above change it is all
> > Working again - with another workaround.
> >
> > Making the suggested changes alone was not enough for me,
> > I then had problems with document-v12.dtd and common-charents-v10.dtd
> > Not being found, I had to copy them into the schema directory.
>
> This is a side affect of not configuring the
> catalog.xcat properly. Due to that it will erroneously
> try to find the resources relative to the xml doc.
Actually relative to the resource that declared it.
-David
Re: Working - RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by David Crossley <cr...@apache.org>.
Gav.... wrote:
>
> > -----Original Message-----
> > From: David Crossley
> > Sent: Tuesday, 4 April 2006 11:57 AM
> > To: dev@forrest.apache.org
> > Subject: Re: Working - RE: Glossary Plugin FOR-755 - was RE: [jira]
> > Updated: (FOR-639) define terminology for the various aspects of
> > Dispatcher
> >
> > Gav.... wrote:
> > >
> > > 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;
> >
> > That last part is not correct. It should be
> > <!ENTITY % glossary PUBLIC
> > "-//Apache Forrest//ENTITIES Glossary V1.0//EN"
> > FIXME:...................^^^^^^^^
> > "glossary-v10.mod">
> > %glossary;
>
> Ok, changed that, I thought it had to match the rest.
>
> > Then your catalog.xcat needs to declare that as well.
>
> Hmm, changing the catalog.xcat to say ENTITIES instead of
> DTD does not work for me, this has the effect of the dtd
No. You have two resources: the glossary-v10.dtd and glossary-v10.mod
They need separate Public Identifiers and separate
entries in the catalog.xcat file.
> And mod files being looked for in xdocs again. I changed
> It back to DTD and with the above change it is all
> Working again - with another workaround.
>
> Making the suggested changes alone was not enough for me,
> I then had problems with document-v12.dtd and common-charents-v10.dtd
> Not being found, I had to copy them into the schema directory.
This is a side affect of not configuring the
catalog.xcat properly. Due to that it will erroneously
try to find the resources relative to the xml doc.
> I guess at the moment this is because I am testing directly in the plugin
> Directory to get it working. If it was to be deployed properly into forrest
> or included into a site build then the other files would be found more
> easily from there respective positions. Just a guess.
No that is incorrect.
> > At the moment you are creating a circular reference
> > to the glossary-v10.dtd
>
> Thanks, I guessed a loop somewhere.
>
> Now all the above is done, I am back again at the stage where the 'ant test'
> fails validation due to <acronym> being declared twice
>
> I have removed the <acronym> code from glossary-v10.mod and the ant test now
> Passes no problems, and the glossary.xml and glossary.html display as
> intended.
>
> Is there anything else anyone wants me to check on before I attach the files
> to the 755 issue?
No, just attach a zip file please.
-David
Re: Working - RE: Glossary Plugin FOR-755 - was RE: [jira] Updated:
(FOR-639) define terminology for the various aspects of Dispatcher
Posted by Ross Gardler <rg...@apache.org>.
Gav.... wrote:
> I've deployed my test site via forrestbot and the sample glossary.html is
> available via http://apache.minitutorials.com/glossary.html
Great work Gavin. Can you attach the code to the issue.
Ross
RE: Working - RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by "Gav...." <br...@brightontown.com.au>.
I've deployed my test site via forrestbot and the sample glossary.html is
available via http://apache.minitutorials.com/glossary.html
Gav...
> -----Original Message-----
> From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> Sent: Tuesday, 4 April 2006 8:01 PM
> To: dev@forrest.apache.org; brightoncomputers@brightontown.com.au
> Subject: RE: Working - RE: Glossary Plugin FOR-755 - was RE: [jira]
> Updated: (FOR-639) define terminology for the various aspects of
> Dispatcher
>
>
> I have now done some further testing.
>
> I tested it on a test seed site using pelt skin - works fine.
> I tested it on a test seed site using dispatcher enabled pelt theme, works
> fine.
> Even the PDF produced is fine.
>
> Gav...
>
>
> > -----Original Message-----
> > From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> > Sent: Tuesday, 4 April 2006 7:34 PM
> > To: dev@forrest.apache.org
> > Subject: RE: Working - RE: Glossary Plugin FOR-755 - was RE: [jira]
> > Updated: (FOR-639) define terminology for the various aspects of
> > Dispatcher
> >
> >
> >
> > > -----Original Message-----
> > > From: David Crossley [mailto:crossley@apache.org]
> > > Sent: Tuesday, 4 April 2006 11:57 AM
> > > To: dev@forrest.apache.org
> > > Subject: Re: Working - RE: Glossary Plugin FOR-755 - was RE: [jira]
> > > Updated: (FOR-639) define terminology for the various aspects of
> > > Dispatcher
> > >
> > > Gav.... wrote:
> > > >
> > > > 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;
> > >
> > > That last part is not correct. It should be
> > > <!ENTITY % glossary PUBLIC
> > > "-//Apache Forrest//ENTITIES Glossary V1.0//EN"
> > > FIXME:...................^^^^^^^^
> > > "glossary-v10.mod">
> > > %glossary;
> >
> > Ok, changed that, I thought it had to match the rest.
> >
> > >
> > > Then your catalog.xcat needs to declare that as well.
> >
> > Hmm, changing the catalog.xcat to say ENTITIES instead of
> > DTD does not work for me, this has the effect of the dtd
> > And mod files being looked for in xdocs again. I changed
> > It back to DTD and with the above change it is all
> > Working again - with another workaround.
> >
> > Making the suggested changes alone was not enough for me,
> > I then had problems with document-v12.dtd and common-charents-v10.dtd
> > Not being found, I had to copy them into the schema directory.
> >
> > I guess at the moment this is because I am testing directly in the
> plugin
> > Directory to get it working. If it was to be deployed properly into
> > forrest
> > or included into a site build then the other files would be found more
> > easily from there respective positions. Just a guess.
> >
> > > At the moment you are creating a circular reference
> > > to the glossary-v10.dtd
> >
> > Thanks, I guessed a loop somewhere.
> >
> > Now all the above is done, I am back again at the stage where the 'ant
> > test'
> > fails validation due to <acronym> being declared twice
> >
> > I have removed the <acronym> code from glossary-v10.mod and the ant test
> > now
> > Passes no problems, and the glossary.xml and glossary.html display as
> > intended.
> >
> > Is there anything else anyone wants me to check on before I attach the
> > files
> > to the 755 issue?
> >
> > Gav...
> >
> >
> >
> > >
> > > -David
> > >
> > >
> > > --
> > > No virus found in this incoming message.
> > > Checked by AVG Free Edition.
> > > Version: 7.1.385 / Virus Database: 268.3.5/300 - Release Date:
> 3/04/2006
> >
> >
> >
> >
> > --
> > No virus found in this incoming message.
> > Checked by AVG Free Edition.
> > Version: 7.1.385 / Virus Database: 268.3.5/300 - Release Date: 3/04/2006
>
>
>
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.385 / Virus Database: 268.3.5/300 - Release Date: 3/04/2006
RE: Working - RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by "Gav...." <br...@brightontown.com.au>.
I have now done some further testing.
I tested it on a test seed site using pelt skin - works fine.
I tested it on a test seed site using dispatcher enabled pelt theme, works
fine.
Even the PDF produced is fine.
Gav...
> -----Original Message-----
> From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> Sent: Tuesday, 4 April 2006 7:34 PM
> To: dev@forrest.apache.org
> Subject: RE: Working - RE: Glossary Plugin FOR-755 - was RE: [jira]
> Updated: (FOR-639) define terminology for the various aspects of
> Dispatcher
>
>
>
> > -----Original Message-----
> > From: David Crossley [mailto:crossley@apache.org]
> > Sent: Tuesday, 4 April 2006 11:57 AM
> > To: dev@forrest.apache.org
> > Subject: Re: Working - RE: Glossary Plugin FOR-755 - was RE: [jira]
> > Updated: (FOR-639) define terminology for the various aspects of
> > Dispatcher
> >
> > Gav.... wrote:
> > >
> > > 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;
> >
> > That last part is not correct. It should be
> > <!ENTITY % glossary PUBLIC
> > "-//Apache Forrest//ENTITIES Glossary V1.0//EN"
> > FIXME:...................^^^^^^^^
> > "glossary-v10.mod">
> > %glossary;
>
> Ok, changed that, I thought it had to match the rest.
>
> >
> > Then your catalog.xcat needs to declare that as well.
>
> Hmm, changing the catalog.xcat to say ENTITIES instead of
> DTD does not work for me, this has the effect of the dtd
> And mod files being looked for in xdocs again. I changed
> It back to DTD and with the above change it is all
> Working again - with another workaround.
>
> Making the suggested changes alone was not enough for me,
> I then had problems with document-v12.dtd and common-charents-v10.dtd
> Not being found, I had to copy them into the schema directory.
>
> I guess at the moment this is because I am testing directly in the plugin
> Directory to get it working. If it was to be deployed properly into
> forrest
> or included into a site build then the other files would be found more
> easily from there respective positions. Just a guess.
>
> > At the moment you are creating a circular reference
> > to the glossary-v10.dtd
>
> Thanks, I guessed a loop somewhere.
>
> Now all the above is done, I am back again at the stage where the 'ant
> test'
> fails validation due to <acronym> being declared twice
>
> I have removed the <acronym> code from glossary-v10.mod and the ant test
> now
> Passes no problems, and the glossary.xml and glossary.html display as
> intended.
>
> Is there anything else anyone wants me to check on before I attach the
> files
> to the 755 issue?
>
> Gav...
>
>
>
> >
> > -David
> >
> >
> > --
> > No virus found in this incoming message.
> > Checked by AVG Free Edition.
> > Version: 7.1.385 / Virus Database: 268.3.5/300 - Release Date: 3/04/2006
>
>
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.385 / Virus Database: 268.3.5/300 - Release Date: 3/04/2006
RE: Working - RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by "Gav...." <br...@brightontown.com.au>.
> -----Original Message-----
> From: David Crossley [mailto:crossley@apache.org]
> Sent: Tuesday, 4 April 2006 11:57 AM
> To: dev@forrest.apache.org
> Subject: Re: Working - RE: Glossary Plugin FOR-755 - was RE: [jira]
> Updated: (FOR-639) define terminology for the various aspects of
> Dispatcher
>
> Gav.... wrote:
> >
> > 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;
>
> That last part is not correct. It should be
> <!ENTITY % glossary PUBLIC
> "-//Apache Forrest//ENTITIES Glossary V1.0//EN"
> FIXME:...................^^^^^^^^
> "glossary-v10.mod">
> %glossary;
Ok, changed that, I thought it had to match the rest.
>
> Then your catalog.xcat needs to declare that as well.
Hmm, changing the catalog.xcat to say ENTITIES instead of
DTD does not work for me, this has the effect of the dtd
And mod files being looked for in xdocs again. I changed
It back to DTD and with the above change it is all
Working again - with another workaround.
Making the suggested changes alone was not enough for me,
I then had problems with document-v12.dtd and common-charents-v10.dtd
Not being found, I had to copy them into the schema directory.
I guess at the moment this is because I am testing directly in the plugin
Directory to get it working. If it was to be deployed properly into forrest
or included into a site build then the other files would be found more
easily from there respective positions. Just a guess.
> At the moment you are creating a circular reference
> to the glossary-v10.dtd
Thanks, I guessed a loop somewhere.
Now all the above is done, I am back again at the stage where the 'ant test'
fails validation due to <acronym> being declared twice
I have removed the <acronym> code from glossary-v10.mod and the ant test now
Passes no problems, and the glossary.xml and glossary.html display as
intended.
Is there anything else anyone wants me to check on before I attach the files
to the 755 issue?
Gav...
>
> -David
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.385 / Virus Database: 268.3.5/300 - Release Date: 3/04/2006
Re: Working - RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by David Crossley <cr...@apache.org>.
Gav.... wrote:
>
> 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;
That last part is not correct. It should be
<!ENTITY % glossary PUBLIC
"-//Apache Forrest//ENTITIES Glossary V1.0//EN"
FIXME:...................^^^^^^^^
"glossary-v10.mod">
%glossary;
Then your catalog.xcat needs to declare that as well.
At the moment you are creating a circular reference
to the glossary-v10.dtd
-David
RE: Working - RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by "Gav...." <br...@brightontown.com.au>.
> -----Original Message-----
> From: Ross Gardler [mailto:rgardler@apache.org]
> Sent: Tuesday, 4 April 2006 2:11 AM
> To: dev@forrest.apache.org
> 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:rgardler@apache.org]
> >>Sent: Monday, 3 April 2006 8:00 PM
> >>To: dev@forrest.apache.org
> >>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
Re: Working - RE: Glossary Plugin FOR-755 - was RE: [jira] Updated:
(FOR-639) define terminology for the various aspects of Dispatcher
Posted by Ross Gardler <rg...@apache.org>.
Gav.... wrote:
>
>>-----Original Message-----
>>From: Ross Gardler [mailto:rgardler@apache.org]
>>Sent: Monday, 3 April 2006 8:00 PM
>>To: dev@forrest.apache.org
>>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.
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 aren’t 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
Working - RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by "Gav...." <br...@brightontown.com.au>.
> -----Original Message-----
> From: Ross Gardler [mailto:rgardler@apache.org]
> Sent: Monday, 3 April 2006 8:00 PM
> To: dev@forrest.apache.org
> 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. I also had to ant local-deploy the projectInfo
plugin each time.
>
> One other thought, you have actually added the plugin name to
> forrest.properties haven't you?
Er, yep, was already there when doing an ant seedPlugin.
>
> > BTW I have not completely followed this thread because I do not have
> > much time for forrest ATM so you may have already stated whether you use
> > skins or the dispatcher?
>
> We've not got that far yet. Still trying to get the glossary file
> converted to XDoc.
>
> Ross
Well, I have had some success now :)
I have the plugin working now and the sample glossary.html file works just
fine. :)
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.
2. To get rid of another resource not found error message, I had to put
copyover.xsl into the /resources/stylesheets/ directory.
I would be happier if workaround 1. was solved, in fact I think it must
before it is accepted.
Workaround 2. may be a necessity I don't know.
If anyone has ideas as to why the above is happening I'm all ears.
Should I maybe send in a patch for what I have so you guys arent working
blind?
Gav...
Re: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
define terminology for the various aspects of Dispatcher
Posted by Ross Gardler <rg...@apache.org>.
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)
One other thought, you have actually added the plugin name to
forrest.properties haven't you?
> BTW I have not completely followed this thread because I do not have
> much time for forrest ATM so you may have already stated whether you use
> skins or the dispatcher?
We've not got that far yet. Still trying to get the glossary file
converted to XDoc.
Ross
RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
define terminology for the various aspects of Dispatcher
Posted by Thorsten Scherler <th...@wyona.com>.
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).
BTW I have not completely followed this thread because I do not have
much time for forrest ATM so you may have already stated whether you use
skins or the dispatcher?
salu2
--
Thorsten Scherler
COO Spain
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
thorsten.scherler@wyona.com thorsten@apache.org
RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by "Gav...." <br...@brightontown.com.au>.
Hi David,
> -----Original Message-----
> From: David Crossley [mailto:crossley@apache.org]
> Sent: Monday, 3 April 2006 4:23 PM
> To: dev@forrest.apache.org
> Subject: Re: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
> define terminology for the various aspects of Dispatcher
>
> Gav.... wrote:
> >
> > Ok, I was just posting what I thought to be relevant parts of
> input.xmap,
> > heres the whole caboodle :-
> >
> > ------
> > <?xml version="1.0"?>
> >
> > <map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0">
> > <map:components>
> > <map:generators default="file"/>
> > <map:serializers default="html"/>
> > <map:transformers default="xslt"/>
> > <map:readers default="resource"/>
> > <map:matchers default="wildcard"/>
>
> Those defaults can be removed.
Done.
>
> > <map:actions>
> > <map:action logger="sitemap.action.sourcetype" name="sourcetype"
> > src="org.apache.forrest.sourcetype.SourceTypeAction">
> > <sourcetype name="glossary-v10">
> > <document-declaration public-id="-//Apache Forrest//DTD Glossary
> > V1.0//EN" />
> > </sourcetype>
> > </map:action>
> > </map:actions>
>
> That seems correct.
>
> > <map:selectors default="parameter"><!-- was "browser" -->
> > <map:selector logger="sitemap.selector.parameter" name="parameter"
> > src="org.apache.cocoon.selection.ParameterSelector" />
> > </map:selectors>
> > </map:components>
> >
> > <map:resources>
> > <map:resource name="transform-to-document">
> > <map:act type="sourcetype" src="{src}">
> > <map:select type="parameter">
> > <map:parameter name="parameter-selector-test"
> value="{sourcetype}"
> > />
> > <map:when test="glossary-v10">
> > <map:generate type="file" src="{lm:project.{../../1}.xml}"/>
> > <map:transform
> > src="{lm:glossary.transform.glossary.document}"/>
> > <map:serialize type="xml-document"/>
> > </map:when>
> > <map:otherwise />
>
> Remove that map:otherwise. When the document is not a glossary,
> then Cocoon processing passes through to the next sitemap.
Done.
>
> > </map:select>
> > </map:act>
> > </map:resource>
> > </map:resources>
> >
> > <map:pipelines>
> > <map:pipeline internal="true">
> > <map:match pattern="**.xml">
> > <map:call resource="transform-to-document">
> > <map:parameter name="src" value="{lm:project.{1}.xml}" />
> > </map:call>
> > </map:match>
> >
> > </map:pipeline>
> >
> > </map:pipelines>
> > </map:sitemap>
> > ------
> >
> > There are still some differences to Listlocations input.xmap so will
> look at
> > those, otherwise it looks ok to me.
>
> Yep, other than listed above the input.xmap looks
> fine to me. And those shouldn't cause any issues.
>
> One way to help a bit with testing is to make a
> deliberate error in the input.xmap, e.g. make a spelling
> mistake for the transformer src:
> <map:transform src="{lm:glossary.transform.glossERRORary.document}"/>
> This should give you an error if Cocoon has reached that
> part of the sitemap and if it doesn't then you know that
> something is wrong.
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.
My workaround yesterday of putting the .dtd and .mod files into /xdocs/
directory may be masking a problem causing all this.
Removing those files from there gives me this error message when I try to
goto glossary.html or glossary.xml
\forrest\whiteboard\plugins\org.apache.forrest.plugin.input.glossary\src\doc
umentation\content\xdocs\glossary-v10.dtd (The system cannot find the file
specified)
Why is insisting on looking in xdocs all the time, and why is input.xmap
being ignored altogether. I have no answer at the moment.
Gav...
>
> There are other techniques described at
> http://forrest.apache.org/docs_0_80/howto/howto-dev.html#debug-
> logtransformer
>
> -David
>
>
> --
> 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
Re: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by David Crossley <cr...@apache.org>.
Gav.... wrote:
>
> Ok, I was just posting what I thought to be relevant parts of input.xmap,
> heres the whole caboodle :-
>
> ------
> <?xml version="1.0"?>
>
> <map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0">
> <map:components>
> <map:generators default="file"/>
> <map:serializers default="html"/>
> <map:transformers default="xslt"/>
> <map:readers default="resource"/>
> <map:matchers default="wildcard"/>
Those defaults can be removed.
> <map:actions>
> <map:action logger="sitemap.action.sourcetype" name="sourcetype"
> src="org.apache.forrest.sourcetype.SourceTypeAction">
> <sourcetype name="glossary-v10">
> <document-declaration public-id="-//Apache Forrest//DTD Glossary
> V1.0//EN" />
> </sourcetype>
> </map:action>
> </map:actions>
That seems correct.
> <map:selectors default="parameter"><!-- was "browser" -->
> <map:selector logger="sitemap.selector.parameter" name="parameter"
> src="org.apache.cocoon.selection.ParameterSelector" />
> </map:selectors>
> </map:components>
>
> <map:resources>
> <map:resource name="transform-to-document">
> <map:act type="sourcetype" src="{src}">
> <map:select type="parameter">
> <map:parameter name="parameter-selector-test" value="{sourcetype}"
> />
> <map:when test="glossary-v10">
> <map:generate type="file" src="{lm:project.{../../1}.xml}"/>
> <map:transform
> src="{lm:glossary.transform.glossary.document}"/>
> <map:serialize type="xml-document"/>
> </map:when>
> <map:otherwise />
Remove that map:otherwise. When the document is not a glossary,
then Cocoon processing passes through to the next sitemap.
> </map:select>
> </map:act>
> </map:resource>
> </map:resources>
>
> <map:pipelines>
> <map:pipeline internal="true">
> <map:match pattern="**.xml">
> <map:call resource="transform-to-document">
> <map:parameter name="src" value="{lm:project.{1}.xml}" />
> </map:call>
> </map:match>
>
> </map:pipeline>
>
> </map:pipelines>
> </map:sitemap>
> ------
>
> There are still some differences to Listlocations input.xmap so will look at
> those, otherwise it looks ok to me.
Yep, other than listed above the input.xmap looks
fine to me. And those shouldn't cause any issues.
One way to help a bit with testing is to make a
deliberate error in the input.xmap, e.g. make a spelling
mistake for the transformer src:
<map:transform src="{lm:glossary.transform.glossERRORary.document}"/>
This should give you an error if Cocoon has reached that
part of the sitemap and if it doesn't then you know that
something is wrong.
There are other techniques described at
http://forrest.apache.org/docs_0_80/howto/howto-dev.html#debug-logtransformer
-David
Re: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
define terminology for the various aspects of Dispatcher
Posted by Ross Gardler <rg...@apache.org>.
Gav.... wrote:
>
>>-----Original Message-----
>>From: Ross Gardler [mailto:rgardler@apache.org]
...
>>In addition to Davids comments, you must ensure that you have the
>>appropriate locationmap entry in the pluginx locationmap. Again, follow
>>Davids advice and use another plugins locationmap as an example,
>>Listocations is a nice simple plugin to follow.
>
>
> I have been following listlocations plugin as an example ever since it was
> mentioned a couple of days ago. It has been helpful, and I am certain that
> my setup, apart from the obvious changes rewuired, is the same.
>
> Here is my locationmap.xml
>
Looks good.
Ross
RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by "Gav...." <br...@brightontown.com.au>.
> -----Original Message-----
> From: Ross Gardler [mailto:rgardler@apache.org]
> Sent: Monday, 3 April 2006 4:26 PM
> To: dev@forrest.apache.org
> Subject: Re: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
> define terminology for the various aspects of Dispatcher
>
> Gav.... wrote:
> > David wrote :-
> >
> >
> >>Gav.... wrote:
>
> ..
>
> >>> <map:when test="glossary-v10">
> >>> <map:generate type="file" src="{lm:project.{../../1}.xml}"/>
> >>> <map:transform
> >>
> >>src="{lm:glossary.transform.glossary.document}"/><!-- Not sure about
> this
> >>-->
> >>
> >>That is correct, similar to listLocations/input.xmap
>
> In addition to Davids comments, you must ensure that you have the
> appropriate locationmap entry in the pluginx locationmap. Again, follow
> Davids advice and use another plugins locationmap as an example,
> Listocations is a nice simple plugin to follow.
I have been following listlocations plugin as an example ever since it was
mentioned a couple of days ago. It has been helpful, and I am certain that
my setup, apart from the obvious changes rewuired, is the same.
Here is my locationmap.xml
<locationmap xmlns="http://apache.org/forrest/locationmap/1.0">
<components>
<matchers default="lm">
<matcher
name="lm"
src="org.apache.forrest.locationmap.WildcardLocationMapHintMatcher"/>
</matchers>
<selectors default="exists">
<selector name="exists" logger="sitemap.selector.exists"
src="org.apache.forrest.sourceexists.SourceExistsSelector" />
</selectors>
</components>
<locator>
<match pattern="glossary.transform.*.*">
<location src="resources/stylesheets/{1}-to-{2}.xsl" />
</match>
</locator>
</locationmap>
Gav...
>
> 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
Re: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
define terminology for the various aspects of Dispatcher
Posted by Ross Gardler <rg...@apache.org>.
Gav.... wrote:
> David wrote :-
>
>
>>Gav.... wrote:
..
>>> <map:when test="glossary-v10">
>>> <map:generate type="file" src="{lm:project.{../../1}.xml}"/>
>>> <map:transform
>>
>>src="{lm:glossary.transform.glossary.document}"/><!-- Not sure about this
>>-->
>>
>>That is correct, similar to listLocations/input.xmap
In addition to Davids comments, you must ensure that you have the
appropriate locationmap entry in the pluginx locationmap. Again, follow
Davids advice and use another plugins locationmap as an example,
Listocations is a nice simple plugin to follow.
Ross
RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by "Gav...." <br...@brightontown.com.au>.
David wrote :-
>
> Gav.... wrote:
> > > -----Original Message-----
> > > From: Ross Gardler
> > > Sent: Sunday, 2 April 2006 11:25 PM
> > > To: dev@forrest.apache.org
> > > Subject: Re: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-
> > > ...
> > >
> > > >>1) request the XML source of the document, this should be an XDoc.
> If it
> > > >>is not then it means the plugin is not intercepting and processing
> the
> > > >>request.
> > > >
> > > >
> > > > Just looks like xml to me,
> > > >
> > > > <glossary>
> > > > ???
> > > > <part id="a">
> > > > <title>A</title>
> > >
> > >
> > > That confirms that the glossary plugin is not processing the XML file
> > > with the glossary-to-document.xsl
>
> I find it to be a sign that the input.xmap is
> not correct.
Ok, I was just posting what I thought to be relevant parts of input.xmap,
heres the whole caboodle :-
------
<?xml version="1.0"?>
<map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0">
<map:components>
<map:generators default="file"/>
<map:serializers default="html"/>
<map:transformers default="xslt"/>
<map:readers default="resource"/>
<map:matchers default="wildcard"/>
<map:actions>
<map:action logger="sitemap.action.sourcetype" name="sourcetype"
src="org.apache.forrest.sourcetype.SourceTypeAction">
<sourcetype name="glossary-v10">
<document-declaration public-id="-//Apache Forrest//DTD Glossary
V1.0//EN" />
</sourcetype>
</map:action>
</map:actions>
<map:selectors default="parameter"><!-- was "browser" -->
<map:selector logger="sitemap.selector.parameter" name="parameter"
src="org.apache.cocoon.selection.ParameterSelector" />
</map:selectors>
</map:components>
<map:resources>
<map:resource name="transform-to-document">
<map:act type="sourcetype" src="{src}">
<map:select type="parameter">
<map:parameter name="parameter-selector-test" value="{sourcetype}"
/>
<map:when test="glossary-v10">
<map:generate type="file" src="{lm:project.{../../1}.xml}"/>
<map:transform
src="{lm:glossary.transform.glossary.document}"/>
<map:serialize type="xml-document"/>
</map:when>
<map:otherwise />
</map:select>
</map:act>
</map:resource>
</map:resources>
<map:pipelines>
<map:pipeline internal="true">
<map:match pattern="**.xml">
<map:call resource="transform-to-document">
<map:parameter name="src" value="{lm:project.{1}.xml}" />
</map:call>
</map:match>
</map:pipeline>
</map:pipelines>
</map:sitemap>
------
There are still some differences to Listlocations input.xmap so will look at
those, otherwise it looks ok to me.
>
> Be careful looking at the logs until you understand
> more about how the sitemap works.
I wasn't really looking at them, just forwarding as per Ross' request.
> ...
> Your input.xmap is missing the SourceTypeAction or perhaps
> you just forgot to show us that bit. As suggested elsewhere,
> your input.xmap should be very similar to listLocations/input.xmap
> In fact you could throw away the glossary.xmap that Ross donated
> and copy listLocations/input.xmap and change the obvious things.
>
> There should be nothing more than what you have below
> and the <map:components><map:actions> sections.
Ok, will take a look.
Gav...
>
> > I have :-
> >
> > <map:selectors default="parameter"><!-- was "browser" -->
> > <map:selector logger="sitemap.selector.parameter" name="parameter"
> src="org.apache.cocoon.selection.ParameterSelector" />
> > </map:selectors>
> > </map:components>
> >
> > <map:resources>
> > <map:resource name="transform-to-document">
> > <map:act type="sourcetype" src="{src}">
> > <map:select type="parameter">
> > <map:parameter name="parameter-selector-test"
> value="{sourcetype}" />
> > <map:when test="glossary-v10">
> > <map:generate type="file" src="{lm:project.{../../1}.xml}"/>
> > <map:transform
> src="{lm:glossary.transform.glossary.document}"/><!-- Not sure about this
> -->
>
> That is correct, similar to listLocations/input.xmap
>
> > <map:serialize type="xml-document"/>
> > <!-- was <map:transform src="{project:skins-
> dir}{forrest:skin}/xslt/xdoc/glossary-to-document.xsl"/>-->
> > </map:when>
> > <map:otherwise />
> > </map:select>
> > </map:act>
> > </map:resource>
> > </map:resources>
> >
> > ...
> >
> > <map:pipelines>
> > <map:pipeline internal="true">
> > <map:match pattern="**.xml">
> > <map:call resource="transform-to-document">
> > <map:parameter name="src" value="{lm:project.{1}.xml}" />
> > </map:call>
> > </map:match>
> >
> > </map:pipeline>
> >
> > </map:pipelines>
>
> All of the above looks correct.
>
> > > Also tell us where you have put the glossary-to-document.xsl file.
> >
> > In /resources/stylesheets/
>
> Correct.
>
> > Also, in the locationmap.xml I have added in :-
> >
> > <locator>
> > <match pattern="glossary.transform.*.*">
> > <location src="resources/stylesheets/{1}-to-{2}.xsl" />
> > </match>
> > </locator>
> >
> > Also, while I am checking things, the top of glossary.xml looks like :-
> >
> > <?xml version="1.0" encoding="UTF-8"?>
> > <!DOCTYPE glossary PUBLIC "-//Apache Forrest//DTD Glossary V1.0//EN"
> > "glossary-v10.dtd">
> > <!-- possibly "document" -->
> > <glossary>
> > <part id="a">
> > <title>A</title
> >
> > I wasn???t sure if it was DOCTYPE glossary or DOCTYPE document, I have
> tried both at some stage.
>
> What you have is correct, as long as that Public Identifier
> matches the sourcetype/action defined in your input.xmap
>
> -David
>
>
> --
> 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
Re: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by David Crossley <cr...@apache.org>.
Gav.... wrote:
> > -----Original Message-----
> > From: Ross Gardler
> > Sent: Sunday, 2 April 2006 11:25 PM
> > To: dev@forrest.apache.org
> > Subject: Re: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
> > define terminology for the various aspects of Dispatcher
> >
> > Gav.... wrote:
> > > Ross Wrote:-
> > >
> > >>Gav.... wrote:
> > >>
> >
> > ...
> >
> > >>
> > >>>A 'Forrest Run' also works fine and the site displays great, all pages
> > >>
> > >>work
> > >>
> > >>>fine Except the 'glossary.xml' test file which although displays,
> > >>
> > >>produces
> > >>
> > >>>no content, just the menus and tabs etc..
> >
> > ...
> >
> > >>1) request the XML source of the document, this should be an XDoc. If it
> > >>is not then it means the plugin is not intercepting and processing the
> > >>request.
> > >
> > >
> > > Just looks like xml to me,
> > >
> > > <glossary>
> > > ???
> > > <part id="a">
> > > <title>A</title>
> >
> >
> > That confirms that the glossary plugin is not processing the XML file
> > with the glossary-to-document.xsl
I find it to be a sign that the input.xmap is
not correct.
> > >>2) do "forrest run" then look in PLUGIN_HOME/build/webapp/logs/ to see
> > >>if there are any errors, in particular check that the
> > >>glossary-to-document.xsl is being found, and if not, why not
> > >
> > > Amongst other things there is in the Locationmap.log :-
Be careful looking at the logs until you understand
more about how the sitemap works.
> > > ERROR [core.modules.mapper.lm] (/glossary.xml): Ignoring locationmap
> > config exception: Unable to build LocationMap.
> > >
> > > Caused by: org.apache.cocoon.ResourceNotFoundException: Resource not
> > found.
> > > at <map:serialize type="xml"> -
> > file:/D:/Apache2/forrest/main/webapp/sitemap.xmap:398:37
> > >
> > > Caused by: java.io.FileNotFoundException:
> > D:\Apache2\forrest\whiteboard\plugins\org.apache.forrest.plugin.input.glos
> > sary\src\documentation\content\locationmap.xml (The system cannot find the
> > file specified)
> >
> > Not a problem. This should really be reported as a warning not an error.
> > There is an issue for this.
> >
> > Not sure what the problem is, can you post the part of your input.xmap
> > that you believe should be processing the glossary.xml to produce the
> > xdoc from it.
Your input.xmap is missing the SourceTypeAction or perhaps
you just forgot to show us that bit. As suggested elsewhere,
your input.xmap should be very similar to listLocations/input.xmap
In fact you could throw away the glossary.xmap that Ross donated
and copy listLocations/input.xmap and change the obvious things.
There should be nothing more than what you have below
and the <map:components><map:actions> sections.
> I have :-
>
> <map:selectors default="parameter"><!-- was "browser" -->
> <map:selector logger="sitemap.selector.parameter" name="parameter" src="org.apache.cocoon.selection.ParameterSelector" />
> </map:selectors>
> </map:components>
>
> <map:resources>
> <map:resource name="transform-to-document">
> <map:act type="sourcetype" src="{src}">
> <map:select type="parameter">
> <map:parameter name="parameter-selector-test" value="{sourcetype}" />
> <map:when test="glossary-v10">
> <map:generate type="file" src="{lm:project.{../../1}.xml}"/>
> <map:transform src="{lm:glossary.transform.glossary.document}"/><!-- Not sure about this -->
That is correct, similar to listLocations/input.xmap
> <map:serialize type="xml-document"/>
> <!-- was <map:transform src="{project:skins-dir}{forrest:skin}/xslt/xdoc/glossary-to-document.xsl"/>-->
> </map:when>
> <map:otherwise />
> </map:select>
> </map:act>
> </map:resource>
> </map:resources>
>
> ...
>
> <map:pipelines>
> <map:pipeline internal="true">
> <map:match pattern="**.xml">
> <map:call resource="transform-to-document">
> <map:parameter name="src" value="{lm:project.{1}.xml}" />
> </map:call>
> </map:match>
>
> </map:pipeline>
>
> </map:pipelines>
All of the above looks correct.
> > Also tell us where you have put the glossary-to-document.xsl file.
>
> In /resources/stylesheets/
Correct.
> Also, in the locationmap.xml I have added in :-
>
> <locator>
> <match pattern="glossary.transform.*.*">
> <location src="resources/stylesheets/{1}-to-{2}.xsl" />
> </match>
> </locator>
>
> Also, while I am checking things, the top of glossary.xml looks like :-
>
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE glossary PUBLIC "-//Apache Forrest//DTD Glossary V1.0//EN"
> "glossary-v10.dtd">
> <!-- possibly "document" -->
> <glossary>
> <part id="a">
> <title>A</title
>
> I wasn???t sure if it was DOCTYPE glossary or DOCTYPE document, I have tried both at some stage.
What you have is correct, as long as that Public Identifier
matches the sourcetype/action defined in your input.xmap
-David
RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by "Gav...." <br...@brightontown.com.au>.
> -----Original Message-----
> From: Ross Gardler [mailto:rgardler@apache.org]
> Sent: Sunday, 2 April 2006 11:25 PM
> To: dev@forrest.apache.org
> Subject: Re: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
> define terminology for the various aspects of Dispatcher
>
> Gav.... wrote:
> > Ross Wrote:-
> >
> >>Gav.... wrote:
> >>
>
> ...
>
> >>
> >>>A 'Forrest Run' also works fine and the site displays great, all pages
> >>
> >>work
> >>
> >>>fine Except the 'glossary.xml' test file which although displays,
> >>
> >>produces
> >>
> >>>no content, just the menus and tabs etc..
>
> ...
>
> >>1) request the XML source of the document, this should be an XDoc. If it
> >>is not then it means the plugin is not intercepting and processing the
> >>request.
> >
> >
> > Just looks like xml to me,
> >
> > <glossary>
> > −
> > <part id="a">
> > <title>A</title>
>
>
> That confirms that the glossary plugin is not processing the XML file
> with the glossary-to-document.xsl
>
> ...
>
> >>2) do "forrest run" then look in PLUGIN_HOME/build/webapp/logs/ to see
> >>if there are any errors, in particular check that the
> >>glossary-to-document.xsl is being found, and if not, why not
> >
> >
> > Amongst other things there is in the Locationmap.log :-
> >
> > ERROR [core.modules.mapper.lm] (/glossary.xml): Ignoring locationmap
> config exception: Unable to build LocationMap.
> >
> > Caused by: org.apache.cocoon.ResourceNotFoundException: Resource not
> found.
> > at <map:serialize type="xml"> -
> file:/D:/Apache2/forrest/main/webapp/sitemap.xmap:398:37
> >
> > Caused by: java.io.FileNotFoundException:
> D:\Apache2\forrest\whiteboard\plugins\org.apache.forrest.plugin.input.glos
> sary\src\documentation\content\locationmap.xml (The system cannot find the
> file specified)
>
> Not a problem. This should really be reported as a warning not an error.
> There is an issue for this.
>
> Not sure what the problem is, can you post the part of your input.xmap
> that you believe should be processing the glossary.xml to produce the
> xdoc from it.
I have :-
<map:selectors default="parameter"><!-- was "browser" -->
<map:selector logger="sitemap.selector.parameter" name="parameter" src="org.apache.cocoon.selection.ParameterSelector" />
</map:selectors>
</map:components>
<map:resources>
<map:resource name="transform-to-document">
<map:act type="sourcetype" src="{src}">
<map:select type="parameter">
<map:parameter name="parameter-selector-test" value="{sourcetype}" />
<map:when test="glossary-v10">
<map:generate type="file" src="{lm:project.{../../1}.xml}"/>
<map:transform src="{lm:glossary.transform.glossary.document}"/><!-- Not sure about this -->
<map:serialize type="xml-document"/>
<!-- was <map:transform src="{project:skins-dir}{forrest:skin}/xslt/xdoc/glossary-to-document.xsl"/>-->
</map:when>
<map:otherwise />
</map:select>
</map:act>
</map:resource>
</map:resources>
...
<map:pipelines>
<map:pipeline internal="true">
<map:match pattern="**.xml">
<map:call resource="transform-to-document">
<map:parameter name="src" value="{lm:project.{1}.xml}" />
</map:call>
</map:match>
</map:pipeline>
</map:pipelines>
>
> Also tell us where you have put the glossary-to-document.xsl file.
>
> Ross
In /resources/stylesheets/
Also, in the locationmap.xml I have added in :-
<locator>
<match pattern="glossary.transform.*.*">
<location src="resources/stylesheets/{1}-to-{2}.xsl" />
</match>
</locator>
Also, while I am checking things, the top of glossary.xml looks like :-
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glossary PUBLIC "-//Apache Forrest//DTD Glossary V1.0//EN"
"glossary-v10.dtd">
<!-- possibly "document" -->
<glossary>
<part id="a">
<title>A</title
I wasn’t sure if it was DOCTYPE glossary or DOCTYPE document, I have tried both at some stage.
Gav...
Re: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
define terminology for the various aspects of Dispatcher
Posted by Ross Gardler <rg...@apache.org>.
Gav.... wrote:
> Ross Wrote:-
>
>>Gav.... wrote:
>>
...
>>
>>>A 'Forrest Run' also works fine and the site displays great, all pages
>>
>>work
>>
>>>fine Except the 'glossary.xml' test file which although displays,
>>
>>produces
>>
>>>no content, just the menus and tabs etc..
...
>>1) request the XML source of the document, this should be an XDoc. If it
>>is not then it means the plugin is not intercepting and processing the
>>request.
>
>
> Just looks like xml to me,
>
> <glossary>
> −
> <part id="a">
> <title>A</title>
That confirms that the glossary plugin is not processing the XML file
with the glossary-to-document.xsl
...
>>2) do "forrest run" then look in PLUGIN_HOME/build/webapp/logs/ to see
>>if there are any errors, in particular check that the
>>glossary-to-document.xsl is being found, and if not, why not
>
>
> Amongst other things there is in the Locationmap.log :-
>
> ERROR [core.modules.mapper.lm] (/glossary.xml): Ignoring locationmap config exception: Unable to build LocationMap.
>
> Caused by: org.apache.cocoon.ResourceNotFoundException: Resource not found.
> at <map:serialize type="xml"> - file:/D:/Apache2/forrest/main/webapp/sitemap.xmap:398:37
>
> Caused by: java.io.FileNotFoundException: D:\Apache2\forrest\whiteboard\plugins\org.apache.forrest.plugin.input.glossary\src\documentation\content\locationmap.xml (The system cannot find the file specified)
Not a problem. This should really be reported as a warning not an error.
There is an issue for this.
Not sure what the problem is, can you post the part of your input.xmap
that you believe should be processing the glossary.xml to produce the
xdoc from it.
Also tell us where you have put the glossary-to-document.xsl file.
Ross
RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by "Gav...." <br...@brightontown.com.au>.
Ross Wrote:-
> Gav.... wrote:
> >
> >>-----Original Message-----
> >>From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> >>Sent: Sunday, 2 April 2006 5:22 PM
> >>To: dev@forrest.apache.org
> >>Subject: RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
> >>define terminology for the various aspects of Dispatcher
> >>
> >>Should I be using the .forrest. rather than .cocoon. sourcetype then?
> >>(I did change this earlier to no effect, but guess other configs were
> >>Wrong also)
> >
> >
> > Answer : Yes, to that one!
> >
> > Ok, I now have the plugin built and an 'ant test' is successful.
> (woohoo!)
> > A 'Forrest Run' also works fine and the site displays great, all pages
> work
> > fine Except the 'glossary.xml' test file which although displays,
> produces
> > no content, just the menus and tabs etc..
>
> Cool!
>
> > So a little bit more work to do, but getting there.
>
> Here's some "starter" debugging tips (we really ought to document these):
>
> 1) request the XML source of the document, this should be an XDoc. If it
> is not then it means the plugin is not intercepting and processing the
> request.
Just looks like xml to me,
<glossary>
−
<part id="a">
<title>A</title>
−
<item id="ASampleGlossaryEntry">
<term>A Sample Glossary Entry</term>
−
<definition>
This is just an example, check the source for tags to be used.
</definition>
</item>
</part>
−
<part id="b">
<title>B</title>
−
<item>
<term/>
<definition/>
</item>
</part>
−
<part id="c">
<title>C</title>
−
<item>
<term/>
<definition/>
</item>
</part>
−
<part id="xyz">
<title>XYZ</title>
−
<item>
<term/>
<definition/>
</item>
</part>
</glossary>
>
> 2) do "forrest run" then look in PLUGIN_HOME/build/webapp/logs/ to see
> if there are any errors, in particular check that the
> glossary-to-document.xsl is being found, and if not, why not
Amongst other things there is in the Locationmap.log :-
ERROR [core.modules.mapper.lm] (/glossary.xml): Ignoring locationmap config exception: Unable to build LocationMap.
Caused by: org.apache.cocoon.ResourceNotFoundException: Resource not found.
at <map:serialize type="xml"> - file:/D:/Apache2/forrest/main/webapp/sitemap.xmap:398:37
Caused by: java.io.FileNotFoundException: D:\Apache2\forrest\whiteboard\plugins\org.apache.forrest.plugin.input.glossary\src\documentation\content\locationmap.xml (The system cannot find the file specified)
WARN [core.modules.mapper.lm] (/glossary.html): Locationmap did not return a location for hint project-skinconf.xsl
And in the error.log :-
ERROR (2006-04-02) 21:35.46:880 [core.modules.mapper.lm] (/glossary.xml) PoolThread-4/SelectNode: Ignoring locationmap config exception: Unable to build LocationMap
Caused by: java.io.FileNotFoundException: D:\Apache2\forrest\whiteboard\plugins\org.apache.forrest.plugin.input.glossary\src\documentation\content\locationmap.xml (The system cannot find the file specified)
>
> Then see what extra information the above might lead you to and post
> again.
>
> Ross
Thanks for looking, I will take another look later.
Gav...
>
>
> --
> 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
Re: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
define terminology for the various aspects of Dispatcher
Posted by Ross Gardler <rg...@apache.org>.
Gav.... wrote:
>
>>-----Original Message-----
>>From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
>>Sent: Sunday, 2 April 2006 5:22 PM
>>To: dev@forrest.apache.org
>>Subject: RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
>>define terminology for the various aspects of Dispatcher
>>
>>Should I be using the .forrest. rather than .cocoon. sourcetype then?
>>(I did change this earlier to no effect, but guess other configs were
>>Wrong also)
>
>
> Answer : Yes, to that one!
>
> Ok, I now have the plugin built and an 'ant test' is successful. (woohoo!)
> A 'Forrest Run' also works fine and the site displays great, all pages work
> fine Except the 'glossary.xml' test file which although displays, produces
> no content, just the menus and tabs etc..
Cool!
> So a little bit more work to do, but getting there.
Here's some "starter" debugging tips (we really ought to document these):
1) request the XML source of the document, this should be an XDoc. If it
is not then it means the plugin is not intercepting and processing the
request.
2) do "forrest run" then look in PLUGIN_HOME/build/webapp/logs/ to see
if there are any errors, in particular check that the
glossary-to-document.xsl is being found, and if not, why not
Then see what extra information the above might lead you to and post again.
Ross
RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by "Gav...." <br...@brightontown.com.au>.
> -----Original Message-----
> From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> Sent: Sunday, 2 April 2006 5:22 PM
> To: dev@forrest.apache.org
> Subject: RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
> define terminology for the various aspects of Dispatcher
>
> Should I be using the .forrest. rather than .cocoon. sourcetype then?
> (I did change this earlier to no effect, but guess other configs were
> Wrong also)
Answer : Yes, to that one!
Ok, I now have the plugin built and an 'ant test' is successful. (woohoo!)
A 'Forrest Run' also works fine and the site displays great, all pages work
fine Except the 'glossary.xml' test file which although displays, produces
no content, just the menus and tabs etc..
So a little bit more work to do, but getting there.
Thanks David for the pointers.
Gav...
>
> Gav...
>
> > -----Original Message-----
> > From: David Crossley [mailto:crossley@apache.org]
> > Sent: Sunday, 2 April 2006 4:15 PM
> > To: dev@forrest.apache.org; brightoncomputers@brightontown.com.au
> > Subject: Re: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
> > define terminology for the various aspects of Dispatcher
> >
> > David Crossley wrote:
> > > Gav.... wrote:
> > > >
> > > > 1. Does glossary.xmap get renamed to and therefore replace
> output.xmap
> > ?
> > >
> > > As you discovered, it is an input plugin so
> > > glossary.xmap becomes input.xmap
> > > I have not looked at glossary.xmap. Perhaps it
> > > needs some stuff removed. Look at another plugin
> > > for guidance.
> >
> > I looked. There is lots that needs to be removed.
> > Remember that Ross said in FOR-755 that his example
> > glossary.xmap is prior to plugins.
> >
> > Your input.xmap will need to look very much like
> > the listLocations plugin input.xmap except that
> > you don't need the extra <map:match> which is only
> > there for backwards-compatibility with the initial
> > basic version of that plugin.
> >
> > Do 'svn up' as i just tidied up that plugin.
> >
> > -David
> >
> >
> > --
> > 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
>
>
>
>
> --
> 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
RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by "Gav...." <br...@brightontown.com.au>.
Should I be using the .forrest. rather than .cocoon. sourcetype then?
(I did change this earlier to no effect, but guess other configs were
Wrong also)
Gav...
> -----Original Message-----
> From: David Crossley [mailto:crossley@apache.org]
> Sent: Sunday, 2 April 2006 4:15 PM
> To: dev@forrest.apache.org; brightoncomputers@brightontown.com.au
> Subject: Re: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
> define terminology for the various aspects of Dispatcher
>
> David Crossley wrote:
> > Gav.... wrote:
> > >
> > > 1. Does glossary.xmap get renamed to and therefore replace output.xmap
> ?
> >
> > As you discovered, it is an input plugin so
> > glossary.xmap becomes input.xmap
> > I have not looked at glossary.xmap. Perhaps it
> > needs some stuff removed. Look at another plugin
> > for guidance.
>
> I looked. There is lots that needs to be removed.
> Remember that Ross said in FOR-755 that his example
> glossary.xmap is prior to plugins.
>
> Your input.xmap will need to look very much like
> the listLocations plugin input.xmap except that
> you don't need the extra <map:match> which is only
> there for backwards-compatibility with the initial
> basic version of that plugin.
>
> Do 'svn up' as i just tidied up that plugin.
>
> -David
>
>
> --
> 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
RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by "Gav...." <br...@brightontown.com.au>.
> -----Original Message-----
> From: David Crossley [mailto:crossley@apache.org]
> Sent: Sunday, 2 April 2006 4:15 PM
> To: dev@forrest.apache.org; brightoncomputers@brightontown.com.au
> Subject: Re: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
> define terminology for the various aspects of Dispatcher
>
> David Crossley wrote:
> > Gav.... wrote:
> > >
> > > 1. Does glossary.xmap get renamed to and therefore replace output.xmap
> ?
> >
> > As you discovered, it is an input plugin so
> > glossary.xmap becomes input.xmap
> > I have not looked at glossary.xmap. Perhaps it
> > needs some stuff removed. Look at another plugin
> > for guidance.
>
> I looked. There is lots that needs to be removed.
> Remember that Ross said in FOR-755 that his example
> glossary.xmap is prior to plugins.
>
> Your input.xmap will need to look very much like
> the listLocations plugin input.xmap except that
> you don't need the extra <map:match> which is only
> there for backwards-compatibility with the initial
> basic version of that plugin.
>
> Do 'svn up' as i just tidied up that plugin.
Thanks David, will do that shortly.
Gav...
>
> -David
>
>
> --
> 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
RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by "Gav...." <br...@brightontown.com.au>.
> -----Original Message-----
> From: David Crossley [mailto:crossley@apache.org]
> Sent: Sunday, 2 April 2006 4:15 PM
> To: dev@forrest.apache.org; brightoncomputers@brightontown.com.au
> Subject: Re: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
> define terminology for the various aspects of Dispatcher
>
> David Crossley wrote:
> > Gav.... wrote:
> > >
> > > 1. Does glossary.xmap get renamed to and therefore replace output.xmap
> ?
> >
> > As you discovered, it is an input plugin so
> > glossary.xmap becomes input.xmap
> > I have not looked at glossary.xmap. Perhaps it
> > needs some stuff removed. Look at another plugin
> > for guidance.
>
> I looked. There is lots that needs to be removed.
> Remember that Ross said in FOR-755 that his example
> glossary.xmap is prior to plugins.
>
> Your input.xmap will need to look very much like
> the listLocations plugin input.xmap except that
> you don't need the extra <map:match> which is only
> there for backwards-compatibility with the initial
> basic version of that plugin.
>
> Do 'svn up' as i just tidied up that plugin.
I just noticed, a normal 'svn up' from main will not update any
Plugins. I cd'd to the listLocations plugin and did it from there
And it worked fine.
What is the method for updating all plugins normally, it could be
Some more of mine may be out of date.
Gav...
>
> -David
>
>
> --
> 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
Re: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by David Crossley <cr...@apache.org>.
David Crossley wrote:
> Gav.... wrote:
> >
> > 1. Does glossary.xmap get renamed to and therefore replace output.xmap ?
>
> As you discovered, it is an input plugin so
> glossary.xmap becomes input.xmap
> I have not looked at glossary.xmap. Perhaps it
> needs some stuff removed. Look at another plugin
> for guidance.
I looked. There is lots that needs to be removed.
Remember that Ross said in FOR-755 that his example
glossary.xmap is prior to plugins.
Your input.xmap will need to look very much like
the listLocations plugin input.xmap except that
you don't need the extra <map:match> which is only
there for backwards-compatibility with the initial
basic version of that plugin.
Do 'svn up' as i just tidied up that plugin.
-David
Re: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by David Crossley <cr...@apache.org>.
Gav.... wrote:
>
> Ok, I have started this, created the basic Glossary output plugin,
> Now need to configure it.
>
> I have questions (never done a plugin before so bear with me) :-
>
> I'm referring to the attachments provided on FOR-755 here -
>
> 1. Does glossary.xmap get renamed to and therefore replace output.xmap ?
As you discovered, it is an input plugin so
glossary.xmap becomes input.xmap
I have not looked at glossary.xmap. Perhaps it
needs some stuff removed. Look at another plugin
for guidance.
> 2.Where do the .dtd and .mod files need to go?
> 3a. I have put glossary2document.xsl in resources/stylesheets, is this
> correct?
> 3b. And will I need to rename it to glossary-to-document.xsl ?
Yes obviously follow the naming convention.
> 3c. If yes to 3b, anything else to change?
Add to the locationmap.xml ... Again use another
plugin for guidance.
> 4. Glossary.xml is placed in the xdocs directory, this is the main file we
> Need to add our Terminology. Looking quickly, its an A-Z arrangement, can we
> and should we have a separate A-Z for Dispatcher Terminology, therefore a
> separate dispatcher-glossary.xml file, or will ALL Forrest terminology
> reside in the same Glossary.xml file?
No this doesn't happen in the plugin
(apart from a simple example). The real data files
go in whatever project that the user creates.
For example the forrest project will use it
in site-author/content/xdocs/**
I expect that is better to allow separate glossary
data files. They can be any filename because the input.xmap
should respond on the Content Aware Pipeline, i.e. the
source-type action responding on the document type declaration
or namespace.
The listLocations plugins uses a horrid workaround
to match on the filename. It needs to be fixed to
use the publicIdentifier in the XML instance document.
> I am doing this in Whiteboard at the moment, is this ok?
I don't know the answer to this. Needs a separate
discussion.
Wherever you do it is fine at the moment.
> I am not creating samples, I could rename Ross's original Glossary.xml to
> something else and use that as a sample ?
Use lowercase filenames.
No, that datafile is Ross' example. I reckon
create a really trivial example data file.
Say four entries, using very obvious terms, e.g.
HTML = HyperText Markup Language
CSS = Cascading Style Sheets
ASF = Apache Software Foundation
... perhaps use one of those with an example
link to another site.
> Anything else?
>
> Lots of 'Q''s in there, sorry.
>
> 1 hour later ...
>
> Ant Test - Build Failed die to could not validate Glossary.xml, I guess
> that's because the .dtd and .mod files are in the wrong place.
As discussed in the Howto Build a Plugin,
make sure to use Forrest's Ant. Also this error
is probably because you don't have the DTD catalog.xcat
configured properly or using the wrong Public Identifier
for the XML file.
-David
> Gav...
>
> >
> > Failing that, i reckon just use an ordinary document
> > with concise definitions that link to examples in
> > the other documents.
>
> I have started this also, in fact started in when your idea of
> Using the Glossary Plugin came through. Hmm, I wonder which I'll
> Finish first :)
>
> > However it gets done is good.
> >
> > -David
>
> On it,
>
> Gav...
Re: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
define terminology for the various aspects of Dispatcher
Posted by Ross Gardler <rg...@apache.org>.
David Crossley wrote:
> Gav.... wrote:
>
>>Right, putting the .dtd and .mod files in xdocs directory and it now
>>validates the glossary.xml file -- the validation fails but its further
>>Than I got before.
>
>
> No that is not the correct place, but it was a workaround
> to get you going.
>
> Look to some other plugins for examples of how to
> handle the DTDs, e.g.
>
> org.apache.forrest.plugin.input.listLocations/resources/schema/
In particular you need to look at the catalog definition files that tell
Forrest where to find the DTD.
Ross
Re: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by David Crossley <cr...@apache.org>.
Gav.... wrote:
> Right, putting the .dtd and .mod files in xdocs directory and it now
> validates the glossary.xml file -- the validation fails but its further
> Than I got before.
No that is not the correct place, but it was a workaround
to get you going.
Look to some other plugins for examples of how to
handle the DTDs, e.g.
org.apache.forrest.plugin.input.listLocations/resources/schema/
-David
Re: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
define terminology for the various aspects of Dispatcher
Posted by Ross Gardler <rg...@apache.org>.
David Crossley wrote:
> Gav.... wrote:
>
>>Back again,
>>
>>
>>>From: Gav....
>>>
>>>A wee bit further now then but I reckon I am stuck at this point,
>>>
>>>I Commented out these
>>>
>>><!ELEMENT acronym (%content.mix;)*>
>>><!ATTLIST acronym %common.att;>
>>>
>>>And it all validates fine, can not test if acronym tags still work yet
>>>because I now get a build error :-
>>>
>>>Cannot find catalogManager.properties
>>>
>>>I have seen this before and generally does not fail a build, but this one
>>>:-
>
>
> It is not an error. You can supply one if you
> want (see FAQ). I often wonder if we should add a
> default file just to shut that warning up.
+1 to a default, this used to fool me too.
>>>X [0] index.html BROKEN:
>>>org.apache.cocoon.acting.sourcetype,SourceTypeAction
>>>
>>>Is a new one on me, it may be something needs updating but I have no clue
>>>at
>>>the moment.
>>>
>>>Ideas?
>>
>>Well I have one of my own and it goes like this:-
>>
>>In input.xmap we have :
>>
>><map:actions>
>> <map:action logger="sitemap.action.sourcetype" name="sourcetype"
>>src="org.apache.cocoon.acting.sourcetype.SourceTypeAction">
>> <sourcetype name="glossary-v10">
>> <document-declaration public-id="-//SAAFE//DTD Glossary V1.0//EN"
>>/>
>> </sourcetype>
>> </map:action>
>> </map:actions>
>>
>>The document-declaration points to I guess saafe.org and on this page [1]
>>A well know RDG :) says
As David said, but I will back up as this is my code donation, please
remove any references you find to SAAFE and turn them to Apache
references as per other DTD's and plugins. This is a complete code
donation and I don't require any credits other than the normal onces. I
certainly don't maintain these DTD's with my SAAFE work.
>><quote>Fixme ( rdg )
>>We should also support the public entity descriptor ("-//SAAFE/DTD Public
>>Document//EN") above.</quote>
>>
>>Not quite the same, anyhow, maybe this document-declaration should be
>>pointing somewhere else.
>
>
> Don't know what that means. Leave it until later.
Errr... well I wrote it and I don't know what it means either ;-)
Just drop the fixme, it may have been some weird requirement on the
project I created this plugin for and eventually talked the client out
of - it was a long time ago, I can't remember the details.
Ross
Re: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by David Crossley <cr...@apache.org>.
Gav.... wrote:
> Back again,
>
> > From: Gav....
> >
> > A wee bit further now then but I reckon I am stuck at this point,
> >
> > I Commented out these
> >
> > <!ELEMENT acronym (%content.mix;)*>
> > <!ATTLIST acronym %common.att;>
> >
> > And it all validates fine, can not test if acronym tags still work yet
> > because I now get a build error :-
> >
> > Cannot find catalogManager.properties
> >
> > I have seen this before and generally does not fail a build, but this one
> > :-
It is not an error. You can supply one if you
want (see FAQ). I often wonder if we should add a
default file just to shut that warning up.
> > X [0] index.html BROKEN:
> > org.apache.cocoon.acting.sourcetype,SourceTypeAction
> >
> > Is a new one on me, it may be something needs updating but I have no clue
> > at
> > the moment.
> >
> > Ideas?
>
> Well I have one of my own and it goes like this:-
>
> In input.xmap we have :
>
> <map:actions>
> <map:action logger="sitemap.action.sourcetype" name="sourcetype"
> src="org.apache.cocoon.acting.sourcetype.SourceTypeAction">
> <sourcetype name="glossary-v10">
> <document-declaration public-id="-//SAAFE//DTD Glossary V1.0//EN"
> />
> </sourcetype>
> </map:action>
> </map:actions>
>
> The document-declaration points to I guess saafe.org and on this page [1]
> A well know RDG :) says
The SourceTypeAction doesn't "point to" anything.
That <document-declaration> is declaring the
Public Identifier to match in the input xml
instances. See:
SourceTypeAction (content aware pipelines)
http://forrest.apache.org/docs/dev/cap.html
We should be using an Apache public identifier.
Follow some of the other Forrest DTDs for example
syntax. I glanced at the Glossary DTDs and they already do.
I reckon that you need to change the document type
declaration in your xml instance to use those Apache IDs.
Ditto in the SourceTypeAction above.
> <quote>Fixme ( rdg )
> We should also support the public entity descriptor ("-//SAAFE/DTD Public
> Document//EN") above.</quote>
>
> Not quite the same, anyhow, maybe this document-declaration should be
> pointing somewhere else.
Don't know what that means. Leave it until later.
-David
> I think I will have to wait on an answer here, in the meantime I can carry
> on and start to populate the glossary.xml file.
>
> [1] -
> http://www.saafe.org/documentation/rt/matchingInputAndOutputFormats.html
>
> Gav...
>
>
RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by "Gav...." <br...@brightontown.com.au>.
Back again,
> -----Original Message-----
> From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> Sent: Saturday, 1 April 2006 8:59 PM
> To: dev@forrest.apache.org
> Subject: RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
> define terminology for the various aspects of Dispatcher
>
> A wee bit further now then but I reckon I am stuck at this point,
>
> I Commented out these
>
> <!ELEMENT acronym (%content.mix;)*>
> <!ATTLIST acronym %common.att;>
>
> And it all validates fine, can not test if acronym tags still work yet
> because I now get a build error :-
>
> Cannot find catalogManager.properties
>
> I have seen this before and generally does not fail a build, but this one
> :-
>
> X [0] index.html BROKEN:
> org.apache.cocoon.acting.sourcetype,SourceTypeAction
>
> Is a new one on me, it may be something needs updating but I have no clue
> at
> the moment.
>
> Ideas?
Well I have one of my own and it goes like this:-
In input.xmap we have :
<map:actions>
<map:action logger="sitemap.action.sourcetype" name="sourcetype"
src="org.apache.cocoon.acting.sourcetype.SourceTypeAction">
<sourcetype name="glossary-v10">
<document-declaration public-id="-//SAAFE//DTD Glossary V1.0//EN"
/>
</sourcetype>
</map:action>
</map:actions>
The document-declaration points to I guess saafe.org and on this page [1]
A well know RDG :) says
<quote>Fixme ( rdg )
We should also support the public entity descriptor ("-//SAAFE/DTD Public
Document//EN") above.</quote>
Not quite the same, anyhow, maybe this document-declaration should be
pointing somewhere else.
I think I will have to wait on an answer here, in the meantime I can carry
on and start to populate the glossary.xml file.
[1] -
http://www.saafe.org/documentation/rt/matchingInputAndOutputFormats.html
Gav...
RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by "Gav...." <br...@brightontown.com.au>.
A wee bit further now then but I reckon I am stuck at this point,
I Commented out these
<!ELEMENT acronym (%content.mix;)*>
<!ATTLIST acronym %common.att;>
And it all validates fine, can not test if acronym tags still work yet
because I now get a build error :-
Cannot find catalogManager.properties
I have seen this before and generally does not fail a build, but this one :-
X [0] index.html BROKEN:
org.apache.cocoon.acting.sourcetype,SourceTypeAction
Is a new one on me, it may be something needs updating but I have no clue at
the moment.
Ideas?
Gav...
> -----Original Message-----
> From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> Sent: Saturday, 1 April 2006 8:45 PM
> To: dev@forrest.apache.org
> Subject: RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
> define terminology for the various aspects of Dispatcher
>
> Ok, I have reduced the glossary.xml to a minimum and now this is fine.
> I have one error causing the build to fail. The xmlvalidate is complaining
> that the glossary-v10.mod - Element Type "Acronym" must not be declared
> more
> than once. As far as I can see, it is only declared only once ....
>
> <!-- =============================================================== -->
> <!-- Element declarations -->
> <!-- =============================================================== -->
>
> <!ELEMENT glossary (authors?, (part)+)>
> <!ATTLIST glossary %common.att;>
>
> <!ELEMENT part (title, (item | part)+) >
> <!ATTLIST part %common.att;>
>
> <!ELEMENT item ((term)+, acronym?, see?, definition)>
> <!ATTLIST item %common.att;>
>
> <!ELEMENT term (%content.mix;)*>
> <!ATTLIST term %common.att;>
>
> <!ELEMENT acronym (%content.mix;)*>
> <!ATTLIST acronym %common.att;>
>
> <!ELEMENT definition (%flow;)*>
> <!ATTLIST definition cite IDREF #IMPLIED>
>
> <!ELEMENT see (id, text)>
>
> <!ELEMENT id (#PCDATA)>
>
> <!ELEMENT text (%content.mix;)*>
> <!ATTLIST text %common.att;>
>
> <!-- =============================================================== -->
> <!-- End of DTD -->
>
>
> ... Unless it is finding another declaration of it somewhere else?
>
> Apologies for all the posts, just thinking out loud, hopefully someone
> might
> jump in at an appropriate time when they see me going in the wrong
> direction. Anyway, off to remove the ONLY Acronym declaration and see what
> happens.
>
> Gav...
>
> > -----Original Message-----
> > From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> > Sent: Saturday, 1 April 2006 8:10 PM
> > To: dev@forrest.apache.org
> > Subject: RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
> > define terminology for the various aspects of Dispatcher
> >
> > Right, putting the .dtd and .mod files in xdocs directory and it now
> > validates the glossary.xml file -- the validation fails but its further
> > Than I got before.
> >
> > Gav...
> >
> > > -----Original Message-----
> > > From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> > > Sent: Saturday, 1 April 2006 8:01 PM
> > > To: dev@forrest.apache.org; brightoncomputers@brightontown.com.au
> > > Subject: RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-
> 639)
> > > define terminology for the various aspects of Dispatcher
> > >
> > > Ok, back again, input plugin created, same questions apply really :-
> > >
> > > > > Ok, I have started this, created the basic Glossary input plugin,
> > > > > Now need to configure it.
> > > > >
> > > > > I have questions (never done a plugin before so bear with me) :-
> > > > >
> > > > > I'm referring to the attachments provided on FOR-755 here -
> > > > >
> > > > > 1. Does glossary.xmap get renamed to and therefore replace
> > input.xmap
> > > ?
> > > > > 2.Where do the .dtd and .mod files need to go?
> > >
> > > (I have placed these in /resources/schemas/)
> > >
> > > > > 3a. I have put glossary2document.xsl in resources/stylesheets, is
> > this
> > > > > correct?
> > > > > 3b. And will I need to rename it to glossary-to-document.xsl ?
> > > > > 3c. If yes to 3b, anything else to change?
> > > > > 4. Glossary.xml is placed in the xdocs directory, this is the main
> > > file
> > > > we
> > > > > Need to add our Terminology. Looking quickly, its an A-Z
> > arrangement,
> > > > can
> > > > > we
> > > > > and should we have a separate A-Z for Dispatcher Terminology,
> > > therefore
> > > > a
> > > > > separate dispatcher-glossary.xml file, or will ALL Forrest
> > terminology
> > > > > reside in the same Glossary.xml file?
> > > > >
> > > > > I am doing this in Whiteboard at the moment, is this ok?
> > > > > I am not creating samples, I could rename Ross's original
> > Glossary.xml
> > > > to
> > > > > something else and use that as a sample ?
> > > > >
> > > > > Anything else?
> > > > >
> > > > > Lots of 'Q''s in there, sorry.
> > > > >
> > > > > 1 hour later ...
> > > > >
> > > > > Ant Test - Build Failed die to could not validate Glossary.xml, I
> > > guess
> > > > > that's because the .dtd and .mod files are in the wrong place.
> > >
> > > This is still the case, fails I guess due to the .dtd and .mod files
> not
> > > being found.
> > >
> > > Gav...
> > >
> > >
> > >
> > >
> > >
> > >
> > > --
> > > 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
> >
> >
> >
> >
> >
> > --
> > 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
>
>
>
>
>
> --
> 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
RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by "Gav...." <br...@brightontown.com.au>.
Ok, I have reduced the glossary.xml to a minimum and now this is fine.
I have one error causing the build to fail. The xmlvalidate is complaining
that the glossary-v10.mod - Element Type "Acronym" must not be declared more
than once. As far as I can see, it is only declared only once ....
<!-- =============================================================== -->
<!-- Element declarations -->
<!-- =============================================================== -->
<!ELEMENT glossary (authors?, (part)+)>
<!ATTLIST glossary %common.att;>
<!ELEMENT part (title, (item | part)+) >
<!ATTLIST part %common.att;>
<!ELEMENT item ((term)+, acronym?, see?, definition)>
<!ATTLIST item %common.att;>
<!ELEMENT term (%content.mix;)*>
<!ATTLIST term %common.att;>
<!ELEMENT acronym (%content.mix;)*>
<!ATTLIST acronym %common.att;>
<!ELEMENT definition (%flow;)*>
<!ATTLIST definition cite IDREF #IMPLIED>
<!ELEMENT see (id, text)>
<!ELEMENT id (#PCDATA)>
<!ELEMENT text (%content.mix;)*>
<!ATTLIST text %common.att;>
<!-- =============================================================== -->
<!-- End of DTD -->
... Unless it is finding another declaration of it somewhere else?
Apologies for all the posts, just thinking out loud, hopefully someone might
jump in at an appropriate time when they see me going in the wrong
direction. Anyway, off to remove the ONLY Acronym declaration and see what
happens.
Gav...
> -----Original Message-----
> From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> Sent: Saturday, 1 April 2006 8:10 PM
> To: dev@forrest.apache.org
> Subject: RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
> define terminology for the various aspects of Dispatcher
>
> Right, putting the .dtd and .mod files in xdocs directory and it now
> validates the glossary.xml file -- the validation fails but its further
> Than I got before.
>
> Gav...
>
> > -----Original Message-----
> > From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> > Sent: Saturday, 1 April 2006 8:01 PM
> > To: dev@forrest.apache.org; brightoncomputers@brightontown.com.au
> > Subject: RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
> > define terminology for the various aspects of Dispatcher
> >
> > Ok, back again, input plugin created, same questions apply really :-
> >
> > > > Ok, I have started this, created the basic Glossary input plugin,
> > > > Now need to configure it.
> > > >
> > > > I have questions (never done a plugin before so bear with me) :-
> > > >
> > > > I'm referring to the attachments provided on FOR-755 here -
> > > >
> > > > 1. Does glossary.xmap get renamed to and therefore replace
> input.xmap
> > ?
> > > > 2.Where do the .dtd and .mod files need to go?
> >
> > (I have placed these in /resources/schemas/)
> >
> > > > 3a. I have put glossary2document.xsl in resources/stylesheets, is
> this
> > > > correct?
> > > > 3b. And will I need to rename it to glossary-to-document.xsl ?
> > > > 3c. If yes to 3b, anything else to change?
> > > > 4. Glossary.xml is placed in the xdocs directory, this is the main
> > file
> > > we
> > > > Need to add our Terminology. Looking quickly, its an A-Z
> arrangement,
> > > can
> > > > we
> > > > and should we have a separate A-Z for Dispatcher Terminology,
> > therefore
> > > a
> > > > separate dispatcher-glossary.xml file, or will ALL Forrest
> terminology
> > > > reside in the same Glossary.xml file?
> > > >
> > > > I am doing this in Whiteboard at the moment, is this ok?
> > > > I am not creating samples, I could rename Ross's original
> Glossary.xml
> > > to
> > > > something else and use that as a sample ?
> > > >
> > > > Anything else?
> > > >
> > > > Lots of 'Q''s in there, sorry.
> > > >
> > > > 1 hour later ...
> > > >
> > > > Ant Test - Build Failed die to could not validate Glossary.xml, I
> > guess
> > > > that's because the .dtd and .mod files are in the wrong place.
> >
> > This is still the case, fails I guess due to the .dtd and .mod files not
> > being found.
> >
> > Gav...
> >
> >
> >
> >
> >
> >
> > --
> > 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
>
>
>
>
>
> --
> 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
RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by "Gav...." <br...@brightontown.com.au>.
Right, putting the .dtd and .mod files in xdocs directory and it now
validates the glossary.xml file -- the validation fails but its further
Than I got before.
Gav...
> -----Original Message-----
> From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> Sent: Saturday, 1 April 2006 8:01 PM
> To: dev@forrest.apache.org; brightoncomputers@brightontown.com.au
> Subject: RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
> define terminology for the various aspects of Dispatcher
>
> Ok, back again, input plugin created, same questions apply really :-
>
> > > Ok, I have started this, created the basic Glossary input plugin,
> > > Now need to configure it.
> > >
> > > I have questions (never done a plugin before so bear with me) :-
> > >
> > > I'm referring to the attachments provided on FOR-755 here -
> > >
> > > 1. Does glossary.xmap get renamed to and therefore replace input.xmap
> ?
> > > 2.Where do the .dtd and .mod files need to go?
>
> (I have placed these in /resources/schemas/)
>
> > > 3a. I have put glossary2document.xsl in resources/stylesheets, is this
> > > correct?
> > > 3b. And will I need to rename it to glossary-to-document.xsl ?
> > > 3c. If yes to 3b, anything else to change?
> > > 4. Glossary.xml is placed in the xdocs directory, this is the main
> file
> > we
> > > Need to add our Terminology. Looking quickly, its an A-Z arrangement,
> > can
> > > we
> > > and should we have a separate A-Z for Dispatcher Terminology,
> therefore
> > a
> > > separate dispatcher-glossary.xml file, or will ALL Forrest terminology
> > > reside in the same Glossary.xml file?
> > >
> > > I am doing this in Whiteboard at the moment, is this ok?
> > > I am not creating samples, I could rename Ross's original Glossary.xml
> > to
> > > something else and use that as a sample ?
> > >
> > > Anything else?
> > >
> > > Lots of 'Q''s in there, sorry.
> > >
> > > 1 hour later ...
> > >
> > > Ant Test - Build Failed die to could not validate Glossary.xml, I
> guess
> > > that's because the .dtd and .mod files are in the wrong place.
>
> This is still the case, fails I guess due to the .dtd and .mod files not
> being found.
>
> Gav...
>
>
>
>
>
>
> --
> 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
RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by "Gav...." <br...@brightontown.com.au>.
Ok, back again, input plugin created, same questions apply really :-
> > Ok, I have started this, created the basic Glossary input plugin,
> > Now need to configure it.
> >
> > I have questions (never done a plugin before so bear with me) :-
> >
> > I'm referring to the attachments provided on FOR-755 here -
> >
> > 1. Does glossary.xmap get renamed to and therefore replace input.xmap ?
> > 2.Where do the .dtd and .mod files need to go?
(I have placed these in /resources/schemas/)
> > 3a. I have put glossary2document.xsl in resources/stylesheets, is this
> > correct?
> > 3b. And will I need to rename it to glossary-to-document.xsl ?
> > 3c. If yes to 3b, anything else to change?
> > 4. Glossary.xml is placed in the xdocs directory, this is the main file
> we
> > Need to add our Terminology. Looking quickly, its an A-Z arrangement,
> can
> > we
> > and should we have a separate A-Z for Dispatcher Terminology, therefore
> a
> > separate dispatcher-glossary.xml file, or will ALL Forrest terminology
> > reside in the same Glossary.xml file?
> >
> > I am doing this in Whiteboard at the moment, is this ok?
> > I am not creating samples, I could rename Ross's original Glossary.xml
> to
> > something else and use that as a sample ?
> >
> > Anything else?
> >
> > Lots of 'Q''s in there, sorry.
> >
> > 1 hour later ...
> >
> > Ant Test - Build Failed die to could not validate Glossary.xml, I guess
> > that's because the .dtd and .mod files are in the wrong place.
This is still the case, fails I guess due to the .dtd and .mod files not
being found.
Gav...
RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Posted by "Gav...." <br...@brightontown.com.au>.
Erm, first mistake, it's an input plugin, back later...
Gav...
> -----Original Message-----
> From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> Sent: Saturday, 1 April 2006 7:34 PM
> To: dev@forrest.apache.org
> Subject: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
> define terminology for the various aspects of Dispatcher
>
> Hi All,
>
> > -----Original Message-----
> > From: David Crossley [mailto:crossley@apache.org]
> > Sent: Saturday, 1 April 2006 6:42 AM
> > To: dev@forrest.apache.org; brightoncomputers@brightontown.com.au
> > Subject: Re: [jira] Updated: (FOR-639) define terminology for the
> various
> > aspects of Dispatcher
> >
> > Gav.... wrote:
> > > Ok, Paul has also mentioned this so needs sorting, I'll see what I can
> > come
> > > up with in the next day or two.
> > >
> > > What we have so far it terms of Dispatcher Docs published:-
> > >
> > > dispatcher.html
> > > howto-structurer-install.html
> > > howto-dispatcher-quickstart.html
> > > howto-structurer-dsl.html
> > > howto-structurer-contracts.html
> > >
> > > The howto-structurer-install.html is actually describing how to
> > > Install the "Dispatcher" so I think should be renamed to avoid
> > > Further confusion.
> >
> > Yes, i have wondered about that too.
> > Today i will 'svn move' the documents,
> > amend all the links and references, and
> > create .htaccess redirects for the website.
> >
> > > The howto-structurer-dsl is out of date and contains incorrect
> > > Contract examples. Is there an upto date version of this or
> > > Shall I attempt to correct the examples given.
> > > Also, I would like an example of what is meant by
> > > "Domain Specific" in this context (of -dsl)
> > >
> > > This FOR is about clarifying and defining terminology used. So do we
> > > Want a new page called dispatcher-terminology.html or similar and how
> > > Do we want the content presented - in example form, or in a strict
> > > Dictionary type arrangement leaving the examples on the howto pages?
> >
> > There was a mailing list discussion about this.
> > Need to find that.
> >
> > One really good idea was to create the new Glossary plugin
> > http://issues.apache.org/jira/browse/FOR-755
> > and use that.
>
> Ok, I have started this, created the basic Glossary output plugin,
> Now need to configure it.
>
> I have questions (never done a plugin before so bear with me) :-
>
> I'm referring to the attachments provided on FOR-755 here -
>
> 1. Does glossary.xmap get renamed to and therefore replace output.xmap ?
> 2.Where do the .dtd and .mod files need to go?
> 3a. I have put glossary2document.xsl in resources/stylesheets, is this
> correct?
> 3b. And will I need to rename it to glossary-to-document.xsl ?
> 3c. If yes to 3b, anything else to change?
> 4. Glossary.xml is placed in the xdocs directory, this is the main file we
> Need to add our Terminology. Looking quickly, its an A-Z arrangement, can
> we
> and should we have a separate A-Z for Dispatcher Terminology, therefore a
> separate dispatcher-glossary.xml file, or will ALL Forrest terminology
> reside in the same Glossary.xml file?
>
> I am doing this in Whiteboard at the moment, is this ok?
> I am not creating samples, I could rename Ross's original Glossary.xml to
> something else and use that as a sample ?
>
> Anything else?
>
> Lots of 'Q''s in there, sorry.
>
> 1 hour later ...
>
> Ant Test - Build Failed die to could not validate Glossary.xml, I guess
> that's because the .dtd and .mod files are in the wrong place.
>
> Gav...
>
> >
> > Failing that, i reckon just use an ordinary document
> > with concise definitions that link to examples in
> > the other documents.
>
> I have started this also, in fact started in when your idea of
> Using the Glossary Plugin came through. Hmm, I wonder which I'll
> Finish first :)
>
> >
> > However it gets done is good.
> >
> > -David
>
> On it,
>
> Gav...
>
>
>
>
>
> --
> 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