forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gav...." <brightoncomput...@brightontown.com.au>
Subject RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Date Sat, 01 Apr 2006 12:58:36 GMT
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




Mime
View raw message