Grzegorz Kossakowski a écrit :
Raphaël Piéroni pisze:
Hello,
Hello Raphaël
Hi Grzegorz,
I would like to redirect from a block to another block.
But this redirection is a little special because:
- the name of the block is dynamically found
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 parameter is base64 encoded. So i will need an action to decode it.
- the name of the pipeline in the called block is always the same
- it is possible that the block to be called is created long after the
calling one
(therefore i can't define the dependency in the servlet-service.xml)
Is this achievable? if yep, how?
Unfortunately, as for now I fear it's not possible to achieve but it wouldn't
be that hard to extend
current functionality to support dynamic connection to other blocks.
Before I go into details I would like to hear about your use-case. I've been
wondering if supporting
dynamic block connection is a good idea recently. I came to conclusion that in
most situations I
could imagine dynamic block connections are *not* needed.
Therefore I would like to hear more details about your case.
My use case is that my client might define new outputing formats. those
formats are defined
using xslt, and are stored in different jars.
I just want these jars (that the client can put in the war's classpath)
to be usable without modifying the
core servlet service of the webapp (which reside in the main block jar)
Regards,
Raphaël
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
