[xgws-dev] CVS Update: codes/xsul/java/doc

[Aleksander Andrzej Slominski]

aslom       06/02/20 03:52:07

  Modified:    xsul/java/doc changes.html
  Log:
  for the record
  
  Revision  Changes    Path
  1.38      +16 -3     codes/xsul/java/doc/changes.html
  
  Index: changes.html
  ===================================================================
  RCS file: /l/extreme/cvs/codes/xsul/java/doc/changes.html,v
  retrieving revision 1.37
  retrieving revision 1.38
  diff -u -b -t -w -r1.37 -r1.38
  --- changes.html	20 Feb 2006 08:46:40 -0000	1.37
  +++ changes.html	20 Feb 2006 08:52:07 -0000	1.38
  @@ -10,14 +10,27 @@
   <h1>Changes to XSUL</h1>
   
   
  -<h3>(XSUL_2_1_x)</h3>
  +<h3>2006- (XSUL_2_1_x)</h3>
   
   <ul>
   
   
  +<li>2006-02-19:
  +<b>added <samp>isRequestResponseOperation()</samp> to <samp>WSIFOperation</samp> class</b>
  +(that is extension when comparing to Apache WSIF API)
  +so it is easier to know if operation is request-response or one-way.
  +Otherwise one would need to walk WSDL and find if it had output message
  +in an operation declared by walking WSDL.
  +<br/>
  +The same result can be obtained in XSUL: if createOutputMessage()
  +returns null in then there is no output message (so it is input only message!)
  +but that is somewhat not documented (though it works!)
  +as <samp>executeRequestResponseOperation(in, null, null)</samp> is equivalent to
  +<samp>executeInputOnlyOperation(in)</samp>
  +</li>
   
   <li>2006-02-19 :
  -one-way invocation in XWSIF API should now work ...
  +<b>one-way invocation in XWSIF API should now work</b> ...
   applied fixes to other problems reported by Shan (Shanmuga.MUHUNTHAN)
   mostly about XSUL not reusing sockets but it is still not fixed for one-way
   response messages (will require using thread pool maybe from util_concurrent)