On 12/4/06, Bernhard Slominski <[EMAIL PROTECTED]> wrote:
Hi,
I was playing the the ChainProcessor and found out that there is no
default
mapping.
So I suggest that like the default mapping for the other build-in
processors
there should be the following default mapping:
<context-param>
<param-name>
org.apache.shale.remoting.CHAIN_RESOURCES
</param-name>
<param-value>
/chain/*:org.apache.shale.remoting.impl.ChainProcessor
</param-value>
</context-param>
What do you think?
My biggest concern about doing this by default would be that it would
introduce a new required dependency (commons-chain) -- currently Shale
Remoting depends only on commons logging. In addition, although Commons
Chain is quite nice, it is not the only way people might want to compose the
processing for an incoming Ajax request ... so locking just one way in as a
default would seem to exclude other options.
In the mean time, you can use the "Other" series of configuration parameters
to utilize the chain processor if you want it (although this is not
zero-config, of course).
Bernhard
Craig
