Re: Axis C++ WebService Messages calls with Complex Types and Arrays throws Exception: m_iExceptionCode=72 m_sMessage=0x00a50580 "Cannot deserialize the requested element"
Hi,
It would aid diagnosing your deserialization problem if you could capture
the SOAP request/response messages.
Regards,
Adrian
___
Adrian Dick ([EMAIL PROTECTED])
G Sabarinath <[EMAIL PROTECTED]> wrote on 16/11/2006 14:38:26:
> Hi,
> I am able to develop , run, and use WebServices in Axis C++ having simple
> Types (int, string etc) as message arguments .
> Howerver when I use complex Types with Arrays as message arguments it I
> am getting the following Exception.
> requested element ">
>
> Details of the WSDL and code are given below:
>
> CompleType schema in my WSDL:( start)
>
> http://localhost:/axis/BinOptNewService";
> xmlns="http://www.w3.org/2001/XMLSchema";>
>
>
>
>
>
> maxOccurs="unbounded">
>
>
>
>
>type="string" minOccurs="1" maxOccurs="1">
>
>type="double" minOccurs="1" maxOccurs="1">
>
>
>
>
> CompleType schema in my WSDL: (end.)
>
> WASDL Extracts associated with message "addBinTemplate":
>
-
> --
> ---
>
>
>
> --
>
>
>
> transport="http://schemas.xmlsoap.org/soap/http"/>
>
>
>
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> namespace="http://localhost:/axis/BinOptNewService";
> use="encoded"/>
>
>
> http://schemas.xmlsoap.org/soap/encoding/";
> namespace="http://localhost:/axis/BinOptNewService";
> use="encoded"/>
>
>
>
>
> WSDL2Ws generated classes:
> --
>
> class BinInfoType
> {
> public:
> xsd__string BinName;
> xsd__string BinID;
> ParamType_Array * Param;
>
> xsd__string getBinName();
> void setBinName(xsd__string InValue);
>
> xsd__string getBinID();
> void setBinID(xsd__string InValue);
>
> ParamType_Array * getParam();
> void setParam(ParamType_Array * pInValue);
>
> BinInfoType();
> void reset();
> virtual ~BinInfoType();
> };
>
> class ParamType
> {
> public:
> xsd__string ParamName;
> xsd__double ParamValue;
>
> xsd__string getParamName();
> void setParamName(xsd__string InValue);
>
> xsd__double getParamValue();
> void setParamValue(xsd__double InValue);
>
> ParamType();
> void reset();
> virtual ~ParamType();
> };
>
> class STORAGE_CLASS_INFO ParamType_Array : public Axis_Array
> {
> public:
> ParamType_Array();
> ParamType_Array(const ParamType_Array & original);
> virtual ~ParamType_Array();
> void set( class ParamType** array, const int size);
> class ParamType** get(int & size) const;
> void clone(const ParamType_Array & original);
> virtual Axis_Array * clone() const;
> void clear();
> };
>
>
> Client code:
> -
>
> BinOptNewService bop;
> BinInfoType *bot = new BinInfoType();
> ParamType **pm = new ParamType*[2];
> ParamType_Array *pmA = new ParamType_Array();
>
> pm[0] = new ParamType();
> pm[1] = new ParamType();
> pm[0]->setParamName("P1");
> pm[0]->setParamValue(100.0);
> pm[1]->setParamName("P2");
> pm[1]->setParamValue(200.0);
>
> pmA->set(pm, 2);
> bot->setParam(pmA);
> bot->setBinID("111");
> bot->setBinName("MyBin");
> int Result1 = bop.addBinTemplate("Bin", bot); // This call thows
> m_iExceptionCode=72 m_sMessage=0x00a50580 "Cannot deserialize the
requested
> element "
>
> Other messages in the Same WebService having simple type arguments work
> fine!!
>
> Thnaks & Regards
> G Sabarinath
>IBM Global Services India Ltd.
>Bangalore.
>Contact : 91-98450-74838 (Cell)
>
>
> -
> 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]
Re: Simple axis server
Hi, The simple_axis_server supports only a single concurrent connection. Please remember this was originally designed to aid testing, so kept very simple. If you require the ability for multiple concurrent connections I would suggest you use Axis with the Apache modules. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) news <[EMAIL PROTECTED]> wrote on 07/11/2006 11:19:29: > Hi listers, > > Can somebody tell me how many connection the simple server can handle. > Can I adjust this and in where. > > I am now using axis 1.5... > > thanks in advance > > Roel Bindels > > > - > 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]
Re: Memory Leak with version1.6b
Hi,
Have you followed the advice given here:
http://ws.apache.org/axis/cpp/arch/mem-management.html
Regards,
Adrian
___
Adrian Dick ([EMAIL PROTECTED])
"Markus Heinisch" <[EMAIL PROTECTED]> wrote on 11/10/2006
10:15:48:
> Hello,
>
> I'm new to AXIS_CPP. I have managed to deploy my own sample Web
> service with the simple axis server on Win XP (using Visual Studio 2005).
>
> While testing my Web service with SoapUi, I discovered a memory leak!
> My Web service is very simple and based on the class:
> class EosServiceWS
> {
> public:
> EosServiceWS();
> public:
> virtual ~EosServiceWS();
> public:
> void onFault();
> xsd__string search(xsd__int Value0);
> xsd__string suche(xsd__string Value0);
> void test(); // <---
> My test case
> };
> The class was generated from the WSDL file (like all server side files).
> I only tested the method test(), which has an empty body, but I see
> a constant increasing memory consumption which does not shrink.
> Is it a known problem? on Windows? How about Linux?
>
> Any hints to find a workaround are welcome.
>
> Cheers Markus
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can Axis C++ services be deployed using IIS server instead of apache?
Hi, "Out of the box", you cannot deploy Axis C++ services to IIS. However, it should be possible to write an IIS module, similar to those for Apache included with Axis C++. Regards, Adrian _______ Adrian Dick ([EMAIL PROTECTED]) "Vijaya Bhaskar Peddinti" <[EMAIL PROTECTED]> wrote on 05/10/2006 06:24:20: > > Just wanted to know whethere Axis C++ services be deployed using IIS > server? > > CAUTION - Disclaimer * > This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION > intended solely for the use of the addressee(s). If you are not the > intended recipient, please notify the sender by e-mail and delete > the original message. Further, you are not to copy, disclose, or > distribute this e-mail or its contents to any other person and any > such actions are unlawful. This e-mail may contain viruses. Infosys > has taken every reasonable precaution to minimize this risk, but is > not liable for any damage you may sustain as a result of any virus > in this e-mail. You should carry out your own virus checks before > opening the e-mail or attachment. Infosys reserves the right to > monitor and review the content of all messages sent to or from this > e-mail address. Messages sent to or from this e-mail address may be > stored on the Infosys e-mail system. > ***INFOSYS End of Disclaimer INFOSYS*** > > - > 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]
Re: Axis C++ SOAP 1.2 faults
Hi,
There is a Jira issue to provide support for SOAP 1.2 faults (
http://issues.apache.org/jira/browse/AXISCPP-642 ), and I made this
proposal on how this could be implemented (
http://marc.theaimsgroup.com/?l=axis-c-dev&m=111640463326474&w=2 )
Regretably, I personally haven't had any time to implement this function,
and it doesn't look like I'm going to anytime soon.
Of course, this is an open source project so anybody can take this issue
and proposal and donate a suitable implementation back to the community.
Regards,
Adrian
_______
Adrian Dick ([EMAIL PROTECTED])
Nadir Amra <[EMAIL PROTECTED]> wrote on 18/09/2006 14:48:02:
> I believe it is a known issue
>
> Nadir K. Amra
>
>
> Kamlesh kumar <[EMAIL PROTECTED]> wrote on 09/15/2006 06:56:59 PM:
>
> > I am interested in creating SOAP faults based on SOAP
> > 1.2 spec using Axis C++. Looking at SOAPFault API it
> > seems we can only create SOAP fault that is compliant
> > with SOAP 1.1 spec.
> >
> > Also, I see the following comment in the SOAPFault
> > serialize() function?
> >
> > int SoapFault::serialize(SoapSerializer& pSZ,
> > SOAP_VERSION eSoapVersion)
> > {
> > // written according to SOAP Version 1.1
> >
> >
> > Is there a way I can create SOAP 1.2 faults or is this
> > a known issue ? Also, are there any plans to address
> > it?
> >
> > Thanks,
> > Kamlesh
> >
> >
> >
> >
> >
> > __
> > Do You Yahoo!?
> > Tired of spam? Yahoo! Mail has the best spam protection around
> > http://mail.yahoo.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]
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Handlers, client.wsdd, change soap body on request/response path
Hi, I'd recommend you read the Handler Tutorial here : http://ws.apache.org/axis/cpp/arch/handler.html Personally, I would advise only to modify the soap headers and not the soap body within handlers in Axis C++. The APIs you can use are made available through the IMessageData object ( [axis install]/include/axis/IMessageData.hpp ). Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Krankurs Leonid <[EMAIL PROTECTED]> wrote on 11/09/2006 14:02:53: > > Could anybody please clarify if the following can be done by Axis C++ 1.6 > client side > (all methods that needed have been implemented already in Axis C++ 1.6 > build) > > 1. Handler can change the soap body of the message on request/response path > 2. if (1) yes, how the handler(s) needs to be configured in client.wsdd? > 2.0. from what base class should the handler be derived > 2.1. what type(level) of the handler should it be (service, global, > transport) This depends on the behaviour you're expecting. service - this handler is used when invoking a given service - you can specify the same handler for more than one service global - this handler is used when invoking any service transport - Due to only supporting HTTP(S) this is equivalent to global for Axis C++. > 2.2. should the handler be explicitly configured to be in a chain? > > 2.3. What methods should be used on request path to get the current body, > change the body, set the new body > 2.4. What methods should be used on response path to get the current body, > change the body, set the new body > > Could you please give any samples or link(s) to samples? See the Handler Tutorial here : http://ws.apache.org/axis/cpp/arch/handler.html You will need to use the APIs made available through IMessageData ( [axis install]/include/axis/IMessageData.hpp ) > > > Thank you, > > -- > View this message in context: http://www.nabble.com/Handlers%2C- > client.wsdd%2C-change-soap-body-on-request-response-path-tf2252258. > html#a6246232 > Sent from the Axis - C++ - User forum at Nabble.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]
Re: Problem in checkout Axis C++ from SVN
Hi, I'm not an SVN expert, but the Apache infrastructure guys have written a page here (http://www.apache.org/dev/version-control.html) which you may find of use, in particular the Anonymous Subversion section. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) "Popuri, Monica" <[EMAIL PROTECTED]> wrote on 08/09/2006 10:32:06: > Hi All, > > I am not able to get the source code from SVN using following link. > It gives connection refused with server svn.apache.org error. Please help. > > svn co http://svn.apache.org/repos/asf/webservices/axis/trunk/c/ axisc > > Thanks, > Monica > > > - > 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]
RE: axis c++ 1.4
Hi, This sounds like the server.wsdd file has been edited on Windows, this results in rogue ^M characters at the ends of lines due to differences in how carriage returns are handled. You will need to manually correct the file, or you may have the dos2unix command which will fix this kind of problem. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) "Popuri, Monica" <[EMAIL PROTECTED]> wrote on 07/09/2006 11:54:39: > Not sure, i have tried to debug the problem till code level. > The output of simple_axis_server command is : Warning - The > WSDDFilePath file (/home/server.wsdd^M) in the AXISCPP.CONF file > does not exist. > where the name of file has a ^M character appended to it, that may > be the reason that my file is not visible to simple_Axis_server. > If I check the src file common/AxisConfig.cpp file. this reads the > file but adds another character like > FILE *fp = fopen (pcValue + 1, "r"); > Can this be the reason that a ^M is getting added. > > Thanks if some body reads this and helps me. > > Regards, > Monica - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: axis c++ 1.4
Hi, Is this the entirety of your trace log ? Are you also using startup trace? Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) "Popuri, Monica" <[EMAIL PROTECTED]> wrote on 06/09/2006 11:47:05: > > Thanks Adrian, > > > Samisa: > Atleast I can see the logs but I am not able to get the reason of > problem yet: here is some part of log (from end) > [06/09/2006 12:33:29:601 CEST] 3076378752 SharedObject > > SharedObject @0x956caf0 > [06/09/2006 12:33:29:601 CEST] 3076378752 SharedObject < > SharedObject @0x956caf0 > [06/09/2006 12:33:29:601 CEST] 3076378752 SharedObject < > SharedObject @0x956caf0 > [06/09/2006 12:33:29:601 CEST] 3076378752 SerializerPool > > SerializerPool @0x956caf0 > [06/09/2006 12:33:29:601 CEST] 3076378752 SerializerPool > > SerializerPool @0x956caf0 > [06/09/2006 12:33:29:601 CEST] 3076378752 SerializerPool < > SerializerPool @0x956caf0 > [06/09/2006 12:33:29:601 CEST] 3076378752 SerializerPool < > SerializerPool @0x956caf0 > [06/09/2006 12:33:29:601 CEST] 3076378752 SharedObject > > SharedObject @0x956cb28 > [06/09/2006 12:33:29:601 CEST] 3076378752 SharedObject > > SharedObject @0x956cb28 > [06/09/2006 12:33:29:601 CEST] 3076378752 SharedObject < > SharedObject @0x956cb28 > [06/09/2006 12:33:29:601 CEST] 3076378752 SharedObject < > SharedObject @0x956cb28 > [06/09/2006 12:33:29:601 CEST] 3076378752 HandlerPool > HandlerPool @0x956cb28 > [06/09/2006 12:33:29:601 CEST] 3076378752 HandlerPool > HandlerPool @0x956cb28 > [06/09/2006 12:33:29:601 CEST] 3076378752 HandlerPool < HandlerPool @0x956cb28 > [06/09/2006 12:33:29:601 CEST] 3076378752 HandlerPool < HandlerPool @0x956cb28 > [06/09/2006 12:33:29:601 CEST] 3076378752 WSDDDeployment > > WSDDDeployment @0x956cb60 > [06/09/2006 12:33:29:601 CEST] 3076378752 WSDDDeployment > > WSDDDeployment @0x956cb60 > [06/09/2006 12:33:29:601 CEST] 3076378752 WSDDDeployment < > WSDDDeployment @0x956cb60 > [06/09/2006 12:33:29:601 CEST] 3076378752 WSDDDeployment < > WSDDDeployment @0x956cb60 > [06/09/2006 12:33:29:601 CEST] 3076378752 AxisConfig > AxisConfig > @0x956cb98,0x956b0f8 > [FFF8FFB05609FFC8FF86FFBF00FFF32400FFEC140508FFFCFF8D6D00] > <..V...$...m.> > [06/09/2006 12:33:29:602 CEST] 3076378752 AxisConfig > AxisConfig > @0x956cb98,0x956b0f8 > [FFF8FFB05609FFC8FF86FFBF00FFF32400FFEC140508FFFCFF8D6D00] > <..V...$...m.> > [06/09/2006 12:33:29:602 CEST] 3076378752 AxisConfig > > getAxisConfProperty @0x956b0f8,[] <> > [06/09/2006 12:33:29:602 CEST] 3076378752 AxisConfig > > getAxisConfProperty @0x956b0f8,[] <> > [06/09/2006 12:33:29:602 CEST] 3076378752 AxisConfig < > getAxisConfProperty @0x956b0f8,@1 > [06/09/2006 12:33:29:602 CEST] 3076378752 AxisConfig < > getAxisConfProperty @0x956b0f8,@1 "ZY<87>^D$Ã'^H" > [06/09/2006 12:33:29:602 CEST] 3076378752 AxisConfig > > getAxisConfProperty @0x956b0f8,[0100] <> > [06/09/2006 12:33:29:602 CEST] 3076378752 AxisConfig > > getAxisConfProperty @0x956b0f8,[0100] <> > [06/09/2006 12:33:29:602 CEST] 3076378752 AxisConfig < > getAxisConfProperty @0x956b0f8,@2 "/usr/local/axiscpp_deploy/log/AxisLog" > [06/09/2006 12:33:29:602 CEST] 3076378752 AxisConfig < > getAxisConfProperty @0x956b0f8,@3 "ZY<87>^D$Ã'^H" > [06/09/2006 12:33:29:602 CEST] 3076378752 AxisConfig > > getAxisConfProperty @0x956b0f8,[0200] <> > [06/09/2006 12:33:29:602 CEST] 3076378752 AxisConfig > > getAxisConfProperty @0x956b0f8,[0200] <> > [06/09/2006 12:33:29:602 CEST] 3076378752 AxisConfig < > getAxisConfProperty @0x956b0f8,@1 > > > Please assist, > > Thanks, > Monica > > > > > > -Original Message- > From: Adrian Dick [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 06, 2006 3:55 PM > To: Apache AXIS C User List > Subject: RE: axis c++ 1.4 > > > Hi, > > If you build with trace, you can enable trace to aid determining the > problem. Instructions for using trace can be found here: > http://ws.apache.org/axis/cpp/TraceGuide.html > > Regards, > Adrian > ___ > Adrian Dick ([EMAIL PROTECTED]) > > "Popuri, Monica" <[EMAIL PROTECTED]> wrote on 06/09/2006 10:41:53: > > > Thanks Samisa, > > > > I have downloaded , built and installed axis c++ from said link (not > > from SVN), actually
RE: axis c++ 1.4
Hi, If you build with trace, you can enable trace to aid determining the problem. Instructions for using trace can be found here: http://ws.apache.org/axis/cpp/TraceGuide.html Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) "Popuri, Monica" <[EMAIL PROTECTED]> wrote on 06/09/2006 10:41:53: > Thanks Samisa, > > I have downloaded , built and installed axis c++ from said link (not > from SVN), actually things are fine on one of my server and not on > other server. the simple_axis_server still aborts on this second > server. If I build the source using buildWithTraceAndDebug option, > will I be able to see the error? > > Thanks again and regards, > Monica > > -Original Message- > From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 05, 2006 5:10 PM > To: Apache AXIS C User List > Subject: Re: axis c++ 1.4 > > > Linux source is here: > http://www.apache.org/dist/ws/axis-c/axis-c-src-Linux-current-src.tar.gz > Windows source is here: > http://www.apache.org/dist/ws/axis-c/axis-c-src-Linux-current-src.tar.gz > > The above are 1.6 beta release packages. > If you would like to checkout the source form svn, you can run the > following command: > > svn co http://svn.apache.org/repos/asf/webservices/axis/trunk/c/ axisc > > Thanks, > Samisa... > > Popuri, Monica wrote: > > hi Samisa, > > > > Thanks for the link, But I am not able to get exactly which is the > link to download the source from SVN. Because when I select the link > given it shows me the whole directory structure. Please help. > > > > Thanks & Regards, > > Monica > > -Original Message- > > From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED] > > Sent: Monday, September 04, 2006 8:17 PM > > To: Apache AXIS C User List > > Subject: Re: axis c++ 1.4 > > > > > > Yes, have a look at the ant build guide > > http://ws.apache.org/axis/cpp/antbuild-guide.html > > > > Samisa... > > > > Popuri, Monica wrote: > > > >> Thanks Samisa for your prompt reply, If I download source. Is > there a good documentation on how to install using source. Because I > remember there needs to be a lot of steps to make the source. > >> Regards, > >> Monica > >> > >> -Original Message- > >> From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED] > >> Sent: Monday, September 04, 2006 3:33 PM > >> To: Apache AXIS C User List > >> Subject: Re: axis c++ 1.4 > >> > >> > >> Are you using the binary version? If that is the case, you may try > >> downloading the source and try with debug options to gdb. > >> The given gdb trace does not reveal any source location hints :( > >> > >> Samisa... > >> > >> Popuri, Monica wrote: > >> > >> > >>> Hi Samisa, > >>> > >>> I am facing problem in starting simple_axis_server in axis c++ > 1.6 . For some reason my simple_axis_server is getting aborted with > following error when I see through gdb: > >>> (gdb) bt > >>> #0 0x0013bcef in raise () from /lib/tls/libc.so.6 > >>> #1 0x0013d4f5 in abort () from /lib/tls/libc.so.6 > >>> #2 0x00c794b7 in __cxa_call_unexpected () from /usr/lib/libstdc++.so.5 > >>> #3 0x00c79504 in std::terminate () from /usr/lib/libstdc++.so.5 > >>> #4 0x00c796dc in __cxa_rethrow () from /usr/lib/libstdc++.so.5 > >>> #5 0x00e9e377 in initialize_module () from > /usr/local/axiscpp_deploy/deploy/lib/libaxis_server.so > >>> #6 0x0804b9d1 in main () > >>> > >>> > >>> I have verified many times that my axiscpp.conf is in right > place ( axiscpp_deploy/deploy/etc folder). server.wsdd is in > (axiscpp_deploy/deploy/conf folder) and other directories are > correct. For eas following is content of axiscpp.conf file: > >>> LogPath:/usr/local/axiscpp_deploy/deploy/log/AxisLog > >>> WSDDFilePath:/usr/local/axiscpp_deploy/deploy/etc/server.wsdd > >>> ClientLogPath:/usr/local/axiscpp_deploy/deploy/log/AxisClientLog > >>> XMLParser:/usr/local/axiscpp_deploy/deploy/lib/libaxis_xmlparser.so > >>> Transport_http:/usr/local/axiscpp_deploy/deploy/lib/libaxis2_transport.so > >>> > >>> > >>> Besides above APACHE2_HOME, AXISCPP_HOME, AXISCPP_DEPLOY env vars are set > >>> > >>> Could you please help me in resolving why I get this error. > >>> > >>> Secondly I am never able to deploy axis in apache following the
RE: Accessing C++ web service from JSP Client
Hi, Once you've deployed your C++ web service using Axis C++ ( http://ws.apache.org/axis/cpp/serveruser-guide.html#Deploy_the_service ), everything you need for accessing and deploying your JSP client to access the C++ web service should be contained within your WSDL file. The only possible addition is to ensure endpoint is correct for Axis C++, which will be in the form: http:///axis/ Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Murali Konnipati <[EMAIL PROTECTED]> wrote on 24/08/2006 11:05:55: > Hi Adrian, > >Thank you very much for your reply. Could you please provide me > information on how exactly I need to access the web service. > > Thanks & Regards, > > Murali Krishna K > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of Adrian Dick > Sent: Thursday, August 24, 2006 3:20 PM > To: Apache AXIS C User List > Subject: Re: Accessing C++ web service from JSP Client > > Hi, > > If you've generated and deployed your C++ web service from a WSDL file, > then any web service client ( be it C++, Java, .Net or JSP) should be able > to use it, by using the WSDL file. > > Regards, > Adrian > ___ > Adrian Dick ([EMAIL PROTECTED]) > > > Murali Konnipati <[EMAIL PROTECTED]> wrote on 24/08/2006 > 09:59:49: > > > Hi All, > > > >I have a C++ based web service and I would like to access the above > > C++ web service from the JSP client. I don't know is it possible to do > the > > same or no...? > > > > Please do the needful favor on the same. > > > > Thanks in advance, > > > > Murali Krishna K > > > > - > > 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] > > - > 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]
Re: Accessing C++ web service from JSP Client
Hi, If you've generated and deployed your C++ web service from a WSDL file, then any web service client ( be it C++, Java, .Net or JSP) should be able to use it, by using the WSDL file. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Murali Konnipati <[EMAIL PROTECTED]> wrote on 24/08/2006 09:59:49: > Hi All, > >I have a C++ based web service and I would like to access the above > C++ web service from the JSP client. I don't know is it possible to do the > same or no...? > > Please do the needful favor on the same. > > Thanks in advance, > > Murali Krishna K > > - > 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]
Re: An exception is trown when creating an instance of Call class
Hi, The steps you have taken so far sound correct, however, it sounds like you haven't completed the client-side configuration, see the client configuration steps of the Axis C++ install guide (http://ws.apache.org/axis/cpp/install-guide.html#Installing_Client ). Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Krankurs Leonid <[EMAIL PROTECTED]> wrote on 24/08/2006 05:17:12: > > Hi, > > What lib(s) and dll(s) from build must be used for utilization of invoke > method of Call object? > > I looked in from C:\Axis\ws-axis\c\tests\auto_build\testcases\dynamic\Test01 > - > there are no projects in this folder > > I created VC ++ 2k5 project based on files Calculator.h, Calculator.cpp > from C:\Axis\ws-axis\c\tests\auto_build\testcases\dynamic\Test01 > > i did include call.hpp, and used axis_client.lib, axis_client.dll. > > the app is crashing (throwing exception) when > Call* m_pCall = new Call(); > > the message of the caught exception looks like: > > < > Exception : DLOPEN FAILED in loading parser library Failed to load parser > within > server engine: > Error Message='The specified module could not be found. > 'Error Code='126' > Load lib error='' > > > > > sound quite confusing ... > > > Thank you in advance for any help there > > > Regards, > Leonid > > -- > View this message in context: http://www.nabble.com/An-exception-is- > trown-when-creating-an-instance-of-Call-class-tf2156580.html#a5957461 > Sent from the Axis - C++ - User forum at Nabble.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]
Fw: What is the best AXIS C++ practice to implement request/response MEP
Hi, I'm posting this back to the mailing list, so others can participate. For simple XSD types, simply choose the appropriate getElementAs method (eg: getElementAsString for xsd:string) For arrays of simple XSD types use getBasicArray For complex types, use getCmplxObject and getCmplxArray -- I strongly recommend looking at a WSDL2Ws generated example to understand how these should be used. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Hi Adrian, Thanks for the quick response - i have a scenario when in wsdl file of the service : name="MyResponse" /> What CAll::getElementAs should i use after Call::checkMessage>? Best regards, Leonid - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Where to deallocate memory for server-sided return values?
Hi,
If you're using Axis C++ 1.6beta (or a more recent nightly build) the
combination of the Axis engine and generated server skeletons will ensure
the value returned from the service is deallocated.
Regards,
Adrian
___
Adrian Dick ([EMAIL PROTECTED])
<[EMAIL PROTECTED]> wrote on 23/08/2006 08:44:25:
> Hi,
>
> can anybody tell me where i can deallocate allocated memory for
> result-values (e.g. strings or ArrayOfStrings) on server side?
> Or is this done by axis itself?
>
> Example of such a server-side method:
>
> ArrayOfstring* ServerSideClass::getStringList()
> {
> // Allocate memory:
> ArrayOfstring* resultArray = new ArrayOfstring;
> int resultArraySize = 3;
> resultArray->item.m_Array = new xsd__string[resultArraySize];
> resultArray->item.m_Size = resultArraySize;
>
> // Fill the resultArray:
> resultArray->item.m_Array[0] = "String1";
> resultArray->item.m_Array[1] = "String2";
> resultArray->item.m_Array[2] = "String3";
> return resultArray;
>
> // BUT WHERE TO DEALLOCATE THE resultArray ???
> }
>
> THANKS FOR ANY HELP!!
>
>
>
> -
> 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]
Re: To see the soap message...
Hi, What do you mean by "to see the soap message sent/received" ? Do you mean you want to be able to see the entire serialized SOAP message? If so, there are no methods giving this capability. If you simply want to have the data deserialized you need to use the IWrapperSoapDeSerializer::getAttributeAs... and getElementAs methods. Have you tried using the WSDL2Ws tooling to generate the client stubs and service skeletons for you? This will provide all the appropriate serialization/deserialization logic based on your WSDL. Regards, Adrian _______ Adrian Dick ([EMAIL PROTECTED]) "Raju, Prabhakar \(P.\)" <[EMAIL PROTECTED]> wrote on 23/08/2006 14:55:37: > Hi, > From axis c++ classes, to see the soap message sent / received, am I > to use this method ? > virtual void IWrapperSoapDeSerializer::getChardataAs ( void * pValue, > XSDTYPEtype > ) [pure virtual] > Deserialize character data, ie the data typically enclosed by an XML tag > > > FYI - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What is the best AXIS C++ practice to implement request/response MEP
Hi, If you don't want to use generated stub objects, you can work directly with the Call API, in much the same way as within generated stub objects. Probably the best way to understand using this API is to generate a stub from a simple WSDL then re-work to suit your needs. Also, we have a handful of testcases which you could use for examples. These can be found in the SVN repository here: http://svn.apache.org/viewvc/webservices/axis/trunk/c/tests/auto_build/testcases/dynamic/ Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) leo_k2 <[EMAIL PROTECTED]> wrote on 22/08/2006 14:10:41: > > I am a novice to AXIS C++. What would be the best AXIS C++ practice to > implement request/response MEP - no proxy object - just sending a SOAP > request and getting a SOAP response in one call. Is there any sample > implementing this pattern? > Is that about handles and chains? Thank you. > -- > View this message in context: http://www.nabble.com/What-is-the- > best-AXIS-C%2B%2B-practice-to-implement-request-response-MEP- > tf2146224.html#a5925179 > Sent from the Axis - C++ - User forum at Nabble.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]
RE: Apache axis not loading...
I'm surprised you aren't seeing anything from the compiler (or linker) showing a more specific error You can force ANT to log to a file by specifying the option -l It may then become more obvious, otherwise you can post it here, and we will be better able to diagnose the problem. Adrian _______ Adrian Dick ([EMAIL PROTECTED]) "Raju, Prabhakar \(P.\)" <[EMAIL PROTECTED]> wrote on 22/08/2006 13:43:04: > Nothig specific I could see. Is there a trace or log of compilation? It > just said failed with error code 1. > > FYI > > -----Original Message- > From: Adrian Dick [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 22, 2006 3:35 AM > To: Apache AXIS C User List > Subject: Re: Apache axis not loading... > > Hi, > > This based on the location in the ANT scripts at which failure occured, > it > sounds like the Apache module failed to compile. What were the > compilation > errors (You should see these just before the point at which the ANT > script > indicated a failure) ? > > Adrian > ___ > Adrian Dick ([EMAIL PROTECTED]) > > > "Raju, Prabhakar \(P.\)" <[EMAIL PROTECTED]> wrote on 21/08/2006 21:09:18: > > > Hi, > > The problem is not with apache. My build did not create this file > > libaxiscpp_mod2.so. When I turned the flags on for apache 2 modules, > > g++ failed just before building apache20 libs at line 27 of > > buildApache20Module.xml. > > > Line 27: exceptions="true" > > outtype="shared" multithreaded="true"> > > Any clues? > > regards > > > - > 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] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Apache axis not loading...
Hi, This based on the location in the ANT scripts at which failure occured, it sounds like the Apache module failed to compile. What were the compilation errors (You should see these just before the point at which the ANT script indicated a failure) ? Adrian ___ Adrian Dick ([EMAIL PROTECTED]) "Raju, Prabhakar \(P.\)" <[EMAIL PROTECTED]> wrote on 21/08/2006 21:09:18: > Hi, > The problem is not with apache. My build did not create this file > libaxiscpp_mod2.so. When I turned the flags on for apache 2 modules, > g++ failed just before building apache20 libs at line 27 of > buildApache20Module.xml. > Line 27: exceptions="true" > outtype="shared" multithreaded="true"> > Any clues? > regards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Query about Axis-C version
The binaries were built using gcc 3.2.3, so that sounds like it could be sufficiently different to cause compatibility issues. If your latest checks don't get it working, it may be that you will need to compile from source, to suit your version of the compiler. Adrian ___ Adrian Dick ([EMAIL PROTECTED]) "Jacoud Bastien" <[EMAIL PROTECTED]> wrote on 18/08/2006 14:37:31: > Yes I use binaries version of Axis and the version of the compiler is 3.4.2. > I'm trying to re-install Axis with the installation guide to be sure > I did not forget something during the 1st installation. > > > -----Message d'origine- > De : Adrian Dick [mailto:[EMAIL PROTECTED] > Envoyé : vendredi 18 août 2006 12:38 > À : Apache AXIS C User List > Objet : RE: Query about Axis-C version > > Hmm... > > If, as you say, you have the Axis C++ JARs available on the appropriate > paths, and using the command you originally gave, I wouldn't expect you to > see this error. > > Are you using pre-build binaries? > If so, could it be the compiler/linker used to create theAxis C++ binaries > is not totally compatible with the compiler/linker you're using for your > application? > > > Adrian > ___ > Adrian Dick ([EMAIL PROTECTED]) > > > "Jacoud Bastien" <[EMAIL PROTECTED]> wrote on 18/08/2006 > 09:49:51: > > > Hi, > > This is one of errors I obtained: > > > > D:\DOCUME~1\A118733\LOCALS~1\Temp/cc0qbaaa.o(.text+0x55f): > > ConnectionException.cpp: undefined reference to `axiscpp:: > > SoapFaultException::SoapFaultException()' > > > > All other errors look like to this one. > > > > Regards, > > Bastien. > > > > -Message d'origine- > > De : Adrian Dick [mailto:[EMAIL PROTECTED] > > Envoyé : vendredi 18 août 2006 10:40 > > À : Apache AXIS C User List > > Objet : Re: Query about Axis-C version > > > > Hi, > > > > Your command looks right. What are the specific errors you're seeing? > > > > Regards. > > Adrian > > ___ > > Adrian Dick ([EMAIL PROTECTED]) > > > > > > "Jacoud Bastien" <[EMAIL PROTECTED]> wrote on 18/08/2006 > > 09:05:15: > > > > > Hello, > > > I had developed java web services with Axis 1.3 to deploy them on > > > tomcat server. These services work correctly with a java client. > > > For another application, I need to compile web services in C++. So I > > > downloaded the current version of Axis-C on your web site (it seems > > > to be 1.6 Beta version) and I tried to compile the web services from > > > my WSDL files on a windows platform. > > > To compile from the WSDL, I followed the procedure described on the > > > joined file, but, when I realize the operation: > > > "g++ *.cpp -I/include -L > > installation directory>/lib -ldl -laxiscpp_client -ocalculator" > > > I obtain lot of "undefined reference" messages although I put .dll > > > files in lib directory. > > > I don't know if it's an error of Axis version or I don't realize > > > good operation. Can you help to resolve this problem? > > > Regards, > > > > > > Bastien JACOUD > > > Unité Public - Santé - Transport - Département SPSL - Atos WORLDLINE > > > [EMAIL PROTECTED] > > > Tel.: + 33.(0)4 78 17 69 57 > > > 107-109 Boulevard Vivier Merle 69438 Lyon Cedex 03 > > > [attachment "clientuser-guide.pdf" deleted by Adrian Dick/UK/IBM] > > > - > > > 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] > > > > > - > 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] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Query about Axis-C version
Hmm... If, as you say, you have the Axis C++ JARs available on the appropriate paths, and using the command you originally gave, I wouldn't expect you to see this error. Are you using pre-build binaries? If so, could it be the compiler/linker used to create theAxis C++ binaries is not totally compatible with the compiler/linker you're using for your application? Adrian _______ Adrian Dick ([EMAIL PROTECTED]) "Jacoud Bastien" <[EMAIL PROTECTED]> wrote on 18/08/2006 09:49:51: > Hi, > This is one of errors I obtained: > > D:\DOCUME~1\A118733\LOCALS~1\Temp/cc0qbaaa.o(.text+0x55f): > ConnectionException.cpp: undefined reference to `axiscpp:: > SoapFaultException::SoapFaultException()' > > All other errors look like to this one. > > Regards, > Bastien. > > -Message d'origine- > De : Adrian Dick [mailto:[EMAIL PROTECTED] > Envoyé : vendredi 18 août 2006 10:40 > À : Apache AXIS C User List > Objet : Re: Query about Axis-C version > > Hi, > > Your command looks right. What are the specific errors you're seeing? > > Regards. > Adrian > ___ > Adrian Dick ([EMAIL PROTECTED]) > > > "Jacoud Bastien" <[EMAIL PROTECTED]> wrote on 18/08/2006 > 09:05:15: > > > Hello, > > I had developed java web services with Axis 1.3 to deploy them on > > tomcat server. These services work correctly with a java client. > > For another application, I need to compile web services in C++. So I > > downloaded the current version of Axis-C on your web site (it seems > > to be 1.6 Beta version) and I tried to compile the web services from > > my WSDL files on a windows platform. > > To compile from the WSDL, I followed the procedure described on the > > joined file, but, when I realize the operation: > > "g++ *.cpp -I/include -L > installation directory>/lib -ldl -laxiscpp_client -ocalculator" > > I obtain lot of "undefined reference" messages although I put .dll > > files in lib directory. > > I don't know if it's an error of Axis version or I don't realize > > good operation. Can you help to resolve this problem? > > Regards, > > > > Bastien JACOUD > > Unité Public - Santé - Transport - Département SPSL - Atos WORLDLINE > > [EMAIL PROTECTED] > > Tel.: + 33.(0)4 78 17 69 57 > > 107-109 Boulevard Vivier Merle 69438 Lyon Cedex 03 > > [attachment "clientuser-guide.pdf" deleted by Adrian Dick/UK/IBM] > > - > > 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] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Query about Axis-C version
Hi, Your command looks right. What are the specific errors you're seeing? Regards. Adrian ___ Adrian Dick ([EMAIL PROTECTED]) "Jacoud Bastien" <[EMAIL PROTECTED]> wrote on 18/08/2006 09:05:15: > Hello, > I had developed java web services with Axis 1.3 to deploy them on > tomcat server. These services work correctly with a java client. > For another application, I need to compile web services in C++. So I > downloaded the current version of Axis-C on your web site (it seems > to be 1.6 Beta version) and I tried to compile the web services from > my WSDL files on a windows platform. > To compile from the WSDL, I followed the procedure described on the > joined file, but, when I realize the operation: > “g++ *.cpp -I/include -L installation directory>/lib -ldl -laxiscpp_client –ocalculator” > I obtain lot of “undefined reference” messages although I put .dll > files in lib directory. > I don’t know if it’s an error of Axis version or I don’t realize > good operation. Can you help to resolve this problem? > Regards, > > Bastien JACOUD > Unité Public - Santé - Transport - Département SPSL - Atos WORLDLINE > [EMAIL PROTECTED] > Tel.: + 33.(0)4 78 17 69 57 > 107–109 Boulevard Vivier Merle 69438 Lyon Cedex 03 > [attachment "clientuser-guide.pdf" deleted by Adrian Dick/UK/IBM] > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
Re: Configure file missing in linux source
Hi, Assuming you're talking about Axis C++ 1.x, the "configure" system hasn't been supported for some time now. You can find the current build instructions here: http://ws.apache.org/axis/cpp/antbuild-guide.html And the installation instructions here: http://ws.apache.org/axis/cpp/install-guide.html Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) "Raju, Prabhakar \(P.\)" <[EMAIL PROTECTED]> wrote on 17/08/2006 15:12:20: > Hi, > The file "configure" is missing in linux src download. I couln't > install. Please help. > regards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis] Null message contents with AXISCPP
Hi, Well, it's good to here we've resolved the first of your problems. As for your second problem Currently, I'm not too certain as to where your problem lies, however I do have a couple of thoughts. I notice the SOAP elements in your response message don't seem to exactly match the names in your WSDL snippets. Alternatively, I know the handling of attributes in Axis C++ is still fairly basic, so you could be hitting some limitation there, possibly relating to complex type elements with attributes but no child element. We could make a better diagnosis of the problem if you're able to turn on trace while reproducing this problem (see http://ws.apache.org/axis/cpp/TraceGuide.html for details), and also capture the SOAP response message. Adrian _______ Adrian Dick ([EMAIL PROTECTED]) "Alastair FETTES" <[EMAIL PROTECTED]> wrote on 09/08/2006 00:22:14: > Hi Adrian, > > I'm much happier now with that multi-ref situation worked out. For one > thing we have a layer on top of our w/s architecture that removes > redundancies in the data and thus the benefits from using multi-ref > aren't very high. Much more importantly though is the fact that > disabling multirefs solved the first of my problems. The second problem > is still causing me a wee bit of grief. > > The basic idea is I am trying to make my XML more efficient by using > attributes as opposed to elements. It also follows my own/our coding > guidelines for XML and the general rule of thumb when authoring XML. > When I convert our data holders from element to attributes though, I get > the second problem. > > The following is a message that causes a SoapFaultException with the > message "Cannot deserialize the requested element". > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > > soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";> > xsi:type="ns1:fooOutputType" > xmlns:ns1="http://www.foo.com/"/> > > > > > This is the schema that causes the problem: > > http://www.w3.org/2001/XMLSchema"; > targetNamespace="http://www.foo.com/"; > xmlns:foo="http://www.foo.com/";> > http://schemas.xmlsoap.org/soap/encoding/"/> > > > > > > > > > > Referred to by the following WSDL messages: > ... > > > > > > > > > > > > > > ... > parameterOrder="inputMessage"> > > > > parameterOrder="inputMessage"> > > > > ... > > Client is an executable Axis-C++ application. Server is Axis-Java > hosted on Tomcat. Server does not have a problem at all. Axis-CPP > causes the problems. > > When fooMessageFromString() is called, I get an SoapFaultException. > When I call fooStringFromMessage() I get an unhandled exception (note: I > am handling AxisException, SoapFaultException and OtherFaultException in > my try/catch block). > > Have you ever seen problems such as this before? > > Thanks, > Alastair > > This e-mail and any attachments are intended solely for the use of the > intended recipient(s) and may contain legally privileged, proprietary > and/or confidential information. Any use, disclosure, dissemination, > distribution or copying of this e-mail and any attachments for any > purposes that have not been specifically authorized by the sender is > strictly prohibited. If you are not the intended recipient, please > immediately notify the sender by reply e-mail and permanently delete all > copies and attachments. > > The entire content of this e-mail is for "information purposes" only and > should not be relied upon by the recipient in any way unless otherwise > confirmed in writing by way of letter or facsimile. > > > -Original Message- > From: Adrian Dick [mailto:[EMAIL PROTECTED] > Sent: Monday, August 07, 2006 1:36 AM > To: Apache AXIS C User List > Subject: Re: [Axis] Null message contents with AXISCPP > > Hi, > > In reference to your first problem. I notice your response SOAP message > is > making use of multi-ref. > Unfortunately, this isn't currently supported by Axis C++. > > You don't mention which server you're using, but if it's Axis Java, you > can > disable multi-ref using the WSDD file (see > http://ws.apache.org/axis/java/reference.html#Gl
Re: [Axis] Null message contents with AXISCPP
Hi,
In reference to your first problem. I notice your response SOAP message is
making use of multi-ref.
Unfortunately, this isn't currently supported by Axis C++.
You don't mention which server you're using, but if it's Axis Java, you can
disable multi-ref using the WSDD file (see
http://ws.apache.org/axis/java/reference.html#GlobalAxisConfiguration ).
What specific problems are you seeing when using attributes? Do you have
any error messages?
Regards,
Adrian
___
Adrian Dick ([EMAIL PROTECTED])
"Alastair FETTES" <[EMAIL PROTECTED]> wrote on 04/08/2006
23:55:20:
> I'm currently having a problem running the Axis-C 1.6b.
>
> All environment settings have been set as appropriate and I am able to
> run *simple* methods. I.e. The "echoString" test case works for me (see
> attached wsdl). I am correctly able to send the value out and retrieve
> the mssage back. However, when I try to run more complex services I run
> into problems. I.e. "echoMessageFromString" (see attached wsdl).
>
> Attached is a copy of my WSDL. Server side is java and I have tested it
> through the URL interface and visibily inspected the response XML to be
> the following:
>
>
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>
>
>
> soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";>
>
>
>
>
> soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> xsi:type="ns1:messageOutputType"
> xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
> xmlns:ns1="http://foo.com/";>
> my attribute value 3
> my attribute value 4
>
>
>
>
> This is as expected therefore I am not worried about the java-server
> side (other than the lack of default namespace and the foo.com namespace
> declared top level). The problem lies on the cpp-client side.
>
> The following bit of (generated) code always returns null:
> messageOutputType* foo::echoMessageFromString(xsd__string Value0)
> {
> ...
> pReturn = (messageOutputType *) m_pCall->getCmplxObject(
> (void *) Axis_DeSerialize_messageOutputType,
> (void *) Axis_Create_messageOutputType,
> (void *) Axis_Delete_messageOutputType,
> "returnMessage",
> 0);
> ...
> }
>
> Another problem is when I switch from using child elements to attributes
> for transfer of data. I run into problems that Axis is unable to
> serialize/deserialize the messages in this case. The following is an
> example of a schema type that I have encountered this problem with:
>
>
>
>
>
>
>
> All problems are occuring on the CPP side mind you. To sum up what this
> means is I'm able to pass strings and other simple types back and forth
> but not (slightly) more complex messages, rending the CPP side useless
> for me. I could use Axis2 but have had no luck with code generation on
> that side (see [Axis2] Code generation to C email from 2/8/2006).
>
> Any help would be most appreciated.
>
> Cheers,
> Alastair
>
> This e-mail and any attachments are intended solely for the use of the
> intended recipient(s) and may contain legally privileged, proprietary
> and/or confidential information. Any use, disclosure, dissemination,
> distribution or copying of this e-mail and any attachments for any
> purposes that have not been specifically authorized by the sender is
> strictly prohibited. If you are not the intended recipient, please
> immediately notify the sender by reply e-mail and permanently delete all
> copies and attachments.
>
> The entire content of this e-mail is for "information purposes" only and
> should not be relied upon by the recipient in any way unless otherwise
> confirmed in writing by way of letter or facsimile.
> [attachment "example.wsdl" deleted by Adrian Dick/UK/IBM]
> -
> 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]
Re: Installation problems on Windows XP
Hi, This sounds like one of two problems (or possibly both). 1) The mod_axis2.dll isn't in the location you specified within httpd.conf 2) The Axis DLLs upon which it has dependencies are not available on the PATH (ie ensure /bin is included on the system path used by Apache) Hope that helps. Adrian ___ Adrian Dick ([EMAIL PROTECTED]) "Vijaya Bhaskar Peddinti" <[EMAIL PROTECTED]> wrote on 03/08/2006 07:25:25: > Hi all, > > I am trying to install axis-c-1.6b-Win32 with Apache 2.2.3 and I am > getting the following error: > > The Apache service named reported the following error: > >>> httpd.exe: Syntax error on line 486 of C:/Program Files/Apache > Software Foundation/Apache2.2/conf/httpd.conf: Cannot load C: > /Program Files/Apache Software Foundation/Apache2. > 2/modules/mod_axis2.dll into server: The specified module could not be found. > > > Please guide me on how to resolve this. > > Thanks & Regards, > Bhaskar. > > > CAUTION - Disclaimer * > This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION > intended solely for the use of the addressee(s). If you are not the > intended recipient, please notify the sender by e-mail and delete > the original message. Further, you are not to copy, disclose, or > distribute this e-mail or its contents to any other person and any > such actions are unlawful. This e-mail may contain viruses. Infosys > has taken every reasonable precaution to minimize this risk, but is > not liable for any damage you may sustain as a result of any virus > in this e-mail. You should carry out your own virus checks before > opening the e-mail or attachment. Infosys reserves the right to > monitor and review the content of all messages sent to or from this > e-mail address. Messages sent to or from this e-mail address may be > stored on the Infosys e-mail system. > ***INFOSYS End of Disclaimer INFOSYS*** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: trouble about c++ client using vc6
Hi,
Does the error occur as you enter the constructor or when invoking
m_pCall->setEndpointURI()?
If the former, this suggests a configuration problem which startup trace
should capture.
Are catching any exceptions produced from Axis (ie: catch AxisException) ?
If so, what messages are you seeing?
In any case, I'd recommend enabling trace and startup trace, re-creating
the problem and see if anything obvious shows up in the trace files.
Instructions on using trace can be found here:
http://ws.apache.org/axis/cpp/TraceGuide.html
Regards,
Adrian
___
Adrian Dick ([EMAIL PROTECTED])
iamnxm <[EMAIL PROTECTED]> wrote on 03/07/2006 08:09:07:
> I have successfully set up a axis-java webservice. I try to call it
> with a c++ client. There are my steps : 1) Deploying my web service
> using AdminClient Tool. 2) Show WSDL via add "?WSDL" to the end of
> the webservice (eg.http://localhost:8080/update/UpdateService?WSDL)
> 3) Utilise WSDL2WS tool to generate the client stub 4) Create a vc
> MFC wizard project 5) Add stub files to the project 6) Set the
> include path to the include directory of the axis binary
> distribution 7) Add the axis_client.lib to the library modules path
> of this project 8) call webservice like below: UpdateService up;
> char * hasUp = up.hasUpdate(); or UpdateService *up = new
> UpdateService; char * hasUp = up->hasUpdate(); compilation goes well
> but error occurs when runing. I have debuged it and fond that it
> seems that there are some errors in clauses below: UpdateService::
> UpdateService() :Stub(" ", APTHTTP1_1) { m_pCall->setEndpointURI("
> http://192.168.1.107:8080/update/services/UpdateService";); } any
> suggestions are appreciated
> View this message in context: trouble about c++ client using vc6
> Sent from the Axis - C++ - User forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis C++ client getting "Aborted"
Hi, Can you try turning on trace and startup trace. Details of how to do this (and some useful entries to watch out for) can be found here: http://ws.apache.org/axis/cpp/TraceGuide.html Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) "Bhatt, Nitin IN GGN SISL" <[EMAIL PROTECTED]> wrote on 22/06/2006 04:49:28: > Hi all, > > I have managed to build and compile the client side stub using Axis > C++ client. > The problem that I am facing now is that as soon as I construct the > object for my client, I get an “Aborted” message. > > > Any suggestions. > > Thanks > > Nitin >
RE: Axis can't find my xerces library
Hi, When Axis-C is built it is linked with a dependency on the version of Xerces-C present while building. This means, if you build against Xerces-C v2.2.0 then you will need Xerces-C v2.2.0 available when running Axis-C. I'm surprised you're able to build Axis-C, when Xerces-C v2.2.0 failed to build -- but presumably that means it managed to build the artefacts required by Axis-C ( which is actually a surprisingly small subset of the Xerces-C objects). Have you tried re-building Axis-C using your successful Xerces-C v2.7.0 build? And then also running with that version? Regards, Adrian _______ Adrian Dick ([EMAIL PROTECTED]) "Yair Zaslavsky" <[EMAIL PROTECTED]> wrote on 08/06/2006 15:42:43: > Good day Adrian (and all), > I'm compiling Axis C- 1.6B with Xerces-C 2.2.0. > I fail to build Xerces-C 2.2.0 > I tried building (as experiment) Xerces-C 2.7.0 (without building axis - > just to see I undertstand how to build xerces) and succeeded, and > provided an error log. > Can you tell me what I'm doing wrong? > Can you elaborate more about the "built time" and "run time" versions of > xerces - I didn't fully understand this issue. > Thanks > Yair > > > > -Original Message- > From: Adrian Dick [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 08, 2006 5:37 PM > To: Apache AXIS C User List > Subject: RE: Axis can't find my xerces library > > Hi, > > So, you're saying that you're trying to use Axis-C 1.6b with Xerces-C > 2.7.0 > ? > If this is the case and assuming you're using using the binary > distribution > of Axis-C you will have problems, as this was built against Xerces-C > 2.2.0 > (hence not finding the correct library). > > My initial reaction is to suggest building Axis-C from source against > your > desired version of Xerces-C --- we've found it doesn't particularly > matter > which version you use, as long as it is the same version and build time > and > runtime. > Alternatively, you may also wish to try a recent nightly build, which I > believe uses Xerces-C 2.6.0 (as the highest level compatible with the > compilers across our build machines). > > Regards, > Adrian > ___ > Adrian Dick ([EMAIL PROTECTED]) > > > "Yair Zaslavsky" <[EMAIL PROTECTED]> wrote on 08/06/2006 15:13:20: > > > As explained in previous emails, I am trying to compile axis on > > linux 64bit machine. > > I downloaded xerces c++ 2.2.0 for that. > > Apache's xerces instructions are for 2.7.0. I tried building xerces > > c++ 2.2.0 with these versions, but in vein. > > I tried budiling xerces c++ 2.7.0 with the instructions and succeeded. > > > > Here is my xerces-c-root environment variable value: > > echo $XERCESCROOT > > /home/yair/xerces-c-src2_2_0/xerces-c-src2_2_0/ > > > > I ran: > > autoconf > > ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread > -b64 > > gmake > > > > > > In file included from /home/yair/xerces-c-src2_2_0/xerces-c- > > src2_2_0//include/xercesc/util/RefArrayVectorOf.hpp:30, > > from XMLString.cpp:74: > > /home/yair/xerces-c-src2_2_0/xerces-c- > > src2_2_0//include/xercesc/util/RefArrayVectorOf.c: In destructor > > `xercesc_2_2::RefArrayVectorOf::~RefArrayVectorOf()': > > /home/yair/xerces-c-src2_2_0/xerces-c- > > src2_2_0//include/xercesc/util/RefArrayVectorOf.c:21: error: > > `fAdoptedElems' undeclared (first use this function) > > /home/yair/xerces-c-src2_2_0/xerces-c- > > src2_2_0//include/xercesc/util/RefArrayVectorOf.c:21: error: (Each > > undeclared identifier is reported only once for each function it > appears > in.) > > /home/yair/xerces-c-src2_2_0/xerces-c- > > src2_2_0//include/xercesc/util/RefArrayVectorOf.c:23: error: > > `fCurCount' undeclared (first use this function) > > /home/yair/xerces-c-src2_2_0/xerces-c- > > src2_2_0//include/xercesc/util/RefArrayVectorOf.c:24: error: > > `fElemList' undeclared (first use this function) > > gmake[1]: *** [XMLString.o] Error 1 > > gmake[1]: Leaving directory `/home/yair/xerces-c-src2_2_0/xerces-c- > > src2_2_0/src/xercesc/util' > > > > > > > > Without this, I cannot use axis. > > Any help is appreciated. > > > > > > > > From: John Hawkins [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, June 07, 2006 5:49 PM > > To: Apache AXIS C User List > > Subject: RE: Axis can't find my xerces library > > > > > > I'm going to g
RE: Axis can't find my xerces library
Hi, So, you're saying that you're trying to use Axis-C 1.6b with Xerces-C 2.7.0 ? If this is the case and assuming you're using using the binary distribution of Axis-C you will have problems, as this was built against Xerces-C 2.2.0 (hence not finding the correct library). My initial reaction is to suggest building Axis-C from source against your desired version of Xerces-C --- we've found it doesn't particularly matter which version you use, as long as it is the same version and build time and runtime. Alternatively, you may also wish to try a recent nightly build, which I believe uses Xerces-C 2.6.0 (as the highest level compatible with the compilers across our build machines). Regards, Adrian _______ Adrian Dick ([EMAIL PROTECTED]) "Yair Zaslavsky" <[EMAIL PROTECTED]> wrote on 08/06/2006 15:13:20: > As explained in previous emails, I am trying to compile axis on > linux 64bit machine. > I downloaded xerces c++ 2.2.0 for that. > Apache’s xerces instructions are for 2.7.0. I tried building xerces > c++ 2.2.0 with these versions, but in vein. > I tried budiling xerces c++ 2.7.0 with the instructions and succeeded. > > Here is my xerces-c-root environment variable value: > echo $XERCESCROOT > /home/yair/xerces-c-src2_2_0/xerces-c-src2_2_0/ > > I ran: > autoconf > ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread -b64 > gmake > > > In file included from /home/yair/xerces-c-src2_2_0/xerces-c- > src2_2_0//include/xercesc/util/RefArrayVectorOf.hpp:30, > from XMLString.cpp:74: > /home/yair/xerces-c-src2_2_0/xerces-c- > src2_2_0//include/xercesc/util/RefArrayVectorOf.c: In destructor > `xercesc_2_2::RefArrayVectorOf::~RefArrayVectorOf()': > /home/yair/xerces-c-src2_2_0/xerces-c- > src2_2_0//include/xercesc/util/RefArrayVectorOf.c:21: error: > `fAdoptedElems' undeclared (first use this function) > /home/yair/xerces-c-src2_2_0/xerces-c- > src2_2_0//include/xercesc/util/RefArrayVectorOf.c:21: error: (Each > undeclared identifier is reported only once for each function it appears in.) > /home/yair/xerces-c-src2_2_0/xerces-c- > src2_2_0//include/xercesc/util/RefArrayVectorOf.c:23: error: > `fCurCount' undeclared (first use this function) > /home/yair/xerces-c-src2_2_0/xerces-c- > src2_2_0//include/xercesc/util/RefArrayVectorOf.c:24: error: > `fElemList' undeclared (first use this function) > gmake[1]: *** [XMLString.o] Error 1 > gmake[1]: Leaving directory `/home/yair/xerces-c-src2_2_0/xerces-c- > src2_2_0/src/xercesc/util' > > > > Without this, I cannot use axis. > Any help is appreciated. > > > > From: John Hawkins [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 07, 2006 5:49 PM > To: Apache AXIS C User List > Subject: RE: Axis can't find my xerces library > > > I'm going to guess that you don't have correct versions of xerces in > your lib path and readable > > > "Yair Zaslavsky" <[EMAIL PROTECTED]> > 07/06/2006 15:03 > > Please respond to > "Apache AXIS C User List" > > To > > "Apache AXIS C User List" > > cc > > > > Subject > > RE: Axis can't find my xerces library > > > > > > > > > > > I performed the rename (libaxis_xerces.so -> libaxis_xmlparser.so ), > and now I get the following error: > > terminate called after throwing an instance of 'std::logic_error' > what(): basic_string::_S_construct NULL not valid > > > I did use both runtime tracing and startup tracing, but I do not see > log files, so it’s hard for me to provide more info: > > The startup tracing is set using the envrioment variable: > AXISCPP_STARTUP_TRACE and set it /home/yair/axis_startup.log > At the axiscpp.conf file I added the following line: > LogPath:/home/yair/axis_runtime.log > > Do you have any ideas for the cause of the error? > > Thanks > > Yair > > > > > the names are wrong - you need the libaxis_xerces - you'll have to > rename it in the axiscppconf file (or rename the axis_xerces lib to > the one that simpleaxisserver is looking for.) > It's not clear to me but it looks like you might not have set > axiscpp_deploy correctly because the conf file below is correct. > > "Yair Zaslavsky" <[EMAIL PROTECTED]> > 07/06/2006 14:22 > > > Please respond to > "Apache AXIS C User List" > > > > To > > "Apache AXIS C User List" > > cc > > > > Subject > > RE: Axis can't find my xerces library > > > > > > > > > > > > > > You are correct John, t
Re: xsd_Base64
Hi, You say the maximum data size you can use is 36,615 -- is this just for a particular example, or have you experimented with different sizes around this value? Taking a quick look through the code, I can see that we may have a problem with large data objects, as the data length is stored as an int. According to the ANSI C spec this is a signed 16bit integer, so having a maximum value of 32,767, although a number of compilers use a 32bit integer which increase this to a maximum value of 2,147,483,647. Changing this to an unsigned long long (64bit integer) will give a maximum of 18,446,744,073,709,551,615, sufficient for most needs. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) "Pawel Pustelnik" <[EMAIL PROTECTED]> wrote on 31/05/2006 20:38:27: > Hello All, > > What is the maximum size of the xsd_Base64 array? > I am asking because I found something strange. > I want to send a binary data from the server to the client. > I implemented the client and server using apache axis and it is > working but not perfectly. > I read the image file (for example some JPG file) and send it to the > client. However when data size is more then 36615 bytes then the > client can only read 36615 bytes. > Is it a bug in axis? (I created very similar server in *.asmx file > under Windows and I can send very big images without any problems). > > Regards, > Pawel > > > -- > Pawel Pustelnik > Control Engineer > > --- > Future Processing Sp. z o.o. > Tel: +48 604 084 653 > Tel/Fax: +48 32 2726202 > [EMAIL PROTECTED] > www.future-processing.com > --- > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: AxisEngineException
Hi,
I believe you've found a bug in the generated stubs.
About 7 lines into each web service operation in the generated stubs you
will find something like:
if (NULL==m_pCall->getTransportProperty("SOAPAction",false))
m_pCall->setTransportProperty(SOAPACTION_HEADER ,
"http://tempuri.org/Add";);
The test for an existing value is what's causing you the problem. Because
you've already used the stub once, the SOAPaction has already been set, so
the value isn't being reset with the new value, which is why we're seeing
the server respond with the wrong message.
The reason we haven't found this a problem is because the majority of our
testing takes place against Axis C++ and Axis Java, which use the message
element names to determine the operation being invoked, while you appear to
be using a .Net web service which I believe makes use of the soapAction.
Can you try removing the test for an exising value within your generated
stubs and re-run.
If this resolves your problem, can you raise a Jira issue and we will fix
WSDL2Ws so it no longer has this behaviour.
Regards,
Adrian
___
Adrian Dick ([EMAIL PROTECTED])
"Cheng, John" <[EMAIL PROTECTED]> wrote on 16/05/2006 21:44:47:
> Adrian,
>
> I got the soap message that exchanged for two function calls (see
> below). I think the soapaction in the http header for the second
> function always uses the previous functions soapacton.
>
> I also attached my wsdl file. Thanks!
>
> John Cheng
>
> ==
>
> For s.HelloWorld();
>
> Send:
>
> -
> localhost:8080
> text/xml; charset=UTF-8
> "http://tempuri.org/HelloWorld";
> 340
>
>
>
> - xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> -
> http://tempuri.org/"; />
>
>
>
>
>
> Return:
>
> -
> Microsoft-IIS/5.1
> Tue, 16 May 2006 20:20:54 GMT
> ASP.NET
> 2.0.50727
> private, max-age=0
> text/xml; charset=utf-8
> 363
>
>
>
> - http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
> -
> - http://tempuri.org/";>
> Hello World
>
>
>
>
>
>
> s.Add(12, 24);
>
> Send:
>
> -
> localhost:8080
> text/xml; charset=UTF-8
> "http://tempuri.org/HelloWorld";
> 362
>
>
>
> - xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> -
> - http://tempuri.org/";>
> 12
> 24
>
>
>
>
>
> Return:
>
> -
> Microsoft-IIS/5.1
> Tue, 16 May 2006 20:21:07 GMT
> ASP.NET
> 2.0.50727
> private, max-age=0
> text/xml; charset=utf-8
> 363
>
>
>
>
> - http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
> -
> - http://tempuri.org/";>
> Hello World
>
>
>
>
> -Original Message-
> From: Adrian Dick [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 16, 2006 3:51 AM
> To: Apache AXIS C User List
> Subject: RE: AxisEngineException
>
> Hi,
>
> I'm surprised you're having problems using the same stub twice. We have
> numerous testcases which re-use the same stub object, including mixed
> operations.
>
> Looking at the trace, it would appear the second call didn't receive the
> expected SOAP message.
>
> Can you use TCPmon, or similiar, to capture the "on-the-wire" messages
> when
> making these two subsequent calls?
> A copy of your WSDL would also be helpful, so we can ensure the correct
> names and values are being used throughout.
>
> Regards,
> Adrian
> ___
> Adrian Dick ([EMAIL PROTECTED])
>
>
> "Cheng, John" <[EMAIL PROTECTED]> wrote on 15/05/2006 16:26:36:
>
> > Adrian,
> >
> > Thanks for the help! I found the problem after enable the trace. It
> was
> > due to my searching path did not include the directory where
> > AxisXMLParserXerces.dll is located. My testing sample is working now.
> > But I found a
RE: Crash in XercesHandler.cpp with & in response
Excellent news!!!
When the final release becomes available in the next few days, you may wish
to consider upgrading to Axis C++ 1.6 , as a number of memory issues (like
this one) and leaks have been resolved since 1.5.
Adrian
___
Adrian Dick ([EMAIL PROTECTED])
"Iwan Tomlow" <[EMAIL PROTECTED]> wrote on 16/05/2006 15:28:12:
> Hi all,
>
> Just letting you know I think the problem is solved!
> I was trying to get the 1.6 nightly build to work, but kept running into
> other problems.
>
> However, I took a glance at the XercesHandler.cpp included in the 1.6,
> and it seems the part that was causing me problems has been changed
> significantly (more then described in AXISCPP-825).
>
> I applied this change to my 1.5 sources, rebuild AxisXmlParser.xml, and
> don't get the crash anymore on any machine!
> Just for reference, the code for the 'PreviousNameOrValue' case in
> XercesHandler::characters was changed to:
>
> // The following code is necessary as it is important to get the correct
> heap
> // (i.e the one that XMLString is using!) when creating a memory object
> to put
> // back into 'm_pNextElement->m_pchNameOrValue'. By using the XMLString
> // function, we can ensure that only the memory belonging to (and thus
> able to
> // destroy) the same segment as XMLString is used. If you don't
> understand
> // what is going on, don't change it!
> if (cp_PreviousNameOrValue)
> {
> // Get a pointer to the transcoded character.
> char * pTransChar = XMLString::transcode( chars);
> // Create a dummy string and populate.
> char * psDummy = new char[ strlen(
> m_pNextElement->m_pchNameOrValue) +
>
> strlen( pTransChar) + 1];
> strcpy( psDummy, m_pNextElement->m_pchNameOrValue);
> strcat( psDummy, pTransChar);
> // Create pointer to new Name or Value string.
> char * pNewNameOrValue = XMLString::replicate(
> psDummy);
> // Delete the old Name and Value string.
> XMLString::release( const_cast
> (&(m_pCurrElement->m_pchNameOrValue)));
> // Assign the new value of Name or Value string.
> m_pNextElement->m_pchNameOrValue = pNewNameOrValue;
> // Clean up.
> delete [] psDummy;
> XMLString::release( &pTransChar);
> }
>
> Regards,
> Iwan
>
> -Original Message-
> From: Iwan Tomlow [mailto:[EMAIL PROTECTED]
> Sent: dinsdag 16 mei 2006 15:13
> To: Apache AXIS C User List
> Subject: RE: Crash in XercesHandler.cpp with & in response
>
> Ah, that's more difficult, since the webservice is only made available
> over HTTPS, so I can't just drop tcpmon in between.
> The xml-data is actually taken from the log the server has written just
> before posting the reply.
>
> I really think it's more of a memory issue as described in AXISCPP-825,
> but that fix alone doesn't seem enough.
> I've been experimenting some more, and it doesn't always crash: in debug
> mode it works fine most of the time; on Windows XP the release mode
> crashes sometimes; on Windows 2000 however, the release version crashes
> consistently - and the production client-app must run on a Windows 2000
> touchscreen terminal :(
>
> Regards,
> Iwan
>
> -Original Message-
> From: Adrian Dick [mailto:[EMAIL PROTECTED]
> Sent: dinsdag 16 mei 2006 14:55
> To: Apache AXIS C User List
> Subject: RE: Crash in XercesHandler.cpp with & in response
>
> Hi,
>
> Ok, I can't see anything obviously wrong with your SOAP message ... I
> wouldn't expect the & to cause problems, as we have a passing
> testcase to check the correct encoding/decoding of this, and looking
> through the SVN history the code which handles encoding/decoding hasn't
> been touched since before the release of 1.5.
>
> I'm wondering if perhaps you're hitting a problem with the
> transport/parser interaction.
> I should have asked before, can you also include the HTTP headers, etc.
> so I can check if there are any content/chunk length issues here.
>
> Regards,
> Adrian
> ___
> Adrian Dick ([EMAIL PROTECTED])
>
>
> "Iwan Tomlow" <[EMAIL PROTECTED]> wrote on 16/05/2006 10:01:03:
>
> > Sure, this is the on-the-wire message (in which I had to replace some
> > personal data for confidentiality).
> > The & in causes XercesHandler to parse the data in
> > 2 steps, and the 2nd call to XercesHandler::characters is causing
> > problems in the use of 'cp_PreviousNameOrValue'.
> >
> > Thanks for your assistan
RE: Crash in XercesHandler.cpp with & in response
Hi, Ok, I can't see anything obviously wrong with your SOAP message ... I wouldn't expect the & to cause problems, as we have a passing testcase to check the correct encoding/decoding of this, and looking through the SVN history the code which handles encoding/decoding hasn't been touched since before the release of 1.5. I'm wondering if perhaps you're hitting a problem with the transport/parser interaction. I should have asked before, can you also include the HTTP headers, etc. so I can check if there are any content/chunk length issues here. Regards, Adrian _______ Adrian Dick ([EMAIL PROTECTED]) "Iwan Tomlow" <[EMAIL PROTECTED]> wrote on 16/05/2006 10:01:03: > Sure, this is the on-the-wire message (in which I had to replace some > personal data for confidentiality). > The & in causes XercesHandler to parse the data in 2 > steps, and the 2nd call to XercesHandler::characters is causing problems > in the use of 'cp_PreviousNameOrValue'. > > Thanks for your assistance, > Iwan > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > > http://thenamespace";> > > 12345 > 104 > 03/11/2008 > 0 > 0 > 01/01/1975 > SOMEWHERE > XXBOOT & > BUTEIJN > 1234/999.999.999 ployerPhone> > THERE > AA > FIRST > 1 > CITY > XX > STREET 11 > AA > > LAST > XX > > xsi:nil="true"/> xsi:nil="true"/> > > > > > > -Original Message- > From: Adrian Dick [mailto:[EMAIL PROTECTED] > Sent: dinsdag 16 mei 2006 10:21 > To: Apache AXIS C User List > Subject: RE: Crash in XercesHandler.cpp with & in response > > Hi, > > As we've now excluded the illegal use of '&', it could be related to how > the SOAP message is being received, I know of some bugs fixed in 1.6 > which could cause similar problems to those you describe. > Is it possible for you to attach the "on-the-wire" SOAP/HTTP message > causing this problem? > > Thanks, > Adrian > ___ > Adrian Dick ([EMAIL PROTECTED]) > > > "Iwan Tomlow" <[EMAIL PROTECTED]> wrote on 15/05/2006 16:41:16: > > > Hm, sorry I didn't make this clear enough: when looking at the data > > over the wire, the ampersand is escaped correctly. > > The webservice is deployed with axis-java, so no problems there. My > > example should read BOOT & BUTEIJN. > > The & was already resolved by xerces when I copy/pasted the value > > to this e-mail, sorry for the confusion. > > > > So Xerces parser has no problems at all, but there seems to be a bug > > in the XercesHandler implementation in Axis. > > Btw, I have the problem with both Xerces 2.2.0 (as included in axis > > 1.5 release), and also when I build Axis 1.5 myself linked with Xerces > > > 2.7.0. > > > > I have not been able to use the 1.6 nightly build yet, and I would > > rather be able to quickly fix the production problem with a 1.5 patch > > first. > > > > Regards, > > Iwan > > > > -Original Message- > > From: Adrian Dick [mailto:[EMAIL PROTECTED] > > Sent: maandag 15 mei 2006 17:20 > > To: Apache AXIS C User List > > Subject: Re: Crash in XercesHandler.cpp with & in response > > > > Hi, > > > > > > Under the SOAP (and underlying XML) standards the ampersand character > > is reserved, so you are not permitted to use it within data. > > You will need to ensure any occurances are correctly encoded --- ie: > > '&' > > becomes "&". > > > > It looks quite likely the Xerces Parser is failing when it hits this > > invalid use of '&'. > > > > How is this XML data being produced? Are you using xsd:any -- in > which > > case you'll need to ensure this encoding takes place -- or are you > > seeing an error in the Axis serialization code, where this should be > > taking place on your behalf. > > > > Are you in a position to test if this problem is still present with > > the latest Axis 1.6 nightly builds? > > > > Regards, > > Adrian > > ___ > > Adrian Dick ([EMAIL PROTECTED]) > > > > > > "Iwan Tomlow" <[EMAIL PROTECTED]> wrote on 15/05/2006 13:34:04: > > > > > Hi all, > > > > > > I'm using the A
RE: AxisEngineException
Hi,
I'm surprised you're having problems using the same stub twice. We have
numerous testcases which re-use the same stub object, including mixed
operations.
Looking at the trace, it would appear the second call didn't receive the
expected SOAP message.
Can you use TCPmon, or similiar, to capture the "on-the-wire" messages when
making these two subsequent calls?
A copy of your WSDL would also be helpful, so we can ensure the correct
names and values are being used throughout.
Regards,
Adrian
_______
Adrian Dick ([EMAIL PROTECTED])
"Cheng, John" <[EMAIL PROTECTED]> wrote on 15/05/2006 16:26:36:
> Adrian,
>
> Thanks for the help! I found the problem after enable the trace. It was
> due to my searching path did not include the directory where
> AxisXMLParserXerces.dll is located. My testing sample is working now.
> But I found another interesting problem with the library, though. I have
> a piece of code looks like this:
>
> ServiceSoap
> s("http://localhost/WebService1/service.asmx";);
> xsd__string str = s.HelloWorld();
> int x = s.Add(12, 24);
>
> My experience with other web service client code told me the two
> sequential calls should work. But it's not working here. Only the first
> call works. The second one will give an AxisGenException. After I switch
> my calling sequence, it's the same. The second one doesn't work. Why is
> there such limitation? I attached my log file this time.
>
> Thanks!
>
> John Cheng
>
>
> -Original Message-
> From: Adrian Dick [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 10, 2006 3:06 AM
> To: Apache AXIS C User List
> Subject: Re: AxisEngineException
>
> Hi,
>
> Have you tried turning on trace? ( See
> http://ws.apache.org/axis/cpp/TraceGuide.html#enablingRuntimeTrace and
> possibly also
> http://ws.apache.org/axis/cpp/TraceGuide.html#enablingStartupTrace )
> This may give you some pointers to the problem, if there's nothing
> obvious
> you can post your tracefile here so we can look for any problems.
>
> As for project files, see my response to another recent question here:
> http://marc.theaimsgroup.com/?l=axis-c-user&m=114724798004149&w=2
>
> Regards,
> Adrian
> ___
> Adrian Dick ([EMAIL PROTECTED])
>
>
> "Cheng, John" <[EMAIL PROTECTED]> wrote on 09/05/2006 19:10:32:
>
> > Hi,
> > I am having a problem to make a C++ app to call a .NET C# web
> > service, using Axis C++. The service was implemented and tested
> > separately. I generated the client side code using WSDL2Ws and
> > included it with my application (on windows platform). But when
> > running the application I get AxisEngineException while
> > instantiating the generated class. There is no other information,
> > and I could not figure it out base on the document. I also tried to
> compile
> > the distributed project vc\Distribution.sln and vc\AxisDevelopment.
> > sln, hope to get a debug version of axis_client.lib. But it
> > complains some files can not be found, for example:
> > src\common\AxisException.cpp is not in the package. Any help?
> > Thanks!
> > John Cheng
> [attachment "AxisClientLog.my.zip" deleted by Adrian Dick/UK/IBM]
RE: Crash in XercesHandler.cpp with & in response
Hi, As we've now excluded the illegal use of '&', it could be related to how the SOAP message is being received, I know of some bugs fixed in 1.6 which could cause similar problems to those you describe. Is it possible for you to attach the "on-the-wire" SOAP/HTTP message causing this problem? Thanks, Adrian _______ Adrian Dick ([EMAIL PROTECTED]) "Iwan Tomlow" <[EMAIL PROTECTED]> wrote on 15/05/2006 16:41:16: > Hm, sorry I didn't make this clear enough: when looking at the data over > the wire, the ampersand is escaped correctly. > The webservice is deployed with axis-java, so no problems there. My > example should read BOOT & BUTEIJN. > The & was already resolved by xerces when I copy/pasted the value to > this e-mail, sorry for the confusion. > > So Xerces parser has no problems at all, but there seems to be a bug in > the XercesHandler implementation in Axis. > Btw, I have the problem with both Xerces 2.2.0 (as included in axis 1.5 > release), and also when I build Axis 1.5 myself linked with Xerces > 2.7.0. > > I have not been able to use the 1.6 nightly build yet, and I would > rather be able to quickly fix the production problem with a 1.5 patch > first. > > Regards, > Iwan > > -Original Message- > From: Adrian Dick [mailto:[EMAIL PROTECTED] > Sent: maandag 15 mei 2006 17:20 > To: Apache AXIS C User List > Subject: Re: Crash in XercesHandler.cpp with & in response > > Hi, > > > Under the SOAP (and underlying XML) standards the ampersand character is > reserved, so you are not permitted to use it within data. > You will need to ensure any occurances are correctly encoded --- ie: > '&' > becomes "&". > > It looks quite likely the Xerces Parser is failing when it hits this > invalid use of '&'. > > How is this XML data being produced? Are you using xsd:any -- in which > case you'll need to ensure this encoding takes place -- or are you > seeing an error in the Axis serialization code, where this should be > taking place on your behalf. > > Are you in a position to test if this problem is still present with the > latest Axis 1.6 nightly builds? > > Regards, > Adrian > ___ > Adrian Dick ([EMAIL PROTECTED]) > > > "Iwan Tomlow" <[EMAIL PROTECTED]> wrote on 15/05/2006 13:34:04: > > > Hi all, > > > > I'm using the Axis C++ 1.5 in a production project, and we are > > experiencing problems when the response from the webservice contains > > ampersands in the xml-data, like BOOT & BUTEIJN. > > > > The generated Axis-client stub crashes (with 'Invalid Address > > specified to RtlFreeHeap' in MCVC6.0 debugger) on the following code > > in XercesHandler::characters > > >>> free(const_cast (cp_PreviousNameOrValue)); > >free(cp_CurrentNameOrValue); > > > > I found a jira-issue (AXISCPP-825) that seems to address this issue, > > but the reported fix (change free to delete[]) does not work for me, > > the result is the same. > > > > Does anyone have this issue, any hints? > > Strange thing: it appears everything works fine if a point my > > XMLParser in axiscpp.conf to the debug-library 'AxisXMLParser_D.dll' > > instead of the release-build, but I'm afraid that is just a > coincidence. > > > > Any help appreciated. > > > > Kind regards, > > Iwan Tomlow >
Re: Crash in XercesHandler.cpp with & in response
Hi, Under the SOAP (and underlying XML) standards the ampersand character is reserved, so you are not permitted to use it within data. You will need to ensure any occurances are correctly encoded --- ie: '&' becomes "&". It looks quite likely the Xerces Parser is failing when it hits this invalid use of '&'. How is this XML data being produced? Are you using xsd:any -- in which case you'll need to ensure this encoding takes place -- or are you seeing an error in the Axis serialization code, where this should be taking place on your behalf. Are you in a position to test if this problem is still present with the latest Axis 1.6 nightly builds? Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) "Iwan Tomlow" <[EMAIL PROTECTED]> wrote on 15/05/2006 13:34:04: > Hi all, > > I'm using the Axis C++ 1.5 in a production project, and we are > experiencing problems when the response from the webservice contains > ampersands in the xml-data, like BOOT & BUTEIJN. > > The generated Axis-client stub crashes (with 'Invalid Address specified > to RtlFreeHeap' in MCVC6.0 debugger) on the following code in > XercesHandler::characters > >>> free(const_cast (cp_PreviousNameOrValue)); >free(cp_CurrentNameOrValue); > > I found a jira-issue (AXISCPP-825) that seems to address this issue, but > the reported fix (change free to delete[]) does not work for me, the > result is the same. > > Does anyone have this issue, any hints? > Strange thing: it appears everything works fine if a point my XMLParser > in axiscpp.conf to the debug-library 'AxisXMLParser_D.dll' instead of > the release-build, but I'm afraid that is just a coincidence. > > Any help appreciated. > > Kind regards, > Iwan Tomlow
Re: Compilation under Visual Studio
Hi, The Visual Studio, and also Visual C++ 6.0, project files are no longer be actively maintained and supported, as we make use of the ANT based system due to its better portability. Hence, your seeing errors with missing files. You will find the Visual C++ 6.0 project files appear to have been kept up-to-date, so it may be possible for you to ask Visual Studio to upgrade these in someway. If you're in a position to update these project files and donate back the updates one of the commiters can see they're included in SVN. Many Thanks, Adrian _______ Adrian Dick ([EMAIL PROTECTED]) "Kovgan, Peter" <[EMAIL PROTECTED]> wrote on 08/05/2006 15:59:30: > I have found Visual Studio project files under VC. > I have following errors trying to compile AxisDevelopment.sln (last > version I checked out just now): > > Error 91 fatal error C1083: Cannot open source file: '..\.. > \src\soap\XercesHandler.cpp': No such file or directory c1xx > Error 261 fatal error C1083: Cannot open source file: '..\.. > \src\soap\SoapParserXerces.cpp': No such file or directory c1xx > Error 262 fatal error C1083: Cannot open source file: '..\.. > \src\soap\SoapParserExpat.cpp': No such file or directory c1xx > Error 429 fatal error C1083: Cannot open source file: '..\.. > \src\soap\SoapInputSource.cpp': No such file or directory c1xx > > Where are missed files??? > What happens here? > > Thanks.
Re: Deployment of Axis C++ & 2.0 vs. 1.6?
Hi, See some comments below. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) [EMAIL PROTECTED] wrote on 10/05/2006 07:50:16: > Hi, > We are thinking about using axis-c++ in one of our current projects. During > our analysis several questions about using Axis-c++ arose. It would be great > if you could help us with some of our issues or point us to further > information: > > - What is the suggested deployment scenario when using axis c++ in a > multi-threaded server environment. As we understand you offer the option of > using the mod interface to Apache or to use the SimpleAxisServer as a server > hull for the deployed web-services. When no web-server functionality is > needed which option is recommended. Or in other words: According to your > experience which option is the more stable one? Generally, we would recommend using the mod interfaces, using Apache as the HTTP server. As the name suggests, SimpleAxisServer is a simple server implementation, basically sufficient to allow testing of the Axis server engine, so we wouldn't recommend its use in a production environment - though its simplicity could be very useful for help you understand how to use the Axis Server engine within your own environment, it is also relatively simply to modify for non-HTTP transport mechanisms. > - In future versions of our product we might need to incorporate server > functionality that shares state between the client and the server. Is there > any support for session handling in the two deployment scenarios above? > - On the axis-c++ website you mention that you are planning to release the > final version 1.6 in mid march. Is 1.6 still developed or are you > concentrating all your efforts on axis 2? The 1.6 final release has been delayed while fixing some bugs found in the 1.6 Beta, but it should be available soon. > > Thanks in advance (and thanks for providing your great tool as well!!), > Markus > > -- > "Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ... > Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail
Re: AxisEngineException
Hi, Have you tried turning on trace? ( See http://ws.apache.org/axis/cpp/TraceGuide.html#enablingRuntimeTrace and possibly also http://ws.apache.org/axis/cpp/TraceGuide.html#enablingStartupTrace ) This may give you some pointers to the problem, if there's nothing obvious you can post your tracefile here so we can look for any problems. As for project files, see my response to another recent question here: http://marc.theaimsgroup.com/?l=axis-c-user&m=114724798004149&w=2 Regards, Adrian _______ Adrian Dick ([EMAIL PROTECTED]) "Cheng, John" <[EMAIL PROTECTED]> wrote on 09/05/2006 19:10:32: > Hi, > I am having a problem to make a C++ app to call a .NET C# web > service, using Axis C++. The service was implemented and tested > separately. I generated the client side code using WSDL2Ws and > included it with my application (on windows platform). But when > running the application I get AxisEngineException while > instantiating the generated class. There is no other information, > and I could not figure it out base on the document. I also tried to compile > the distributed project vc\Distribution.sln and vc\AxisDevelopment. > sln, hope to get a debug version of axis_client.lib. But it > complains some files can not be found, for example: > src\common\AxisException.cpp is not in the package. Any help? > Thanks! > John Cheng
Re: Fw: axis-c-1.6b-Win32-trace-bin
Hi, The AxisConfiguration tool was introduced after the Axis C++ 1.6Beta. Therefore it can only be found in the latest nightly builds. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Adrian Dick/UK/[EMAIL PROTECTED] wrote on 25/04/2006 15:33:51: > Forwarding to Axis C++ user mailing list. > > Regards, > Adrian > _______ > Adrian Dick ([EMAIL PROTECTED]) > > "Magnus Karlsson" <[EMAIL PROTECTED]> wrote on 25/04/2006 > 14:57:12: > > > Hi! > > > > I am planning to install the newest binary for Axis C++. In the > > installation manual there should exist a > > file "AxisConfiguration executable". I can't find it. > > Do you know where I can find it? > > > > Best regards > > Magnus Karlsson >
Fw: axis-c-1.6b-Win32-trace-bin
Forwarding to Axis C++ user mailing list. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) "Magnus Karlsson" <[EMAIL PROTECTED]> wrote on 25/04/2006 14:57:12: > Hi! > > I am planning to install the newest binary for Axis C++. In the > installation manual there should exist a > file "AxisConfiguration executable". I can't find it. > Do you know where I can find it? > > Best regards > Magnus Karlsson
Re: Fw: AIX 32 bit built
Hi,
I assume you actually took traced source. I think this is a mistake on
our part -- it doesn't really make sense to provide trace instrumented
source when the build scripts are capable of instrumenting anyway.
I shall tweak the packaging scripts to ensure future releases don't contain
instrumented source in the source bundle.
Regards,
Adrian
_______
Adrian Dick ([EMAIL PROTECTED])
"Antoine Galataud" <[EMAIL PROTECTED]> wrote on 12/04/2006
19:27:29:
> Hi,
>
> thanks a lot for your answer. Effectively, I built Axis with trace
> although it's a traced release (I took AIX-trace-bin, and called ant
> with buildWithTrace) ! I think it's my problem. I will try to test
> that asap, and give you some more feedback.
> The answers to the 2 other questions are respectively no and yes ;-)
>
> Many thanks again !
> 2006/4/12, Fred Preston <[EMAIL PROTECTED]>:
>
> Hi Antoine,
> I've been trying to replicate the problem that you are
> seeing on AIX and I am not having much success. We build and run
> all of the tests on AIX twice a day and do not experience the
> problem you are seeing. I have a couple of questions for you...
>
> Q. Are you running more two identical client application instances
> as this might account for why you are seeing double trace entries.
> Q. Have you somehow built a 'trace' build of Axis on a build that
> already had trace?
> Q. If you hard code the location of the library, it works? (e.g. ...
> // Obtain AXIS deployment path from environment, If not set, we will use
> // default deployment path. Note that default deployment path is the
NULL
> // string unless it is modified.
> sConfPath = getenv ("AXISCPP_DEPLOY"); < Q.
> Do you get the correct value from this getenv?
> if (sConfPath)
> setValue(0,AXCONF_AXISHOME,sConfPath);
>
> // get the value of the path
> // sConfPath = getAxisConfProperty(AXCONF_AXISHOME); < Q.
> What value is actually returned?
> )
>
> Its interesting that the first line of the double trace entry is
> usually correct, but the second is may be wrong. But, although the
> first appears correct, when you try to load the library, both fail.
>
> Regards,
>
> Fred Preston.
>
> "Antoine Galataud" <[EMAIL PROTECTED]>
> 04/04/2006 17:05
>
> Please respond to
> "Apache AXIS C User List"
>
> To
>
> "Apache AXIS C User List"
>
> cc
>
> Subject
>
> Re: AIX 32 bit built
edObject @205e6508
> [04/04/2006 17:52:20:230 DFT] 1 SharedObject < SharedObject @205e6508
> [04/04/2006 17:52:20:230 DFT] 1 RequestScopeHandlerPool >
> RequestScopeHandlerPool @205e6508
> [04/04/2006 17:52:20:230 DFT] 1 RequestScopeHandlerPool >
> RequestScopeHandlerPool @205e6508
> [04/04/2006 17:52:20:230 DFT] 1 RequestScopeHandlerPool <
> RequestScopeHandlerPool @205e6508
> [04/04/2006 17:52:20:230 DFT] 1 RequestScopeHandlerPool <
> RequestScopeHandlerPool @205e6508
> [04/04/2006 17:52:20:230 DFT] 1 SharedObject > SharedObject @205e6598
> [04/04/2006 17:52:20:230 DFT] 1 SharedObject > SharedObject @205e6598
> [04/04/2006 17:52:20:230 DFT] 1 SharedObject < SharedObject @205e6598
> [04/04/2006 17:52:20:230 DFT] 1 SharedObject < SharedObject @205e6598
> [04/04/2006 17:52:20:230 DFT] 1 SessionScopeHandlerPool >
> SessionScopeHandlerPool @205e6598
> [04/04/2006 17:52:20:230 DFT] 1 SessionScopeHandlerPool >
> SessionScopeHandlerPool @205e6598
> [04/04/2006 17:52:20:230 DFT] 1 SessionScopeHandlerPool <
> SessionScopeHandlerPool @205e6598
> [04/04/2006 17:52:20:231 DFT] 1 SessionScopeHandlerPool <
> SessionScopeHandlerPool @205e6598
> [04/04/2006 17:52:20:231 DFT] 1 SharedObject > SharedObject @205e6618
> [04/04/2006 17:52:20:231 DFT] 1 SharedObject > SharedObject @205e6618
> [04/04/2006 17:52:20:231 DFT] 1 SharedObject < SharedObject @205e6618
> [04/04/2006 17:52:20:231 DFT] 1 SharedObject < SharedObject @205e6618
> [04/04/2006 17:52:20:231 DFT] 1 DeserializerPool > DeserializerPool
@205e6618
> [04/04/2006 17:52:20:231 DFT] 1 DeserializerPool > DeserializerPool
@205e6618
> [04/04/2006 17:52:20:231 DFT] 1 DeserializerPool < DeserializerPool
@205e6618
> [04/04/2006 17:52:20:231 DFT] 1 DeserializerPool < DeserializerPool
@205e6618
> [04/04/2006 17:52:20:231 DFT] 1 SharedObject > SharedObject @205e6698
> [04/04/2006 17:52:20:231 DFT] 1 SharedObject > SharedObject @205e6698
> [04/04/2006 17:52:20:231 DFT] 1 SharedObject < SharedObject @205e6698
> [04/04/2006 17:52:20:231 DFT] 1 SharedObject < SharedObject @205e6698
> [04/04/2006 17:52:20:231 DFT] 1 SerializerPool > SerializerPo
Re: Known exception
Hi, You don't mention which version of Axis C++, but I shall assume the 1.6Beta for the moment. There is an error in the Calculator sample, on line 45 of Client.cpp the endpoint is incorrectly capitalized, Calculator should start with an upper case 'C'. This is why the server is returning an exception, as it is unable to find the corresponding service. As for getting the message: "Exception: Cannot deserialize the requested element." this is as a result of a problem in the stubs generated by WSDL2Ws for rpc/encoded WSDLs, I believe this may now be fixed in the nightly builds. Regards, Adrian _______ Adrian Dick ([EMAIL PROTECTED]) Atanacio Reyes <[EMAIL PROTECTED]> wrote on 08/04/2006 19:04:43: > Hi. > > I'm trying to deploy the calculator example, and on > client side, I have the next error. > > Exception: Cannot deserialize the requested element. > > the request soap message is: > > POST /axis/calculator HTTP/1.1 > Host: localhost:80 > Content-Type: text/xml; charset=UTF-8 > SOAPAction: "Calculator#add" > Content-Length: 405 > > > > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > > xmlns:ns1="http://localhost/axis/Calculator";> > xsi:type="xsd:int">20 > xsi:type="xsd:int">20 > > > > > And the response from simple_axis_server is: > > HTTP/1.1 200 OK > Server: Apache Axis C++/1.6.a > Connection: close > Content-Length: 345 > Content-Type: text/xml > > > > > > SOAP-ENV:Server > Unknown exception > areyes:80 > Unknown Exception has > occurred > > > > > > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com
Re: Fwd: Axis response n namespace in array
Hi, I agree that the SOAP response does look wrong. On just the element below, ns2 is declared twice (with different values), which makes for invalid SOAP, and looking at your response message ns2 was already declared on the parent element. http://www.w3.org/2001/06/soap-encoding"; xmlns:ns2=" http://gti-ia-zo.nl/ettTypes.xsd"; enc:arrayType="ns2:lineupType[0]"> I've checked your WSDL, and there's nothing obvious that would cause problems. I believe there may have been some fixes relating to namespaces applied since 1.5, so can you check if this is still a problem in the 1.6beta release? Regards, Adrian _______ Adrian Dick ([EMAIL PROTECTED]) "Roel Bindels" <[EMAIL PROTECTED]> wrote on 03/04/2006 21:22:31: > Hello listers, > > I'm having some troublems with the response message. I'm using axis > 1.5 as soap server and the Python ZSI library as a client. > There are some differences between the approach of the both > framework, but I was able to conquer those. > But now I'm getting a strange response from axis, wich I doubt to be correct. > > Can somebody please take a look at my wsdl and the response in my attachments. > > specially to the next line: > > http://www.w3. > org/2001/06/soap-encoding" xmlns:ns2=" http://gti-ia-zo.nl/ett > Types.xsd" enc:arrayType="ns2:lineupType[0]"> > > This tells me that there should be a lineupTypeArray in my wsdl > since this is pointing to ns2. I guess thet this should be an ampty > namspace and that the namspace of my wsdl should be ns3. > > Can somebody verify this or not > > greetings > Roel Bindels > [attachment "ett.wsdl" deleted by Adrian Dick/UK/IBM] [attachment > "getLineup.txt" deleted by Adrian Dick/UK/IBM]
Re: Axis C++ 1.6beta
Hi,
After your email yesterday, I've been looking into some of the issues you
highlight, sorry for not getting back sooner.
It would appear you've managed to find a hole in our recent work to improve
memory management, and myself and Fred are currently working on fixing the
generated stubs and beans for rpc/encoded WSDLs.
Of course, we're always pleased to receive fixes. The preferred manner for
providing fixes is as a context diff file.
If you are providing code fixes, it may be more appropriate to mail these
on the axis-c-dev mailing list. It's also worthwhile raising new Jira
issues (here: http://issues.apache.org/jira/browse/AXISCPP ) and attaching
the diff files.
Regards,
Adrian
___
Adrian Dick ([EMAIL PROTECTED])
Petr Cvachoucek <[EMAIL PROTECTED]> wrote on 30/03/2006 13:20:27:
> Hi again,
>
> I did some more investigations and seems successfully solved memory
> leaks. In general the source code generated by wsdl2ws tool needs to be
> extended and copy constructors and assignment operators must be added,
> and destructors must do cleanup. If someone is interested, I can send
> what is required to do.
>
> When testing the client and server (both axis c++ - generated by
> wsdl2ws, using apache2 on server side), I encountered other serious
> problems. The client crashes sometimes, I tried to find the reason and
> found bugs in the axis HTTP transport library. Client crashes sometimes
> when the server response is in chunked format (but not every time).
>
> The method HTTPTransport::getBytes() doesn't work in all cases, here is
> the part I needed to change to make it work correctly:
>
> (original position in HTTPTransport.cpp, line 767)
>
> case eSOAPMessageIsChunked:
> {
>if (m_GetBytesState == eSOAPMessageIsChunked)
>{
> if( m_iBytesLeft == 0)
> {
>getNextDataPacket( "No data available for next chunk size.");
> }
> m_iContentLength = getChunkSize();
>
> while( m_iContentLength + strlen(ASCII_S_CRLF) > m_iBytesLeft)
> {
>getNextDataPacket( "No data available for next chunk.");
> }
> if( m_iBytesLeft >= m_iContentLength + strlen(ASCII_S_CRLF))
> {
>nextChunk = m_strReceived.substr(
> m_iContentLength + strlen(ASCII_S_CRLF));
>
>m_strReceived = m_strReceived.substr( 0, m_iContentLength);
>m_iBytesLeft = m_iContentLength;
>
>if( peekChunkLength( nextChunk) == 0)
>{
> m_GetBytesState = eWaitingForHTTPHeader;
>}
> }
> else
> {
>nextChunk = "";
> }
>
> if( m_bMimeTrue)
> {
>processRootMimeBody();
>m_iBytesLeft = m_strReceived.length();
> }
>
> break;
>}
> }
>
> Also the method HTTPTransport::copyDataToParserBuffer() needs
modification:
>
> (original position in HTTPTransport.cpp, line 1722)
>
>
> bool HTTPTransport::copyDataToParserBuffer(char * pcBuffer, int *
> piSize, int iBytesToCopy)
> {
>bool bTransportInProgress = false;
>if( iBytesToCopy > 0)
>{
> int iToCopy = (*piSize < iBytesToCopy) ? *piSize : iBytesToCopy;
> strncpy( pcBuffer, m_strReceived.c_str(), iToCopy);
> m_iBytesLeft -= iToCopy;
> *piSize = iToCopy;
>
> if( m_iBytesLeft > 0)
> {
>m_strReceived = m_strReceived.substr( iToCopy);
> }
> else
> {
>m_strReceived = "";
> }
> bTransportInProgress = true;
>}
>else
>{
> *piSize = 0;
>}
>
>return bTransportInProgress;
> }
>
>
> The original behavior was pretty unstable, there were passed invalid
> data to xerces parser and then the xerces throws an exception. But seems
> it is not handled correctly in axis soap engine, because the axis engine
>crashes.
>
> I'll continue testing and let you know if I find some more bugs. Btw,
> does anybody know why it isn't possible to download previous releases of
> axis c++ ? (only 1.6beta is on http://www.apache.org/dist/ws/axis-c/).
> The 1.6beta is still pretty unstable in my opinion, why there is no
> earlier stable version available for download?
>
> Petr
Re: compilation problem
Hi,
It would appear I also don't have authority to do this within the Axis
(Java) project.
Maybe it will be easier for you to re-create against Axis C++, and close
the original?
Adrian
___
Adrian Dick ([EMAIL PROTECTED])
Olivier Destrebecq <[EMAIL PROTECTED]> wrote on 29/03/2006 19:56:26:
> I don't think i have privileges to do this. Could you move it for me?
>
> Best,
> Olivier Destrebecq
> [EMAIL PROTECTED]
>
>
>
> On Mar 28, 2006, at 10:50 PM, Adrian Dick wrote:
>
> > Ah!
> >
> > Wrong project within Jira ... you want this in the AXIS-C++ project
> > You should be able to select the issue then "Move this issue" from
> > the left
> > hand side.
> >
> > Regards,
> > Adrian
> > ___
> > Adrian Dick ([EMAIL PROTECTED])
> >
> > Olivier Destrebecq <[EMAIL PROTECTED]> wrote on 28/03/2006 22:56:40:
> >
> >> done: AXIS-2451
> >>
> >> Best,
> >> Olivier Destrebecq
> >> [EMAIL PROTECTED]
> >>
> >>
> >>
> >> On Mar 28, 2006, at 1:45 AM, Adrian Dick wrote:
> >>
> >>> Hi,
> >>>
> >>> I've just taken look at what is produced by WSDL2Ws from your WSDL,
> >>> and
> >>> there is a problem in WSDL2Ws.
> >>>
> >>> The generated deserialization methods are producing the wrong
> >>> code for
> >>> nillable simple-type elements.
> >>>
> >>> Can you raise an issue in Jira
> >>> (http://issues.apache.org/jira/browse/AXISCPP) with the component
> >>> of "WSDL
> >>> processing - RPC", and then attach your WSDL file to the issue.
> >>>
> >>> Many Thanks,
> >>> Adrian
> >>> _______
> >>> Adrian Dick ([EMAIL PROTECTED])
> >>>
> >>>
> >>> Olivier Destrebecq <[EMAIL PROTECTED]> wrote on 27/03/2006 19:25:52:
> >>>
> >>>>> Can you check the data type of the compilation element
> >>>>> contained by
> >>>>> the
> >>>>> param object?
> >>>>
> >>>>> here is how compilation is declared : xsd__boolean *compilation;
> >>>>
> >>>> Here is simplified WSDL that demonstrate the problem:
> >>>> [attachment "Kani.xml" deleted by Adrian Dick/UK/IBM] and the
> >>>> source
> >>>> code as it is generated on my machine:
> >>>> [attachment "Archive.zip" deleted by Adrian Dick/UK/IBM]
> >>>> Best,
> >>>> Olivier Destrebecq
> >>>> [EMAIL PROTECTED]
> >>>>
> >>>>
> >>>>
> >>>> On Mar 26, 2006, at 11:28 PM, Adrian Dick wrote:
> >>>>
> >>>>> Hi,
> >>>>>
> >>>>> I'm guessing the compilation problem is on the second line in the
> >>>>> snippet
> >>>>> your provide, ie:
> >>>>> param->compilation = *p_compilation;
> >>>>>
> >>>>> Can you check the data type of the compilation element
> >>>>> contained by
> >>>>> the
> >>>>> param object?
> >>>>>
> >>>>> It sounds to me as though the WSDL2Ws tooling hasn't correctly
> >>>>> processed
> >>>>> the WSDL for this element, resulting in inconsistent code.
> >>>>> If this does appear to be the case, can you please attach your
> >>>>> WSDL to
> >>>>> allow us to correctly re-create the problem.
> >>>>>
> >>>>> Thanks,
> >>>>> Adrian
> >>>>> ___
> >>>>> Adrian Dick ([EMAIL PROTECTED])
> >>>>>
> >>>>> Olivier Destrebecq <[EMAIL PROTECTED]> wrote on 24/03/2006
> >>>>> 23:29:00:
> >>>>>
> >>>>>> I downloaded axis 1.6b and am trying to build the client side
> >>>>>> of a
> >>>>>> web service. The source file get generated fine, I add the
> >>>>>> various
> >>>>>> path to my project an then try to build.
> >>>>>>
> >>>>>> I get a bunch of error in the deserialization functions:
> >>>>>> All of them along those lines:
> >>>>>>
> >>>>>>xsd__boolean* p_compilation = (pIWSDZ->getElementAsBoolean
> >>>>>> ("compilation",0));
> >>>>>>param->compilation = *p_compilation;
> >>>>>>
> >>>>>> error: cannot convert 'axiscpp::xsd__boolean' to
> >>>>>> 'axiscpp::xsd__boolean*' in assignment
> >>>>>>
> >>>>>> compilation is declared as like this in the class:
> >>>>>> xsd__boolean *
> >>>>>> compilation;
> >>>>>>
> >>>>>> So i don't really know what i should change to get it to
> >>>>>> generate the
> >>>>>> C++ file correctly.
> >>>>>> Note that I'm running on a mac, so maybe it has something to do
> >>>>>> with
> >>>>>> this.
> >>>>>>
> >>>>>> any idea appreciated
> >>>>>> Best,
> >>>>>> Olivier Destrebecq
> >>>>>> [EMAIL PROTECTED]
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >
>
Re: compilation problem
Ah!
Wrong project within Jira ... you want this in the AXIS-C++ project
You should be able to select the issue then "Move this issue" from the left
hand side.
Regards,
Adrian
_______
Adrian Dick ([EMAIL PROTECTED])
Olivier Destrebecq <[EMAIL PROTECTED]> wrote on 28/03/2006 22:56:40:
> done: AXIS-2451
>
> Best,
> Olivier Destrebecq
> [EMAIL PROTECTED]
>
>
>
> On Mar 28, 2006, at 1:45 AM, Adrian Dick wrote:
>
> > Hi,
> >
> > I've just taken look at what is produced by WSDL2Ws from your WSDL,
> > and
> > there is a problem in WSDL2Ws.
> >
> > The generated deserialization methods are producing the wrong code for
> > nillable simple-type elements.
> >
> > Can you raise an issue in Jira
> > (http://issues.apache.org/jira/browse/AXISCPP) with the component
> > of "WSDL
> > processing - RPC", and then attach your WSDL file to the issue.
> >
> > Many Thanks,
> > Adrian
> > ___
> > Adrian Dick ([EMAIL PROTECTED])
> >
> >
> > Olivier Destrebecq <[EMAIL PROTECTED]> wrote on 27/03/2006 19:25:52:
> >
> >>> Can you check the data type of the compilation element contained by
> >>> the
> >>> param object?
> >>
> >>> here is how compilation is declared : xsd__boolean *compilation;
> >>
> >> Here is simplified WSDL that demonstrate the problem:
> >> [attachment "Kani.xml" deleted by Adrian Dick/UK/IBM] and the source
> >> code as it is generated on my machine:
> >> [attachment "Archive.zip" deleted by Adrian Dick/UK/IBM]
> >> Best,
> >> Olivier Destrebecq
> >> [EMAIL PROTECTED]
> >>
> >>
> >>
> >> On Mar 26, 2006, at 11:28 PM, Adrian Dick wrote:
> >>
> >>> Hi,
> >>>
> >>> I'm guessing the compilation problem is on the second line in the
> >>> snippet
> >>> your provide, ie:
> >>> param->compilation = *p_compilation;
> >>>
> >>> Can you check the data type of the compilation element contained by
> >>> the
> >>> param object?
> >>>
> >>> It sounds to me as though the WSDL2Ws tooling hasn't correctly
> >>> processed
> >>> the WSDL for this element, resulting in inconsistent code.
> >>> If this does appear to be the case, can you please attach your
> >>> WSDL to
> >>> allow us to correctly re-create the problem.
> >>>
> >>> Thanks,
> >>> Adrian
> >>> ___
> >>> Adrian Dick ([EMAIL PROTECTED])
> >>>
> >>> Olivier Destrebecq <[EMAIL PROTECTED]> wrote on 24/03/2006 23:29:00:
> >>>
> >>>> I downloaded axis 1.6b and am trying to build the client side of a
> >>>> web service. The source file get generated fine, I add the various
> >>>> path to my project an then try to build.
> >>>>
> >>>> I get a bunch of error in the deserialization functions:
> >>>> All of them along those lines:
> >>>>
> >>>>xsd__boolean* p_compilation = (pIWSDZ->getElementAsBoolean
> >>>> ("compilation",0));
> >>>>param->compilation = *p_compilation;
> >>>>
> >>>> error: cannot convert 'axiscpp::xsd__boolean' to
> >>>> 'axiscpp::xsd__boolean*' in assignment
> >>>>
> >>>> compilation is declared as like this in the class: xsd__boolean *
> >>>> compilation;
> >>>>
> >>>> So i don't really know what i should change to get it to
> >>>> generate the
> >>>> C++ file correctly.
> >>>> Note that I'm running on a mac, so maybe it has something to do
> >>>> with
> >>>> this.
> >>>>
> >>>> any idea appreciated
> >>>> Best,
> >>>> Olivier Destrebecq
> >>>> [EMAIL PROTECTED]
> >>>>
> >>>>
> >>>>
> >>>
> >>
> >
>
Re: compilation problem
Hi,
I've just taken look at what is produced by WSDL2Ws from your WSDL, and
there is a problem in WSDL2Ws.
The generated deserialization methods are producing the wrong code for
nillable simple-type elements.
Can you raise an issue in Jira
(http://issues.apache.org/jira/browse/AXISCPP) with the component of "WSDL
processing - RPC", and then attach your WSDL file to the issue.
Many Thanks,
Adrian
_______
Adrian Dick ([EMAIL PROTECTED])
Olivier Destrebecq <[EMAIL PROTECTED]> wrote on 27/03/2006 19:25:52:
> > Can you check the data type of the compilation element contained by
> > the
> > param object?
>
> > here is how compilation is declared : xsd__boolean *compilation;
>
> Here is simplified WSDL that demonstrate the problem:
> [attachment "Kani.xml" deleted by Adrian Dick/UK/IBM] and the source
> code as it is generated on my machine:
> [attachment "Archive.zip" deleted by Adrian Dick/UK/IBM]
> Best,
> Olivier Destrebecq
> [EMAIL PROTECTED]
>
>
>
> On Mar 26, 2006, at 11:28 PM, Adrian Dick wrote:
>
> > Hi,
> >
> > I'm guessing the compilation problem is on the second line in the
> > snippet
> > your provide, ie:
> > param->compilation = *p_compilation;
> >
> > Can you check the data type of the compilation element contained by
> > the
> > param object?
> >
> > It sounds to me as though the WSDL2Ws tooling hasn't correctly
> > processed
> > the WSDL for this element, resulting in inconsistent code.
> > If this does appear to be the case, can you please attach your WSDL to
> > allow us to correctly re-create the problem.
> >
> > Thanks,
> > Adrian
> > ___
> > Adrian Dick ([EMAIL PROTECTED])
> >
> > Olivier Destrebecq <[EMAIL PROTECTED]> wrote on 24/03/2006 23:29:00:
> >
> >> I downloaded axis 1.6b and am trying to build the client side of a
> >> web service. The source file get generated fine, I add the various
> >> path to my project an then try to build.
> >>
> >> I get a bunch of error in the deserialization functions:
> >> All of them along those lines:
> >>
> >>xsd__boolean* p_compilation = (pIWSDZ->getElementAsBoolean
> >> ("compilation",0));
> >>param->compilation = *p_compilation;
> >>
> >> error: cannot convert 'axiscpp::xsd__boolean' to
> >> 'axiscpp::xsd__boolean*' in assignment
> >>
> >> compilation is declared as like this in the class: xsd__boolean *
> >> compilation;
> >>
> >> So i don't really know what i should change to get it to generate the
> >> C++ file correctly.
> >> Note that I'm running on a mac, so maybe it has something to do with
> >> this.
> >>
> >> any idea appreciated
> >> Best,
> >> Olivier Destrebecq
> >> [EMAIL PROTECTED]
> >>
> >>
> >>
> >
>
Re: Failed to call "delayed quotes" sample web service by Axis C++ and VC 6
Hi, Can you raise an issue here: http://issues.apache.org/jira/browse/AXISCPP For this particular problem choose the "WSDL processing - RPC" component The SOAP request and response is message going "on-the-wire" between the client and server. You can capture this using a tcp/ip monitor tool. Such a tool is available within /lib/axisjava/axis.jar. To run: java -cp /lib/axisjava/axis.jar org.apache.axis.utils.tcpmon Once running configure it to listen on a port and forward to your server. You will then need to modify your client application to talk to that local port (using the setEndPoint() method on your generated Stub) When you run the client the tcp monitor tool will show the SOAP/HTTP request and response messages. Copy these into a text file and attach to the Jira issue. Many Thanks Adrian ___ Adrian Dick ([EMAIL PROTECTED]) "Bo Xie" <[EMAIL PROTECTED]> wrote on 27/03/2006 12:06:11: > The WSDL file is > http://services.xmethods.net/soap/urn:xmethods-delayed-quotes.wsdl. > You can download it. > The trace file was attached in former email. > What's "SOAP request/response"? Sorry I am a Axis newbie and don't > know how to get this attachment. > > Best Regards, > Xie Bo > > On 3/27/06, Adrian Dick <[EMAIL PROTECTED]> wrote: > > Can you please raise a Jira issue for this, and attach: > > - WSDL file > > - SOAP request/response > > - trace file
Re: Failed to call "delayed quotes" sample web service by Axis C++ and VC 6
Hi,
Well, looking through your trace and comparing with some of our existing
testcases, I believe you may have found a problem in the code generated by
WSDL2Ws for handling faults.
In short summary:
- the stub checks the received SOAP message for the expected response, and
doesn't find it, so throws an AxisException
- this is caught by the stub code, which then checks for a SOAP fault
- the fault is then deserialized
- the stub then throws the AxisException (from checkMessage) to the client
Application, rather than the deserialized SOAP fault.
Having done a quick check of the testcases, this is only a problem for
rpc/encoded WSDLs, doc/literal appears to do the correct thing.
Can you please raise a Jira issue for this, and attach:
- WSDL file
- SOAP request/response
- trace file
As an aside, the particular fault you were experience had the faultstring:
"electric.directory.DirectoryException: cannot automatically create
subdirectory http:" if that's of any assistance, you can check the SOAP
response message for the complete response.
Regards,
Adrian
___
Adrian Dick ([EMAIL PROTECTED])
"Bo Xie" <[EMAIL PROTECTED]> wrote on 27/03/2006 09:26:39:
> Hi Adrian,
>
> Thank you very much for your reply! Attached please find the trace log.
>
> Best Regards,
> Xie, Bo
>
> On 3/27/06, Adrian Dick <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > Here are a few items that will aid us in understanding the problem
you're
> > experiencing.
> > - Provide exception handling round the use of the web service, are you
> > having an AxisException thrown? If so, can you capture the message
using
> > exception.what().
> > - Enable engine trace ( see step 4 of
> > http://ws.apache.org/axis/cpp/install-guide.html#Installing_Client for
> > detail on setting configuration)
> >
> > Thanks,
> > Adrian
> > ___
> > Adrian Dick ([EMAIL PROTECTED])
> >
> >
> > "Bo Xie" <[EMAIL PROTECTED]> wrote on 27/03/2006 08:17:28:
> >
> > > Hi,
> > >
> > > I tried to build SOAP C++ Windows Client to call "delayed quotes" web
> > > service, but failed. Following are steps:
> > > 1. Generate .hpp/.cpp
> > > --
> > > E:\temp\TestAxis>java -classpath .\wsdl2ws.jar;.\commons-logging.
> > > jar;.\jaxrpc.ja
> > >
> >
r;.\saaj.jar;.\wsdl4j.jar;.\wsdl2ws.jar;.\axis.jar;.\commons-discovery.jar
> > > org.apache.axis.wsdl.wsdl2ws.WSDL2Ws
> > > http://services.xmethods.net/soap/urn:xmethods-delayed-quotes.wsdl
> > > -lc++ -sclient
> > >
> > > Code generation completed.
> > > --
> > > 2. TestAxis.cpp
> > > --
> > > #include "stdafx.h"
> > > #include "StockQuotePortType.hpp"
> > >
> > > int main(int argc, char* argv[])
> > > {
> > >StockQuotePortType s;
> > >float f=s.getQuote("IBM");
> > >printf("The quote is %f\n",f);
> > >return 0;
> > > }
> > > --
> > >
> > > 3. When I debug the TestAxis project, it will throw an exception
> > > "Unhandled exception in TestAxis.exe: 0xC005: Access Violation"
in
> > > Line 62 of StockQuotePortType.cpp
> > > --Line 62--
> > > if( AXIS_SUCCESS == m_pCall->checkMessage(
> > > "getQuoteResponse1","http://www.themindelectric.com/wsdl/net.
> > > xmethods.services.stockquote.StockQuote/"))
> > > -
> > >
> > > If you want the TestAxis VC project, please let me know.
> > >
> > > Any suggestions are welcome and appreciated!
> > >
> > > Best Regards,
> > >
> > > Xie, Bo
> >
> >
> [attachment "AxisLogClient.txt" deleted by Adrian Dick/UK/IBM]
Re: Runtime problem getting Calculator sample to work
Hi, Have you tried any of the following, which may aid in understanding the exact problem: - Testing with an Axis C++ client? - Testing against a C# server? -- and comparing the SOAP/HTTP messages for any differences - Using the latest Axis C++ 1.6 Beta -- it's has had a lot of stability and memory improvements since 1.5 final, in addition to a number of other fixes and some new function. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) "Gabriel Malik" <[EMAIL PROTECTED]> wrote on 25/03/2006 17:51:32: > Hi, > > I'm trying to get the sample CalculatorDoc to work. Both C# client and C++ > server code are generated from the CalculatorDoc.wsdl. (please see below for > details) Both builds went successfully. However, when I run the client, > calling all the methods, namely add, sub, mul and div, they all return zero, > but using tcpMon I can see that the answers are correct in the SOAP > messages. Did I miss any setup procedure? This sounds like a > deserialization problem on the C# client side, do I need to do anything > special? > > Server: > Axis C++ 1.5 (Final) > > Client: > Microsoft Visual Studio 2003 (C#) > .NET Framework 1.1 SP1 > > and I also tried (with the same result) > > Microsoft Visual Studio 2005 (C#) > .NET Framework 2.0 > > Thank you in advance, > Gabe Malik > > _ > Don’t just search. Find. Check out the new MSN Search! > http://search.msn.click-url.com/go/onm00200636ave/direct/01/ >
Re: Failed to call "delayed quotes" sample web service by Axis C++ and VC 6
Hi,
Here are a few items that will aid us in understanding the problem you're
experiencing.
- Provide exception handling round the use of the web service, are you
having an AxisException thrown? If so, can you capture the message using
exception.what().
- Enable engine trace ( see step 4 of
http://ws.apache.org/axis/cpp/install-guide.html#Installing_Client for
detail on setting configuration)
Thanks,
Adrian
___
Adrian Dick ([EMAIL PROTECTED])
"Bo Xie" <[EMAIL PROTECTED]> wrote on 27/03/2006 08:17:28:
> Hi,
>
> I tried to build SOAP C++ Windows Client to call "delayed quotes" web
> service, but failed. Following are steps:
> 1. Generate .hpp/.cpp
> --
> E:\temp\TestAxis>java -classpath .\wsdl2ws.jar;.\commons-logging.
> jar;.\jaxrpc.ja
>
r;.\saaj.jar;.\wsdl4j.jar;.\wsdl2ws.jar;.\axis.jar;.\commons-discovery.jar
> org.apache.axis.wsdl.wsdl2ws.WSDL2Ws
> http://services.xmethods.net/soap/urn:xmethods-delayed-quotes.wsdl
> -lc++ -sclient
>
> Code generation completed.
> --
> 2. TestAxis.cpp
> --
> #include "stdafx.h"
> #include "StockQuotePortType.hpp"
>
> int main(int argc, char* argv[])
> {
>StockQuotePortType s;
>float f=s.getQuote("IBM");
>printf("The quote is %f\n",f);
>return 0;
> }
> --
>
> 3. When I debug the TestAxis project, it will throw an exception
> "Unhandled exception in TestAxis.exe: 0xC005: Access Violation" in
> Line 62 of StockQuotePortType.cpp
> --Line 62--
> if( AXIS_SUCCESS == m_pCall->checkMessage(
> "getQuoteResponse1","http://www.themindelectric.com/wsdl/net.
> xmethods.services.stockquote.StockQuote/"))
> -
>
> If you want the TestAxis VC project, please let me know.
>
> Any suggestions are welcome and appreciated!
>
> Best Regards,
>
> Xie, Bo
RE: Building on Linux
Hmm,
This is most unusual.
We can see the scripts have correctly detected your OS, yet we still see an
issue with the SolarisLinker.
The only time I've seen this problem is when using versions of ant-contrib
and cpptasks that differ from our recommended versions, yet you claim to be
using those versions.
Is it possible you have an alternate version being picked up somehow?
Regards,
Adrian
___
Adrian Dick ([EMAIL PROTECTED])
"Lei Tang" <[EMAIL PROTECTED]> wrote on 24/03/2006 14:59:42:
> Adrian,
>
> I run the "ant -v initialize" and the top a few lines from the output
> are:
>
> Apache Ant version 1.6.2 compiled on May 23 2005
> Buildfile: build.xml
> Detected Java version: 1.5 in: /usr/java/jdk1.5.0_06/jre
> Detected OS: Linux
>
> At the end the output are:
>
> pre-init:
> [property] Loading /usr/local/axiscpp_src/c/build/version.properties
>
> set-platform-specifics:
> [property] Loading
> /usr/local/axiscpp_src/c/build/build.Linux.properties
> [property] Loading
> /usr/local/axiscpp_src/c/build/build.common.properties
> Override ignored for property server.simpleaxisserver
> Property ${env.APACHE_HOME} has not been set
> Property ${env.XML4C_HOME} has not been set
> Override ignored for property server.apache2
> Override ignored for property server.apache1
> Property ${env.OPENSSL_HOME} has not been set
> Override ignored for property HTTP.SSLChannel
> Property ${env.OPENSSL_HOME} has not been set
>
> checkIfDebug:
> Skipped because property 'debug' not set.
>
> initialize:
>
> BUILD SUCCESSFUL
> Total time: 2 seconds
>
> I also attached the whole output in a file.
>
> Thanks,
>
> Lei
>
> -Original Message-
> From: Adrian Dick [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 24, 2006 3:35 AM
> To: Apache AXIS C User List
> Subject: Re: Building on Linux
>
> Hi,
>
> Have you tried running "ant -v initialize" as suggested in the original
> discussion.
>
> This will help us determine what ANT/Java and our scripts _think_ you're
> running. It is possible we don't correctly detect the particular Linux
> variant you're using.
>
> Thanks,
> Adrian
> ___
> Adrian Dick ([EMAIL PROTECTED])
>
>
> "Lei Tang" <[EMAIL PROTECTED]> wrote on 24/03/2006 03:50:45:
>
> > When I built from source on Linux I got errors:
> >
> > BUILD FAILED
> > /usr/local/axiscpp_src/c/build.xml:245: The following error occurred
> > while execu ting this line:
> > /usr/local/axiscpp_src/c/build.xml:233: The following error occurred
> > while execu ting this line:
> > /usr/local/axiscpp_src/c/build.xml:96: The following error occurred
> > while execut ing this line:
> > /usr/local/axiscpp_src/c/build/buildClient.xml:23: SolarisLinker
> > doesn't denote a ProcessorDef
> >
> > I installed the following on my Linux Fedora Core 4 machine:
> > Ant: 1.6.2
> > Ant-contrib: 0.6
> > CppTasks: 1.0b3
> > Java: 1.5
> >
> > I found the same problem at
> > http://marc.theaimsgroup.com/?l=axis-c-user&m=112169616401422
> > Does anybody know how to solve this issue?
> >
> > Lei
>
> [attachment "ant_output.txt" deleted by Adrian Dick/UK/IBM]
Re: Ask for step-by-step guide to call "delayed quotes"
Hi,
You will find step-by-step instructions, based on the Calculator sample
WSDL here: http://ws.apache.org/axis/cpp/clientuser-guide.html
Regards,
Adrian
___
Adrian Dick ([EMAIL PROTECTED])
"Bo Xie" <[EMAIL PROTECTED]> wrote on 26/03/2006 17:25:23:
> Hi,
>
> I am a AXIS C++ newbie. Could you please tell me how to use AXIS C++
> to call
"http://services.xmethods.net/soap/urn:xmethods-delayed-quotes.wsdl";?
> Thank you!
>
> Best Regards,
> Xie, Bo
>
> PS. Following is a step-by-step guide to call "delayed quotes" thru
gSOAP:
> -
> 0. Download gsoap_linux_2.7.6e.tar.gz
>
> 1. Write main program quote.c
>
> #include "soapH.h" /* include generated proxy and SOAP support */
>
> int main(int argc, char **argv)
> { struct soap soap;
> float q;
> char *sym;
> if (argc > 1)
> sym = argv[1];
> else
> { fprintf(stderr, "Usage: quote \n");
> return -1;
> }
> soap_init(&soap);
> if (soap_call_ns1__getQuote(&soap,
> "http://services.xmethods.net/soap";, NULL, sym, q) == 0)
> printf("\nCompany - %sQuote - %f\n", sym, q);
> else
> soap_print_fault(&soap, stderr);
> return 0;
> }
>
> /* The namespace mapping table is required and associates namespace
> prefixes with namespace names: */
> struct Namespace namespaces[] =
> {
> {"SOAP-ENV", "http://schemas.xmlsoap.org/soap/envelope/"},/*
> MUST be first */
> {"SOAP-ENC", "http://schemas.xmlsoap.org/soap/encoding/"},/*
> MUST be second */
> {"xsi", "http://www.w3.org/1999/XMLSchema-instance"}, /*
> MUST be third */
> {"xsd", "http://www.w3.org/1999/XMLSchema"},
> {"ns1", "urn:xmethods-delayed-quotes"}, /* Method namespace URI
*/
> {NULL, NULL}
> };
>
>
> 2. Generate the SOAP Stub Routines
> wsdl2h -s -o quote.h
> http://services.xmethods.net/soap/urn:xmethods-delayed-quotes.wsdl
> soapcpp2 quote.h
> cp stdsoap2.h YOURDIRECTORY/
> cp stdsoap2.cpp YOURDIRECTORY/
>
> 3. Compile Your Client App
> g++ -o quote quote.c soapC.cpp soapClient.cpp stdsoap2.cpp
>
> 4. Try it Out
> ./quote IBM
> Company - IBMQuote - 82.870003
> -
Re: compilation problem
Hi,
I'm guessing the compilation problem is on the second line in the snippet
your provide, ie:
param->compilation = *p_compilation;
Can you check the data type of the compilation element contained by the
param object?
It sounds to me as though the WSDL2Ws tooling hasn't correctly processed
the WSDL for this element, resulting in inconsistent code.
If this does appear to be the case, can you please attach your WSDL to
allow us to correctly re-create the problem.
Thanks,
Adrian
_______
Adrian Dick ([EMAIL PROTECTED])
Olivier Destrebecq <[EMAIL PROTECTED]> wrote on 24/03/2006 23:29:00:
> I downloaded axis 1.6b and am trying to build the client side of a
> web service. The source file get generated fine, I add the various
> path to my project an then try to build.
>
> I get a bunch of error in the deserialization functions:
> All of them along those lines:
>
>xsd__boolean* p_compilation = (pIWSDZ->getElementAsBoolean
> ("compilation",0));
>param->compilation = *p_compilation;
>
> error: cannot convert 'axiscpp::xsd__boolean' to
> 'axiscpp::xsd__boolean*' in assignment
>
> compilation is declared as like this in the class: xsd__boolean *
> compilation;
>
> So i don't really know what i should change to get it to generate the
> C++ file correctly.
> Note that I'm running on a mac, so maybe it has something to do with
> this.
>
> any idea appreciated
> Best,
> Olivier Destrebecq
> [EMAIL PROTECTED]
>
>
>
Re: AIX 32 bit built
Hi, At the start of the log file, is a snapshot of various environment variables, including AXISCPP_DEPLOY, which may be worth checking. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) "Antoine Galataud" <[EMAIL PROTECTED]> wrote on 24/03/2006 10:31:07: > Hi ! > > I suceeded in compiling Axis with xerces 2.7.0 version. It worked just fine. > > Now I'm getting issues at startup, with simple_axis_server or with > apache module. The strange thing is that it seems configuration file > parser get correctly the values, but then the values are corrupted > with something and it produces strange ascii chars (see log output > below). Then, it can't load any lib. > I'm also wondering if it finds correctly the > $AXISCPP_DEPLOY/etc/axiscpp.conf file (it could explain that it > can't find any library), because if you look at the logs, it > outputed a wrong configuration value for log files location (though > I set another value in the axiscpp.conf file) > > What could be the reasons ? > > Thanks > > logs : > [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > AxisConfig @205c7ee8, > 205c5848 > [205C5848F008BCC4F008BCD4] < > \XH> > [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > AxisConfig @205c7ee8, > 205c5848 > [205C5848F008BCC4F008BCD4] < > \XH> > [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty > @205c5848,[] <> > [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty > @205c5848,[] <> > [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty > @205c5848,@1 > [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty > @205c5848,@1 "¾ïÞ" > [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty > @205c5848,[0001] <> > [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty > @205c5848,[0001] <> > [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty > @205c5848,@2 "/usr/local/axiscpp_deploy/log/AxisLog" > [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty > @205c5848,@3 "Kÿÿä‚'" > [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty > @205c5848,[0002] <> > [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty > @205c5848,[0002] <> > [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty > @205c5848,@2 "/usr/local/axiscpp_deploy/log/AxisClientLog" > [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty > @205c5848,@3 "Kÿÿä‚'" > [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty > @205c5848,[0003] <> > [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty > @205c5848,[0003] <> > [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty > @205c5848,@1 > [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty > @205c5848,@1 "¾ïÞ" > [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty > @205c5848,[0004] <> > [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty > @205c5848,[0004] <> > [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty > @205c5848,@1 > [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty > @205c5848,@1 "¾ïÞ" > [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty > @205c5848,[0005] <> > [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty > @205c5848,[0005] <> > [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty > @205c5848,@2 "libhttp_transport.a" > [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty > @205c5848,@3 "Kÿÿä‚'" > [24/03/2006 11:26:51:271 NFT] 1 AxisConfig > getAxisConfProperty > @205c5848,[0006] <> > [24/03/2006 11:26:51:271 NFT] 1 AxisConfig > getAxisConfProperty > @205c5848,[0006] <> > [24/03/2006 11:26:51:271 NFT] 1 AxisConfig < getAxisConfProperty > @205c5848,@1 > [24/03/2006 11:26:51:271 NFT] 1 AxisConfig < getAxisConfProperty > @205c5848,@1 "¾ïÞ" > [24/03/2006 11:26:51:271 NFT] 1 AxisConfig > getAxisConfProperty > @205c5848,[0007] <> > [24/03/2006 11:26:51:271 NFT] 1 AxisConfig > getAxisConfProperty > @205c5848,[0007] <> > [24/03/2006 11:26:51:271 NFT] 1 AxisConfig < getAxisConfProperty > @205c
Re: Building on Linux
Hi, Have you tried running "ant -v initialize" as suggested in the original discussion. This will help us determine what ANT/Java and our scripts _think_ you're running. It is possible we don't correctly detect the particular Linux variant you're using. Thanks, Adrian _______ Adrian Dick ([EMAIL PROTECTED]) "Lei Tang" <[EMAIL PROTECTED]> wrote on 24/03/2006 03:50:45: > When I built from source on Linux I got errors: > > BUILD FAILED > /usr/local/axiscpp_src/c/build.xml:245: The following error occurred > while execu > ting this line: > /usr/local/axiscpp_src/c/build.xml:233: The following error occurred > while execu > ting this line: > /usr/local/axiscpp_src/c/build.xml:96: The following error occurred > while execut > ing this line: > /usr/local/axiscpp_src/c/build/buildClient.xml:23: SolarisLinker doesn't > denote > a ProcessorDef > > I installed the following on my Linux Fedora Core 4 machine: > Ant: 1.6.2 > Ant-contrib: 0.6 > CppTasks: 1.0b3 > Java: 1.5 > > I found the same problem at > http://marc.theaimsgroup.com/?l=axis-c-user&m=112169616401422 > Does anybody know how to solve this issue? > > Lei
Re: Java client array encoding causes troubles for AxisCPP service
Hi, Handling of arrays for rpc/encoded web services is a suprisingly complex problem. The SOAP spec provides several different, but apparently equivalent, techniques. One of which is that employed by Axis C++ serialiation, another of which is that used by Axis Java. Regrettably, it would appear the AxisCPP deserializer doesn't handle all the variations. Can you raise a Jira issue for this, including the SOAP messages you give below. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) "Jonathan G Beakley \(beakley\)" <[EMAIL PROTECTED]> wrote on 20/03/2006 15:54:59: > I have noticed an inconsistency in the encoding of arrays by Axis Java > clients (created using WSDL2Java) and AxisCPP clients (created using > WSDL2Ws), and I was hoping someone could give me some advice. > > In short, I have the following RPC/encoded WSDL snippet that defines the > array: > > > http://www.w3.org/2001/XMLSchema"; > targetNamespace="http://localhost/axis/csaapi/xsd";> > http://schemas.xmlsoap.org/soap/encoding/"/> > > > >wsdl:arrayType="int[]"/> > > > > > > > When I create and run the AxisCPP client, it generates XML that uses > "" to denote the elements in the array: > > > xmlns:ns1="http://localhost/axis/csaapi";> > 0 > xmlns:enc="http://www.w3.org/2001/06/soap-encoding"; > enc:arrayType="xsd:int[9]"> > 1 > 2 > 3 > > > > > My AxisCPP service handles this just fine. > > BUT, my Java client generates XML that doesn't use the "" > construct, and it causes my CPP service to fail to parse the data. > Here's the Java XML: > > > > soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; > xmlns:ns1="http://localhost/axis/csaapi";> > 0 >xsi:type="soapenc:Array" > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";> > 1 > 2 > 3 > > > > > Could someone give me advice on the best way to handle this? Note that > I've already turned the MULTIREF option off to fix a different set of > problems. I'd prefer to keep the RPC/Encoded style if at all possible. > > Thank you very much in advance! > > -Jonathan Beakley > [EMAIL PROTECTED]
Re: Application, Session or Request scope
Hi, There is already a mechanism in place to do this. As part of WrapperClassHandler, from which the generated wrapper class is inherited, there are the init and fini methods. These methods are called respectively as the service library is loaded (ie: first invocation of service) and unloaded (ie: server shutdown). As these methods are virtual, you can override these within the generated wrapper class, to do the initialization and clearup activities you require. One word of warning, although this has been designed to work in this manner, it hasn't (so far) been tested. Please let us know how you get on with trying this. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) "Antoine Galataud" <[EMAIL PROTECTED]> wrote on 21/03/2006 12:43:45: > > Sorry, I haven't been really clear with what I wanted to do. I'll > try to clarify my thoughts a little : > > I get a web service library, that handles the web service technical > part and access to business objects. But my business part is heavy > to initialize, and I want to do it only once, so when a first > request come to the web service, the back end service starts and > replys, then any other request doesn't involve a back end service start. > > So what I want to do is, as axis java does, define an application > scope for the web service and get the service running until container stops. > 2006/3/21, John Hawkins < [EMAIL PROTECTED]>: > > Antoine, > > Can I clarify what you're trying to do here? Are you trying to have > a stateful session with a particular instance of a service i.e. the > same service gets called twice? Or pass context across the-wire on > subsequent uses of the same stub? > > thanks, > John. > > > > > "Antoine Galataud" <[EMAIL PROTECTED]> > 21/03/2006 09:27 > > Please respond to > "Apache AXIS C User List" > > To > > "Apache AXIS C User List" > > cc > > Subject > > Re: Application, Session or Request scope > > > > > Hi ! > > I've found no way to solve my scope issue for the moment, I'm still > looking for a way to do this (application scope, not handlers). > > Thanks for any idea ! > > 2006/3/16, Antoine Galataud < [EMAIL PROTECTED] >: > It doesn't work : > > in fact, I succeeded in getting a session scope, e.g I request the > service 2 times in the same main() client, but I can't have an > application scope. But I don't get the error I described in my > earlier mail, now it gives me nothing. And I'm talking about service > scope, I don't use any handler. > > Thanks for your answer > > 2006/3/16, John Hawkins <[EMAIL PROTECTED] >: > > I've just looked at this again and I'm not sure I understand your > question now! > > > If I look at your wsdd file it doesn't look correct to my thoughts > (is it the complete wsdd file?) e.g. this is a client sample wsdd file > > > > http://xml.apache.org/axis/wsdd/ " xlmns: > C="http//xml.apache.org.axis/wsdd/providers/c"> > > > > > > type="\samples\handlers\myClientHandler.dll"> name="myClientHandlerReq" > type="\samples\handlers\myClientHandler.dll"> > > > > > > > > type="\samples\handlers\myClientHandler.dll"> name="myClientHandlerRes" > type="\samples\handlers\myClientHandler.dll"> > > > > > > > > > > > > > > > > > > > > "Antoine Galataud" <[EMAIL PROTECTED] > > 16/03/2006 12:57 > > Please respond to > "Apache AXIS C User List" > > To > > "Apache AXIS C User List" > > cc > > Subject > > Re: Application, Session or Request scope > > > > > > > > yes, i'm referring to the service scope. I saw in the doc that I > could set a scope for handlers in response/reauest flows, but I > didn't see anything about service. > > I'll try to set the scope also in client.wsdd, maybe it's what I'm missing. > > Thanks for any further comments/suggestions. > > 2006/3/16, James Jose <[EMAIL PROTECTED] >: > > Hi, > > We are running HandlerTest01 to HandlerTest10. But here Antoine is > referring the scope of the service ..? > > > Regards > James > -- > James Jose > Messaging Clients Team, WMQDDC > IBM Software Labs, India > Direct: 91-80- 25094331 Ext :2331 > E-mail: [EMAIL PROTECTED] > > > John Hawkins < [EMAIL PROTECTE
Re: Errors running wsdl2ws
Hi, Thanks for pointing out the mistake within the endpoint used by the sample, we shall update this immediately. I have to admit surprise at the particular error you're seeing from the fault, and we shall investage why this is occuring. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Petr Cvachoucek <[EMAIL PROTECTED]> wrote on 21/03/2006 06:01:52: > Yes we had the same problem, may be this is also your case. It is not > related to linux, its a problem on all platforms. > > The calculator sample tried to set endpoint to > http://localhost/axis/calculator, but the service name is Calculator. > The server responded with soap fault (requested service not registered > at the server), which was correctly parsed by a client, but then the > client throws incorrect exception, so the user gets misleading error > 'Cannot deserialize the requested element.'. > > So first try to run calculator sample with correct endpoint, > try for ex: ./calculator div 100 5 http://localhost/axis/Calculator > > If it will work, you should by hand modify the client stub source code > to throw the correct exception, so the user gets correct error > description if there is a soap fault. > > Petr > > Lei Tang wrote: > > I installed Sun JDK and now I can generate the C++ skeleton and stub > > code. But after I built the Calculator sample and deployed it, I got > > the following error when running the client app: > >terminate called after throwing an instance of > > 'axiscpp::SoapFaultException' > > what(): Cannot deserialize the requested element > >Aborted > > > > Does anybody else have the similar problem with Axis c++ 1.6b on the > > linux (Fedora Core 4)? Any help would be appreciated! > > > > Thanks, > > > > Lei > > > > -Original Message- > > From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED] > > Sent: Friday, March 17, 2006 9:35 PM > > To: Apache AXIS C User List > > Subject: Re: Errors running wsdl2ws > > > > Seems like you are using gcj. > > I suggest you use JDK from Sun, or try to compile the whole WSDL2WS Java > > tool, including the required jars from Axis Java using gcj. > > > > I have never been able to use gcj with Axis successfully :-( > > > > Samisa... > > > > Lei Tang wrote: > > > >> I installed latest Axis C++ 1.6b on linux (Fedora 4). When I used > >> wsdl2ws to generat the C++ code for the sample calculator.wsdl file > >> with following command > >> > >> */java org.apache.axis.wsdl.wsdl2ws.WSDL2Ws > >> /usr/local/axiscpp_deploy/wsdls/calcul > >> ator.wsdl -lc++ -sserver -o/tests/ltang/calculator//* > >> > >> I got the following errors: > >> > >> */java.lang.NullPointerException > >>at gnu.xml.dom.ls.ReaderInputStream.close() > > (/usr/lib/libgcj.so.6.0.0) > >>at gnu.xml.aelfred2.XmlParser.doParse(java.lang.String, > >> java.lang.String, jav > >> a.io.Reader, java.io.InputStream, java.lang.String) > >> (/usr/lib/libgcj.so.6.0.0) > >>at gnu.xml.aelfred2.SAXDriver.parse(org.xml.sax.InputSource) > >> (/usr/lib/libgcj > >> .so.6.0.0) > >>at gnu.xml.aelfred2.XmlReader.parse(org.xml.sax.InputSource) > >> (/usr/lib/libgcj > >> .so.6.0.0) > >>at gnu.xml.dom.ls.DomLSParser.doParse(org.w3c.dom.ls.LSInput) > >> (/usr/lib/libgc > >> j.so.6.0.0) > >>at gnu.xml.dom.ls.DomLSParser.parse(org.w3c.dom.ls.LSInput) > >> (/usr/lib/libgcj. > >> so.6.0.0) > >>at gnu.xml.dom.DomDocumentBuilder.parse(org.xml.sax.InputSource) > >> (/usr/lib/li > >> bgcj.so.6.0.0) > >>at > >> org.apache.axis.utils.XMLUtils.newDocument(org.xml.sax.InputSource) > >> (Unkno wn Source) > >>at org.apache.axis.utils.XMLUtils.newDocument(java.lang.String, > >> java.lang.Str > >> ing, java.lang.String) (Unknown Source) > >>at > >> org.apache.axis.wsdl.symbolTable.SymbolTable.populate(java.lang.String > >> , ja va.lang.String, java.lang.String) (Unknown Source) > >>at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run() (Unknown > > Source) > >>at java.lang.Thread.run() (/usr/lib/libgcj.so.6.0.0) > >> org.apache.axis.wsdl.wsdl2ws.WrapperFault: > > java.lang.NullPointerException > >>at > >> > > org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.WSDL2Ws(org.apache.axis.wsdl.wsdl2w > > s. > >> CLArgParser) (Unknown Source) > >>at org.apache.axis
Re: newbie problems part 2: compiling simple_axis_server
Hi, These JARs are shipped with the binary package of Axis C++. Alternatively, these are Jars from Axis (Java) and it's pre-reqs. Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Lukasz Michalski <[EMAIL PROTECTED]> wrote on 09/03/2006 16:50:18: > On Thursday 09 March 2006 09:43, Adrian Dick wrote: > > Hi, > > > > Looking at the point it fails, it is trying to build WSDL2Ws.jar, so it is > > more likely you're missing one of the pre-req JARS (see list here: > > http://ws.apache.org/axis/cpp/clientuser-guide.html#Pre_reqs ). > > > > Adrian > > ___ > > Adrian Dick ([EMAIL PROTECTED]) > > > > My lib/axisjava dir is empty. Where those jars could be downloaded from? > > Thanks, > Łukasz
Re: newbie problems part 2: compiling simple_axis_server
Hi, Looking at the point it fails, it is trying to build WSDL2Ws.jar, so it is more likely you're missing one of the pre-req JARS (see list here: http://ws.apache.org/axis/cpp/clientuser-guide.html#Pre_reqs ). Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Lukasz Michalski <[EMAIL PROTECTED]> wrote on 08/03/2006 19:31:04: > > I turned off apache module compilation and ran into next problems: > > compileSimpleAxisServer: > > buildVersionResource: >[cc] Starting dependency analysis for 2 files. >[cc] 2 files are up to date. >[cc] 0 files to be recompiled from dependency analysis. >[cc] 0 total files to be compiled. >[cc] Starting link > > compileWSDL2Ws: > [javac] Compiling 84 source files > to /home/users/zork/java/axis-c-1.6b-Linux-trace-src/obj/classes > > [javac] /home/users/zork/java/axis-c-1.6b-Linux-trace- > src/src/wsdl/org/apache/axis/wsdl/symbolTable/CElementDecl.java:33: > cannot find symbol > [javac] symbol : class TypeEntry > [javac] location: class org.apache.axis.wsdl.symbolTable.CElementDecl > [javac] private TypeEntry type; > [ and 100 errors more] > > I found answer to similar problems in archive: > http://marc.theaimsgroup.com/?l=axis-c-user&m=111958291324713&w=2 > > As far as I understand javac cannot find $(srcdir)/lib/axis/wsdl2ws.jar where > those symbols are defined. > > I tried to set CLASSPATH to: > > [EMAIL PROTECTED] axis-c-1.6b-Linux-trace-src]$ set |grep CLASSPATH > CLASSPATH=/home/users/zork/java/axis-c-1.6b-Linux-trace- > src/lib/axis/wsdl2ws.jar > > and rerun ant. Still got same errors. > > I tried to simply copy $(srcdir)/lib/axis/wsdl2ws.jar to > /usr/share/java where > all other jars reside, but this didn't help too. > > I tried to run javac manually passing classpath on command line: > > [EMAIL PROTECTED] axis-c-1.6b-Linux-trace-src]$ javac -classpath > lib/axis/ /home/users/zork/java/axis-c-1.6b-Linux-trace- > src/src/wsdl/org/apache/axis/wsdl/symbolTable/CElementDecl.java > /home/users/zork/java/axis-c-1.6b-Linux-trace- > src/src/wsdl/org/apache/axis/wsdl/symbolTable/CElementDecl.java:33: > cannot find symbol > symbol : class TypeEntry > location: class org.apache.axis.wsdl.symbolTable.CElementDecl > private TypeEntry type; > > I am not java expert, can anyone tell me what could be wrong? > > Regards, > Łukasz >
Re: Problem with multiple service/ports in a single WSDL file
Hi, The Axis C++ WSDL2Ws tool currently only supports a single service/port within a WSDL file. There is a Jira issue requesting the addition of this feature ( http://issues.apache.org/jira/browse/AXISCPP-906 ). Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Chuck Harris <[EMAIL PROTECTED]> wrote on 08/03/2006 19:22:32: > Hello, > > I am trying to use the latest release of Axis C++ to build a C++ client > to access some existing Java web services. However, WSDL2Ws is only > producing some of the client source files that I need. My WSDL file, > which was generated by the Sun JWSDK 2.0, is at the bottom of this > message. > > When I run WSDL2Ws, it generates the files: > WSLogEvent.hpp > WSLogEvent.cpp > ILogService.hpp > ILogService.cpp > > which is the set of files required for one of the two ports in the file. > However, it does not produce any files for ITNService (which, > ironically, is what I am trying to test at the moment). > > A search of the mailing list archive didn't produce any similar > messages, and a cursory walk through the WSDL2Ws code likewise wasn't > very illuminating. > > Changing the order of the components for the two ports did not change > the output. Removing all references to ILogService did cause the other > two files (ITNService.cpp and ITNService.hpp) to be generated. > > Is there a known limitation of WSDL2Ws that it only expects a single > service/port combination in the WSDL file? Alternately, is the Sun > JWSDK producing a funky WSDL in this case? > > Or if (as is probably the case) this is merely user error, can anyone > point out what I'm doing wrong? If necessary, I can hand-edit the WSDL > files to produce the initial C++ files, but I'd like to be able to use > my production files in the future. > > Thank you in advance for any assistance. > > Thanks, > Chuck Harris > [EMAIL PROTECTED] > > > > WSDL file: > > > http://ws.xpert.xo.com/"; > xmlns:tns="http://ws.xpert.xo.com/"; > xmlns="http://schemas.xmlsoap.org/wsdl/"; > xmlns:ns2="http://ws.xpert.xo.com/types"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";> > > http://ws.xpert.xo.com/types"; > xmlns:tns="http://ws.xpert.xo.com/types"; > xmlns:soap11-enc="http://schemas.xmlsoap. > org/soap/encoding/" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > xmlns="http://www.w3.org/2001/XMLSchema";> > > > name="_fullLocationInformation" > type="string" > nillable="true" /> > type="int" /> > type="string" > nillable="true" /> > type="string" > nillable="true" > minOccurs="0" maxOccurs="unbounded" /> > type="string" > nillable="true" > minOccurs="0" maxOccurs="unbounded" /> > type="string" > nillable="true" /> > type="string" nillable="true" /> > type="string" > nillable="true" /> > type="string" > nillable="true" > minOccurs="0" maxOccurs="unbounded" /> > type="long" /> > type="string" > nillable="true" /> > type="string" > nillable="true" /> > type="long" />
Re: Axis C++ and Solaris... feedback
Hi, I've just taken a look at the code within the HTTP transport, and there is an inconsistent mix of signed and unsigned short values when handling the port number. It is very likely this is the cause of your problems. The fix looks very simple. Can you raise a JIRA issues for this, so we can track it. Thanks, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) WebSphere MQ and ESB Development IBM United Kingdom Ltd. Tel: +44-(0)-1962-819212 Notes: Adrian Dick/UK/[EMAIL PROTECTED] "Antoine Galataud" <[EMAIL PROTECTED]> wrote on 06/03/2006 15:15:47: > Ok !! It works !!! > > With 1.6a.n ! > > Seems it's a bug, because the client can't open a connection (open a > socket) on a port > 32000 (something like that, I didn't verified > the exact number). So, apache was running on 64010, it was bad. > I verified with some home made samples in cpp and java, the > connections work for ports >32000. So i guess it's an axis bug. > Could you confirm ? > > Thanks > 2006/3/6, Antoine Galataud < [EMAIL PROTECTED]>: > Hi all ! > > I'm still searching for a solution to my client problem (SIGABRT) > received. I think I'm near the problem, but i need help to solve it ! > > In fact, exception thrown by client is HTTPTransportException, and > it seems to be thrown in HTTPChannel::OpenChannel(). But I don't > know exactly where. > Here is my client log : > > [06/03/2006 12:10:53:808 MET] 1 HTTPTransport > openConnection @248e8 > [06/03/2006 12:10:53:808 MET] 1 HTTPChannel > open @249c8 > [06/03/2006 12:10:53:809 MET] 1 HTTPChannel > OpenChannel @249c8 > [06/03/2006 12:10:53:809 MET] 1 URL > getHostName > [06/03/2006 12:10:53:809 MET] 1 URL < getHostName "localhost" > [06/03/2006 12:10:53:809 MET] 1 URL > getPort > [06/03/2006 12:10:53:809 MET] 1 URL < getPort 64010 > [06/03/2006 12:10:53:877 MET] 1 HTTPTransportException > > HTTPTransportException @fefea988,54, > [06/03/2006 12:10:53:878 MET] 1 HTTPTransportException > > getMessageForExceptionCode @fefea988,54 > [06/03/2006 12:10:53:878 MET] 1 HTTPTransportException < > getMessageForExceptionCode @fefea988,"HTTPTransportException:Unknown > Transport Exception" > [06/03/2006 12:10:53:878 MET] 1 HTTPTransportException < > HTTPTransportException @fefea988 > [06/03/2006 12:10:53:878 MET] 1 ClientAxisEngine X process @24a88, > caught AxisException(6, "HTTPTransportException:Unknown Transport Exception") > [06/03/2006 12:10:53:879 MET] 1 AxisGenException > AxisGenException > @fefea9e0,54, "HTTPTransportException:Unknown Transport Exception" > [06/03/2006 12:10:53:879 MET] 1 AxisGenException > > getMessageForExceptionCode @fefea9e0,54 > [06/03/2006 12:10:53:879 MET] 1 AxisGenException < > getMessageForExceptionCode @fefea9e0,"" > [06/03/2006 12:10:53:879 MET] 1 AxisGenException > > getMessageForExceptionCode @fefea9e0,54 > [06/03/2006 12:10:53:879 MET] 1 AxisGenException < > getMessageForExceptionCode @fefea9e0,"" > [06/03/2006 12:10:53:879 MET] 1 AxisGenException < AxisGenException @fefea9e0 > [06/03/2006 12:10:53:879 MET] 1 HTTPTransportException > > ~HTTPTransportException @fefea988 > [06/03/2006 12:10:53:880 MET] 1 HTTPTransportException < > ~HTTPTransportException @fefea988 > [06/03/2006 12:10:53:880 MET] 1 SoapFaultException > > SoapFaultException @fefeaa38,AxisException(6, " > HTTPTransportException:Unknown Transport Exception") > [06/03/2006 12:10:53:880 MET] 1 SoapFaultException < > SoapFaultException @fefeaa38 > > it is said as an unknown transport exception, but i can guess it is > when connection is opened, maybe when socket is opened. > > Some more details : the server is running on http://localhost:64010/axis > the service Calculator provides add(int,int) method at http: > //localhost:64010/axis/Calculator#add > > In the file Calculator.cpp generated by wsdl2ws, i tried to set > endpoint uri to "http://localhost:64010/axis"; or even " http: > //localhost:64010/axis/Calculator " > > What can be the possible cause(s) of this problem ? > > Thanks in advance ! > > 2006/3/3, Antoine Galataud < [EMAIL PROTECTED] >: > I forgot : i also had to relink libaxiscpp_mod.so, cause some libs > were missing > like this : > CC -qoption ld -i -o libaxiscpp_mod.so -G -lCrun -lCstd /axis/axis- > c-1.6a.n-SunOS-trace-bin/lib/axis/libaxiscpp_mod.so > 2006/3/3, Antoine Galataud < [EMAIL PROTECTED]>: > ok, i tried with : > - 1.6a.n binary release for SunOS > - calculator example > - xerces 2.2.0 > > I'm stuck again with the "same" error : when i run t
Re: Client Exception: N7axiscpp19AxisEngineExceptionE
Hi, The Axis C++ 1.5 binaries were produced using the Xerces-C 2.2.0 binaries. If you wish to use a different version of Xerces-C you will need to re-build the Axis C++ XMLParser library from source, against your desired version. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Rob Redmon <[EMAIL PROTECTED]> wrote on 01/03/2006 22:13:52: > > I should add that since my last message, I've also downloaded and > built: xerces-c-current.tar.gz > And added the parser to my library path so that LD_LIBRARY_PATH is: > /home/robr/packages/xerces-c-src_2_7_0/lib:/home/robr/packages/axis- > c-1.5.0-linux-bin/lib > > I'm still getting > N7axiscpp19AxisEngineExceptionE > > And not seeing anything on the wire. > > Rob > > Rob Redmon wrote: > I am not seeing anything on the wire and I'm using the xerces that > came with my AXIS dist, namely: > > axis-c-1.5.0-linux-bin/lib/libaxis_xerces.so > > My LD_LIBRARY_PATH is: > /home/robr/packages/axis-c-1.5.0-linux-bin/lib/ > > > > John Hawkins wrote: > > Are you getting anything sent across the wire? > > AND: If you are not then please can check that you have the correct > version of xerces in your lib path. > > > > > Rob Redmon <[EMAIL PROTECTED]> > 17/02/2006 22:03 > > Please respond to > "Apache AXIS C User List" > > To > > axis-c-user@ws.apache.org > > cc > > Subject > > Client Exception: N7axiscpp19AxisEngineExceptionE > > > > > > I've tried creating stubs for 3 different simple WebService providers > and I'm always getting this exception: > N7axiscpp19AxisEngineExceptionE > > I also tried the Calculator client example (w/NO deployed matching > webservice on localhost) to see what error I'd arrive at and I got the > same Exception. > My relevant environment variables are: > AXISCPP_DEPLOY=/home/robr/packages/axis-c-1.5.0-linux-bin/ > > Here's a copy of my $AXISCPP_DEPLOY/etc/axiscpp.conf > LogPath:/home/robr/log/AxisLog > #WSDDFilePath:/home/obj/etc/server.wsdd > ClientLogPath:/home/robr/log/AxisClientLog > #ClientWSDDFilePath:/home/obj/etc/client.wsdd > XMLParser:/home/robr/lib/libaxis_xerces.so > Transport_http:/home/robr/lib/libhttp_transport.so > Channel_HTTP:/home/robr/lib/libhttp_channel.so > #Channel_HTTP_SSL: > /home/samisa/autoCVS/cvsAutoBuild/deploy/lib/libaxis3_transport_ssl_channel.so > > -- > Rob Redmon > NOAA/NGDC > 325 Broadway E/GC2 > Boulder, Colorado 80305 > Tel: (303) 497-4331 > Fax: (303) 497-6513 > [EMAIL PROTECTED] > > "Engineering is the art of making what you want from things you can get." > > > -- > Rob Redmon > NOAA/NGDC > 325 Broadway E/GC2 > Boulder, Colorado 80305 > Tel: (303) 497-4331 > Fax: (303) 497-6513 > [EMAIL PROTECTED] > > "Engineering is the art of making what you want from things you can get." > > > -- > Rob Redmon > NOAA/NGDC > 325 Broadway E/GC2 > Boulder, Colorado 80305 > Tel: (303) 497-4331 > Fax: (303) 497-6513 > [EMAIL PROTECTED] > > "Engineering is the art of making what you want from things you can get."
RE: Unhandled exception at 0x7c901230 : User breakpoint
Hi, Can you try turning on start up trace. Set the following environment variable to point to the log file you wish to create: AXISCPP_STARTUP_TRACE eg: AXISCPP_STARTUP_TRACE=c:\test\starttrace.txt Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) "Yaron Cohen" <[EMAIL PROTECTED]> wrote on 28/02/2006 11:47:15: > Hi, > > Now my conf file looks like this: > > # The comment character is '#' > #Available directives are as follows > #(Some of these directives may not be implemented yet) > # > #WSDDFilePath:The path to the server wsdd > #LogPath:The path to the axis log > #ClientLogPath:The path to the axis client log > #ClientWSDDFilePath:The path to the client wsdd > #Transport_http:The HTTP transport library > #Transport_smtp:The SMTP transport library > #XMLParser:The xml parser library > #NodeName:Node name > #ListenPort:Listening port > #Channel_HTTP:The HTTP transport channel library > #Channel_HTTP_SSL:The HTTP transport secure channel library > > #LogPath:Axis\logs\AxisLog.txt > #WSDDFilePath:Axis\conf\server.wsdd > > Transport_http:C:\test\HTTPTransport.dll > Channel_HTTP:C:\test\HTTPChannel.dll > XMLParser:C:\test\AxisXMLParserXerces.dll > ClientLogPath:C:\test\log.txt > > All the dlls(HTTPTransport.dll, HTTPChannel.dll, > AxisXMLParserXerces.dll) are at c:\test, so it would not be any spaces > in the folder path. In addition, I tried to set the path to > D:\mySms\axis-c-win32-current-bin\axis-c-1-5-win32\bin, but it still > does not work. > > I am getting the same problem. > > I am still not getting any logs. > > Any suggestions? > > Thanks > Yaron > > -Original Message- > From: Adrian Dick [mailto:[EMAIL PROTECTED] > Sent: Monday, February 27, 2006 1:08 PM > To: Apache AXIS C User List > Subject: RE: Unhandled exception at 0x7c901230 : User breakpoint > > Hi, > > > ok, for the logs. > LogPath is used by Axis c++ server, for client you need to use > ClientLogPath > > The paths you're specifying for the various Axis C++ DLLs look a little > suspicious to me, are they really located within your samples structure? > or should your paths look more like: > > Transport_http:D:\mySms\axis-c-win32-current-bin\axis-c-1-5-win32\bin\HT > TPTransport.dll > > Asides from that you look to have the right settings. So it could be a > path issue. Your path needs to include: Axis C++ libraries ( install>\bin ) and the Xerces-c libraries ( \bin ) > (must > be v2.2.0 if using binary package). > > Adrian > ___ > Adrian Dick ([EMAIL PROTECTED]) > WebSphere MQ and ESB Development > IBM United Kingdom Ltd. > Tel: +44-(0)-1962-819212 > Notes: Adrian Dick/UK/[EMAIL PROTECTED] > > "Yaron Cohen" <[EMAIL PROTECTED]> wrote on 27/02/2006 08:57:14: > > > Hi, > > > > Thanks for the quick answer. > > > > I am working with the latest version (I think) since I just download > it > > (axis-c-1-5-win32). > > > > In addition, the first error that I got was that it can not find the > > conf file. > > > > After I solved this problem, I did what ever you said in the > > http://ws.apache.org/axis/cpp/install-guide.html#Installing_Client. > > Nevertheless, I think that I am not configuring it right. > > > > Here is my conf file content: > > > > # The comment character is '#' > > #Available directives are as follows > > #(Some of these directives may not be implemented yet) > > # > > #WSDDFilePath:The path to the server wsdd > > #LogPath:The path to the axis log > > #ClientLogPath:The path to the axis client log > > #ClientWSDDFilePath:The path to the client wsdd > > #Transport_http:The HTTP transport library > > #Transport_smtp:The SMTP transport library > > #XMLParser:The xml parser library > > #NodeName:Node name > > #ListenPort:Listening port > > #Channel_HTTP:The HTTP transport channel library > > #Channel_HTTP_SSL:The HTTP transport secure channel library > > > > #LogPath:Axis\logs\AxisLog.txt > > #WSDDFilePath:Axis\conf\server.wsdd > > > Transport_http:D:\mySms\axis-c-win32-current-bin\axis-c-1-5-win32\sample > > s\client\WebServiceClientTest3\HTTPTransport.dll > > > Channel_HTTP:D:\mySms\axis-c-win32-current-bin\axis-c-1-5-win32\samples\ > > client\WebServiceClientTest3\HTTPChannel.dll > > > XMLParser:D:\mySms\axis-c-win32-current-bin\axis-c-1-5-win32\samples\cli > > ent\WebServiceClientTest3\AxisXMLParserXerces.dll > > #ClientWSDDFilePath:C:\Documents and > > > Settings\yaronco\Desktop\axis
Re: exception code 61
Hi,
To answer your second question:
The locking mechanism used on Windows relied on an API which changed
between versions of MS Visual C++. Unfortunately, this was not discovered
until after Axis C++ 1.5 was released.
However, we have now fixed this section of code to use an alternate API.
If you wish to use source, you can get this from SVN (see instructions
here: http://ws.apache.org/axis/cpp/developers-guide.html#checkingOut )
Adrian
___
Adrian Dick ([EMAIL PROTECTED])
WebSphere MQ and ESB Development
IBM United Kingdom Ltd.
Tel: +44-(0)-1962-819212
Notes: Adrian Dick/UK/[EMAIL PROTECTED]
>
> I am trying to rebuild the axis to get an debuggable version - but
> without luck neither, the error from ant is:
> 4290: C++ exception specification ignored except to indicate a function
> is not __declspec(nothrow)
>[cc] C:\opt\work\axis-c-src-1-5-win32\src\engine\Axis.cpp(302) :
> error C2440: 'reinterpret_ca
> st' : cannot convert from 'volatile long *' to 'void ** '
>[cc] Conversion loses qualifiers
>[cc] C:\opt\work\axis-c-src-1-5-win32\src\engine\Axis.cpp(302) :
> fatal error C1903: unable to
> recover from previous error(s); stopping compilation
> where the code is like this:
>
> static volatile long g_uModuleInitializing = 0;
> static void start_initializing()
> {
> long exchange = 1;
> long comperand = 0;
> while (InterlockedCompareExchange(((void **)&g_uModuleInitializing),
> static_cast(&exchange), static_cast(&comperand)));
> }
> the line 302 is the last line where calling
> InterlockedCompareExchange(((void **)...
> Any suggestion?
>
> By the way, the same code works ok on linux.
>
> Thanks!
> Tao
Re: Solaris Axis C++ compilation problem
Hi, Have you tried using the latest code from SVN, as I believe a fix may already have been included. Instructions for accessing this are available here: http://ws.apache.org/axis/cpp/developers-guide.html#checkingOut Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) "Antoine Galataud" <[EMAIL PROTECTED]> wrote on 27/02/2006 17:29:04: > Hi all ! > > I saw some threads in this mailing list concerning the same problem, > but no solution seems to appear; > > I am working on a project to include Axis C++ framework on a lot of > different platforms; for the moment, i've just tried with Solaris (our > dev platform), and I am running in troubles. I get the following error > while calling ant build target : > > BUILD FAILED > axis/1.5.0/build.xml:231: The following error occurred while executing > this line: > axis/1.5.0/build.xml:219: The following error occurred while executing > this line: > axis/1.5.0/build.xml:90: The following error occurred while > executing this line: > axis/1.5.0/build/buildClient.xml:23: CC failed with return code 1 > > and cpp compile error : > > [cc] "/rms/sunpro/sun-one- > studio-8/C++patch04/SUNWspro/prod/include/CC/Cstd/./list.cc", > line 171: Error: The operation "axiscpp::HandlerChain::ChainItem == > const axiscpp::HandlerChain::ChainItem" is illegal. > [cc] 1 Error(s) detected > > I tried to figure out where was located the instruction throwing this > error, but don't want to modify source code. Is there somebody here > that had the same problem, and maybe found a solution ? > > Thanks ! > -- > Antoine Galataud > [EMAIL PROTECTED] > Département Architecture des Systèmes d'Information > INSA - Rouen
RE: Unhandled exception at 0x7c901230 : User breakpoint
Hi, ok, for the logs. LogPath is used by Axis c++ server, for client you need to use ClientLogPath The paths you're specifying for the various Axis C++ DLLs look a little suspicious to me, are they really located within your samples structure? or should your paths look more like: Transport_http:D:\mySms\axis-c-win32-current-bin\axis-c-1-5-win32\bin\HTTPTransport.dll Asides from that you look to have the right settings. So it could be a path issue. Your path needs to include: Axis C++ libraries ( \bin ) and the Xerces-c libraries ( \bin ) (must be v2.2.0 if using binary package). Adrian ___ Adrian Dick ([EMAIL PROTECTED]) WebSphere MQ and ESB Development IBM United Kingdom Ltd. Tel: +44-(0)-1962-819212 Notes: Adrian Dick/UK/[EMAIL PROTECTED] "Yaron Cohen" <[EMAIL PROTECTED]> wrote on 27/02/2006 08:57:14: > Hi, > > Thanks for the quick answer. > > I am working with the latest version (I think) since I just download it > (axis-c-1-5-win32). > > In addition, the first error that I got was that it can not find the > conf file. > > After I solved this problem, I did what ever you said in the > http://ws.apache.org/axis/cpp/install-guide.html#Installing_Client. > Nevertheless, I think that I am not configuring it right. > > Here is my conf file content: > > # The comment character is '#' > #Available directives are as follows > #(Some of these directives may not be implemented yet) > # > #WSDDFilePath:The path to the server wsdd > #LogPath:The path to the axis log > #ClientLogPath:The path to the axis client log > #ClientWSDDFilePath:The path to the client wsdd > #Transport_http:The HTTP transport library > #Transport_smtp:The SMTP transport library > #XMLParser:The xml parser library > #NodeName:Node name > #ListenPort:Listening port > #Channel_HTTP:The HTTP transport channel library > #Channel_HTTP_SSL:The HTTP transport secure channel library > > #LogPath:Axis\logs\AxisLog.txt > #WSDDFilePath:Axis\conf\server.wsdd > Transport_http:D:\mySms\axis-c-win32-current-bin\axis-c-1-5-win32\sample > s\client\WebServiceClientTest3\HTTPTransport.dll > Channel_HTTP:D:\mySms\axis-c-win32-current-bin\axis-c-1-5-win32\samples\ > client\WebServiceClientTest3\HTTPChannel.dll > XMLParser:D:\mySms\axis-c-win32-current-bin\axis-c-1-5-win32\samples\cli > ent\WebServiceClientTest3\AxisXMLParserXerces.dll > #ClientWSDDFilePath:C:\Documents and > Settings\yaronco\Desktop\axis-c-win32-current-bin\axis-c-1-5-win32\sampl > es\client\WebServiceClientTest3\deploy\conf\client.wsdd > LogPath:D:\mySms\axis-c-win32-current-bin\axis-c-1-5-win32\samples\clien > t\WebServiceClientTest3\deploy\log\log.txt > > I am not getting any logs in the > "D:\mySms\axis-c-win32-current-bin\axis-c-1-5-win32\samples\client\WebSe > rviceClientTest3\deploy\log" configured directory. > > Please help me, it looks like I am lost. > > > > -Original Message- > From: Adrian Dick [mailto:[EMAIL PROTECTED] > Sent: Monday, February 27, 2006 10:44 AM > To: Apache AXIS C User List > Subject: Re: Unhandled exception at 0x7c901230 : User breakpoint > > Hi, > > Which version of Axis C++ are you using, and are you following the > bundled > instructions or latest versions available on > http://ws.apache.org/axis/cpp/documentation.html ? > > It sounds like the problem you're seeing is caused by the Xerces-C > libraries not being available on the system library path at runtime. > Check > the latest install/config instructions here: > http://ws.apache.org/axis/cpp/install-guide.html#Installing_Client > > Adrian > ___ > Adrian Dick ([EMAIL PROTECTED]) > > > "Yaron Cohen" <[EMAIL PROTECTED]> wrote on 27/02/2006 07:25:15: > > > Hi, > > > > I have the same problem as described at: http://www.nabble. > > > com/Using-generated-CPP-files-in-visual-studio-2003-t841990.html#a218167 > 1. > > > Can you please explain to me: > > > > How should I configure the conf file? It looks like what ever I do > > in order to configure it, I get the same error. > > > > Please note that I did what ever you explain under "Client > > Installation and Configuration" and it does not work. > > > > Thanks > > Yaron > > > > > > Yaron Cohen > > VoIP Integrations Software Engineer EIS, R&D > > NICE Systems. Israel > > > > (T) +972 (9) 7752338 > > (M) +972 (54) 5442488 > > (F) +972 (9) 7753600 > > > > [EMAIL PROTECTED] > > www.nice.com > > > > --- > > NICE - Insight from Interactions > > >
Re: Unhandled exception at 0x7c901230 : User breakpoint
Hi, Which version of Axis C++ are you using, and are you following the bundled instructions or latest versions available on http://ws.apache.org/axis/cpp/documentation.html ? It sounds like the problem you're seeing is caused by the Xerces-C libraries not being available on the system library path at runtime. Check the latest install/config instructions here: http://ws.apache.org/axis/cpp/install-guide.html#Installing_Client Adrian ___ Adrian Dick ([EMAIL PROTECTED]) "Yaron Cohen" <[EMAIL PROTECTED]> wrote on 27/02/2006 07:25:15: > Hi, > > I have the same problem as described at: http://www.nabble. > com/Using-generated-CPP-files-in-visual-studio-2003-t841990.html#a2181671. > Can you please explain to me: > > How should I configure the conf file? It looks like what ever I do > in order to configure it, I get the same error. > > Please note that I did what ever you explain under “Client > Installation and Configuration” and it does not work. > > Thanks > Yaron > > > Yaron Cohen > VoIP Integrations Software Engineer EIS, R&D > NICE Systems. Israel > > (T) +972 (9) 7752338 > (M) +972 (54) 5442488 > (F) +972 (9) 7753600 > > [EMAIL PROTECTED] > www.nice.com > > --- > NICE - Insight from Interactions >
Re: Problem communicating strings with Apache Axis 1.3 toolkit
Hi, I have raised Jira issue AXISCPP-938 ( http://issues.apache.org/jira/browse/AXISCPP-938 ) to follow the progress of this problem. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) "Michael Thadani" <[EMAIL PROTECTED]> wrote on 03/02/2006 00:14:17: > Hi, > > I have a small webservice deployed on a jetty webserver running axis > java 1.3. I have written test clients in java to verify it is working > correctly. > > After having difficulties using the 1.5 binary release of axisc (the > object files were being ignored because of apparent incompatability), I > decided to build axisc from source and built from the cvs. > > I now have a small c++ client. I have been able to successfully send > strings from the client to the server and return an int value denoting > their size (very simple but it was just a test case). However, in > another test I am attempting to return a string from a method and the > axisc client is not performing correctly. > > The program does not terminate unexpectedly but calling the remote > function does not seem to return a valid string. Attempts to print the > contents of the returned string (via std::cout) have not worked - after > calling 'std::cout << returnedString' the program's output is blank and > subsequent cout calls seem to not work (they are executed but do not > produce output). > > The soap requests are being made (viewable from the SOAP Monitor) so it > appears the problem lies in the parsing/interpreting of the response. > > I have included the xml below in case there is a problem in it that I am > not seeing. > > Is the 1.6 current build currently correctly accepting strings as return > parameters? If so, any suggestions about how I may go about debugging > this odd behaviour? > > Thanks in advance > Michael Thadani > > > > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > > > The quick brown fox jumped over the > lazy dog. > 2 > 10 > > > > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > > soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; > xmlns:ns1="urn:simplewebservice"> >xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>e > quick > > >
Re: Status of Axis C++ build system
Hi, The makefile/libtool based build system hasn't been maintained for some time, so it is very likely it refers to non-existent files, while missing out more recently added files. There is an ANT based system, which is used by the nightly builds. You can find instructions on its use here: http://ws.apache.org/axis/cpp/antbuild-guide.html Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Josef Spillner <[EMAIL PROTECTED]> wrote on 23/02/2006 15:39:10: > Hi there, > > I tried compiling Axis C++ 1.5 on Linux, and got a couple of errors which > remain when using the latest SVN trunk sources. > > It starts with missing files when running autogen.sh: > > samples/server/Makefile.am:1: required directory samples/server/interoptests > does not exist > samples/server/Makefile.am:1: required directory samples/server/simple does > not exist > > and continues up to linker errors in src/server/simple_axis_server. For the > latter one, I replaced -lserver_engine with > ../../engine/server/libserver_engine.la (always use the *.la files > for linking > with libtool!). > > Since for the former case, I don't know if the files are referenced > wrongly in > configure.ac or have not yet been added to SVN (= are actually missing), I'd > like to know who currently works on, or at least with, the Linux build > system. > > Josef > > -- > Tous ces gens qui confondent informatique et bureautique, carte et territoire, > interface et programme, boutons colorés et facilité... > - S. Blondeel
RE: SSL Client
Hi, See responses below Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Iwan Tomlow <[EMAIL PROTECTED]> wrote on 22/02/2006 07:35:57: > Hi, > > thanks for the reply, I did actually get it working with the changes > I described - these were applied to the Axis C++ 1.5 Final sources. > I was actually looking for the repository on the Apache website, and > the main page at http://ws.apache.org/axis still links to 'Get > Involved' > 'CVS Repository' = http://ws.apache.org/axis/cvs.html - > but the links there are no longer valid? Ah, yes. Just noticed that hasn't been updated. However, there is current information within the C++ developers documentation: http://ws.apache.org/axis/cpp/developers-guide.html > > One extra remark for others trying to get SSL to work: I noticed > that even for a client-only installation, I needed the > AXISCPP_DEPLOY environment variable and an appropriate axiscpp.conf > configuration file there for SSL to work (with Channel_HTTP_SSL: ... > \HTTPSSLChannel.dll in it). > This axiscpp.conf was not necessary for the client without SSL, is > that correct? I've just taken a look and it would appear this is the case. For most of the other properties within axiscpp.conf the engine has a default value (meaning you needn't setup AXISCPP_DEPLOY, and axiscpp.conf), but Channel_HTTP_SSL does not have a default.
Re: AxisC++ 1.5 fail retrieve string arrays in SOAP message?
Hi, There were still some outstanding issues with arrays at the release of Axis C++ 1.5. There has since been a lot of work in improving the design and workings of arrays, which is available in the 1.6 nightly builds - you may wish to try these to see if your problems have already been resolved. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Tao Yang <[EMAIL PROTECTED]> wrote on 21/02/2006 23:52:33: > Just in case someone else may want to know my lesson here. > > It turns out this is happening because I always return a array whose > last item is null - I was paranoid before I dig into Axis C++ and afraid > of it won't know the size of the array so that that null is put in as > boundary indicator. However, nicely the Axis C++ does return the array > size; but fail to cope with my "null" boundary indicator and thought > error has happened. > > This does raise a question though: why Axis C++ can't handle a "null" > item? the java version process this nicely by the way. > > cheers, > Tao > > Tao Yang wrote: > > > Oops, I forget to say. Even the valid response is observed through > > the SOAPMonitor, the c++ client code is always reporting: > > "result.size = 0" > > What could be preventing it extract the strings from the message? > > > > Thanks, > > Tao > > > >> > >
Re: Re: SIGABRT on Axis C++ client
Hi, It sounds like you also need to ensure Xerces-C (v2.2.0 if using binary package) is available on the system path You will find full instructions on setting up the client here: http://ws.apache.org/axis/cpp/install-guide.html#Installing_Client Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Tao Yang <[EMAIL PROTECTED]> wrote on 21/02/2006 14:47:54: > Hi, > > But I am only using the client lib - my code is talking to a Axis JAVA > server deployed in tomcat. > Or do you mean even one uses only the client, he has to provide the > server dploy description? If so, what it should contain? I tried add > one, still same crash though. > > BTW, I also changed the XMLParser to use the one in axiscpp's lib > directory, no hlep neither. :-( > > But still thanks for reply. > Tao > > >Hi, > > > > your configuration file axiscpp.conf file is not right plese check your > >axiscpp.conf file. > >this file must have the following entry.. > > LogPath:/home/Axis/log/server.log > > WSDDFilePath:/home/Axis/etc/server.wsdd > > Transport_http:/home/Axis/lib/libhttp_transport.so > > XMLParser:/home/Axis/lib/libaxis_xerces.so > > Channel_HTTP:/home/Axis/lib/libhttp_channel.so > > > > > >Thanks > >Arashad Ahamad > > > > > >
Re: linux distribution don't have ssl support?
Hi, In response to your questions: 1) It would appear there is a mistake in the installation instructions. The file names should read: libaxis3_transport_channel.so becomes libhttp_channel.so libaxis3_transport_ssl_channel.so becomes libhttp_channelssl.so libaxis3_transport.so becomes libhttp_transport.so 2) As you say, it would appear the SSL channel is missing from the binary packages. If you wish to stay at Axis C++ 1.5, you will need to rebuild these. Alternatively, you may wish to try the latest 1.6 nightly builds, which include the SLL libraries. 3) I agree with you that the deploy directory appears to be missing for linux. Again, this is present for the latest 1.6 nightly builds 4) Axis C++ should work fine with Axis java Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Tao Yang <[EMAIL PROTECTED]> wrote on 20/02/2006 16:38:34: > Hi, > > I am trying to get Axis C++ 1.5 on linux as client to interact > with Axis 1.3 server (java, deployed on tomcat 5) this morning. I > notice a few things: > 1) The installation document mentioned following configuration: > > Transport_http:/usr/local/axiscpp_deploy/lib/libaxis3_transport.so > Channel_HTTP:/usr/local/axiscpp_deploy/lib/libaxis3_transport_channel.so > XMLParser:/usr/local/axiscpp_deploy/lib/libaxis_xercesc.so > ClientWSDDFilePath:/usr/local/axiscpp_deploy/etc/client.wsdd > ClientLogPath:/usr/local/axiscpp_deploy/log/AxisClientLog > > which is a bit confusing since I cannot find neither > libaxis3_transport.so nor libaxis3_transport_channel.so in > the tar gz'ed file - axis-c-linux-current-bin.tar.gz > I can only find following libs: > > > [EMAIL PROTECTED] axis4Lin]$ ls axis-c-1.5.0-linux-bin/lib/ > axis libaxiscpp_mod.solibdoclitfault.so > axisjava libaxiscpp_mod.so.1 libelement.so > libarray.so libaxiscpp_mod.so.1.5.0 libenumeration.so > libaxis_clientC.solibaxis_server.solibhttp_channel.so > libaxis_clientC.so.1 libaxis_server.so.1 libhttp_channel.so.1 > libaxis_clientC.so.1.5.0 libaxis_server.so.1.5.0 libhttp_channel.so.1.5.0 > libaxis_client.so libaxis_xerces.solibhttp_transport.so > libaxis_client.so.1 libaxis_xerces.so.1 libhttp_transport.so.1 > libaxis_client.so.1.5.0 libaxis_xerces.so.1.5.0 > libhttp_transport.so.1.5.0 > libaxiscpp_mod2.solibbase.so libref.so > libaxiscpp_mod2.so.1 libbench.so librpcfault.so > libaxiscpp_mod2.so.1.5.0 libcalculator.so libtransportProperties.so > [EMAIL PROTECTED] axis4Lin]$ > Plus, the SSL channel also seems missing - no > libaxis3_transport_ssl_channel.so > found neither. > > Do I have to re-built it by myself? > > Another thing is there is no deploy dir found in the linux bin distro as > in window's. > And the content of deploy dir in window's distro seems to me are for > linux. Am I > missing something here? > > At last, one important question is: does Axis C++ work with Axis (java) > as I would > expect? > > Thanks, > Tao
Re: Problem With Namespaces
Hi, Are you in a position to try the latest Axis C++ 1.6 nightly build? As there have been a number of namespace related fixes since 1.5. Adrian ___ Adrian Dick ([EMAIL PROTECTED]) "Percey, Michael (MED US)" <[EMAIL PROTECTED]> wrote on 02/02/2006 21:16:11: > I have a VB 6.0 Client UI that must communicate with a Websphere > Soap Server. I'm building a CPP DLL using Axis C++ 1.5 to translate > the VB request into a SOAP Request, forward that request to > Websphere, receive the corresponding response, translate and return > that response to the VB Client. > > Note that we've already integrated Axis Java 1.3 into our Java Swing > client and it is succesfully processing Requests/Responses with the > same Websphere Soap Server. > > I have the DLL up and running, and it is serializing the VB Request > and forwarding that request on to the server. It turns out that the > Websphere Soap Server cannot deserialize the Axis C++ Soap message > because of the NameSpace definition that appears within each > arguement element. > > I've verified this problem and solution using TCPMon. An example follows: > > > http://service.ctk.se. > soarian.siemens.com"> > >http://dto.ctk.se.soarian.siemens.com > ">getMasterFileList >http://dto.ctk.se.soarian.siemens.com > ">MasterFile >http://dto.ctk.se.soarian.siemens.com > ">NULL >http://dto.ctk.se.soarian. > siemens.com">NULL >http://dto.ctk.se. > soarian.siemens.com">1 > > > > > The namespace on the request is not a problem. Then namespace on > the arguement elements cause the following error to occur: > Cannot deserialize element action of bean com.siemens.soarian.se. > ctk.dto.WSRequestFlatDTO. Message being parsed: > So, to the question. Are there any options to turn off the usage of > the Namespaces. If not, can anybody give me an idea where I need to > look in the source to modify this myself. > > Thanks - MikeP > > > --- > This message and any included attachments are from Siemens Medical Solutions > USA, Inc. and are intended only for the addressee(s). > The information contained herein may include trade secrets or privileged or > otherwise confidential information. Unauthorized review, forwarding,printing, > copying, distributing, or using such information is strictly > prohibited and may > be unlawful. If you received this message in error, or have reason to believe > you are not authorized to receive it, please promptly delete this message and > notify the sender by e-mail with a copy to Central. > [EMAIL PROTECTED] > > Thank you
Re: Problem running WSDL2Ws Tool
Hi, The problem with classpath ordering was resolved sometime ago. I notice from your classpath that you're using the Axis (java) 1.3 JARs, the Axis C++ WSDL2Ws tool is built and tested in combination with Axis 1.2 - it could be there is an incompatibility with the later version. I would recommend using the JAR files provided with the Axis C++ package - these can be found in lib/axisjava. Adrian ___ Adrian Dick ([EMAIL PROTECTED]) "Michael Thadani" <[EMAIL PROTECTED]> wrote on 31/01/2006 00:23:39: > I recently deployed an axis java on my server and was wishing to > develop a c++ client to consume the webservice on it. > > However, I have stumbled into a wall with the wsdl2ws tool – it > doesn’t seem to run L > > The exception I am encountering is: > > java org.apache.axis.wsdl.wsdl2ws.WSDL2Ws SimpleWebService.wsdl -lc++ -sclient > Exception in thread "main" java.lang.NoSuchMethodError: org.apache. > axis.wsdl.symbolTable.BindingEntry.getBindingStyle() > Lorg/apache/axis/enum/Style; > at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.setMethodInfo(Unknown Source) > at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.getServiceInfo(Unknown Source) > at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws. > generateWrappers(Unknown Source)at org.apache.axis.wsdl. > wsdl2ws.WSDL2Ws.main(Unknown Source) > > I had a look through the archive of old posts but I couldn’t find a > case where it had been successfully resolved. > > I read in the user guide to ensure wsdl 2ws.jar was ahead of axis. > jar and have done so but still encounter the issue. > > I have included the contents of my current $CLASSPATH > > /home/mthadani/axisc-1.5.0-linux/lib/axis/wsdl2ws.jar: > /home/mthadani/axis-1_3/lib/commons-discovery-0.2.jar: > /home/mthadani/axis-1_3/lib/commons-logging-1.0.4.jar: > /home/mthadani/axis-1_3/lib/jaxrpc.jar: > /home/mthadani/axis-1_3/lib/saaj.jar: > /home/mthadani/axis-1_3/lib/log4j-1.2.8.jar: > /home/mthadani/axis-1_3/lib/xml-apis.jar: > /home/mthadani/axis-1_3/lib/mail.jar: > /home/mthadani/axis-1_3/lib/axis-schema.jar: > /home/mthadani/axis-1_3/lib/wsdl4j-1.5.1.jar: > /home/mthadani/axis-1_3/lib/axis-ant.jar: > /home/mthadani/axis-1_3/lib/axis.jar:/home/mthadani/axis-1_3: > /home/mthadani/jetty-5.1.10/lib/org.mortbay.jetty.jar: > /home/mthadani/jetty-5.1.10/lib/javax.servlet.jar: > /home/mthadani/jetty-5.1.10/ext/jasper-runtime.jar: > /home/mthadani/jetty-5.1.10/ext/jasper-compiler.jar: > /home/mthadani/jetty-5.1.10/ext/xercesImpl.jar: > /home/mthadani/jetty-5.1.10/ext/ant.jar:/home/mthadani/jetty-5.1. > 10/ext/commons-el.jar:/home/mthadani/jetty-5.1.10/ext/activation. > jar:/home/mthadani/jetty-5.1.10/mx4j.jar:/home/mthadani/jetty-5.1. > 10/mx4j-tools.jar:/usr/java/j2sdk1.4.2_09/lib/tools.jar:. > > Any assistance would be most welcome > > Michael
Re: empty array of complex type crashes the client
Hi, Responses to your questions below. Adrian ___ Adrian Dick ([EMAIL PROTECTED]) > > > - The SOAP response message looks more like an rcp/encoded > > style message - due to the inclusion of xsi:type="..." - yet > > your WSDL states doc/literal, > > Could you point one place where it is "wrong"? > > For instance, should > > be changed to > > > (assuming all literals are strings)? Actually, the problem isn't in the WSDL file - you still need to include the type there - but with the SOAP message. So, in your provided SOAP response you have the element: empty value Which is what I'd expect to see for an rpc/encoded SOAP message. But for doc/literal I would expect: empty value As it is basically assumed the recipient application will know the type from the WSDL and element name. That said, it doesn't seem to be causing any problems. > > > As for your question of complex types support. Axis C++ > > supports most WSDL/XSD features for complex types, and we > > have numerous testcases > > It is wonderful news, thank you. > Do you run the testcases also in Windows? Yes, I test my changes on Windows. The nightly builds are regularly tested on Windows, Linux and AIX, plus I believe other community members test on other platforms.
Re: empty array of complex type crashes the client
Hi, I've just tested your WSDL using the latest 1.6 nighty build with the SOAP message you provided. It worked correctly for 0, 1, 2 and 12 elements within the Array. However, a couple of observations: - your provided WSDL seems to be missing the portType (I presume accidentally deleted when simplify the WSDL file), so I added back in a very simple portType declaration to use your provided messages, etc. - The SOAP response message looks more like an rcp/encoded style message - due to the inclusion of xsi:type="..." - yet your WSDL states doc/literal, however this doesn't cause too much problem as the deserializer for doc/literal will simply ignore these attributes. As for your question of complex types support. Axis C++ supports most WSDL/XSD features for complex types, and we have numerous testcases to detect regressions in any of those features. Of course, there is always scope for improving testcases and adding in support for the remaining features - if you believe you've identified such an item please do let us know. Adrian _______ Adrian Dick ([EMAIL PROTECTED]) Guilhem Tardy <[EMAIL PROTECTED]> wrote on 28/01/2006 02:36:06: > Hi, > > I have attached the WSDL file, as per your request. > > More experimentation showed that it is not just empty arrays. The problem seem > more about complex types. (The Register message, also in WSDL file attached, > uses simple types and works fine.) > > The returned message is: > xsi:type="xsd:string">empty typeempty > value > > Now, according to some documents, I need ComplexTypes in order to ensure WS-I > compliance of my WSDL description. > > Again, could you comment on the support for complex types in Axis C++? > > Thanks, > Guilhem. > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com [attachment "test.wsdl" deleted by Adrian Dick/UK/IBM]
Re: empty array of complex type crashes the client
Hi, I think the complete WSDL will aid in better understanding the problem you're seeing here - plus the SOAP response message that is failing. Thanks, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Guilhem Tardy <[EMAIL PROTECTED]> wrote on 27/01/2006 15:55:36: > Adrian, > > > Looking at your WSDL you're using rpc/literal style messages. > > This was correct, until I made it all document/literal (of the "wrapped" type, > so as to conform to WS-I. > > > > > > > > > > > > > > > > > > > > > > > soapAction="http://test.wsdl#test"/> use="literal"/> use="literal"/> > > (Please let me know if you wish to see the complete WSDL file.) > > Unfortunately, the problem remains. I have tested with the server returning > either of the following: > > http://test.wsdl";> > http://test.wsdl";> > > In both cases, the client crashes. This is unfortunate, because the server is > expected to return no event in most cases. > > Could you comment on the support for complex types in Axis C++? > > Best regards, > Guilhem. > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com
Re: deserialization ??
Hi,
As has been suggested, it sounds like the deserializer has returned NULL,
for a value (based on the code) which cannot be NULL.
I can see from your SOAP message that a value is present, so something must
have happened in the deserializer.
Can you provide the WSDL and SOAP request/responses messages to allow us to
further diagnose the cause?
Adrian
___
Adrian Dick ([EMAIL PROTECTED])
Tomaž Rotovnik <[EMAIL PROTECTED]> wrote on 24/01/2006 13:39:42:
> Then just first test if p_idInstalacije is NULL (I did so).
>
> I beleive that "idInstalacije" should not be null, because you send
> some value. I think I also have some problems with correct order of
> sending parameters. In your case you need to have the next order of
> sending parameters:
>
> idInstalacije
> idUsr
> jezik
> shema
>
> If you have that order than the problem could be in xsd__int
> variable. You should check max and min value that can be asigned (I
> have problems with that also)
>
>
>
> - Original Message -
> From: Primož Führer
> To: Apache AXIS C User List
> Sent: Tuesday, January 24, 2006 10:48 AM
> Subject: Re: deserialization ??
>
> The problem occurs just before delete variable, when it tries to set
> param->idInstalacije = *p_idInstalacije, because p_idInstalacije has
> value null because of the line :
> xsd__int* p_idInstalacije = (pIWSDZ->getElementAsInt
>
> whole method:
>
> int Axis_DeSerialize_UserPrijava(UserPrijava* param,
> IWrapperSoapDeSerializer* pIWSDZ)
> {
> try
> {
> xsd__int* p_idInstalacije =
(pIWSDZ->getElementAsInt("idInstalacije",0));
> param->idInstalacije = *p_idInstalacije; //Error occurs here
> delete p_idInstalacije;
> xsd__int* p_idUsr = (pIWSDZ->getElementAsInt("idUsr",0));
> param->idUsr = *p_idUsr;
> delete p_idUsr;
> xsd__int* p_jezik = (pIWSDZ->getElementAsInt("jezik",0));
> param->jezik = *p_jezik;
> delete p_jezik;
> param->shema = pIWSDZ->getElementAsString("shema",0);
>
> }
> - Original Message -
> From: Tomaž Rotovnik
> To: Apache AXIS C User List
> Sent: Tuesday, January 24, 2006 10:39 AM
> Subject: Re: deserialization ??
>
> Hi
>
> The problem is in deleting allocated variables (calling delete or free)
>
> The code should also be compiled as Multithreaded or Singlethreaded
> DLL (run time library options).
>
>
>
> - Original Message -
> From: Primož Führer
> To: Apache AXIS C User List
> Sent: Tuesday, January 24, 2006 10:30 AM
> Subject: deserialization ??
>
> i'm using web service for login, when i invoke it it creates next
> request and get response:(As response must return id_usr = 30 ,
> id_instalacije = 0,jezik = 1)
>
> problem is in deserialization(i think) where gives exception...
> acces violation at 0x05. as it seems the client don't get back
> values... What could be wrong:
>
> REQUEST
> -
>
> POST /idoc/services/Prijava HTTP/1.1
>
> Host: 192.168.0.210:8080
>
> Content-Type: text/xml; charset=UTF-8
>
> SOAPAction: ""
>
> Content-Length: 462
>
>
>
>
> http://schemas.xmlsoap.org/soap/envelope/
> " xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http:
> //www.w3.org/2001/XMLSchema-instance">
>
> http://192.168.0.210:8080/idoc/services/Prijava";>
> primozf
> primozf
>
>
>
>
> RESPONSE
>
>
> HTTP/1.1 200 OK
>
> Content-Type: text/xml; charset=utf-8
>
> Transfer-Encoding: chunked
>
> Date: Tue, 24 Jan 2006 09:22:14 GMT
>
> Server: Apache Coyote/1.0
>
>
>
> 3ab
>
> http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.
> org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
> ">http://192.168.0.
> 210:8080/idoc/services/Prijava">
> 0
> http://schemas.
> xmlsoap.org/soap/encoding/">30
> http://schemas.
> xmlsoap.org/soap/encoding/">1
> http://schemas.xmlsoap.org/soap/encoding/"/>
>
>
>
>
>
> 0
>
>
>
>
>
>
>
>
Re: Problem while execueting axis c++ client application
Hi, The 1.6 nightly builds does not generate the stubs for the samples. You can do this using the WSDL2Ws tooling, for the calculator samples use the Calculator.wsdl found in /tests/auto_build/testcases/wsdls Adrian ___ Adrian Dick ([EMAIL PROTECTED]) mohan devanoor <[EMAIL PROTECTED]> wrote on 24/01/2006 12:30:25: > hello ; > thanx for dat help. > I have download the nightly build > axis-c-1.6a.n-Win32-trace-bin > But cud not find complete sample programs ... > i can view only client.cpp in client and calculator.cpp in server.. > does this work. > or can u please provide link for nightly build for axis c++ 1.5 > > > > Yahoo! Photos > Got holiday prints? See all the ways to get quality prints in your hands ASAP.
Re: empty array of complex type crashes the client
Hi,
Looking at your WSDL you're using rpc/literal style messages.
Axis c++ supports either rpc/encoded or doc/literal, but not rpc/literal.
Are you in a position to convert the WSDL? If so, I'd recommend
doc/literal as it has been more thoroughly tested and is the option
recommended for WS-I compliance.
Adrian
_______
Adrian Dick ([EMAIL PROTECTED])
Guilhem Tardy <[EMAIL PROTECTED]> wrote on 23/01/2006 17:21:30:
> Hi,
>
> I would very much appreciate if someone confirms that no problem should
arise
> from an empty array:
>
>
> > To aid in understanding the problem you're currently seeing,
> > can you provide the following:
> > - Version of Axis C++
>
> from CVS (last week)
>
> > - WSDL file
>
> corresponding part of WSDL file is below:
>
>
> xmlns:tns="test.wsdl" xmlns="http://schemas.xmlsoap.org/wsdl/";
> xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
>
>
>
>
>
> This object contains two strings : the first
> identifies the event type, the secont gives details abount the
> event.
>
>
>
>
>
>
>
>
>
>
> Used as a return type in the Advertise
procedure.
> This array contains events about availability changes of contacts and
> invitations, it may be used otherwise in the future.
>
>
>maxOccurs="unbounded" minOccurs="0">
>
>
>
>
>
> See Advertise porttype, EventArray and
> EventSequenceObject
>
> See Advertise porttype, EventList and
>
>
>
>
> See Advertise porttype, EventArray and
> EventSequenceObject
>
>
>
>
>
> transport="http://schemas.xmlsoap.org/soap/http"/>
> soapAction="test.wsdl#Advertise"/> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> namespace="test.wsdl"/> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> namespace="test.wsdl"/>
>
>
>
>
> Note that the above has but I expect no
relation to
> the current problem, does it?
>
> - SOAP request/response for the failing situation
>
> Since Axis C++ client crashes, I get little debug info. Below is
> extract of the
> server (not Axis).
>
> I can send the complete WSDL file, request/response (seen by server) and
> relevant Etheral dump at client privately. Just let me know if you need
it.
>
> The request received by server:
>
> params:
> array(2) {
> ["Status"]=>
> string(32) "a75514999f8dc847cfc6035e89750728"
> ["AuthTicket"]=>
> string(1) "0"
> }
>
> This calls the corresponding method at server:
>
> methodreturn:
> array(0) {
> }
>
> Therefore...
>
> no value provided for complexType element EventElement and element is not
> nillable, so serialize nothing
> returning:
>
> serializing response
> have WSDL for serialization: style is rpc
> style is rpc for serialization: use is literal
> In Envelope length=104 body (max 1000 characters)= xmlns="test.wsdl"> style=rpc use=
> encodingStyle=http://schemas.xmlsoap.org/soap/encoding/
> headers:
> string(0) ""
> namespaces:
> array(0) {
> }
>
> Best regards,
> Guilhem.
>
> __
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
Re: Problem while execueting axis c++ client application
Hi, A lot of work has been done in the area of memory management since Axis c++ 1.5, you may wish to try with the latest nightly build. Adrian ___ Adrian Dick ([EMAIL PROTECTED]) mohan devanoor <[EMAIL PROTECTED]> wrote on 24/01/2006 05:22:28: > hello , > i use Apache 2 , axis c++ and Microsoft Visual C++ 6.0 > when i compile and run a client application i do get a error message > and application terminates can any one help me please.. > > Error message: > The instruction at 0x0040175d referenced memory at 0x . The > memory could not be read. > i hav started debugging it . The problem is within the webservice method at > > m_pCall->unInitialize(); > xsd__int r = *Ret; > delete Ret; > return r; > > i also compiled by debug option "/MD" but couldnt find solution.. > can any one help.. > > What are the most popular cars? Find out at Yahoo! Autos
Re: Still problem in wsdl2ws code generation
Hi, In Axis C++ 1.5 these message will appear for every anonymous type found in the WSDL, they are simply information messages and can be safely ignored. The latest 1.6 nightly builds no longer give this message, if you wish to try a later version. Adrian ___ Adrian Dick ([EMAIL PROTECTED]) mohan devanoor <[EMAIL PROTECTED]> wrote on 23/01/2006 14:08:10: > hello, > as u said i hav downloaded all the jar files required to run wsdl2ws > > wsdl2ws.jar > > axis.jar > > axis-ant.jar > > jaxrpc.jar > > log4j-1.2.8.jar > > saaj.jar > > wsdl4j-1.5.1.jar > > mail.jar > > activation.jar > still same error > > c:\>java org.apache.axis.wsdl.wsdl2ws.WSDL2Ws hello.wsdl -o. > /ClientOut -lc++ -sclient > ignoring anonymous type >welcome > ignoring anonymous type >welcomeResponse > > Code generation completed. > > please can any give a solution to this problem > > Yahoo! Autos. Looking for a sweet ride? Get pricing, reviews, & more > on new and used cars.
Re: possible problem with xmlns fields in Envelope
Hi, If I've understood correct, the problem you're seeing is the client is expecting an xsi:type="..." field when deserializing elements, yet your SOAP message doesn't contain this detail? This sounds like your client is expecting an rpc/encoded style SOAP message, yet you're receiving a doc/literal style SOAP message. If you can provide the WSDL used to generate your stubs, and the SOAP request/response messages we will be better able to understand the problem. Adrian _______ Adrian Dick ([EMAIL PROTECTED]) Guilhem Tardy <[EMAIL PROTECTED]> wrote on 22/01/2006 02:00:50: > An update on my earlier email. > > The problem was indeed with missing types in the response. > > I couldn't say if it is standard or not to omit this information from SOAP > messages when it can be obtained otherwise (through WSDL), but Axis C++ client > requires the type. This is actually implied by a comment in the source code. > > I "fixed" the server, so that it includes the type even for well > known 'string' > from standard XLMSchema. > > Regards, > Guilhem. > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com
Re: empty array of complex type crashes the client
Hi, To aid in understanding the problem you're currently seeing, can you provide the following: - Version of Axis C++ - WSDL file - SOAP request/response for the failing situation Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Guilhem Tardy <[EMAIL PROTECTED]> wrote on 22/01/2006 16:00:44: > Hi, > > I just discovered that the AxisClient throws an exception and crashes when > receiving an empty array of complex type (Event: a pair of strings). > > Unfortunately, this is the normal return value for one operation if > there is no > new "Event" to handle. > > Any suggestion to solve or workaround this problem? > > Regards, > Guilhem. > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com
Re: Failure of Google Search API web service using Axis
Hi, Comparing your SOAP request to the WSDL, it would appear the message parts have been sent in the wrong order, hence the Fault message you're receiving from the server. The WSDL defines the order as: key, q, start, maxResults, filer, restrict, safeSearch, lr, ie, oe While the SOAP request is sending: filter, key, restrict, start, ie, safeSearch, lr, maxResults, oe, q This sounds like a problem within Axis C, which will need to looking into. It's not a problem I'm previously aware of, but have you tried using the Axis C++ 1.6 nightly builds, to see if it has been resolved? If not, can you raise a Jira, attaching the SOAP messages and WSDL, to aid investigation. ( Jira can be accessed here: http://issues.apache.org/jira/browse/AXISCPP ) Adrian _______ Adrian Dick ([EMAIL PROTECTED]) Ashutosh Kumar <[EMAIL PROTECTED]> wrote on 18/01/2006 09:08:05: > Hi ! > Enclosed here are the serialized SOAP request and response that my > machine is sending/receiving to/from the server. Please help me > identify the probable error in the Soap data being send to the Google Server. > > > File being send > ** > POST http://api.google.com/search/beta2 HTTP/1.1 > Host: api.google.com:80 > Content-Type: text/xml; charset=UTF-8 > SOAPAction: "urn:GoogleSearchAction" > Content-Length: 784 > > > http://schemas.xmlsoap.org/soap/envelope/ > " xmlns:xsd=" http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http: > //www.w3.org/2001/XMLSchema-instance"> > > > true > GOOGLE KEY > > 0 > UTF-8 > true > lang_en > 10 > UTF-8 > QUERY TERM > > > > > File received from server > > HTTP/1.1 500 Internal Server Error > Content-Type: text/xml; charset=utf-8 > Cache-control: private > Transfer-Encoding: chunked > Date: Wed, 18 Jan 2006 08:46:06 GMT > Server: GFE/1.3 > Cneonction: Close > 6b9 > > http://schemas.xmlsoap.org/soap/envelope/ > " xmlns:xsi=" http://www.w3.org/1999/XMLSchema-instance"; xmlns:xsd=" > http://www.w3.org/1999/XMLSchema";> > > > SOAP-ENV:Server > Exception while handling service request: com.google. > soap.search.GoogleSearchService.doGoogleSearch(boolean,java.lang. > String,java.lang.String,int,java.lang.String,boolean,java.lang. > String,int,java.lang.String ,java.lang.String) -- no signature > match > /search/beta2 > > java.lang.NoSuchMethodException: com.google.soap.search. > GoogleSearchService.doGoogleSearch (boolean,java.lang.String,java. > lang.String,int,java.lang.String,boolean,java.lang.String,int,java. > lang.String,java.lang.String) -- no signature match > at org.apache.soap.util.MethodUtils.getEntryPoint(MethodUtils.java:194) > at org.apache.soap.util.MethodUtils.getMethod(MethodUtils.java:548) > at org.apache.soap.util.MethodUtils.getMethod(MethodUtils.java:528) > at org.apache.soap.server.RPCRouter.invoke(RPCRouter.java:114) > at org.apache.soap.providers.RPCJavaProvider.invoke > (RPCJavaProvider.java:129) > at org.apache.soap.server.http.RPCRouterServlet. > doPost(RPCRouterServlet.java:288) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) > at javax.servlet.http.HttpServlet.service (HttpServlet.java:802) > at com.google.gse.HttpConnection.runServlet(HttpConnection.java:436) > at com.google.gse.HttpConnection.run(HttpConnection.java:376) > at com.google.gse.DispatchQueue$WorkerThread.run(DispatchQueue.java :254) > > > > > Thanks & Regards > Ashutosh Kumar > > On 1/17/06, Adrian Dick <[EMAIL PROTECTED]> wrote: > Hi, > > > I need the "on-the-wire" request/response messages to fully determine the > problem. > > However, based on your description it sounds like you received a Fault back > from the server, rather than the expected response. This will cause an > exception to be thrown, but the generated stub should be catching this, > determining it's a Fault and deserializing the fault. > > In turn this will be thrown and should be caught by your application. > As your WSDL (below) doesn't specify any Faults you will need to catch > "OtherFaultException". Using the method getFaultDetail on this will give > the contents of the fault detail received. > > Knowing the detail returned in the Fault will aid in diagnosing the > problem, but having the request/responses messages will be particularly > useful. > > Adrian > ___ > Adrian Dick ([EMAIL PROTECTED]) > > > Ashutosh Kumar <[EMAIL PROTECTED] > wrote on 17/01/2006 09:34:28: > > > Hi Adrian, > > I am using "axis-c-src-1-5-wi
Re: Failure of Google Search API web service using Axis
Hi,
I need the "on-the-wire" request/response messages to fully determine the
problem.
However, based on your description it sounds like you received a Fault back
from the server, rather than the expected response. This will cause an
exception to be thrown, but the generated stub should be catching this,
determining it's a Fault and deserializing the fault.
In turn this will be thrown and should be caught by your application.
As your WSDL (below) doesn't specify any Faults you will need to catch
"OtherFaultException". Using the method getFaultDetail on this will give
the contents of the fault detail received.
Knowing the detail returned in the Fault will aid in diagnosing the
problem, but having the request/responses messages will be particularly
useful.
Adrian
_______
Adrian Dick ([EMAIL PROTECTED])
Ashutosh Kumar <[EMAIL PROTECTED]> wrote on 17/01/2006 09:34:28:
> Hi Adrian,
> I am using "axis-c-src-1-5-win32" for my project and I am getting
> "abnormal termination of program" when using Google Search API in my
> C++ code generated using Axis, GoogleSearch.wsdl (copy of which is
> enclosed here with the mail) and Eclipse to generate client side
> stubs. In the project when I am calling
> m_pcall->checkMessage("doGoogleSearchResponse", "urn:GoogleSearch");
>
> Inside this function,
>
> soapdeserialiser::checkmessagebody() function is called and inside
> this function, the condition
>
> if (0 != strcmp (m_pNode->m_pchNameOrValue, pName))
>
> fails as the value stored in
>
> m_pNode->m_pchNameOrValue = "Fault" & pName =
> "doGoogleSearchResponse". This leads to exception and untimely
> termination of the program. I need to know when does this "m_pnode"
> gets popultated and this value Fault is coming from the wsdl file or
> is getting populated while execution of the program.
>
> The wsdl file being used is
> **
>
> -
> -
> - xmlns:typens="urn:GoogleSearch " xmlns:xsd="
http://www.w3.org/2001/XMLSchema";
> xmlns:soap=" http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:soapenc="
> http://schemas.xmlsoap.org/soap/encoding/ " xmlns:wsdl=" http:
> //schemas.xmlsoap.org/wsdl/" xmlns ="http://schemas.xmlsoap.org/wsdl/"; >
> -
> -
> - http://www.w3.org/2001/XMLSchema"; targetNamespace
="
> urn:GoogleSearch">
> -
> -
>
>
>
>
>
>
>
>
>
>
>
>
>
> -
> -
>
>
>
>
>
>
>
>
>
>
>
> -
> -
> -
>
>
>
>
> -
> -
> -
>
>
>
>
> -
> -
>
>
>
>
>
>
> -
> -
>
>
>
> -
>
>
> -
>
>
>
> -
>
>
> -
> -
>
>
>
>
>
>
>
>
>
>
>
> -
>
>
> -
> -
> -
>
>
>
> -
>
>
>
> -
>
>
>
>
> -
> -
> http://schemas.xmlsoap.org/soap/http
> " />
> -
>
> -
> http://schemas.xmlsoap.org/soap/encoding/"; />
>
> -
> http://schemas.xmlsoap.org/soap/encoding/"; />
>
>
> -
>
> -
> http://schemas.xmlsoap.org/soap/encoding/"; />
>
> -
> http://schemas.xmlsoap.org/soap/encoding/"; />
>
>
> -
>
> -
> http://schemas.xmlsoap.org/soap/encoding/"; />
>
> -
> http://schemas.xmlsoap.org/soap/encoding/"; />
>
>
>
> -
> -
> -
> http://api.google.com/search/beta2 " />
>
>
>
> ***
>
> Please reply with the probable solution and also with the reason how
> this value Fault is coming into picture.
>
> Thanks & Regards
> Ashutosh
>
>
> On 1/16/06, Adrian Dick <[EMAIL PROTECTED]> wrote:
> Hi,
>
> This sounds like the received message doesn't match the expected.
>
> Can you capture the server response message? Then it will be possible to
> compare with the WSDL and generated stubs for the expected response.
> ( You can use org.apache.axis.utils.tcpmon, within axis.jar, as part of
the
> WSDL2Ws tooling).
>
> Also, can you confirm which version of Axis C++ you're using.
>
> Adrian
> ___
> Adrian Dick ([EMAIL PROTECTED])
>
>
> Ashutosh Kumar <[EMAIL PROTECTED] > wrote on 16/01/2006 09:57:09:
>
> > Hi !
> > I am trying to call google search api in my c++ clinet code
> > generated using GoogleSearch.wsdl, axis and eclipse. The query being
> > made is as follows
> >
> > doGoogleSearch(true,license key,"",0,utf-8,true,"",10,utf-8,query
term);
> >
> > which in turn is calling GoogleSearchPort::doGoogleSearch() and
> > inside this function it is failing while calling
> >
> > m_pCall->checkMessage("doGoogleSearchResponse", "urn:GoogleSearch").
> >
> > The Debug error that I am getting is "abnormal program termination".
> > This error message is set after the failure of checkMessageBody()
> > function in SoapDeserializer.cpp file of axis/soap.
> >
> > Could you provide some help in this matter.
> >
> > Thanks & Regards
> > Ashutosh Kumar
> >
Re: Failure of Google Search API web service using Axis
Hi,
This sounds like the received message doesn't match the expected.
Can you capture the server response message? Then it will be possible to
compare with the WSDL and generated stubs for the expected response.
( You can use org.apache.axis.utils.tcpmon, within axis.jar, as part of the
WSDL2Ws tooling).
Also, can you confirm which version of Axis C++ you're using.
Adrian
_______
Adrian Dick ([EMAIL PROTECTED])
Ashutosh Kumar <[EMAIL PROTECTED]> wrote on 16/01/2006 09:57:09:
> Hi !
> I am trying to call google search api in my c++ clinet code
> generated using GoogleSearch.wsdl, axis and eclipse. The query being
> made is as follows
>
> doGoogleSearch(true,license key,"",0,utf-8,true,"",10,utf-8,query term);
>
> which in turn is calling GoogleSearchPort::doGoogleSearch() and
> inside this function it is failing while calling
>
> m_pCall->checkMessage("doGoogleSearchResponse", "urn:GoogleSearch").
>
> The Debug error that I am getting is "abnormal program termination".
> This error message is set after the failure of checkMessageBody()
> function in SoapDeserializer.cpp file of axis/soap.
>
> Could you provide some help in this matter.
>
> Thanks & Regards
> Ashutosh Kumar
>
Re: WSDL2Ws and Attachment
Hi, The code you describe below is not valid, suggesting there is a problem within WSDL2Ws. To aid finding the problem can you confirm which version of Axis c++ you're using? Also, it would be useful if you could attach your WSDL, so we can attempt to reproduce the problem. Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Jinshan Li <[EMAIL PROTECTED]> wrote on 14/01/2006 07:00:19: > I use WSDL2Ws to generate a c++ stub, the following function is > generated. Is it OK, there is not parameter name and type? > > void MessagePort::service(, AXIS_OUT_PARAM usrType** OutValue0, > AXIS_OUT_PARAM optType** OutValue1) > > -- > http://www.goldensoft.net
Re: WSDL2Ws and Vectors
Hi,
Axis C++ doesn't provide explicit support for
{http://xml.apache.org/xml-soap}Vector.
That is, we support all of the xsd built-in simple types (and arrays of
them), then the WSDL2Ws tool generates classes based on the schema
definition for all other types within a WSDL.
Could there be a problem with the way in which the schema for Vector is
imported into the WSDL?
Regards,
Adrian
___
Adrian Dick ([EMAIL PROTECTED])
Keith <[EMAIL PROTECTED]> wrote on 05/01/2006 03:12:52:
> I have a WSDL that defines methods that take and return Vectors. I’
> m trying to use Axis to create a C++ client but I get the following
> message when trying to create the C++ code from my WSDL:
>
> org.apache.axis.wsdl.wsdl2ws.WrapperFault: unregisterd type {http:
> //xml.apache.org/xml-soap}Vector refered
> at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.
> createParameterInfo(Unknown Source)
> at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.
> addRPCStyleOutputMessageToMethodInfo(Unknown Source)
> at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.setMethodInfo(Unknown
Source)
> at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.getServiceInfo(Unknown
Source)
> at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.
> generateWrappers(Unknown Source)
> at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.main(Unknown Source)
>
> Is Vector just not yet supported?
>
> On a side note, I’m assuming that “unregisterd” and “refered” are
> simple spelling mistakes.
>
> Thanks,
> Keith
>
RE: stub transport
Hi, To stop the mock server you should actually use the following command: java org.apache.test.StopMockServer -p -h Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) "Stettler, Robert" <[EMAIL PROTECTED]> wrote on 19/12/2005 12:48:15: > Sweet! Exactly what I was looking for. > > -Original Message- > From: Adrian Dick [mailto:[EMAIL PROTECTED] > Sent: Monday, December 19, 2005 5:45 AM > To: Apache AXIS C User List > Subject: RE: stub transport > > Hi, > > Here are some simple instruction on using the MockServer utility we use > for > testing Axis c++ client without a server. >Compile mock server java code (found within >/tests/utils/monitor ) >Run the mock server: >java org.apache.test.MockServer -p -r > > The server response file is a text file containing the full HTTP > response, > it will look something like this: >HTTP/1.1 200 OK >Server: WebSphere Application Server/5.1 >Content-Type: text/xml; charset=utf-8 >Content-Language: en-GB >Transfer-Encoding: chunked > >1ad > >xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; >xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; >xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>< > soapenv:Body> > xmlns="http://localhost/axis/Calculator";>5 sponse> >0 > > > The easiest way to generate this file is to capture the communication > from > a real server but if that isn't possible you will need to generate by > hand > (plenty of examples within root>/test/auto_build/testcases/output > ) > Rather than providing the specific chunk size (1ad, on the line ahead of > the payload) you can provide ### and the MockServer will calculate the > correct size. > > If your testcase makes multiple calls to the web service, you can simply > append all the requests (in the correct order!) within the server > response > file. > > Once the test has been completed you need to run the following: >java org.apache.test.StopTCPMonitor -p -h > > I hope that is of help > Adrian > > ___ > Adrian Dick ([EMAIL PROTECTED]) > > > "Stettler, Robert" <[EMAIL PROTECTED]> wrote on 16/12/2005 > 14:00:42: > > > I have 1.5 Final source. > > > > -Original Message- > > From: John Hawkins [mailto:[EMAIL PROTECTED] > > Sent: Friday, December 16, 2005 5:09 AM > > To: Apache AXIS C User List > > Subject: RE: stub transport > > > > > > hi Robert, > > > > no docs as it's an internal tool used within the test framework. Do > > you use the source or binaries? It's not shipped with the binaries.. > > > > > > > > > "Stettler, Robert" <[EMAIL PROTECTED]> > > 14/12/2005 16:51 > > > > Please respond to > > "Apache AXIS C User List" > > > > To > > > > "Apache AXIS C User List" > > > > cc > > > > > > > > Subject > > > > RE: stub transport > > > > > > > > > > > > > > > > > > > > > > I am looking for a simple solution to simulate the server side, so > > that I can test my client code completely. I know I can create > > apache stubs and I have generated stubs in WebLogic, but I am > > looking for something simpler. > > > > > > You meantioned a unit test system? Can you point me to some doc? > > > > -Original Message- > > From: John Hawkins [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, December 14, 2005 11:40 AM > > To: Apache AXIS C User List > > Subject: Re: stub transport > > > > > > hi Robert, > > sorry unit testing of what - the service? So you want to emulate a > > client? We currently have a "unit test" system where we can emulate > > the service. > > > > "Stettler, Robert" <[EMAIL PROTECTED]> > > 14/12/2005 14:37 > > > > > > Please respond to > > "Apache AXIS C User List" > > > > > > > > To > > > > > > > > cc > > > > > > > > Subject > > > > stub transport > > > > > > > > > > > > > > > > > > > > > > > > > > > > Is there any sort of stub http transport? Maybe something file > > driven? I
RE: stub transport
Hi, Here are some simple instruction on using the MockServer utility we use for testing Axis c++ client without a server. Compile mock server java code (found within /tests/utils/monitor ) Run the mock server: java org.apache.test.MockServer -p -r The server response file is a text file containing the full HTTP response, it will look something like this: HTTP/1.1 200 OK Server: WebSphere Application Server/5.1 Content-Type: text/xml; charset=utf-8 Content-Language: en-GB Transfer-Encoding: chunked 1ad http://schemas.xmlsoap.org/soap/envelope/"; xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>http://localhost/axis/Calculator";>5 0 The easiest way to generate this file is to capture the communication from a real server but if that isn't possible you will need to generate by hand (plenty of examples within /test/auto_build/testcases/output ) Rather than providing the specific chunk size (1ad, on the line ahead of the payload) you can provide ### and the MockServer will calculate the correct size. If your testcase makes multiple calls to the web service, you can simply append all the requests (in the correct order!) within the server response file. Once the test has been completed you need to run the following: java org.apache.test.StopTCPMonitor -p -h I hope that is of help Adrian ___ Adrian Dick ([EMAIL PROTECTED]) "Stettler, Robert" <[EMAIL PROTECTED]> wrote on 16/12/2005 14:00:42: > I have 1.5 Final source. > > -Original Message- > From: John Hawkins [mailto:[EMAIL PROTECTED] > Sent: Friday, December 16, 2005 5:09 AM > To: Apache AXIS C User List > Subject: RE: stub transport > > > hi Robert, > > no docs as it's an internal tool used within the test framework. Do > you use the source or binaries? It's not shipped with the binaries.. > > > > "Stettler, Robert" <[EMAIL PROTECTED]> > 14/12/2005 16:51 > > Please respond to > "Apache AXIS C User List" > > To > > "Apache AXIS C User List" > > cc > > > > Subject > > RE: stub transport > > > > > > > > > > > I am looking for a simple solution to simulate the server side, so > that I can test my client code completely. I know I can create > apache stubs and I have generated stubs in WebLogic, but I am > looking for something simpler. > > > You meantioned a unit test system? Can you point me to some doc? > > -Original Message- > From: John Hawkins [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 14, 2005 11:40 AM > To: Apache AXIS C User List > Subject: Re: stub transport > > > hi Robert, > sorry unit testing of what - the service? So you want to emulate a > client? We currently have a "unit test" system where we can emulate > the service. > > "Stettler, Robert" <[EMAIL PROTECTED]> > 14/12/2005 14:37 > > > Please respond to > "Apache AXIS C User List" > > > > To > > > > cc > > > > Subject > > stub transport > > > > > > > > > > > > > > Is there any sort of stub http transport? Maybe something file > driven? I would like to use something like that for unit testing? > > > > > > The information contained in this e-mail is confidential and/or proprietary > to Capital One and/or its affiliates. The information transmitted herewith > is intended only for use by the individual or entity to which it is > addressed. If the reader of this message is not the intended recipient, > you are hereby notified that any review, retransmission, dissemination, > distribution, copying or other use of, or taking of any action in reliance > upon this information is strictly prohibited. If you have received this > communication in error, please contact the sender and delete the material > from your computer. > > > > The information contained in this e-mail is confidential and/or proprietary > to Capital One and/or its affiliates. The information transmitted herewith > is intended only for use by the individual or entity to which it is > addressed. If the reader of this message is not the intended recipient, > you are hereby notified that any review, retransmission, dissemination, > distribution, copying or other use of, or taking of any action in reliance > upon this information is strictly prohibited. If you have received this > communication in error, please contact the sender and delete the material > from your computer. > >
Re: Use of DataHandler in a webservice
Sorry, for not making it clear. I updated the example code sent by John
below.
Adrian
___
Adrian Dick ([EMAIL PROTECTED])
Arnault BELLINA <[EMAIL PROTECTED]> wrote on 16/12/2005 12:57:14:
> Thanks John for your Answer. It will be very usefull !
> Adrian : which code do you update ? The example code or the axis source
code ?
> Do I have to download another time the Axis cpp 1.6 a on http:
> //cvs.apache.org/dist/axis/nightly ?
>
> Thanks for your answer
>
> Arnault
>
> Adrian Dick <[EMAIL PROTECTED]> a écrit :
> The example originally attached won't work with some recent changes, so
> I've updated with the correct code.
>
> Adrian
> ___
> Adrian Dick ([EMAIL PROTECTED])
>
>
> John Hawkins/UK/[EMAIL PROTECTED] wrote on 16/12/2005 10:49:19:
>
> >
> > Hi,
> >
> > OK, so Now that I've woken up !
> >
> > No, we shouldn't be creating the datahandler class (yo u are correct
> > :-) And in the latest build we don't. We have a number of
> > datahandler tests and they appear to be working fine on the latest
> > build. May I suggest you try out the latest build -> http://ws.
> > apache.org/axis/interim.html.
> >
> > And see if you still get the same problem. Don't worry that this is
> > not a full release - we are due to ship the 1.6 release pretty soon
> > (end of month?). I didn't run through the 1.5 code however, it might
> > be possible to just throw out the extra Datahandler class if you can
> > see that the ISoapAttachment class is being used on the service?
> >
> > This is a sample from one of our tests ->
> > (ISoapAttachment is the Datahandler object described in WSDL)
> >
>
>
> > ISoapAttachment *att=ws.createSoapAttachment();
> >
> > char *text=stringToAscii("This is a
> > test message for attachment");
> >
> > //Adding the content type as text/plain
> >
> att->addHeader(AXIS_CONTENT_TYPE,"text/plain"
> > );
> > xsd__base64Binary b64b1;
> b64b1.set((xsd__unsignedByte*)text,
> strlen(text));
> > att->addBody(&b64b1);
> > //Calling the dataHandlerService,
> > service will return content
> > Result=ws.echoContent(att);
>
> >
>
>
> >
> >
> > cheers,
> > John.
> >
> >
> >
> >
>
> >
> > Arnault BELLINA
> > 16/12/2005 09:59
> >
> > Please respond to
> > "Apache AXIS C User List"
> >
> > To
> >
> > Apache AXIS C User List
> >
> > cc
> >
> > Subject
> >
> > Re: Use of DataHandler in a webservice
> >
> >
> >
> >
> > I'm using the current axis cpp version (I guess the 1.5)
> > thanks for your help.
> >
> > this is the wsdl :
> >
> >
> >
> > xmlns:intf="urn:Message"
xmlns:apachesoap="http://xml.apache.org/xml-soap
> > " xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:xsd="
> > http://www.w3.org/2001/XMLSchema";
> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/
> > ">
> >
> &g t;
> >
> > targetNamespace="urn:Message" elementFormDefault="qualified">
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> location="http://localhost:8080/services/Message"/>
> >
> >
> >
> >
> >
> >
> >
> > John Hawkins a écrit :
> >
> > Hi,
> > please could you send the whole wsdl. Yes creation of the
> > datahandler classes is normal
> >
> > What version of axis cpp are you using ?
> >
> >
>
> >
> > Arnault BELLINA
> > 16/12/2005 09:33
> >
> > Please respond to
>
Re: Use of DataHandler in a webservice
The example originally attached won't work with some recent changes, so
I've updated with the correct code.
Adrian
_______
Adrian Dick ([EMAIL PROTECTED])
John Hawkins/UK/[EMAIL PROTECTED] wrote on 16/12/2005 10:49:19:
>
> Hi,
>
> OK, so Now that I've woken up !
>
> No, we shouldn't be creating the datahandler class (you are correct
> :-) And in the latest build we don't. We have a number of
> datahandler tests and they appear to be working fine on the latest
> build. May I suggest you try out the latest build -> http://ws.
> apache.org/axis/interim.html.
>
> And see if you still get the same problem. Don't worry that this is
> not a full release - we are due to ship the 1.6 release pretty soon
> (end of month?). I didn't run through the 1.5 code however, it might
> be possible to just throw out the extra Datahandler class if you can
> see that the ISoapAttachment class is being used on the service?
>
> This is a sample from one of our tests ->
> (ISoapAttachment is the Datahandler object described in WSDL)
>
> ISoapAttachment *att=ws.createSoapAttachment();
>
> char *text=stringToAscii("This is a
> test message for attachment");
>
> //Adding the content type as text/plain
>
att->addHeader(AXIS_CONTENT_TYPE,"text/plain"
> );
> xsd__base64Binary b64b1;
b64b1.set((xsd__unsignedByte*)text,
strlen(text));
> att->addBody(&b64b1);
> //Calling the dataHandlerService,
> service will return content
> Result=ws.echoContent(att);
>
>
>
> cheers,
> John.
>
>
>
>
>
> Arnault BELLINA <[EMAIL PROTECTED]>
> 16/12/2005 09:59
>
> Please respond to
> "Apache AXIS C User List"
>
> To
>
> Apache AXIS C User List
>
> cc
>
> Subject
>
> Re: Use of DataHandler in a webservice
>
>
>
>
> I'm using the current axis cpp version (I guess the 1.5)
> thanks for your help.
>
> this is the wsdl :
>
>
> xmlns:intf="urn:Message" xmlns:apachesoap="http://xml.apache.org/xml-soap
> " xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:xsd="
> http://www.w3.org/2001/XMLSchema";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/
> ">
>
>
> http://www.w3.org/2001/XMLSchema";
> targetNamespace="urn:Message" elementFormDefault="qualified">
> http://xml.apache.org/xml-soap"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> http://schemas.
> xmlsoap.org/soap/http"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> http://localhost:8080/services/Message"/>
>
>
>
>
>
>
>
> John Hawkins <[EMAIL PROTECTED]> a écrit :
>
> Hi,
> please could you send the whole wsdl. Yes creation of the
> datahandler classes is normal
>
> What version of axis cpp are you using ?
>
>
>
> Arnault BELLINA <[EMAIL PROTECTED]>
> 16/12/2005 09:33
>
> Please respond to
> "Apache AXIS C User List"
>
> To
>
> axis-c-user@ws.apache.org
>
> cc
>
> Subject
>
> Use of DataHandler in a webservice
>
>
>
>
>
>
>
> Hello all !
>
> I have a WSDL interface from a Web Service (AXIS-based).
> A web service accepts a file as an attachment and a string and return an
int.
> I got the wsdl from this service (see at the end of the mail).
>
> As soon as I try to create the client stub for this WSDL I get a
> possible error of DataHandler use :
>
> Possible error in class DataHandler: class with no
> attributes
> Possible error in class DataHandler: class with no
> attributes
>
> The webservice is in Doc mode, can I use d
Re: Where to put AxisClient.dll?
Hi, Visual C++ uses the system path to locate libraries, so you will need to ensure the Axis C++ libraries can be found on that path. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Pico Florin <[EMAIL PROTECTED]> wrote on 27/10/2005 14:58:36: > Hi! > I have a problem with my Axis C++ client. I cannot starting from > Visual C++ 6.0 because a message error is shown: >"This application has failed to satrt because AxisClient.dll was > not found. Re-installing the application may fix the problem". > Thank you, > Florin > > How much free photo storage do you get? Store your holiday snaps for > FREE with Yahoo! Photos. Get Yahoo! Photos
RE: xsd__string always null
Hi,
I believe we would only need to modify the if(...) on line 2551 of
SoapDeSerializer.cpp (within getXSDType() ) to also include URI_ENC.
Regards,
Adrian
___
Adrian Dick ([EMAIL PROTECTED])
John Hawkins/UK/[EMAIL PROTECTED] wrote on 25/10/2005 18:22:08:
>
> Why can't we handle soapenc?
>
>
>
>
> "Dushshantha Chandradasa" <[EMAIL PROTECTED]>
> 25/10/2005 13:14
>
> Please respond to
> "Apache AXIS C User List"
>
> To
>
> "Apache AXIS C User List"
>
> cc
>
> Subject
>
> RE: xsd__string always null
>
>
>
>
> Hi Chris,
>
> Your problem here is the namespace soapenc. C++ client cannot understand
> soapenc:string. It can unserstand xsd:string. If you can ask the java
> service to send the response as xsd:string, C++ will work properly. You
> can do that by making the following change in server-config.wsdd of your
> service.
>
>
>
> This will prevent the Java service sending soapenc:string.
>
> Thanks,
> Dushshantha
>
> -Original Message-
> From: Christopher S. Johnson [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, October 25, 2005 5:49 PM
> To: axis-c-user@ws.apache.org
> Subject: xsd__string always null
>
> All -
>
> I have a java web service server and a C++ client, it seems from
> following
> the http stream that the service is working (simple getVersion service)
> but it seems that that xsd__string that is returned is always null.
>
> I'm doing something like this..
>
> Any ideas would be helpful.
>
> Thanks..
>
> Version v;
> xsd__string s;
> s = v.getVersion();
> printf("%s\n",s);
>
> the ouput is (null)
>
>
> POST /axis/services/Version HTTP/1.1
> Host: 192.168.12.113:80
> Content-Type: text/xml; charset=UTF-8
> SOAPAction: ""
> Content-Length: 364
>
>
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>
> http://192.168.12.113/axis/services/Version";>
>
>
>
>
> HTTP/1.1 200 OK
> Date: Tue, 25 Oct 2005 12:35:27 GMT
> Content-Type: text/xml;charset=utf-8
> Content-Length: 632
>
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>
> soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> xmlns:ns1="http://192.168.12.113/axis/services/Version";>
>xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>Apache Axis
> version: 1.2RC3
> Built on Feb 28, 2005 (10:15:14 EST)
>
>
>
