Josef
I can't comment on PocketSoap development, but I can say that all the
Axis2 features are based on pure open standards from W3C and OASIS,
and tested for interoperability.
Paul
On 3/26/07, Stadelmann Josef <[EMAIL PROTECTED]> wrote:
Paul,
Thank you for your tip with TCPmon. my PockeSOAP VB Client talks now
to the Axis2 MyService5 Service; from VB6 to Java Axis2 Web-Services!
However I have the following long-term-concerns!
{-- extract/posted at/from
http://tech.groups.yahoo.com/group/pocketsoap/message/4812
Axis2 is a very flexibel Message Processing Engine and has the
concept of modules to extend functionality not directly belonging to
the application code in client and service.
i.e Endpoint-References / Modells should be configurable
i.e. encryption and decryption should be added at configuration time.
i.e. Authentication as well
Are there any plans to enhance PocketSOAP to support part of the same
existing or under development standing modules which Axis2 supports
today?
I have managed to add the proper SOAP-HEADERS and re-use the SOAP-ENV
returned from the service to conform to WS-ADDRESSING, and hence can
talk in scope=soapsession from VB-Client to Java-Axis2-Services
statefule using a ServiceGroupContext (-ID).
The same Java-Axis2-Service is used from Java-based-client-code as
well as from VB-based-client-code.
So I would like to see how one can snap-in, register, configure in a
xml file and have PocketSOAP-Clients engage i.e. WS-ADDRESSING in
order to overcome the burden of adding soap-headers through client
code.
I am interessed about the future development of PocketSOAP
Regards
Josef
--}
-----Ursprüngliche Nachricht-----
Von: Paul Fremantle [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 19. März 2007 10:12
An: [email protected]
Betreff: Re: [AXIS2] PocketSOAP or ASP.NET & Visual Studio.NET to
connect to an AXIS2 Web-Service
Josef
Have you already posted any TCPMON traces of the interactions with
PocketSOAP? If not I'd love to look at them. TCPMON captures the HTTP
level flows and you can save to a file.
Paul
On 3/19/07, Stadelmann Josef <[EMAIL PROTECTED]> wrote:
>
>
>
> Hi all,
>
> I would like your thoughts and know about your experiences on the following
> subject matters and approach.
>
> We have an Axis2 1.1 running and use Java clients based on the userguide
> SOAPClient example.
>
> Such a clients should now migrated away from Java to a Microsoft
> Environment.
>
> We have done some basic tests using Visaul Basic 6.0 and PocketSOAP. So far
> we are unable to talk to axis2 1.1 by PocketSOAP,
>
> maybe we do something wrong, which is possible in absence of richt
> documentation, or documentation adressing the specific needs
>
> of a PocketSOAP VB Client talking to an Axis2 1.1 web-service.
>
> So we aim at considering a move to and an introduction of Visual Studio.NET
> and ASP.NET to get a client able to talk to axis2 1.1
>
> For Both PocketSOAP & VB 6.0 as well as Visual Studio.NET + ASP.NET we would
> like to have your experiences.
>
> What is the better choice / approach to develope a client talking to an
> axis2 web services and passing an OM Element?
>
> Thank's for any hints and guidelines
> Josef
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
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]
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
