Hi manoj,
Manoj Mallawaarachchie wrote:
Hi All,
STEP 1
I'm now preparing some basic documet for background work in my blog
http://manoj-ws.blogspot.com/ .
I'm doing this for summarize the SOAP Encoding requirements and
challanges in it's implementation. This helps for developers to easily
get start other than reading big documents.(my aim is to provice first
level information for get start)
Why don't u create this doc in axis2 wiki. That is the best place to
share the documents. Create your proposal anywhere starting from
http://wiki.apache.org/ws/FrontPage/Axis2. Or ust post your doc the dev list
-- Chinthaka
STEP 2
Read and undestand the SOAP Encoding and specifications. And document
key areas which need for development.
STEP 3
Prepare the proposal for SOAP Encoding module.
STEP 4
Design Architecture and identify Modules (sub systems)
STEP 5
Design the Interfaces and functions/methods
.......... More
Please give your feed back for above steps for improvements.
Best regards,
Manoj
On 8/23/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
FWIW,
Before I turned to Axis, I was trying to get an rpc-encoded SOAP client working
using JAXB and XMLBeans. I already had a JMS transport framework available for
sending text messages between other applications, and didn't want to take on
the work of getting it working with Axis. (The existing Axis layer didn't
support all our requirements.)
I found that XMLBeans could take in the WSDL and generate classes for
everything in the WSDL schema section if also fed a file (via an import
statement in the WSDL) containing the SOAP encoding schema--even handled the
arrays, which pleasantly surprised me.
It didn't, however, generate Java for any of the operations--so, for example, if I had a
"createOrder" operation that had complex types Customer and Order as parameters--the
XMLBeans generated classes could create Customer and Order, but no way to get the
"createOrder" element.
Same with JAXB--using the "experimental" -wsdl tag with JWSDP 1.5, I was able
to feed it my WSDL and get classes that seem to support everything in the WSDL schema
(again, including the arrays), but again--no support for the operation-level elements.
In case anyone was curious about what doesn't work with XMLBeans/JAXB and
rpc-style services--that's as far as I progressed before I gave up and switched
to Axis.
Meghan
Ajith,
people have tried XMLBeans/extra schemas with SOAP-enc rules...doesn't work :)
-- dims
On 8/23/05, Ajith Ranabahu <[EMAIL PROTECTED]> wrote:
Hi Manoj,
I see Chinthaka has pointed you to the correct documentation and code.
Axis 1.x is the best source to see how SOAP encoding should work.
However Axis2 way is slighlty different and these are the limitations we
have right now in a more specific manner..
1. Axis 1 used a built in databinding but Axis2 has a pluggable model
for the databinding frameworks. The problem we have right now is that
since we feed the the schema section of the WSDL to generate the
bindings to the third party framework, that framework (Say XMLBeans)
has to be made aware of the SOAP encoding rules. XMLBeans compiler takes
in extra schemas in compilation so theoretically we should be able to
feed the SOAP encoding in, in the form of an schema. I'm not sure how
far this'll work but we can surely try!
2. If (1) is not feasible we'll have to disable SOAP encoding in third
party frameworks except for our own framework. This 'own framework' is
.>> still not existing (:))but I guess it'll be based on the Axis 1 (
These are the main issues we have regarding SOAPEncoding right now.
Eran Chinthaka wrote:
Hi Manoj,
The best reference I'd suggest is Axis 1.x. I think it has a very robust and
good implementation of SOAP encoding. Having understood that if you have any
questions in implementing that to Axis2, feel free to ask that from the list
again.
You might find some of the tutorials found in http://ws.apache.org/axis2
also useful to understand more abt Axis2.
Chinthaka
--
Davanum Srinivas : http://wso2.com/ - Oxygenating The Web Service Platform
