[CXF-1841] Some issues with outbound jca connector

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0.9, 2.1.3
• Component/s: Integration
• Assignee: Willem Jiang
• Reporter: William Tam
• Created: 06/Oct/08 04:13
• Updated: 23/Jan/09 17:52
• Resolved: 16/Oct/08 07:27

Description

1. The client proxy factory does not get configured by Configurer to inject configurations. So, for example, the ws security cannot be enabled in JCA connector.
2. ManagedConnectionImpl should implement equals() ahd hashcode() based on properties as required by JCA 1.5
3. A single bus is shared by multiple web applications. It is not possible to have a per web application bus config.
4. If a bean class is defined in a WAR and it is referenced by bus config, the bus cannot be created when the JCA connector starts in WebSphere 6.1. The reason is JCA connector classloader cannot load the class in belong in a WAR.
5. The outbound connector APIs should be moved to the api module so that javadoc can be produced for them.