Declaring the Custom Spring Bean Components in your Application

Configuring Web Services 17-3 Example 17–1 bea-jaxws.xml File endpoints endpoint nameEchoServicename implementation-class com.bea.wlevs.test.echo.impl.EchoServiceImpl implementation-class url-patternechourl-pattern wsdl-location META-INFwsdlecho.wsdl wsdl-location service-name {http:wsdl.oracle.comexamplescepecho}EchoService service-name port-name {http:wsdl.oracle.comexamplescepecho}EchoServicePort port-name endpoint endpoints For more information, see Section 4.7, Managing Libraries and Other Non-Class Files in Oracle CEP Projects .

4. Reference the bea-jaxws.xml file in the MANIFEST.MF file using the

BEA-JAXWS-Descriptor header: BEA-JAXWS-Descriptor: META-INFbea-jaxws.xml; For more information, see Section 4.7, Managing Libraries and Other Non-Class Files in Oracle CEP Projects .

5. Import the following packages to the Oracle CEP application in the MANIFEST.MF

file using the Import-Package header: Import-Package: com.ctc.wstx.stax, com.sun.xml.bind.v2, com.sun.xml.messaging.saaj.soap, com.sun.xml.ws, javax.jws, javax.xml.bind, javax.xml.bind.annotation, javax.xml.namespace, javax.xml.soap, javax.xml.transform, javax.xml.transform.stream, javax.xml.ws, Table 17–1 bea-jaxws.xml File Attributes Attribute Description name The name of the web service. implementation-class The class that implements the service. url-pattern The url pattern to access the webservice. wsdl-location Relative path to the wsdl in the bundle. service-name QName of the service. port-name QName of the port. 17-4 Oracle Complex Event Processing Developers Guide javax.xml.ws.spi, org.xml.sax, weblogic.xml.stax; For more information, see Section 4.7, Managing Libraries and Other Non-Class Files in Oracle CEP Projects . 6. Add a glassfish-ws element to the Oracle CEP server DOMAIN_ DIR configconfig.xml file that describes your Oracle CEP domain, where DOMAIN_DIR refers to your domain directory: glassfish-ws nameJAXWSname http-service-nameJettyServerhttp-service-name glassfish-ws 18 Configuring Applications With Data Cartridges 18-1 18 Configuring Applications With Data Cartridges This section describes: ■ Section 18.1, Understanding Data Cartridge Application Context ■ Section 18.2, How to Configure Oracle Spatial Application Context ■ Section 18.3, How to Configure Oracle JDBC Data Cartridge Application Context For more information on data cartridges, see Introduction to Data Cartridges in the Oracle Complex Event Processing CQL Language Reference.

18.1 Understanding Data Cartridge Application Context

Depending on the data cartridge implementation, you may be able to define an application context that the Oracle CEP server propagates to an instance of the data cartridge and the complex objects it provides. You may configure an application context for the following data cartridges: ■ Section 18.2, How to Configure Oracle Spatial Application Context ■ Section 18.3, How to Configure Oracle JDBC Data Cartridge Application Context For more information on data cartridges, see Introduction to Data Cartridges in the Oracle Complex Event Processing CQL Language Reference.

18.2 How to Configure Oracle Spatial Application Context

You define an application context for an instance of Oracle Spatial using element spatial:context in your Oracle CEP application’s Event Processing Network EPN assembly file. All constructors and methods from com.oracle.cartridge.spatial.Geometry and Oracle Spatial functions are aware of spatial:context. For example, the SRID is automatically set from the value in the Oracle Spatial application context. For more information, see: ■ SDO_SRID in the Oracle Spatial Developers Guide at http:download.oracle.comdocscdE11882_ 01appdev.112e11830sdo_objrelschema.htmSPATL492 ■ Understanding Oracle Spatial in the Oracle Complex Event Processing CQL Language Reference