Select one of the following options for creating SDO objects:

• EclipseLink is an open source, object-relational mapping package for Java developers. EclipseLink provides a framework for storing Java objects in a relational database or converting Java objects to XML documents.

  Use EclipseLink to create SDO objects. For instructions on installing, configuring, and using EclipseLink to create SDO objects, visit the following URL:

  http://wiki.eclipse.org/EclipseLink/Installing_and_Configuring_EclipseLink
  

• Oracle JDeveloper enables you to create an SDO service interface for JPA entities. While this feature is more tailored for use with the Oracle Application Development Framework (ADF) service binding in a SOA composite application, you can also use this feature with the Enterprise JavaBeans service binding in SOA composite applications. The SDO service interface feature generates the necessary WSDL and XSD files. If you use this feature, you must perform the following tasks to work with the Enterprise JavaBeans service binding:

  • Browse for and select this WSDL file in the WSDL Chooser dialog, which is accessible from the WSDL URL field of the Create EJB Service dialog (described in Creating an Enterprise JavaBeans Service in ).

  • Add the BC4J Service Runtime library to the SOA project. To add this library, double-click the project and select Libraries and Classpath to add the library in the Project Properties dialog. You are now ready to design the business logic.

  For more information, see the SDO for Enterprise JavaBeans/JPA topic in the Oracle JDeveloper online help (this includes instructions on how create to an SDO service interface).

To create a session bean and import the SDO objects:

To create a profile and an EAR file:

An Enterprise JavaBeans bean must define the SDO types. The example that follows provides details.

InputStreamReader reader = new InputStreamReader(url.openStream());
StreamSource source = new StreamSource(reader);
List<SDOType> list = ((SDOXSDHelper) XSDHelper.INSTANCE).define(source, null);

The weblogic-ejb-jar.xml file is the descriptor file that must be added in the deployment jar. The weblogic-ejb-jar.xml file is automatically created when you create a session bean. This file must be modified by adding the entries shown in the following example:

<?xml version = '1.0' encoding = 'windows-1252'?>
<weblogic-ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                  xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-ejb-jar
 http://www.bea.com/ns/weblogic/weblogic-ejb-jar/1.0/weblogic-ejb-jar.xsd"
                  xmlns="http://www.bea.com/ns/weblogic/weblogic-ejb-jar">

    <weblogic-enterprise-bean>
    <ejb-name>HelloEJB</ejb-name>
    <stateless-session-descriptor>
      <pool>
        <initial-beans-in-free-pool>2</initial-beans-in-free-pool>
      </pool>
    </stateless-session-descriptor>
  </weblogic-enterprise-bean>

    </weblogic-ejb-jar>

Figure 37-2 provides a code example of a session bean with SDO logic defined.

Figure 37-2 Session Bean with Defined SDO Logic

Description of "Figure 37-2 Session Bean with Defined SDO Logic"

To generate the WSDL file, the Enterprise JavaBeans interface must use the following web service annotations. Use of these annotations is described in JSR 224: Java API for XML-Based Web Services (JAX-WS) 2.0. Visit the following URL for details:

http://www.jcp.org/en/jsr/detail?id=224

In addition, only a document/literal WSDL is currently supported by the Enterprise JavaBeans binding layer.

Table 37-1 describes the annotations to use.

@PortableWebService(
targetNamespace = "http://hello.demo.oracle/",
serviceName = "HelloService")

@WebMethod
@SOAPBinding(parameterStyle =
SOAPBinding.ParameterStyle.BARE)

@SDODatabinding(schemaLocation = "etc/HelloService.xsd")

The following example provides an example of an Enterprise JavaBeans interface with annotations.

@Remote
@PortableWebService(targetNamespace = "http://www.example.org/customer-example",
 serviceName = "CustomerSessionEJBService")
@SDODatabinding(schemaLocation = "customer.xsd")
public interface CustomerSessionEJB {
     @WebMethod(operationName="createCustomer")
   @SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
   @WebResult(targetNamespace = "http://www.example.org/customer-example",
 partName = "parameters", name = "customer")
   CustomerType createCustomer();
     @WebMethod(operationName="addPhoneNumber")
   @SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
   @WebResult(targetNamespace = "http://www.example.org/customer-example",
 partName = "parameters", name = "customer")
   CustomerType addPhoneNumber(@WebParam(targetNamespace =
 "http://www.example.org/customer-example", partName = "parameters", name =
 "phone-number")PhoneNumber phNumber);
} 

To deploy the EAR file from Oracle JDeveloper:

You can create the following types of Java interface-based Enterprise JavaBeans integrations with SOA composite applications:

• Invoke Java interface-based Enterprise JavaBeans from a SOA composite application

• Invoke a SOA composite application from Enterprise JavaBeans using a Java interface

To integrate Java interface-based Enterprise JavaBeans with SOA composite applications:

You can create the following types of SDO-based Enterprise JavaBeans integrations with SOA composite applications:

• Invoke SDO-based Enterprise JavaBeans from a SOA composite application

• Invoke a SOA composite application from Enterprise JavaBeans using SDO parameters

To integrate SDO-based Enterprise JavaBeans with SOA composite applications:

1. Go to the SOA composite application in the SOA Composite Editor.

2. In the Technology section of the Components window, drag the EJB icon into the appropriate swimlane, as described in Table 37-3.

   Table 37-3 Swimlane for EJB Service

   To Invoke...	Drag the EJB Service to this Swimlane...
   SDO-based Enterprise JavaBeans from a SOA composite application	External References
   A SOA composite application from Enterprise JavaBeans using SDO parameters	Exposed Services

   The Create EJB Service dialog is displayed.

3. In the Interface section, click WSDL.

4. See the step in Table 37-4 based on the swimlane in which you dragged the EJB service.

   Table 37-4 Swimlane Location

   If You Dragged the EJB Service to this Swimlane...	Then Go To...
   External References	44.a
   Exposed Services	44.b

   1. View the Create EJB Service dialog that displays in the External References swimlane, as shown in Figure 37-4.

      Figure 37-4 Create EJB Service in External References Swimlane

      
      Description of "Figure 37-4 Create EJB Service in External References Swimlane"

   2. View the Create EJB Service dialog that displays in the Exposed Services swimlane, as shown in Figure 37-5.

      Figure 37-5 Create EJB Service in Exposed Services Swimlane

      
      Description of "Figure 37-5 Create EJB Service in Exposed Services Swimlane"

5. Enter values appropriate to your environment. The fields that display differ based on the swimlane in which you dragged the EJB Service icon. Table 37-5 provides details.

   Table 37-5 Create EJB Service Dialog

   Field	Value
   Name	Accept the default value or enter a different name.
   Type	Displays the following value: Displays Reference if you dragged this icon into the External References swimlane. Displays Service if you dragged this icon into the Exposed Services swimlane.
   Version	Note: This field only displays if you dragged the EJB Service icon into the External References swimlane. Select the version of EJB to support: EJB2 or EJB3 (the default selection). If you select WSDL from the Interface list, only EJB3 is available for selection.
   Interface	Select WSDL.
   JNDI Name	Note: This field only displays if you dragged the EJB Service icon into the External References swimlane. Enter the JNDI name of your Enterprise JavaBeans.
   Jar File	Click the Search icon to select the EJB JAR file created in Designing an SDO-Based Enterprise JavaBeans Application. The JAR Chooser dialog searches for and displays JAR files starting in the SCA-INF/lib subdirectory of the current project directory. The JAR file includes the interface class and any supporting classes. Note: If you select a JAR file outside of the current project, Oracle JDeveloper creates a copy of the JAR file in the SCA-INF/lib directory of the current project. When prompted, click OK to accept.
   Java Interface	Click the Browse icon to invoke the Class Browser dialog for selecting the fully qualified Java class name of the previously created Enterprise JavaBeans interface. This class must exist in the selected JAR file. If a JAR file is not specified, it is assumed that the class is in the /SCA-INF/classes subdirectory of the current project directory. Note: If you use the Jar File field, you do not need to add a new JAR file to the project by selecting Project Properties > Libraries and Classpath > Add JAR/Directory from the Application main menu.
   WSDL URL	Note: Ensure that you have created the annotations for the Enterprise JavaBeans interface before generating the WSDL file, as described in How to Use Web Service Annotations. Click the second icon to the right to generate a WSDL file that represents the Enterprise JavaBeans interface. If you created SDO objects through Oracle JDeveloper, as described in How to Create SDO Objects Using the SDO Compiler, ensure that you select the WSDL file that was automatically generated with this option.
   Port Type	Select the port type.
   Callback Port Type	Select the callback port type (for asynchronous services).

6. Click OK.

Use the standard Enterprise JavaBeans client. The following example provides details:

InitialContext ic = new InitialContext(jndiProps);
SimpleEjb svc = (SimpleEjb) ic.lookup("PassthroughRef");
String result = svc.addBreadCrumb("RemoteTest");

To invoke an SDO - Enterprise JavaBeans service from Enterprise JavaBeans, you must use the client library. Follow these guidelines to design an Enterprise JavaBeans client.

• Look up the SOAServiceInvokerBean from the JNDI tree.

• Get an instance of SOAServiceFactory and ask the factory to return a proxy for the Enterprise JavaBeans service interface.

• You can include a client side Enterprise JavaBeans invocation library ($FMW_HOME/soa/soa/modules/oracle.soa.fabric_11.1.1/fabric-client.jar or the fabric-runtime.jar file located in the Oracle JDeveloper home directory or Oracle WebLogic Server) in the Enterprise JavaBeans client application. For example, the fabric-runtime.jar file can be located in the JDev_Home\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1 directory.

  If the Enterprise JavaBeans application is running in a different JVM than Oracle SOA Suite, the Enterprise JavaBeans application must reference the ejbClient library. The code that follows provides an example.

  You must specify the complete path of the service ID with the MyTestEJBService parameter of serviceFactory.createService (for example, "default/MyTestProject!1.0/MyTestEJBService"). If the complete path is not specified, you receive an EJBException- Could not locate the service error.

Properties props = new Properties();
        props.put(Context.INITIAL_CONTEXT_FACTORY,
 "weblogic.jndi.WLInitialContextFactory");
        props.put(Context.PROVIDER_URL, "t3://" + HOSTNAME + ":" + PORT);
        InitialContext ctx = new InitialContext(props);
        SOAServiceInvokerBean invoker =
                (SOAServiceInvokerBean)
 ctx.lookup("SOAServiceInvokerBean#oracle.integration.platform.blocks.sdox.ejb.api.
SOAServiceInvokerBean");

        //--  Create a SOAServiceFactory instance
        SOAServiceFactory serviceFactory = SOAServiceFactory.newInstance(invoker);

        //--  Get a dynamice proxy that is essentially a remote reference
        HelloInterface ejbRemote =
 serviceFactory.createService("complete_path/MyTestEJBService", HelloInterface.class);

        //--  Invoke methods
        Item item = (Item) DataFactory.INSTANCE.create(Item.class);
        item.setNumber(new BigInteger("32"));
        SayHello sayHello = (SayHello)
 DataFactory.INSTANCE.create(SayHello.class);
        sayHello.setItem(item);

        SayHelloResponse response = ejbRemote.sayHello(sayHello);
        Item reply = response.getResult();