This looks out of date at this point as the config-property is common across all of the
jca deployment types and handled by the custom ConnectionFactoryProperty. I don't see
any related failures in the profile service tests.
As Emanuel notes, there are some issues with essentially duplicate properties with
different names when config-property is an alias for specifying another metadata property.
Ideally the config-property would have those specified in a consistent manner as a
MapCompositeType, and would incorporate cf specific property descriptions from the rar
metadata, but that is another issue.
View the original post :
Reply to the post :