You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Thorsten Scherler <th...@apache.org> on 2005/04/19 11:49:05 UTC
CForms and forrest
Hello all,
I am looking into integrate some applications (mainly workflows) written
for cocoon with cforms and flow into forrest.
I reckon it would be an input plugin that will transform all cform
templates into xdocs format to later skin/view it. Has anybody made
experience with this approach in forrest?
The idea is to create a framework plugin (input.cforms/flow) that will
be able to pickup a project specific implementation of a flow/cform
work-flow. Each work-flow should *not* go into his own plugin but should
be implemented in the project. Ideally the usage of custom sitemap.xmap
in the project should be minimal.
TIA for any informations and experience or tips and tricks. ;-)
salu2
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
Re: CForms and forrest
Posted by Ross Gardler <rg...@apache.org>.
Thorsten Scherler wrote:
> Hello all,
>
> I am looking into integrate some applications (mainly workflows) written
> for cocoon with cforms and flow into forrest.
Not directly related, but you may find this work interesting
http://wiki.apache.org/cocoon/Schema2CocoonForms
Ross
Re: CForms and forrest
Posted by Thorsten Scherler <th...@apache.org>.
On Wed, 2005-04-20 at 11:19 +1000, David Crossley wrote:
> Thorsten Scherler wrote:
> > Seems to be that I am the first one in trying to do it.
> >
> > I just did some testing, but I actually I get
> >
> > Message: null
> >
> > Description: No details available.
> >
> > Sender: org.apache.cocoon.servlet.CocoonServlet
> >
> > Source: Cocoon Servlet
> >
> > Request URI
> >
> > dima/bearbeiten/
> >
> > cause
> >
> > org.apache.cocoon.forms.transformation.FormsTemplateTransformer
> >
> > I reckon I have not defined the needed components in the forrest-core.xconf and/or
> > have not provided the needed jars in the lib.
> >
> > Anybody a hint what I have to do to enable the flow/cforms in forrest?
>
> Forrest only ships the Cocoon Blocks that we currently need.
> See lib/core/cocoon-*
>
> You would need to add the Cforms Block, relevant to the
> cocoon-2.2 version that we are using.
>
> Yes you would need to add to forrest-core.xconf
>
> See info about cocoon in our etc/cocoon_upgrade/README.txt
> I am not saying that you need to upgrade our Cocoon,
> just get some notes for how to add another block.
>
> In addition to that readme, there is a wiki page at
> http://wiki.apache.org/cocoon/AddingCocoonBlocksToForrest
> (I don't know why that is on the wiki, rather than in
> our own xdocs.)
>
Cheers, David.
That is helping a lot.
I actually came to a state where all components from
xconf/forrest-core.xconf (flow/froms) have been initialized and I could
start my project.
I had to defined the components in the *.xconf and add some libe. This
libs are from 2.1.6. I will do it again for 2.2-dev (cocoon-trunk) as
soon the svn server is up again.
One question should I rather do the support for cform/flow in the core
or better in a plugin?
...but because I did not include all needed blocks I now get:
java.lang.NoClassDefFoundError: org/mozilla/javascript/Scriptable
at java.lang.Class.getDeclaredConstructors0(Native Method)
at
java.lang.Class.privateGetDeclaredConstructors(Class.java:1610)
at java.lang.Class.getConstructor0(Class.java:1922)
at java.lang.Class.newInstance0(Class.java:278)
at java.lang.Class.newInstance(Class.java:261)
at
org.apache.cocoon.core.container.ComponentFactory.newInstance(ComponentFactory.java:107)
at
org.apache.cocoon.core.container.SingleThreadedComponentHandler.doGet(SingleThreadedComponentHandler.java:55)
at
org.apache.cocoon.core.container.AbstractComponentHandler.get(AbstractComponentHandler.java:172)
at
org.apache.cocoon.core.container.CoreServiceManager.lookup(CoreServiceManager.java:370)
at
org.apache.cocoon.core.container.DefaultServiceSelector.select(DefaultServiceSelector.java:138)
at
org.apache.cocoon.components.treeprocessor.sitemap.FlowNode.service(FlowNode.java:62)
at
org.apache.cocoon.components.LifecycleHelper.setupComponent(LifecycleHelper.java:152)
at
org.apache.cocoon.components.LifecycleHelper.setupComponent(LifecycleHelper.java:106)
at
org.apache.cocoon.components.treeprocessor.DefaultTreeBuilder.setupNode(DefaultTreeBuilder.java:422)
at
org.apache.cocoon.components.treeprocessor.sitemap.FlowNodeBuilder.buildNode(FlowNodeBuilder.java:38)
at
org.apache.cocoon.components.treeprocessor.sitemap.SitemapNodeBuilder.buildNode(SitemapNodeBuilder.java:70)
at
org.apache.cocoon.components.treeprocessor.DefaultTreeBuilder.createTree(DefaultTreeBuilder.java:296)
at
org.apache.cocoon.components.treeprocessor.DefaultTreeBuilder.build(DefaultTreeBuilder.java:381)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.buildConcreteProcessor(TreeProcessor.java:401)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.setupConcreteProcessor(TreeProcessor.java:348)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:247)
at
org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:112)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:54)
at
org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:112)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:76)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.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:203)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:149)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:248)
at
org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:112)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:54)
at
org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:112)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:76)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.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:203)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:149)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:248)
at
org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:112)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:76)
at
org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(SelectNode.java:82)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:76)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.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:203)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:149)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:248)
at org.apache.cocoon.Cocoon.process(Cocoon.java:503)
at
org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1097)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:354)
at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1808)
at
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:525)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1758)
at org.mortbay.http.HttpServer.service(HttpServer.java:879)
at
org.mortbay.http.HttpConnection.service(HttpConnection.java:790)
at
org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:952)
at
org.mortbay.http.HttpConnection.handle(HttpConnection.java:807)
at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:197)
at
org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
at org.mortbay.util.ThreadPool
$PoolThread.run(ThreadPool.java:501)
> --David
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
Re: CForms and forrest
Posted by Thorsten Scherler <th...@apache.org>.
Cheers Ross. :)
I will have a look on the code as soon as I can. It seems that the cform
stuff right now is not priority one.
Anyway thx a million.
salu2
On Wed, 2005-04-20 at 12:44 +0100, Ross Gardler wrote:
> David Crossley wrote:
> > Thorsten Scherler wrote:
> >
> >>Seems to be that I am the first one in trying to do it.
> >>
> >>I just did some testing, but I actually I get
> >>
> >>Message: null
> >>
> >>Description: No details available.
> >>
> >>Sender: org.apache.cocoon.servlet.CocoonServlet
> >>
> >>Source: Cocoon Servlet
> >>
> >>Request URI
> >>
> >>dima/bearbeiten/
> >>
> >>cause
> >>
> >>org.apache.cocoon.forms.transformation.FormsTemplateTransformer
> >>
> >>I reckon I have not defined the needed components in the forrest-core.xconf and/or
> >> have not provided the needed jars in the lib.
> >>
> >>Anybody a hint what I have to do to enable the flow/cforms in forrest?
> >
> >
> > Forrest only ships the Cocoon Blocks that we currently need.
> > See lib/core/cocoon-*
> >
> > You would need to add the Cforms Block, relevant to the
> > cocoon-2.2 version that we are using.
> >
> > Yes you would need to add to forrest-core.xconf
>
> Actually, if you are working on this now I may as well start a branch
> with my experiments in the next plugins extensions. It allows plugins to
> provide their own xconf stuff. This part works.
>
> The part that doesn't work is allowing plugins to provide additions to
> the web.xml file. This is necessary for some blocks, like the database
> block which is what I wanted this functionality for and why I never
> finished it. Deadlines meant I had to hack a solution.
>
> The code is quite a long way out of sync with Head and I'm not able to
> spend time directly on this branch until after 0.7 is out. However, you
> might find it works for you in this use case.
>
> I'll mail when I set the branch up, may not be until tonight (GMT)
>
> Ross
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
Re: CForms and forrest
Posted by Ross Gardler <rg...@apache.org>.
David Crossley wrote:
> Thorsten Scherler wrote:
>
>>Seems to be that I am the first one in trying to do it.
>>
>>I just did some testing, but I actually I get
>>
>>Message: null
>>
>>Description: No details available.
>>
>>Sender: org.apache.cocoon.servlet.CocoonServlet
>>
>>Source: Cocoon Servlet
>>
>>Request URI
>>
>>dima/bearbeiten/
>>
>>cause
>>
>>org.apache.cocoon.forms.transformation.FormsTemplateTransformer
>>
>>I reckon I have not defined the needed components in the forrest-core.xconf and/or
>> have not provided the needed jars in the lib.
>>
>>Anybody a hint what I have to do to enable the flow/cforms in forrest?
>
>
> Forrest only ships the Cocoon Blocks that we currently need.
> See lib/core/cocoon-*
>
> You would need to add the Cforms Block, relevant to the
> cocoon-2.2 version that we are using.
>
> Yes you would need to add to forrest-core.xconf
Actually, if you are working on this now I may as well start a branch
with my experiments in the next plugins extensions. It allows plugins to
provide their own xconf stuff. This part works.
The part that doesn't work is allowing plugins to provide additions to
the web.xml file. This is necessary for some blocks, like the database
block which is what I wanted this functionality for and why I never
finished it. Deadlines meant I had to hack a solution.
The code is quite a long way out of sync with Head and I'm not able to
spend time directly on this branch until after 0.7 is out. However, you
might find it works for you in this use case.
I'll mail when I set the branch up, may not be until tonight (GMT)
Ross
Re: CForms and forrest
Posted by David Crossley <cr...@apache.org>.
Thorsten Scherler wrote:
> Seems to be that I am the first one in trying to do it.
>
> I just did some testing, but I actually I get
>
> Message: null
>
> Description: No details available.
>
> Sender: org.apache.cocoon.servlet.CocoonServlet
>
> Source: Cocoon Servlet
>
> Request URI
>
> dima/bearbeiten/
>
> cause
>
> org.apache.cocoon.forms.transformation.FormsTemplateTransformer
>
> I reckon I have not defined the needed components in the forrest-core.xconf and/or
> have not provided the needed jars in the lib.
>
> Anybody a hint what I have to do to enable the flow/cforms in forrest?
Forrest only ships the Cocoon Blocks that we currently need.
See lib/core/cocoon-*
You would need to add the Cforms Block, relevant to the
cocoon-2.2 version that we are using.
Yes you would need to add to forrest-core.xconf
See info about cocoon in our etc/cocoon_upgrade/README.txt
I am not saying that you need to upgrade our Cocoon,
just get some notes for how to add another block.
In addition to that readme, there is a wiki page at
http://wiki.apache.org/cocoon/AddingCocoonBlocksToForrest
(I don't know why that is on the wiki, rather than in
our own xdocs.)
--David
Re: CForms and forrest
Posted by Thorsten Scherler <th...@apache.org>.
Seems to be that I am the first one in trying to do it.
I just did some testing, but I actually I get
Message: null
Description: No details available.
Sender: org.apache.cocoon.servlet.CocoonServlet
Source: Cocoon Servlet
Request URI
dima/bearbeiten/
cause
org.apache.cocoon.forms.transformation.FormsTemplateTransformer
I reckon I have not defined the needed components in the forrest-core.xconf and/or
have not provided the needed jars in the lib.
Anybody a hint what I have to do to enable the flow/cforms in forrest?
TIA
salu2
On Tue, 2005-04-19 at 11:49 +0200, Thorsten Scherler wrote:
> Hello all,
>
> I am looking into integrate some applications (mainly workflows) written
> for cocoon with cforms and flow into forrest.
>
> I reckon it would be an input plugin that will transform all cform
> templates into xdocs format to later skin/view it. Has anybody made
> experience with this approach in forrest?
>
> The idea is to create a framework plugin (input.cforms/flow) that will
> be able to pickup a project specific implementation of a flow/cform
> work-flow. Each work-flow should *not* go into his own plugin but should
> be implemented in the project. Ideally the usage of custom sitemap.xmap
> in the project should be minimal.
>
> TIA for any informations and experience or tips and tricks. ;-)
>
> salu2
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)