Oracle Application Server Logo
   
   
Welcome selected tab: Features    
 

Core Features
J2EE 1.3 Compatible
Object-Relational Persistence
Web Services
     
    Core Features
     
  • J2EE Standards Support

    Oracle Application Server Containers for J2EE is J2EE 1.3 compatible, providing complete support for all J2EE 1.3 APIs -- JavaServer Pages 1.2, Java Servlet 2.3, Enterprise JavaBeans 2.0, JDBC 2.0 Extension, J2EE Connector Architecture 1.0, Java Message Service 1.02b, Java Transaction API 1.0, Java API for XML Processing 1.1, Java Authentication and Authorization Service 1.0, JavaMail 1.2, and Java Activation Framework 1.0.

    With Oracle Application Server Containers for J2EE you can take advantage of all that the J2EE platform has to offer to create flexible, secure, portable, and highly performant applications.

  • Industry Leading Object-Relational Persistence Solution

    Oracle TopLink is the industry leading Java object-to-relational persistence architecture, that provides a highly flexible and productive mechanism for storing Java objects and Enterprise Java Beans (EJBs) in relational database tables. TopLink offers you excellent performance and choice, working with any database, any application server, any development toolset and process, and any J2EE architecture.

    Through its support for all J2EE architectures, TopLink allows you to use the increasingly popular POJO (plain old Java objects) model, offering you the ability to develop and deploy applications today, safe in the knowledge that migration to the next generation EJB 3.0 architecture will be simpler and easier.

  • Web Services Support

    Oracle Application Server Web Services are tightly integrated with J2EE so that new and existing applications can easily be exposed as Web services. Web services executing on Oracle Application Server Containers for J2EE benefit from all the runtime and lifecycle management elements of J2EE applications. In addition to J2EE application components, the following types of Web services can be exposed :

      * Stateless or Stateful Java classes as RPC or Document Style Web services
      * Stateless session EJBs as Web services
      * PL/SQL Stored Procedures as Web services
      * JMS endpoints (Topics and Queues) as Document Style Web services

    OracleAS Web services supports the use of both typed and untyped SOAP messages, enabling better interoperability with Web services running on .NET. Access to SOAP headers is provided via an API enabling the use of SOAP headers to transmit and receive additional semantic information from messages.

    To provide a simpler testing environment for Web services, a dynamic WSDL tester is provided. The dynamic WSDL tester constructs a Web based test client from a given WSDL document, enabling deployed Web services to be invoked without needing to explicitly build a client.

 
   
    OC4J on OTN

 

Check the OC4J page on OTN for the latest information, technical notes and how-to examples.

 


 
 
  Welcome  |  Features 
 
Copyright © 2003, 2005 Oracle. All Rights Reserved.