You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Clay Leeds <cl...@medata.com> on 2004/10/19 07:52:54 UTC
Re: xml-fop Build Failed
Just when you thought it was safe...
On Aug 3, 2004, at 4:09 PM, Dave Brondsema wrote:
> The sitemap.xmap is no longer necessary, forrest provides a default
> one which works fine. .fo files aren't needed in the raw directories.
>
> cd src/documentation
> rm sitemap.xmap
> cd content
> find fo/ dev/ -name *.fo | xargs rm
>
> But the embed.fo doesn't work with forrest. So..
>
> mv xdocs/fo/embed.fo fo/embed.fo
> mv xdocs/dev/fo/embed* dev/fo/
>
> And then manually generate the pdfs that correspond.
>
> BUILD SUCCESSFUL
I'm getting an exception when I try to build xml-fop.
I attempted to follow the above instructions, although I had to do a
little workaround to get it to work:
1. I used my CVS GUI to do a /cvs co https://... xml-fop/
2. I extracted the xml-fop xdocs/* files from the 'xml-fop_new.zip'
file[1] into a temporary directory.
3. I followed Dave's instructions (above)
4. I then manually copied (I must be a masochist) each of the xml-fop
xdocs files from the 'xml-fop_new.zip' file[1] into my xml-fop /cvs co
https://... xml-fop/ dir.
And the stack dump below shows where I stopped.
Web Maestro Clay
[1]
http://homepage.mac.com/webmaestro/xml-fop/xml-fop_new.zip
Here's the stack dump:
[clay@Web-Maestro-Mac xml-fop]$ forrest
Apache Forrest. Run 'forrest -projecthelp' to list options
Buildfile:
/Users/Shared/_WebDLs/_repos/forrest/src/core/forrest.build.xml
init-props:
Loading project specific properties from
/Users/Shared/_WebDLs/_repos/xml-fop/forrest.properties
Loading user specific properties from /Users/clay/forrest.properties
Loading default properties from
/Users/Shared/_WebDLs/_repos/forrest/src/core/context/default-
forrest.properties
echo-settings:
check-skin:
fetch-skins-descriptors:
fetch-skin:
unpack-skins:
init-skins:
init:
-prepare-classpath:
check-contentdir:
examine-proj:
validation-props:
validate-xdocs:
90 file(s) have been successfully validated.
...validated xdocs
validate-skinconf:
1 file(s) have been successfully validated.
...validated skinconf
validate-sitemap:
...validated sitemap
validate-skins-stylesheets:
validate-skins:
validate-skinchoice:
...validated existence of skin 'pelt'
validate-stylesheets:
validate:
site:
Deleting directory
/Users/Shared/_WebDLs/_repos/xml-fop/build/tmp/cocoon-work
Created dir: /Users/Shared/_WebDLs/_repos/xml-fop/build/tmp/cocoon-work
Copying the various non-generated resources to site.
Warnings will be issued if the optional project resources are not found.
This is often the case, because they are optional and so may not be
available.
Copying project resources and images to site ...
Warning: /Users/Shared/_WebDLs/_repos/xml-fop/build/webapp/resources
not found.
Copying 25 files to /Users/Shared/_WebDLs/_repos/xml-fop/build/site
Copying main skin images to site ...
Copying 21 files to
/Users/Shared/_WebDLs/_repos/xml-fop/build/site/skin/images
Copying 13 files to
/Users/Shared/_WebDLs/_repos/xml-fop/build/site/skin/images
Copying project skin images to site ...
Warning:
/Users/Shared/_WebDLs/_repos/xml-fop/src/documentation/skins/common/
images not found.
Warning:
/Users/Shared/_WebDLs/_repos/xml-fop/src/documentation/skins/pelt/
images not found.
Copying main skin css and js files to site ...
Copying 8 files to /Users/Shared/_WebDLs/_repos/xml-fop/build/site/skin
Copying 6 files to /Users/Shared/_WebDLs/_repos/xml-fop/build/site/skin
Copying project skin css and js files to site ...
Warning:
/Users/Shared/_WebDLs/_repos/xml-fop/src/documentation/skins/common not
found.
Warning:
/Users/Shared/_WebDLs/_repos/xml-fop/src/documentation/skins/pelt not
found.
Finished copying the non-generated resources.
Now Cocoon will generate the rest ...
Static site will be generated at:
/Users/Shared/_WebDLs/_repos/xml-fop/build/site
Note that there are various reasons for "build failed" messages.
* Cocoon will report the status of each document:
- in column 1: *=okay X=brokenLink ^=pageSkipped (see FAQ).
* Even if only one link is broken, you will still get "failed".
* Your site would still be generated, but some pages would be broken.
* Please check the file:
/Users/Shared/_WebDLs/_repos/xml-fop/build/tmp/brokenlinks.xml
for any broken links in the generated site.
------------------------------------------------------------------------
cocoon 2.2.0-dev
Copyright (c) 1999-2004 Apache Software Foundation. All rights reserved.
------------------------------------------------------------------------
Cannot find CatalogManager.properties
^ dev/
^ design/
^ design/alt.design/
* [1/80] [80/83] 13.2s 20.7Kb linkmap.html
* [2/80] [1/27] 1.894s 11.1Kb design/alt.design/coroutines.html
* [3/79] [0/30] 1.185s 21.0Kb design/breakpos.html
* [4/78] [0/44] 1.081s 8.6Kb logocontest.html
* [5/77] [0/0] 0.951s 2.3Kb skin/basic.css
* [6/76] [0/45] 1.825s 11.2Kb extensions.html
* [7/75] [0/30] 1.032s 10.5Kb design/images.html
* [8/75] [1/27] 0.954s 13.2Kb dev/implement.html
* [9/80] [6/23] 0.895s 11.4Kb
design/alt.design/properties/introduction.html
* [10/79] [0/47] 0.907s 11.9Kb configuration.html
* [11/78] [0/30] 1.683s 15.1Kb design/renderers.html
* [12/77] [0/27] 0.979s 12.7Kb dev/fonts.html
* [13/76] [0/43] 0.885s 9.7Kb todo.html
* [15/86] [12/40] 0.924s 11.7Kb dev/svg.html
X [0] dev/svg/paints.pdf BROKEN:
org.apache.fop.apps.FOPException: No flow in page-sequence
* [17/84] [0/23] 7.319s 5.0Kb
design/alt.design/properties/PropertyConsts-class.html
* [18/83] [0/30] 0.848s 8.4Kb design/pdf-library.html
* [19/82] [0/27] 0.862s 18.8Kb dev/conventions.html
X [0] dev/svg/transparency.pdf
BROKEN: org.apache.fop.apps.FOPException: No flow in page-sequence
* [21/83] [3/30] 0.829s 12.2Kb design/alt.design/footnotes.html
* [22/82] [0/27] 1.663s 18.3Kb dev/doc.html
* [23/81] [0/49] 0.845s 19.0Kb running.html
* [24/80] [0/0] 0.253s 1.0Kb skin/print.css
* [26/78] [0/29] 1.055s 23.3Kb dev/rtflib.html
* [27/77] [0/26] 1.136s 17.5Kb design/alt.design/traits.html
* [28/76] [0/30] 0.708s 8.9Kb design/useragent.html
* [29/75] [0/44] 1.741s 17.2Kb servlets.html
* [30/74] [0/44] 0.777s 9.6Kb download.html
* [31/73] [0/32] 1.162s 9.2Kb dev/faq.html
* [32/72] [0/0] 0.411s 108.9Kb dev/fo/embedding.fo
* [33/71] [0/43] 0.723s 10.8Kb compiling.html
* [34/70] [0/26] 0.535s 5.6Kb design/alt.design/xml-parsing.html
X [0] dev/svg/link.pdf BROKEN:
org.apache.fop.apps.FOPException: No flow in page-sequence
* [38/66] [0/46] 1.751s 23.3Kb graphics.html
* [39/65] [0/30] 1.313s 26.3Kb design/properties.html
* [40/76] [12/12] 0.77s 10.9Kb skin/screen.css
* [42/74] [0/0] 6.505s 161b
skin/images/rc-t-r-5-1header-2searchbox-3searchbox.png
* [43/73] [0/0] 0.272s 161b
skin/images/rc-t-l-5-1header-2tab-selected-3tab-selected.png
* [45/71] [0/0] 0.503s 168b
skin/images/rc-t-r-15-1body-2menu-3menu.png
* [46/70] [0/0] 0.271s 161b
skin/images/rc-t-r-5-1header-2tab-unselected-3tab-unselected.png
* [47/73] [4/48] 0.987s 10.7Kb index.html
* [49/71] [0/43] 1.093s 18.8Kb team.html
* [50/70] [0/23] 0.657s 5.0Kb
design/alt.design/properties/enumerated-values.html
* [52/68] [0/44] 1.274s 11.9Kb news.html
* [53/67] [0/23] 0.588s 5.0Kb
design/alt.design/properties/propertyExpressions.html
* [54/66] [0/30] 2.222s 9.8Kb design/extending.html
* [55/65] [0/43] 0.943s 14.0Kb anttask.html
* [56/64] [0/26] 0.82s 13.0Kb
design/alt.design/compound-properties.html
* [58/62] [0/43] 1.436s 18.0Kb resources.html
* [59/61] [0/30] 0.763s 6.8Kb design/startup.html
* [60/60] [0/30] 0.808s 15.2Kb dev/tools.html
* [62/59] [1/30] 1.931s 15.7Kb design/alt.design/galleys.html
* [64/57] [0/32] 0.761s 14.3Kb design/fotree.html
* [65/56] [0/43] 4.258s 6.8Kb compliance.html
* [66/55] [0/35] 0.91s 13.8Kb design/index.html
* [67/54] [0/30] 0.89s 9.1Kb design/embedding.html
* [68/53] [0/0] 0.23s 168b
skin/images/rc-b-l-15-1body-2menu-3menu.png
* [69/52] [0/26] 4.77s 41.4Kb
design/alt.design/user-agent-refs.html
* [70/51] [0/30] 1.622s 7.2Kb design/optimise.html
* [72/49] [0/29] 0.676s 9.6Kb dev/extensions.html
X [0] dev/svg/paints.svg BROKEN:
/Users/Shared/_WebDLs/_repos/xml-fop/src/documentation/content/xdocs/
dev/svg/paints.xml (No such file or directory)
* [74/47] [0/0] 0.2s 161b
skin/images/rc-t-l-5-1header-2searchbox-3searchbox.png
X [0] dev/svg/text.svg BROKEN:
/Users/Shared/_WebDLs/_repos/xml-fop/src/documentation/content/xdocs/
dev/svg/text.xml (No such file or directory)
X [0] dev/svg/images.svg BROKEN:
/Users/Shared/_WebDLs/_repos/xml-fop/src/documentation/content/xdocs/
dev/svg/images.xml (No such file or directory)
* [77/44] [0/27] 0.803s 12.5Kb dev/testing.html
* [78/43] [0/46] 0.915s 22.4Kb hyphenation.html
* [79/42] [0/43] 0.701s 9.5Kb bugs.html
* [80/41] [0/43] 0.905s 21.5Kb fonts.html
* [81/40] [0/0] 0.317s 1.2Kb skin/profile.css
* [82/39] [0/30] 1.645s 9.4Kb design/svg.html
* [83/38] [0/27] 0.798s 10.9Kb dev/release.html
X [0] dev/svg/link.svg BROKEN:
/Users/Shared/_WebDLs/_repos/xml-fop/src/documentation/content/xdocs/
dev/svg/link.xml (No such file or directory)
* [87/35] [1/44] 0.822s 14.6Kb status.html
* [89/33] [0/0] 0.17s 161b
skin/images/rc-t-l-5-1header-2tab-unselected-3tab-unselected.png
* [90/32] [0/0] 0.608s 0b dev/fo/embedding.pdf
Exception in thread "main" java.lang.NoSuchMethodError:
org.apache.batik.bridge.UnitProcessor.createContext(Lorg/apache/batik/
bridge/BridgeContext;Lorg/w3c/dom/Element;)Lorg/apache/batik/util/
UnitProcessor$Context;
at org.apache.fop.svg.SVGElement.layout(SVGElement.java:218)
at
org.apache.fop.fo.flow.InstreamForeignObject.layout(InstreamForeignObjec
t.java:251)
at org.apache.fop.fo.flow.Block.layout(Block.java:257)
at
org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:154)
at
org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:110)
at
org.apache.fop.fo.pagination.PageSequence.makePage(PageSequence.java:
400)
at
org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:338)
at
org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java:262)
at
org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:223)
at
org.apache.cocoon.xml.AbstractXMLPipe.endElement(AbstractXMLPipe.java:
112)
at
org.apache.cocoon.xml.AbstractXMLPipe.endElement(AbstractXMLPipe.java:
112)
at
org.apache.cocoon.xml.xlink.XLinkPipe.endElement(XLinkPipe.java:211)
at
org.apache.cocoon.components.sax.XMLTeePipe.endElement(XMLTeePipe.java:
89)
at
org.apache.cocoon.environment.internal.EnvironmentChanger.endElement(Env
ironmentStack.java:147)
at
org.apache.cocoon.components.sax.XMLTeePipe.endElement(XMLTeePipe.java:
89)
at
org.apache.cocoon.components.sax.XMLByteStreamInterpreter.parse(XMLByteS
treamInterpreter.java:100)
at
org.apache.cocoon.components.sax.XMLByteStreamInterpreter.deserialize(XM
LByteStreamInterpreter.java:73)
at
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipe
line.processXMLPipeline(AbstractCachingProcessingPipeline.java:218)
at
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process
(AbstractProcessingPipeline.java:685)
at
org.apache.cocoon.components.source.impl.SitemapSource.toSAX(SitemapSour
ce.java:352)
at
org.apache.cocoon.components.source.SourceUtil.parse(SourceUtil.java:
206)
at
org.apache.cocoon.generation.FileGenerator.generate(FileGenerator.java:
117)
at
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipe
line.processXMLPipeline(AbstractCachingProcessingPipeline.java:235)
at
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process
(AbstractProcessingPipeline.java:478)
at
org.apache.cocoon.components.treeprocessor.sitemap.SerializeNode.invoke(
SerializeNode.java:134)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(AbstractParentProcessingNode.java:54)
at
org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.i
nvoke(PreparableMatchNode.java:112)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(AbstractParentProcessingNode.java:76)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(P
ipelineNode.java:138)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(AbstractParentProcessingNode.java:76)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(
PipelinesNode.java:95)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process
(ConcreteTreeProcessor.java:298)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process
(ConcreteTreeProcessor.java:241)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreePro
cessor.java:238)
at org.apache.cocoon.Cocoon.process(Cocoon.java:646)
at
org.apache.cocoon.bean.CocoonWrapper.getPage(CocoonWrapper.java:441)
at
org.apache.cocoon.bean.CocoonBean.processTarget(CocoonBean.java:493)
at
org.apache.cocoon.bean.CocoonBean.process(CocoonBean.java:354)
at org.apache.cocoon.Main.main(Main.java:321)
^C[clay@Web-Maestro-Mac xml-fop]$
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: planning for Forrestbot at apache.org
Posted by Clay Leeds <cl...@medata.com>.
On Oct 26, 2004, at 6:33 AM, David Crossley wrote:
> Okay i have summarised that previous discussion from
> Infrastructure@a.o and built two proposal documents.
> These are at the Forrest website.
>
> Draft: Proposal for ASF-wide documentation staging and publishing
> http://forrest.apache.org/proposal-asf-publish.html
> This draws together various past discussions to address
> the diverse issues with documentation publishing at apache.org
>
> Draft: Proposal for ASF-wide Forrestbot
> http://forrest.apache.org/proposal-asf-forrestbot.html
> This shows the Forrestbot role.
>
> I am going to continue the previous discussions on the
> Infrastructure mailing list. Any Apache committers can
> join in to help.
> http://www.apache.org/foundation/mailinglists.html#foundation-
> infrastructure
>
> --David
FWIW, I responded to David's 'ASF-wide doc' & 'Forrestbot' proposals on
infrastructure@, general@x.a.o & dev@f.a.o[1]
[1]
http://issues.apache.org/eyebrowse/ReadMsg?
listName=dev@forrest.apache.org&msgNo=15242
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: planning for Forrestbot at apache.org
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> This looks like the type of thing a PMC should consider (Apache XML
> Project, Apache XML Graphics Project, Apache Xalan Project, etc.). Or
> should we wait until the Draft has been completed?
As the title of the proposals say ...
Proposal for ASF-wide documentation staging and publishing
Proposal for ASF-wide Forrestbot
.............^^^^^^^^
It cuts across all Apache projects. So yes we need people
from all projects to get involved in the discussion on
infrastructure@a.o
The "drafts" will not be completed until people help
to do so. As the documents say, this is the summary
of the discussion so far.
--
David Crossley
Re: planning for Forrestbot at apache.org
Posted by Clay Leeds <cl...@medata.com>.
This looks like the type of thing a PMC should consider (Apache XML
Project, Apache XML Graphics Project, Apache Xalan Project, etc.). Or
should we wait until the Draft has been completed?
Cheers!
On Oct 26, 2004, at 6:33 AM, David Crossley wrote:
> Okay i have summarised that previous discussion from
> Infrastructure@a.o and built two proposal documents.
> These are at the Forrest website.
>
> Draft: Proposal for ASF-wide documentation staging and publishing
> http://forrest.apache.org/proposal-asf-publish.html
> This draws together various past discussions to address
> the diverse issues with documentation publishing at apache.org
>
> Draft: Proposal for ASF-wide Forrestbot
> http://forrest.apache.org/proposal-asf-forrestbot.html
> This shows the Forrestbot role.
>
> I am going to continue the previous discussions on the
> Infrastructure mailing list. Any Apache committers can
> join in to help.
> http://www.apache.org/foundation/mailinglists.html#foundation-
> infrastructure
>
> --David
>
> David Crossley wrote:
>> Co-incidence. There is a closely related discussion just
>> started at cocoon-dev:
>> http://marc.theaimsgroup.com/?t=109835905000003
>>
>> We have also had big discussions on this at infrastructure.at.a.o
>> a few months ago. That needs to be summarised for forrest-dev
>> I will try to do that soon.
>>
>> --David
>>
>> David Crossley wrote:
>>> Clay Leeds wrote:
>>>> David Crossley wrote:
>>>>>>> Yes, it will be wonderful when we finally get a forrestbot at
>>>>>>> ASF.
>>>>>>
>>>>>> Yes that will. What is prohibiting that? Is there anything I
>>>>>> (we--either the FOP Team or someone else from the Forrest Team)
>>>>>> can do
>>>>>> to help?
>>>>>
>>>>> I thought that i already said. It is that we are waiting and
>>>>> waiting
>>>>> for the new Apache machines to come on-line. On the current
>>>>> machines
>>>>> no project can run live services. Cocoon and Forrest have been
>>>>> waiting since the year dot.
>>>>
>>>> 'the year dot.' hmph! never heard it called that, but I assume you
>>>> mean
>>>> Jan 1, 2004.
>>>
>>> It is an expression which means "since the beginning".
>>> In this case, since the beginning of Cocoon and Forrest projects.
>>>
>>>>> It is getting very close now, so yes the Forrest "team",
>>>>> which includes anybody who wants to help, needs to start
>>>>> getting our thinking caps on. That is for a separate
>>>>> email thread soon.
>>>>
>>>> Sounds good. I'll pay attention.
>>>
>>> Thanks.
>
>
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: planning for Forrestbot at apache.org
Posted by David Crossley <cr...@apache.org>.
Okay i have summarised that previous discussion from
Infrastructure@a.o and built two proposal documents.
These are at the Forrest website.
Draft: Proposal for ASF-wide documentation staging and publishing
http://forrest.apache.org/proposal-asf-publish.html
This draws together various past discussions to address
the diverse issues with documentation publishing at apache.org
Draft: Proposal for ASF-wide Forrestbot
http://forrest.apache.org/proposal-asf-forrestbot.html
This shows the Forrestbot role.
I am going to continue the previous discussions on the
Infrastructure mailing list. Any Apache committers can
join in to help.
http://www.apache.org/foundation/mailinglists.html#foundation-infrastructure
--David
David Crossley wrote:
> Co-incidence. There is a closely related discussion just
> started at cocoon-dev:
> http://marc.theaimsgroup.com/?t=109835905000003
>
> We have also had big discussions on this at infrastructure.at.a.o
> a few months ago. That needs to be summarised for forrest-dev
> I will try to do that soon.
>
> --David
>
> David Crossley wrote:
> > Clay Leeds wrote:
> > > David Crossley wrote:
> > > >>> Yes, it will be wonderful when we finally get a forrestbot at ASF.
> > > >>
> > > >> Yes that will. What is prohibiting that? Is there anything I
> > > >> (we--either the FOP Team or someone else from the Forrest Team) can do
> > > >> to help?
> > > >
> > > > I thought that i already said. It is that we are waiting and waiting
> > > > for the new Apache machines to come on-line. On the current machines
> > > > no project can run live services. Cocoon and Forrest have been
> > > > waiting since the year dot.
> > >
> > > 'the year dot.' hmph! never heard it called that, but I assume you mean
> > > Jan 1, 2004.
> >
> > It is an expression which means "since the beginning".
> > In this case, since the beginning of Cocoon and Forrest projects.
> >
> > > > It is getting very close now, so yes the Forrest "team",
> > > > which includes anybody who wants to help, needs to start
> > > > getting our thinking caps on. That is for a separate
> > > > email thread soon.
> > >
> > > Sounds good. I'll pay attention.
> >
> > Thanks.
planning for Forrestbot at apache.org
Posted by David Crossley <cr...@apache.org>.
Co-incidence. There is a closely related discussion just
started at cocoon-dev:
http://marc.theaimsgroup.com/?t=109835905000003
We have also had big discussions on this at infrastructure.at.a.o
a few months ago. That needs to be summarised for forrest-dev
I will try to do that soon.
--David
David Crossley wrote:
> Clay Leeds wrote:
> > David Crossley wrote:
> > >>> Yes, it will be wonderful when we finally get a forrestbot at ASF.
> > >>
> > >> Yes that will. What is prohibiting that? Is there anything I
> > >> (we--either the FOP Team or someone else from the Forrest Team) can do
> > >> to help?
> > >
> > > I thought that i already said. It is that we are waiting and waiting
> > > for the new Apache machines to come on-line. On the current machines
> > > no project can run live services. Cocoon and Forrest have been
> > > waiting since the year dot.
> >
> > 'the year dot.' hmph! never heard it called that, but I assume you mean
> > Jan 1, 2004.
>
> It is an expression which means "since the beginning".
> In this case, since the beginning of Cocoon and Forrest projects.
>
> > > It is getting very close now, so yes the Forrest "team",
> > > which includes anybody who wants to help, needs to start
> > > getting our thinking caps on. That is for a separate
> > > email thread soon.
> >
> > Sounds good. I'll pay attention.
>
> Thanks.
Re: xml-fop Build Failed
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> David Crossley wrote:
> > A while ago i heard you mention 'forrestbot' in a passing comment.
> > I asked "What forrestbot" ... i did not realise that any Apache
> > websites were actually being updated by the old experimental
> > forrestbot.
>
> So, the FOP Dev => Doc Mgmt page:
> a) is incorrect as the forrestbot isn't working
I gather that these are questions, so will try to answer.
I am not sure if the old forrestbot is working or not.
Especially not sure about the penultimate phase where it
'cvs commit' the generated HTML back to the FOP cvs,
nor about the ultimate phase on the server where the
'cvs update' would be done to make the docs be published.
> b) is technically correct (it works but uses forrest-0.5.x)
Depends on the answer to a).
Yes, the old forrestbot is still 0.5
> >> In other words, until I get the xdocs/ back in the running, we aren't
> >> updating our site unless I manually edit the files using vi. If
> >> necessary, I could do your suggestion below, although I'll have to
> >> reapply any changes to the 'working' xdocs/*.xml files (which isn't
> >> really that big a deal).
> >
> > FOP is going to need to do the suggestion below anyway.
> > However lets get your build issues solved ASAP.
>
> Agreed. As soon as I get a BUILD SUCCESSFUL, I will:
> 1. COMMIT changes to xdocs/
> 2. determine more recent changes & update xdocs/ w newer content
> 3. COMMIT changes to xdocs/
> 4. COMMIT HTML changes using suggestion below from /forrest/ build/site/
>
> Does it sound like I've got the process figured out?
Yes.
> >>> Yes, it will be wonderful when we finally get a forrestbot at ASF.
> >>> --
> >>> David Crossley
> >>
> >> Yes that will. What is prohibiting that? Is there anything I
> >> (we--either the FOP Team or someone else from the Forrest Team) can do
> >> to help?
> >
> > I thought that i already said. It is that we are waiting and waiting
> > for the new Apache machines to come on-line. On the current machines
> > no project can run live services. Cocoon and Forrest have been
> > waiting since the year dot.
>
> 'the year dot.' hmph! never heard it called that, but I assume you mean
> Jan 1, 2004.
It is an expression which means "since the beginning".
In this case, since the beginning of Cocoon and Forrest projects.
> > It is getting very close now, so yes the Forrest "team",
> > which includes anybody who wants to help, needs to start
> > getting our thinking caps on. That is for a separate
> > email thread soon.
>
> Sounds good. I'll pay attention.
Thanks.
--
David Crossley
Re: xml-fop Build Failed
Posted by Clay Leeds <cl...@medata.com>.
On Oct 19, 2004, at 10:24 PM, David Crossley wrote:
> Clay Leeds wrote:
>> Speaking of which, it sounds like Apache Forrest-0.6 is not yet live
>> on
>> the server which serves <http://xml.apache.org/fop/>.
>
> There are no live services running on any Apache server.
Thanks!
>> I don't understand what you meant when you said 'I wondered that a
>> while ago, but you must have missed my question.'
>
> A while ago i heard you mention 'forrestbot' in a passing comment.
> I asked "What forrestbot" ... i did not realise that any Apache
> websites were actually being updated by the old experimental
> forrestbot.
So, the FOP Dev => Doc Mgmt page:
a) is incorrect as the forrestbot isn't working
b) is technically correct (it works but uses forrest-0.5.x)
>> In other words, until I get the xdocs/ back in the running, we aren't
>> updating our site unless I manually edit the files using vi. If
>> necessary, I could do your suggestion below, although I'll have to
>> reapply any changes to the 'working' xdocs/*.xml files (which isn't
>> really that big a deal).
>
> FOP is going to need to do the suggestion below anyway.
> However lets get your build issues solved ASAP.
Agreed. As soon as I get a BUILD SUCCESSFUL, I will:
1. COMMIT changes to xdocs/
2. determine more recent changes & update xdocs/ w newer content
3. COMMIT changes to xdocs/
4. COMMIT HTML changes using suggestion below from /forrest/ build/site/
Does it sound like I've got the process figured out?
>>> Yes, it will be wonderful when we finally get a forrestbot at ASF.
>>> --
>>> David Crossley
>>
>> Yes that will. What is prohibiting that? Is there anything I
>> (we--either the FOP Team or someone else from the Forrest Team) can do
>> to help?
>
> I thought that i already said. It is that we are waiting and waiting
> for the new Apache machines to come on-line. On the current machines
> no project can run live services. Cocoon and Forrest have been
> waiting since the year dot.
'the year dot.' hmph! never heard it called that, but I assume you mean
Jan 1, 2004.
> It is getting very close now, so yes the Forrest "team",
> which includes anybody who wants to help, needs to start
> getting our thinking caps on. That is for a separate
> email thread soon.
Sounds good. I'll pay attention.
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Build Failed
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> David Crossley wrote:
> > Clay Leeds wrote:
> >> And now onto the response to your question.
> >> ========================
> >>
> >> Instructions for updating xml-fop are on the Development tab's > Doc
> >> Mgmt page [1]:
> >> 1. Developer commits code to FOP repository
> >> 2. Forrestbot "refresh". Automatically done every six hours.
> >> Can be manually refreshed by authorized users at the
> >> Forrestbot Web Interface.
> >> 3. Forrestbot "publish". Always done manually at the
> >> Forrestbot Web Interface.
> >> 4. Automatic Live Site Update every six hours (midnight, 6am,
> >> noon, 6pm Pacific time).
> >
> > I see. I wondered that a while ago, but you must have
> > missed my question. I would suggest going to the manual
> > build method that i described below for "xml-commons".
> > It could be a long time before we can update the Forrestbot.
> > We are waiting for one of the new Apache servers to come
> > on-line.
>
> Glad you asked the question as it appears we (the FOP Team) need to
> either update our Doc Mgmt page, or temporarily 'double' update the web
> site manually: 1) vi over SSH updating of HTML; 2) xdocs/*.xml.
>
> Speaking of which, it sounds like Apache Forrest-0.6 is not yet live on
> the server which serves <http://xml.apache.org/fop/>.
There are no live services running on any Apache server.
> I don't understand what you meant when you said 'I wondered that a
> while ago, but you must have missed my question.'
A while ago i heard you mention 'forrestbot' in a passing comment.
I asked "What forrestbot" ... i did not realise that any Apache
websites were actually being updated by the old experimental
forrestbot.
> Wasn't your question:
> David Crossley wrote:
> > Can you tell me how you currently update the FOP website.
>
> I thought I answered this question when I said:
> > With the exception of a couple of 'vi over SSH' changes to the LIVE
> > site (xml-site/targets/fop/), the FOP docs have not been updated
> > recently. We are in dire need of update.
>
> In other words, until I get the xdocs/ back in the running, we aren't
> updating our site unless I manually edit the files using vi. If
> necessary, I could do your suggestion below, although I'll have to
> reapply any changes to the 'working' xdocs/*.xml files (which isn't
> really that big a deal).
FOP is going to need to do the suggestion below anyway.
However lets get your build issues solved ASAP.
> Was there another question you had that I didn't answer? :-)
:-)
> David Crossley wrote:
> >>> For most websites it is entirely a manual operation.
> >>> For example at "XML Commons" we do this:
> >>> *) Edit the source at
> >>> cvs://xml-commons/src/documentation/content/xdocs/*.xml
> >>> *) Generate the site locally with whatever Forrest that
> >>> the project has decided to use.
> >>> *) Commit the HTML/PDF result to cvs://xml-site/targets/commons/
> >>> *) Commit the edited source to
> >>> cvs://xml-commons/src/documentation/content/xdocs/
> >>>
> >>> To publish the result, we have an automated cron job to
> >>> do 'cvs update'. Otherwise we do it manually with
> >>> ssh cvs.apache.org
> >>> cd /www/xml.apache.org/commons
> >>> cvs -q update -dP
> >>
> >> The Doc Mgmt page [1] has a forrestbot interface which makes
> >> PUBLISHing
> >> fairly simple.
> >
> > Yes, it will be wonderful when we finally get a forrestbot at ASF.
> > --
> > David Crossley
>
> Yes that will. What is prohibiting that? Is there anything I
> (we--either the FOP Team or someone else from the Forrest Team) can do
> to help?
I thought that i already said. It is that we are waiting and waiting
for the new Apache machines to come on-line. On the current machines
no project can run live services. Cocoon and Forrest have been
waiting since the year dot.
It is getting very close now, so yes the Forrest "team",
which includes anybody who wants to help, needs to start
getting our thinking caps on. That is for a separate
email thread soon.
> BTW, thank you for your attention on this issue. I look forward to
> resolving it, and with the help of you and the rest of the Forrest Team
> it doesn't seem like too much of a challenge!
>
> Web Maestro Clay
>
> p.s. I hope you don't mind that I married this issue with our previous
> issue on the dev list, but I figured I'd like to complete 'both'
> issues, and I'd rather hash this out on the dev@ list. It's my feeling
> that this is more dev-related anyway.
They don't seem related and it might draw attention away
from your actual build issues. Anyway, yes it is a good idea
to bring such threads over to the dev list. We do not want to
confuse users.
--
David Crossley
Re: xml-fop Build Failed
Posted by Clay Leeds <cl...@medata.com>.
On Oct 19, 2004, at 5:42 PM, David Crossley wrote:
> Clay Leeds wrote:
>> And now onto the response to your question.
>> ========================
>>
>> Instructions for updating xml-fop are on the Development tab's > Doc
>> Mgmt page [1]:
>> 1. Developer commits code to FOP repository
>> 2. Forrestbot "refresh". Automatically done every six hours.
>> Can be manually refreshed by authorized users at the
>> Forrestbot Web Interface.
>> 3. Forrestbot "publish". Always done manually at the
>> Forrestbot Web Interface.
>> 4. Automatic Live Site Update every six hours (midnight, 6am,
>> noon, 6pm Pacific time).
>
> I see. I wondered that a while ago, but you must have
> missed my question. I would suggest going to the manual
> build method that i described below for "xml-commons".
> It could be a long time before we can update the Forrestbot.
> We are waiting for one of the new Apache servers to come
> on-line.
Glad you asked the question as it appears we (the FOP Team) need to
either update our Doc Mgmt page, or temporarily 'double' update the web
site manually: 1) vi over SSH updating of HTML; 2) xdocs/*.xml.
Speaking of which, it sounds like Apache Forrest-0.6 is not yet live on
the server which serves <http://xml.apache.org/fop/>.
I don't understand what you meant when you said 'I wondered that a
while ago, but you must have missed my question.' Wasn't your question:
David Crossley wrote:
> Can you tell me how you currently update the FOP website.
I thought I answered this question when I said:
> With the exception of a couple of 'vi over SSH' changes to the LIVE
> site (xml-site/targets/fop/), the FOP docs have not been updated
> recently. We are in dire need of update.
In other words, until I get the xdocs/ back in the running, we aren't
updating our site unless I manually edit the files using vi. If
necessary, I could do your suggestion below, although I'll have to
reapply any changes to the 'working' xdocs/*.xml files (which isn't
really that big a deal).
Was there another question you had that I didn't answer? :-)
David Crossley wrote:
>>> For most websites it is entirely a manual operation.
>>> For example at "XML Commons" we do this:
>>> *) Edit the source at
>>> cvs://xml-commons/src/documentation/content/xdocs/*.xml
>>> *) Generate the site locally with whatever Forrest that
>>> the project has decided to use.
>>> *) Commit the HTML/PDF result to cvs://xml-site/targets/commons/
>>> *) Commit the edited source to
>>> cvs://xml-commons/src/documentation/content/xdocs/
>>>
>>> To publish the result, we have an automated cron job to
>>> do 'cvs update'. Otherwise we do it manually with
>>> ssh cvs.apache.org
>>> cd /www/xml.apache.org/commons
>>> cvs -q update -dP
>>
>> The Doc Mgmt page [1] has a forrestbot interface which makes
>> PUBLISHing
>> fairly simple.
>
> Yes, it will be wonderful when we finally get a forrestbot at ASF.
> --
> David Crossley
Yes that will. What is prohibiting that? Is there anything I
(we--either the FOP Team or someone else from the Forrest Team) can do
to help?
BTW, thank you for your attention on this issue. I look forward to
resolving it, and with the help of you and the rest of the Forrest Team
it doesn't seem like too much of a challenge!
Web Maestro Clay
p.s. I hope you don't mind that I married this issue with our previous
issue on the dev list, but I figured I'd like to complete 'both'
issues, and I'd rather hash this out on the dev@ list. It's my feeling
that this is more dev-related anyway.
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Build Failed
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
>
> And now onto the response to your question.
> ========================
>
> Instructions for updating xml-fop are on the Development tab's > Doc
> Mgmt page [1]:
> 1. Developer commits code to FOP repository
> 2. Forrestbot "refresh". Automatically done every six hours.
> Can be manually refreshed by authorized users at the
> Forrestbot Web Interface.
> 3. Forrestbot "publish". Always done manually at the
> Forrestbot Web Interface.
> 4. Automatic Live Site Update every six hours (midnight, 6am,
> noon, 6pm Pacific time).
I see. I wondered that a while ago, but you must have
missed my question. I would suggest going to the manual
build method that i described below for "xml-commons".
It could be a long time before we can update the Forrestbot.
We are waiting for one of the new Apache servers to come
on-line.
> MY CURRENT PLAN TO UPDATE xml-fop
> =================================
> 1. do a fresh cvs checkout of xml-fop
> 2. extract the xml-fop_new.zip file[2] that the Forrest Team helped with
> (NOTE: see [3] for thread, but [2] is the actual xml-fop*.zip file
> for which Dave had a BUILD SUCCESSFUL[4] later in the thread).
> 4. follow Dave's excellent instructions[4]
> 5. replace the xdocs/*.xml files (and sub-dir's files) with
> files extracted from xml-fop_new.zip
> 6. manually generate some PDFs as explained in [4]
> 7. /forrest/
> 8. I should then receive a BUILD SUCCESSFUL
>
> Unfortunately, I'm getting a java error. I admit that I haven't done
> step 6 yet, but I can live with a BUILD FAILED error if the only errors
> are something I know how to fix.
>
> > For most websites it is entirely a manual operation.
> > For example at "XML Commons" we do this:
> > *) Edit the source at
> > cvs://xml-commons/src/documentation/content/xdocs/*.xml
> > *) Generate the site locally with whatever Forrest that
> > the project has decided to use.
> > *) Commit the HTML/PDF result to cvs://xml-site/targets/commons/
> > *) Commit the edited source to
> > cvs://xml-commons/src/documentation/content/xdocs/
> >
> > To publish the result, we have an automated cron job to
> > do 'cvs update'. Otherwise we do it manually with
> > ssh cvs.apache.org
> > cd /www/xml.apache.org/commons
> > cvs -q update -dP
>
> The Doc Mgmt page [1] has a forrestbot interface which makes PUBLISHing
> fairly simple.
Yes, it will be wonderful when we finally get a forrestbot at ASF.
--
David Crossley
Re: xml-fop Build Failed
Posted by Clay Leeds <cl...@medata.com>.
NOTE: This discussion was moved from a thread on
user@forrest.apache.org, since similar threads existed on both lists:
http://issues.apache.org/eyebrowse/ReadMsg?
listName=user@forrest.apache.org&msgNo=807
Discussion continues below...
On Oct 19, 2004, at 12:21 AM, David Crossley wrote:
> Clay Leeds wrote:
>> David Crossley wrote:
>>> Clay Leeds wrote:
>>>> As you know. I am the "Web Maestro" for the Apache FOP web site. I
>>>> intend to update the http://xml.apache.org/fop/ web site soon after
>>>> xml.apache.org's forrestbot is updated to Apache Forrest 0.6.
>>>
>>> This bit confuses me. I did not realise that any "forrestbot"
>>> new or old is assisting yet with the xml.apache.org site.
>>> We do want it to.
>>
>> Actually, I really just want to make certain that when I commit files
>> for 'xml-fop' via cvs.apache.org, Forrest-0.6 is used to process my
>> xml-fop/src/documentation/content/xdocs/*.xml
>
> I am still confused. Can you tell me how you currently update
> the FOP website.
With the exception of a couple of 'vi over SSH' changes to the LIVE
site (xml-site/targets/fop/), the FOP docs have not been updated
recently. We are in dire need of update.
A LITTLE BACKGROUND INFO
========================
(skip if this bores you ;-)) I was considered for FOP committer access,
not for my heretofore non-existent Java coding abilities, but rather
for my commitment to helping others on the mailing list, and more
importantly, my numerous comments on improving web site documentation.
Unfortunately, when I became a committer I discovered that xml-fop's
xdocs would not BUILD SUCCESSFULLY. I embarked on a campaign to improve
the situation only to find that Forrest was 'about' to release 0.6
(this was months ago). I updated xml-fop to meet 0.6 a few months ago.
My hope is that once the xml-fop docs are in a state where I don't have
to stress that they still aren't updated, I will be able to focus on
contributing actual Java-code improvements.
And now onto the response to your question.
========================
Instructions for updating xml-fop are on the Development tab's > Doc
Mgmt page [1]:
1. Developer commits code to FOP repository
2. Forrestbot "refresh". Automatically done every six hours.
Can be manually refreshed by authorized users at the
Forrestbot Web Interface.
3. Forrestbot "publish". Always done manually at the
Forrestbot Web Interface.
4. Automatic Live Site Update every six hours (midnight, 6am,
noon, 6pm Pacific time).
MY CURRENT PLAN TO UPDATE xml-fop
=================================
1. do a fresh cvs checkout of xml-fop
2. extract the xml-fop_new.zip file[2] that the Forrest Team helped with
(NOTE: see [3] for thread, but [2] is the actual xml-fop*.zip file
for which Dave had a BUILD SUCCESSFUL[4] later in the thread).
4. follow Dave's excellent instructions[4]
5. replace the xdocs/*.xml files (and sub-dir's files) with
files extracted from xml-fop_new.zip
6. manually generate some PDFs as explained in [4]
7. /forrest/
8. I should then receive a BUILD SUCCESSFUL
Unfortunately, I'm getting a java error. I admit that I haven't done
step 6 yet, but I can live with a BUILD FAILED error if the only errors
are something I know how to fix.
> For most websites it is entirely a manual operation.
> For example at "XML Commons" we do this:
> *) Edit the source at
> cvs://xml-commons/src/documentation/content/xdocs/*.xml
> *) Generate the site locally with whatever Forrest that
> the project has decided to use.
> *) Commit the HTML/PDF result to cvs://xml-site/targets/commons/
> *) Commit the edited source to
> cvs://xml-commons/src/documentation/content/xdocs/
>
> To publish the result, we have an automated cron job to
> do 'cvs update'. Otherwise we do it manually with
> ssh cvs.apache.org
> cd /www/xml.apache.org/commons
> cvs -q update -dP
The Doc Mgmt page [1] has a forrestbot interface which makes PUBLISHing
fairly simple.
>> Also, is there a reason why the first meta tag in all caps? Wouldn't
>> that violate xhtml rules, which, I believe specify all tags should be
>> lowercase (I realize it says HTML 4.01 Transitional... or are we
>> fishing for a PATCH? ;-))?
>
> No, i think that if we had used an XHTML serializer in the
> forrest sitemap then all would be lowercase. At the moment
> we are still serializing to HTML so it doesn't matter.
Sounds good! Thanks!
> --
> David Crossley
I hope this clears things up a bit. As you can see, I'm eager to update
the FOP web site!
[1]
http://xml.apache.org/fop/dev/doc.html
[2]
http://homepage.mac.com/webmaestro/xml-fop/xml-fop_new.zip
[3]
http://marc.theaimsgroup.com/?l=forrest-dev&m=109039040919791&w=2
[4]
http://marc.theaimsgroup.com/?l=forrest-dev&m=109157457703573&w=2
[5]
http://issues.apache.org/eyebrowse/ReadMsg?
listName=dev@forrest.apache.org&msgNo=14528
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Build Failed
Posted by Clay Leeds <cl...@medata.com>.
On Oct 20, 2004, at 10:44 AM, Juan Jose Pablos wrote:
> Clay Leeds wrote:
>>> So
>>> 1) I will upgrade fop-0.20.5.jar and batik-all-1.5.1.jar from the
>>> cocoon-2.2.0-dev tree in the next hour unless someone has any
>>> objection.
>> Will I need to do that as well?
>
> Well you need to get the latest copy from forrest svn.
I'll get the latest forrest from svn. Thanks!
>>> 2) Clay
>>> Please apply this patch and upgrade to the svn version
>> Wouldn't it be the other way around (/svn up/ and then apply the
>> PATCH?)?
>
> This patch is for the xml-fop cvs.
ok. I was confused, because you said apply this patch and upgrade to
the svn version... as you indicate, xml-fop uses cvs, and forrest uses
svn... All these projects make it confusing to me to know what to fix
(although the fact that it's called fix4fop.diff should've been a
clue!)
>>> (you need to create an empty site.xml for this to work.
>> That seems strange, as my site.xml file has tons in it. Forgive my
>> question, but what is the purpose of an empty site.xml file?
>
> ¿?
> Are we talking about the same site?
> I did check the problem on a copy of the xml-fop. Are we usinng the
> same one?
Nope. I've practically given up on the xml-fop xdocs/*.xml (and subdir
*.xml files). My plan (which may be a bad plan!) was to start from the
xml-fop_new.zip file referenced in this POST[1] (link [2] from that
post).
Obviously, I would rather work with the xml-fop cvs files, but Dave
Brondsema's instructions dealt with link [2] from that post. I suppose
that those instructions might be able to work from xml-fop cvs, though.
If so (or I could get new instructions which work with xml-fop cvs),
that would be great and would save me a step or two!
Oh what a tangled web we weave... when we try and figure out all this
stuff and it takes months to learn!
>>> Cheers,
>>> Cheche
>>> <fix4fop.diff>
[1]
http://issues.apache.org/eyebrowse/ReadMsg?
listName=dev@forrest.apache.org&msgNo=14532
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Build Failed
Posted by Juan Jose Pablos <ch...@apache.org>.
Clay Leeds wrote:
>> So
>> 1) I will upgrade fop-0.20.5.jar and batik-all-1.5.1.jar from the
>> cocoon-2.2.0-dev tree in the next hour unless someone has any objection.
>
>
> Will I need to do that as well?
>
Well you need to get the latest copy from forrest svn.
>> 2) Clay
>> Please apply this patch and upgrade to the svn version
>
>
> Wouldn't it be the other way around (/svn up/ and then apply the PATCH?)?
>
This patch is for the xml-fop cvs.
>> (you need to create an empty site.xml for this to work.
>
>
> That seems strange, as my site.xml file has tons in it. Forgive my
> question, but what is the purpose of an empty site.xml file?
¿?
Are we talking about the same site?
I did check the problem on a copy of the xml-fop. Are we usinng the same
one?
Cheers,
Cheche
>
>> Cheers,
>> Cheche
>> <fix4fop.diff>
>
>
> Web Maestro Clay
Re: xml-fop Build Failed
Posted by Clay Leeds <cl...@medata.com>.
On Oct 20, 2004, at 12:47 AM, Juan Jose Pablos wrote:
> I have managed to work around this java error. I do not why but the
> fop-0.20.5.jar library on the cocoon 2.2.0-dev tree is diferent to
> the one in the forrest distribution.
strange...
> So
> 1) I will upgrade fop-0.20.5.jar and batik-all-1.5.1.jar from the
> cocoon-2.2.0-dev tree in the next hour unless someone has any
> objection.
Will I need to do that as well?
> 2) Clay
> Please apply this patch and upgrade to the svn version
Wouldn't it be the other way around (/svn up/ and then apply the
PATCH?)?
> (you need to create an empty site.xml for this to work.
That seems strange, as my site.xml file has tons in it. Forgive my
question, but what is the purpose of an empty site.xml file?
> Cheers,
> Cheche
> <fix4fop.diff>
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> David Crossley wrote:
> > Clay Leeds wrote:
> >> Here's what the Compliance Page currently looks like:
> >>
> >> http://homepage.mac.com/webmaestro/xml-fop/compliance.html
> >>
> >> Here's what I want the Compliance Page to look like:
> >>
> >> http://xml.apache.org/fop/compliance.html
> >
> > Is it intentional that you are using the old
> > deprecated crust skin (which equals old krysalis-site)?
> >
> > If not, then you should switch to using "pelt"
> > which i expect would enable you to have CSS control
> > over the colours in your compliance table.
>
> Heh... I kept using 'crust' because I liked the color better. I've
> never really liked the forrest 'dark' blue much.
You have full control over the colours.
They are defined in skinconf.xml
Just uncomment which set of default <color>
elements that you want to use and then tweak
each <color> if you want a different colour.
> Of course, I kept
> seeing seeing that 'using deprecated krysalis-site warning' and figured
> I'd have to fix that some time, since it annoyed me.
See forrest.apache.org/docs/skins.html
It is deprecated a while ago.
> Thanks! I'll
> update the colors with CSS.
You will probably need to update your
compliance2document.xsl to add certain "class"
attributes to the <td> elements of your compliance
table. Then use CSS to colour each class of table cells.
--
David Crossley
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Clay Leeds <cl...@medata.com>.
On Nov 7, 2004, at 5:25 PM, David Crossley wrote:
> Clay Leeds wrote:
>> Here's what the Compliance Page currently looks like:
>>
>> http://homepage.mac.com/webmaestro/xml-fop/compliance.html
>>
>> Here's what I want the Compliance Page to look like:
>>
>> http://xml.apache.org/fop/compliance.html
>
> Is it intentional that you are using the old
> deprecated crust skin (which equals old krysalis-site)?
>
> If not, then you should switch to using "pelt"
> which i expect would enable you to have CSS control
> over the colours in your compliance table.
Heh... I kept using 'crust' because I liked the color better. I've
never really liked the forrest 'dark' blue much. Of course, I kept
seeing seeing that 'using deprecated krysalis-site warning' and figured
I'd have to fix that some time, since it annoyed me. Thanks! I'll
update the colors with CSS.
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
>
> Here's what the Compliance Page currently looks like:
>
> http://homepage.mac.com/webmaestro/xml-fop/compliance.html
>
> Here's what I want the Compliance Page to look like:
>
> http://xml.apache.org/fop/compliance.html
Is it intentional that you are using the old
deprecated crust skin (which equals old krysalis-site)?
If not, then you should switch to using "pelt"
which i expect would enable you to have CSS control
over the colours in your compliance table.
--
David Crossley
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Clay Leeds <cl...@medata.com>.
On Nov 7, 2004, at 9:59 PM, Dave Brondsema wrote:
> Clay Leeds wrote:
>> I was unsuccessful at applying the PATCH. I tried running the PATCH:
>> cd xml-fop/
>> patch -p0 "/Users/Shared/_WebDLs/_repos/fop-patch/a-jump.patch"
>> ...after about 10 minutes of no apparent change, I did a [Control]+C.
>> Perhaps I don't have the hang of this PATCH thing after all. I did
>> copy the files catalog.xcat & catalog.fop.xcat to
>> src/documentation/resources/schema/ though. I also committed the
>> CatalogManager.properties file.
>
> patch reads from standard input, so you have to do:
>
> patch -p0 < filename
>
> That redirects the contents of filename into the standard input of
> 'patch'. Same as `cat filename | patch -p0`. Without any input it
> will just sit and wait for some, which is what happened to you when
> you put the filename as a parameter to patch.
I guess it helps to read the man again. D'oh! Thanks!
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Dave Brondsema <da...@brondsema.net>.
Clay Leeds wrote:
> On Nov 7, 2004, at 2:14 PM, Juan Jose Pablos wrote:
>
>> Clay Leeds wrote:
>>
>>> I'm sorry, could you zip those files and send again (or attach to a
>>> JIRA, or send to me privately or something)? It looks like you sent
>>> catalog.xcat and resources.xml(?), but those 'files' were embedded in
>>> the message, and were severely modified by SpamAssassin so it's hard
>>> to tell.
>>
>>
>> sure.
>
>
> I was unsuccessful at applying the PATCH. I tried running the PATCH:
>
> cd xml-fop/
> patch -p0 "/Users/Shared/_WebDLs/_repos/fop-patch/a-jump.patch"
>
> ...after about 10 minutes of no apparent change, I did a [Control]+C.
> Perhaps I don't have the hang of this PATCH thing after all. I did copy
> the files catalog.xcat & catalog.fop.xcat to
> src/documentation/resources/schema/ though. I also committed the
> CatalogManager.properties file.
>
patch reads from standard input, so you have to do:
patch -p0 < filename
That redirects the contents of filename into the standard input of
'patch'. Same as `cat filename | patch -p0`. Without any input it
will just sit and wait for some, which is what happened to you when you
put the filename as a parameter to patch.
--
Dave Brondsema : dave@brondsema.net
http://www.splike.com : programming
http://csx.calvin.edu : student org
http://www.brondsema.net : personal
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Clay Leeds <cl...@medata.com>.
On Nov 7, 2004, at 2:14 PM, Juan Jose Pablos wrote:
> Clay Leeds wrote:
>> I'm sorry, could you zip those files and send again (or attach to a
>> JIRA, or send to me privately or something)? It looks like you sent
>> catalog.xcat and resources.xml(?), but those 'files' were embedded in
>> the message, and were severely modified by SpamAssassin so it's hard
>> to tell.
>
> sure.
I was unsuccessful at applying the PATCH. I tried running the PATCH:
cd xml-fop/
patch -p0 "/Users/Shared/_WebDLs/_repos/fop-patch/a-jump.patch"
...after about 10 minutes of no apparent change, I did a [Control]+C.
Perhaps I don't have the hang of this PATCH thing after all. I did copy
the files catalog.xcat & catalog.fop.xcat to
src/documentation/resources/schema/ though. I also committed the
CatalogManager.properties file.
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Juan Jose Pablos <ch...@che-che.com>.
Clay Leeds wrote:
> I'm sorry, could you zip those files and send again (or attach to a
> JIRA, or send to me privately or something)? It looks like you sent
> catalog.xcat and resources.xml(?), but those 'files' were embedded in
> the message, and were severely modified by SpamAssassin so it's hard to
> tell.
>
sure.
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Clay Leeds <cl...@medata.com>.
On Nov 7, 2004, at 12:40 PM, Juan Jose Pablos wrote:
> Clay Leeds wrote:
>> Great idea, Cheche! I've committed the following files:
>> - forrest.properties
>> - src/documentation/sitemap.xmap
>> - src/documentation/skinconf.xml
>> - src/documentation/content/xdocs/compliance.xml
>> - src/documentation/content/xdocs/site.xml
>
> Update cvs with these two files. That would resolve the validation
> errors.
I'm sorry, could you zip those files and send again (or attach to a
JIRA, or send to me privately or something)? It looks like you sent
catalog.xcat and resources.xml(?), but those 'files' were embedded in
the message, and were severely modified by SpamAssassin so it's hard to
tell.
>> Here's what the Compliance Page currently looks like:
>> http://homepage.mac.com/webmaestro/xml-fop/compliance.html
>> Here's what I want the Compliance Page to look like:
>> http://xml.apache.org/fop/compliance.html
>
> I will have a look later...
>
> Cheers,
> Cheche
Thanks!
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Clay Leeds <cl...@medata.com>.
On Nov 7, 2004, at 4:58 PM, David Crossley wrote:
> Juan Jose Pablos wrote:
>>>>> Great idea, Cheche! I've committed the following files:
>>>>> - forrest.properties
>>>>> - src/documentation/sitemap.xmap
>>>>> - src/documentation/skinconf.xml
>>>>> - src/documentation/content/xdocs/compliance.xml
>>>>> - src/documentation/content/xdocs/site.xml
>>
>> Please
>> Create a directory called:
>> src/documentation/classes
>> And add this file.
>
> In past discussions, we already fixed this part with
> Clay's local project. I think that he might have forgotten
> to also add classes/CatalogManager.properties to the xml-fop CVS.
<sheepishly>
That is correct David. I apologize *profusely* Cheche and David. I'm
using a CVS GUI for managing my changes (MacCVSClient X), and I missed
the new files & directory. So, I just added Cheche's
src/documentation/classes/CatalogManger.properties,
src/documentation/resources/schema/catalog.fop.xcat, &
src/documentation/resources/schema/catalog.xcat. Thanks again, Cheche.
</sheepishly>
Also, I just removed all of the book.xml files throughout (except for
DnI/ which is newer, and I need to confirm whether it is forrest-based
or extra).
> Yes, he does need to also change his old CatalogManager.properties
> to point to the new "catalog.xcat" rather than "catalog".
I've checked those files in (see above). To reiterate, I was getting
errors for the SVG & FO transformations, but I wasn't receiving any
errors for the compliance.xml or any other pages, running /forrest/
from the command line. Compliance.html would provide no errors when I
ran /forrest/ or when I did /forrest run/. It would show up without the
extra links or Citation links.
> Clay, the verbosity setting in Ceche's example is set
> to "10" to show you the resolver messages and make
> sure that everything is working for you. When satisfied,
> switch is back to level "1".
Erm... I don't understand. The verbosity setting for what?
>> There is other errors, we will look at them tomorrow
>
> I don't see any errors. I can see the new compliance.html
>
> --David
Again, I apologize for the mix-up. I have *not* successfully applied
Cheche's PATCH, although I have created the files by hand and committed
them (see reply to Cheche's msg).
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by David Crossley <cr...@apache.org>.
Juan Jose Pablos wrote:
> >>>Great idea, Cheche! I've committed the following files:
> >>>- forrest.properties
> >>>- src/documentation/sitemap.xmap
> >>>- src/documentation/skinconf.xml
> >>>- src/documentation/content/xdocs/compliance.xml
> >>>- src/documentation/content/xdocs/site.xml
> >>>
> Please
> Create a directory called:
> src/documentation/classes
> And add this file.
In past discussions, we already fixed this part with
Clay's local project. I think that he might have forgotten
to also add classes/CatalogManager.properties to the xml-fop CVS.
Yes, he does need to also change his old CatalogManager.properties
to point to the new "catalog.xcat" rather than "catalog".
Clay, the verbosity setting in Ceche's example is set
to "10" to show you the resolver messages and make
sure that everything is working for you. When satisfied,
switch is back to level "1".
> There is other errors, we will look at them tomorrow
I don't see any errors. I can see the new compliance.html
--David
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Juan Jose Pablos <ch...@che-che.com>.
Clay Leeds wrote:
> Cheche,
>
> When you send files like this, I get them all in the body of your POST.
> They are not attached, and as such, I have trouble:
> - knowing where one ends and another begins (although I can figure that
> out)
> - what to call the file...
>
> I *think* this file is CatalogManager.properties... And now I see where
> verbosity is set to 10...
>
> BTW, The next part of the message is exactly as it came to me (although
> it is quoted). I thought Cheche, you would like to see how I see your
> attachments.
>
Ok, I will put it on a bug report.
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Clay Leeds <cl...@medata.com>.
Cheche,
When you send files like this, I get them all in the body of your POST.
They are not attached, and as such, I have trouble:
- knowing where one ends and another begins (although I can figure that
out)
- what to call the file...
I *think* this file is CatalogManager.properties... And now I see where
verbosity is set to 10...
BTW, The next part of the message is exactly as it came to me (although
it is quoted). I thought Cheche, you would like to see how I see your
attachments.
On Nov 7, 2004, at 4:45 PM, Juan Jose Pablos wrote:
>>>> Great idea, Cheche! I've committed the following files:
>>>> - forrest.properties
>>>> - src/documentation/sitemap.xmap
>>>> - src/documentation/skinconf.xml
>>>> - src/documentation/content/xdocs/compliance.xml
>>>> - src/documentation/content/xdocs/site.xml
>>>>
> Please
> Create a directory called:
> src/documentation/classes
> And add this file.
>
> There is other errors, we will look at them tomorrow
>
>
> Cheers,
> Cheche
> # Copyright 2002-2004 The Apache Software Foundation
> #
> # Licensed under the Apache License, Version 2.0 (the "License");
> # you may not use this file except in compliance with the License.
> # You may obtain a copy of the License at
> #
> # http://www.apache.org/licenses/LICENSE-2.0
> #
> # Unless required by applicable law or agreed to in writing, software
> # distributed under the License is distributed on an "AS IS" BASIS,
> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> implied.
> # See the License for the specific language governing permissions and
> # limitations under the License.
>
> #======================================================================
> =
> # CatalogManager.properties for Catalog Entity Resolver.
> #
> # This is the default properties file for your project.
> # This facilitates local configuration of application-specific
> catalogs.
> # If you have defined any local catalogs, then they will be loaded
> # before Forrest's core catalogs.
> #
> # See the Apache Forrest documentation:
> # http://forrest.apache.org/docs/your-project.html
> # http://forrest.apache.org/docs/validation.html
>
> # verbosity:
> # The level of messages for status/debug (messages go to standard
> output).
> # The setting here is for your own local catalogs.
> # The verbosity of Forrest's core catalogs is controlled via
> # forrestcore/src/core/context/WEB-INF/cocoon.xconf
> #
> # The following messages are provided ...
> # 0 = none
> # 1 = ? (... not sure yet)
> # 2 = 1+, Loading catalog, Resolved public, Resolved system
> # 3 = 2+, Catalog does not exist, resolvePublic, resolveSystem
> # 10 = 3+, List all catalog entries when loading a catalog
> # (Cocoon also logs the "Resolved public" messages.)
> verbosity=10
>
> # catalogs ... list of additional catalogs to load
> # (Note that Apache Forrest will automatically load its own default
> catalog
> # from src/core/context/resources/schema/catalog.xcat)
> # use full pathnames
> # pathname separator is always semi-colon (;) regardless of operating
> system
> # directory separator is always slash (/) regardless of operating
> system
> #
> #catalogs=/home/me/forrest/my-site/src/documentation/resources/schema/
> catalog.xcat
> catalogs=../resources/schema/catalog.xcat
> relative-catalogs=false
>
>
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Juan Jose Pablos <ch...@che-che.com>.
>>>Great idea, Cheche! I've committed the following files:
>>>- forrest.properties
>>>- src/documentation/sitemap.xmap
>>>- src/documentation/skinconf.xml
>>>- src/documentation/content/xdocs/compliance.xml
>>>- src/documentation/content/xdocs/site.xml
>>>
Please
Create a directory called:
src/documentation/classes
And add this file.
There is other errors, we will look at them tomorrow
Cheers,
Cheche
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Clay Leeds <cl...@medata.com>.
On Nov 7, 2004, at 3:35 PM, David Crossley wrote:
> Juan Jose Pablos wrote:
>> Clay Leeds wrote:
>>> Great idea, Cheche! I've committed the following files:
>>> - forrest.properties
>>> - src/documentation/sitemap.xmap
>>> - src/documentation/skinconf.xml
>>> - src/documentation/content/xdocs/compliance.xml
>>> - src/documentation/content/xdocs/site.xml
>>
>> Update cvs with these two files. That would resolve the validation
>> errors.
>
> Just to explain a little bit. There has already been
> a lot of misunderstanding about this topic.
Much of which is my fault. It's been a challenge working through the
errors experienced when attempting to run /forrest/ for xml-fop/. I
actually started working to get the FOP site up and running back in
February[1]. I had some successes (getting BUILD SUCCESSFUL using
book.xml throughout), but one of my main goals was to get the Whole
site PDF going (FOP should have Whole Site PDF if any site has it! ;-))
> Clay already had a plain-text "catalog" file that worked
> in his project at documentation/resources/schema/catalog
Yes. Unfortunately, I hadn't committed it until this evening. (Sorry!
More apologies in another letter!)...
> You have provided him with an xml-based catalog instead.
> Either format will be okay.
>
> --
> David Crossley
Thank you all again, for your time!
[1]
http://issues.apache.org/eyebrowse/ReadMsg?
listName=dev@forrest.apache.org&msgNo=10441
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Clay Leeds <cl...@medata.com>.
On Nov 7, 2004, at 4:14 PM, Juan Jose Pablos wrote:
> I saw that, but that file did not stop these errors. Only when I
> created the local xml-based catalog, I could validate this xml file.
>
> I think that maybe it is on our site.
>
> After adding this xml-based catalog, Forrest report this error:
>
> X [0] compliance.html
> BROKEN:
> /home/cheche/xml/xml-fop/src/documentation/content/xdocs/compliance-
> v10.dtd (No such file or directory)
>
> The only way I found to avoid this is adding the compliance public
> identifier to forrest catalog.
>
> I need to find a way to add {project.home}/catalog.xcat to
> catalog.forrest.xcat
>
> WDYT?
FWIW, I just got this after doing /forrest/ from the currently
committed files.
* [82/77] [1/46] 2.076s 54.0Kb compliance.html
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Clay Leeds <cl...@medata.com>.
On Nov 13, 2004, at 8:22 AM, Ross Gardler wrote:
> David Crossley wrote:
>> Clay Leeds wrote:
>>> FWIW, I was able to resolve the problem with missing links on the
>>> FOP Compliance page by using Xalan.sh to transform compliance.xml
>>> using compliance2html.xsl (as explained here[1]). Unfortunately, I
>>> can't seem to get the page skinned via forrest. The '.ihtml'
>>> solution is deprecated, and placing a 'compliance.html' in
>>> src/documentation/content/ does not result in a skin
>>> compliance.html.
> <snip/>
>> Note the warning on the 'forrest seed site' sample
>> for ihtml about the need for <h*> level headings
>> (though i think Ross fixed that recently in head).
>
> It is fixed in Head, but the symptoms of this problem were different
> to those described by Clay, it resulted in a skinned page, but with no
> content.
Thanks for the update. 'We' probably should include that fix in
whatever is going into forrest-0.6.1
> Clay, what you need to do is put your .html files in the xdocs folder.
> Anything outside of xdocs is treated as raw content and so is not
> skinned, anything inside is processed and skinned accordingly.
If I get the time, I'll provide a PATCH for the documentation that
explains all this. I don't think that is well explained anywhere
(although I could be wrong).
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Ross Gardler <rg...@apache.org>.
David Crossley wrote:
> Clay Leeds wrote:
>
>> FWIW, I was able to resolve the problem with missing links on the FOP
>> Compliance page by using Xalan.sh to transform compliance.xml using
>> compliance2html.xsl (as explained here[1]). Unfortunately, I can't
>> seem to get the page skinned via forrest. The '.ihtml' solution is
>> deprecated, and placing a 'compliance.html' in
>> src/documentation/content/ does not result in a skin compliance.html.
<snip/>
> Note the warning on the 'forrest seed site' sample
> for ihtml about the need for <h*> level headings
> (though i think Ross fixed that recently in head).
It is fixed in Head, but the symptoms of this problem were different to
those described by Clay, it resulted in a skinned page, but with no content.
Clay, what you need to do is put your .html files in the xdocs folder.
Anything outside of xdocs is treated as raw content and so is not
skinned, anything inside is processed and skinned accordingly.
Ross
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Clay Leeds <cl...@medata.com>.
On Nov 13, 2004, at 11:47 AM, Clay Leeds wrote:
> On Nov 12, 2004, at 4:52 PM, David Crossley wrote:
>> The "ihtml" functionality is still there. It is just
>> that you now use the .html extension, rather than
>> the .ihtml extension. In fact both should work, we do
>> still have a .ihtml extension file in our core forrest
>> docs.
>
> Good to know.
The problems with this file have gotten considerably worse. I now have
*every* file in xdocs/ generating an error (but skin files work fine):
* [33/51] [0/0] 0.907s 390b
skin/images/rc-t-r-15-1body-2menu-3menu.png
* [34/50] [0/0] 0.331s 207b
skin/images/rc-t-r-5-1header-2tab-unselected-3tab-unselected.png
X [0] index.html BROKEN:
/Users/Shared/_WebDLs/_repos/xml-fop/src/documentation/raw.xmap (No
such file or directory)
>> Note the warning on the 'forrest seed site' sample
>> for ihtml about the need for <h*> level headings
>> (though i think Ross fixed that recently in head).
>>
>> --David
>
> That would be good to put on the web site. I'm pretty busy this
> weekend or I'd do it myself.
Haven't found time yet to do something on presenting a PATCH adding
this info to Forrest docs.
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Clay Leeds <cl...@medata.com>.
On Nov 12, 2004, at 4:52 PM, David Crossley wrote:
> Clay Leeds wrote:
>> FWIW, I was able to resolve the problem with missing links on the FOP
>> Compliance page by using Xalan.sh to transform compliance.xml using
>> compliance2html.xsl (as explained here[1]). Unfortunately, I can't
>> seem to get the page skinned via forrest. The '.ihtml' solution is
>> deprecated, and placing a 'compliance.html' in
>> src/documentation/content/ does not result in a skin compliance.html.
>
> The "ihtml" functionality is still there. It is just
> that you now use the .html extension, rather than
> the .ihtml extension. In fact both should work, we do
> still have a .ihtml extension file in our core forrest
> docs.
Good to know.
> Note the warning on the 'forrest seed site' sample
> for ihtml about the need for <h*> level headings
> (though i think Ross fixed that recently in head).
>
> --David
That would be good to put on the web site. I'm pretty busy this weekend
or I'd do it myself.
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by David Crossley <dc...@indexgeo.com.au>.
Clay Leeds wrote:
> FWIW, I was able to resolve the problem with missing links on the FOP
> Compliance page by using Xalan.sh to transform compliance.xml using
> compliance2html.xsl (as explained here[1]). Unfortunately, I can't seem
> to get the page skinned via forrest. The '.ihtml' solution is
> deprecated, and placing a 'compliance.html' in
> src/documentation/content/ does not result in a skin compliance.html.
The "ihtml" functionality is still there. It is just
that you now use the .html extension, rather than
the .ihtml extension. In fact both should work, we do
still have a .ihtml extension file in our core forrest
docs.
Note the warning on the 'forrest seed site' sample
for ihtml about the need for <h*> level headings
(though i think Ross fixed that recently in head).
--David
> I'm open to ideas for fixing this 'workaround'.
>
> BTW, I resolved the issue with the missing bgcolor of @class="yes" not
> working (I removed <!-- & --> from inside the <style> tags. This
> effectively cancelled the following style '.yes' but did not affect
> .'no' or '.partial', and committed the change to
> src/documentation/resources/schema/compliance2html.xsl):
>
>> <style>
>> <--
>> .yes { background-color: #99FF99 }
>> .no { background-color: #FF9999 }
>> .partial { background-color: #FFFFCC }
>> .category { /*background-color: #CFDCED;*/
>> font-size: 1.2em }
>> -->
>> </style>
>
>
> [1]
> http://issues.apache.org/eyebrowse/ReadMsg?
> listName=dev@forrest.apache.org&msgNo=15405
>
> Web Maestro Clay
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Clay Leeds <cl...@medata.com>.
FWIW, I was able to resolve the problem with missing links on the FOP
Compliance page by using Xalan.sh to transform compliance.xml using
compliance2html.xsl (as explained here[1]). Unfortunately, I can't seem
to get the page skinned via forrest. The '.ihtml' solution is
deprecated, and placing a 'compliance.html' in
src/documentation/content/ does not result in a skin compliance.html.
I'm open to ideas for fixing this 'workaround'.
BTW, I resolved the issue with the missing bgcolor of @class="yes" not
working (I removed <!-- & --> from inside the <style> tags. This
effectively cancelled the following style '.yes' but did not affect
.'no' or '.partial', and committed the change to
src/documentation/resources/schema/compliance2html.xsl):
> <style>
> <--
> .yes { background-color: #99FF99 }
> .no { background-color: #FF9999 }
> .partial { background-color: #FFFFCC }
> .category { /*background-color: #CFDCED;*/
> font-size: 1.2em }
> -->
> </style>
[1]
http://issues.apache.org/eyebrowse/ReadMsg?
listName=dev@forrest.apache.org&msgNo=15405
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Clay Leeds <cl...@medata.com>.
I've spent a fair amount of time playing around with the compliance*
files over the last few days, and although I haven't gotten it to work
as it should, I may have a suitable workaround.
xml-fop includes the following 'compliance' files:
[clay@Clay-Leeds-Computer xml-fop]$ find . -iname *compliance*
./build/site/compliance.html
./src/documentation/content/xdocs/compliance.xml
./src/documentation/resources/schema/dtd/compliance-v10.dtd
./src/documentation/resources/stylesheets/compliance2document.xsl
./src/documentation/resources/stylesheets/compliance2fo.xsl
./src/documentation/resources/stylesheets/compliance2html.xsl
The only stylesheet which specifies the CSS for the table-cells is
'compliance2html.xsl' and the relevant xsl:template doesn't appear to
be processed:
<xsl:template match="head">
<head>
<meta http-equiv="Content-Language" content="en-us"/>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252"/>
<link type="text/css" href="skin/page.css" rel="stylesheet"/>
<style>
<!--
.yes { background-color: #99FF99 }
.no { background-color: #FF9999 }
.partial { background-color: #FFFFCC }
.category { /*background-color: #CFDCED;*/
font-size: 1.2em }
-->
</style>
</head>
</xsl:template>
(BTW, I the colors changed to light green - yes, light red - no, yellow
- partial)
However, if I use Xalan to transform compliance.xml using
compliance2html.xsl, the output is almost correct (@class='yes' doesn't
work, but class='no' & class='partial' do?):
./xalan.sh -IN compliance.xml -XSL compliance2html.xsl -OUT
041109_compliance_001.html
The result:
<http://homepage.mac.com/webmaestro/xml-fop/041109_compliance_001.html>
I just tried transforming:
./xalan.sh -IN compliance.xml -XSL compliance2document.xsl -OUT
041109_compliance_001.xml
The result:
<http://homepage.mac.com/webmaestro/xml-fop/041109_compliance_001.xml>
When processed with Forrest, this xdoc file provides the same output
we've been dealing with (table is OK--without the styles--but it's
missing the mini-TOC & citation links).
Unless anyone has any better ideas, I'm about ready to settle for using
the HTML file output by ./xalan.sh above. I'll have to generate that
file by hand for the time being, and I'll have to skin it, but that
shouldn't be too bad. I think we all were hoping for a better way,
though.
Now all I/we have to do, is figure out the directory structure for RAW
files & images (a moving target these days... ;-)), so I can get the
links to the raw SVG & FO (and possibly PDF) files to resolve.
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Clay Leeds <cl...@medata.com>.
On Nov 8, 2004, at 4:14 PM, David Crossley wrote:
> Clay Leeds wrote:
>> Juan Jose Pablos wrote:
>>> David Crossley wrote:
>>>> Juan Jose Pablos wrote:
>>>>> The only work around this was to add a catalog using the
>>>>> CatalogManager.properties.
>>>> Correct. That file is required. It is not a "work around",
>>>> it is required.
>>>
>>> If you have ${project.content-dir}/classes/CatalogManager.properties
>>>
>>> You must add relative-catalogs=false and a relative path on catalogs
>>> i.e:
>>>
>>> relative-catalogs=false
>>> catalogs=../resources/schema/catalog.xcat
>>
>> The version of CatalogManager.properties that was committed last night
>> is what you sent me, Cheche (thanks!). The only lines which are not
>> commented out are:
>>
>> [..]
>> verbosity=10
>> [..]
>> catalogs=../resources/schema/catalog.xcat
>> relative-catalogs=false
>
> As i said before, don't leave that settting
> at "verbosity=10" or you will get swamped with messages.
> It is just for testing that your catalog entity resolver
> is finding your compliance.dtd properly.
Thanks again for the re-clarification. After running it, all I see are
~10 new lines at the top of the Forrest/Cocoon output:
====
[..]
------------------------------------------------------------------------
cocoon 2.2.0-dev
Copyright (c) 1999-2004 Apache Software Foundation. All rights reserved.
------------------------------------------------------------------------
Parse catalog:
file:/Users/Shared/_WebDLs/_repos/xml-fop/src/documentation/resources/
schema/catalog.xcat
Loading catalog:
file:/Users/Shared/_WebDLs/_repos/xml-fop/src/documentation/resources/
schema/catalog.xcat
Default BASE:
file:/Users/Shared/_WebDLs/_repos/xml-fop/src/documentation/resources/
schema/catalog.xcat
override: yes
OVERRIDE: yes
public: -//APACHE//DTD Compliance V1.0//EN
dtd/compliance-v10.dtd
PUBLIC: -//APACHE//DTD Compliance V1.0//EN
file:/Users/Shared/_WebDLs/_repos/xml-fop/src/documentation/resources/
schema/dtd/compliance-v10.dtd
^ design/
^ dev/
^ design/alt.design/
* [1/83] [83/86] 31.325s 29.7Kb linkmap.html
[..]
====
I've turned it off locally and have committed that in case anyone else
downloads this version.
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> Juan Jose Pablos wrote:
> > David Crossley wrote:
> >> Juan Jose Pablos wrote:
> >>> The only work around this was to add a catalog using the
> >>> CatalogManager.properties.
> >> Correct. That file is required. It is not a "work around",
> >> it is required.
> >
> > If you have ${project.content-dir}/classes/CatalogManager.properties
> >
> > You must add relative-catalogs=false and a relative path on catalogs
> > i.e:
> >
> > relative-catalogs=false
> > catalogs=../resources/schema/catalog.xcat
>
> The version of CatalogManager.properties that was committed last night
> is what you sent me, Cheche (thanks!). The only lines which are not
> commented out are:
>
> [..]
> verbosity=10
> [..]
> catalogs=../resources/schema/catalog.xcat
> relative-catalogs=false
As i said before, don't leave that settting
at "verbosity=10" or you will get swamped with messages.
It is just for testing that your catalog entity resolver
is finding your compliance.dtd properly.
--
David Crossley
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Clay Leeds <cl...@medata.com>.
On Nov 8, 2004, at 2:49 AM, Juan Jose Pablos wrote:
> David Crossley wrote:
>> Juan Jose Pablos wrote:
>>> The only work around this was to add a catalog using the
>>> CatalogManager.properties.
>> Correct. That file is required. It is not a "work around",
>> it is required.
>
> If you have ${project.content-dir}/classes/CatalogManager.properties
>
> You must add relative-catalogs=false and a relative path on catalogs
> i.e:
>
> relative-catalogs=false
> catalogs=../resources/schema/catalog.xcat
The version of CatalogManager.properties that was committed last night
is what you sent me, Cheche (thanks!). The only lines which are not
commented out are:
[..]
verbosity=10
[..]
catalogs=../resources/schema/catalog.xcat
relative-catalogs=false
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Juan Jose Pablos <ch...@che-che.com>.
David Crossley wrote:
> Juan Jose Pablos wrote:
>>The only work around this was to add a catalog using the
>>CatalogManager.properties.
>
>
> Correct. That file is required. It is not a "work around",
> it is required.
>
>
If you have ${project.content-dir}/classes/CatalogManager.properties
You must add relative-catalogs=false and a relative path on catalogs i.e:
relative-catalogs=false
catalogs=../resources/schema/catalog.xcat
Cheers,
Cheche
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by David Crossley <cr...@apache.org>.
Juan Jose Pablos wrote:
> David Crossley wrote:
> >
> > In that situation forrest is expecting a project file with
> > the default name of "catalog.xcat". Putting that file in my
> > seed project's src/documentation/resources/schema/ directory
> > did the trick. The validation of the compliance.xml works now.
>
> But when you want to build the page i.e compliance.html fail.
>
> The only work around this was to add a catalog using the
> CatalogManager.properties.
Correct. That file is required. It is not a "work around",
it is required.
> Which seems fine. Please double check this solution, so we would update
> our documentation.
>
> > As usual, if people want to call the file something else
> > e.g. "catalog.fop.xcat" then that must be declared in
> > the forrest.properties file.
>
> Would not make more sense to put it on CatalogManager.properties ?
See above. It *must* be declared in CatalogManager.properties
Also, if the name of catalog file is not the default "catalog.xcat"
the the new filename must be declared in forrest.properties
--David
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Juan Jose Pablos <ch...@che-che.com>.
David Crossley wrote:
>
> In that situation forrest is expecting a project file with
> the default name of "catalog.xcat". Putting that file in my
> seed project's src/documentation/resources/schema/ directory
> did the trick. The validation of the compliance.xml works now.
>
But when you want to build the page i.e compliance.html fail.
The only work around this was to add a catalog using the
CatalogManager.properties.
Which seems fine. Please double check this solution, so we would update
our documentation.
cheers,
Cheche
> As usual, if people want to call the file something else
> e.g. "catalog.fop.xcat" then that must be declared in
> the forrest.properties file.
Would not make more sense to put it on CatalogManager.properties ?
Cheers,
Cheche
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Clay Leeds <cl...@medata.com>.
On Nov 8, 2004, at 1:52 AM, David Crossley wrote:
> I don't know why Cheche did it that way, with one catalog
> linking to another catalog. I have a local seed project
> with your compliance.xml and everything works fine.
> To get your system to be the same as mine you need to just:
>
> cd src/documentation/resources/schema
> mv -f catalog.fop.xcat catalog.xcat
> rm catalog
>
> So doing 'ls' in that directory ...
> ------
> catalog.xcat
> dtd/
> ------
Mine looks similar (although I've got a CVS.sandboxinfo folder in
there, from my CVS GUI app).
Thanks!
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Juan Jose Pablos <ch...@che-che.com>.
David Crossley wrote:
> Clay Leeds wrote:
>
>>David Crossley wrote:
>>
>>>So Clay, all you need to do is to replace your plain-text
>>>file called "catalog" with an xml-based one called "catalog.xcat".
>>
>>I think I did that now, although I also have Cheche's catalog.fop.xcat.
>>Can you take a look at the current commits and make certain it's all
>>OK?
>
>
> I don't know why Cheche did it that way, with one catalog
> linking to another catalog.
Well, That was to ensure that we have the same setup than on the forrest
project. But yes, you can use the setup that david Crossley proposal's
Let me know, how are you getting on.
Cheers,
cheche
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> David Crossley wrote:
> > So Clay, all you need to do is to replace your plain-text
> > file called "catalog" with an xml-based one called "catalog.xcat".
>
> I think I did that now, although I also have Cheche's catalog.fop.xcat.
> Can you take a look at the current commits and make certain it's all
> OK?
I don't know why Cheche did it that way, with one catalog
linking to another catalog. I have a local seed project
with your compliance.xml and everything works fine.
To get your system to be the same as mine you need to just:
cd src/documentation/resources/schema
mv -f catalog.fop.xcat catalog.xcat
rm catalog
So doing 'ls' in that directory ...
------
catalog.xcat
dtd/
------
--
David Crossley
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Clay Leeds <cl...@medata.com>.
On Nov 7, 2004, at 4:43 PM, David Crossley wrote:
> So Clay, all you need to do is to replace your plain-text
> file called "catalog" with an xml-based one called "catalog.xcat".
I think I did that now, although I also have Cheche's catalog.fop.xcat.
Can you take a look at the current commits and make certain it's all
OK?
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by David Crossley <cr...@apache.org>.
Juan Jose Pablos wrote:
> David Crossley wrote:
> > Just to explain a little bit. There has already been
> > a lot of misunderstanding about this topic.
> >
> > Clay already had a plain-text "catalog" file that worked
> > in his project at documentation/resources/schema/catalog
> >
> > You have provided him with an xml-based catalog instead.
> > Either format will be okay.
> >
>
> I saw that, but that file did not stop these errors.
I did some further investigation and found that the
plain text catalog works fine for the 'forrest run' webapp,
but doing command-line 'forrest' it does not.
In that situation forrest is expecting a project file with
the default name of "catalog.xcat". Putting that file in my
seed project's src/documentation/resources/schema/ directory
did the trick. The validation of the compliance.xml works now.
As usual, if people want to call the file something else
e.g. "catalog.fop.xcat" then that must be declared in
the forrest.properties file.
So Clay, all you need to do is to replace your plain-text
file called "catalog" with an xml-based one called "catalog.xcat".
--David
> Only when I created
> the local xml-based catalog, I could validate this xml file.
>
> I think that maybe it is on our site.
>
> After adding this xml-based catalog, Forrest report this error:
>
> X [0] compliance.html BROKEN:
> /home/cheche/xml/xml-fop/src/documentation/content/xdocs/compliance-v10.dtd
> (No such file or directory)
>
> The only way I found to avoid this is adding the compliance public
> identifier to forrest catalog.
>
>
> I need to find a way to add {project.home}/catalog.xcat to
> catalog.forrest.xcat
>
> WDYT?
>
> Cheers,
> Cheche
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Juan Jose Pablos <ch...@che-che.com>.
David Crossley wrote:
> Juan Jose Pablos wrote:
>
>>Clay Leeds wrote:
>>
>>>Great idea, Cheche! I've committed the following files:
>>>- forrest.properties
>>>- src/documentation/sitemap.xmap
>>>- src/documentation/skinconf.xml
>>>- src/documentation/content/xdocs/compliance.xml
>>>- src/documentation/content/xdocs/site.xml
>>>
>>
>>Update cvs with these two files. That would resolve the validation errors.
>
>
> Just to explain a little bit. There has already been
> a lot of misunderstanding about this topic.
>
> Clay already had a plain-text "catalog" file that worked
> in his project at documentation/resources/schema/catalog
>
> You have provided him with an xml-based catalog instead.
> Either format will be okay.
>
I saw that, but that file did not stop these errors. Only when I created
the local xml-based catalog, I could validate this xml file.
I think that maybe it is on our site.
After adding this xml-based catalog, Forrest report this error:
X [0] compliance.html BROKEN:
/home/cheche/xml/xml-fop/src/documentation/content/xdocs/compliance-v10.dtd
(No such file or directory)
The only way I found to avoid this is adding the compliance public
identifier to forrest catalog.
I need to find a way to add {project.home}/catalog.xcat to
catalog.forrest.xcat
WDYT?
Cheers,
Cheche
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by David Crossley <cr...@apache.org>.
Juan Jose Pablos wrote:
> Clay Leeds wrote:
> >
> > Great idea, Cheche! I've committed the following files:
> > - forrest.properties
> > - src/documentation/sitemap.xmap
> > - src/documentation/skinconf.xml
> > - src/documentation/content/xdocs/compliance.xml
> > - src/documentation/content/xdocs/site.xml
> >
>
> Update cvs with these two files. That would resolve the validation errors.
Just to explain a little bit. There has already been
a lot of misunderstanding about this topic.
Clay already had a plain-text "catalog" file that worked
in his project at documentation/resources/schema/catalog
You have provided him with an xml-based catalog instead.
Either format will be okay.
--
David Crossley
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Juan Jose Pablos <ch...@che-che.com>.
Clay Leeds wrote:
>
> Great idea, Cheche! I've committed the following files:
> - forrest.properties
> - src/documentation/sitemap.xmap
> - src/documentation/skinconf.xml
> - src/documentation/content/xdocs/compliance.xml
> - src/documentation/content/xdocs/site.xml
>
Update cvs with these two files. That would resolve the validation errors.
> Here's what the Compliance Page currently looks like:
>
> http://homepage.mac.com/webmaestro/xml-fop/compliance.html
>
> Here's what I want the Compliance Page to look like:
>
> http://xml.apache.org/fop/compliance.html
>
I will have a look later...
Cheers,
Cheche
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Clay Leeds <cl...@medata.com>.
On Nov 6, 2004, at 3:39 AM, Juan Jose Pablos wrote:
> Clay Leeds wrote:
>> On Nov 5, 2004, at 7:41 PM, David Crossley wrote:
>>> Would you please create an Issue in our Forrest Jira
>>> and attach a (tar.gz or zip) archive your actual current files:
>>>
>>> sitemap.xmap
>>> compliance.xml
>>> compliance2document.xsl
>>> compliance.dtd
>>>
>>> That will give us a better idea of what is wrong.
>> Will do.
>> Web Maestro Clay
>
> Would not be easier to put them con cvs? Your actual site on xml-fop
> is broken anyway.
>
> It is going to be 3 months since you first report of "xml-fop Build
> Failed".
>
> Please, Please, Please....... Put them on the CVS so we can help you
> property.
> Do it man, we are putting much effort in Read, Write & Reply emails
>
> Cheers,
> Cheche
Great idea, Cheche! I've committed the following files:
- forrest.properties
- src/documentation/sitemap.xmap
- src/documentation/skinconf.xml
- src/documentation/content/xdocs/compliance.xml
- src/documentation/content/xdocs/site.xml
NOTE: The compliance2document.xsl file is unchanged.
Here's what the Compliance Page currently looks like:
http://homepage.mac.com/webmaestro/xml-fop/compliance.html
Here's what I want the Compliance Page to look like:
http://xml.apache.org/fop/compliance.html
FWIW, other files I committed:
- src/documentation/content/xdocs/graphics.xml
- src/documentation/content/xdocs/resources.xml
- src/documentation/resources/images/group-logo.gif
- src/documentation/resources/images/logo.jpg
(new fop and 'xmlgraphics' logos, updated resources page & some mods to
graphics.xml)
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Juan Jose Pablos <ch...@che-che.com>.
Clay Leeds wrote:
> On Nov 5, 2004, at 7:41 PM, David Crossley wrote:
>
>> Would you please create an Issue in our Forrest Jira
>> and attach a (tar.gz or zip) archive your actual current files:
>>
>> sitemap.xmap
>> compliance.xml
>> compliance2document.xsl
>> compliance.dtd
>>
>> That will give us a better idea of what is wrong.
>
>
> Will do.
>
> Web Maestro Clay
Would not be easier to put them con cvs? Your actual site on xml-fop is
broken anyway.
It is going to be 3 months since you first report of "xml-fop Build Failed".
Please, Please, Please....... Put them on the CVS so we can help you
property.
Do it man, we are putting much effort in Read, Write & Reply emails
Cheers,
Cheche
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Clay Leeds <cl...@medata.com>.
On Nov 5, 2004, at 7:41 PM, David Crossley wrote:
> Would you please create an Issue in our Forrest Jira
> and attach a (tar.gz or zip) archive your actual current files:
>
> sitemap.xmap
> compliance.xml
> compliance2document.xsl
> compliance.dtd
>
> That will give us a better idea of what is wrong.
Will do.
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> Clay Leeds wrote:
> <snip>
> > improved the Compliance page! We have content! It's not 'there' yet,
> > as it's missing the Table of Contents (which is particularly important
> > on this page, since each item must be referenced for
> > navigability--again, see[1]).
> >
> > [1] FOP Standards Compliance
> > http://xml.apache.org/fop/compliance.html
>
> I thought I'd clarify a bit (and change the Subject finally!) about the
> problems I'm now facing with Forrest generation of the FOP Compliance
> page. First of all, I don't know if any of the current FOP Committers
> actually understands the Compliance page itself. I believe KL (inactive
> committer) was the original author and others made edits. Perhaps I
> might be able to get some help from CG (active) or GlenM (active).
> We'll see.
> - I was wrong. The Table of Contents is being generated at the top
> - the links portion is a separate beast I'll have to learn
> (XSL-FO Object Support, XSL-FO Property Support)
> - the XSL-FO Object Support table is missing bgcolor of cells
> (required for readability)
> - table is missing the Citation column
> (contains convenient links to the citation in the XSL-FO Spec)
Would you please create an Issue in our Forrest Jira
and attach a (tar.gz or zip) archive your actual current files:
sitemap.xmap
compliance.xml
compliance2document.xsl
compliance.dtd
That will give us a better idea of what is wrong.
--
David Crossley
xml-fop Compliance Page (was Re: xml-fop Build Failed)
Posted by Clay Leeds <cl...@medata.com>.
On Nov 5, 2004, at 9:51 AM, Clay Leeds wrote:
<snip>
> improved the Compliance page! We have content! It's not 'there' yet,
> as it's missing the Table of Contents (which is particularly important
> on this page, since each item must be referenced for
> navigability--again, see[1]).
>
> [1] FOP Standards Compliance
> http://xml.apache.org/fop/compliance.html
I thought I'd clarify a bit (and change the Subject finally!) about the
problems I'm now facing with Forrest generation of the FOP Compliance
page. First of all, I don't know if any of the current FOP Committers
actually understands the Compliance page itself. I believe KL (inactive
committer) was the original author and others made edits. Perhaps I
might be able to get some help from CG (active) or GlenM (active).
We'll see.
- I was wrong. The Table of Contents is being generated at the top
- the links portion is a separate beast I'll have to learn
(XSL-FO Object Support, XSL-FO Property Support)
- the XSL-FO Object Support table is missing bgcolor of cells
(required for readability)
- table is missing the Citation column
(contains convenient links to the citation in the XSL-FO Spec)
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Build Failed
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> David Crossley wrote:
> > Clay Leeds wrote:
> >> In any case, my CRITICAL problem is that the Compliance Page renders
> >> no
> >> content (other than the site structure, nav links, etc.).
> >
> > That sounds like you have now properly configured
> > the DTD and the catalog entity resolver.
>
> Yup!
>
> > The two remaining causes would be your sitemap.xmap
> > or your compliance2document.xsl stylesheet.
>
> A good assumption.
>
> > I clipped this from the sitemap that you attached
> > earlier in this thread. Is that the latest?
> > It does not match the examples.
> > You seem to have a mixture of the basic solution:
> > http://localhost:8888/docs/your-project.html#adding_new_content_type
> > and the advanced solution:
> > http://localhost:8888/docs/your-project.html#adding_new_content_type_2
>
> That's entirely possible. I spent some time trying to weed out the
> problems, and when I stopped getting errors, I thought I was 'done'
> (except for the 'little' problem that compliance.html still has no real
> content).
>
> > ---- clip from xml-fop sitemap ----
> > <map:match pattern="**compliance.xml">
> > <map:generate src="{project:content.xdocs}{1}compliance.xml"/>
> > <map:act type="sourcetype"
> > src="{project:content.xdocs}{1}compliance.xml">
> > <map:transform
> > src="{project:resources.stylesheets}/compliance2html.xsl"/>
> > </map:act>
> > <map:serialize type="xml"/>
> > </map:match>
> > ------------------------------------
> >
> > You just need the proper syntax for the "basic solution".
>
> So the new, improved version should be:
>
> ---- clip from xml-fop sitemap ----
> <map:match pattern="**compliance.xml">
> <map:generate src="{project:content.xdocs}{1}compliance.xml"/>
> <map:transform
> src="{project:resources.stylesheets}/compliance2html.xsl" />
> <map:serialize type="xml"/>
> </map:match>
> ------------------------------------
>
> wait a minute... I just noticed two different XSL files:
>
> <map:transform
> src="{project:resources.stylesheets}/compliance2html.xsl" />
>
> and
>
> <map:transform
> src="{project:resources.stylesheets}/compliance2document.xsl" />
>
> I changed it to compliance2document.xsl and did a run /forrest/ run!
>
> > The "advanced solution" is for when you need to detect
> > different versions of the "Apache FOP Compliance DTD"
> > and transform each type accordingly.
>
> Thanks for the clarification. But how is that a combination of Basic
> and Advanced? It looks like I just did the Advanced solution.
As i said above, your sitemap had bits and pieces of the
"advanced solution". You were completely missing the
map:select and map:when elements. Please read the examples
more carefully. This is a waste of time and energy.
Anyway, stick with the basic solution that you now
seem to have working.
> > The other issue that i see, is that you need to transform
> > from your "compliance" document type into the internal
> > Forrest "Apache Document-v1*" document type. I have not
> > seen your stylesheet "compliance2html.xsl" but its name
> > suggests that you are skipping the vital internal transformation
> > and going straight to "html" output. However, i might be
> > mistaken and it is just a bad choice of filename.
>
> Yeah... I just noticed that too (see above...). As for how the
> compliance.xml format, it's a *completely* different beast (hence the
> new DTD!). I don't know how it works... I'm just hoping I won't have to
> re-create the darn thing (have you taken a look at it[1]?. It would be
> akin to hand-crafting the Forrest Document-v20.dtd file... by *hand*!
> Egads! I am not excited about the possibility to have to do that
> (159,978 bytes)!
Sorry, i cannot parse that.
--David
> Scratch that! Changing to:
>
> <map:transform
> src="{project:resources.stylesheets}/compliance2document.xsl" />
>
> improved the Compliance page! We have content! It's not 'there' yet, as
> it's missing the Table of Contents (which is particularly important on
> this page, since each item must be referenced for navigability--again,
> see[1]).
>
> [1] FOP Standards Compliance
> http://xml.apache.org/fop/compliance.html
>
> Web Maestro Clay
Re: xml-fop Build Failed
Posted by Clay Leeds <cl...@medata.com>.
On Nov 4, 2004, at 5:37 PM, David Crossley wrote:
> Clay Leeds wrote:
>> In any case, my CRITICAL problem is that the Compliance Page renders
>> no
>> content (other than the site structure, nav links, etc.).
>
> That sounds like you have now properly configured
> the DTD and the catalog entity resolver.
Yup!
> The two remaining causes would be your sitemap.xmap
> or your compliance2document.xsl stylesheet.
A good assumption.
> I clipped this from the sitemap that you attached
> earlier in this thread. Is that the latest?
> It does not match the examples.
> You seem to have a mixture of the basic solution:
> http://localhost:8888/docs/your-project.html#adding_new_content_type
> and the advanced solution:
> http://localhost:8888/docs/your-project.html#adding_new_content_type_2
That's entirely possible. I spent some time trying to weed out the
problems, and when I stopped getting errors, I thought I was 'done'
(except for the 'little' problem that compliance.html still has no real
content).
> ---- clip from xml-fop sitemap ----
> <map:match pattern="**compliance.xml">
> <map:generate src="{project:content.xdocs}{1}compliance.xml"/>
> <map:act type="sourcetype"
> src="{project:content.xdocs}{1}compliance.xml">
> <map:transform
> src="{project:resources.stylesheets}/compliance2html.xsl"/>
> </map:act>
> <map:serialize type="xml"/>
> </map:match>
> ------------------------------------
>
> You just need the proper syntax for the "basic solution".
So the new, improved version should be:
---- clip from xml-fop sitemap ----
<map:match pattern="**compliance.xml">
<map:generate src="{project:content.xdocs}{1}compliance.xml"/>
<map:transform
src="{project:resources.stylesheets}/compliance2html.xsl" />
<map:serialize type="xml"/>
</map:match>
------------------------------------
wait a minute... I just noticed two different XSL files:
<map:transform
src="{project:resources.stylesheets}/compliance2html.xsl" />
and
<map:transform
src="{project:resources.stylesheets}/compliance2document.xsl" />
I changed it to compliance2document.xsl and did a run /forrest/ run!
> The "advanced solution" is for when you need to detect
> different versions of the "Apache FOP Compliance DTD"
> and transform each type accordingly.
Thanks for the clarification. But how is that a combination of Basic
and Advanced? It looks like I just did the Advanced solution.
> The other issue that i see, is that you need to transform
> from your "compliance" document type into the internal
> Forrest "Apache Document-v1*" document type. I have not
> seen your stylesheet "compliance2html.xsl" but its name
> suggests that you are skipping the vital internal transformation
> and going straight to "html" output. However, i might be
> mistaken and it is just a bad choice of filename.
Yeah... I just noticed that too (see above...). As for how the
compliance.xml format, it's a *completely* different beast (hence the
new DTD!). I don't know how it works... I'm just hoping I won't have to
re-create the darn thing (have you taken a look at it[1]?. It would be
akin to hand-crafting the Forrest Document-v20.dtd file... by *hand*!
Egads! I am not excited about the possibility to have to do that
(159,978 bytes)!
Scratch that! Changing to:
<map:transform
src="{project:resources.stylesheets}/compliance2document.xsl" />
improved the Compliance page! We have content! It's not 'there' yet, as
it's missing the Table of Contents (which is particularly important on
this page, since each item must be referenced for navigability--again,
see[1]).
[1] FOP Standards Compliance
http://xml.apache.org/fop/compliance.html
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Build Failed
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> David Crossley wrote:
> > Clay Leeds wrote:
> >> (NOTE: yeah, I feel silly about the CatalogManager.properties warning,
> >> since I haven't figured out how to set it correctly either... At least
> >> my VCR doesn't flash 12:00! This page[4] says "You can add a local
> >> CatalogManager.properties to your project.classes-dir to define your
> >> additional catalogs for DTDs and other entities." but there's no
> >> example so I don't know what that file should look like--should I just
> >> switch to project.classes-dir & /touch CatalogManager.properties/?
> >> Anyway, 'If you do not add such a configuration file, then there will
> >> be a harmless message on startup "CatalogManager.properties not
> >> found".' 12:00... 12:00...;-))
> >>
> >> [4]
> >> http://forrest.apache.org/docs/upgrading_06.html#local-catalog
> >
> > Copy it from a fresh 'forrest seed site' in
> > src/documentation/classes/CatalogManager.properties
>
> I see that it actually does exist in my directory now (as mentioned in
> a previous post, I started from a fresh /forrest seed/ last week). I
> don't think recall it being there before.
>
> > I just added that to /docs/upgrading_06.html#local-catalog
> > and clarified its description in the main document that you
> > should be following: /docs/validation.html#catalog
>
> Thanks. I've made the modifications indicated to the
> CatalogManager.properties file (I no longer get the error!). Here's the
> only line from that file that is not commented out:
>
> ====
> catalogs=/Users/Shared/_WebDLs/_repos/xml-fop/src/documentation/
> resources/schema/catalog.xcat
> ====
>
> I also created the src/documentation/resources/schema/catalog.xcat file
> with these contents:
>
> ====
> <?xml version="1.0"?>
> <!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 W3C stuff like XHTML and SVG -->
> <catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"
> prefer="public">
>
> <!-- Extensible HTML 1.0 -->
> <public publicId="-//APACHE//DTD Compliance V1.0//EN"
> uri="dtd/compliance-v10.dtd"/>
>
> </catalog>
> ====
>
> I checked to ensure that this file exists (it always has):
>
> ====
> src/documentation/resources/schema/dtd/compliance-v10.dtd
> ====
>
> (I don't think xml-fop's site needs anything else in
> resources/schema/dtd...)
>
> In any case, my CRITICAL problem is that the Compliance Page renders no
> content (other than the site structure, nav links, etc.).
That sounds like you have now properly configured
the DTD and the catalog entity resolver.
The two remaining causes would be your sitemap.xmap
or your compliance2document.xsl stylesheet.
I clipped this from the sitemap that you attached
earlier in this thread. Is that the latest?
It does not match the examples.
You seem to have a mixture of the basic solution:
http://localhost:8888/docs/your-project.html#adding_new_content_type
and the advanced solution:
http://localhost:8888/docs/your-project.html#adding_new_content_type_2
---- clip from xml-fop sitemap ----
<map:match pattern="**compliance.xml">
<map:generate src="{project:content.xdocs}{1}compliance.xml"/>
<map:act type="sourcetype"
src="{project:content.xdocs}{1}compliance.xml">
<map:transform
src="{project:resources.stylesheets}/compliance2html.xsl"/>
</map:act>
<map:serialize type="xml"/>
</map:match>
------------------------------------
You just need the proper syntax for the "basic solution".
The "advanced solution" is for when you need to detect
different versions of the "Apache FOP Compliance DTD"
and transform each type accordingly.
The other issue that i see, is that you need to transform
from your "compliance" document type into the internal
Forrest "Apache Document-v1*" document type. I have not
seen your stylesheet "compliance2html.xsl" but its name
suggests that you are skipping the vital internal transformation
and going straight to "html" output. However, i might be
mistaken and it is just a bad choice of filename.
--
David Crossley
Re: xml-fop Build Failed
Posted by Clay Leeds <cl...@medata.com>.
On Nov 3, 2004, at 9:38 PM, David Crossley wrote:
> Clay Leeds wrote:
>> (NOTE: yeah, I feel silly about the CatalogManager.properties warning,
>> since I haven't figured out how to set it correctly either... At least
>> my VCR doesn't flash 12:00! This page[4] says "You can add a local
>> CatalogManager.properties to your project.classes-dir to define your
>> additional catalogs for DTDs and other entities." but there's no
>> example so I don't know what that file should look like--should I just
>> switch to project.classes-dir & /touch CatalogManager.properties/?
>> Anyway, 'If you do not add such a configuration file, then there will
>> be a harmless message on startup "CatalogManager.properties not
>> found".' 12:00... 12:00...;-))
>>
>> [4]
>> http://forrest.apache.org/docs/upgrading_06.html#local-catalog
>
> Copy it from a fresh 'forrest seed site' in
> src/documentation/classes/CatalogManager.properties
I see that it actually does exist in my directory now (as mentioned in
a previous post, I started from a fresh /forrest seed/ last week). I
don't think recall it being there before.
> I just added that to /docs/upgrading_06.html#local-catalog
> and clarified its description in the main document that you
> should be following: /docs/validation.html#catalog
Thanks. I've made the modifications indicated to the
CatalogManager.properties file (I no longer get the error!). Here's the
only line from that file that is not commented out:
====
catalogs=/Users/Shared/_WebDLs/_repos/xml-fop/src/documentation/
resources/schema/catalog.xcat
====
I also created the src/documentation/resources/schema/catalog.xcat file
with these contents:
====
<?xml version="1.0"?>
<!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 W3C stuff like XHTML and SVG -->
<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"
prefer="public">
<!-- Extensible HTML 1.0 -->
<public publicId="-//APACHE//DTD Compliance V1.0//EN"
uri="dtd/compliance-v10.dtd"/>
</catalog>
====
I checked to ensure that this file exists (it always has):
====
src/documentation/resources/schema/dtd/compliance-v10.dtd
====
(I don't think xml-fop's site needs anything else in
resources/schema/dtd...)
In any case, my CRITICAL problem is that the Compliance Page renders no
content (other than the site structure, nav links, etc.).
As I indicated in Tuesday's message[1] I still have problems with the
svg & fo transformations. However, at this point I am content to just
follow the instructions for "Images"[2] (which I assume follows the
same general pattern as the previous instructions for "RAW" files--is
this a correct assumption?) and have the files copied over as RAW
files. It'll probably cut down on run time anyway, not to have to
generate those files every time a /forrest/ run is done.
[1]
http://issues.apache.org/eyebrowse/ReadMsg?
listName=dev@forrest.apache.org&msgNo=15153
[2]
http://forrest.apache.org/docs/your-project.html#images
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Build Failed
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
>
> (NOTE: yeah, I feel silly about the CatalogManager.properties warning,
> since I haven't figured out how to set it correctly either... At least
> my VCR doesn't flash 12:00! This page[4] says "You can add a local
> CatalogManager.properties to your project.classes-dir to define your
> additional catalogs for DTDs and other entities." but there's no
> example so I don't know what that file should look like--should I just
> switch to project.classes-dir & /touch CatalogManager.properties/?
> Anyway, 'If you do not add such a configuration file, then there will
> be a harmless message on startup "CatalogManager.properties not
> found".' 12:00... 12:00...;-))
>
> [4]
> http://forrest.apache.org/docs/upgrading_06.html#local-catalog
Copy it from a fresh 'forrest seed site' in
src/documentation/classes/CatalogManager.properties
I just added that to /docs/upgrading_06.html#local-catalog
and clarified its description in the main document that you
should be following: /docs/validation.html#catalog
--
David Crossley
Re: xml-fop Build Failed
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> David Crossley wrote:
> > Clay Leeds wrote:
> >> Although snipped from this response, hopefully the unrelated SVG stuff
> >> won't be ignored... as it's related to my continuing xml-fop Build
> >> Failed... ;-)
> >
> > That is why it would be far better to address separate
> > issues in separate threads. I had to snip everything that
> > was not related to the FOP compliance DTD resolution
> > so that we could focus. Hopefully someone else can help
> > with your remaining SVG issues.
>
> Agreed. Thank you for helping me move in the direction of clarity. I
> will repost that portion of the message. Which begs the question...
> should I move that (and the rest of this thread to the user@f.a.o list,
> or should we keep it here in dev@f.a.o?
Please keep it on the dev list. I am afraid that this
whole thread is too confusing and would damage the
understanding of our users. The user list needs to
be kept as simple as possible.
--
David Crossley
Re: xml-fop Build Failed
Posted by Clay Leeds <cl...@medata.com>.
On Nov 4, 2004, at 4:59 PM, David Crossley wrote:
> Clay Leeds wrote:
>> Although snipped from this response, hopefully the unrelated SVG stuff
>> won't be ignored... as it's related to my continuing xml-fop Build
>> Failed... ;-)
>
> That is why it would be far better to address separate
> issues in separate threads. I had to snip everything that
> was not related to the FOP compliance DTD resolution
> so that we could focus. Hopefully someone else can help
> with your remaining SVG issues.
Agreed. Thank you for helping me move in the direction of clarity. I
will repost that portion of the message. Which begs the question...
should I move that (and the rest of this thread to the user@f.a.o list,
or should we keep it here in dev@f.a.o?
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Build Failed
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> David Crossley wrote:
>
> > [snip some unrelated SVG stuff]
>
> Although snipped from this response, hopefully the unrelated SVG stuff
> won't be ignored... as it's related to my continuing xml-fop Build
> Failed... ;-)
That is why it would be far better to address separate
issues in separate threads. I had to snip everything that
was not related to the FOP compliance DTD resolution
so that we could focus. Hopefully someone else can help
with your remaining SVG issues.
--
David Crossley
Re: xml-fop Build Failed
Posted by Clay Leeds <cl...@medata.com>.
On Nov 3, 2004, at 10:30 PM, David Crossley wrote:
> Clay Leeds wrote:
>> Over the weekend and the last few days, I've spent a lot of time
>> fumbling attempting to follow the instructions to fix my custom
>> sitemap.xmap file (attached to this msg). Specifically, I was
>> referring
>> to the "Adding a new content type (advanced)"[1] and the "SourceType
>> (content aware pipelines)"[2] pages.
>
> You should not need to get as far as [2] (that is
> just for reference).
I *shouldn't* need to, but I couldn't proceed without the 'context'
(parent <=> child relationship) for the code snippet displayed on [1].
(see the next passage...)
>> NOTE1: [2] could be improved by showing the <map:action../> example in
>> context. Not knowing where it goes, when placing the current example
>> into my sitemap.xmap file I got an error. I figured it out by going
>> here[3] (except that's for Cocoon 2.1 but the 2.0 docs appear to be
>> the
>> same).
>
> Not sure why you would look at Cocoon-2.0 docs. They are
> very old. In Forrest we use Cocoon-2.2 (it does not yet
> have online docs, but their 2.1 docs will suffice).
That was just silly. For some reason I thought Forrest uses Cocoon 2.0
instead of 2.2. In any case, I think it's OK, but I'm hoping someone
will look at my new sitemap.xmap to see if my new content type is OK.
>> I've attached an improvement PATCH for [2]...
>
> Added that thanks. However i made changes, so move your
> version of cap.xml out of the way or do 'svn revert cap.xml'
> to get rid of your local changes before doing 'svn update'.
Already rm'd... although, I'm not worried about that too much, as the
xml-fop/ build will use apache-forrest-0.6 (or perhaps 0.6.1 if
released soon enough!).
> [snip some unrelated SVG stuff]
Although snipped from this response, hopefully the unrelated SVG stuff
won't be ignored... as it's related to my continuing xml-fop Build
Failed... ;-)
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Build Failed
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> David Crossley wrote:
[snip successful use of 'patch']
>
> I doubt that Cheche's patch will "fix" the compliance.html
> > situation for you. Rather you need to follow the documentation
> > to which we have referred, e.g. Provide your "Compliance DTD",
> > configure the catalog entity resolver, etc. etc.
>
> Still working on that. See below and attached sitemap.xmap after
> slogging through this message.
>
> David Crossley wrote:
> >> <!-- ========================== FOP Additions
> >> ========================== -->
> >> <map:match pattern="body-compliance.xml">
> >> <map:generate type="file-nolabel"
> >> src="content/xdocs/compliance.xml"/>
> >> <map:transform
> >> src="resources/stylesheets/compliance2html.xsl"/>
> >> <map:serialize type="xml"/>
> >> </map:match>
> >> <!-- ======================== End FOP Additions
> >> ======================== -->
> >
> > That match is not correct anymore. Please follow the
> > documentation your-project.html "Adding new content type".
>
> Over the weekend and the last few days, I've spent a lot of time
> fumbling attempting to follow the instructions to fix my custom
> sitemap.xmap file (attached to this msg). Specifically, I was referring
> to the "Adding a new content type (advanced)"[1] and the "SourceType
> (content aware pipelines)"[2] pages.
You should not need to get as far as [2] (that is
just for reference).
> NOTE1: [2] could be improved by showing the <map:action../> example in
> context. Not knowing where it goes, when placing the current example
> into my sitemap.xmap file I got an error. I figured it out by going
> here[3] (except that's for Cocoon 2.1 but the 2.0 docs appear to be the
> same).
Not sure why you would look at Cocoon-2.0 docs. They are
very old. In Forrest we use Cocoon-2.2 (it does not yet
have online docs, but their 2.1 docs will suffice).
> I've attached an improvement PATCH for [2]...
Added that thanks. However i made changes, so move your
version of cap.xml out of the way or do 'svn revert cap.xml'
to get rid of your local changes before doing 'svn update'.
[snip some unrelated SVG stuff]
> [1]
> http://forrest.apache.org/docs/your-
> project.html#adding_new_content_type_2
> [2]
> http://forrest.apache.org/docs/cap.html
> [3]
> http://cocoon.apache.org/2.1/userdocs/concepts/sitemap.html
> [4]
> http://forrest.apache.org/docs/upgrading_06.html#local-catalog
>
> Web Maestro Clay
Re: RAW files (was Re: xml-fop Build Failed)
Posted by Clay Leeds <cl...@medata.com>.
I have yet to find a solution to this problem outlined below and also
here[1]. I do not appear to be able to copy RAW files to my static site
(*.fo, *.svg, & *.pdf).
Attempted solutions I have tried placing these files:
1. src/documentation/content/* (the 'old' pre-0.6 method)
- src/documentation/content/svg/*.svg
- src/documentation/content/fo/*.fo
- src/documentation/content/dev/fo/*.pdf
RESULT: JAVA CORE-DUMP ERROR (see [1])
Exception in thread "main" java.lang.NoSuchMethodError:
org.apache.batik.bridge.UnitProcessor.createContext(Lorg/apache/batik/
bridge/BridgeContext;Lorg/w3c/dom/Element;)Lorg/apache/batik/util/
UnitProcessor$Context;
[..]
2. src/documentation/resources/images/* (the current method on
http://forrest.apache.org)
- src/documentation/resources/images/dev/svg/*.svg
- src/documentation/resources/images/dev/fo/*.fo
- src/documentation/resources/images/dev/fo/*.pdf
RESULT EXAMPLE: BROKEN:
/Users/Shared/_WebDLs/_repos/xml-fop/src/documentation/content/xdocs/
images/paints.xml (No such file or directory)
3. src/documentation/resources/images/* (messy, but if it works I'm
happy!)
- src/documentation/resources/images/*.svg
- src/documentation/resources/images/*.fo
- src/documentation/resources/images/*.pdf
RESULT EXAMPLE: BROKEN:
/Users/Shared/_WebDLs/_repos/xml-fop/src/documentation/content/xdocs/
images/paints.xml (No such file or directory)
4. src/documentation/content/xdocs/images/* (messy, but if it works I'm
happy!)
- src/documentation/content/xdocs/images/*.svg
- src/documentation/content/xdocs/images/*.fo
- src/documentation/content/xdocs/images/*.pdf
RESULT EXAMPLE: BROKEN:
/Users/Shared/_WebDLs/_repos/xml-fop/src/documentation/content/xdocs/
images/paints.xml (No such file or directory)
I'm open to suggestions on how to resolve this problem.
[1]
http://issues.apache.org/eyebrowse/ReadMsg?
listName=dev@forrest.apache.org&msgNo=15274
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
RAW files (was Re: xml-fop Build Failed)
Posted by Clay Leeds <cl...@medata.com>.
This message is a re-post of problems experienced in the 'xml-fop Build
Failed' thread[5], with discussion un-related to non-RAW files removed.
BUILD ERRORS
============
On another, related side note, I've tar'd up the sub-directories in
src/documentation/content (except xdocs/ of course!). When running
/forrest/ I get errors for each of the references to items in the fo/,
dev/, dev/fo/, dev/svg, & design/ directories. However, if I un-tar
them:
[clay@Clay-Leeds-Computer clay]$ ls -l
"/Users/Shared/_WebDLs/_repos/xml-fop/src/documentation/content"
total 208
drwxrwxrwx 3 clay 102 Nov 1 13:36 CVS.sandboxinfo
drwxrwxrwx 4 clay 136 Oct 26 20:27 design
-rw-rw-rw- 1 clay 86225 Oct 29 15:22 design.tar.gz
drwxrwxrwx 5 clay 170 Oct 27 15:40 dev
-rw-rw-rw- 1 clay 85908 Oct 29 15:22 dev.tar.gz
drwxrwxrwx 15 clay 510 Oct 27 15:32 fo
-rw-rw-rw- 1 clay 33272 Oct 29 15:22 fo.tar.gz
drwxrwxrwx 39 clay 1326 Oct 27 14:39 xdocs
I get a Java dump error that complains about svg stuff:
====
Cannot find CatalogManager.properties
^ dev/
^ design/
^ design/alt.design/
* [1/82] [82/85] 17.425s 21.7Kb linkmap.html
* [2/84] [3/30] 2.436s 12.3Kb design/alt.design/coroutines.html
* [3/84] [1/33] 1.652s 22.7Kb design/breakpos.html
* [4/84] [1/46] 1.255s 9.7Kb logocontest.html
* [5/83] [0/0] 0.905s 2.3Kb skin/basic.css
* [6/83] [1/47] 1.835s 12.5Kb extensions.html
* [7/83] [1/33] 1.344s 12.1Kb design/images.html
* [8/82] [0/0] 4.835s 9.1Kb design/alt.design/coroutines.pdf
* [9/83] [2/30] 1.246s 14.5Kb dev/implement.html
* [10/89] [7/26] 0.975s 12.9Kb
design/alt.design/properties/introduction.html
* [11/89] [1/49] 2.623s 13.5Kb configuration.html
* [12/89] [1/33] 1.604s 17.0Kb design/renderers.html
* [13/89] [1/30] 1.135s 14.1Kb dev/fonts.html
* [14/88] [0/0] 0.884s 14.1Kb dev/fonts.pdf
* [15/88] [1/45] 1.116s 10.7Kb todo.html
* [16/87] [0/0] 2.176s 5.9Kb todo.pdf
* [18/98] [13/43] 1.751s 12.8Kb dev/svg.html
X [0] dev/svg/paints.pdf BROKEN:
Can't find bundle for base name org.apache.fop.svg.resources.Messages,
locale en_US
* [20/96] [0/24] 0.666s 5.7Kb
design/alt.design/properties/PropertyConsts-class.html
* [21/96] [1/33] 1.228s 9.9Kb design/pdf-library.html
* [22/95] [0/0] 0.682s 0b dev/fo/embedding.fo.pdf
Exception in thread "main" java.lang.NoSuchMethodError:
org.apache.batik.bridge.UnitProcessor.createContext(Lorg/apache/batik/
bridge/BridgeContext;Lorg/w3c/dom/Element;)Lorg/apache/batik/util/
UnitProcessor$Context;
at org.apache.fop.svg.SVGElement.layout(SVGElement.java:218)
at
org.apache.fop.fo.flow.InstreamForeignObject.layout(InstreamForeignObjec
t.java:251)
at org.apache.fop.fo.flow.Block.layout(Block.java:257)
at
org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:154)
at
org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:110)
at
org.apache.fop.fo.pagination.PageSequence.makePage(PageSequence.java:
400)
at
org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:338)
at
org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java:262)
at
org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:223)
at
org.apache.cocoon.xml.AbstractXMLPipe.endElement(AbstractXMLPipe.java:
112)
at
org.apache.cocoon.xml.AbstractXMLPipe.endElement(AbstractXMLPipe.java:
112)
at
org.apache.cocoon.xml.xlink.XLinkPipe.endElement(XLinkPipe.java:211)
at
org.apache.cocoon.components.sax.XMLTeePipe.endElement(XMLTeePipe.java:
89)
at
org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDis
patcher.dispatch(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unkno
wn Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
Source)
at
org.apache.excalibur.xml.impl.JaxpParser.parse(JaxpParser.java:296)
at
org.apache.excalibur.xml.impl.JaxpParser.parse(JaxpParser.java:315)
at
org.apache.cocoon.components.source.SourceUtil.parse(SourceUtil.java:
211)
at
org.apache.cocoon.generation.FileGenerator.generate(FileGenerator.java:
117)
at
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipe
line.processXMLPipeline(AbstractCachingProcessingPipeline.java:235)
at
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process
(AbstractProcessingPipeline.java:478)
at
org.apache.cocoon.components.treeprocessor.sitemap.SerializeNode.invoke(
SerializeNode.java:134)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(AbstractParentProcessingNode.java:54)
at
org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.i
nvoke(PreparableMatchNode.java:112)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(AbstractParentProcessingNode.java:76)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(P
ipelineNode.java:138)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(AbstractParentProcessingNode.java:76)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(
PipelinesNode.java:95)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process
(ConcreteTreeProcessor.java:298)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process
(ConcreteTreeProcessor.java:241)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreePro
cessor.java:238)
at
org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(Moun
tNode.java:111)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(AbstractParentProcessingNode.java:76)
at
org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(Sel
ectNode.java:82)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(AbstractParentProcessingNode.java:76)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(P
ipelineNode.java:138)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(AbstractParentProcessingNode.java:76)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(
PipelinesNode.java:95)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process
(ConcreteTreeProcessor.java:298)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process
(ConcreteTreeProcessor.java:241)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreePro
cessor.java:238)
at org.apache.cocoon.Cocoon.process(Cocoon.java:646)
at
org.apache.cocoon.bean.CocoonWrapper.getPage(CocoonWrapper.java:441)
at
org.apache.cocoon.bean.CocoonBean.processTarget(CocoonBean.java:493)
at
org.apache.cocoon.bean.CocoonBean.process(CocoonBean.java:354)
at org.apache.cocoon.Main.main(Main.java:321)
====
SVG Transformations
===================
As stated above, I'm having problems with my svg transformations when
the content/dev/svg/ directory exists (above core-dump) but when it
doesn't exist, I get this error:
====
* [18/98] [13/43] 2.089s 12.8Kb dev/svg.html
X [0] dev/svg/paints.pdf BROKEN:
Can't find bundle for base name org.apache.fop.svg.resources.Messages,
locale en_US
====
FO Transformations
==================
Remove the above directories makes the error go away, but I get errors
for each *.fo file transformed by Forrest:
====
X [0] dev/fo/embedding.fo.pdf
BROKEN:
/Users/Shared/_WebDLs/_repos/xml-fop/src/documentation/content/dev/fo/
embedding.fo (No such file or directory)
====
As noted above, when this file exist (i.e., when content/ contains fo/
& dev/fo/ directories) I get the above Java core dump error. This seems
to be related to the java error core dump problem listed above. I
suspect fixing that problem will help me fix this one as well.
I tried untar'ing those directories but *deleting* the content/dev/svg/
directory, but it still gives a similar java core dump error:
* [22/95] [0/0] 2.946s 0b dev/fo/embedding.fo.pdf
Exception in thread "main" java.lang.NoSuchMethodError:
org.apache.batik.bridge.UnitProcessor.createContext(Lorg/apache/batik/
bridge/BridgeContext;Lorg/w3c/dom/Element;)Lorg/apache/batik/util/
UnitProcessor$Context;
at org.apache.fop.svg.SVGElement.layout(SVGElement.java:218)
at
org.apache.fop.fo.flow.InstreamForeignObject.layout(InstreamForeignObjec
t.java:251)
at org.apache.fop.fo.flow.Block.layout(Block.java:257)
at
org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:154)
at
org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:110)
at
org.apache.fop.fo.pagination.PageSequence.makePage(PageSequence.java:
400)
at
org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:338)
at
org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java:262)
at
org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:223)
at
org.apache.cocoon.xml.AbstractXMLPipe.endElement(AbstractXMLPipe.java:
112)
at
org.apache.cocoon.xml.AbstractXMLPipe.endElement(AbstractXMLPipe.java:
112)
at
org.apache.cocoon.xml.xlink.XLinkPipe.endElement(XLinkPipe.java:211)
at
org.apache.cocoon.components.sax.XMLTeePipe.endElement(XMLTeePipe.java:
89)
at
org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDis
patcher.dispatch(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unkno
wn Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
Source)
at
org.apache.excalibur.xml.impl.JaxpParser.parse(JaxpParser.java:296)
at
org.apache.excalibur.xml.impl.JaxpParser.parse(JaxpParser.java:315)
at
org.apache.cocoon.components.source.SourceUtil.parse(SourceUtil.java:
211)
at
org.apache.cocoon.generation.FileGenerator.generate(FileGenerator.java:
117)
at
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipe
line.processXMLPipeline(AbstractCachingProcessingPipeline.java:235)
at
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process
(AbstractProcessingPipeline.java:478)
at
org.apache.cocoon.components.treeprocessor.sitemap.SerializeNode.invoke(
SerializeNode.java:134)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(AbstractParentProcessingNode.java:54)
at
org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.i
nvoke(PreparableMatchNode.java:112)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(AbstractParentProcessingNode.java:76)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(P
ipelineNode.java:138)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(AbstractParentProcessingNode.java:76)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(
PipelinesNode.java:95)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process
(ConcreteTreeProcessor.java:298)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process
(ConcreteTreeProcessor.java:241)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreePro
cessor.java:238)
at
org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(Moun
tNode.java:111)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(AbstractParentProcessingNode.java:76)
at
org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(Sel
ectNode.java:82)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(AbstractParentProcessingNode.java:76)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(P
ipelineNode.java:138)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(AbstractParentProcessingNode.java:76)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(
PipelinesNode.java:95)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process
(ConcreteTreeProcessor.java:298)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process
(ConcreteTreeProcessor.java:241)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreePro
cessor.java:238)
at org.apache.cocoon.Cocoon.process(Cocoon.java:646)
at
org.apache.cocoon.bean.CocoonWrapper.getPage(CocoonWrapper.java:441)
at
org.apache.cocoon.bean.CocoonBean.processTarget(CocoonBean.java:493)
at
org.apache.cocoon.bean.CocoonBean.process(CocoonBean.java:354)
at org.apache.cocoon.Main.main(Main.java:321)
[1]
http://forrest.apache.org/docs/your-
project.html#adding_new_content_type_2
[2]
http://forrest.apache.org/docs/cap.html
[3]
http://cocoon.apache.org/2.1/userdocs/concepts/sitemap.html
[4]
http://forrest.apache.org/docs/upgrading_06.html#local-catalog
[5]
http://issues.apache.org/eyebrowse/ReadMsg?
listName=dev@forrest.apache.org&msgNo=15153
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Build Failed
Posted by Clay Leeds <cl...@medata.com>.
On Oct 30, 2004, at 7:52 PM, David Crossley wrote:
> Do 'man patch'. Peek at the top of the patch file
> to see what directory level you need to be in
> when you issue the command 'patch -p0 < my-patch.diff'
> Read 'man patch' about the -pNUM option:
> "Strip the smallest prefix containing NUM leading slashes
> from each file name found in the patch file".
Thanks... I'm still having problems but at least I was able to
successfully apply a PATCH.
BTW, many apologies for the long message & attachments...
>> Also, I've created a new
>> sitemap.xmap file (see my previous POST[1]), with most of the changes
>> I
>> think I need. I am still having problems with the dev/faq.xml and the
>> /compliance.xml file (which I'm assuming your fix4fop.diff file fixes
>> ;-)).
>
> I doubt that Cheche's patch will "fix" the compliance.html
> situation for you. Rather you need to follow the documentation
> to which we have referred, e.g. Provide your "Compliance DTD",
> configure the catalog entity resolver, etc. etc.
Still working on that. See below and attached sitemap.xmap after
slogging through this message.
On Oct 30, 2004, at 12:10 AM, David Crossley wrote:
>> <!-- ========================== FOP Additions
>> ========================== -->
>> <map:match pattern="body-compliance.xml">
>> <map:generate type="file-nolabel"
>> src="content/xdocs/compliance.xml"/>
>> <map:transform
>> src="resources/stylesheets/compliance2html.xsl"/>
>> <map:serialize type="xml"/>
>> </map:match>
>> <!-- ======================== End FOP Additions
>> ======================== -->
>
> That match is not correct anymore. Please follow the
> documentation your-project.html "Adding new content type".
Over the weekend and the last few days, I've spent a lot of time
fumbling attempting to follow the instructions to fix my custom
sitemap.xmap file (attached to this msg). Specifically, I was referring
to the "Adding a new content type (advanced)"[1] and the "SourceType
(content aware pipelines)"[2] pages.
NOTE1: [2] could be improved by showing the <map:action../> example in
context. Not knowing where it goes, when placing the current example
into my sitemap.xmap file I got an error. I figured it out by going
here[3] (except that's for Cocoon 2.1 but the 2.0 docs appear to be the
same). I've attached an improvement PATCH for [2]...
NOTE2: The PATCH also fixes a problem with a missing closing tag in
//map:action/sourcetype/document-element:
<sourcetype name="foo">
<document-element local-name="foo">
</sourcetype>
should be:
<sourcetype name="foo">
<document-element local-name="foo"/>
</sourcetype>
BUILD ERRORS
============
On another, related side note, I've tar'd up the sub-directories in
src/documentation/content (except xdocs/ of course!). When running
/forrest/ I get errors for each of the references to items in the fo/,
dev/, dev/fo/, dev/svg, & design/ directories. However, if I un-tar
them:
[clay@Clay-Leeds-Computer clay]$ ls -l
"/Users/Shared/_WebDLs/_repos/xml-fop/src/documentation/content"
total 208
drwxrwxrwx 3 clay 102 Nov 1 13:36 CVS.sandboxinfo
drwxrwxrwx 4 clay 136 Oct 26 20:27 design
-rw-rw-rw- 1 clay 86225 Oct 29 15:22 design.tar.gz
drwxrwxrwx 5 clay 170 Oct 27 15:40 dev
-rw-rw-rw- 1 clay 85908 Oct 29 15:22 dev.tar.gz
drwxrwxrwx 15 clay 510 Oct 27 15:32 fo
-rw-rw-rw- 1 clay 33272 Oct 29 15:22 fo.tar.gz
drwxrwxrwx 39 clay 1326 Oct 27 14:39 xdocs
I get a Java dump error that complains about svg stuff:
====
Cannot find CatalogManager.properties
^ dev/
^ design/
^ design/alt.design/
* [1/82] [82/85] 17.425s 21.7Kb linkmap.html
* [2/84] [3/30] 2.436s 12.3Kb design/alt.design/coroutines.html
* [3/84] [1/33] 1.652s 22.7Kb design/breakpos.html
* [4/84] [1/46] 1.255s 9.7Kb logocontest.html
* [5/83] [0/0] 0.905s 2.3Kb skin/basic.css
* [6/83] [1/47] 1.835s 12.5Kb extensions.html
* [7/83] [1/33] 1.344s 12.1Kb design/images.html
* [8/82] [0/0] 4.835s 9.1Kb design/alt.design/coroutines.pdf
* [9/83] [2/30] 1.246s 14.5Kb dev/implement.html
* [10/89] [7/26] 0.975s 12.9Kb
design/alt.design/properties/introduction.html
* [11/89] [1/49] 2.623s 13.5Kb configuration.html
* [12/89] [1/33] 1.604s 17.0Kb design/renderers.html
* [13/89] [1/30] 1.135s 14.1Kb dev/fonts.html
* [14/88] [0/0] 0.884s 14.1Kb dev/fonts.pdf
* [15/88] [1/45] 1.116s 10.7Kb todo.html
* [16/87] [0/0] 2.176s 5.9Kb todo.pdf
* [18/98] [13/43] 1.751s 12.8Kb dev/svg.html
X [0] dev/svg/paints.pdf BROKEN:
Can't find bundle for base name org.apache.fop.svg.resources.Messages,
locale en_US
* [20/96] [0/24] 0.666s 5.7Kb
design/alt.design/properties/PropertyConsts-class.html
* [21/96] [1/33] 1.228s 9.9Kb design/pdf-library.html
* [22/95] [0/0] 0.682s 0b dev/fo/embedding.fo.pdf
Exception in thread "main" java.lang.NoSuchMethodError:
org.apache.batik.bridge.UnitProcessor.createContext(Lorg/apache/batik/
bridge/BridgeContext;Lorg/w3c/dom/Element;)Lorg/apache/batik/util/
UnitProcessor$Context;
at org.apache.fop.svg.SVGElement.layout(SVGElement.java:218)
at
org.apache.fop.fo.flow.InstreamForeignObject.layout(InstreamForeignObjec
t.java:251)
at org.apache.fop.fo.flow.Block.layout(Block.java:257)
at
org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:154)
at
org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:110)
at
org.apache.fop.fo.pagination.PageSequence.makePage(PageSequence.java:
400)
at
org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:338)
at
org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java:262)
at
org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:223)
at
org.apache.cocoon.xml.AbstractXMLPipe.endElement(AbstractXMLPipe.java:
112)
at
org.apache.cocoon.xml.AbstractXMLPipe.endElement(AbstractXMLPipe.java:
112)
at
org.apache.cocoon.xml.xlink.XLinkPipe.endElement(XLinkPipe.java:211)
at
org.apache.cocoon.components.sax.XMLTeePipe.endElement(XMLTeePipe.java:
89)
at
org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDis
patcher.dispatch(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unkno
wn Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
Source)
at
org.apache.excalibur.xml.impl.JaxpParser.parse(JaxpParser.java:296)
at
org.apache.excalibur.xml.impl.JaxpParser.parse(JaxpParser.java:315)
at
org.apache.cocoon.components.source.SourceUtil.parse(SourceUtil.java:
211)
at
org.apache.cocoon.generation.FileGenerator.generate(FileGenerator.java:
117)
at
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipe
line.processXMLPipeline(AbstractCachingProcessingPipeline.java:235)
at
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process
(AbstractProcessingPipeline.java:478)
at
org.apache.cocoon.components.treeprocessor.sitemap.SerializeNode.invoke(
SerializeNode.java:134)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(AbstractParentProcessingNode.java:54)
at
org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.i
nvoke(PreparableMatchNode.java:112)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(AbstractParentProcessingNode.java:76)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(P
ipelineNode.java:138)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(AbstractParentProcessingNode.java:76)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(
PipelinesNode.java:95)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process
(ConcreteTreeProcessor.java:298)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process
(ConcreteTreeProcessor.java:241)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreePro
cessor.java:238)
at
org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(Moun
tNode.java:111)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(AbstractParentProcessingNode.java:76)
at
org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(Sel
ectNode.java:82)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(AbstractParentProcessingNode.java:76)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(P
ipelineNode.java:138)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(AbstractParentProcessingNode.java:76)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(
PipelinesNode.java:95)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process
(ConcreteTreeProcessor.java:298)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process
(ConcreteTreeProcessor.java:241)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreePro
cessor.java:238)
at org.apache.cocoon.Cocoon.process(Cocoon.java:646)
at
org.apache.cocoon.bean.CocoonWrapper.getPage(CocoonWrapper.java:441)
at
org.apache.cocoon.bean.CocoonBean.processTarget(CocoonBean.java:493)
at
org.apache.cocoon.bean.CocoonBean.process(CocoonBean.java:354)
at org.apache.cocoon.Main.main(Main.java:321)
====
SVG Transformations
===================
As stated above, I'm having problems with my svg transformations when
the content/dev/svg/ directory exists (above core-dump) but when it
doesn't exist, I get this error:
====
* [18/98] [13/43] 2.089s 12.8Kb dev/svg.html
X [0] dev/svg/paints.pdf BROKEN:
Can't find bundle for base name org.apache.fop.svg.resources.Messages,
locale en_US
====
FO Transformations
==================
Remove the above directories makes the error go away, but I get errors
for each *.fo file transformed by Forrest:
====
X [0] dev/fo/embedding.fo.pdf
BROKEN:
/Users/Shared/_WebDLs/_repos/xml-fop/src/documentation/content/dev/fo/
embedding.fo (No such file or directory)
====
As noted above, when this file exist (i.e., when content/ contains fo/
& dev/fo/ directories) I get the above Java core dump error. This seems
to be related to the java error core dump problem listed above. I
suspect fixing that problem will help me fix this one as well.
I tried untar'ing those directories but *deleting* the content/dev/svg/
directory, but it still gives a similar java core dump error:
* [22/95] [0/0] 2.946s 0b dev/fo/embedding.fo.pdf
Exception in thread "main" java.lang.NoSuchMethodError:
org.apache.batik.bridge.UnitProcessor.createContext(Lorg/apache/batik/
bridge/BridgeContext;Lorg/w3c/dom/Element;)Lorg/apache/batik/util/
UnitProcessor$Context;
at org.apache.fop.svg.SVGElement.layout(SVGElement.java:218)
at
org.apache.fop.fo.flow.InstreamForeignObject.layout(InstreamForeignObjec
t.java:251)
at org.apache.fop.fo.flow.Block.layout(Block.java:257)
at
org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:154)
at
org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:110)
at
org.apache.fop.fo.pagination.PageSequence.makePage(PageSequence.java:
400)
at
org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:338)
at
org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java:262)
at
org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:223)
at
org.apache.cocoon.xml.AbstractXMLPipe.endElement(AbstractXMLPipe.java:
112)
at
org.apache.cocoon.xml.AbstractXMLPipe.endElement(AbstractXMLPipe.java:
112)
at
org.apache.cocoon.xml.xlink.XLinkPipe.endElement(XLinkPipe.java:211)
at
org.apache.cocoon.components.sax.XMLTeePipe.endElement(XMLTeePipe.java:
89)
at
org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDis
patcher.dispatch(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unkno
wn Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
Source)
at
org.apache.excalibur.xml.impl.JaxpParser.parse(JaxpParser.java:296)
at
org.apache.excalibur.xml.impl.JaxpParser.parse(JaxpParser.java:315)
at
org.apache.cocoon.components.source.SourceUtil.parse(SourceUtil.java:
211)
at
org.apache.cocoon.generation.FileGenerator.generate(FileGenerator.java:
117)
at
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipe
line.processXMLPipeline(AbstractCachingProcessingPipeline.java:235)
at
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process
(AbstractProcessingPipeline.java:478)
at
org.apache.cocoon.components.treeprocessor.sitemap.SerializeNode.invoke(
SerializeNode.java:134)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(AbstractParentProcessingNode.java:54)
at
org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.i
nvoke(PreparableMatchNode.java:112)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(AbstractParentProcessingNode.java:76)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(P
ipelineNode.java:138)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(AbstractParentProcessingNode.java:76)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(
PipelinesNode.java:95)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process
(ConcreteTreeProcessor.java:298)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process
(ConcreteTreeProcessor.java:241)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreePro
cessor.java:238)
at
org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(Moun
tNode.java:111)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(AbstractParentProcessingNode.java:76)
at
org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(Sel
ectNode.java:82)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(AbstractParentProcessingNode.java:76)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(P
ipelineNode.java:138)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(AbstractParentProcessingNode.java:76)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(
PipelinesNode.java:95)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process
(ConcreteTreeProcessor.java:298)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process
(ConcreteTreeProcessor.java:241)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreePro
cessor.java:238)
at org.apache.cocoon.Cocoon.process(Cocoon.java:646)
at
org.apache.cocoon.bean.CocoonWrapper.getPage(CocoonWrapper.java:441)
at
org.apache.cocoon.bean.CocoonBean.processTarget(CocoonBean.java:493)
at
org.apache.cocoon.bean.CocoonBean.process(CocoonBean.java:354)
at org.apache.cocoon.Main.main(Main.java:321)
On Oct 30, 2004, at 12:10 AM, David Crossley wrote:
>> <!-- ========================= FOP Additions
>> ========================== -->
>> <map:match pattern="**/faq.pdf">
>> <map:generate type="file-nolabel"
>> src="content/xdocs/{1}/faq.xml"/>
>> <map:transform src="library/xslt/faq2document.xsl"
>> label="content"/>
>> <map:transform
>> src="skins/forrest-site/xslt/fo/document2fo.xsl"/>
>> <map:serialize type="fo2pdf"/>
>> </map:match>
>> <!-- ======================= End FOP Additions
>> ======================== -->
>
> I don't understand the purpose of that one. Leave it out
> and see if the core sitemaps handle the faq.pdf
This has been removed, and the Dev FAQ and the FOP FAQ now render
correctly. Thanks!
(NOTE: yeah, I feel silly about the CatalogManager.properties warning,
since I haven't figured out how to set it correctly either... At least
my VCR doesn't flash 12:00! This page[4] says "You can add a local
CatalogManager.properties to your project.classes-dir to define your
additional catalogs for DTDs and other entities." but there's no
example so I don't know what that file should look like--should I just
switch to project.classes-dir & /touch CatalogManager.properties/?
Anyway, 'If you do not add such a configuration file, then there will
be a harmless message on startup "CatalogManager.properties not
found".' 12:00... 12:00...;-))
[1]
http://forrest.apache.org/docs/your-
project.html#adding_new_content_type_2
[2]
http://forrest.apache.org/docs/cap.html
[3]
http://cocoon.apache.org/2.1/userdocs/concepts/sitemap.html
[4]
http://forrest.apache.org/docs/upgrading_06.html#local-catalog
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Build Failed
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> Juan Jose Pablos wrote:
> >>
> >> The main reason I hadn't committed yet, is that I don't want to
> >> 'break' the xml-fop web site. So, I've been biding my time, working
> >> towards a BUILD SUCCESSFUL. Once I get that (with all content and
> >> issues resolved--especially CRITICAL issues) I will update to the
> >> most recent changes and commit my changes to CVS. At least that is
> >> my plan. :-)
> >
> > Yes, and no, all the pain that you had with the sitemap.xmap have been
> > resolved by the patch that I had sent you a couple weeks ago.
>
> Thanks. I have not had the chance to update that (I never was able to
> figure out how to use a PATCH yet, anyway.
Do 'man patch'. Peek at the top of the patch file
to see what directory level you need to be in
when you issue the command 'patch -p0 < my-patch.diff'
Read 'man patch' about the -pNUM option:
"Strip the smallest prefix containing NUM leading slashes
from each file name found in the patch file".
> Also, I've created a new
> sitemap.xmap file (see my previous POST[1]), with most of the changes I
> think I need. I am still having problems with the dev/faq.xml and the
> /compliance.xml file (which I'm assuming your fix4fop.diff file fixes
> ;-)).
I doubt that Cheche's patch will "fix" the compliance.html
situation for you. Rather you need to follow the documentation
to which we have referred, e.g. Provide your "Compliance DTD",
configure the catalog entity resolver, etc. etc.
--David
> > Please revise that patch. I took me a while to compile it for you.
>
> I'll give it a shot. I'll revisit that diff file, and see if I can use
> it to fix my remaining problems. Would you diff my new sitemap.xmap
> with your best version and see how 'close' I am? Thank you very much!
>
> > Cheers,
> > Cheche
>
> [1]
> http://issues.apache.org/eyebrowse/ReadMsg?listId=65&msgNo=14675
>
> Web Maestro Clay
Re: xml-fop Build Failed
Posted by Clay Leeds <cl...@medata.com>.
On Oct 30, 2004, at 3:06 AM, Juan Jose Pablos wrote:
<snip>
>>>> I never was able to get that patch to work. However, since I've
>>>> been able to workaround the problem, I think I'm OK.
>>>
>>> It makes easier to help you out if you put the changes on a cvs so
>>> we can work in the same version..
>>>
>>> Cheers,
>>> Cheche
>>
>> The main reason I hadn't committed yet, is that I don't want to
>> 'break' the xml-fop web site. So, I've been biding my time, working
>> towards a BUILD SUCCESSFUL. Once I get that (with all content and
>> issues resolved--especially CRITICAL issues) I will update to the
>> most recent changes and commit my changes to CVS. At least that is
>> my plan. :-)
>
> Yes, and no, all the pain that you had with the sitemap.xmap have been
> resolved by the patch that I had sent you a couple weeks ago.
Thanks. I have not had the chance to update that (I never was able to
figure out how to use a PATCH yet, anyway. Also, I've created a new
sitemap.xmap file (see my previous POST[1]), with most of the changes I
think I need. I am still having problems with the dev/faq.xml and the
/compliance.xml file (which I'm assuming your fix4fop.diff file fixes
;-)).
> Please revise that patch. I took me a while to compile it for you.
I'll give it a shot. I'll revisit that diff file, and see if I can use
it to fix my remaining problems. Would you diff my new sitemap.xmap
with your best version and see how 'close' I am? Thank you very much!
> Cheers,
> Cheche
[1]
http://issues.apache.org/eyebrowse/ReadMsg?listId=65&msgNo=14675
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Build Failed
Posted by Juan Jose Pablos <ch...@apache.org>.
Clay Leeds wrote:
>
> http://cvs.apache.org/viewcvs.cgi/xml-fop/src/documentation/content/
> xdocs/site.xml
>
> Revision 1.1 - (view) (download) (as text) (annotate) - [select
> for diffs]
> Wed Oct 27 21:08:04 2004 UTC (40 hours, 38 minutes ago) by clay
> Branch: MAIN
> CVS Tags: HEAD
> added site.xml to prepare for forrest-0.6
>
Sorry my fault
I had tried to to find out if you had commited on the cvs with another
tag, and I was using it on the xdocs.
cvs update -A fixed.
>>> I never was able to get that patch to work. However, since I've
>>> been able to workaround the problem, I think I'm OK.
>>
>>
>> It makes easier to help you out if you put the changes on a cvs so
>> we can work in the same version..
>>
>> Cheers,
>> Cheche
>
>
> The main reason I hadn't committed yet, is that I don't want to
> 'break' the xml-fop web site. So, I've been biding my time, working
> towards a BUILD SUCCESSFUL. Once I get that (with all content and
> issues resolved--especially CRITICAL issues) I will update to the
> most recent changes and commit my changes to CVS. At least that is my
> plan. :-)
Yes, and no, all the pain that you had with the sitemap.xmap have been
resolved by the patch that I had sent you a couple weeks ago.
Please revise that patch. I took me a while to compile it for you.
Cheers,
Cheche
Re: xml-fop Build Failed
Posted by Clay Leeds <cl...@medata.com>.
NOTE: This message is a bit of an update on the status of the xml-fop
BUILD.
On Oct 28, 2004, at 8:58 AM, Clay Leeds wrote:
> I do have a few problems I need to resolve:
>
> CRITICAL:
> - compliance.html/.xml - *no* content (should look like[5])
> - design/alt.design/xml-parsing.html - *no* content (should look
> like[6])
> - all links in *navigation* from
> design/alt.design/properties/introduction.html
> display *no* content (click[7] and try links in site navigation menu)
These issues have not yet been resolved.
> MODERATE:
> - the tab corner images do not render
This appears to have been resolved.
> MINOR:
> - I'd like to figure out how to transform svg=>PNG+PDF on the fly. For
> now,
> I will be generating all PNG & PDF files and placing them in their
> respective resources/* or content/* directories.
This issue appears to have been resolved due to my attempts to "Upgrade
to 0.6" and update the sitemap.xmap to 0.6.
> - I think the breadcrumb should display below the tabs (although that
> may be skin-related)
I think this is skin-related... If I want to move it, I'll have to
choose another skin.
...more below...
On Oct 29, 2004, at 1:18 PM, Clay Leeds wrote:
> NOTE: Some of these may no longer be necessary for me to add (they
> might have been integrated into Forrest's default sitemap.xmap). For
> others, the Forrest Team may want to *make* them part of the default
> sitemap.xmap (svg => pdf)?
>
> [1]
> http://cvs.apache.org/viewcvs.cgi/xml-fop/src/documentation/
> sitemap.xmap?rev=1.17&view=markup
Keeping in mind the possibility that some sitemap.xmap pipelines &
transformation may not be necessary (if they are either already
integrated into Forrest, or could be integrated into Forrest--see NOTE:
above), I removed all items from the sitemap.xmap file which were
outside the 'FOP Additions' sections (being careful to retain the
integrity of all parent elements to the 'FOP Additions' sections).
The sitemap.xmap file I came up with is pasted at the bottom of this
message. Unfortunately, I ran /forrest/ and got a BUILD FAILED (I'm not
too concerned with this, as if I simply delete the sitemap.xmap file, I
get a BUILD SUCCESSFUL--albeit with CRITICAL issues--no content in the
compliance.html, xml-parsing.html, etc.). The BUILD FAILED I get
appears to be because of one file:
====
X [0] dev/faq.pdf BROKEN:
/Users/Shared/_WebDLs/_repos/xml-fop/src/documentation/library/xslt/
faq2document.xsl (No such file or directory)
====
I was receiving the following error with my first pass. I played with
sitemap.xmap a bit, and removed all @type="file-nolabel" from the
remaining <map:generate../> elements (@ pattern="body-compliance.xml",
@pattern="compliance.pdf", @pattern="**/faq.pdf"). This resolved the
problem (although I'm still having a problem with my faq.pdf file).
====
* [1/0] [0/0] 1.988s 0b linkmap.html
org.apache.avalon.framework.configuration.ConfigurationException: Type
'file-nolabel' does not exist for 'map:generate' at
file:/Users/Shared/_WebDLs/_repos/xml-fop/src/documentation/
sitemap.xmap:36:79
at
org.apache.cocoon.components.treeprocessor.DefaultTreeBuilder.getTypeFor
Statement(Unknown Source)
at
org.apache.cocoon.components.treeprocessor.sitemap.GenerateNodeBuilder.b
uildNode(Unknown Source)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNodeB
uilder.buildChildNodesList(Unknown Source)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNodeB
uilder.buildChildNodes(Unknown Source)
at
org.apache.cocoon.components.treeprocessor.sitemap.MatchNodeBuilder.buil
dNode(Unknown Source)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNodeBuilder.b
uildNode(Unknown Source)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNodeBuilder.
buildNode(Unknown Source)
at
org.apache.cocoon.components.treeprocessor.sitemap.SitemapNodeBuilder.bu
ildNode(Unknown Source)
at
org.apache.cocoon.components.treeprocessor.DefaultTreeBuilder.createTree
(Unknown Source)
at
org.apache.cocoon.components.treeprocessor.DefaultTreeBuilder.build(Unkn
own Source)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.buildConcretePr
ocessor(Unknown Source)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.setupConcretePr
ocessor(Unknown Source)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(Unknown
Source)
at
org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(Unkn
own Source)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(Unknown Source)
at
org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(Unk
nown Source)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(Unknown Source)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(U
nknown Source)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.
invokeNodes(Unknown Source)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(
Unknown Source)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process
(Unknown Source)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process
(Unknown Source)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(Unknown
Source)
at org.apache.cocoon.Cocoon.process(Unknown Source)
at org.apache.cocoon.bean.CocoonWrapper.getPage(Unknown Source)
at org.apache.cocoon.bean.CocoonBean.processTarget(Unknown
Source)
at org.apache.cocoon.bean.CocoonBean.process(Unknown Source)
at org.apache.cocoon.Main.main(Unknown Source)
X [0] linkmap.html BROKEN: URI not
found: Type 'file-nolabel' does not exist for 'map:generate' at
file:/Users/Shared/_WebDLs/_repos/xml-fop/src/documentation/
sitemap.xmap:36:79
Total time: 0 minutes 15 seconds, Site size: 0 Site pages: 1
BUILD FAILED
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
site.xml:43: Java returned: 1
Total time: 40 seconds
[clay@Clay-Leeds-Computer xml-fop]$
====
I also had a problem with svg2png generator, so I commented it out:
====
<!--
<map:match pattern="*/svg/*.png">
<map:generate src="content/xdocs/{1}/svg/{2}.svg"/>
<map:serialize type="svg2png"/>
</map:match>
-->
====
Here's what I believe will be the basis for the sitemap.xmap for
xml-fop:
====
<?xml version="1.0"?>
<map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0">
<!-- =========================== Components
================================ -->
<map:components>
<map:serializers default="html">
<!-- ========================== FOP Additions
========================== -->
<map:serializer name="svg2pdf" mime-type="application/pdf"
src="org.apache.cocoon.serialization.SVGSerializer">
<parameter name="transcoder"
value="org.apache.fop.svg.PDFTranscoder"/>
</map:serializer>
<!-- ======================= End FOP Additions
======================== -->
</map:serializers>
</map:components>
<!-- =========================== Views
=================================== -->
<map:views>
<map:view name="content" from-label="content">
<map:serialize type="xml"/>
</map:view>
<map:view name="pretty-content" from-label="content">
<map:transform src="library/xslt/simple-xml2html.xsl"/>
<map:serialize type="html"/>
</map:view>
<map:view name="links" from-position="last">
<map:transform src="library/xslt/filterlinks.xsl"/>
<map:serialize type="links"/>
</map:view>
</map:views>
<!-- =========================== Pipelines
================================= -->
<map:pipelines>
<!-- Utility Pipeline that creates the grammer for the Chaperon
Wiki -->
<!-- Pipeline that manages the internal URI space
For the external URI space manager, see the next pipeline.
Set it to internal-only="true" in production environment -->
<map:pipeline internal-only="false">
<!-- ========================== FOP Additions
========================== -->
<map:match pattern="body-compliance.xml">
<map:generate src="content/xdocs/compliance.xml"/>
<map:transform src="resources/stylesheets/compliance2html.xsl"/>
<map:serialize type="xml"/>
</map:match>
<!-- ======================== End FOP Additions
======================== -->
</map:pipeline>
<map:pipeline internal-only="false">
<!-- ========================== FOP Additions
========================== -->
<map:match pattern="*/svg/*.svg">
<map:read src="content/xdocs/{1}/svg/{2}.svg"
mime-type="image/svg"/>
</map:match>
<!--
<map:match pattern="*/svg/*.png">
<map:generate src="content/xdocs/{1}/svg/{2}.svg"/>
<map:serialize type="svg2png"/>
</map:match>
-->
<map:match pattern="*/svg/*.pdf">
<map:generate src="content/xdocs/{1}/svg/{2}.svg"/>
<map:serialize type="svg2pdf"/>
</map:match>
<map:match pattern="fo/*.fo">
<map:read src="content/xdocs/fo/{1}.fo" mime-type="text/xml"/>
</map:match>
<map:match pattern="fo/*.ent">
<map:read src="content/xdocs/fo/{1}.ent"
mime-type="text/plain"/>
</map:match>
<map:match pattern="fo/*.fo.pdf">
<map:generate src="content/xdocs/fo/{1}.fo"/>
<map:serialize type="fo2pdf"/>
</map:match>
<map:match pattern="**/fo/*.fo">
<map:read src="content/xdocs/{1}/fo/{2}.fo"
mime-type="text/xml"/>
</map:match>
<map:match pattern="**/fo/*.fo.pdf">
<map:generate src="content/xdocs/{1}/fo/{2}.fo"/>
<map:serialize type="fo2pdf"/>
</map:match>
<map:match pattern="compliance.pdf">
<map:generate src="content/xdocs/compliance.xml"/>
<map:transform src="resources/stylesheets/compliance2fo.xsl"
label="content"/>
<map:serialize type="fo2pdf"/>
</map:match>
<!-- ======================= End FOP Additions
======================== -->
<map:match pattern="**">
<!-- ========================= FOP Additions
========================== -->
<map:match pattern="**/faq.pdf">
<map:generate src="content/xdocs/{1}/faq.xml"/>
<map:transform src="library/xslt/faq2document.xsl"
label="content"/>
<map:transform
src="skins/forrest-site/xslt/fo/document2fo.xsl"/>
<map:serialize type="fo2pdf"/>
</map:match>
<!-- ======================= End FOP Additions
======================== -->
</map:match>
</map:pipeline>
</map:pipelines>
</map:sitemap>
====
As mentioned above, after running /forrest/ I am still getting one
error:
====
X [0] dev/faq.pdf BROKEN:
/Users/Shared/_WebDLs/_repos/xml-fop/src/documentation/library/xslt/
faq2document.xsl (No such file or directory)
====
In addition, I'm still missing all content in
xml-fop/build/site/compliance.html
xml-fop/build/site/design/alt.design/xml-parsing.html
My goal for these pages is to get something(!) between these two items:
<!--+
|start content
+-->
<!--+
|end content
+-->
:-)
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Build Failed
Posted by Clay Leeds <cl...@medata.com>.
On Oct 30, 2004, at 12:10 AM, David Crossley wrote:
> Clay Leeds wrote:
>> I'm looking for a bit of help getting xml-fop to output some custom
>> content types (they were in the old xml-fop/../../sitemap.xmap file).
>> Every item which matches the following pattern in this file[1] are
>> what
>> I think I need to add (stuff in the FOP Additions sections):
>>
>> </map:serializers>
>
> Why is this closing tag here?
Sorry, it was garbage. My next message contained the sitemap.xmap in
its entirety.
>> <!-- .. -->
>> <map:serializer name="svg2png" mime-type="image/png"
>> src="org.apache.cocoon.serialization.SVGSerializer"/>
>
> Don't need this svg2png here because it is in the core
> sitemaps.
As I expected. Thanks for the clarification.
>> <!-- ========================== FOP Additions
>> ========================== -->
>> <map:serializer name="svg2pdf" mime-type="application/pdf"
>> src="org.apache.cocoon.serialization.SVGSerializer">
>> <parameter name="transcoder"
>> value="org.apache.fop.svg.PDFTranscoder"/>
>> </map:serializer>
>> <!-- ======================= End FOP Additions
>> ======================== -->
>> </map:serializers>
>
> The svg2pdf serializer does not seem to be in the core
> sitemaps, so you need to declare it in yours.
OK.
>> <!-- ========================== FOP Additions
>> ========================== -->
>> <map:match pattern="body-compliance.xml">
>> <map:generate type="file-nolabel"
>> src="content/xdocs/compliance.xml"/>
>> <map:transform
>> src="resources/stylesheets/compliance2html.xsl"/>
>> <map:serialize type="xml"/>
>> </map:match>
>> <!-- ======================== End FOP Additions
>> ======================== -->
>
> That match is not correct anymore. Please follow the
> documentation your-project.html "Adding new content type".
Thanks. I'll put that in, and see how that improves things.
<snip/>
>> <!-- ========================= FOP Additions
>> ========================== -->
>> <map:match pattern="**/faq.pdf">
>> <map:generate type="file-nolabel"
>> src="content/xdocs/{1}/faq.xml"/>
>> <map:transform src="library/xslt/faq2document.xsl"
>> label="content"/>
>> <map:transform
>> src="skins/forrest-site/xslt/fo/document2fo.xsl"/>
>> <map:serialize type="fo2pdf"/>
>> </map:match>
>> <!-- ======================= End FOP Additions
>> ======================== -->
>
> I don't understand the purpose of that one. Leave it out
> and see if the core sitemaps handle the faq.pdf
I'll see. Keep in mind that the 'real' one I'm using is in the next
POST.
>> NOTE: Some of these may no longer be necessary for me to add (they
>> might have been integrated into Forrest's default sitemap.xmap). For
>> others, the Forrest Team may want to *make* them part of the default
>> sitemap.xmap (svg => pdf)?
>
> The only one that i can see that might need to go to the
> core is the svg2pdf serializer. For now, just declare it
> in your project sitemap.
Sounds good!
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Build Failed
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> I'm looking for a bit of help getting xml-fop to output some custom
> content types (they were in the old xml-fop/../../sitemap.xmap file).
> Every item which matches the following pattern in this file[1] are what
> I think I need to add (stuff in the FOP Additions sections):
>
> </map:serializers>
Why is this closing tag here?
> <!-- .. -->
> <map:serializer name="svg2png" mime-type="image/png"
> src="org.apache.cocoon.serialization.SVGSerializer"/>
Don't need this svg2png here because it is in the core
sitemaps.
> <!-- ========================== FOP Additions
> ========================== -->
> <map:serializer name="svg2pdf" mime-type="application/pdf"
> src="org.apache.cocoon.serialization.SVGSerializer">
> <parameter name="transcoder"
> value="org.apache.fop.svg.PDFTranscoder"/>
> </map:serializer>
> <!-- ======================= End FOP Additions
> ======================== -->
> </map:serializers>
The svg2pdf serializer does not seem to be in the core
sitemaps, so you need to declare it in yours.
> <!-- ========================== FOP Additions
> ========================== -->
> <map:match pattern="body-compliance.xml">
> <map:generate type="file-nolabel"
> src="content/xdocs/compliance.xml"/>
> <map:transform src="resources/stylesheets/compliance2html.xsl"/>
> <map:serialize type="xml"/>
> </map:match>
> <!-- ======================== End FOP Additions
> ======================== -->
That match is not correct anymore. Please follow the
documentation your-project.html "Adding new content type".
> and...
>
> <map:pipeline internal-only="false">
> <!-- ========================== FOP Additions
> ========================== -->
> <map:match pattern="*/svg/*.svg">
> <map:read src="content/xdocs/{1}/svg/{2}.svg"
> mime-type="image/svg"/>
> </map:match>
> <map:match pattern="*/svg/*.png">
> <map:generate src="content/xdocs/{1}/svg/{2}.svg"/>
> <map:serialize type="svg2png"/>
> </map:match>
> <map:match pattern="*/svg/*.pdf">
> <map:generate src="content/xdocs/{1}/svg/{2}.svg"/>
> <map:serialize type="svg2pdf"/>
> </map:match>
> <map:match pattern="fo/*.fo">
> <map:read src="content/xdocs/fo/{1}.fo" mime-type="text/xml"/>
> </map:match>
> <map:match pattern="fo/*.ent">
> <map:read src="content/xdocs/fo/{1}.ent"
> mime-type="text/plain"/>
> </map:match>
> <map:match pattern="fo/*.fo.pdf">
> <map:generate src="content/xdocs/fo/{1}.fo"/>
> <map:serialize type="fo2pdf"/>
> </map:match>
> <map:match pattern="**/fo/*.fo">
> <map:read src="content/xdocs/{1}/fo/{2}.fo"
> mime-type="text/xml"/>
> </map:match>
> <map:match pattern="**/fo/*.fo.pdf">
> <map:generate src="content/xdocs/{1}/fo/{2}.fo"/>
> <map:serialize type="fo2pdf"/>
> </map:match>
> <map:match pattern="compliance.pdf">
> <map:generate type="file-nolabel"
> src="content/xdocs/compliance.xml"/>
> <map:transform src="resources/stylesheets/compliance2fo.xsl"
> label="content"/>
> <map:serialize type="fo2pdf"/>
> </map:match>
> <!-- ======================= End FOP Additions
> ======================== -->
All of those seem to be needed in your project sitemap.
> <!-- ========================= FOP Additions
> ========================== -->
> <map:match pattern="**/faq.pdf">
> <map:generate type="file-nolabel"
> src="content/xdocs/{1}/faq.xml"/>
> <map:transform src="library/xslt/faq2document.xsl"
> label="content"/>
> <map:transform
> src="skins/forrest-site/xslt/fo/document2fo.xsl"/>
> <map:serialize type="fo2pdf"/>
> </map:match>
> <!-- ======================= End FOP Additions
> ======================== -->
I don't understand the purpose of that one. Leave it out
and see if the core sitemaps handle the faq.pdf
> NOTE: Some of these may no longer be necessary for me to add (they
> might have been integrated into Forrest's default sitemap.xmap). For
> others, the Forrest Team may want to *make* them part of the default
> sitemap.xmap (svg => pdf)?
The only one that i can see that might need to go to the
core is the svg2pdf serializer. For now, just declare it
in your project sitemap.
--David
> [1]
> http://cvs.apache.org/viewcvs.cgi/xml-fop/src/documentation/
> sitemap.xmap?rev=1.17&view=markup
>
> Web Maestro Clay
Re: xml-fop Build Failed
Posted by Clay Leeds <cl...@medata.com>.
I'm looking for a bit of help getting xml-fop to output some custom
content types (they were in the old xml-fop/../../sitemap.xmap file).
Every item which matches the following pattern in this file[1] are what
I think I need to add (stuff in the FOP Additions sections):
</map:serializers>
<!-- .. -->
<map:serializer name="svg2png" mime-type="image/png"
src="org.apache.cocoon.serialization.SVGSerializer"/>
<!-- ========================== FOP Additions
========================== -->
<map:serializer name="svg2pdf" mime-type="application/pdf"
src="org.apache.cocoon.serialization.SVGSerializer">
<parameter name="transcoder"
value="org.apache.fop.svg.PDFTranscoder"/>
</map:serializer>
<!-- ======================= End FOP Additions
======================== -->
</map:serializers>
<!-- ========================== FOP Additions
========================== -->
<map:match pattern="body-compliance.xml">
<map:generate type="file-nolabel"
src="content/xdocs/compliance.xml"/>
<map:transform src="resources/stylesheets/compliance2html.xsl"/>
<map:serialize type="xml"/>
</map:match>
<!-- ======================== End FOP Additions
======================== -->
and...
<map:pipeline internal-only="false">
<!-- ========================== FOP Additions
========================== -->
<map:match pattern="*/svg/*.svg">
<map:read src="content/xdocs/{1}/svg/{2}.svg"
mime-type="image/svg"/>
</map:match>
<map:match pattern="*/svg/*.png">
<map:generate src="content/xdocs/{1}/svg/{2}.svg"/>
<map:serialize type="svg2png"/>
</map:match>
<map:match pattern="*/svg/*.pdf">
<map:generate src="content/xdocs/{1}/svg/{2}.svg"/>
<map:serialize type="svg2pdf"/>
</map:match>
<map:match pattern="fo/*.fo">
<map:read src="content/xdocs/fo/{1}.fo" mime-type="text/xml"/>
</map:match>
<map:match pattern="fo/*.ent">
<map:read src="content/xdocs/fo/{1}.ent"
mime-type="text/plain"/>
</map:match>
<map:match pattern="fo/*.fo.pdf">
<map:generate src="content/xdocs/fo/{1}.fo"/>
<map:serialize type="fo2pdf"/>
</map:match>
<map:match pattern="**/fo/*.fo">
<map:read src="content/xdocs/{1}/fo/{2}.fo"
mime-type="text/xml"/>
</map:match>
<map:match pattern="**/fo/*.fo.pdf">
<map:generate src="content/xdocs/{1}/fo/{2}.fo"/>
<map:serialize type="fo2pdf"/>
</map:match>
<map:match pattern="compliance.pdf">
<map:generate type="file-nolabel"
src="content/xdocs/compliance.xml"/>
<map:transform src="resources/stylesheets/compliance2fo.xsl"
label="content"/>
<map:serialize type="fo2pdf"/>
</map:match>
<!-- ======================= End FOP Additions
======================== -->
<!-- ========================= FOP Additions
========================== -->
<map:match pattern="**/faq.pdf">
<map:generate type="file-nolabel"
src="content/xdocs/{1}/faq.xml"/>
<map:transform src="library/xslt/faq2document.xsl"
label="content"/>
<map:transform
src="skins/forrest-site/xslt/fo/document2fo.xsl"/>
<map:serialize type="fo2pdf"/>
</map:match>
<!-- ======================= End FOP Additions
======================== -->
NOTE: Some of these may no longer be necessary for me to add (they
might have been integrated into Forrest's default sitemap.xmap). For
others, the Forrest Team may want to *make* them part of the default
sitemap.xmap (svg => pdf)?
[1]
http://cvs.apache.org/viewcvs.cgi/xml-fop/src/documentation/
sitemap.xmap?rev=1.17&view=markup
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Build Failed
Posted by Clay Leeds <cl...@medata.com>.
On Oct 29, 2004, at 1:56 AM, Juan Jose Pablos wrote:
>> I'm sorry about that. I first got on the job of getting the xml-fop
>> web site updated ages ago (6 months?). Unfortunately, the files were
>> in disarray. Soon after I started I saw that forrest was moving to
>> 0.6, so I decided to make xml-fop ready for the transition to 0.6.
>> This meant creating a site.xml file, removing the book.xml files,
>> and making assorted other changes (skinconf.xml, forrest.properties,
>> tabs.xml, etc.).
>>
>> Over this long period of time, I must've forgotten that I was the one
>> who created 'site.xml' on my local drive. I have since become a
>> committer for xml-fop, and just committed site.xml.
>>
> I am not able to see this either. Are you commiting these changes on
> the same cvs?
http://cvs.apache.org/viewcvs.cgi/xml-fop/src/documentation/content/
xdocs/site.xml
Revision 1.1 - (view) (download) (as text) (annotate) - [select for
diffs]
Wed Oct 27 21:08:04 2004 UTC (40 hours, 38 minutes ago) by clay
Branch: MAIN
CVS Tags: HEAD
added site.xml to prepare for forrest-0.6
>> I never was able to get that patch to work. However, since I've been
>> able to workaround the problem, I think I'm OK.
>
> It makes easier to help you out if you put the changes on a cvs so we
> can work in the same version..
>
> Cheers,
> Cheche
The main reason I hadn't committed yet, is that I don't want to 'break'
the xml-fop web site. So, I've been biding my time, working towards a
BUILD SUCCESSFUL. Once I get that (with all content and issues
resolved--especially CRITICAL issues) I will update to the most recent
changes and commit my changes to CVS. At least that is my plan. :-)
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Build Failed
Posted by Juan Jose Pablos <ch...@che-che.com>.
Clay,
Good to know that you are able to get the a "BUILD SUCCESSFUL"
>>
>>> 2. cp src/documentation/content/xdocs/site.xml site.xml.bak
>>
>>
>> I am not able to see this file on the CVS version. please double
>> check that you have commited.
>
>
> I'm sorry about that. I first got on the job of getting the xml-fop
> web site updated ages ago (6 months?). Unfortunately, the files were
> in disarray. Soon after I started I saw that forrest was moving to
> 0.6, so I decided to make xml-fop ready for the transition to 0.6.
> This meant creating a site.xml file, removing the book.xml files, and
> making assorted other changes (skinconf.xml, forrest.properties,
> tabs.xml, etc.).
>
> Over this long period of time, I must've forgotten that I was the one
> who created 'site.xml' on my local drive. I have since become a
> committer for xml-fop, and just committed site.xml.
>
I am not able to see this either. Are you commiting these changes on the
same cvs?
>>> 4. patch -p1 < fix4fop.diff
>>
>>
>> I thought that you need to use p0
>> patch -p0 < fix4fop.diff
>>
>>> If you couldn't already tell, I'm new to applying patches. :-)
>>
>>
>> no problem, we are here to learn :-)
>
>
> I never was able to get that patch to work. However, since I've been
> able to workaround the problem, I think I'm OK.
It makes easier to help you out if you put the changes on a cvs so we
can work in the same version..
Cheers,
Cheche
Re: xml-fop Build Failed
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> I'm appending a response I received from Victor Mote (who I believe may
> have created the Compliance page), which was submitted to the FOP-DEV
> list and may shed some light on the Compliance page problem (and
> possibly the other "CRITICAL" problems as well).
>
> On Oct 28, 2004, at 8:58 AM, Clay Leeds wrote:
> > I do have a few problems I need to resolve:
> >
> > CRITICAL:
> > - compliance.html/.xml - *no* content (should look like[5])
> > - design/alt.design/xml-parsing.html - *no* content (should look
> > like[6])
> > - all links in *navigation* from
> > design/alt.design/properties/introduction.html
> > display *no* content (click[7] and try links in site navigation menu)
>
> On Oct 28, 2004, at 2:43 PM, Victor Mote wrote:
> > OK. The compliance page uses a different DTD than any of the other
> > pages:
> > xml-fop/src/documentation/resources/schema/dtd/compliance-v10.dtd
> >
> > One possibility to consider is changing it to the standard format.
> > That is
> > probably possible, but you may have to give some things up to get it
> > done.
> > My recollection is that I always decided it was worth it to use the
> > non-standard way. Also, the standard DTD may be better now than it was.
> >
> > A different DTD means that it must use a different stylesheet also.
> > This is
> > likely the crux of the problem. The process of telling Forrest/Cocoon
> > about
> > the compliance stylesheet is probably broken. The easiest solution is
> > probably to ask on the Forrest user list. They were always extremely
> > helpful
> > in solving these problems. When I was working with Forrest, it
> > required a
> > decent understanding of Cocoon, but their newer versions might hide
> > some of
> > that. Look in one of the "sitemap" files (sorry -- I don't remember
> > which
> > one is the
> > current one):
> > xml-fop/src/documentation
> >
> > In each you'll see a section entitled "FOP Additions" (line 295 in
> > sitemap.xmap, and line 257 in sitemap-0.5.xmap). That shows you the
> > location
> > of the stylesheets as well (there is another entry later for the to-pdf
> > stylesheet). Find out where the equivalent sitemap for the new version
> > is
> > and how to mimic the logic that is here.
> >
> > That's about all I can think of to tell you. Good luck.
> >
> > Victor Mote
>
> I think this means I'll have to find the FOP-ADDITIONS sections of the
> 'old' xml-fop sitemap.xmap file and put those sections into a new
> sitemap.xmap. Hopefully I'm on the right track, and when I try to
> tackle this tomorrow I'll have better clarity on it.
That sounds correct. The "upgrading 06" document warns
about this. With the new Forrest, all of that should be
much easier.
http://forrest.apache.org/docs/upgrading_06.html#sitemap
--
David Crossley
Re: xml-fop Build Failed
Posted by Clay Leeds <cl...@medata.com>.
I'm appending a response I received from Victor Mote (who I believe may
have created the Compliance page), which was submitted to the FOP-DEV
list and may shed some light on the Compliance page problem (and
possibly the other "CRITICAL" problems as well).
On Oct 28, 2004, at 8:58 AM, Clay Leeds wrote:
> I do have a few problems I need to resolve:
>
> CRITICAL:
> - compliance.html/.xml - *no* content (should look like[5])
> - design/alt.design/xml-parsing.html - *no* content (should look
> like[6])
> - all links in *navigation* from
> design/alt.design/properties/introduction.html
> display *no* content (click[7] and try links in site navigation menu)
On Oct 28, 2004, at 2:43 PM, Victor Mote wrote:
> OK. The compliance page uses a different DTD than any of the other
> pages:
> xml-fop/src/documentation/resources/schema/dtd/compliance-v10.dtd
>
> One possibility to consider is changing it to the standard format.
> That is
> probably possible, but you may have to give some things up to get it
> done.
> My recollection is that I always decided it was worth it to use the
> non-standard way. Also, the standard DTD may be better now than it was.
>
> A different DTD means that it must use a different stylesheet also.
> This is
> likely the crux of the problem. The process of telling Forrest/Cocoon
> about
> the compliance stylesheet is probably broken. The easiest solution is
> probably to ask on the Forrest user list. They were always extremely
> helpful
> in solving these problems. When I was working with Forrest, it
> required a
> decent understanding of Cocoon, but their newer versions might hide
> some of
> that. Look in one of the "sitemap" files (sorry -- I don't remember
> which
> one is the
> current one):
> xml-fop/src/documentation
>
> In each you'll see a section entitled "FOP Additions" (line 295 in
> sitemap.xmap, and line 257 in sitemap-0.5.xmap). That shows you the
> location
> of the stylesheets as well (there is another entry later for the to-pdf
> stylesheet). Find out where the equivalent sitemap for the new version
> is
> and how to mimic the logic that is here.
>
> That's about all I can think of to tell you. Good luck.
>
> Victor Mote
I think this means I'll have to find the FOP-ADDITIONS sections of the
'old' xml-fop sitemap.xmap file and put those sections into a new
sitemap.xmap. Hopefully I'm on the right track, and when I try to
tackle this tomorrow I'll have better clarity on it.
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Build Failed
Posted by Clay Leeds <cl...@medata.com>.
On Oct 28, 2004, at 10:22 AM, Scherler, Thorsten wrote:
> Clay Leeds escribió:
>> On Oct 28, 2004, at 9:35 AM, Scherler, Thorsten wrote:
>> I don't know. Where are they supposed to be? erm... wait a minute. I
>> hadn't copied the files up. Is there an 'easy' way to copy a
>> directory (with sub-directories) over sftp? I'm thinking of something
>> like 'cp -R xml-fop'... It took me a long time to copy all of the
>> directories (and sub directories!) over, and as you could see, I
>> missed some things...
>
> Are you on Linux? I use konqueror for that. :) There you can just use
> sftp://minotaurus.apache.org/~clay and copy everything like in a
> filesystem. I hate the scp commands. ;-)
[OT - copying files to minotaur.a.o]
I'm on Mac OS X, and was using sftp. I suppose I could use some sort of
FTP program like CyberDuck. Unless you've got a better idea! :-p
>>> Try to use the following sequence that the published strip has the
>>> same color like the selected tab:
>>> <color name="published" value="#000000"/>
>>> <color name="navstrip" value="#E5E4D9" font="#000000"/>
>> I've modified skinconf.xml so that 'published' and 'navstrip'
>> sections of the <!-- Lenya using pelt--> section are uncommented (but
>> feedback still is):
>> -->
>> <color name="published" value="#000000"/>
>> <!--
>> <color name="feedback" value="#4C6C8F" font="#FFFFFF"
>> align="center"/>
>> -->
>> <color name="navstrip" value="#E5E4D9" font="#000000"/>
>> <!--
>> Is that what you mean? Is there one or two .css file(s) I can change
>> on www.a.o/~clay/xml-fop/ to show this, or must I run /forrest/ again
>> and copy all the files over again?
>
> second option. :(
D'oh!
> But you can as well hack the css directly. This will be the
> profile.css. Just add something like the following on the end:
> #publishedStrip {
> color: #000000;
> background: #E5E4D9;
> }
>
> HTH
> thorsten
I'm currently logged in via ssh, and notice the following in
profile.css:
#publishedStrip {
color: #FFFFFF;
background: #4C6C8F;
}
#publishedStrip {
color: #000000;
background: #E5E4D9;
}
(#publishedStrip is in there twice! and the 2nd time it is
correct--shouldn't that override the incorrect version?)
Anyway, I deleted the upper version, and it all appears fine to me...
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Build Failed
Posted by "Scherler, Thorsten" <th...@apache.org>.
Clay Leeds escribió:
> On Oct 28, 2004, at 9:35 AM, Scherler, Thorsten wrote:
>
>
> I don't know. Where are they supposed to be? erm... wait a minute. I
> hadn't copied the files up. Is there an 'easy' way to copy a directory
> (with sub-directories) over sftp? I'm thinking of something like 'cp -R
> xml-fop'... It took me a long time to copy all of the directories (and
> sub directories!) over, and as you could see, I missed some things...
>
Are you on Linux? I use konqueror for that. :) There you can just use
sftp://minotaurus.apache.org/~clay and copy everything like in a
filesystem. I hate the scp commands. ;-)
>> Try to use the following sequence that the published strip has the
>> same color like the selected tab:
>> <color name="published" value="#000000"/>
>> <color name="navstrip" value="#E5E4D9" font="#000000"/>
>
>
> I've modified skinconf.xml so that 'published' and 'navstrip' sections
> of the <!-- Lenya using pelt--> section are uncommented (but feedback
> still is):
> -->
> <color name="published" value="#000000"/>
> <!--
> <color name="feedback" value="#4C6C8F" font="#FFFFFF" align="center"/>
> -->
> <color name="navstrip" value="#E5E4D9" font="#000000"/>
> <!--
>
> Is that what you mean? Is there one or two .css file(s) I can change on
> www.a.o/~clay/xml-fop/ to show this, or must I run /forrest/ again and
> copy all the files over again?
>
second option. :(
But you can as well hack the css directly. This will be the profile.css.
Just add something like the following on the end:
#publishedStrip {
color: #000000;
background: #E5E4D9;
}
HTH
thorsten
Re: xml-fop Build Failed
Posted by Clay Leeds <cl...@medata.com>.
On Oct 28, 2004, at 5:07 PM, David Crossley wrote:
> Clay Leeds wrote:
>>
>> ....I
>> hadn't copied the files up. Is there an 'easy' way to copy a directory
>> (with sub-directories) over sftp? I'm thinking of something like 'cp
>> -R
>> xml-fop'... It took me a long time to copy all of the directories (and
>> sub directories!) over, and as you could see, I missed some things...
>
> I just tar.gz them locally, then scp that to
> www.apache.org and ssh to the server and
> unpack them into my demo space.
>
> --
> David Crossley
D'oh! That was so easy... I hadn't thought of it! Thanks!
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Build Failed
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
>
> ....I
> hadn't copied the files up. Is there an 'easy' way to copy a directory
> (with sub-directories) over sftp? I'm thinking of something like 'cp -R
> xml-fop'... It took me a long time to copy all of the directories (and
> sub directories!) over, and as you could see, I missed some things...
I just tar.gz them locally, then scp that to
www.apache.org and ssh to the server and
unpack them into my demo space.
--
David Crossley
Re: xml-fop Build Failed
Posted by Clay Leeds <cl...@medata.com>.
On Oct 28, 2004, at 9:35 AM, Scherler, Thorsten wrote:
> Clay Leeds escribió:
>> I achieved a BUILD SUCCESSFUL running forrest-0.7-dev. Whew! You can
>> check out the site here[1]. The files used to create the FOP site
>> (tar.gzip'd) are here[2].
>
> CONGRATULATION, dude!!!
>
> :)
>
> Nice to hear.
Thanks!
> BTW where are the round images in [1].
I don't know. Where are they supposed to be? erm... wait a minute. I
hadn't copied the files up. Is there an 'easy' way to copy a directory
(with sub-directories) over sftp? I'm thinking of something like 'cp -R
xml-fop'... It took me a long time to copy all of the directories (and
sub directories!) over, and as you could see, I missed some things...
> Try to use the following sequence that the published strip has the
> same color like the selected tab:
> <color name="published" value="#000000"/>
> <color name="navstrip" value="#E5E4D9" font="#000000"/>
I've modified skinconf.xml so that 'published' and 'navstrip' sections
of the <!-- Lenya using pelt--> section are uncommented (but feedback
still is):
-->
<color name="published" value="#000000"/>
<!--
<color name="feedback" value="#4C6C8F" font="#FFFFFF"
align="center"/>
-->
<color name="navstrip" value="#E5E4D9" font="#000000"/>
<!--
Is that what you mean? Is there one or two .css file(s) I can change on
www.a.o/~clay/xml-fop/ to show this, or must I run /forrest/ again and
copy all the files over again?
> Good on ya,mate!
>
> thorsten
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Build Failed
Posted by "Scherler, Thorsten" <th...@apache.org>.
Clay Leeds escribió:
> I achieved a BUILD SUCCESSFUL running forrest-0.7-dev. Whew! You can
> check out the site here[1]. The files used to create the FOP site
> (tar.gzip'd) are here[2].
>
CONGRATULATION, dude!!!
:)
Nice to hear.
BTW where are the round images in [1]. Try to use the following sequence
that the published strip has the same color like the selected tab:
<color name="published" value="#000000"/>
<color name="navstrip" value="#E5E4D9" font="#000000"/>
Good on ya,mate!
thorsten
Re: xml-fop Build Failed
Posted by Clay Leeds <cl...@medata.com>.
I achieved a BUILD SUCCESSFUL running forrest-0.7-dev. Whew! You can
check out the site here[1]. The files used to create the FOP site
(tar.gzip'd) are here[2].
I still have a few problems I'm trying to resolve
see below...
On Oct 22, 2004, at 3:27 AM, Juan Jose Pablos wrote:
> Clay Leeds wrote:
>> I am having problems with your instructions. I'm having problems
>> running
>> the patch file fix4fop.diff.
>
>
>> 2. cp src/documentation/content/xdocs/site.xml site.xml.bak
>
> I am not able to see this file on the CVS version. please double check
> that you have commited.
I'm sorry about that. I first got on the job of getting the xml-fop web
site updated ages ago (6 months?). Unfortunately, the files were in
disarray. Soon after I started I saw that forrest was moving to 0.6, so
I decided to make xml-fop ready for the transition to 0.6. This meant
creating a site.xml file, removing the book.xml files, and making
assorted other changes (skinconf.xml, forrest.properties, tabs.xml,
etc.).
Over this long period of time, I must've forgotten that I was the one
who created 'site.xml' on my local drive. I have since become a
committer for xml-fop, and just committed site.xml.
>> 4. patch -p1 < fix4fop.diff
>
> I thought that you need to use p0
> patch -p0 < fix4fop.diff
>> If you couldn't already tell, I'm new to applying patches. :-)
>
> no problem, we are here to learn :-)
I never was able to get that patch to work. However, since I've been
able to workaround the problem, I think I'm OK.
I do have a few problems I need to resolve:
CRITICAL:
- compliance.html/.xml - *no* content (should look like[5])
- design/alt.design/xml-parsing.html - *no* content (should look
like[6])
- all links in *navigation* from
design/alt.design/properties/introduction.html
display *no* content (click[7] and try links in site navigation menu)
MODERATE:
- the tab corner images do not render
MINOR:
- I'd like to figure out how to transform svg=>PNG+PDF on the fly. For
now,
I will be generating all PNG & PDF files and placing them in their
respective resources/* or content/* directories.
- I think the breadcrumb should display below the tabs (although that
may be skin-related)
[1]
http://www.apache.org/~clay/xml-fop/
[2]
http://www.apache.org/~clay/xml-fop_041027.tar.gz
[3]
http://marc.theaimsgroup.com/?l=forrest-dev&m=109157457703573&w=2
[4]
http://issues.apache.org/eyebrowse/ReadMsg?
listName=dev@forrest.apache.org&msgNo=14540
[5]
http://xml.apache.org/fop/compliance.html
[6]
http://xml.apache.org/fop/design/alt.design/xml-parsing.html
[7]
http://www.apache.org/~clay/xml-fop/design/alt.design/properties/
introduction.html
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Build Failed
Posted by Clay Leeds <cl...@medata.com>.
Cheche,
On Oct 22, 2004, at 9:40 AM, Juan Jose Pablos wrote:
> Clay,
>> I was not planning to commit any changes until I have this fixed.
>> Which file were you referring to?
>> - xml-fop/site.xml.bak is just a backup of
>> src/documentation/content/xdocs/site.xml
>> - then I rm src/documentation/content/xdocs/site.xml
>> - then I touch src/documentation/content/xdocs/site.xml
> I have not been able to see any site.xml file on the current version
> of cvs:
>
> http://cvs.apache.org/viewcvs.cgi/xml-fop/
> Are we talking about the same cvs?
>
> Cheers,
> Cheche
Curiouser and curiouser! I didn't believe it, but a quick look at:
http://cvs.apache.org/viewcvs.cgi/xml-fop/src/documentation/content/
xdocs/?hideattic=0#dirlist
...confirms it! (Sorry for doubting you!). I even looked 'in the attic'
and it's not there either! Strange! Well, perhaps it's not there
because I created it locally ages ago, when I first took over the task
of maintaining the web site (it was a long time ago, and it was when I
first started 'playing' with Forrest.
In any case, the site.xml file exists in the xml-fop_new.zip file on my
personal web space[1], and also as site.xml.bak[2]. (Speaking of which,
how does an Apache Committer get space on Apache.org/~clay/ for this
type of thing? I didn't see anything in the Committers FAQ[3]).
[1]
http://homepage.mac.com/webmaestro/xml-fop/xml-fop_new.zip
[2]
http://homepage.mac.com/webmaestro/xml-fop/site.xml.bak
[3]
http://www.apache.org/dev/committers.html
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Build Failed
Posted by Juan Jose Pablos <ch...@che-che.com>.
Clay,
> I was not planning to commit any changes until I have this fixed. Which
> file were you referring to?
> - xml-fop/site.xml.bak is just a backup of
> src/documentation/content/xdocs/site.xml
> - then I rm src/documentation/content/xdocs/site.xml
> - then I touch src/documentation/content/xdocs/site.xml
>
I have not been able to see any site.xml file on the current version of cvs:
http://cvs.apache.org/viewcvs.cgi/xml-fop/
Are we talking about the same cvs?
Cheers,
Cheche
Re: xml-fop Build Failed
Posted by Clay Leeds <cl...@medata.com>.
On Oct 22, 2004, at 3:27 AM, Juan Jose Pablos wrote:
> Clay Leeds wrote:
>> I am having problems with your instructions. I'm having problems
>> running
>> the patch file fix4fop.diff.
>
>> 2. cp src/documentation/content/xdocs/site.xml site.xml.bak
>
> I am not able to see this file on the CVS version. please double check
> that you have commited.
I was not planning to commit any changes until I have this fixed. Which
file were you referring to?
- xml-fop/site.xml.bak is just a backup of
src/documentation/content/xdocs/site.xml
- then I rm src/documentation/content/xdocs/site.xml
- then I touch src/documentation/content/xdocs/site.xml
(I could've just mv'd src/documentation/content/xdocs/site.xml
site.xml.bak, but I wanted the security of backing up the file before I
deleted it--although it is in CVS so I didn't really need to...)
>> 4. patch -p1 < fix4fop.diff
>
> I thought that you need to use p0
> patch -p0 < fix4fop.diff
Thanks! But I still get errors. (I tried that before I e-mailed last
time, but got errors then too.):
====
[clay@Clay-Leeds-Computer xml-fop]$ patch -p0 < fix4fop.diff
can't find file to patch at input line 7
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|? src/documentation/content/xdocs/site.xml
|Index: src/documentation/sitemap.xmap
|===================================================================
|RCS file: /home/cvspublic/xml-fop/src/documentation/sitemap.xmap,v
|retrieving revision 1.17
|diff -r1.17 sitemap.xmap
--------------------------
File to patch:
====
Then I continued, creating a sitemap.xmap... and here's the rest of the
terminal window:
====
[clay@Clay-Leeds-Computer xml-fop]$ touch src/documentation/sitemap.xmap
[clay@Clay-Leeds-Computer xml-fop]$ patch -p0 < fix4fop.diff
patching file src/documentation/sitemap.xmap
Reversed (or previously applied) patch detected! Assume -R? [n] n
Apply anyway? [n] y
Hunk #1 FAILED at 22.
Hunk #2 FAILED at 24.
Hunk #3 FAILED at 28.
Hunk #4 FAILED at 32.
Hunk #5 FAILED at 33.
Hunk #6 FAILED at 34.
Hunk #7 FAILED at 40.
Hunk #8 FAILED at 42.
Hunk #9 FAILED at 75.
9 out of 9 hunks FAILED -- saving rejects to file
src/documentation/sitemap.xmap.rej
patching file src/documentation/content/xdocs/DnI/properties.xml
Hunk #1 FAILED at 2245.
1 out of 1 hunk FAILED -- saving rejects to file
src/documentation/content/xdocs/DnI/properties.xml.rej
[clay@Clay-Leeds-Computer xml-fop]$ patch -p0 < fix4fop.diff
patching file src/documentation/sitemap.xmap
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
9 out of 9 hunks ignored -- saving rejects to file
src/documentation/sitemap.xmap.rej
patching file src/documentation/content/xdocs/DnI/properties.xml
Hunk #1 FAILED at 2245.
1 out of 1 hunk FAILED -- saving rejects to file
src/documentation/content/xdocs/DnI/properties.xml.rej
[clay@Clay-Leeds-Computer xml-fop]$
====
It doesn't look like it really did anything. I recognize the 'Hunk #1
FAILED at 2245.' as a place where I changed properties.xml for an
entity problem.
>> If you couldn't already tell, I'm new to applying patches. :-)
>
> no problem, we are here to learn :-)
Thanks! I appreciate your gentle touch!
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Build Failed
Posted by Juan Jose Pablos <ch...@che-che.com>.
Clay Leeds wrote:
> I am having problems with your instructions. I'm having problems running
> the patch file fix4fop.diff.
> 2. cp src/documentation/content/xdocs/site.xml site.xml.bak
I am not able to see this file on the CVS version. please double check
that you have commited.
> 4. patch -p1 < fix4fop.diff
I thought that you need to use p0
patch -p0 < fix4fop.diff
>
> If you couldn't already tell, I'm new to applying patches. :-)
no problem, we are here to learn :-)
Re: xml-fop Build Failed
Posted by Clay Leeds <cl...@medata.com>.
Juan Jose Pablos said:
> Juan Jose Pablos wrote:
>> Clay Leeds wrote:
>>> On Oct 19, 2004, at 10:59 AM, Juan Jose Pablos wrote:
>>>> Clay,
>>>>
>>>>> * [90/32] [0/0] 0.608s 0b dev/fo/embedding.pdf
>>>>> Exception in thread "main" java.lang.NoSuchMethodError:
>>>>> org.apache.batik.bridge.UnitProcessor.createContext(Lorg/apache/
>>>>> batik/
>>>>> bridge/BridgeContext;Lorg/w3c/dom/Element;)Lorg/apache/batik/util/
>>>>> UnitProcessor$Context;
>>
>> I am able to see this error as well.
>>
>> I am going to try to rebuild the jars with cocoon 2.2
>>
>> Stay tuned :-)
>
> I have managed to work around this java error. I do not why but the
> fop-0.20.5.jar library on the cocoon 2.2.0-dev tree is diferent to the
> one in the forrest distribution.
>
> So
> 1) I will upgrade fop-0.20.5.jar and batik-all-1.5.1.jar from the
> cocoon-2.2.0-dev tree in the next hour unless someone has any objection.
>
> 2) Clay
> Please apply this patch and upgrade to the svn version
>
> (you need to create an empty site.xml for this to work.
>
> Cheers,
> Cheche
I am having problems with your instructions. I'm having problems running
the patch file fix4fop.diff.
My steps:
1. switch to xml-fop/
2. cp src/documentation/content/xdocs/site.xml site.xml.bak
3. touch src/documentation/content/xdocs/site.xml
4. patch -p1 < fix4fop.diff
I also am not certain I understand the part which indicates I need a blank
site.xml file. Is it because of the -p1 portion?
If you couldn't already tell, I'm new to applying patches. :-)
Thanks!
--
Clay Leeds - cleeds@medata.com
Web Developer - Medata, Inc. - http://www.medata.com
PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: xml-fop Build Failed
Posted by Juan Jose Pablos <ch...@che-che.com>.
Juan Jose Pablos wrote:
> Clay Leeds wrote:
>
>> On Oct 19, 2004, at 10:59 AM, Juan Jose Pablos wrote:
>>
>>> Clay,
>>>
>>>> * [90/32] [0/0] 0.608s 0b dev/fo/embedding.pdf
>>>> Exception in thread "main" java.lang.NoSuchMethodError:
>>>> org.apache.batik.bridge.UnitProcessor.createContext(Lorg/apache/
>>>> batik/
>>>> bridge/BridgeContext;Lorg/w3c/dom/Element;)Lorg/apache/batik/util/
>>>> UnitProcessor$Context;
>>>
>>>
>
> I am able to see this error as well.
>
> I am going to try to rebuild the jars with cocoon 2.2
>
> Stay tuned :-)
>
I have managed to work around this java error. I do not why but the
fop-0.20.5.jar library on the cocoon 2.2.0-dev tree is diferent to the
one in the forrest distribution.
So
1) I will upgrade fop-0.20.5.jar and batik-all-1.5.1.jar from the
cocoon-2.2.0-dev tree in the next hour unless someone has any objection.
2) Clay
Please apply this patch and upgrade to the svn version
(you need to create an empty site.xml for this to work.
Cheers,
Cheche
Re: xml-fop Build Failed
Posted by Juan Jose Pablos <ch...@che-che.com>.
Clay Leeds wrote:
> On Oct 19, 2004, at 10:59 AM, Juan Jose Pablos wrote:
>
>> Clay,
>>
>>> * [90/32] [0/0] 0.608s 0b dev/fo/embedding.pdf
>>> Exception in thread "main" java.lang.NoSuchMethodError:
>>> org.apache.batik.bridge.UnitProcessor.createContext(Lorg/apache/
>>> batik/
>>> bridge/BridgeContext;Lorg/w3c/dom/Element;)Lorg/apache/batik/util/
>>> UnitProcessor$Context;
>>
I am able to see this error as well.
I am going to try to rebuild the jars with cocoon 2.2
Stay tuned :-)
Cheers,
cheche
Re: xml-fop Build Failed
Posted by Clay Leeds <cl...@medata.com>.
On Oct 19, 2004, at 10:59 AM, Juan Jose Pablos wrote:
> Clay,
>
>> * [90/32] [0/0] 0.608s 0b dev/fo/embedding.pdf
>> Exception in thread "main" java.lang.NoSuchMethodError:
>> org.apache.batik.bridge.UnitProcessor.createContext(Lorg/apache/
>> batik/
>> bridge/BridgeContext;Lorg/w3c/dom/Element;)Lorg/apache/batik/util/
>> UnitProcessor$Context;
>
>
> This type of error is typical When you mix jar version.
> Could you make sure that the batik.jar that you are using is the same
> that we use in the forrest distribution?
I'll double-check this. Thanks for the heads up!
> I am downloading the fop cvs and I am getting a diferent error:
>
> validate-xdocs:
> /home/cheche/xml/xml-fop/src/documentation/content/xdocs/DnI/
> properties.xml:2245:39: The entity "rarr" was referenced, but not
> declared.
>
> Do you know much about this?
>
> Cheers,
> Cheche
Yeah, I know. I forgot to indicate that in my POST. Sorry!
One of our esteemed FOP COMMITTERs is documenting the Design and
Implementation of FOP (Thanks Simon!). There was an entity he added to
his documentation, which is based on DocBook. Unfortunately, he added
→ (which looks like -->) into his documentation. I 'fixed' the
problem so the build could continue by swapping out → with -->
[1]
http://marc.theaimsgroup.com/?l=fop-dev&m=106979236016078&w=2
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: DocBook and numeric entity declaration
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> David Crossley wrote:
> > Clay Leeds wrote:
> >> Changing → to → is an acceptable solution. The xml-fop
> >> /forrest/ build does not error out when it tries to validate
> >> 'properties.xml'. I made the change and checked it in.
> >>
> >> I'd also like to resolve the error in Forrest if possible, so the rest
> >> of this POST deals with that.
> >
> > I do not see any such problem. I have a test seed site
> > that includes a couple of Full DocBook examples using the
> > DocBook XSL and also processes them via Forrest's default
> > docbook2document XSL. I can add an example character entity
> > to them → and everything works perfectly:
> > 'forrest validate' is fine
> > and with 'forrest run' i see the entity rendered as "->"
> > as expected.
>
> Is it:
> - just /forrest/ which doesn't render it?
Everything is fine. Sorry, i should have said so above.
It is important to test all situations.
> - did you render xml-fop/ yesterday (after I changed it to its numeric
> entity: →)?
I am not using xml-fop xdocs. This is my own stuff.
> - is this your own example which you added an example character entity?
That is correct.
> > This is my document type declaration.
> > <!DOCTYPE article
> > PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
> > "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
> >
> > Forrest resolves all the DTDs and *.ent properly.
> >
> > More below ...
> >
> >> I suspect the problem is related to the fact that properties.xml
> >> references a dtd like this:
> >>
> >> <!--
> >> <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
> >> "docbookx.dtd">
> >> -->
> >>
> >> A couple of things I note here:
> >> 1. It's commented out
> >
> > I don't understand. How can it ever work if it is commented out?
>
> I suspected this may be the problem, but wasn't sure.
Definitely the problem. The whole system depends on
the Public Identifier, i.e. Forrest's validation,
the entity resolver, and the sitemaps for Cocoon to decide
which pipeline to apply to each different document type.
> However, even if
> it's not commented out, the docbookx.dtd file doesn't exist in that
> directory, so I'm thinking it would still fail.
That is why we have the Catalog Entity Resolver. Please try
the suggestion below. If the resolver is failing, then you will
get the wrong messages and if you are using full URLs as the
System Identifier then you would see network traffic going
to get the DTD on every parse. http://ngrep.sf.net/
'ngrep dtd'.
> > Remember, if you suspect issues with the catalog entity resolver
> > then raise the verbosity level in src/core/context/WEB-INF/cocoon.xconf
> > for the <entity-resolver> component. Then watch the messages
> > when Cocoon starts and during 'forrest run'. You should see stacks
> > of messages and then "Resolved public: ..." when the forrest catalog
> > finds each DTD and *.ent file.
> > --David
>
> Actually, I didn't remember. Glad you brought that up.
I am going to enhance/create FAQs for this.
> BTW, perhaps
> forrest could be improved with a note in the output/BUILD FAILED
> indicating this tip.
If we can, yes.
--
David Crossley
Re: DocBook and numeric entity declaration
Posted by Clay Leeds <cl...@medata.com>.
On Oct 21, 2004, at 10:45 PM, David Crossley wrote:
> Clay Leeds wrote:
>> Changing → to → is an acceptable solution. The xml-fop
>> /forrest/ build does not error out when it tries to validate
>> 'properties.xml'. I made the change and checked it in.
>>
>> I'd also like to resolve the error in Forrest if possible, so the rest
>> of this POST deals with that.
>
> I do not see any such problem. I have a test seed site
> that includes a couple of Full DocBook examples using the
> DocBook XSL and also processes them via Forrest's default
> docbook2document XSL. I can add an example character entity
> to them → and everything works perfectly:
> 'forrest validate' is fine
> and with 'forrest run' i see the entity rendered as "->"
> as expected.
Is it:
- just /forrest/ which doesn't render it?
- did you render xml-fop/ yesterday (after I changed it to its numeric
entity: →)?
- is this your own example which you added an example character entity?
> This is my document type declaration.
> <!DOCTYPE article
> PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
> "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
>
> Forrest resolves all the DTDs and *.ent properly.
>
> More below ...
>
>> I suspect the problem is related to the fact that properties.xml
>> references a dtd like this:
>>
>> <!--
>> <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
>> "docbookx.dtd">
>> -->
>>
>> A couple of things I note here:
>> 1. It's commented out
>
> I don't understand. How can it ever work if it is commented out?
I suspected this may be the problem, but wasn't sure. However, even if
it's not commented out, the docbookx.dtd file doesn't exist in that
directory, so I'm thinking it would still fail.
> Remember, if you suspect issues with the catalog entity resolver
> then raise the verbosity level in src/core/context/WEB-INF/cocoon.xconf
> for the <entity-resolver> component. Then watch the messages
> when Cocoon starts and during 'forrest run'. You should see stacks
> of messages and then "Resolved public: ..." when the forrest catalog
> finds each DTD and *.ent file.
> --David
Actually, I didn't remember. Glad you brought that up. BTW, perhaps
forrest could be improved with a note in the output/BUILD FAILED
indicating this tip.
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: DocBook and numeric entity declaration
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> Juan Jose Pablos wrote:
> > I am downloading the fop cvs and I am getting a diferent error:
> >
> > validate-xdocs:
> > /home/cheche/xml/xml-fop/src/documentation/content/xdocs/DnI/
> > properties.xml:2245:39: The entity "rarr" was referenced, but not
> > declared.
> >
> > Do you know much about this?
>
> I've found out a little more about this problem. Apparently Forrest (or
> Cocoon?) is not properly validating DocBook character entities. There
> may be a couple of reasons for this
>
> Here's the most recent msg[1] I sent to fop-dev on the subject:
>
> On Oct 20, 2004, at 11:32 AM, Simon Pepping wrote:
> > Clay,
> >
> > I am a bit surprised. The docbook dtd clearly defines the entity
> > → in iso-num.ent:
> > <!ENTITY rarr "→"> <!-- RIGHTWARDS DOUBLE ARROW -->
> > Why does not the forrest build see this? Does it not read the DTD?
> >
> > I do not like character entities in decimal numbers. I can never
> > figure out what they refer to. IMO character codes should be given in
> > hexadecimal notation; all Unicode documentation uses this. Then it
> > becomes → as shown above.
> >
> > Regards, Simon
>
> Changing → to → is an acceptable solution. The xml-fop
> /forrest/ build does not error out when it tries to validate
> 'properties.xml'. I made the change and checked it in.
>
> I'd also like to resolve the error in Forrest if possible, so the rest
> of this POST deals with that.
I do not see any such problem. I have a test seed site
that includes a couple of Full DocBook examples using the
DocBook XSL and also processes them via Forrest's default
docbook2document XSL. I can add an example character entity
to them → and everything works perfectly:
'forrest validate' is fine
and with 'forrest run' i see the entity rendered as "->"
as expected.
This is my document type declaration.
<!DOCTYPE article
PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
Forrest resolves all the DTDs and *.ent properly.
More below ...
> I suspect the problem is related to the fact that properties.xml
> references a dtd like this:
>
> <!--
> <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
> "docbookx.dtd">
> -->
>
> A couple of things I note here:
> 1. It's commented out
I don't understand. How can it ever work if it is commented out?
Remember, if you suspect issues with the catalog entity resolver
then raise the verbosity level in src/core/context/WEB-INF/cocoon.xconf
for the <entity-resolver> component. Then watch the messages
when Cocoon starts and during 'forrest run'. You should see stacks
of messages and then "Resolved public: ..." when the forrest catalog
finds each DTD and *.ent file.
--David
> 2. this is a relative/local link, but the 'docbookx.dtd' is not local
> (I also tried
> 'http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd'
> and 'http://www.oasis-open.org/docbook/xml/4.2/' and as expected
> neither
> works.)
> 3. fwiw, iso-num.ent is at
> http://www.oasis-open.org/docbook/xml/4.2/ent/iso-num.ent
>
> I'm not very 'up' on DocBook, so this may be how it's 'supposed' to
> work. Nevertheless, → is the only thing in 'properties.xml' that
> doesn't validate during the /forrest/ run (unless I replace → with
> → or →).
>
> Web Maestro Clay
>
> [1]
> http://marc.theaimsgroup.com/?l=fop-dev&m=109839392707948&w=2
DocBook and numeric entity declaration (was Re: xml-fop Build Failed)
Posted by Clay Leeds <cl...@medata.com>.
Forgive me but portions of this e-mail have been cross-posted...
On Oct 19, 2004, at 10:59 AM, Juan Jose Pablos wrote:
> I am downloading the fop cvs and I am getting a diferent error:
>
> validate-xdocs:
> /home/cheche/xml/xml-fop/src/documentation/content/xdocs/DnI/
> properties.xml:2245:39: The entity "rarr" was referenced, but not
> declared.
>
> Do you know much about this?
>
> Cheers,
> Cheche
I've found out a little more about this problem. Apparently Forrest (or
Cocoon?) is not properly validating DocBook character entities. There
may be a couple of reasons for this
Here's the most recent msg[1] I sent to fop-dev on the subject:
On Oct 20, 2004, at 11:32 AM, Simon Pepping wrote:
> Clay,
>
> I am a bit surprised. The docbook dtd clearly defines the entity
> → in iso-num.ent:
> <!ENTITY rarr "→"> <!-- RIGHTWARDS DOUBLE ARROW -->
> Why does not the forrest build see this? Does it not read the DTD?
>
> I do not like character entities in decimal numbers. I can never
> figure out what they refer to. IMO character codes should be given in
> hexadecimal notation; all Unicode documentation uses this. Then it
> becomes → as shown above.
>
> Regards, Simon
Changing → to → is an acceptable solution. The xml-fop
/forrest/ build does not error out when it tries to validate
'properties.xml'. I made the change and checked it in.
I'd also like to resolve the error in Forrest if possible, so the rest
of this POST deals with that.
I suspect the problem is related to the fact that properties.xml
references a dtd like this:
<!--
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"docbookx.dtd">
-->
A couple of things I note here:
1. It's commented out
2. this is a relative/local link, but the 'docbookx.dtd' is not local
(I also tried
'http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd'
and 'http://www.oasis-open.org/docbook/xml/4.2/' and as expected
neither
works.)
3. fwiw, iso-num.ent is at
http://www.oasis-open.org/docbook/xml/4.2/ent/iso-num.ent
I'm not very 'up' on DocBook, so this may be how it's 'supposed' to
work. Nevertheless, → is the only thing in 'properties.xml' that
doesn't validate during the /forrest/ run (unless I replace → with
→ or →).
Web Maestro Clay
[1]
http://marc.theaimsgroup.com/?l=fop-dev&m=109839392707948&w=2
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml-fop Build Failed
Posted by Juan Jose Pablos <ch...@che-che.com>.
Clay,
> * [90/32] [0/0] 0.608s 0b dev/fo/embedding.pdf
> Exception in thread "main" java.lang.NoSuchMethodError:
> org.apache.batik.bridge.UnitProcessor.createContext(Lorg/apache/batik/
> bridge/BridgeContext;Lorg/w3c/dom/Element;)Lorg/apache/batik/util/
> UnitProcessor$Context;
This type of error is typical When you mix jar version.
Could you make sure that the batik.jar that you are using is the same
that we use in the forrest distribution?
I am downloading the fop cvs and I am getting a diferent error:
validate-xdocs:
/home/cheche/xml/xml-fop/src/documentation/content/xdocs/DnI/properties.xml:2245:39:
The entity "rarr" was referenced, but not declared.
Do you know much about this?
Cheers,
Cheche