hi alek,
Does not know if i understood correct but using raw XML messages does
not mean that you forgo type handling. you can still validate against
schema if the SOAP envelope conforms to doc/literal or
doc/literal/wrapped (WS-I Profile). If you use a dynamic approach you
have to parse wsdl files and schemata anyway to know, how the SOAP body
message should look like. In my approach, I transformed this information
into internal description representation and used visitor pattern to
visit the descriptions to create a dynamic SOAP envelope. Only the
values are needed in the right order with special marks for array,
complex type, attribute. But this is implementation specific.
Of course, if you have services using RMI or CORBA instead of SOAP you
need another abstraction layer where WSIF can help if it supports the
transport protocols. It's long time ago when i worked with it. :(
But the big advantage of Web service technology is to achieve
interoperability through standards revolving around XML. So I don't
think that another abstraction layer is really needed.
but in short, it depends on the requirements.
best regards,
chris
p.s.: how is the status of the GPEL engine? i am really interested in
how your implementation strategies are. do you do any static code
analyzing so far or rather do you use XMLBeans to get BPEL in memory
representation. Apache now started workflow project with synergy effect:
http://incubator.apache.org/projects/ode.html
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]
