[RAMPART-188] unable to engage rampart 1.4 on websphere application server 6.1

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Cannot Reproduce
• Affects Version/s: 1.4
• Component/s: rampart-core, rampart-integration, rampart-policy, rampart-trust
• Environment: websphere application server 6.1.
• Assignee: Ruchith B. Gunaratne
• Reporter: shrikant
• Created: 31/Jul/08 01:16
• Updated: 21/Dec/10 12:48
• Resolved: 21/Dec/10 12:48

Description

I have enterprise app which contains a MDB and a web service client (java project) on websphere 6.1. I am using axis2 1.4 jars, rampart 1.4 for client project. When the mdb invokes the web service client, I am exception AxisFault: Trying to engage a module which is not available: rampart.

I am able to run the web service client in standalone mode, but when it is packaged and deployed within EAR its not able to engage the rampart module. However axis is able to engage the addressing module perfectly fine.

I have configured my application class loader policy as "parent last" to make sure that apps jars are loaded first.

I do not know why rampart module is not being engaged when the web service client application is deployed onto websphere application server 6.1. Any help will be appreciated.

Thank you,
Shrikant