Re: X-Versions supported by Forrest
Ferdinand Soethe wrote: > > Thanks, all of you. Now I understand where to look and how to read > that. > > David Crossley wrote: > > DC> We had a recent discussion that we need to have a document > DC> that describes all of this, but no-one has done it. > > Have made a note to do that ... I didn't mean to imply that anyone in particular should do it. Thanks anyway and thanks for the other contributions that you have made via Jira. Those patches certainly help. --David
Re: Introduction of XHTML?
Ferdinand Soethe wrote: > Ross Gardler wrote: > > RG> In this case you could consider using the XHTML subset we have defined > RG> now. We already support it as an input format, it's just that we don't > RG> use it internally yet. This will save you having to retrain folk in the > > This sounds interesting. So this subset is currently transformed to > document-vxx before it gets skinned. And it is probably not a > plug-in (since I found none that looked like it) but a build-in > feature. This has been in the core of forrest since the beginning. We transform every input source into document-v** This "internal" format is planned to be XHTML in Forrest version 0.8 > Only questions remaining is: Where is the grammar for this XHTML > subset defined. I saw only the general xhtml-dtds in > ...\main\webapp\resources\schema. The XHTML "subset" is document-v20 ... it uses a subset of XHTML and no forrest-specific ones such as those used in document-v13, e.g. Ross is suggesting that you use document-v20 now as input because the change to XHTML documents is then trivial. --David
Re: X-Versions supported by Forrest
Thanks, all of you. Now I understand where to look and how to read that. David Crossley wrote: DC> We had a recent discussion that we need to have a document DC> that describes all of this, but no-one has done it. Have made a note to do that ... -- Ferdinand
Re: Introduction of XHTML?
Ross Gardler wrote: RG> It is a policy of the Forrest team to try not to break backward RG> compatibility. Yes, I realized that from past messages in this forum. RG> Occasionally this is not possible. But usually it is. Exactly the reason I wanted to make sure. RG> In this case you could consider using the XHTML subset we have defined RG> now. We already support it as an input format, it's just that we don't RG> use it internally yet. This will save you having to retrain folk in the This sounds interesting. So this subset is currently transformed to document-vxx before it gets skinned. And it is probably not a plug-in (since I found none that looked like it) but a build-in feature. Only questions remaining is: Where is the grammar for this XHTML subset defined. I saw only the general xhtml-dtds in ...\main\webapp\resources\schema. Thanks, Ferdinand Soethe
Re: problem at step 1 running forrest
Guillaume Barreau wrote: > Hi Forrest people, > > When I run forrest on my test site I get the following error messages > and the execution stops. Can someone point me to what I am doing wrong. > I have checked that org/apache/log/Hierarchy is present in > /lib/core/logkit.jar but somehow it doesn't seem to be found. > > Any help appreciated, You will need to provide more information. Please do this ... * Tell us which version of Forrest you are using. * Create a new work directory and do 'forrest seed' * Do 'forrest site > my-output.log' * Provide us with the output, either a URL on your website, or create an entry on our Issue tracker, or send it via this user email list if it is not too big. --David
Re: X-Versions supported by Forrest
Antonio Gallardo wrote: > Ferdinand Soethe dijo: > > > So am I correct to assume that Forrest will always use the latest > > stable release of cocoon (which will always use the latest stable > > release of xalan) or how is this decided? > > We try to stick with this as long as posible. But the reality sometimes is > not exactly as you described above. Also in Cocoon, there is the same > policy to use stable "official" releases of the libs. But sometimes we > need to use a CVS (SVN) version because it fix an important issue. As a > sample take the current xalan version we use now in forrest: > > xalan-2.6.1-dev-20041008T0304.jar > > here, "20041008T0304" means we use a xalan built from the CVS. The CVS > snapshot was from 2004-10-08 Time 03:04 UTC. > > This was done because there was an important bugfix for forrest and this > is the same xalan version shipped currently with cocoon. This needs clarification. We don't use a stable release of Cocoon. We use trunk (currently 2.2). We don't stay on the bleeding edge however. We use a svn revision that works for us, and update forrest's Cocoon occasionally. Cocoon has a general policy to use only released versions of supporting products. At Forrest we don't have this restriction. > > I other words is there an easy way to find out what modules are used > > in any given Forrest release? > > If by modules you mean "jars", then see: > > http://svn.apache.org/viewcvs.cgi/forrest/trunk/lib/ Yes, the best way is to look at your own local version of forrest in the ./lib/ directories. > Also there is an important dir "cocoon_upgrade" and see the readme: > > http://svn.apache.org/viewcvs.cgi/forrest/trunk/etc/cocoon_upgrade/ > > > If not, wouldn't this be a useful thing > > to report somewhere? > > If the above don't answer the question, then we need to publish more info. > :-) > > WDYT? We had a recent discussion that we need to have a document that describes all of this, but no-one has done it. --David
Re: X-Versions supported by Forrest
Antonio Gallardo wrote: > Juan Jose Pablos dijo: > > Antonio Gallardo wrote: > >> On Mar, 12 de Abril de 2005, 12:01, Ferdinand Soethe dijo: > >>>I other words is there an easy way to find out what modules are used > >>>in any given Forrest release? > >> > >> > >> If by modules you mean "jars", then see: > >> > >> http://svn.apache.org/viewcvs.cgi/forrest/trunk/lib/ > >> > > > > Maybe we need something like: > > http://svn.apache.org/repos/asf/cocoon/trunk/lib/jars.xml > > Do you mean something like: > > http://cocoon.apache.org/2.1/installing/jars.html Which is automatically built from the file that Cheche mentioned. > If yes, we can borrow it from cocoon! ;-) However we use Cocoon 2.2 version, so that file does not necessarily relate. --David
Re: X-Versions supported by Forrest
On Mar, 12 de Abril de 2005, 14:45, Juan Jose Pablos dijo: > Antonio Gallardo wrote: >> On Mar, 12 de Abril de 2005, 12:01, Ferdinand Soethe dijo: >>>I other words is there an easy way to find out what modules are used >>>in any given Forrest release? >> >> >> If by modules you mean "jars", then see: >> >> http://svn.apache.org/viewcvs.cgi/forrest/trunk/lib/ >> > > Maybe we need something like: > http://svn.apache.org/repos/asf/cocoon/trunk/lib/jars.xml Do you mean something like: http://cocoon.apache.org/2.1/installing/jars.html If yes, we can borrow it from cocoon! ;-) Best Regards, Antonio Gallardo.
Re: X-Versions supported by Forrest
Antonio Gallardo wrote: On Mar, 12 de Abril de 2005, 12:01, Ferdinand Soethe dijo: I other words is there an easy way to find out what modules are used in any given Forrest release? If by modules you mean "jars", then see: http://svn.apache.org/viewcvs.cgi/forrest/trunk/lib/ Maybe we need something like: http://svn.apache.org/repos/asf/cocoon/trunk/lib/jars.xml
Re: Introduction of XHTML?
Ferdinand Soethe wrote: Thanks. Now I can safely train people to use document-v20 and wait for xhtml to come along and turn into a stable implementation. It is a policy of the Forrest team to try not to break backward compatibility. Occasionally this is not possible. But usually it is. In other words, you can safely train folk up to use Forrest today, safe in the knowledge that we will at worst provide a migration path in the future. In this case you could consider using the XHTML subset we have defined now. We already support it as an input format, it's just that we don't use it internally yet. This will save you having to retrain folk in the future. Ross
Re: Introduction of XHTML?
On Tue, 2005-04-12 at 17:59 +0100, Ross Gardler wrote: > It is part of the switch to the new skinning system that Thorsten has > recently prototyped. Both he and I need this for our work so "soon". > Actually I am developing that not for work but just for the challenge that it is working like I predicted. ;-) salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)
Re: X-Versions supported by Forrest
On Mar, 12 de Abril de 2005, 12:01, Ferdinand Soethe dijo: > > Antonio Gallardo wrote: > > AG> Forrest is built on Apache Cocoon. Cocoon can use saxon as the XSLT > AG> processor. Saxon supports xpath v2. That means is posible to use xpath > v2 > AG> right now in forrest. > > Thanks. That is good to know. If I really need XPath 2 I'll try to figure > out how. I believe it is not too dificult: http://wiki.apache.org/cocoon/Saxon > But I think I'd rather stick with the standard distribution as > long as I can. :-) > So am I correct to assume that Forrest will always use the latest > stable release of cocoon (which will always use the latest stable > release of xalan) or how is this decided? We try to stick with this as long as posible. But the reality sometimes is not exactly as you described above. Also in Cocoon, there is the same policy to use stable "official" releases of the libs. But sometimes we need to use a CVS (SVN) version because it fix an important issue. As a sample take the current xalan version we use now in forrest: xalan-2.6.1-dev-20041008T0304.jar here, "20041008T0304" means we use a xalan built from the CVS. The CVS snapshot was from 2004-10-08 Time 03:04 UTC. This was done because there was an important bugfix for forrest and this is the same xalan version shipped currently with cocoon. > I other words is there an easy way to find out what modules are used > in any given Forrest release? If by modules you mean "jars", then see: http://svn.apache.org/viewcvs.cgi/forrest/trunk/lib/ Also there is an important dir "cocoon_upgrade" and see the readme: http://svn.apache.org/viewcvs.cgi/forrest/trunk/etc/cocoon_upgrade/ > If not, wouldn't this be a useful thing > to report somewhere? If the above don't answer the question, then we need to publish more info. :-) WDYT? Best Regards, Antonio Gallardo
Re: Introduction of XHTML?
Thanks. Now I can safely train people to use document-v20 and wait for xhtml to come along and turn into a stable implementation. Ferdinand Soethe
Re: Introduction of XHTML?
On Tue, 2005-04-12 at 18:52 +0200, Ferdinand Soethe wrote: > I have two questions re the switch from Forrest document-v20-Format to > xhtml: > > - What is a realistic expectation for this to happen in terms of time > and version? (No guarantees expected of course!) > 0.8. There we will introduce the view/viewHelper/businessHelper plugins into forrest. IMO those plugins should be totally based on xhtml. > - Will Forrest still support document-vxx after the switch? > And if so, will document-vxx-support become a plugin? > Hmm, looking on the architecture right now I reckon we would supported it in the core. > Thanks > Ferdinand Soethe > salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)
Re: X-Versions supported by Forrest
Antonio Gallardo wrote: AG> Forrest is built on Apache Cocoon. Cocoon can use saxon as the XSLT AG> processor. Saxon supports xpath v2. That means is posible to use xpath v2 AG> right now in forrest. Thanks. That is good to know. If I really need XPath 2 I'll try to figure out how. But I think I'd rather stick with the standard distribution as long as I can. So am I correct to assume that Forrest will always use the latest stable release of cocoon (which will always use the latest stable release of xalan) or how is this decided? I other words is there an easy way to find out what modules are used in any given Forrest release? If not, wouldn't this be a useful thing to report somewhere? Thanks, Ferdinand Soethe
Re: Introduction of XHTML?
Ferdinand Soethe wrote: I have two questions re the switch from Forrest document-v20-Format to xhtml: - What is a realistic expectation for this to happen in terms of time and version? (No guarantees expected of course!) It is part of the switch to the new skinning system that Thorsten has recently prototyped. Both he and I need this for our work so "soon". Of course "soon" is a relative term. All I can say is that it *will* be in the next release. - Will Forrest still support document-vxx after the switch? Yes. And if so, will document-vxx-support become a plugin? Probably. Although it is likely that that plugin would be included in the default distribution for a while since there are a large number of sites using that format document. Ross
Introduction of XHTML?
I have two questions re the switch from Forrest document-v20-Format to xhtml: - What is a realistic expectation for this to happen in terms of time and version? (No guarantees expected of course!) - Will Forrest still support document-vxx after the switch? And if so, will document-vxx-support become a plugin? Thanks Ferdinand Soethe
Re: X-Versions supported by Forrest
Ferdinand Soethe wrote: Juan Pablos wrote: JJP> we are using xalan-2.6.1 and that support xpath v1 Thanks! Any idea when this will change to support xpath v2? There are soo many useful functions in it. This is what I have found: http://marc.theaimsgroup.com/?t=10620647731&r=1&w=2 saxon support xpath 2.0 BTW -- Ferdinand Soethe
Re: X-Versions supported by Forrest
On Mar, 12 de Abril de 2005, 9:46, Ferdinand Soethe dijo: > > Juan Pablos wrote: > > JJP> we are using xalan-2.6.1 and that support xpath v1 > > Thanks! Any idea when this will change to support xpath v2? There are > soo many useful functions in it. Forrest is built on Apache Cocoon. Cocoon can use saxon as the XSLT processor. Saxon supports xpath v2. That means is posible to use xpath v2 right now in forrest. Best Regards, Antonio Gallardo.
Re: X-Versions supported by Forrest
Juan Pablos wrote: JJP> we are using xalan-2.6.1 and that support xpath v1 Thanks! Any idea when this will change to support xpath v2? There are soo many useful functions in it. -- Ferdinand Soethe
Re: OT: Forrest site down
Jonathan Sidarous wrote: Hmm, this is weird, here's what's happening: I am a Firefox user, and when I got the first email about the site being down, I went out to the Forrest site (using Firefox) and everything was working except those two tabs I told you about. After this, I tried using Internet Explorer, and the whole site was down. Then, I tried going back to Firefox and Internet Explorer just now, and both are failing. It still fails on ctrl+F5. That's all consitent with the local cache having a copy of some pages (and timing out when you returned to Firefox) The CTRL+F5 key combination forces a refresh that bypasses the local cache, so I would expect this to fail (since the server has not been fixed yet). Ross
Re: OT: Forrest site down
Hmm, this is weird, here's what's happening: I am a Firefox user, and when I got the first email about the site being down, I went out to the Forrest site (using Firefox) and everything was working except those two tabs I told you about. After this, I tried using Internet Explorer, and the whole site was down. Then, I tried going back to Firefox and Internet Explorer just now, and both are failing. It still fails on ctrl+F5. - Jonathan On Apr 12, 2005 9:24 AM, Ross Gardler <[EMAIL PROTECTED]> wrote:Jonathan Sidarous wrote:> If it helps at all...I only get the crashing of the website on the> "Documentation" and "How-To" tabs.Interesting, I get it everywhere, but I had to force a cache refresh toget it on the home page - try CTRL-F5 on the home page, does it fail?Ross
Re: OT: Forrest site down
Jonathan Sidarous wrote: If it helps at all...I only get the crashing of the website on the "Documentation" and "How-To" tabs. Interesting, I get it everywhere, but I had to force a cache refresh to get it on the home page - try CTRL-F5 on the home page, does it fail? Ross
Re: OT: Forrest site down
If it helps at all...I only get the crashing of the website on the "Documentation" and "How-To" tabs.On Apr 12, 2005 7:41 AM, Ross Gardler <[EMAIL PROTECTED]> wrote:[EMAIL PROTECTED] wrote:> The Forrest site appears to be down at the moment.So it does, and appears not to be a problem with the servers since othersites are up.I'm looking into it now.Thanks for the heads up.Ross
Re: OT: Forrest site down
[EMAIL PROTECTED] wrote: The Forrest site appears to be down at the moment. So it does, and appears not to be a problem with the servers since other sites are up. I'm looking into it now. Thanks for the heads up. Ross
OT: Forrest site down
The Forrest site appears to be down at the moment. K
