[JAVAEETUTORIAL-229] Use EIS-specific API in the outboundconnector example Created: 01/Aug/13  Updated: 11/Sep/13  Resolved: 11/Sep/13

Status: Resolved
Project: javaeetutorial
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.3

Type: Improvement Priority: Major
Reporter: rcervera Assignee: rcervera
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


Replace the CCI implementation by a custom EIS-specific interface and implementation to access the resource adapter from the web application, as recommended by Siva and Jagadish from JCA. Update the Connector Examples chapter accordingly.

Comment by Kim Haase [ 02/Aug/13 ]

When you redo this example, you may want to use the naming conventions (with hyphens) described in http://docs.oracle.com/javaee/7/tutorial/doc/usingexamples006.htm#GEXAP. It's not very important, so no one mentioned it for the August release – it's great just to have the examples.

Comment by rcervera [ 02/Aug/13 ]

Thanks Kim, I'll fix that for the next release.

Comment by rcervera [ 11/Sep/13 ]

Replaced the Common Client Interface (CCI) by a simpler, EIS-specific, custom client interface.

Generated at Tue Oct 06 20:12:05 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.