Axis 2 Web Services - A Reader View [ PART II ]

-

Axis2 Client API 

Axis 2 Client API handles In-Only and  In-Out MEPs. Axis2 Client API is compelled with so many MEPs. but the both In-Only and In-Out MEPs are widely used and recognized by huge community. 

 As Axis2 provides support for any MEP in the core level, implementing either is fairly straightforward. The In-Only and In-Out MEPs are supported with the two classes InOnlyMEPClient and InOutMEPClient, described in the next two sections.

InOnlyMEPClient Class provide support for fire and forgot messaging. The transport treated as one way. 

InOutMEPClient and the Call class that extends the InOutMEPClient provide the API for request-response messaging. Axis2 takes care of the complete operation, and all of the addressing properties except the To address are under the control of the Axis2.



Users can configure InOutMEPClient to behave differently using the following four parameters:
  1. Sender transport
  2. Listener transport
  3. Use separate listener
  4. Use blocking
The user can switch Axis2 to different interaction by simply switching the properties of Axis2 client API.  Axis2 client API supports for XML parsing and OMElement represent the chuck of XML. 




Comments

Post a Comment

Popular posts from this blog

Missionaries & Canibal Problem in AI using Pro Log

-
Introduction: Missionaries and Cannibals is a notable problem in Artificial Intelligence in which three Missionaries and three Cannibals attempt to cross a river to the other side using a boat.  However, there are constraints on the problem, most notably that there can never be more Cannibals than Missionaries on either side of the river (as they will be eaten!), the boat must always take across at least one person, and the goal state is when all Missionaries and all Cannibals have successfully reached the right side of the river from the left.  Thus, with these constraints in mind, they can be programmed into Prolog fairly simply, and a solution can be searched for.
Read more

Hide the navigation bar in jHipster Angular 2

-
Image
H iding a navigation bar is the easiest solution on Angular 2 version of jHipster . For this, you need to create a NavService and implement it on every component you need to show the navigation bar. Let's first create a service in the directory of your navigation component resides. import { Injectable } from '@angular/core'; @Injectable() export class NavbarService {   visible: boolean;   constructor() { this.visible = false; }   hide() { this.visible = false; }   show() { this.visible = true; }   toggle() { this.visible = !this.visible; } } There after you need to call this service on your navigation component constructor import { Component } from '@angular/core'; import { NavbarService } from './navbar.service'; @Component({   moduleId: module.id,   selector: 'sd-navbar',   templateUrl: 'navbar.component.html' }) export class NavbarComponent {   constructor( public nav: NavbarService ) {} } After the
Read more

Spring Boot - No Need to Restart the Development Server for Each Time

-
It's time for thinking about fastening your development on Spring Boot, Let's do some changes in dependency management and achieve the goals Spring Boot Developer Tools dependency doing a great job on change detection and refresh your current development server.   Just adding the following dependency on the pom.xml, if you are working with maven <dependencies> <dependency> <groupId> org.springframework.boot </groupId> <artifactId> spring-boot-devtools </artifactId> <optional> true </optional> </dependency> </dependencies> If you are going with Gradle dependencies { compile( "org.springframework.boot:spring-boot-devtools" ) }
Read more