Extensible Cci Control; Overview; Using The Extensible Cci Control - BEA WebLogic User Manual

Using Application Explorer in BEA WebLogic Workshop to Create XML Schemas and Web Services

Extensible CCI Control

The following section describes the enhanced CCI control, which is extensible and provides
JCX with typed inputs and outputs for JCA in BEA WebLogic Workshop.

Overview

The extensible CCI control now offers:
• Method and tag validation. BEA WebLogic Workshop provides warnings regarding
invalid methods and tags.
• Improved error handling.
You can now define new methods that rely on the generic service and authService methods.
For example, you can define a JCX with a new method such as the following, without
having to write casting code or explicit transformations:
sapComDocumentSapRfcFunctions.BAPIMATERIALGETDETAILResponseDocument
getDetail(sapComDocumentSapRfcFunctions.BAPIMATERIALGETDETAILDocument
aRequest) throws java.lang.Exception
In addition, the extensible CCI control now generates a JCX file to which you can add your
own methods.

Using the Extensible CCI Control

The extensible CCI control functions much like a database control since it generates JCX
files to which you can add your own methods.
Your own methods can use the correct input and output types rather than the generic
XmlObject types that the JCA control uses. Since the control is just a proxy that uses a
reflection to call the relevant method, it will take care of the casting for you. There is no
longer a need to write custom code that does the cast or transformations that are cast
between an XmlObject.
For example, instead of the generic XmlObject:
XmlObject service(XmlObject input) throws java.lang.Exception;
you will be calling:
BAPIMATERIALGETDETAILResponseDocument
getDetail(BAPIMATERIALGETDETAILDocument aRequest) throws
java.lang.Exception;
BEA WebLogic Adapter for SAP User's Guide A-27