You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Ross Gardler <rg...@apache.org> on 2004/02/12 23:07:26 UTC
Problems with FOP site (Was: Re: Sites built from sites)
Clay Leeds wrote:
> I want to update the FOP web site to fix the breadcrumb problem, and to
> add Whole Site PDF. I do not get errors using the most current version
> from the following "snapshot" link (HEAD branch), but the result (on my
> system) is always "MyProj":
>
> http://cvs.apache.org/snapshots/xml-fop/
OK I tried building with the last nights CVS Head of Forrest and the
most recent snapshot of FOP. First of all I got the problem with
skinconf recently discussed on this list. So I patched your Skinconf.xml
file (sent offlist)
Then I had a problem with your sitemap.xmap. It doesn't parse correctly.
I was going to patch this but there is a large number of customisations
all over the place so didn't even try. I just thought I'd give it a go
with the default Forrst sitemap (I renamed your
old one to get it out of the way, also renamed the 0.5 version of the
sitemap that was in there).
This worked OK.
Your breadcrumbs are correct and the site look fine with "forrest run".
What you need to do is verify that any needed customisations in your
original xmap are copied across (I've not looked to see if any are
actually needed).
>
> I get errors stating 'site.xml is not valid'. Heh... actually, I don't
> think the file exists, as they're using sitemap.xmap instead.
You have to have either site.xml or book.xml. sitemap.xmap is nothing to
do with these files, it manages how the site is built.
> Anyway, I
> have problems generating the FOP web site from this src (Maintenance
> branch, which I'm using mainly for testing Forrest):
>
> http://apache.get-software.com/xml/fop/fop-0.20.5-src.tar.gz
I should have read your mail properly before starting. I didn't try the
above with this branch.
> At this point, I'd like to be able to build locally, the current FOP web
> site. Once there, I'd like to fix the problems indicated above.
Try the above, if it doesn't work I'll have another look using the
maintenance version of FOP.
Ross
Re: Problems with FOP site (Was: Re: Sites built from sites)
Posted by Clay Leeds <cl...@medata.com>.
On Feb 12, 2004, at 2:07 PM, Ross Gardler wrote:
> Clay Leeds wrote:
>> I want to update the FOP web site to fix the breadcrumb problem, and
>> to
>> add Whole Site PDF. I do not get errors using the most current version
>> from the following "snapshot" link (HEAD branch), but the result (on
>> my
>> system) is always "MyProj":
>> http://cvs.apache.org/snapshots/xml-fop/
>
> OK I tried building with the last nights CVS Head of Forrest and the
> most recent snapshot of FOP. First of all I got the problem with
> skinconf recently discussed on this list. So I patched your
> Skinconf.xml file (sent offlist)
>
> Then I had a problem with your sitemap.xmap. It doesn't parse
> correctly. I was going to patch this but there is a large number of
> customisations all over the place so didn't even try. I just thought
> I'd give it a go with the default Forrst sitemap (I renamed your
> old one to get it out of the way, also renamed the 0.5 version of the
> sitemap that was in there).
Wow! I was able to get it to work (without copying the default Forrest
sitemap files!). It still has weird breadcrumb trails (myGroup >
myProject which never actually grows when I click a link), but I should
be able to figure out how to fix that now.
> This worked OK.
>
> Your breadcrumbs are correct and the site look fine with "forrest run".
Again, I typed "forrest seed" and hit [enter] (actually, it was
"forrest -Dskip.contentcheck=yes seed" since I alread have a src/ dir),
then "forrest" and hit [enter]. I haven't tried "forrest run" and then
[enter]. How will that change things?
> What you need to do is verify that any needed customisations in your
> original xmap are copied across (I've not looked to see if any are
> actually needed).
That will take some time, as I don't understand the difference between
what it "should be" and what it "is". I'll probably start off with
doing a "diff" and seeing which lines are changed. Thanks for the tip,
though.
>> I get errors stating 'site.xml is not valid'. Heh... actually, I don't
>> think the file exists, as they're using sitemap.xmap instead.
>
> You have to have either site.xml or book.xml. sitemap.xmap is nothing
> to do with these files, it manages how the site is built.
I'm beginning to think the culprit may've been a problem in the source
I'd downloaded to test with, since a more recent build seems to've
worked better (although it may've been the skinconf.xml issue).
>> Anyway, I
>> have problems generating the FOP web site from this src (Maintenance
>> branch, which I'm using mainly for testing Forrest):
>> http://apache.get-software.com/xml/fop/fop-0.20.5-src.tar.gz
>
> I should have read your mail properly before starting. I didn't try
> the above with this branch.
>
>> At this point, I'd like to be able to build locally, the current FOP
>> web
>> site. Once there, I'd like to fix the problems indicated above.
>
> Try the above, if it doesn't work I'll have another look using the
> maintenance version of FOP.
>
> Ross
So, now that I've generated a site, I can play a bit more and see what
happens. The tips and/or tricks you've recommended are appreciated.
Web Maestro Clay
Re: Problems with FOP site (Was: Re: Sites built from sites)
Posted by Clay Leeds <cl...@medata.com>.
Ross Gardler said:
> Tomcat as nothing to do with the forrest run target. Jetty is the
> Servlet engine that is used. You don;t need Tomcat naywhere near your
> machine. Just give it a go.
>
> Ross
I already tried 'forrest run' (before I sent that msg). Didn't work. Until
I fix the problem introduced when installing Java 1.4.2, I doubt I'll get
it working. The fact that TomCat isn't involved is nice to know, though.
--
Clay Leeds - cleeds@medata.com
Web Developer - Medata, Inc. - http://www.medata.com
PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: Problems with FOP site (Was: Re: Sites built from sites)
Posted by Ross Gardler <rg...@apache.org>.
Clay Leeds wrote:
> On Feb 13, 2004, at 9:53 AM, Ross Gardler wrote:
>
>> Clay Leeds wrote:
>>
>>> Ross Gardler said:
>>>
<snip/>
>>
>> Well this should build the breadcrumbs OK and since they work in a run
>> they should work in a site. Run just starts up a version of Jetty and
>> you can point your browser at http://localhost:8888 to see you site,
>> much faster than building the site from scratch. You can also edit the
>> src, refresh the browser and see the changes.
>
>
> Actually, I've got problems with my TomCat, since upgrading my Mac OS X
> box to Java 1.4.2. As a result, I probably won't be able to do the Jetty
> thing until that's resolved. In any case, I've also done some research
> on "forrest run" and found out how it works. Looks promising, but I
> think I'll just patiently use 'forrest" instead.
Tomcat as nothing to do with the forrest run target. Jetty is the
Servlet engine that is used. You don;t need Tomcat naywhere near your
machine. Just give it a go.
Ross
Re: Problems with FOP site (Was: Re: Sites built from sites)
Posted by Clay Leeds <cl...@medata.com>.
On Feb 13, 2004, at 9:53 AM, Ross Gardler wrote:
> Clay Leeds wrote:
>> Ross Gardler said:
>>> Your breadcrumbs are correct and the site look fine with "forrest
>>> run".
>> This might be one of the problems I was running into: I never did a
>> "forrest run". Since I don't know what 'Jetty' and 'jetty.run' are, I
>> never tried those... I did the following from the command line:
>> forrest -projecthelp
>> forrest seed
>> forrest site
>
> Well this should build the breadcrumbs OK and since they work in a run
> they should work in a site. Run just starts up a version of Jetty and
> you can point your browser at http://localhost:8888 to see you site,
> much faster than building the site from scratch. You can also edit the
> src, refresh the browser and see the changes.
Actually, I've got problems with my TomCat, since upgrading my Mac OS X
box to Java 1.4.2. As a result, I probably won't be able to do the
Jetty thing until that's resolved. In any case, I've also done some
research on "forrest run" and found out how it works. Looks promising,
but I think I'll just patiently use 'forrest" instead.
Thanks for the recommendation!
Web Maestro Clay
Re: Problems with FOP site (Was: Re: Sites built from sites)
Posted by Ross Gardler <rg...@apache.org>.
Clay Leeds wrote:
> On Feb 13, 2004, at 9:53 AM, Ross Gardler wrote:
>
>> Clay Leeds wrote:
>>
>>> Ross Gardler said:
>>>
>>>> Your breadcrumbs are correct and the site look fine with "forrest run".
>>>
<snip/>
> As for the breadcrumb, I was successful at changing 'mygroup >
> myProject" to "apache > xml.apache" but I still need to append " > FOP"
> to that. Here's the relevant portion of skinconf.xml:
The skinconf.xml bit you copied is not the relevant part. you need is:
<!-- Some skins use this to form a 'breadcrumb trail' of links. If
you don't
want these, set the attributes to blank. The DTD purposefully
requires them.
-->
<trail>
<link1 name="apache" href="http://www.apache.org/"/>
<link2 name="xml.apache" href="http://xml.apache.org/"/>
<link3 name="" href=""/>
</trail>
just change the name and href elements in link1, link2 and link3 as you
require.
<snip/>
>> I just took a look. The site is using the old book.xml method. This
>> will still work fine. But it will be worth moving to the new site.xml
>> method. It's easier to manage. But one step at a time. Stick with
>> book.xml for now.
>
>
> Is there an XSL stylesheet which'll help me move from book.xml to site.xml?
No, this would not be possible because of the way site.xml works.
However, it is really quite simple and documented reasonably well. But I
wouldn't touch this until you have everything working the way you want.
Ross
Re: Problems with FOP site (Was: Re: Sites built from sites)
Posted by Clay Leeds <cl...@medata.com>.
On Feb 13, 2004, at 9:53 AM, Ross Gardler wrote:
> Clay Leeds wrote:
>> Ross Gardler said:
>>> Your breadcrumbs are correct and the site look fine with "forrest
>>> run".
>> This might be one of the problems I was running into: I never did a
>> "forrest run". Since I don't know what 'Jetty' and 'jetty.run' are, I
>> never tried those... I did the following from the command line:
>> forrest -projecthelp
>> forrest seed
>> forrest site
>
> Well this should build the breadcrumbs OK and since they work in a run
> they should work in a site. Run just starts up a version of Jetty and
> you can point your browser at http://localhost:8888 to see you site,
> much faster than building the site from scratch. You can also edit the
> src, refresh the browser and see the changes.
Ahh... I'll try that and play with it a bit. So I can edit the src .xml
files, then refresh the browser and it'll update the .html file I'm
viewing? Cool!
As for the breadcrumb, I was successful at changing 'mygroup >
myProject" to "apache > xml.apache" but I still need to append " > FOP"
to that. Here's the relevant portion of skinconf.xml:
<searchsite-domain>xml.apache.org</searchsite-domain>
<searchsite-name>Apache XML</searchsite-name>
<!-- mandatory project logo
skin: forrest-site renders it at the top -->
<project-name>FOP</project-name>
<project-description>Apache FOP Project</project-description>
<project-url>http://xml.apache.org/fop/</project-url>
<project-logo>images/project.png</project-logo>
<!-- Alternative static image:
<project-logo>images/project-logo.gif</project-logo> -->
<!-- optional group logo
skin: forrest-site renders it at the top-left corner -->
<group-name>Apache XML</group-name>
<group-description>Apache XML Projects</group-description>
<group-url>http://xml.apache.org/</group-url>
<group-logo>images/group-logo.gif</group-logo>
<!-- Alternative static image:
<group-logo>images/group-logo.gif</group-logo> -->
(NOTE: that it does not include "apache" and "www.apache.org" anywhere
in there... Where does that come from?
>>> What you need to do is verify that any needed customisations in your
>>> original xmap are copied across (I've not looked to see if any are
>>> actually needed).
>> I'll check that out with the developers. Unfortunately the primary
>> developer who worked (I think) on this portion is no longer actively
>> contributing, although I may be able to contact him.
>
> You should be able to worki it out by reading the sitemap.xmap file.
> Fortuneatly the customisations are clearly marked. You can then check
> to see if there is now an equivalent in Forrest.
Sounds good.
>>>> I get errors stating 'site.xml is not valid'. Heh... actually, I
>>>> don't
>>>> think the file exists, as they're using sitemap.xmap instead.
>>>
>>> You have to have either site.xml or book.xml. sitemap.xmap is
>>> nothing to
>>> do with these files, it manages how the site is built.
>> As far as I can tell, this file does not exist in any of the
>> distributions
>> to which I have access (did you find it in your download src?):
>
> I just took a look. The site is using the old book.xml method. This
> will still work fine. But it will be worth moving to the new site.xml
> method. It's easier to manage. But one step at a time. Stick with
> book.xml for now.
Is there an XSL stylesheet which'll help me move from book.xml to
site.xml?
>> That's why I thought perhaps they were using sitemap.xmap instead.
>
> sitemap.xmap governs how each request is managed. see
> http://xml.apache.org/forrest/sitemap-ref.html
I read up on sitemap-ref, but since I was having problems getting the
site to build in the first place, I found it difficult to understand
how my changes would affect the site. Now that I can build something,
it should move easier.
Web Maestro Clay
Re: Problems with FOP site (Was: Re: Sites built from sites)
Posted by Ross Gardler <rg...@apache.org>.
Clay Leeds wrote:
> Ross Gardler said:
>>Your breadcrumbs are correct and the site look fine with "forrest run".
>
>
> This might be one of the problems I was running into: I never did a
> "forrest run". Since I don't know what 'Jetty' and 'jetty.run' are, I
> never tried those... I did the following from the command line:
>
> forrest -projecthelp
> forrest seed
> forrest site
Well this should build the breadcrumbs OK and since they work in a run
they should work in a site. Run just starts up a version of Jetty and
you can point your browser at http://localhost:8888 to see you site,
much faster than building the site from scratch. You can also edit the
src, refresh the browser and see the changes.
>>What you need to do is verify that any needed customisations in your
>>original xmap are copied across (I've not looked to see if any are
>>actually needed).
>
>
> I'll check that out with the developers. Unfortunately the primary
> developer who worked (I think) on this portion is no longer actively
> contributing, although I may be able to contact him.
You should be able to worki it out by reading the sitemap.xmap file.
Fortuneatly the customisations are clearly marked. You can then check to
see if there is now an equivalent in Forrest.
>
>
>>>I get errors stating 'site.xml is not valid'. Heh... actually, I don't
>>>think the file exists, as they're using sitemap.xmap instead.
>>
>>You have to have either site.xml or book.xml. sitemap.xmap is nothing to
>>do with these files, it manages how the site is built.
>
>
> As far as I can tell, this file does not exist in any of the distributions
> to which I have access (did you find it in your download src?):
I just took a look. The site is using the old book.xml method. This will
still work fine. But it will be worth moving to the new site.xml method.
It's easier to manage. But one step at a time. Stick with book.xml for now.
> That's why I thought perhaps they were using sitemap.xmap instead.
sitemap.xmap governs how each request is managed. see
http://xml.apache.org/forrest/sitemap-ref.html
> Thanks for your help! I should've asked for help *months* ago!
Well once we have you up to speed with Forrest you can come back and
help us too ;-), in the meantime I'm sure the FOP folk will appreciate
you fixing their site,
Ross
Re: Problems with FOP site (Was: Re: Sites built from sites)
Posted by Clay Leeds <cl...@medata.com>.
Ross Gardler said:
> Clay Leeds wrote:
>> I want to update the FOP web site to fix the breadcrumb problem, and to
>> add Whole Site PDF. I do not get errors using the most current version
>> from the following "snapshot" link (HEAD branch), but the result (on my
>> system) is always "MyProj":
>>
>> http://cvs.apache.org/snapshots/xml-fop/
>
> OK I tried building with the last nights CVS Head of Forrest and the
> most recent snapshot of FOP. First of all I got the problem with
> skinconf recently discussed on this list. So I patched your Skinconf.xml
> file (sent offlist)
Got it. I'll try it out. Thanks!
> Then I had a problem with your sitemap.xmap. It doesn't parse correctly.
> I was going to patch this but there is a large number of customisations
> all over the place so didn't even try. I just thought I'd give it a go
> with the default Forrst sitemap (I renamed your
> old one to get it out of the way, also renamed the 0.5 version of the
> sitemap that was in there).
>
> This worked OK.
>
> Your breadcrumbs are correct and the site look fine with "forrest run".
This might be one of the problems I was running into: I never did a
"forrest run". Since I don't know what 'Jetty' and 'jetty.run' are, I
never tried those... I did the following from the command line:
forrest -projecthelp
forrest seed
forrest site
forrest
forrest validate
> What you need to do is verify that any needed customisations in your
> original xmap are copied across (I've not looked to see if any are
> actually needed).
I'll check that out with the developers. Unfortunately the primary
developer who worked (I think) on this portion is no longer actively
contributing, although I may be able to contact him.
>> I get errors stating 'site.xml is not valid'. Heh... actually, I don't
>> think the file exists, as they're using sitemap.xmap instead.
>
> You have to have either site.xml or book.xml. sitemap.xmap is nothing to
> do with these files, it manages how the site is built.
As far as I can tell, this file does not exist in any of the distributions
to which I have access (did you find it in your download src?):
/src/documentation/content/xdocs/site.xml
That's why I thought perhaps they were using sitemap.xmap instead.
>> Anyway, I
>> have problems generating the FOP web site from this src (Maintenance
>> branch, which I'm using mainly for testing Forrest):
>>
>> http://apache.get-software.com/xml/fop/fop-0.20.5-src.tar.gz
>
> I should have read your mail properly before starting. I didn't try the
> above with this branch.
The above branch isn't really necessary. What I was trying to eplain was
that when I had problems doing the FORREST build thing, I tried the
MAINTENANCE branch tosee if it worked. It didn't do what I wanted either.
>> At this point, I'd like to be able to build locally, the current FOP web
>> site. Once there, I'd like to fix the problems indicated above.
>
> Try the above, if it doesn't work I'll have another look using the
> maintenance version of FOP.
>
> Ross
Don't bother with the maintenance version.
Thanks for your help! I should've asked for help *months* ago!
Web Maestro Clay
--
Clay Leeds - cleeds@medata.com
Web Developer - Medata, Inc. - http://www.medata.com
PGP Public Key: https://mail.medata.com/pgp/cleeds.asc