Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 1.6 Alpha
    • Fix Version/s: None
    • Labels:
      None
    • Environment:
      Windows and linux

      Description

      Develop a pull parser that will support atleast UTF-8 and UTF-16 encoding with a clear seperation at the parser abstraction level so as to introduce a third parser available for Axis

      1. build_files.tar.gz
        5 kB
        Dinesh Weerapurage
      2. guththila_src.tar.gz
        12 kB
        Dinesh Weerapurage
      3. guththila_xml.tar.gz
        2 kB
        Dinesh Weerapurage

        Issue Links

          Activity

          Hide
          Samisa Abeysinghe added a comment -

          All the sources and build related stuff has been committed to CVS.

          Testing of the Guththila implementation has to be done and would be addressed by the sub-task that I created.

          Show
          Samisa Abeysinghe added a comment - All the sources and build related stuff has been committed to CVS. Testing of the Guththila implementation has to be done and would be addressed by the sub-task that I created.
          Hide
          Samisa Abeysinghe added a comment -

          I commited the latest stuff, including the build script changes. The testing is in progress. Please do your own testing to verify that I have put in all the correct changes.

          Also, now that the files are there, in the future, when you post changes, please post them as diffs againt the latest CVS. (you can do this by running "cvs diff" in the sub folder of the source tree (e.g. in src/xml/guththila) You can also run this for each file seperately.

          Show
          Samisa Abeysinghe added a comment - I commited the latest stuff, including the build script changes. The testing is in progress. Please do your own testing to verify that I have put in all the correct changes. Also, now that the files are there, in the future, when you post changes, please post them as diffs againt the latest CVS. (you can do this by running "cvs diff" in the sub folder of the source tree (e.g. in src/xml/guththila) You can also run this for each file seperately.
          Hide
          Dinesh Weerapurage added a comment -

          Hi,
          I check them again, the remainning files are latest. Thanks a lot for removing out dated attachments.
          kind regards,
          Dinesh

          Show
          Dinesh Weerapurage added a comment - Hi, I check them again, the remainning files are latest. Thanks a lot for removing out dated attachments. kind regards, Dinesh
          Hide
          Samisa Abeysinghe added a comment -

          I removed the outdated attachments. Please veryfy the remining ones are the latest so that I could commit them

          Show
          Samisa Abeysinghe added a comment - I removed the outdated attachments. Please veryfy the remining ones are the latest so that I could commit them
          Hide
          Dinesh Weerapurage added a comment -

          Hi,
          Sorry for the inconvenience occurred. I tried to remove outdated attachments but if I'm not mistaken I didn't see any option like remove. In that page I noticed

          "This page allows you to manage the attachments for a particular issue. Only users with administrative privileges to remove an issue can remove attachments."

          I suppose, I'm not a user with administrative privileges. Could we find an user with administrative privileges to remove outdated attachments, please?

          thanks,
          Dinesh

          Show
          Dinesh Weerapurage added a comment - Hi, Sorry for the inconvenience occurred. I tried to remove outdated attachments but if I'm not mistaken I didn't see any option like remove. In that page I noticed "This page allows you to manage the attachments for a particular issue. Only users with administrative privileges to remove an issue can remove attachments." I suppose, I'm not a user with administrative privileges. Could we find an user with administrative privileges to remove outdated attachments, please? thanks, Dinesh
          Hide
          Samisa Abeysinghe added a comment -

          Hi Dinesh,
          I am having a hard time fiuring out what the latest attachments are.

          Could you please remove all the outdated attachments by using the "Manage Attachments" right beneth the "File Attachments:" title?
          This will make my life much easier when commiting the stuff.
          Thanks,
          Samisa...

          Show
          Samisa Abeysinghe added a comment - Hi Dinesh, I am having a hard time fiuring out what the latest attachments are. Could you please remove all the outdated attachments by using the "Manage Attachments" right beneth the "File Attachments:" title? This will make my life much easier when commiting the stuff. Thanks, Samisa...
          Hide
          Dinesh Weerapurage added a comment -

          Hi ,
          I changed build.xml , build.commons.Propeties , and buildXMLParser.xml files in cvs , edited files attached in build_file.tar.gz. I happend to edit guththila's XMLParser implementation since I didn't implemented peek () method earlier.

          guththila souce codes for axiscpp/src/guththila in guththila_src.tar.gz

          guththila's XMLParser interface implementation for axiscpp/src/xml/guththilain guththila-xml.tar.gz

          could somebody please commit them to CVS?

          thanks,
          Dinesh

          Show
          Dinesh Weerapurage added a comment - Hi , I changed build.xml , build.commons.Propeties , and buildXMLParser.xml files in cvs , edited files attached in build_file.tar.gz. I happend to edit guththila's XMLParser implementation since I didn't implemented peek () method earlier. guththila souce codes for axiscpp/src/guththila in guththila_src.tar.gz guththila's XMLParser interface implementation for axiscpp/src/xml/guththilain guththila-xml.tar.gz could somebody please commit them to CVS? thanks, Dinesh
          Hide
          Dinesh Weerapurage added a comment -

          Adrian,
          Though Guththila has It's own directory structure. We happened to put all hpp files and cpp files in src/guththila. ( In tspp all the source files and paser implementation included in xml/tspp directory) . rather than putting all files in xml/guththila , we decided to keep guththila source under src/guththila, and it's XMLParser interface under xml/guththila. Please have a look on
          http://www.mail-archive.com/axis-c-dev@ws.apache.org/msg02962.html
          thanks,
          Dinesh

          Show
          Dinesh Weerapurage added a comment - Adrian, Though Guththila has It's own directory structure. We happened to put all hpp files and cpp files in src/guththila. ( In tspp all the source files and paser implementation included in xml/tspp directory) . rather than putting all files in xml/guththila , we decided to keep guththila source under src/guththila, and it's XMLParser interface under xml/guththila. Please have a look on http://www.mail-archive.com/axis-c-dev@ws.apache.org/msg02962.html thanks, Dinesh
          Hide
          Adrian Dick added a comment -

          Dinesh,

          Doesn't guththila sit in it's own directory structure? With just the "shim" layer within the Axis structure?

          Show
          Adrian Dick added a comment - Dinesh, Doesn't guththila sit in it's own directory structure? With just the "shim" layer within the Axis structure?
          Hide
          Dinesh Weerapurage added a comment -

          Hi Adrian and All,
          I also prefer to have guththila/lib, and scripts works well in local machine. But the thing is, wouldn't it violates axis c++ directory convension? ( haveing ws-axis/c/src/guththila/lib). If not we could have it without any problem.
          thanks,
          Dinesh

          Show
          Dinesh Weerapurage added a comment - Hi Adrian and All, I also prefer to have guththila/lib, and scripts works well in local machine. But the thing is, wouldn't it violates axis c++ directory convension? ( haveing ws-axis/c/src/guththila/lib). If not we could have it without any problem. thanks, Dinesh
          Hide
          Adrian Dick added a comment -

          You are correct in saying only 1 'unless' condition maybe used, however you may have an 'if' and 'unless' together.

          The two solutions that are obvious to me are:
          1) (if you can) modify the Guthila structure such that the lib files are located in <parser>/lib - then this script will work immediately.
          2) provide an additional libset entry - I believe ANT will not fail if it is unable to find one of the libset entries - as long as the compiler can succeed with what is provided.

          Show
          Adrian Dick added a comment - You are correct in saying only 1 'unless' condition maybe used, however you may have an 'if' and 'unless' together. The two solutions that are obvious to me are: 1) (if you can) modify the Guthila structure such that the lib files are located in <parser>/lib - then this script will work immediately. 2) provide an additional libset entry - I believe ANT will not fail if it is unable to find one of the libset entries - as long as the compiler can succeed with what is provided.
          Hide
          Dinesh Weerapurage added a comment -

          Hi,
          I could put all the cpp and hpp files in the src/guththila directory. I have some issues to clarify , could someone please help me?

          1. If some one use guththila as a paser , could I use "builXMLParser.xml" to build guththila. ( I mean could I add guththila building stuff to buildXMLParser.xml file when xmlParser.guthtila = "true")

          If yes
          -------
          buildXMLParser.xml file carries following line

          <!-- Additional library of XMLParser -->
          <libset dir="$

          {dir.xmlParser}/lib" libs="${xmlParserLibrary}" unless="os400"/>

          Please correct me If I'm mistaken, as far as I understand It searchs for library in xml parser's lib directory
          (Here , It search libguththila.so in src/guththila/lib)

          since "libset" ant task already uses "unless" attribute once. I suppose we can't have another "unless"
          attribute for "guththila"

          could I create a lib directory in src/guththila in compile time. If I could create a lib inside src/guththila
          we could use
          <!-- Additional library of XMLParser -->
          <libset dir="${dir.xmlParser}

          /lib" libs="$

          {xmlParserLibrary}" unless="os400"/>

          without any problems.

          if no
          ---------

          what could I do with
          <!-- Additional library of XMLParser -->
          <libset dir="${dir.xmlParser}/lib" libs="${xmlParserLibrary}

          " unless="os400"/>

          because It reports an error , if there is no lib directory presant in the src/guththila?

          thanks,
          Dinesh

          Show
          Dinesh Weerapurage added a comment - Hi, I could put all the cpp and hpp files in the src/guththila directory. I have some issues to clarify , could someone please help me? 1. If some one use guththila as a paser , could I use "builXMLParser.xml" to build guththila. ( I mean could I add guththila building stuff to buildXMLParser.xml file when xmlParser.guthtila = "true") If yes ------- buildXMLParser.xml file carries following line <!-- Additional library of XMLParser --> <libset dir="$ {dir.xmlParser}/lib" libs="${xmlParserLibrary}" unless="os400"/> Please correct me If I'm mistaken, as far as I understand It searchs for library in xml parser's lib directory (Here , It search libguththila.so in src/guththila/lib) since "libset" ant task already uses "unless" attribute once. I suppose we can't have another "unless" attribute for "guththila" could I create a lib directory in src/guththila in compile time. If I could create a lib inside src/guththila we could use <!-- Additional library of XMLParser --> <libset dir="${dir.xmlParser} /lib" libs="$ {xmlParserLibrary}" unless="os400"/> without any problems. if no --------- what could I do with <!-- Additional library of XMLParser --> <libset dir="${dir.xmlParser}/lib" libs="${xmlParserLibrary} " unless="os400"/> because It reports an error , if there is no lib directory presant in the src/guththila? thanks, Dinesh
          Hide
          Samisa Abeysinghe added a comment -

          having src and include within src/guththila violates the current conventions that we have in the source structure.

          I would suggest that you drop ser and include within src/guththila and have all cpp and hpp files witin src/guththila itself

          Show
          Samisa Abeysinghe added a comment - having src and include within src/guththila violates the current conventions that we have in the source structure. I would suggest that you drop ser and include within src/guththila and have all cpp and hpp files witin src/guththila itself
          Hide
          Dinesh Weerapurage added a comment -

          oppss... Very sorry about it..I'm using axis-c-1.5 final version, that's why build.xml looks quite old. I will get a fresh checkout and will make necessary changes.
          thanks,
          Dinesh

          Show
          Dinesh Weerapurage added a comment - oppss... Very sorry about it..I'm using axis-c-1.5 final version, that's why build.xml looks quite old. I will get a fresh checkout and will make necessary changes. thanks, Dinesh
          Hide
          Dinesh Weerapurage added a comment -

          Hi,
          I made necessary changes to the build.commons.propeties file.

          If I'm not mistaken, In CVS the file's commited under ws-axis/c/src/guththila , there should be include directory since it carries all header files for guththila src.
          could you please make this directory structure for guththila source
          *.cpp files ----> ws-axis/c/src/guththila/src
          *.hpp files ----> ws-axis/c/src/guththila/include

          if we gonna put *.cpp and *.hpp in ws-axis/c/src/guththila (without src and include directories) then need to change build.xml again.

          Could you please tell me , what is the suitable way to do that?

          thanks,
          Dinesh

          Show
          Dinesh Weerapurage added a comment - Hi, I made necessary changes to the build.commons.propeties file. If I'm not mistaken, In CVS the file's commited under ws-axis/c/src/guththila , there should be include directory since it carries all header files for guththila src. could you please make this directory structure for guththila source *.cpp files ----> ws-axis/c/src/guththila/src *.hpp files ----> ws-axis/c/src/guththila/include if we gonna put *.cpp and *.hpp in ws-axis/c/src/guththila (without src and include directories) then need to change build.xml again. Could you please tell me , what is the suitable way to do that? thanks, Dinesh
          Hide
          Samisa Abeysinghe added a comment -

          Looks like you have done the updated with an older version of build.xml file.

          Please take a frech copy from CVS and add your changes, else it will break the current build process

          Show
          Samisa Abeysinghe added a comment - Looks like you have done the updated with an older version of build.xml file. Please take a frech copy from CVS and add your changes, else it will break the current build process
          Hide
          Samisa Abeysinghe added a comment -

          Oh yes, I missed that point.
          Dinesh would you be able to make that change? (move xmlParser.guththila to build.common)

          Show
          Samisa Abeysinghe added a comment - Oh yes, I missed that point. Dinesh would you be able to make that change? (move xmlParser.guththila to build.common)
          Hide
          John Hawkins added a comment -

          If this is to be used on other platforms then build.common needs to be changed not linux.

          Show
          John Hawkins added a comment - If this is to be used on other platforms then build.common needs to be changed not linux.
          Hide
          Samisa Abeysinghe added a comment -

          Excellent, I would commit the build related changes to the CVS soon

          I will make the "xmlParser.guththila = false" as the default value as then those who do not want to use it would not have to build it by default

          Show
          Samisa Abeysinghe added a comment - Excellent, I would commit the build related changes to the CVS soon I will make the "xmlParser.guththila = false" as the default value as then those who do not want to use it would not have to build it by default
          Hide
          Dinesh Weerapurage added a comment -

          Hi Samisa,
          Thanks for committing code, I looked on ant scripts of Axis C++ main build. I made some changes to
          build.Linux.Propeties and build.xml files. If someone wants to build guththila ,he wants to change build.Linux.Propeties
          xmlParser.guththila = true
          after that ant command will build libaxis_guththila.so in obj/bin directory, could you please commit this build files to CVS.
          thanks again,
          Dinesh

          Show
          Dinesh Weerapurage added a comment - Hi Samisa, Thanks for committing code, I looked on ant scripts of Axis C++ main build. I made some changes to build.Linux.Propeties and build.xml files. If someone wants to build guththila ,he wants to change build.Linux.Propeties xmlParser.guththila = true after that ant command will build libaxis_guththila.so in obj/bin directory, could you please commit this build files to CVS. thanks again, Dinesh
          Hide
          Samisa Abeysinghe added a comment -

          Dinesh,

          I added the sources to the CVS.
          Pull parser implementation in src/guththila and parser lib implementation using Guththila in src/xml/guththila

          I did not put the build stuff in the CVS. Ideally you have to integrate this to the current ant build system.
          We cannot afford to have seperate build systems as it is part of the main source tree.

          I would suggest that you update the ant scripts of the Axis C++ project that would allow the user select the option of building Guththila related stuff if they wish to do so. In other words building that should not be mandatory.

          Samisa...

          Show
          Samisa Abeysinghe added a comment - Dinesh, I added the sources to the CVS. Pull parser implementation in src/guththila and parser lib implementation using Guththila in src/xml/guththila I did not put the build stuff in the CVS. Ideally you have to integrate this to the current ant build system. We cannot afford to have seperate build systems as it is part of the main source tree. I would suggest that you update the ant scripts of the Axis C++ project that would allow the user select the option of building Guththila related stuff if they wish to do so. In other words building that should not be mandatory. Samisa...
          Hide
          Samisa Abeysinghe added a comment -

          For the base sample problem, What SOAP messages are sent and receieved?

          Re commiting - I will put the stuff in CVS, now that it seems to wor for some extent.

          Show
          Samisa Abeysinghe added a comment - For the base sample problem, What SOAP messages are sent and receieved? Re commiting - I will put the stuff in CVS, now that it seems to wor for some extent.
          Hide
          Dinesh Weerapurage added a comment -

          Hi ,
          Thanks for the help, I was able to fix it. Now calculator example works with
          guththila.

          First I started server and then Edited axiscpp.conf's

          XMLParser:/usr/local/axiscpp_deploy/lib/libguththila.so

          then ran Calculator client example it works fine with it.

          Then I tried to run base client example. But it gives

          $ ./base http://localhost:9091/axis/base
          invoking echoString...
          hello world hello world Unknown exception has occured
          invoking echoString...
          hello world hello world Unknown exception has occured
          invoking echoString...
          hello world hello world Unknown exception has occurred

          I was able to run RpcFault example and ref example using guththila as client side xml parser.

          I tried to write ant build scripts to build Guththila and its XMLParser interface. But I was unable to integrate them to main build.xml file

          I wrote two build files to Guththila and it XMLParser interface.

          Building Guththila
          -------------------------
          build.xml file located in /usr/local/axiscpp/src/guththila/ directory
          build with ant command ($ant)
          build.xml will build libguththila.so and will move it to /usr/local/axiscpp_deploy/lib

          Building Guththila's XMLParser Interface
          --------------------------------------------------
          build.xml file is located in /usr/local/axiscpp/src/xml/guththila/ directory
          build with ant command ( $ant)
          build.xml will build libaxis_guththila.so and will move it to /usr/local/axiscpp_deploy/lib

          ***I happened to make some changes to XMLGuththilaParser interface and Guththila source.
          can somebody please commit them to CVS ....

          Show
          Dinesh Weerapurage added a comment - Hi , Thanks for the help, I was able to fix it. Now calculator example works with guththila. First I started server and then Edited axiscpp.conf's XMLParser:/usr/local/axiscpp_deploy/lib/libguththila.so then ran Calculator client example it works fine with it. Then I tried to run base client example. But it gives $ ./base http://localhost:9091/axis/base invoking echoString... hello world hello world Unknown exception has occured invoking echoString... hello world hello world Unknown exception has occured invoking echoString... hello world hello world Unknown exception has occurred I was able to run RpcFault example and ref example using guththila as client side xml parser. I tried to write ant build scripts to build Guththila and its XMLParser interface. But I was unable to integrate them to main build.xml file I wrote two build files to Guththila and it XMLParser interface. Building Guththila ------------------------- build.xml file located in /usr/local/axiscpp/src/guththila/ directory build with ant command ($ant) build.xml will build libguththila.so and will move it to /usr/local/axiscpp_deploy/lib Building Guththila's XMLParser Interface -------------------------------------------------- build.xml file is located in /usr/local/axiscpp/src/xml/guththila/ directory build with ant command ( $ant) build.xml will build libaxis_guththila.so and will move it to /usr/local/axiscpp_deploy/lib ***I happened to make some changes to XMLGuththilaParser interface and Guththila source. can somebody please commit them to CVS ....
          Hide
          John Hawkins added a comment -

          buildWithTraceAndDebug you can get trace out too if you add a traceFile line to the axiscpp conf file.

          Show
          John Hawkins added a comment - buildWithTraceAndDebug you can get trace out too if you add a traceFile line to the axiscpp conf file.
          Hide
          Samisa Abeysinghe added a comment -

          Please build Axis C++ source with debug enabled with the following command:
          ant buildWithDebug

          This will help you to pinpoint the location of the problem in source.

          Show
          Samisa Abeysinghe added a comment - Please build Axis C++ source with debug enabled with the following command: ant buildWithDebug This will help you to pinpoint the location of the problem in source.
          Hide
          Dinesh Weerapurage added a comment -

          Hi,

          I edited ../etc/axiscpp.conf file as following

          XMLParser:/usr/local/axiscpp_deploy/lib/libaxis_guththila.so

          but it gives ( calculator example works fine with libaxis_xmlparser.so)

          $ ./calculator add 10 5 http://localhost:9090/axis/Calculator

          Using service at http://localhost:9090/axis/Calculator

          Segmentation fault

          Then I looked request and response messages.

          POST /axis/Calculator HTTP/1.1

          Host: 127.0.0.1:8080

          Content-Type: text/xml; charset=UTF-8

          SOAPAction: "Calculator#add"

          Content-Length: 404

          <?xml version='1.0' encoding='utf-8' ?>
          <SOAP-ENV:Envelope 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">
          <SOAP-ENV:Body>
          <ns1:add xmlns:ns1="http://localhost/axis/Calculator">
          <in0 xsi:type="xsd:int">10</in0>
          <in1 xsi:type="xsd:int">5</in1>
          </ns1:add>
          </SOAP-ENV:Body>
          </SOAP-ENV:Envelope>

          HTTP/1.1 200 OK

          Date: Wed, 20 Jul 2005 03:53:53 GMT

          Server: Apache/2.0.51 (Unix)

          Content-Length: 400

          Content-Type: text/xml

          <?xml version='1.0' encoding='utf-8' ?>
          <SOAP-ENV:Envelope 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">
          <SOAP-ENV:Body>
          <ns1:addResponse xmlns:ns1="http://localhost/axis/Calculator">
          <addReturn xsi:type="xsd:int">15</addReturn>
          </ns1:addResponse>
          </SOAP-ENV:Body>
          </SOAP-ENV:Envelope>

          seems it is working correctly.

          Then debugged calculator using gdb

          (gdb) bt
          #0 0x402441b0 in strcmp () from /lib/tls/libc.so.6
          #1 0x400aaf43 in axiscpp::SoapDeSerializer::getEnvelope () from /usr/local/axiscpp_deploy/lib/libaxis_client.so
          #2 0x400ac0af in axiscpp::SoapDeSerializer::getVersion () from /usr/local/axiscpp_deploy/lib/libaxis_client.so
          #3 0x40059374 in axiscpp::ClientAxisEngine::invoke () from /usr/local/axiscpp_deploy/lib/libaxis_client.so
          #4 0x40058fe4 in axiscpp::ClientAxisEngine::process () from /usr/local/axiscpp_deploy/lib/libaxis_client.so
          #5 0x400817b1 in axiscpp::Call::invoke () from /usr/local/axiscpp_deploy/lib/libaxis_client.so
          #6 0x08049257 in Calculator::add (this=0xbffff4a0, Value0=10, Value1=5) at Calculator.cpp:51
          #7 0x0804a1b9 in main (argc=5, argv=0xbffff794) at Client.cpp:103

          It seems some problem in SoapDeSerializer::getEnvelop() method. I am unable to move forward from this point. Could you please figure out what's the problem here ?
          anything that I can try out...

          thanks,
          Dinesh

          Show
          Dinesh Weerapurage added a comment - Hi, I edited ../etc/axiscpp.conf file as following XMLParser:/usr/local/axiscpp_deploy/lib/libaxis_guththila.so but it gives ( calculator example works fine with libaxis_xmlparser.so) $ ./calculator add 10 5 http://localhost:9090/axis/Calculator Using service at http://localhost:9090/axis/Calculator Segmentation fault Then I looked request and response messages. POST /axis/Calculator HTTP/1.1 Host: 127.0.0.1:8080 Content-Type: text/xml; charset=UTF-8 SOAPAction: "Calculator#add" Content-Length: 404 <?xml version='1.0' encoding='utf-8' ?> <SOAP-ENV:Envelope 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"> <SOAP-ENV:Body> <ns1:add xmlns:ns1="http://localhost/axis/Calculator"> <in0 xsi:type="xsd:int">10</in0> <in1 xsi:type="xsd:int">5</in1> </ns1:add> </SOAP-ENV:Body> </SOAP-ENV:Envelope> HTTP/1.1 200 OK Date: Wed, 20 Jul 2005 03:53:53 GMT Server: Apache/2.0.51 (Unix) Content-Length: 400 Content-Type: text/xml <?xml version='1.0' encoding='utf-8' ?> <SOAP-ENV:Envelope 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"> <SOAP-ENV:Body> <ns1:addResponse xmlns:ns1="http://localhost/axis/Calculator"> <addReturn xsi:type="xsd:int">15</addReturn> </ns1:addResponse> </SOAP-ENV:Body> </SOAP-ENV:Envelope> seems it is working correctly. Then debugged calculator using gdb (gdb) bt #0 0x402441b0 in strcmp () from /lib/tls/libc.so.6 #1 0x400aaf43 in axiscpp::SoapDeSerializer::getEnvelope () from /usr/local/axiscpp_deploy/lib/libaxis_client.so #2 0x400ac0af in axiscpp::SoapDeSerializer::getVersion () from /usr/local/axiscpp_deploy/lib/libaxis_client.so #3 0x40059374 in axiscpp::ClientAxisEngine::invoke () from /usr/local/axiscpp_deploy/lib/libaxis_client.so #4 0x40058fe4 in axiscpp::ClientAxisEngine::process () from /usr/local/axiscpp_deploy/lib/libaxis_client.so #5 0x400817b1 in axiscpp::Call::invoke () from /usr/local/axiscpp_deploy/lib/libaxis_client.so #6 0x08049257 in Calculator::add (this=0xbffff4a0, Value0=10, Value1=5) at Calculator.cpp:51 #7 0x0804a1b9 in main (argc=5, argv=0xbffff794) at Client.cpp:103 It seems some problem in SoapDeSerializer::getEnvelop() method. I am unable to move forward from this point. Could you please figure out what's the problem here ? anything that I can try out... thanks, Dinesh
          Hide
          Samisa Abeysinghe added a comment -

          Dinesh,
          Would it be possibe for you to look if you can update the ant script to build Guththila?

          This would help us in integrating as we do not have make based build with Axis C++ right now.

          Show
          Samisa Abeysinghe added a comment - Dinesh, Would it be possibe for you to look if you can update the ant script to build Guththila? This would help us in integrating as we do not have make based build with Axis C++ right now.
          Hide
          Dinesh Weerapurage added a comment -

          Hi Mark,
          I attached both Guththaila and its XMLParser implementation here.
          could you please commit them

          guththila source under axiscpp/src/guththila
          guththila xml parser implementation axiscpp/src/xml/guththila

          because we discussed this thing in the list earlier.

          Still I implemented only XMLParser interface and build libaxis_guththila.so, I think it need to integrate it with axis c++ but I don't have a clear idea on how to do it.Hope to develop a sample after integrating it. I need experts help in order to integrate this with axis c++. Everybody's welcome to give me a hand.!!!

          I'm very sorry , I didn't do anything with ant in Guththila, I made Makefile build system to build Guththila and Shell script to build paser interface. I think its better to get this working first and (since it's not integrated) then add to ant build system. any thoughts please .

          Thank you very much for you kind help

          kind regards,
          Dinesh

          Show
          Dinesh Weerapurage added a comment - Hi Mark, I attached both Guththaila and its XMLParser implementation here. could you please commit them guththila source under axiscpp/src/guththila guththila xml parser implementation axiscpp/src/xml/guththila because we discussed this thing in the list earlier. Still I implemented only XMLParser interface and build libaxis_guththila.so, I think it need to integrate it with axis c++ but I don't have a clear idea on how to do it.Hope to develop a sample after integrating it. I need experts help in order to integrate this with axis c++. Everybody's welcome to give me a hand.!!! I'm very sorry , I didn't do anything with ant in Guththila, I made Makefile build system to build Guththila and Shell script to build paser interface. I think its better to get this working first and (since it's not integrated) then add to ant build system. any thoughts please . Thank you very much for you kind help kind regards, Dinesh
          Hide
          Dinesh Weerapurage added a comment -

          Hi,
          some body please commit this code to CVS.

          thanks,
          Dinesh

          Show
          Dinesh Weerapurage added a comment - Hi, some body please commit this code to CVS. thanks, Dinesh
          Hide
          Samisa Abeysinghe added a comment -

          There is an implementation; can compile but cannot run. Is this working? If yes, how to get it working?

          Show
          Samisa Abeysinghe added a comment - There is an implementation; can compile but cannot run. Is this working? If yes, how to get it working?

            People

            • Assignee:
              Samisa Abeysinghe
              Reporter:
              Farhaan Mohideen
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development