Is there any reason why we create a new BeanDefinitionStoreException
from a BeanDefinitionStoreException? Do we add more information? Is
there a reason for getting rid of the root cause?
AbstractSettingsBeanFactoryPostProcessor:
protected void processProperties(ConfigurableListableBeanFactory
Bonjour,
is it impossible or my explanation are too 'messy' or my english too
scrambled ??
just let me know...
thanks.
Seb
Sébastien Geindre a écrit :
Hello everybody,
i need to make a conditional treatment in my sitemap :
generator -- transformer A -(if condition on xml)-
Hi Sébastien,
I'm not the Cocoon guru around here, but could you elaborate on the kind
of xml condition?
Perhaps there is help :-)
Florian
Sébastien Geindre wrote:
Bonjour,
is it impossible or my explanation are too 'messy' or my english too
scrambled ??
just let me know...
thanks.
What you outline we used to call content-based pipelines - and is not
yet supported. By intention in the first place but the opinions change
on this topic. You should find something in the archives.
Joerg
On 22.11.2007 4:28 Uhr, Sébastien Geindre wrote:
Bonjour,
is it impossible or my
Dev at weitling a écrit :
Hi Sébastien,
I'm not the Cocoon guru around here, but could you elaborate on the kind
of xml condition?
Perhaps there is help :-)
ok i'll try:
the B1 transformer post http request to a webservice
the B2 just transform XML data
A transformer compute :
-
Well, my help looks like throwing a life-belt without a rope...
If your transformer B1 and B2 are simple XSL you could merge their
stylesheets and selecting the appropriate templates depending on your
content.
Another idea would be writing a custom selector choosing the transformer.
Flowscript
Hi Bertrand,
Bertrand Delacretaz schrieb:
On Nov 21, 2007 10:39 AM, Reinhard Haller
[EMAIL PROTECTED] wrote:
...The html-document doesn't contain any charset spec and neko has a
charset problem (the charset of the http response is utf-8)
I've had to use the input-encoding
Dev at weitling a écrit :
Well, my help looks like throwing a life-belt without a rope...
If your transformer B1 and B2 are simple XSL you could merge their
stylesheets and selecting the appropriate templates depending on your
content.
unfortunaletly, one of them is a custom transformer
Something with an action [1] or XSP action [2]?
generator
transformer A
action
-- transformer B1
-- transformer C
-- serializer
transformer B2
transformer C
serializer
The action analyses the stream from transformer A and returns
action:set-success/ or action:set-failure/. On success, the
I did not understand you questions, but here's the content's of
Bloclk/COB-INF/sitemap.xmap. I have used the same file for testing
Cocoon 2.1 application.
?xml version=1.0 encoding=iso-8859-1?
map:sitemap xmlns:map=http://apache.org/cocoon/sitemap/1.0;
map:components
map:generators
Sébastien Geindre wrote:
Dev at weitling a écrit :
Another idea would be writing a custom selector choosing the
transformer.
custom selector ?
it will make the test on xml, and this xml could be pass to next
transformer ?
That was one of my dreams, looking at the API of Selector it
Robin Rigby a écrit :
Something with an action [1] or XSP action [2]?
generator
transformer A
action
-- transformer B1
-- transformer C
-- serializer
transformer B2
transformer C
serializer
The action analyses the stream from transformer A and returns
action:set-success/ or
Ok, It's working now. Basically I removed the components definition from
the sitemap.xmap. It worked fine. Now, I need someone to explain to me
what happened. I guess I should not redefine in my sitemap component,
because this will override the config in the war file (the platform). I
don't
Hi,
I'm migrating from Cocoon 2.1 to Cocoon 2.2.
Cocoon 2.2 is deployed as a servlet in Tomcat along with 2 other servlets:
Axis 2 and eXist xmldb.
It seems with Cocoon 2.2 I can call my 2 other servlets from Cocoon and get
any xml result they will generate in my sitemap.
Can I do that with
Raphaël Piéroni pisze:
Grzegorz Kossakowski a écrit :
Raphaël Piéroni pisze:
Hello Raphaël
Hi Grzegorz,
Could you explain how the concrete block is chosen? What has an effect
on making choice?
Yup, an http request parameter is contains a hint to the name of the block.
That
Thanks Grzegorz for this detailed reply, it really helps.
I will take a look at the demos as well.
Regards,
Josh
Grzegorz Kossakowski-3 wrote:
Josh2007 pisze:
Hi,
I'm migrating from Cocoon 2.1 to Cocoon 2.2.
Cocoon 2.2 is deployed as a servlet in Tomcat along with 2 other
servlets:
Josh2007 pisze:
Hi,
I'm migrating from Cocoon 2.1 to Cocoon 2.2.
Cocoon 2.2 is deployed as a servlet in Tomcat along with 2 other servlets:
Axis 2 and eXist xmldb.
It seems with Cocoon 2.2 I can call my 2 other servlets from Cocoon and get
any xml result they will generate in my sitemap.
Grzegorz Kossakowski a écrit :
Raphaël Piéroni pisze:
Grzegorz Kossakowski a écrit :
Raphaël Piéroni pisze:
Hello Raphaël
Hi Grzegorz,
Could you explain how the concrete block is chosen? What has an effect
on making choice?
Yup, an http request
Not quite true. You can accomplish this using XMLFileModule.
Joerg Heinicke wrote:
What you outline we used to call content-based pipelines - and is not
yet supported. By intention in the first place but the opinions change
on this topic. You should find something in the archives.
Joerg
We are using the pattern similar to below in many, many places in our
application. I should also note that we no longer use XMLFileModule but
a new XPathXMLFileModule that I will be checking in shortly.
XPathXMLFileModule works similar to XMLFileModule but it caches
correctly and has more
On 22.11.2007 5:51 Uhr, Reinhard Haller wrote:
...The html-document doesn't contain any charset spec and neko has a
charset problem (the charset of the http response is utf-8)
I've had to use the input-encoding parameter for neko to work
correctly, for example:
map:transform
Mansour wrote:
Ok, It's working now. Basically I removed the components definition from
the sitemap.xmap. It worked fine. Now, I need someone to explain to me
what happened.
Previously in the sitemap you had this:
map:generator label=content
logger=sitemap.generator.file name=file
On 22.11.2007 9:23 Uhr, Mansour wrote:
Ok, It's working now. Basically I removed the components definition from
the sitemap.xmap. It worked fine. Now, I need someone to explain to me
what happened. I guess I should not redefine in my sitemap component,
because this will override the config in
Joerg Heinicke schrieb:
On 22.11.2007 5:51 Uhr, Reinhard Haller wrote:
...The html-document doesn't contain any charset spec and neko has a
charset problem (the charset of the http response is utf-8)
I've had to use the input-encoding parameter for neko to work
correctly, for
24 matches
Mail list logo
