Re: SOAP fault not working with axis2c latest revision(663886) from code generated from axis2/java using adb
Hi Dimuthu, I have raised a JIRA for this issue.Please refer below details. Key: AXIS2C-1188 URL: https://issues.apache.org/jira/browse/AXIS2C-1188 Project: Axis2-C Issue Type: Bug Components: core/engine Affects Versions: Current (Nightly) Environment: axis2c revision number 663886. axis2/java 1.4 and also axis2/java nighlty build Reporter: naveen bhat Thanks, Naveen Bhat On Fri, Jun 6, 2008 at 7:57 AM, Dimuthu Gamage <[EMAIL PROTECTED]> wrote: > Hi, > The idea case should be the server responding with a fault. I think issue > for another JIRA. :( > > Thanks > Dimuthu > > On Fri, Jun 6, 2008 at 4:25 PM, naveen bhat <[EMAIL PROTECTED]> > wrote: > >> Hello group, >> >> I used axis2/java 1.4 to generate server side code from wsdl. >> I did not write the business logic in the service skeleton(i.e all empty >> operations returning NULL). >> I compiled the code to generate libMyService.so. >> I deployed the service(libMyService.so and services.xml). >> I made a request from the axis2/java client. >> Ideally client should receive a soap fault from server. >> But server is not sending any response. >> I monitored the soap messages using tcpmon and found that the server is >> sending only http header, and there was no soap message in response. >> I also experimented the same steps using axis2/java nightly >> build(available at http://people.apache.org/dist/axis2/nightly) but the >> result remained the same. >> >> Need help in this regard.Let me know if you need more details >> >> *PS*: command used to generate the server side code >> WSDL2C.sh -uri -ss -sd -d adb -u. >> *Environment*: >> axis2c revision number 663886. >> axis2/java 1.4 and also axis2/java nighlty build >> >> Thanks in advance >> Navin Bhat >> > >
Re: code generated from WSDL2C is not compiling(axis2/java nightly build)
Hi Dimuthu, Is there an update about the issue described in my previous mails?? Do i have to raise a JIRA for this issue ??? Kindly update me. Thanks in advance, Naveen Bhat On Fri, Jun 6, 2008 at 3:00 AM, naveen bhat <[EMAIL PROTECTED]> wrote: > Hi Dimuthu, > > As you said you will fix this issue, will it be available as a seperate > nightly build of axis2/java. If so, please provide me the link where the > updated axis2/java resides with the fix for this problem. > > Thanks, > Naveen > > > On Fri, Jun 6, 2008 at 2:54 AM, Dimuthu Gamage <[EMAIL PROTECTED]> wrote: > >> hi naveen, >> I don't think there were much changes in skeleton headers after 1.4. Since >> you got this working after including axiom_soap header, I may be able to >> solve this issue by including that header from the codegen template itself. >> >> Thanks >> Dimuthu >> >> >> On Fri, Jun 6, 2008 at 3:56 PM, naveen bhat <[EMAIL PROTECTED]> >> wrote: >> >>> Hello group, >>> >>> With reference to the fix provided for the issue AXIS2C-1168( >>> https://issues.apache.org/jira/browse/AXIS2C-1168?focusedCommentId=12601) >>> i.e the nightly build of axis2/java. >>> I generated the server side skeleton code without adb using the >>> axis2/java nightly build available at the location( >>> http://people.apache.org/dist/axis2/nightly). >>> When the compiled the code using build.sh(script in src folder) it gives >>> error looking for api's of soap envelope,soap header function. >>> I later found , that the generated code did not include axiom_soap.h file >>> in the generated skeleton header file. >>> When i included the header file manually adding >>> "#include", the code compiled properly. >>> I suspect the generation of code without adb is improper. >>> I am not facing such problem when i use axis2/java 1.4. >>> So i guess the problem is with the nightly build. >>> Kindly let me know how to resolve this problem. >>> >>> Environment: >>> axis2c latest revision from svn head. >>> OS:CentOS 4.4 >>> >>> PS: >>> Command used to generate code >>> WSDL2C.sh -uri -ss -sd -d none >>> >>> Thanks in advance, >>> Naveen Bhat >>> >> >> >
Re: code generated from WSDL2C is not compiling(axis2/java nightly build)
Hi Dimuthu, As you said you will fix this issue, will it be available as a seperate nightly build of axis2/java. If so, please provide me the link where the updated axis2/java resides with the fix for this problem. Thanks, Naveen On Fri, Jun 6, 2008 at 2:54 AM, Dimuthu Gamage <[EMAIL PROTECTED]> wrote: > hi naveen, > I don't think there were much changes in skeleton headers after 1.4. Since > you got this working after including axiom_soap header, I may be able to > solve this issue by including that header from the codegen template itself. > > Thanks > Dimuthu > > > On Fri, Jun 6, 2008 at 3:56 PM, naveen bhat <[EMAIL PROTECTED]> > wrote: > >> Hello group, >> >> With reference to the fix provided for the issue AXIS2C-1168( >> https://issues.apache.org/jira/browse/AXIS2C-1168?focusedCommentId=12601) >> i.e the nightly build of axis2/java. >> I generated the server side skeleton code without adb using the axis2/java >> nightly build available at the location( >> http://people.apache.org/dist/axis2/nightly). >> When the compiled the code using build.sh(script in src folder) it gives >> error looking for api's of soap envelope,soap header function. >> I later found , that the generated code did not include axiom_soap.h file >> in the generated skeleton header file. >> When i included the header file manually adding "#include", >> the code compiled properly. >> I suspect the generation of code without adb is improper. >> I am not facing such problem when i use axis2/java 1.4. >> So i guess the problem is with the nightly build. >> Kindly let me know how to resolve this problem. >> >> Environment: >> axis2c latest revision from svn head. >> OS:CentOS 4.4 >> >> PS: >> Command used to generate code >> WSDL2C.sh -uri -ss -sd -d none >> >> Thanks in advance, >> Naveen Bhat >> > >
SOAP fault not working with axis2c latest revision(663886) from code generated from axis2/java using adb
Hello group, I used axis2/java 1.4 to generate server side code from wsdl. I did not write the business logic in the service skeleton(i.e all empty operations returning NULL). I compiled the code to generate libMyService.so. I deployed the service(libMyService.so and services.xml). I made a request from the axis2/java client. Ideally client should receive a soap fault from server. But server is not sending any response. I monitored the soap messages using tcpmon and found that the server is sending only http header, and there was no soap message in response. I also experimented the same steps using axis2/java nightly build(available at http://people.apache.org/dist/axis2/nightly) but the result remained the same. Need help in this regard.Let me know if you need more details *PS*: command used to generate the server side code WSDL2C.sh -uri -ss -sd -d adb -u. *Environment*: axis2c revision number 663886. axis2/java 1.4 and also axis2/java nighlty build Thanks in advance Navin Bhat
Re: Unable to support MTOM for code generation with adb
Hi Dimuthu, I have raised jira for this issue.Please refer https://issues.apache.org/jira/browse/AXIS2C-1181. On Wed, Jun 4, 2008 at 5:38 AM, Dimuthu Gamage <[EMAIL PROTECTED]> wrote: > Hi naveen, > Currently axis2/c codegen doesn't support MTOM. You need to write the code > manually to handle mtom attachments. Can you raise a JIRA on this, so it > will be easy to track this issue. > > Thanks > Dimuthu > > > On Wed, Jun 4, 2008 at 3:38 PM, naveen bhat <[EMAIL PROTECTED]> > wrote: > >> Hello group, >> >> I have a service which receives an MTOM attachment, and the service sends >> back the same. >> I generated the service skeleton code with adb from the wsdl . >> The wsdl describes the data exchanged to be of type xmime:base64binary. >> I am able to receive the MTOM attachment at the client and save it to a >> file. >> In the business logic of the service, i wrote the code to create the >> datahandler from the file received. >> But i found that the code that is serializing the xop node is converting >> it to a string using axiom_node_to_string API. >> Because of which i am unable to see the attachment at the client end. >> >> >> *For Instance:* >> >> Sample server response to client as observed in tcpmon >> >> >> ---MIME boundary >> >> >> >> >> >> MIME boundary >> >> MIME boundary >> No attachment(empty) >> MIME boundary >> >> >> *Serializer logic:* >> >> It is enclosing the xop node in between the tags and >> . >> Its converting xop node to string using >> axiom_node_to_string(xop_node,env)l >> >> >> >> How to generate code with proper serializers to send MTOM from the service >> with adb??? >> Kindly let me know if you need more details. >> >> Thanks in advance, >> Naveen Bhat >> >> >> >
code generated from WSDL2C is not compiling(axis2/java nightly build)
Hello group, With reference to the fix provided for the issue AXIS2C-1168( https://issues.apache.org/jira/browse/AXIS2C-1168?focusedCommentId=12601) i.e the nightly build of axis2/java. I generated the server side skeleton code without adb using the axis2/java nightly build available at the location( http://people.apache.org/dist/axis2/nightly). When the compiled the code using build.sh(script in src folder) it gives error looking for api's of soap envelope,soap header function. I later found , that the generated code did not include axiom_soap.h file in the generated skeleton header file. When i included the header file manually adding "#include", the code compiled properly. I suspect the generation of code without adb is improper. I am not facing such problem when i use axis2/java 1.4. So i guess the problem is with the nightly build. Kindly let me know how to resolve this problem. Environment: axis2c latest revision from svn head. OS:CentOS 4.4 PS: Command used to generate code WSDL2C.sh -uri -ss -sd -d none Thanks in advance, Naveen Bhat
Unable to support MTOM for code generation with adb
Hello group, I have a service which receives an MTOM attachment, and the service sends back the same. I generated the service skeleton code with adb from the wsdl . The wsdl describes the data exchanged to be of type xmime:base64binary. I am able to receive the MTOM attachment at the client and save it to a file. In the business logic of the service, i wrote the code to create the datahandler from the file received. But i found that the code that is serializing the xop node is converting it to a string using axiom_node_to_string API. Because of which i am unable to see the attachment at the client end. *For Instance:* Sample server response to client as observed in tcpmon ---MIME boundary MIME boundary MIME boundary No attachment(empty) MIME boundary *Serializer logic:* It is enclosing the xop node in between the tags and . Its converting xop node to string using axiom_node_to_string(xop_node,env)l How to generate code with proper serializers to send MTOM from the service with adb??? Kindly let me know if you need more details. Thanks in advance, Naveen Bhat
Next Release of axis2c
Hello group, I wanted to know few things. 1. When is the next release date of axis2c?? 2. Whether MTOM with caching be available in the next release??. 3. For a particular version axis2c, which is the corresponding version of axis2/java to be used for code generation.For eg: for axis2c-1.3 is it axis2/java-1.3 to be used???.Is there a dependency of version between axis2c and axis2/java??? Thanks in advance, Naveen Bhat
Re: SOAP fault not working in axis2c 1.4
Hi Dinesh, I hope the problem description in my previous mail was precise. Kindly let me know if you need more details.Let me know how can i solve the problem regarding SOAP fault. Thanks in advance, Navin Bhat On Sun, Jun 1, 2008 at 10:41 PM, naveen bhat <[EMAIL PROTECTED]> wrote: > Hi Dinesh, > > To give to much clear picture about the problem. > I did an investigation on mtom sample(service & client) in axis2c 1.4 and > axis2c 1.3. > I executed the mtom sample in both axis2c 1.4 and axis2c 1.3 for two > scenarios. > > >1. First scenario for SOAP fault,where client sends only >"mtomSample" node without the filename node and the associated >attachment.SOAP fault was sent properly for axis2c 1.3 mtom service, where >as for axis2c 1.4 mtom service it did not send SOAP fault,it sent only http >headers as i explained before. >2. Second scenario for normal file transfer which succeds for both >distributions. > > > I have attached server log(axis2.log), tcp-monitor log (tcpmon_traffic.log) > and mtom log(mtom.log) for axis2c-1.3 and axis2c-1.4 distribution in > seperate zip file.Check these files to analyse the problem. > > I suspect the problem is with axis2c-1.4 distribution fault handling. > I hope my explaination is clear to you. > Eager to hear from you on this issue. > > Thanks in advance, > Naveen. > > > > On Sat, May 31, 2008 at 10:51 PM, Dinesh Premalal <[EMAIL PROTECTED]> > wrote: > >> Hi Naveen, >> >> "naveen bhat" <[EMAIL PROTECTED]> writes: >> >> > Hi Dinesh, >> > >> > Please find the server log file (axis2.log) attached. >> >> I looked through your log files seems there is nothing wrong with >> Axis2/C engine. Does your service work for correct request ? >> >> thanks, >> Dinesh >> >> -- >> http://nethu.org >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >
Re: WSDL2C is not generating soap 1.2 compliant client stubs for wsdl with soap 1.2 bindings
<http://issues.apache.org/jira/browse/AXIS2C-1168>Hello Dimuthu, I have raised a jira with key AXIS2C-1168<http://issues.apache.org/jira/browse/AXIS2C-1168>. Thanks , Naveen On Fri, May 30, 2008 at 1:49 AM, Dimuthu Gamage <[EMAIL PROTECTED]> wrote: > Hi naveen, > > In fact looks like this is not possible with the current wsdl2c > generated code. It just pick the first binding and generate code for > that. > Can you please raise a JIRA. I will look in to that asap. > > Thanks > Dimuthu > > On Fri, May 30, 2008 at 3:06 PM, naveen bhat > <[EMAIL PROTECTED]> wrote: > > Hello group, > > > > Kindly let me know if my queries are relevant to this forum. > > I have not received any response for the query posted below. > > Do i need to post this axis2/java forum? > > Assistance needed. > > > > > > On Mon, May 26, 2008 at 4:47 AM, naveen bhat < > [EMAIL PROTECTED]> > > wrote: > >> > >> Hello group, > >> > >> I am using a wsdl with soap 1.2 bindings.I generated > >> client stub using three version of axis2/java (1.2/1.3/1.4). In all > >> three I found that in the client stub the call for the operation,let > >> say add(for eg) always sets the soap version to AXIS2_SOAP11,but > >> actually it should be AXIS2_SOAP12 for a wsdl with soap 1.2 bindings. > >> I am not finding any options in WSDL2C tool to generate client code > >> for soap 1.2 . I also tried to set the soap version to 1.2 (in main > >> function of client) before calling the operation defined in stub ,but > >> this did not work as the soap version was reset back to soap 1.1 in > >> the stub(let say axis2_stub_op_add() for eg). > >> > >> So my question is how do i use code generator to generate stub which > >> can send soap 1.2 compliant message at the client side. > >> > >> PS: Following command was used to generate stub > >>WSDL2C.sh -uri -d adb -u > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: WSDL2C is not generating soap 1.2 compliant client stubs for wsdl with soap 1.2 bindings
Hello group, Kindly let me know if my queries are relevant to this forum. I have not received any response for the query posted below. Do i need to post this axis2/java forum? Assistance needed. On Mon, May 26, 2008 at 4:47 AM, naveen bhat <[EMAIL PROTECTED]> wrote: > Hello group, > > I am using a wsdl with soap 1.2 bindings.I generated > client stub using three version of axis2/java (1.2/1.3/1.4). In all > three I found that in the client stub the call for the operation,let > say add(for eg) always sets the soap version to AXIS2_SOAP11,but > actually it should be AXIS2_SOAP12 for a wsdl with soap 1.2 bindings. > I am not finding any options in WSDL2C tool to generate client code > for soap 1.2 . I also tried to set the soap version to 1.2 (in main > function of client) before calling the operation defined in stub ,but > this did not work as the soap version was reset back to soap 1.1 in > the stub(let say axis2_stub_op_add() for eg). > > So my question is how do i use code generator to generate stub which > can send soap 1.2 compliant message at the client side. > > PS: Following command was used to generate stub >WSDL2C.sh -uri -d adb -u >
SOAP fault not working in axis2c 1.4
I am working on axis2c 1.4. I created a fault scenario for mtom sample where mtom client sends an invalid soap request to server. I monitored the soap messages using tcpmon. I saw that server recieves request properly but sends back only http headers and no soap message. I also tried with a sample service which i wrote even there i faced the same problem. Kindly help me in this regard. Thanks in advance, Naveen Bhat
WSDL2C is not generating soap 1.2 compliant client stubs for wsdl with soap 1.2 bindings
Hello group, I am using a wsdl with soap 1.2 bindings.I generated client stub using three version of axis2/java (1.2/1.3/1.4). In all three I found that in the client stub the call for the operation,let say add(for eg) always sets the soap version to AXIS2_SOAP11,but actually it should be AXIS2_SOAP12 for a wsdl with soap 1.2 bindings. I am not finding any options in WSDL2C tool to generate client code for soap 1.2 . I also tried to set the soap version to 1.2 (in main function of client) before calling the operation defined in stub ,but this did not work as the soap version was reset back to soap 1.1 in the stub(let say axis2_stub_op_add() for eg). So my question is how do i use code generator to generate stub which can send soap 1.2 compliant message at the client side. PS: Following command was used to generate stub WSDL2C.sh -uri -d adb -u - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
