Re: [WSIF] Dynamic Invocation Evaluation Question

Fri, 23 Feb 2007 14:53:49 -0800

Chris,

I certainly would be interested in seeing what you did with Axiom.

To both,

I think there are benefits, albeit different, to each path, i.e., starting with WSIF or starting with Axiom.  So here's my summary at this point keeping in mind that I need to take a closer look at the Axiom functionality and experiment more with WSIF.

WSIF Pros:
  1. Out of the box it supports dynamic invocation of endpoints.
  2. It supports both SOAP and JMS.
  3. It's a manageable size.
  4. It appears stable.
  5. Less initial development work
  6. Can extend to support other message types such as MQ?
WSIF Not so Pros:
  1. It's based on dated dependencies
  2. Low community/development activity - this is a sticking point with my CTO but I think that the risk is manageable for this particular framework.
Axiom Pros:
  1. Part of Axis2 implementation
  2. Dependencies are current
  3. Supports SOAP and is JMS aware
  4. High community/development activity
Axiom Not so Pros
  1. More initial development work for dynamic functionality and type management
  2. Would have to develop WSDL extension functionality to support dynamic JMS client and MQ (not sure if I worded that correctly)
My requirements can be summarized as such:
  1. Customers don't want a new client component for each service they need to invoke (there's context for this)
  2. Need to support SOAP and REST style services, JMS endpoints, and MQ
  3. Needs to interface with current product which is "C" based (not really a problem)
  4. I can keep type handling to the basics for now
If there's any more input from either or you, or anyone else, with regards to the points expressed above, whether experience or opinion, I would appreciate it.  I will do the grunt research on both and will make a decision by mid next week.

Again, thanks for the quick responses and for your time,

Cliff
Clifford Audinet
Software Architect

Stonebranch, Inc.
950 North Point Parkway
Suite 200
Alpharetta, Ga 30005
(678) 366-7887 X316
http://www.stonebranch.com
mailto:[EMAIL PROTECTED]


Aleksander Slominski wrote: 
Christian Kloner wrote:
  
hi,

why do you think, that Axis2 Java has no support for dynamic
invocation? The thing is, if you use the RawXmlMessage Handler for
sending and receiving messages, you can construct with Axiom any SOAP
message and send it through the net to any destination. I also used it
in my workflow project and created an own invocation API around it. if
you are interested in it, i can manage to give you access to it.

WSIF was a fine project, but i think it is a bit outdated. I used it
in my invocation api 2 years ago but the problem was, that i had to
invoke web services really dynamically without having any java object
to deserialize xml to. as i know, for every xml message, you need to
register a java object to deserialize to. but what is, if you don't
have any java class compiled for the receiving xml message... please
tell me, if I am not correct and WSIF now supports a really dynamic
approach for complex datatype handling. thanks.
    
chris,

at some stage you need to do /some/ type handling - depending on
workflow lang and how you use it you may get away with xpath expressions
and no types validation - the value WSIF could add if you invoke not
just XML web service but anything that can be described in WSDL so
workflow interacts with services using common abstraction (WSDL and WSIF
API)

best,

alek
  


Clifford Audinet wrote:
    
Hello,

I have a project that has several requirements related to dynamic
invocation of web services using SOAP and async messaging using JMS.
Our product is written in C and so initially I thought that using the
new Axis2/C implementation might be the way to go as it supports client
side dynamic invocation of web services.

However, there are some clear benefits in implementing the web
services client in Java.  This led me to look at the Axis2 Java
implementation which doesn't have support for dynamic invocation.  That
lead me to the WSIF project which appears to meet my requirements.  So a
couple of questions:

1) It looks like the last release was 2003 and that there was a release
planned for 2006.  Is that release still planned?
2) As I will be going through the samples over the next couple of days
is it advisable to pull the source for bug fixes, etc that occurred post
2003 release?

Thank you for your time,

Cliff

      
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to