Points to remember : Java Messaging Service and Spring WebService

Spring Web Service can be easily integrated in a Messaging environment with the help of Java Messaging Service, we need to keep some basic points in mind while handling messages using JMS and Spring WS, these are given below and will be helpful in interviews too.
1) You need JMS jar in your class path to use JMS with Spring Webservice.
2) DefaultMessageListenerContainer  uses plain JMS client API, specifically a loop of MessageConsumer.receive() calls that also allow for transactional reception of messages (registering them with XA transactions). Designed to work in a native JMS environment as well as in a J2EE environment, with only minimal differences in configuration.
3) Generally to set the MessageListener of  DefaultMessageListenerContainer for incoming messages WebServiceMessageListener is used and configured like below:
  1. <property name="messageListener">
  2. <bean class="org.springframework.ws.transport.jms.WebServiceMessageListener>
  3. <property name="messageFactory" ref="messageFactory" />
  4. <property name="messageReceiver" ref="messageDispatcher" />
  5. </bean>
  6. </property>
4) The connectionfactory and messagedispatcher are configured in the Listener as shown above.
5) The MessageDispatcher sets the endpoint mapping and its type.You need to an endpoint class either by annotating a class with @Endpoint, @PayloadRoot or you need to define a bean as an endpoint in the context file like below,
  1. <bean class="org.springframework.ws.server.endpoint.mapping.PayloadRootQNameEndpointMapping">
  2. <property name="defaultEndpoint">
  3. <bean class="…
6) The main entrypoint is invoke(Source) method of the endpoint, which gets invoked with the contents of the requesting message .i.e when a request arrives at the server, and possibly returns a response.
7) Spring Web Services provides a WebServiceMessageDrivenBean, an EJB MessageDrivenBean

Comments

Post a Comment

Popular posts from this blog

Java Interview : Threads

Java came up with multi threading long time back, still the kind of response it invokes when this topic raises its head during interviews is not very encouraging. If you have attended an java interview, a couple of suppose to be very smart guys also know as lead developers will shower you with questions on multi threading, grilling you down to make sure what you are talking about, even asking you to write fork-join snippets to solve hadoop use cases. But if you are hired and you write a piece code using executor framework, you will be seen with suspicion generally reserved for people with casual shoes at cocktail parties. So here is post to start out thinking about threads. So a path of execution in java is known as a thread, appropriately an instance of Thread class. The main method runs in its own thread and starts up the program execution. If you implement the Runnable interface, you can run in a thread of you own. The Runnable interface has a run() method you implement your...
Read more

Spring Framework Interview Notes : Part Two Wiring

Image
The Spring container is the guy responsible to get the train moving when working with the Spring framework.  The dependency magic gets the things working by somehow getting all the stuff up and running. Now somehow we need to indicate to the spring container as to where and how to “wire” these beans. Remember these beans are also known as components. Components combine to form the structure and thus make the functionality. The concept of component scanning or component finding comes into the picture, literally searching the applications to find the beans required to create these beans. @ComponentScan is the annotation used by giving the the base packages where these components are defined using annotation or xml . Spring Framework Interview Wiring You can also use Autowiring with its attributes, which finds the beans by-name or by-type and injects them appropriately. @Component, @ComponentScan, @Autowired, @Named,  @Bean  with requires and quali...
Read more

Card Dealer In Java in Less than 5 minutes

Image
Code: package design; import java.util.Collections; import java.util.Stack; public class CardDealer { private int totalPlayers; private static Stack<Card> deck; CardDealer(int players){ totalPlayers=players; deck =  Deck.getCardDeck(); } public static void main(String[] args) { CardDealer cardDealer = new CardDealer(5); cardDealer.dealCards(); } public void dealCards(){ int cardsToPlayer = deck.size()/totalPlayers; for(int i=0;i<cardsToPlayer;i++){ for(int j=1;j<=totalPlayers;j++){ System.out.println("Player:"+j+ " gets "+deck.pop()); } } } private int getPlayers() { return totalPlayers; } }  class Deck{ static Stack<Card> deck = new Stack<Card>(); static Deck d=null; static { d = new Deck(); } public static Stack<Card> getCardDeck(){ return deck; } private Deck(){ populateDeckWithcards(); shuffle(); } pr...
Read more