-
1. Re: sql-listener behaviour problem
itarc Feb 29, 2008 2:27 AM (in response to itarc)Hello,
I investigated a bit more and I found that it should be a sql-listener problem.
I found that that code in the process method of sqlTableGatewayListener.javaif(MessagePayloadProxy.isUsingLegacyPatterns()) { props.setProperty(ListenerTagNames.SQL_ROW_DATA_TAG, obj); } else { payloadProxy.setPayload(message, obj); }
and this one in the messagePayloadProxy.javastatic { setUseLegacyPatterns(ModulePropertyManager.getPropertyManager(ModulePropertyManager.CORE_MODULE).getProperty(USE_LEGACY_EXCHANGE_PATTERNS_CONFIG, "false").equals("true")); }
It looks like I don't have the same configuration between te two environnement.
What does legacy exchange patterns mean ?
How can I set the USE_LEGACY_EXCHANGE_PATTERNS_CONFIG to "True" in the integration environnement ?
Thanks for your Help. -
2. Re: sql-provider behaviour problem
marklittle Feb 29, 2008 5:02 AM (in response to itarc)Is there any reason you're not using 4.2.1GA?
-
3. Re: sql-provider behaviour problem
itarc Feb 29, 2008 7:29 AM (in response to itarc)Effectively I have just made some verification.
I work with a 4.2GA release I downloaded in september on the developpement environnement.
On the other way that it is the 4.2.1GA that is installed on the integration environnement.
That may be the reason of this dissonance between the two environnements.
Unfortunatly, I can not test this today but I let you know on monday if it is solved.
I have anyway found a solution a few hours ago,
I added the "use.legacy.message.payload.exchange.patterns" property
into the core propetries of the jbossesb-properties.xml file
in the jbossesb.sar directory of the integration environnement.
And now I have my data at the right place. -
4. Re: sql-provider behaviour problem
itarc Mar 3, 2008 10:33 AM (in response to itarc)Hello,
My mistake was effectively a difference between the release version which was 4.2GA in development and 4.2.1GA in integration.
Thanks for your help.