This content has been marked as final. Show 3 replies
According to the Waveset documentation Identity connectors provide advantages over resource adapters, including the following:
- Simplified deployment and management because connectors are less tightly bound with Waveset than resource adapters. By placing Java connector bundles in the appropriate directory within your web application, or placing .NET bundles in the appropriate directory in a remote .NET directory, you can extend on-demand the types of native resources that you can manage. Waveset automatically detects any newly deployed connectors.
- Connector release cycles do not rely upon Waveset release cycles. Connector releases can differ from Waveset releases , and you can add or update connectors in your deployment with less dependence on the particular version of Waveset you are currently using.
- Waveset loads each connector in a separate class loader. This enhances support for using multiple versions of a native API from within a single Waveset server.
- Use of the separate and less complex identity connector SPI to develop connectors (Java or .NET). You do not need to know or use any Waveset APIs.
For more information see http://docs.oracle.com/cd/E19225-01/821-0092/giiwd/index.html
Sorry, it's been a while, but better late then never, so - thanks. Your answer was actually helpful.
Glad I could help.
You may want to change your question to answered.