custom serializer
Hi, I am trying to create a custom serializer for apache cocoon. the objective of the serializer is to encode the xml data which will be used for flash devices. so i need to take whole xml data in to a string and encode the string and return the output for the user. i have looked at the code for xmlserializer but i have not been able to create my own serializer yet. thanks
Re: custom serializer
See: http://www.opensubscriber.com/message/users@cocoon.apache.org/4985156.html On 2009/05/11 at 09:14, in message b69d73200905110014p1eec673bq145b4a0ab95f3...@mail.gmail.com, saeid itune saeidit...@gmail.com wrote: Hi, I am trying to create a custom serializer for apache cocoon. the objective of the serializer is to encode the xml data which will be used for flash devices. so i need to take whole xml data in to a string and encode the string and return the output for the user. i have looked at the code for xmlserializer but i have not been able to create my own serializer yet. thanks -- This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks Transtec Computers for their support. - To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org For additional commands, e-mail: users-h...@cocoon.apache.org
Re: ServerPagesGenerator in 2.2 ?!
Hi! Now i tried out the ServerPageGenerator coming from cocoon:cocoon-xsp 2.1.11 but if i try to run it in an environment which is based on 2.2, i get the following error: Caused by: java.lang.NoSuchFieldError: manager at org.apache.cocoon.generation.ServerPagesGenerator.setup(ServerPagesGenerator.java:170) That normally points to a version conflict (i.e. different versions of the class. Here it seems to be ServletGenerator, but that one has a manager, and it is protected, so the ServerPageGenerator should be able to see it Anyone who has a idea what is going wrong? Søren D. Krum - To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org For additional commands, e-mail: users-h...@cocoon.apache.org
[Cocoon 3] : Annotation-specified bean name 'org.apache.cocoon.sample.controller.DemoRESTController' for bean class [org.apache.cocoon.sample.controller.DemoRESTController] conflicts with existing, no
Hi all,
Anybody having the same problem when trying to run the cocoon3 sample?
Cheers,
Robby Pelssers
log4j:WARN Please initialize the log4j system properly.
log4j:WARN Please initialize the log4j system properly.
2009-05-11 10:32:54.224:/:INFO: Initializing Spring root
WebApplicationContext
2009-05-11 10:32:54.724::WARN: Failed startup of context
org.mortbay.jetty.plugin.jetty6pluginwebappcont...@101fa9e{/,D:\developm
ent\workspaces\nxp\cocoon3_demo\target\rcl\webapp}
java.lang.RuntimeException: Cannot invoke listener
org.springframework.web.context.contextloaderliste...@40627c
at
org.apache.cocoon.tools.rcl.wrapper.servlet.ReloadingListener.invoke(Rel
oadingListener.java:190)
at
org.apache.cocoon.tools.rcl.wrapper.servlet.ReloadingListener.contextIni
tialized(ReloadingListener.java:213)
at
org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.jav
a:540)
at
org.mortbay.jetty.servlet.Context.startContext(Context.java:135)
at
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1
220)
at
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:510
)
at
org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:448)
at
org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart(Jetty6PluginW
ebAppContext.java:110)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.ja
va:152)
at
org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandle
rCollection.java:156)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.ja
va:152)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:117
)
at org.mortbay.jetty.Server.doStart(Server.java:222)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.jav
a:132)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.
java:357)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.jav
a:293)
at
org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMo
jo.java:203)
at
org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:182)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
nager.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:558)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoa
l(DefaultLifecycleExecutor.java:512)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
ifecycleExecutor.java:482)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:142)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by:
org.springframework.beans.factory.BeanDefinitionStoreException: Unable
to read spring configurations from classpath*:META-INF/cocoon/spring;
nested exception is org.springframework.
beans.factory.BeanDefinitionStoreException: Unexpected exception parsing
XML document from URL
[file:/D:/development/workspaces/nxp/cocoon3_demo/target/classes/META-IN
F/cocoon/spring/cocoon-sa
mple-controller.xml]; nested exception is
java.lang.IllegalStateException: Annotation-specified bean name
'org.apache.cocoon.sample.controller.DemoRESTController' for bean class
[org.apache.co
coon.sample.controller.DemoRESTController] conflicts with existing,
non-compatible bean definition of same name and class
spring schema issue: spring-aop-2.5.xsd is not valid
Hi all, I know it's not really a cocoon issue but anybody got an idea if this problem will be resolved soon? See attached screenshot for more info. Robby attachment: bean-config.gif - To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org For additional commands, e-mail: users-h...@cocoon.apache.org
Re: spring schema issue: spring-aop-2.5.xsd is not valid
Hi! a kind of strange. Is that just you ide complaining, or do you actually have problems to start your application? My eclipse does not wonder about the form namespace, and spring starts just fine. Søren D. Krum - To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org For additional commands, e-mail: users-h...@cocoon.apache.org
Re: [Cocoon 3] : Annotation-specified bean name 'org.apache.cocoon.sample.controller.DemoRESTController' for bean class [org.apache.cocoon.sample.controller.DemoRESTController] conflicts with existing
Robby Pelssers wrote:
Hi all,
Anybody having the same problem when trying to run the cocoon3 sample?
snip/
I guess you're using alpha-1. It depends on Spring 2.5.5 which causes
this bug. It's fixed in Spring 2.5.6. Explicitly setting the version of
all Spring modules in your project POM should solve the problem.
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member reinh...@apache.org
-
To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org
For additional commands, e-mail: users-h...@cocoon.apache.org
Re: ServerPagesGenerator in 2.2 ?!
I'm not sure why you can't find the XSP block in 2.2 but there is a ServerPagesGenerator: http://svn.apache.org/viewvc/cocoon/trunk/blocks/cocoon-xsp/cocoon-xsp-impl/src/main/java/org/apache/cocoon/generation/ Joerg On 11.05.2009 10:37, Søren Krum wrote: Hi! Now i tried out the ServerPageGenerator coming from cocoon:cocoon-xsp 2.1.11 but if i try to run it in an environment which is based on 2.2, i get the following error: Caused by: java.lang.NoSuchFieldError: manager at org.apache.cocoon.generation.ServerPagesGenerator.setup(ServerPagesGenerator.java:170) That normally points to a version conflict (i.e. different versions of the class. Here it seems to be ServletGenerator, but that one has a manager, and it is protected, so the ServerPageGenerator should be able to see it Anyone who has a idea what is going wrong? Søren D. Krum - To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org For additional commands, e-mail: users-h...@cocoon.apache.org
RE: [Cocoon 3] : Annotation-specified bean name 'org.apache.cocoon.sample.controller.DemoRESTController' for bean class [org.apache.cocoon.sample.controller.DemoRESTController] conflicts with existing
Hi Reinhard,
I was indeed using the alpha-1. I just checked out trunk and am running the
sample without any errors now.
Thx.
Robby
-Original Message-
From: Reinhard Pötz [mailto:reinh...@apache.org]
Sent: Monday, May 11, 2009 11:11 AM
To: users@cocoon.apache.org
Subject: Re: [Cocoon 3] : Annotation-specified bean name
'org.apache.cocoon.sample.controller.DemoRESTController' for bean class
[org.apache.cocoon.sample.controller.DemoRESTController] conflicts with
existing, non-compatible bean definition of same name and class
Robby Pelssers wrote:
Hi all,
Anybody having the same problem when trying to run the cocoon3 sample?
snip/
I guess you're using alpha-1. It depends on Spring 2.5.5 which causes
this bug. It's fixed in Spring 2.5.6. Explicitly setting the version of
all Spring modules in your project POM should solve the problem.
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member reinh...@apache.org
-
To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org
For additional commands, e-mail: users-h...@cocoon.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org
For additional commands, e-mail: users-h...@cocoon.apache.org
Re: ServerPagesGenerator in 2.2 ?!
Joerg Heinicke wrote: I'm not sure why you can't find the XSP block in 2.2 but there is a ServerPagesGenerator: http://svn.apache.org/viewvc/cocoon/trunk/blocks/cocoon-xsp/cocoon-xsp-impl/src/main/java/org/apache/cocoon/generation/ Joerg Looks like that is Snapshot 6, seems like that package never made it over to cocoon 2.2 release. Strange enough, in 2.2 is there still a manager field. And i have just one version of the ServerGenerator in the classpass, so should not be confusion about which version to use. Really strange. Thx for your suggestions anyway. -- Søren D. Krum Systemutvikler/system developer UNINETT FAS + 47 73557859 There are 10 different kind of people in the world, those who understand binary and those who don't - To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org For additional commands, e-mail: users-h...@cocoon.apache.org
Re: ServerPagesGenerator in 2.2 ?!
Ah, that is true. Not all blocks actually got released as part of 2.2 release. But you can still take the block and use it. Regarding your error, the type of manager might have changed from ComponentManager to ServiceManager. Joerg On 11.05.2009 12:37, Søren Krum wrote: Joerg Heinicke wrote: I'm not sure why you can't find the XSP block in 2.2 but there is a ServerPagesGenerator: http://svn.apache.org/viewvc/cocoon/trunk/blocks/cocoon-xsp/cocoon-xsp-impl/src/main/java/org/apache/cocoon/generation/ Joerg Looks like that is Snapshot 6, seems like that package never made it over to cocoon 2.2 release. Strange enough, in 2.2 is there still a manager field. And i have just one version of the ServerGenerator in the classpass, so should not be confusion about which version to use. Really strange. Thx for your suggestions anyway. - To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org For additional commands, e-mail: users-h...@cocoon.apache.org
cocoon 3 sample: remark about usage of servlet-service demo
Hi all, Taking a quick look at the cocoon 3 sample I noticed that the transformer-pipeline and serializer-pipeline are sort of the same except for myParam which get's another value. I noticed as well that I can't leave out the map:serialize type=xml/ from the transformer-pipeline. Otherwise I get following exception java.lang.IllegalStateException: Cannot execute pipeline, last pipeline component is no finisher. So is it fair to conclude that every 'transformation servlet service' is inherent also a 'serializer servlet service'? And what bugs me a bit is that [1] throws in a free transformer... simple.xslt. [2] This makes things a bit confusing in my opinion. It seems that these servlet-services actually do more then their names imply. map:match pattern=ssf/transformer-pipeline map:generate type=service-consumer / map:transform src=sax-pipeline/simple.xslt map:parameter name=myParam value=transformer-pipeline / /map:transform map:serialize type=xml / /map:match map:match pattern=ssf/serializer-pipeline map:generate type=service-consumer / map:transform src=sax-pipeline/simple.xslt [2] map:parameter name=myParam value=serializer-pipeline / /map:transform map:serialize type=xml / /map:match map:match pattern=ssf/calling-a-transformer-servlet-service map:generate src=sax-pipeline/simple.xml / map:transform type=servlet-service map:parameter name=service value=servlet:/ssf/transformer-pipeline / /map:transform map:serialize type=xml / /map:match map:match pattern=ssf/calling-a-serializer-servlet-service map:generate src=sax-pipeline/simple.xml / map:serialize type=servlet-service map:parameter name=service value=servlet:/ssf/serializer-pipeline / [1] /map:serialize /map:match Cheers, Robby
[HELP]Cannot convert null to an object.
Description:org.apache.cocoon.ProcessingException: Error calling continuation at [EcmaError] - file:/var/www/vhosts/navfac.ecatts.com/ecatts/webapps/ROOT/forms/regUserInstallation_NAVY.xml:41:0 at file:/var/www/vhosts/navfac.ecatts.com/ecatts/webapps/ROOT/forms/regUserInstallation_NAVY.xml:41:-1 at resource://org/apache/cocoon/forms/flow/javascript/Form.js:168:-1 at resource://org/apache/cocoon/forms/flow/javascript/Form.js:0:-1 at file:/var/www/vhosts/navfac.ecatts.com/ecatts/webapps/ROOT/flow/userManager.js:0:-1 at map:call - file:/var/www/vhosts/navfac.ecatts.com/ecatts/webapps/ROOT/sitemap.xmap:1473:35 smime.p7s Description: S/MIME cryptographic signature
custom serializer
Hi, I am trying to create a custom serializer for apache cocoon. the objective of the serializer is to encode the xml data which will be used for flash devices. so i need to take whole xml data in to a string and encode the string and return the output for the user. i have looked at the code for xmlserializer but i have not been able to create my own serializer yet. thanks
Re: custom serializer
Hi Can you please let us know what the exact issue is? Regards Sac On Mon, May 11, 2009 at 7:26 PM, saeid itune saeidit...@gmail.com wrote: Hi, I am trying to create a custom serializer for apache cocoon. the objective of the serializer is to encode the xml data which will be used for flash devices. so i need to take whole xml data in to a string and encode the string and return the output for the user. i have looked at the code for xmlserializer but i have not been able to create my own serializer yet. thanks
[SPAM] cocoon 2.2 samples and jboss 5
hi all, Has anyone successfully deployed cocoon 2.2 samples inside jboss 5 ? .. we have been using our cocoon based application with jboss 4.2.3 .. we wanted to upgrade the jboss server to 5 but the application doesn't deploy .. neither it shows any deployment error .. so we just tried to deploy the samples block of cocoon 2.2 with that also the same result .. the application and the samples block they work perfectly fine with jboss 4 .. the problem occurs with jboss 5 .. we have changed the schema locations for the xml files in accordance with the jboss 5 specification .. if anyone has been successful in doing so .. can you please guide us .. Any help will be appreciated Thanks in advance Imran - To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org For additional commands, e-mail: users-h...@cocoon.apache.org
XProc
Hi, Is there any overlap, or have there been attempts to find such, so far as anyone here knows, between cocoon and XProc http://www.w3.org/TR/xproc/ ? quote XProc: An XML Pipeline Language W3C Candidate Recommendation 26 November 2008 /quote (particularly between the cocoon concept of a sitemap and Xproc ). Thanks in advance, Ken. - To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org For additional commands, e-mail: users-h...@cocoon.apache.org
Re: cocoon 3 sample: remark about usage of servlet-service demo
Robby Pelssers wrote:
Hi all,
Taking a quick look at the cocoon 3 sample I noticed that the
“transformer-pipeline” and “serializer-pipeline” are sort of the same
except for myParam which get’s another value.
I noticed as well that I can’t leave out the map:serialize
type=”xml”/ from the transformer-pipeline. Otherwise I get following
exception “java.lang.IllegalStateException: Cannot execute pipeline,
last pipeline component is no finisher”.
So is it fair to conclude that every ‘transformation servlet service’ is
inherent also a ‘serializer servlet service’?
yes
And what bugs me a bit is that [1] throws in a /free/ transformer…
“simple.xslt”. [2] This makes things a bit confusing in my opinion.
It seems that these servlet-services actually do more then their names
imply.
sorry, I can't follow you here. What do the names imply in your opinion?
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member reinh...@apache.org
-
To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org
For additional commands, e-mail: users-h...@cocoon.apache.org
RE: cocoon 3 sample: remark about usage of servlet-service demo
Well,
If I take a look at for instance the servlet-service snippet below which I
renamed to myservice-pipeline
map:match pattern=ssf/myservice-pipeline
map:generate type=service-consumer /
map:transform src=sax-pipeline/simple.xslt [2]
map:parameter name=myParam value=serializer-pipeline /
/map:transform
map:serialize type=xml /
/map:match
It includes an extra transformation step. So it's not really uniquely defined
as either a serializer OR transformer service. It can be invoked by
map:transform type=servlet-service
map:parameter name=service value=servlet:/ssf/myservice-pipeline
/
/map:transform
OR
map:serialize type=servlet-service
map:parameter name=service value=servlet:/ssf/myservice-pipeline
/
/map:serialize
Both invocations of this service would work. That's what I mean with ambiguous
names.
Robby
-Original Message-
From: Reinhard Pötz [mailto:reinh...@apache.org]
Sent: Monday, May 11, 2009 10:20 PM
To: users@cocoon.apache.org
Subject: Re: cocoon 3 sample: remark about usage of servlet-service demo
Robby Pelssers wrote:
Hi all,
Taking a quick look at the cocoon 3 sample I noticed that the
“transformer-pipeline” and “serializer-pipeline” are sort of the same
except for myParam which get’s another value.
I noticed as well that I can’t leave out the map:serialize
type=”xml”/ from the transformer-pipeline. Otherwise I get following
exception “java.lang.IllegalStateException: Cannot execute pipeline,
last pipeline component is no finisher”.
So is it fair to conclude that every ‘transformation servlet service’ is
inherent also a ‘serializer servlet service’?
yes
And what bugs me a bit is that [1] throws in a /free/ transformer…
“simple.xslt”. [2] This makes things a bit confusing in my opinion.
It seems that these servlet-services actually do more then their names
imply.
sorry, I can't follow you here. What do the names imply in your opinion?
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member reinh...@apache.org
-
To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org
For additional commands, e-mail: users-h...@cocoon.apache.org
Re: cocoon 3 sample: remark about usage of servlet-service demo
Robby Pelssers schrieb: Hi all, Taking a quick look at the cocoon 3 sample I noticed that the “transformer-pipeline” and “serializer-pipeline” are sort of the same except for myParam which get’s another value. I noticed as well that I can’t leave out the map:serialize type=”xml”/ from the transformer-pipeline. Otherwise I get following exception “java.lang.IllegalStateException: Cannot execute pipeline, last pipeline component is no finisher”. Yes. Every pipeline needs a Finisher. Since a call using a servlet-service is no different to a call from a browser or other client, there are no exceptions for those pipelines. So is it fair to conclude that every ‘transformation servlet service’ is inherent also a ‘serializer servlet service’? And what bugs me a bit is that [1] throws in a /free/ transformer… “simple.xslt”. [2] This makes things a bit confusing in my opinion. It seems that these servlet-services actually do more then their names imply. I'm not sure what you mean with free transformer. Actually the transformer is not thrown in by [1] but rather defined at [2]. Because if you remove [2] there will be no transformer but still the servet-service. The purpose of servlet-services is to allow to call another servlet. Either to delegate the processing or retrieve input. If the other servlet is a Cocoon sitemap servlet as well, it will use pipelines and those pipeline can use transformers, of course. The samples contain some amount of duplication to demonstrate the various approaches that are possible. We do not necessarily suggest that each and every application should use everything mentioned there. map:match pattern=ssf/transformer-pipeline map:generate type=service-consumer / map:transform src=sax-pipeline/simple.xslt map:parameter name=myParam value=transformer-pipeline / /map:transform map:serialize type=xml / /map:match map:match pattern=ssf/serializer-pipeline map:generate type=service-consumer / map:transform src=sax-pipeline/simple.xslt [2] map:parameter name=myParam value=serializer-pipeline / /map:transform map:serialize type=xml / /map:match map:match pattern=ssf/calling-a-transformer-servlet-service map:generate src=sax-pipeline/simple.xml / map:transform type=servlet-service map:parameter name=service value=servlet:/ssf/transformer-pipeline / /map:transform map:serialize type=xml / /map:match map:match pattern=ssf/calling-a-serializer-servlet-service map:generate src=sax-pipeline/simple.xml / map:serialize type=servlet-service map:parameter name=service value=servlet:/ssf/serializer-pipeline / [1] /map:serialize /map:match Cheers, Robby - To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org For additional commands, e-mail: users-h...@cocoon.apache.org
Map serialize flowscript output
Hi everybody,
I've created a transformer for the sitemap that takes a GXL file as input
and then applies layout algorithm and then passes the resulting graph on as
SVG image. It all works fine, but now I wanted to use JX to fill in a
template that would then be transformed and serialized, but I can't get it
to work. Apparently the pages I send back with cocoon.sendPage are not
transformed.
Long story short: I have the following matcher:
map:match pattern=project.svg
map:call function=projectGraph
map:parameter name=screenURI value=screen/screens/project-graph /
map:parameter name=projectID value=1 /
/map:call
map:transform type=gxl2svgTransformer/
map:serialize type=svgxml/
/map:match
But this just prints me the filled in template instead of feeding it into
the gxl2svgtransformer. The transformers work fine as I already tested them
with a simple generate tag. The flowscript sends pages using
cocoon.sendPage( cocoon.parameters[ screenURI ], {project :project,
dao :dao} );
Somehow I think I got the sitemap concept wrong. Somebody got an idea?
Regards,
Chris
--
Christian Decker
Software Architect
http://blog.snyke.net
Re: Map serialize flowscript output
2009/5/12 Christian Decker decker.christ...@gmail.com:
Hi everybody,
I've created a transformer for the sitemap that takes a GXL file as input
and then applies layout algorithm and then passes the resulting graph on as
SVG image. It all works fine, but now I wanted to use JX to fill in a
template that would then be transformed and serialized, but I can't get it
to work. Apparently the pages I send back with cocoon.sendPage are not
transformed.
Long story short: I have the following matcher:
map:match pattern=project.svg
map:call function=projectGraph
map:parameter name=screenURI value=screen/screens/project-graph /
map:parameter name=projectID value=1 /
/map:call
map:transform type=gxl2svgTransformer/
map:serialize type=svgxml/
/map:match
But this just prints me the filled in template instead of feeding it into
the gxl2svgtransformer. The transformers work fine as I already tested them
with a simple generate tag. The flowscript sends pages using
cocoon.sendPage( cocoon.parameters[ screenURI ], {project :project,
dao :dao} );
Somehow I think I got the sitemap concept wrong. Somebody got an idea?
With the cocoon.sendPage you're passing the request processing on to
the pipeline that matches screenURI. In that pipeline you should do
the svg serialisation.
Jasha Joachimsthal
j.joachimst...@onehippo.com - ja...@apache.org
www.onehippo.com
Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466
San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA
94952-5100 +1 (707) 773-4646
-
To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org
For additional commands, e-mail: users-h...@cocoon.apache.org
