local & global variabes at filters, tranformer and destinations

[albertosaez]

I've been testing the 'live' of variables defined with localMap /globalMap.

Global variables defined at filter:
+ Can be readed at transformation.
+ Can't be readed at destination

Local variables defined at filter:
+ Can't be readed at transformation.
+ Can't be readed at destination

Global variables defined at transformation:
+ Can't be readed at destination

Local variables defined at transformation:
+ Can be readed at destination


(I' m trying to read local & global variables at destination using the syntax:
${variable_name}

[chrisl]

Re: local & global variabes at filters, tranformer and destinations

We have updated the functionality of globalVars in 1.2. The latest source in Subversion includes this functionality (so that global variables are accessible from the destinations).

It is expected behavior for variables defined in the filter to be non accessible from other parts of the channel. All variable definitions should take place in the transformer only.

Hope this helps!
-Chris

[albertosaez]

Re: local & global variabes at filters, tranformer and destinations

Thanks for the answer. This is clear now.

[dheeraj]

Hi

there are few carriers or data structures which are available at some places in a channel, across a channel. There are inbuilt variables like

'tmp' and 'msg' which are available at source and destination filter and transformer and 'message.rawData' and 'message.encodedData' gives the incoming and outgoing message. 'channelMap' , 'globalMap' , 'connectorMap' are the maps which can be used to share variables and there values at various places. I am still searching for the scope of various variables inbuilt and user defined.

Thanks and Regards,
Dheeraj Bansal