You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by ja...@apache.org on 2004/11/24 14:37:16 UTC

cvs commit: ws-fx/sandesha/src/org/apache/sandesha/server CreateSequenceProcessor.java

jaliya      2004/11/24 05:37:16

  Modified:    sandesha/src/org/apache/sandesha/server
                        CreateSequenceProcessor.java
  Log:
  set the sync property of the RMMessageContext depending on the replyTO address
  
  Revision  Changes    Path
  1.11      +4 -1      ws-fx/sandesha/src/org/apache/sandesha/server/CreateSequenceProcessor.java
  
  Index: CreateSequenceProcessor.java
  ===================================================================
  RCS file: /home/cvs/ws-fx/sandesha/src/org/apache/sandesha/server/CreateSequenceProcessor.java,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- CreateSequenceProcessor.java	20 Oct 2004 10:28:49 -0000	1.10
  +++ CreateSequenceProcessor.java	24 Nov 2004 13:37:16 -0000	1.11
  @@ -78,13 +78,15 @@
               //We have some synchronous stuff here
   
               if ((addrHeaders.getReplyTo().getAddress().toString()
  +                          
                       .equals("http://schemas.xmlsoap.org/ws/2003/03/addressing/role/anonymous"))
                       || (addrHeaders.getReplyTo().getAddress().toString()
                               .equals(Constants.NS_URI_ANONYMOUS))) {
  -
  +              
                   //Inform that we have a synchronous response.
                   rmMessageContext.getMsgContext().setResponseMessage(
                           new Message(resEnvelope));
  +                rmMessageContext.setSync(true);
                   return true;
               } else {
                   //FIX THIS FIX THIS
  @@ -97,6 +99,7 @@
   
                   rmMessageContext.setOutGoingAddress(addrHeaders.getReplyTo()
                           .getAddress().toString());
  +                rmMessageContext.setSync(false);
                   storageManger.addCreateSequenceResponse(rmMessageContext);
                   return false;
               }