You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Thorsten Scherler <th...@wyona.com> on 2006/04/03 13:01:29 UTC
RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
define terminology for the various aspects of Dispatcher
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: 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