Hi,
I think that it would be positive to publish these logs on the web so
you would know the outcome of latest forrest build.
Ideally a green/red message on this page would be nice:
http://forrest.zones.apache.org/
WDTY?
cheers,
cheche
El mié, 21-09-2005 a las 15:09 -0700, Mark Eggers escribió:
...
X [0] linkmap.html BROKEN:
org.apache.commons.jxpath.JXPathContext.setNamespaceContextPointer(Lorg/apache/commons/jxpath/Pointer;)V
I guess there are some plugin interactions (especially
in the whiteboard area) that cause
El jue, 15-09-2005 a las 22:38 +0200, Thorsten Scherler escribió:
On Thu, 2005-09-15 at 08:23 -0500, Antonio Gallardo wrote:
Thorsten Scherler wrote:
It is only in the forrest site target, both dynamic (view and
traditional skin) modes are working fine. It has something to do with
the
Hi all,
the forrest site target is broken for views. Besides that you *need* to
copy commons-jxpath-1.2.jar from cocoon-2.2.x into lib/core of forrest.
That will break the whole forrest site as well for the old fashion
skins.
The cli depends on the linkmap, which cannot be build because a
I would suggest that you describe Forrest's problems with namespaces,
JXPath and JXTemplateGenerator at cocoon-dev. IIRC, Vadim made the
modules that use JXPath namespace aware and there have been discussions
about doing the same for JXTemplateGenerator, maybe it even is done.
Anyway, the
As I understood, contracts are points where to place xsl templates. I noticed
some some structure naming convention but I can't find where it's explained.
Now my problem:
1. Originally I had my template for generating voice head
2. I have contract voice-markup.ft
3. I added my original voice
Juan Jose Pablos wrote:
Hi,
I think that it would be positive to publish these logs on the web so
you would know the outcome of latest forrest build.
Ideally a green/red message on this page would be nice:
http://forrest.zones.apache.org/
WDTY?
+1
In the first instance just having the file
Thorsten Scherler wrote:
El mié, 21-09-2005 a las 15:09 -0700, Mark Eggers escribió:
...
X [0] linkmap.html BROKEN:
org.apache.commons.jxpath.JXPathContext.setNamespaceContextPointer(Lorg/apache/commons/jxpath/Pointer;)V
I guess there are some plugin interactions (especially
in the
HANAX wrote:
Can you give some links to examples of the kind of output you would like
to create (i.e. sites with voice and visual rendering)?
I've searched for sites but I didn't find any :( But I have examples of mxml
files that do really cool stuff. I can send you example...
That would
Those are files from IBM multimodal package, so I don't know if this is
suitable license or not, all I know that you can download whole package, but it
won't work until you have websphere site developer installed...
__
PÔVODNÁ
HANAX wrote:
As I understood, contracts are points where to place xsl templates.
Yes, templates, but not complete stylesheets...
I noticed some some structure naming convention but I can't find where it's explained.
Because they are not, at least not in an easily accessible way. There
El vie, 23-09-2005 a las 11:10 +0100, Ross Gardler escribió:
Thorsten Scherler wrote:
El mié, 21-09-2005 a las 15:09 -0700, Mark Eggers escribió:
...
X [0] linkmap.html BROKEN:
org.apache.commons.jxpath.JXPathContext.setNamespaceContextPointer(Lorg/apache/commons/jxpath/Pointer;)V
I
El vie, 23-09-2005 a las 11:26 +0100, Ross Gardler escribió:
HANAX wrote:
As I understood, contracts are points where to place xsl templates.
Yes, templates, but not complete stylesheets...
Hmm yes and no. You need to rip of the templates of the stylesheet. Have
a look at
HANAX wrote:
As I understood, contracts are points where to place xsl templates.
Yes, templates, but not complete stylesheets...
Ok, then how to import some namespace? My namespace is vxml but now it's
ignored...
I noticed some some structure naming convention but I can't find where
El vie, 23-09-2005 a las 11:26 +0100, Ross Gardler escribió:
HANAX wrote:
As I understood, contracts are points where to place xsl templates.
Yes, templates, but not complete stylesheets...
Hmm yes and no. You need to rip of the templates of the stylesheet. Have
a look at
El vie, 23-09-2005 a las 17:23 +0200, HANAX escribió:
El vie, 23-09-2005 a las 11:26 +0100, Ross Gardler escribió:
HANAX wrote:
As I understood, contracts are points where to place xsl templates.
Yes, templates, but not complete stylesheets...
Hmm yes and no. You need to rip
Thorsten Scherler wrote:
Hi all,
the forrest site target is broken for views. Besides that you *need* to
copy commons-jxpath-1.2.jar from cocoon-2.2.x into lib/core of forrest.
That will break the whole forrest site as well for the old fashion
skins.
The cli depends on the linkmap, which
El vie, 23-09-2005 a las 16:47 -0500, Antonio Gallardo escribió:
Thorsten Scherler wrote:
Hi all,
the forrest site target is broken for views. Besides that you *need* to
copy commons-jxpath-1.2.jar from cocoon-2.2.x into lib/core of forrest.
That will break the whole forrest site as well
On Fri, 2005-09-23 at 08:14 +1000, David Crossley wrote:
Kevin wrote:
David Crossley (JIRA) wrote:
...snip...
Could you help with the svn command to revert back to a revision #
with working views and commons-jxpath-20030909.jar?
Work backwards from today. Get the revision numbers from
Antonio Gallardo wrote:
Thorsten Scherler wrote:
Last weekend I started to check this problem. I believe we did a step by
suspecting the problems is in using namespaces in LinkRewriteTransformer
+ jxpath 1.2. This Sunday, I will try to make some
LinkRewriterTransformer samples inside
Kevin wrote:
David Crossley wrote:
Kevin wrote:
Could you help with the svn command to revert back to a revision #
with working views and commons-jxpath-20030909.jar?
Work backwards from today. Get the revision numbers from
the Forrest SVN mailing list, e.g.
need to declare common sitemap components in the project sitemap
Key: FOR-679
URL: http://issues.apache.org/jira/browse/FOR-679
Project: Forrest
Type: Bug
Components: Core operations
Versions:
22 matches
Mail list logo
