[#MULE-1206] JdbcMessageDispatcher ignores custom result set handler class

Similar Issues:
~~MULE-761~~ JdbcMessageDispatcher failure when performing a query with null parameters
~~MULE-3238~~ JdbcConnector & JdbcMessageDispatcher are leaving connections open
~~MULE-3145~~ Attribute aliases for "class" are ignored in Mule Xml
~~MULE-2986~~ Setting custom sessionHandler on the connector
~~MULE-3553~~ using <custom-connector> results in ClassNotFoundException
~~MULE-4916~~ custom-security-filter should allow setting properties and referencing a bean
~~MULE-446~~ File Provider not setting ${ORIGINALFILENAME} properly
~~MULE-2827~~ Host & port set as individual parameters are ignored by RmiRegistryAgent
~~MULE-4538~~ Response Transformer Ignored
~~MULE-1301~~ AbstractXmlTransformer ignores encoding

Instead, the default MapHandler is used, though a custom result handler might have been configured on the connector by the user.

This issue relates to:
~~MULE-714~~ Support read queries for outbound JDBC

Ascending order - Click to sort in descending order

Hide

Permalink

Andrew Perepelytsya added a comment - 19/Nov/06 05:26 PM

Show

Andrew Perepelytsya added a comment - 19/Nov/06 05:26 PM Fixed in http://fisheye.codehaus.org/changelog/mule/?cs=3932

Vote (0)

Watch (0)

Mule