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
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
On 12/4/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: craigmcc
Date: Mon Dec 4 13:25:07 2006
New Revision: 482364
URL: http://svn.apache.org/viewvc?view=revrev=482364
Log:
First round of supporting events when DialogContextManager.create() or
DialogContextManager.remove() is called.
On 12/4/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
* Have the base classes implement Serializable where applicable
Sorry ... I should have discussed this on the list before making these
changes. It comes out of having been badly bit in cases where a subclass of
the base class *cannot*
On 12/4/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
On 12/4/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: craigmcc
Date: Mon Dec 4 13:25:07 2006
New Revision: 482364
URL: http://svn.apache.org/viewvc?view=revrev=482364
Log:
First round of supporting events when
On 12/4/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
The events I associate with either ends of a lifecycle (in the
context of web apps) are init and destroy. Do you think the callback
names onInit and onDestroy would be better (though I see onInstall and
onRemove making sense in the
