"Using the Sun POJO Service Engine" is a guide to the tools available in the Plain Old Java Objects (POJO) Service Engine that enable users to build business integration applications based on JBI standards and using Plain Old Java Objects.

An overview of the POJO Service Engine explains that it automates much of the annotation and generates the code framework in which you can define your applications. The service engine simplifies the process by defining very few annotation and API classes. It provides flexibility by use of method signatures and by handling synchronous and asynchronous messages in a message-oriented way.

The POJO Service Engine supports a message-oriented paradigm rather than service-oriented, the overview continues. WSDL documents can be used but are not required. The service engine allows you to define both service providers and consumers with or without bindings (WSDL documents). You can also call the POJO providers you create from a BPEL process, and you can call a BPEL process from a POJO service consumer.

Unlike the Java EE Service Engine, the POJO Service Engine does not require a web or EJB container. The message data structure does not need to be exposed in a service description language such as WSDL, although a WSDL document can be used if that is preferred. The POJO Service Engine can access JBI normalized message objects and message exchange objects directly, which supports RESTful services, provides options for streaming and handling non-XML data, and avoids unnecessary unmarshaling of the incoming messages to Java objects.

The contents of the Sun POJO Service Engine User's Guide include:

• Providing and Consuming JBI Services
• POJO Service Engine API Annotation and Classes
• Creating a POJO Service Provider (Without Binding)
• Creating a POJO Service Provider (With Binding)
• Creating a POJO Service Provider in an Existing Java Application
• Creating a POJO Service Consumer (Without Binding)
• Creating a POJO Service Consumer (With Binding)
• Creating a Composite Application for a POJO Service Provider (Without Binding)
• Creating a Composite Application for a POJO Service Provider (With Binding)
• Creating a Composite Application for a POJO Service Consumer (Without Binding)
• Creating a Composite Application for a POJO Service Consumer (With Binding)
• Invoking POJO Services from a Business Process
• Calling a Business Process From a POJO Service
• Configuring Runtime Properties for the POJO Service Engine

More Information

POJOs in Action [...read more...]

		fullsource
Print Email Current Profile Archive Blog Generate newsletter