Michel,

You can look at JMS as an integration point. I do not have all your
requirements, but you can always utilize queues as intermediaries.

regards,

Hannington
--- In soapbuilders@yahoogroups.com, Michel Baille
<michel_baille@y...> wrote:
> Hi All,
>
> I have a design problem:
>
> Suppose I wan't to write a SOAP service that transfers messages to
a middleware (the middleware cannot be opened on the web). This SOAP
service must then open a connection to this middleware and transfer
each received messages on it.
>
> I would like my SOAP service to keep the connection with the
middleware open, to avoid opening / closing at each message
reception. What is the best way to do that ?
>
> Regards,
>
> Michel
>
>
>
>
> ---------------------------------
> Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
> Testez le nouveau Yahoo! Mail

http://www.geocities.com/Hofstede112112/index.html

http://www.geocities.com/Moxhampbps/index.html

Hi folks,

  I have a web service developed in Axis, input to the service is
customer address and output is list of customers.

I have a client in Visual Basic and uses MSSOAP Toolkit 3.0.

I get following error when i send a SOAP message.

SoapMapper: "Restoring Data into SoapMapper GetParcelsResult failed
HRESULT=0X800A005B  - Client:Unspecified error. HRESULT=0x800AOO5B

Please lookat my wsdl and other documents. Any pointers will be great
help.

http://www.erc.msstate.edu/~venu/question/


Thanks,
Venu

I am developing an interface between a new C#.NET client, and a Java
Servlet/JSP server application (Tomcat and JRun). The purpose of the
interface to to register for and receive reports, over the Internet.

I am coding the C# client now, and prototyping the server side in C#
as well. The next step is to implement the real web service on the
Java app server.

The question: for the server side, Apache Axis or Sun WSDP?

Martin

Hello All,

I'm novice to SODA. I'm trying to implement persistent server for IBM
Rational ClearQuest based on XMLRPC::Lite.
For "binary compatibility reasons" IBM Rational urges use of
ratlperl
(special Perl distribution based on ActiveState Perl v5.6.1 build
629) for using CQPerlExt Perl module, which provides a ClearQuest API.

Following is my sever code:
use lib "/opt/rational/clearquest/sun5/shlib";
use CQPerlExt;
use XMLRPC::Transport::HTTP;

our $session = CQPerlExt::CQSession_Build();
$session->UserLogon("user","password","CQDB","");

my $daemon = XMLRPC::Transport::HTTP::Daemon
   -> new (LocalPort => 8081)
   -> dispatch_to('CQ')
;
print "Contact to XMLRPC server at ", $daemon->url, "\n";
$daemon->handle;

package CQ;

sub LsProject {shift if UNIVERSAL::isa($_[0] => __PACKAGE__);
   my $queryDef = $session->BuildQuery("Project");
   $queryDef->BuildField("Name");

   my $operator=$queryDef->BuildFilterOperator
($CQPerlExt::CQ_BOOL_OP_AND);
   my $resultSet = $session->BuildResultSet($queryDef);

   $resultSet->Execute;
   my @Projects = ();
   push @Projects, $resultSet->GetColumnValue(1) while ($resultSet-
>MoveNext == $CQPerlExt::CQ_SUCCESS);

   print join(", ", @Projects), "\n";

   return [@Projects];
}


Client code:
#!C:/perl/bin/perl
# Have a chart made for us

use XMLRPC::Lite;

my $conn = XMLRPC::Lite
     -> proxy('http://server:8081/');

print @{$conn->
         on_debug(sub{print @_})->
         call(CQ.LsProject')
     -> result}, "\n";
     ;

POST http://trentino:8081/
Accept: text/xml
Accept: multipart/*
Content-Length: 117
Content-Type: text/xml

<?xml version="1.0" encoding="UTF-8"?
><methodCall><methodName>CQ.LsProject</methodName><params/></methodCal
l>
HTTP/1.1 200 OK
Date: Tue, 07 Oct 2003 15:53:30 GMT
Server: libwww-perl-daemon/1.24
Content-Length: 562
Content-Type: text/xml
Client-Date: Tue, 07 Oct 2003 15:53:30 GMT
Client-Peer: 137.167.6.80:8081
SOAPServer: SOAP::Lite/Perl/0.55

<?xml version="1.0" encoding="UTF-8"?
><methodResponse><fault><value><struct><member><name>faultString</name
><value><string>     (in cleanup) Not a HASH reference
at /opt/rational/clearquest/sun5/shlib/CQPerlExt.pm line 3174.
         (in cleanup) Not a HASH reference
at /opt/rational/clearquest/sun5/shlib/CQPerlExt.pm line 3512.
         (in cleanup) Not a HASH reference
at /opt/rational/clearquest/sun5/shlib/CQPerlExt.pm line 4564.
</string></value></member><member><name>faultCode</name><value><string
>Server</string></value></member></struct></value></fault></methodResp
onse>

As you can see the server returns nothing.

But as you can see on the line before return I print the list of the
Project. And as expected, the list of the projects it printed on the
server side. But it is lost somewhere on the way back to the client.

I'm wondering why XMLRPC::Lite loses output returned by the server.

The failure is reported each time in the same function:

sub DESTROY {
     my $self = tied(%{$_[0]}); # This line is reported as failed
     delete $ITERATORS{$self};
     if (exists $OWNER{$self}) {
         CQPerlExtc::delete_CQResultSet($self);
         delete $OWNER{$self};
     }
}

If I change the server and enter the stub which return the dummy
array prior the CQ API call everything works fine.
My stub looks like following:

sub LsProject {shift if UNIVERSAL::isa($_[0] => __PACKAGE__);
   my @Dummy = ("a", "b", "c");
# This would work
return [@Dummy ];
   my $queryDef = $session->BuildQuery("Project");
This would not work
#  return [@Dummy ];
   $queryDef->BuildField("Name");

   my $operator=$queryDef->BuildFilterOperator
($CQPerlExt::CQ_BOOL_OP_AND);
   my $resultSet = $session->BuildResultSet($queryDef);

   $resultSet->Execute;
   my @Projects = ();
   push @Projects, $resultSet->GetColumnValue(1) while ($resultSet-
>MoveNext == $CQPerlExt::CQ_SUCCESS);

   print join(", ", @Projects), "\n";

   return [@Projects];
}
Please note it the stup (return [@Dummy ];) is entered after the CQ
API call, it would'n return.
It looks like some kind of the memory management problem.

soapbuilders@yahoogroups.com wrote:

>    Date: Mon, 06 Oct 2003 17:00:57 -0000
>    From: "Venu Kanaparthy" <madhavsinghk@...>
> Subject: MSSOAP  Toolkit 3.0  & Apache Axis Interoperability
>
> Hi folks,
>
>  I have a web service developed in Axis, input to the service is
> customer address and output is list of customers.
>
> I have a client in Visual Basic and uses MSSOAP Toolkit 3.0.
>
> I get following error when i send a SOAP message.
>
> SoapMapper: "Restoring Data into SoapMapper GetParcelsResult failed
> HRESULT=0X800A005B  - Client:Unspecified error. HRESULT=0x800AOO5B
>
> Please lookat my wsdl and other documents. Any pointers will be great
> help.
>
> http://www.erc.msstate.edu/~venu/question/
>

My recommendation would be pull down a trial copy of mindreef 2.0 from
mindreef.com, have it act as a proxy between the two systems and let it
tell you who is getting anything wrong.

I havent used MSSOAP, dont know if it still being maintained, dont
recognise 0X800A005B as an obvious error, etc etc. Worry about the basic
issues 'is the url right' before worrying about interop details.

If there is an interop problem, check with the axis-users mail list and
consider filing it with the Axis bug db. This doesnt mean teams of
otherwise idle engineers will close their slashdot browsers and spring
into action fixing the bug, but someone may recognise the problem.

-steve

>    Date: Mon, 06 Oct 2003 20:34:53 -0000
>    From: "MartinKB" <martinkb@...>
> Subject: Apache Axis vs. Sun JWSDP
>
> I am developing an interface between a new C#.NET client, and a Java
> Servlet/JSP server application (Tomcat and JRun). The purpose of the
> interface to to register for and receive reports, over the Internet.
>
> I am coding the C# client now, and prototyping the server side in C#
> as well. The next step is to implement the real web service on the
> Java app server.
>
> The question: for the server side, Apache Axis or Sun WSDP?

Alternate question why not stick with the same language on both ends? It
makes dev easier, and if you have W2K3 server around you have already
paid for your app server anyway.

Axis runs on top of any Java app server (servlets 2.3), though BEA is
intermittently trouble. It comes with source, instead of much in the way
of documentation. What documentation there is assumes you know what you
are doing and sneers at the weak. It has a nice WSDL to JUnit feature
that can be used to test any implementation of a service. And because
you can integrate it inside your WAR file, you retain control of
versioning, get uniformity across systems, etc etc. As it supports DIME
it also lets you upload big binaries from C# land. But it is kind of
large, bits of the code are scary in places (long files with no
comments, not much review and too many TODO comments), and you have to
be self-sufficient to go into production with it. Because it is free,
you can install it widely at minimal cost. JBoss 4 ships with some
version of Axis built in, though that version just causes trouble to
people who include their own version of Axis. (Disclaimer, my code is
Axis, and wrote the bit of the docs that sneers at the weak)


The JWSDP is a kind of 'not for production' bundle from Sun. They want
to intro Web Services to you, but expect you to pony up the cash for a
real Application server before you go live. So while you can get a dev
system up and running quickly, it is not clear if you can go into
production with it. There are lots of docs, though they all blissfully
ignore interoperability with other platforms, to the extent of
pretending that unsigned data types do not exist, so that the
implementations lack of support for such types doesnt matter. You may be
able to get support from Sun for the pack, though they say on the web
site you should get the Sun App server for a "fully supported,
enterprise class" product. A large amount of the pack is actually Apache
product (Tomcat, Ant, Xerces, Xindice), so not only are you left
resorting to the same support process as Axis, the Apache groups avoid
supporting stuff that Sun reship on the basis that Sun have changed it
in places, and it is thus impossible to deal with. So the first response
to any support call is "download the latest release of our build".There
is no DIME support in JWSDP, I believe (Disclaimer, my Ant code ships
with this)

There are also third party Java SOAP implementations, which are built to
a high standard, come with support, etc etc, from vendors like The Mind
Electric, Cape Clear, and others. If you have a limited run of servers,
expect to need some help getting it working want a secure/robust/high
performance solution, these are products to seriously consider.
Certainly I would look at them before touching the JWSDP :)

-steve

Thanks steve for response, Mindreef was indeed useful in looking
at the soap message. The cool thing is, one doesnt need to develop
a client to test the server. Axis provides a soap monitor but
does not provide tools for analyzing WSDL, creating SOAP requests.

I knew that, the server functionality i developed in java and
deployed using Axis Soap toolkit fine, there was only problem in
choosing the right Soap Mapper in MS Soap Toolkit for client.

  All the while i was using CTM (Custom Type Mapper) that gave me
problems for my case, but when i switched to GCTM (Generic Mapper)
things  worked fine.  Now i am able to send complex type , arrays
from Vb client and process them in Java.

Next step is to use DIME and download some data from the server.

Thanks again,
Venu



--- In soapbuilders@yahoogroups.com, Steve Loughran <steve_l@i...>
wrote:
> soapbuilders@yahoogroups.com wrote:
>
> >    Date: Mon, 06 Oct 2003 17:00:57 -0000
> >    From: "Venu Kanaparthy" <madhavsinghk@y...>
> > Subject: MSSOAP  Toolkit 3.0  & Apache Axis Interoperability
> >
> > Hi folks,
> >
> >  I have a web service developed in Axis, input to the service is
> > customer address and output is list of customers.
> >
> > I have a client in Visual Basic and uses MSSOAP Toolkit 3.0.
> >
> > I get following error when i send a SOAP message.
> >
> > SoapMapper: "Restoring Data into SoapMapper GetParcelsResult
failed
> > HRESULT=0X800A005B  - Client:Unspecified error.
HRESULT=0x800AOO5B
> >
> > Please lookat my wsdl and other documents. Any pointers will be
great
> > help.
> >
> > http://www.erc.msstate.edu/~venu/question/
> >
>
> My recommendation would be pull down a trial copy of mindreef 2.0
from
> mindreef.com, have it act as a proxy between the two systems and
let it
> tell you who is getting anything wrong.
>
> I havent used MSSOAP, dont know if it still being maintained, dont
> recognise 0X800A005B as an obvious error, etc etc. Worry about the
basic
> issues 'is the url right' before worrying about interop details.
>
> If there is an interop problem, check with the axis-users mail
list and
> consider filing it with the Axis bug db. This doesnt mean teams of
> otherwise idle engineers will close their slashdot browsers and
spring
> into action fixing the bug, but someone may recognise the problem.
>
> -steve

Hello,

Have a tough one for you good people :)

Is it possible for a .NET client to consume a w3c.dom.element type?  Now let
me elaborate on that....I'm creating a custom proxy class for an exsiting
Java Axis 1.0 web service which features the ApacheSoap:Element return
types.

Now I can do this currently with the SOAP toolkit and the HTTP40Document
classes...but why? I mean was not .NET supposed to be the greatest platform
for Web Services?  Why am I loosing functionality by using .NET?  I mean I
can use interop with legacy COM and the MS SoapTool Kit 3.0 but again why?

I'm currently bashing my skull againts my keyboard trying to figure out how
to resolve the raw SOAP response and request messages correctly.  I do not
want to have to resort to building my soap envelopes via string love.  It
seems a bit unpalatable even for this x vbscript coder.

If anyone has used Axis 1.0 with ApacheSoap:Elements please e-mail or post I
would truly be greatfull.

Thank you very much....

Eric

_________________________________________________________________
Share your photos without swamping your Inbox.  Get Hotmail Extra Storage
today! http://join.msn.com/?PAGE=features/es

Hi I am a c++ programmer and new to soap.I write my first soap
client code, but it's seem's not work as it should be.Any help will
be very appreciated.
It use the zipcoderesolver service to get fullzipcode, see

http://webservices.eraserver.net/zipcoderesolver/zipcoderesolver.asmx
?WSDL
http://webservices.eraserver.net/zipcoderesolver/zipcoderesolver.asmx

I only try the FullZipCode.

the connection is ok, but I always output of 00000-0000, seems the
soap message I send is incorrect, so I wondered is there anyone can
tell me what wrong with the Serializer code in my program.

here is the code and the soap message I got from mssoapT. BTW, my
mssoapt not work as the MSDN soap FAQ said, I have to temporarily
change the SVCNAME to local:8080 to get the soap message I send.
where should I put the the xml file in local machine?

#define
SVCNAME "http://webservices.eraserver.net/zipcoderesolver/zipcodereso
lver.asmx"
//change to http://localhost:8080/... here when I want to get soap I
send, but it doesn't help to get response the client receives.

void CSoaptestDlg::OnGetzipcode()
{
	 // TODO: Add your control notification handler code here
	 CoInitialize(NULL);

	 ISoapSerializerPtr Serializer;
	 ISoapReaderPtr Reader;
	 ISoapConnectorPtr Connector;

	 try
	 {

	 Connector.CreateInstance(__uuidof(HttpConnector));
	 Connector->Property["EndPointURL"] = SVCNAME;
	 Connector->Connect();
	 Connector->Property["SoapAction"]
= "http://webservices.eraserver.net/FullZipCode";
	 Connector->BeginMessage();

	 // Creating a SoapSerializer object and initializing it
with InputSTream
	 Serializer.CreateInstance(_uuidof(SoapSerializer));
	 Serializer->Init(_variant_t((IUnknown*)Connector-
>InputStream));

	 //Write Message Here
	 Serializer->startEnvelope("soap","","");
	 Serializer->startBody("");
	 Serializer->startElement
("FullZipCode","http://webservices.eraserver.net/","","");
	 Serializer->startElement("accessCode","","","");
	 Serializer->writeString("9999");
	 Serializer->endElement();
	 Serializer->startElement("address","","","");
	 Serializer->writeString("111 N2nd St");
	 Serializer->endElement();
	 Serializer->startElement("city","","","");
	 Serializer->writeString("Harrison");
	 Serializer->endElement();
	 Serializer->startElement("state","","","");
	 Serializer->writeString("NJ");
	 Serializer->endElement();
	 Serializer->endElement();
	 Serializer->endBody();
	 Serializer->endEnvelope();

	 Connector->EndMessage();

	 Reader.CreateInstance(_uuidof(SoapReader));
	 Reader->Load(_variant_t((IUnknown*)Connector-
>OutputStream),"");
	 SetResult((const char *)Reader->RPCResult->text);

	 }

	 catch(...)
	 {
		 SetResult("something wrong");
	 }

	 CoUninitialize();
}

and here is the message I get on mssoapt
   <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
- <soap:Envelope soap:encodingStyle=""
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
- <soap:Body soap:encodingStyle="">
- <SOAPSDK1:FullZipCode
xmlns:SOAPSDK1="http://webservices.eraserver.net/"
soap:encodingStyle="">
   <accessCode soap:encodingStyle="">9999</accessCode>
   <address soap:encodingStyle="">111 N2nd St</address>
   <city soap:encodingStyle="">Harrison</city>
   <state soap:encodingStyle="">NJ</state>
   </SOAPSDK1:FullZipCode>
   </soap:Body>
   </soap:Envelope>

Ok I created a custom client side WSDL using XSD in the <type/>
section.  Previously the apache soap namespace was being imported
into the XSD namespace and it was not working correctly.

I created a custom client proxy class as well.  I created classes for
each of the elements being passed from the Axis Web Service...it
appears to be working...well the WSDL is valid.  I used "MindReef"
and it was able to use it againts the web service and I was getting
data back correctly. Unfortunately the .NET client still barfs on the
same xml message error.

I think this has to do with the server not responding with non RPC
encoded style messages....they are actually not fully QNamed
predicated. They are simpley angle bracket error responses. And where
the Server Side code is injected in the response message is where it
barfs in .NET.  Me thinks they are doing both...declaring messages as
RPC but yet still sending messages in Doc/Literal format.

Bad code smell....

Anyone else had any problems with recieving doc-literal using a .NET
client expecting RPC style?

Thanks :)

Eric

MindReef is killer :)  I'm buying it this week.
My only problem is that I created a custom WSDL document using XSD
types instead of importing a general namespace w3c.dom.element, and
the WSDL works fine ...at least I think it does....

Does anyone know if I reference in the Service and Binding sections
in my local file WSDL doc, will it actually use my local file copy or
will it infer the WSDL from the host web service?  Effectively
overriding my local file copy?

Eric

--- In soapbuilders@yahoogroups.com, "Venu Kanaparthy"
<madhavsinghk@y...> wrote:
> Thanks steve for response, Mindreef was indeed useful in looking
> at the soap message. The cool thing is, one doesnt need to develop
> a client to test the server. Axis provides a soap monitor but
> does not provide tools for analyzing WSDL, creating SOAP requests.
>
> I knew that, the server functionality i developed in java and
> deployed using Axis Soap toolkit fine, there was only problem in
> choosing the right Soap Mapper in MS Soap Toolkit for client.
>
>  All the while i was using CTM (Custom Type Mapper) that gave me
> problems for my case, but when i switched to GCTM (Generic Mapper)
> things  worked fine.  Now i am able to send complex type , arrays
> from Vb client and process them in Java.
>
> Next step is to use DIME and download some data from the server.
>
> Thanks again,
> Venu
>
>
>
> --- In soapbuilders@yahoogroups.com, Steve Loughran <steve_l@i...>
> wrote:
> > soapbuilders@yahoogroups.com wrote:
> >
> > >    Date: Mon, 06 Oct 2003 17:00:57 -0000
> > >    From: "Venu Kanaparthy" <madhavsinghk@y...>
> > > Subject: MSSOAP  Toolkit 3.0  & Apache Axis Interoperability
> > >
> > > Hi folks,
> > >
> > >  I have a web service developed in Axis, input to the service is
> > > customer address and output is list of customers.
> > >
> > > I have a client in Visual Basic and uses MSSOAP Toolkit 3.0.
> > >
> > > I get following error when i send a SOAP message.
> > >
> > > SoapMapper: "Restoring Data into SoapMapper GetParcelsResult
> failed
> > > HRESULT=0X800A005B  - Client:Unspecified error.
> HRESULT=0x800AOO5B
> > >
> > > Please lookat my wsdl and other documents. Any pointers will be
> great
> > > help.
> > >
> > > http://www.erc.msstate.edu/~venu/question/
> > >
> >
> > My recommendation would be pull down a trial copy of mindreef 2.0
> from
> > mindreef.com, have it act as a proxy between the two systems and
> let it
> > tell you who is getting anything wrong.
> >
> > I havent used MSSOAP, dont know if it still being maintained,
dont
> > recognise 0X800A005B as an obvious error, etc etc. Worry about
the
> basic
> > issues 'is the url right' before worrying about interop details.
> >
> > If there is an interop problem, check with the axis-users mail
> list and
> > consider filing it with the Axis bug db. This doesnt mean teams
of
> > otherwise idle engineers will close their slashdot browsers and
> spring
> > into action fixing the bug, but someone may recognise the problem.
> >
> > -steve

http://www.geocities.com/McRitchiexjb7/index.html

I have build webservice in .Net using sessions.
Once loggedIn  sessions get set then other web methods are called
seeing upon session values.
I am able to called them successfully via .Net client using cookie
Container.

Now I tried this in java client.I am only able to call first method
i.e loggedIn.I am not able to call other methods.

Do anyone know how to pass sessions through java.

with thanks,
rohit

+1 for the release plan.

Thanks,
dims

--- Susantha Kumara <susantha@...> wrote:
> Hi all,
>
> We are happy to announce our plan to release Apache Axis C++ implementation.
>
> I have volunteered to be the release manager for Apache Axis C++ initial
release.
>
> Following is the release plan.
>
>
> Introduction:
> ------------
> This is the release plan for Axis/C++ version 1.0. The
> goal of Axis/C++ version 1.0 is to provide a stable platform
> for developing Web services using C++ as well as to use Web
> services in C++ client applications.
>
> Major features of Axis/C++ include:
>     - SOAP engine with both client and server support
>     - Partial support for both SOAP 1.1 and SOAP 1.2
>     - WSDD based deployment with dynamic deployment tools.
>     - Support for all basic types, Complex types and Arrays
>     - WSDL2WS tool for building following C/C++ components
>         Server side - Skeletons and Wrappers
>         Client side - Stubs
>     - WSDL2WS tool that generates wrappers, which perform
>       the following functions. These wrappers act as RPC Providers.
>         Serialization
>         Deserialization
>         Method invocation
>     - WSDLs hosted statistically in the server.
>     - Standalone server (with HTTP support)
>     - Web server modules for Apache HTTPD 1.3 (Linux/Windows)
>     - Web interface to the deployed services and their WSDLs.
>     - Sample web services and client applications.
>     - Supportive documentation for developers and users.
>
>
> Dates:
> -----
> The following dates are proposed:
>     Code freeze                          October 21, 2003
>     Release alpha version            October 23, 2003
>     Release beta version             October 30, 2003
>     Release 1.0                           November 6, 2003
>
> Once release freeze is achieved, inclusion of fixes into the release
> requires consensus of active Axis committers.  Deferring of a fix
> requires simple majority.
>
> Fixes are to continue to be made on the "HEAD" of the release.  Once
> there is consensus that a particular fix is to be included in the
> release, I'll merge it into the branch.  In order to make this as smooth
> and as painless a process as possible for the release manager, I'll ask
> that committers show restraint in committing unrelated fixes to the HEAD
> during this time in areas of the code that might interfere with the
> merge process.
>
>
> Release Criteria:
> ----------------
>     - All Axis/C++ functional tests pass.
>     - All critical bugs are fixed
>     - Basic interop tests pass
>     - Confirmation that the released version works on Apache HTTP
>       1.3* on Win32 and Linux
>
>
> Release Manager:
> ---------------
>     Susantha Kumara, susantha@...
>
>
> Release Announcements:
> ---------------------
>      announcements@...
>      axis-dev@...
>      axis-users@...
>      soap-dev@...
>      soap-users@...
>      soapbuilders@yahoogroups.com
>      xml-dist-app@...
>
>
> Thanks,
>
> Susantha (on behalf of Axis C++ team)
>
>


=====
Davanum Srinivas - http://webservices.apache.org/~dims/

That is good news, but I wonder why SOAP 1.1 and SOAP 1.2 are not fully
supported? Also you don't mention MEPs such as one-way and async. Do
you plan to support polymorphism (e.g. Apache Axis map)? Attachments?

Note that gSOAP (SourceForge and soon: Debian) is already stable and
provides more features. It supports both SOAP 1.1 and SOAP 1.2. It
serializes native C and C++ data types as well (including STL and
polymorphism), so no hassle with conversion and/or mappings. Actually,
gSOAP is more XML-centric than SOAP-centric as it provides more generic
compiler-based XML encoding. No offense, but I am just wondering if
this release announcement is not taking us a step back.

- Prof. Robert van Engelen, Florida State University

On Wednesday, October 15, 2003, at 05:35 AM, Susantha Kumara wrote:

> Hi all,
>  
> We are happy to announce our plan to release Apache Axis C++
> implementation.
>  
> I have volunteered to be the release manager for Apache Axis C++
> initial release.
>  
> Following is the release plan.
>  
>
> Introduction:
> ------------
> This is the release plan for Axis/C++ version 1.0. The
> goal of Axis/C++ version 1.0 is to provide a stable platform
> for developing Web services using C++ as well as to use Web
> services in C++ client applications.
>  
> Major features of Axis/C++ include: 
>     - SOAP engine with both client and server support
>     - Partial support for both SOAP 1.1 and SOAP 1.2
>     - WSDD based deployment with dynamic deployment tools.
>     - Support for all basic types, Complex types and Arrays
>     - WSDL2WS tool for building following C/C++ components
>         Server side - Skeletons and Wrappers
>         Client side - Stubs
>     - WSDL2WS tool that generates wrappers, which perform
>       the following functions. These wrappers act as RPC Providers.
>         Serialization
>         Deserialization
>         Method invocation
>     - WSDLs hosted statistically in the server.
>     - Standalone server (with HTTP support)
>     - Web server modules for Apache HTTPD 1.3 (Linux/Windows)
>     - Web interface to the deployed services and their WSDLs.
>     - Sample web services and client applications.
>     - Supportive documentation for developers and users.
>
>
> Dates:
> -----
> The following dates are proposed:
>     Code freeze                          October 21, 2003
>     Release alpha version            October 23, 2003
>     Release beta version             October 30, 2003
>     Release 1.0                           November 6, 2003
>
> Once release freeze is achieved, inclusion of fixes into the release
> requires consensus of active Axis committers.  Deferring of a fix
> requires simple majority.
>
> Fixes are to continue to be made on the "HEAD" of the release.  Once
> there is consensus that a particular fix is to be included in the
> release, I'll merge it into the branch.  In order to make this as
> smooth
> and as painless a process as possible for the release manager, I'll ask
> that committers show restraint in committing unrelated fixes to the
> HEAD
> during this time in areas of the code that might interfere with the
> merge process.
>
>
> Release Criteria:
> ----------------
>     - All Axis/C++ functional tests pass.
>     - All critical bugs are fixed
>     - Basic interop tests pass
>     - Confirmation that the released version works on Apache HTTP
>       1.3* on Win32 and Linux
>
>
> Release Manager:
> ---------------
>     Susantha Kumara, susantha@...
>
>
> Release Announcements:
> ---------------------
>      announcements@...
>      axis-dev@...
>      axis-users@...
>      soap-dev@...
>      soap-users@...
>      soapbuilders@yahoogroups.com
>      xml-dist-app@...
>   
>  
> Thanks,
>  
> Susantha (on behalf of Axis C++ team)
>  

Please move any follow-up on this topic to axis-dev@...;
it was posted to the other lists inadvertantly.

Sanjiva.

----- Original Message -----
From: "Robert van Engelen" <engelen@...>
To: "Susantha Kumara" <susantha@...>
Cc: <announcements@...>; <axis-dev@...>;
<axis-users@...>; <soap-dev@...>;
<soap-users@...>; <soapbuilders@yahoogroups.com>;
<xml-dist-app@...>
Sent: Wednesday, October 15, 2003 11:34 PM
Subject: Re: Release plan of Apache Axis C++ version 1.0


>
> That is good news, but I wonder why SOAP 1.1 and SOAP 1.2 are not fully
> supported? Also you don't mention MEPs such as one-way and async. Do
> you plan to support polymorphism (e.g. Apache Axis map)? Attachments?
>
> Note that gSOAP (SourceForge and soon: Debian) is already stable and
> provides more features. It supports both SOAP 1.1 and SOAP 1.2. It
> serializes native C and C++ data types as well (including STL and
> polymorphism), so no hassle with conversion and/or mappings. Actually,
> gSOAP is more XML-centric than SOAP-centric as it provides more generic
> compiler-based XML encoding. No offense, but I am just wondering if
> this release announcement is not taking us a step back.
>
> - Prof. Robert van Engelen, Florida State University
>
> On Wednesday, October 15, 2003, at 05:35 AM, Susantha Kumara wrote:
>
> > Hi all,
> >
> > We are happy to announce our plan to release Apache Axis C++
> > implementation.
> >
> > I have volunteered to be the release manager for Apache Axis C++
> > initial release.
> >
> > Following is the release plan.
> >
> >
> > Introduction:
> > ------------
> > This is the release plan for Axis/C++ version 1.0. The
> > goal of Axis/C++ version 1.0 is to provide a stable platform
> > for developing Web services using C++ as well as to use Web
> > services in C++ client applications.
> >
> > Major features of Axis/C++ include:
> > - SOAP engine with both client and server support
> > - Partial support for both SOAP 1.1 and SOAP 1.2
> > - WSDD based deployment with dynamic deployment tools.
> > - Support for all basic types, Complex types and Arrays
> > - WSDL2WS tool for building following C/C++ components
> > Server side - Skeletons and Wrappers
> > Client side - Stubs
> > - WSDL2WS tool that generates wrappers, which perform
> > the following functions. These wrappers act as RPC Providers.
> > Serialization
> > Deserialization
> > Method invocation
> > - WSDLs hosted statistically in the server.
> > - Standalone server (with HTTP support)
> > - Web server modules for Apache HTTPD 1.3 (Linux/Windows)
> > - Web interface to the deployed services and their WSDLs.
> > - Sample web services and client applications.
> > - Supportive documentation for developers and users.
> >
> >
> > Dates:
> > -----
> > The following dates are proposed:
> > Code freeze October 21, 2003
> > Release alpha version October 23, 2003
> > Release beta version October 30, 2003
> > Release 1.0 November 6, 2003
> >
> > Once release freeze is achieved, inclusion of fixes into the release
> > requires consensus of active Axis committers. Deferring of a fix
> > requires simple majority.
> >
> > Fixes are to continue to be made on the "HEAD" of the release. Once
> > there is consensus that a particular fix is to be included in the
> > release, I'll merge it into the branch. In order to make this as
> > smooth
> > and as painless a process as possible for the release manager, I'll ask
> > that committers show restraint in committing unrelated fixes to the
> > HEAD
> > during this time in areas of the code that might interfere with the
> > merge process.
> >
> >
> > Release Criteria:
> > ----------------
> > - All Axis/C++ functional tests pass.
> > - All critical bugs are fixed
> > - Basic interop tests pass
> > - Confirmation that the released version works on Apache HTTP
> > 1.3* on Win32 and Linux
> >
> >
> > Release Manager:
> > ---------------
> > Susantha Kumara, susantha@...
> >
> >
> > Release Announcements:
> > ---------------------
> > announcements@...
> > axis-dev@...
> > axis-users@...
> > soap-dev@...
> > soap-users@...
> > soapbuilders@yahoogroups.com
> > xml-dist-app@...
> >
> >
> > Thanks,
> >
> > Susantha (on behalf of Axis C++ team)
> >

Hi to all!

I'm using glue for SOAP messaging and I would like to know if I can
and how I can to gain access over the connection stream that are
sending the data back and forward. I need this to see the progress of
the incoming data from the server, in the case that there is much
data to exchange with the client. Thanks!

Daniel

I am getting an error w/ some encoding issue.  I have two classes,
Entry and Directory.  Directory is the server class.  In the client
class I call a method in the Directory class, that returns an object
of type Entry.  This is where the problem is.  It says that it is
unable to encode it.

Here is the error I am getting:


Exception in thread "main" [SOAPException: faultCode=SOAP-ENV:Client;
msg=No Deserializer found to deserialize a
'urn:directoryserver:entry' using encoding style
'http://schemas.xmlsoap.org/soap/encoding/'.;
targetException=java.lang.IllegalArgumentException: No Deserializer
found to deserialize a 'urn:directoryserver:entry' using encoding
style 'http://schemas.xmlsoap.org/soap/encoding/'.]
         at org.apache.soap.rpc.Call.invoke(Call.java:294)
         at Directory.Client.main(Client.java:146)




I am sure the error is w/ my DeploymentDescriptor.xml file:

<isd:service xmlns:isd="http://xml.apache.org/xml-soap/deployment"
     id="urn:directoryserver">
         <isd:provider type="java"
             scope="Application"
             methods="add addEntry size entryAt search">
             <isd:java class="Directory.Directory"/>
         </isd:provider>

<isd:faultListener>org.apache.soap.server.DOMFaultListener</isd:faultL
istener>
     <isd:mappings>
     <isd:map encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
              xmlns:x="urn:directoryserver"
              qname="x:entry"
              javaType="Directory.Entry"

java2XMLClassName="org.apache.soap.encoding.soapenc.BeanSerializer"

xml2JavaClassName="org.apache.soap.encoding.soapenc.BeanSerializer"/>
   </isd:mappings>

</isd:service>




Here is the part of code in the Client file where i get an error:

Integer place = new Integer(0);
						 System.out.println
("This is place : " + place);


							 call = new
Call();

	 call.setTargetObjectURI("urn:directoryserver");

	 call.setMethodName("entryAt");

	 call.setEncodingStyleURI(Constants.NS_URI_SOAP_ENC);

							 params = new
Vector();


	 params.addElement(new Parameter("place", Integer.class,
place, null));
							 call.setParams
(params);

							 resp =
call.invoke(url, "" );

							 if (
resp.generatedFault() ) {
								 Fault
fault = resp.getFault ();

	 System.out.println("The call failed: ");

	 System.out.println("Fault Code   = " + fault.getFaultCode());

	 System.out.println("Fault String = " + fault.getFaultString
());
   							 }
    						 else {

	 Parameter result = resp.getReturnValue();

	 //System.out.println(result.getValue());

	 Object value = result.getValue();
								 Entry
ent = (Entry)value;

	 System.out.println(ent.getfname());
							 }

Hi,

Any body willing to share lessons on IBM's SOAP FOR CICS?
If you have any, let's hear them.
This new feature promises lots of possibilities for this great
Transaction Processing Environment (CICS Transaction Server).

Currently, we are testing S4C in our CICS TS 1.3 Test Region under
OS/390 2.10 and LE.
I'm trying to work out the inbound soap service provider shipped with
the feature.

We have CWS working, and now I plan to make sure BTS is ready to
support SOAP inbound requests.

Check out http://www.ibm.com/cics/soap

Regards,
Alex Meseguer

I thought this had all died down, but at the recent ICANN meeting on the
topic, there was a little presentation by VeriSign that covered feedback
from their little field experiment [1]. Page 25 is the core one for web
services, though pages 21-23 are mildly entertaining, particularly all
the places where the recommended workarounds are 'application patches'
and 'user education'. It'll be our apps and our users, I suspect.

Slide #26 says :-
   Automated HTTP Tools

   Issue: Automated processes using HTTP over TCP port 80 may
   exhibit problems when encountering the Site Finder page
   instead of a DNS Name Error response

   Response: No reported occurrences
     o The site includes a robots.txt file to prevent indexing
     o Other types of automated tools are discouraged according
       to BCP 56

---------

Which means that (a) nobody complains and (b) you shouldn't be using
anything other than web browsers to talk HTTP on port 80.

Sigh.

Accordingly I have just written up the experiments I conducted while
sitefinder was live testing both Axis and .NET WSE 2.0 clients: both
failed with error messages that were definitely not consumer friendly.

The full paper is at [2]; I will send it to Matt Larson next week so
that he can't make the 'none reported' claim any more.

Comments welcome,

-Steve

[1] Review of Technical Issues and VeriSign  Response
http://www.icann.org/presentations/turner-secsac-dc-15oct03.ppt
[2] The Impact of Site Finder on Web Services

Alex,

Please confirm that you have S4C working with CICS TS v1.3?
The IBM documentation says that it requires CICS TS v2.2.

Is there anything special that you had to do to make it run with v1.3?

Thanks,
Anne

At 04:45 AM 10/18/2003, you wrote:
>    Date: Fri, 17 Oct 2003 13:35:51 -0000
>    From: "meseguer78" <alejandro_meseguer@...>
>Subject: S4C LISTENERS
>
>Hi,
>
>Any body willing to share lessons on IBM's SOAP FOR CICS?
>If you have any, let's hear them.
>This new feature promises lots of possibilities for this great
>Transaction Processing Environment (CICS Transaction Server).
>
>Currently, we are testing S4C in our CICS TS 1.3 Test Region under
>OS/390 2.10 and LE.
>I'm trying to work out the inbound soap service provider shipped with
>the feature.
>
>We have CWS working, and now I plan to make sure BTS is ready to
>support SOAP inbound requests.
>
>Check out http://www.ibm.com/cics/soap
>
>Regards,
>Alex Meseguer

Hi,
As gSoap does more than what is proposed here - that should be the standard
metric.
    First I would make sure if the axis c++ client can talk to gsoap server
at it's current level
   of implementation - stl usage, DIME(streaming), and perhaps ws_security -
by the time
   the stable 1.0 of your release is ready.


>From: Robert van Engelen <engelen@...>
>Reply-To: soapbuilders@yahoogroups.com
>To: "Susantha Kumara" <susantha@...>
>CC: <announcements@...>, <axis-dev@...>,
><axis-users@...>, <soap-dev@...>,
><soap-users@...>, <soapbuilders@yahoogroups.com>,
><xml-dist-app@...>
>Subject: [soapbuilders] Re: Release plan of Apache Axis C++ version 1.0
>Date: Wed, 15 Oct 2003 13:34:22 -0400
>
>
>That is good news, but I wonder why SOAP 1.1 and SOAP 1.2 are not fully
>supported? Also you don't mention MEPs such as one-way and async. Do
>you plan to support polymorphism (e.g. Apache Axis map)? Attachments?
>
>Note that gSOAP (SourceForge and soon: Debian) is already stable and
>provides more features. It supports both SOAP 1.1 and SOAP 1.2. It
>serializes native C and C++ data types as well (including STL and
>polymorphism), so no hassle with conversion and/or mappings. Actually,
>gSOAP is more XML-centric than SOAP-centric as it provides more generic
>compiler-based XML encoding. No offense, but I am just wondering if
>this release announcement is not taking us a step back.
>
>- Prof. Robert van Engelen, Florida State University
>
>On Wednesday, October 15, 2003, at 05:35 AM, Susantha Kumara wrote:
>
> > Hi all,
> >  
> > We are happy to announce our plan to release Apache Axis C++
> > implementation.
> >  
> > I have volunteered to be the release manager for Apache Axis C++
> > initial release.
> >  
> > Following is the release plan.
> >  
> >
> > Introduction:
> > ------------
> > This is the release plan for Axis/C++ version 1.0. The
> > goal of Axis/C++ version 1.0 is to provide a stable platform
> > for developing Web services using C++ as well as to use Web
> > services in C++ client applications.
> >  
> > Major features of Axis/C++ include: 
> >     - SOAP engine with both client and server support
> >     - Partial support for both SOAP 1.1 and SOAP 1.2
> >     - WSDD based deployment with dynamic deployment tools.
> >     - Support for all basic types, Complex types and Arrays
> >     - WSDL2WS tool for building following C/C++ components
> >         Server side - Skeletons and Wrappers
> >         Client side - Stubs
> >     - WSDL2WS tool that generates wrappers, which perform
> >       the following functions. These wrappers act as RPC Providers.
> >         Serialization
> >         Deserialization
> >         Method invocation
> >     - WSDLs hosted statistically in the server.
> >     - Standalone server (with HTTP support)
> >     - Web server modules for Apache HTTPD 1.3 (Linux/Windows)
> >     - Web interface to the deployed services and their WSDLs.
> >     - Sample web services and client applications.
> >     - Supportive documentation for developers and users.
> >
> >
> > Dates:
> > -----
> > The following dates are proposed:
> >     Code freeze                          October 21, 2003
> >     Release alpha version            October 23, 2003
> >     Release beta version             October 30, 2003
> >     Release 1.0                           November 6, 2003
> >
> > Once release freeze is achieved, inclusion of fixes into the release
> > requires consensus of active Axis committers.  Deferring of a fix
> > requires simple majority.
> >
> > Fixes are to continue to be made on the "HEAD" of the release.  Once
> > there is consensus that a particular fix is to be included in the
> > release, I'll merge it into the branch.  In order to make this as
> > smooth
> > and as painless a process as possible for the release manager, I'll ask
> > that committers show restraint in committing unrelated fixes to the
> > HEAD
> > during this time in areas of the code that might interfere with the
> > merge process.
> >
> >
> > Release Criteria:
> > ----------------
> >     - All Axis/C++ functional tests pass.
> >     - All critical bugs are fixed
> >     - Basic interop tests pass
> >     - Confirmation that the released version works on Apache HTTP
> >       1.3* on Win32 and Linux
> >
> >
> > Release Manager:
> > ---------------
> >     Susantha Kumara, susantha@...
> >
> >
> > Release Announcements:
> > ---------------------
> >      announcements@...
> >      axis-dev@...
> >      axis-users@...
> >      soap-dev@...
> >      soap-users@...
> >      soapbuilders@yahoogroups.com
> >      xml-dist-app@...
> >   
> >  
> > Thanks,
> >  
> > Susantha (on behalf of Axis C++ team)
> >  
>

_________________________________________________________________
Enjoy MSN 8 patented spam control and more with MSN 8 Dial-up Internet
Service.  Try it FREE for one month!   http://join.msn.com/?page=dept/dialup

I just started trying out SOAP in JWSD and tried creating a sample
program based on the samples given... and i get this error when i run
the sample program. Can anyone help ? Thanks in advance

[java] java.rmi.RemoteException: Runtime exception; nested exception
is:
[java]     deserialization error: unexpected XML reader state.
expected: END but found: START: ClientName