Missing data when going through proxy server
Hello, everybody. I have a problem that I've been grappling with for days without any significant progress, hoping someone can help. I have a client using the stub code generated by Axis2/C 1.5. It is talking to a Java web services server that has stub code generated by Axis2 1.4.1. Some the the web service requests generate large responses, maybe a string with 130K characters. When the client talks directly to the server, then everything works fine. But when the client talks to the server through a proxy server then the response comes back incomplete. The Axis2/C stub returns a response but some of the fields are null (like the big string field). I found this https://issues.apache.org/jira/browse/AXIS2C-936 and I can deal with it by checking for NULLs in the response, but the question is why is the response incomplete? I've tried this with Squid and Privoxy as the proxy servers and both exhibit the same behavior. I've used tools like SoapUI and Paros to see the response coming back through the proxy server and they are fine (the big text string is present). So why doesn't my client app see it? I don't think it is length related since I've tested with shorter response strings (a few hundred characters) and the problem still happens. I also implemented a test program using gSOAP and it worked fine through the proxy server. Has anybody seen this problem with proxy servers before? Any suggestions as to what might be wrong? Thanks for any assistance. Eric
RE : Missing data when going through proxy server
Hi Eric. A few suggestions: check what the client receives with TCPMon. If you are using Guththila, the deserialisation could be stopping when a non-ASCII character is reached. (possibly the proxy software does a conversion?) HTH -Message d'origine- De : Eric Hsiung [mailto:er...@bodymedia.com] Envoyé : lundi, mai 4, 2009 12:53 À : axis-c-user@ws.apache.org Objet : Missing data when going through proxy server Hello, everybody. I have a problem that I've been grappling with for days without any significant progress, hoping someone can help. I have a client using the stub code generated by Axis2/C 1.5. It is talking to a Java web services server that has stub code generated by Axis2 1.4.1. Thanks for any assistance. Eric _ Ce message est confidentiel, à l'usage exclusif du destinataire ci-dessus et son contenu ne représente en aucun cas un engagement de la part de AXA, sauf en cas de stipulation expresse et par écrit de la part de AXA. Toute publication, utilisation ou diffusion, même partielle, doit être autorisée préalablement. Si vous n'êtes pas destinataire de ce message, merci d'en avertir immédiatement l'expéditeur. This e-mail message is confidential, for the exclusive use of the addressee and its contents shall not constitute a commitment by AXA, except as otherwise specifically provided in writing by AXA. Any unauthorized disclosure, use or dissemination, either whole or partial, is prohibited. If you are not the intended recipient of the message, please notify the sender immediately.
RE: RE : Missing data when going through proxy server
Hi, Carl. Thanks for the quick response. I've used SoapUI and Paros, both of which show the response that comes back from the server, and everything looks fine. I just tried tcpmon and it shows the same thing. I'm not familiar with Guththila but is there some way I can feed the server response directly to Guththila and see what happens? Thanks for your help. Eric -Original Message- From: Lefrancois, Carl [mailto:carl.lefranc...@axa-canada.com] Sent: Monday, May 04, 2009 2:00 PM To: Apache AXIS C User List Subject: RE : Missing data when going through proxy server [heur] Importance: Low Hi Eric. A few suggestions: check what the client receives with TCPMon. If you are using Guththila, the deserialisation could be stopping when a non-ASCII character is reached. (possibly the proxy software does a conversion?) HTH -Message d'origine- De : Eric Hsiung [mailto:er...@bodymedia.com] Envoyé : lundi, mai 4, 2009 12:53 À : axis-c-user@ws.apache.org Objet : Missing data when going through proxy server Hello, everybody. I have a problem that I've been grappling with for days without any significant progress, hoping someone can help. I have a client using the stub code generated by Axis2/C 1.5. It is talking to a Java web services server that has stub code generated by Axis2 1.4.1. Thanks for any assistance. Eric _ Ce message est confidentiel, à l'usage exclusif du destinataire ci-dessus et son contenu ne représente en aucun cas un engagement de la part de AXA, sauf en cas de stipulation expresse et par écrit de la part de AXA. Toute publication, utilisation ou diffusion, même partielle, doit être autorisée préalablement. Si vous n'êtes pas destinataire de ce message, merci d'en avertir immédiatement l'expéditeur. This e-mail message is confidential, for the exclusive use of the addressee and its contents shall not constitute a commitment by AXA, except as otherwise specifically provided in writing by AXA. Any unauthorized disclosure, use or dissemination, either whole or partial, is prohibited. If you are not the intended recipient of the message, please notify the sender immediately.
Handling Large data in a method call
Hi, We have a web method exposed by .net app and we using client stubs generated through Axis2. This method accepts an array of objects. The object is very heavy object containing 25+ members variables of double and string type. The calls to this method fails sometimes due to memory when we are trying to send large number of objects e.g. 10-20. Any suggestions/idea , how can we compress the size of data to fix this problem? We have control up to some extent on server side as well. Thanks, Sudhir
Re: Limitations in using ADB for our ws-clent
Hi Amila, Any word on this. Damian any thing from your side. Sudhir On Thu, Apr 30, 2009 at 7:55 PM, Sudhir Mongia sudhir.mon...@gmail.comwrote: Hi Amila, I am also running into the same issue. Could you please confirm which version of Axis2-ADB support both extension and restrictions? I can see the following on http://ws.apache.org/axis2/1_4_1/adb/adb-howto.html http://ws.apache.org/axis2/1_4_1/adb/adb-howto.html Known Limitations ADB is meant to be a 'Simple' databinding framework and was not meant to compile all types of schemas. The following limitations are the most highlighted. 1. Complex Type Extensions and Restrictions. The documentation says, it is a known limitation. Thanks, Sudhir On Thu, Apr 30, 2009 at 3:42 PM, Amila Suriarachchi amilasuriarach...@gmail.com wrote: On Thu, Apr 30, 2009 at 8:58 AM, Damian Carey jami...@gmail.com wrote: Hello, I'm moderately experience Java Desktop (Swing/RMI/DB/Hibernate etc) developer with some XML experience, but no SOAP experience. My current Axis2 problem is just that I do not have experienced eyes, and so I can't accurately sniff potential problems. I would be most appreciative of any suggestions / guidance / advice regarding these beginners issues. We have a task to connect ourselves to an existing webservice, and we have been given a WSDL file to develop our web services client. Question 1: Limitations of ADB: Firstly after reading http://ws.apache.org/axis2/1_4_1/userguide-creatingclients.html#choosingclient I decided on ADB as a client as it seems to be the simplest. However, that web page has the following intriguing comment regarding ADB : ... and has difficulty with structures such as XML Schema element extensions and restrictions. For what it is worth I have scanned the WSDL file and found zero instances of the string extension, and 26 instances of the string restriction. All the restrictions are of the form simpleType name=WorkType restriction base=xsd:string enumeration value=LABR/ enumeration value=OTH/ /restriction /simpleType Is it easy to tell if these potential ADB difficulties applies to us? Can experienced eyes look through a WSDL and recognise where ADB will/may have a problem? Or is it just a matter of waiting until testing to discover problems? Currently ADB supports both extension and restrictions. Question 2: Size of the stub: Going through the process on the Axis2 web site I created the stub. The WSDL file is 50KB, and the generated STUB is more than 50,000 lines long and 2.4MB in size!!! Now I was surprised by the size, but browsing through the stub it all seems reasonable and in order - even if it is a touch verbose. I really don't care about the size if it is going to work OK. I only care about the size if it may indicate that there may be a problem. use -u option. Does the massive size of the stub indicate any problem? Does it suggest that ADB may not cope and perhaps we should pursue one of the other methods? (such as XMLBeans or JiBX) thanks, Amila. Any guidance would be much appreciated. Thanks for your time. -Damian -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: Limitations in using ADB for our ws-clent
Sudhir, Sorry, no progress from my end. Currently I just have the WSDL and we are building our sw-client against that. Unfortunately we will not have an opportunity to test against the server until later, so we will not discover if ADB has a limitation until we have chewed up a lot of time. I am really happy with ADB - I think I have wrapped my head around it's main ideas - but there is still that lingering concern to discover if it will work. As I mentioned earlier in the thread we do have several instances of restriction in our WDSL - ubt it looks to be at the simple end of the spectrum. If anyone has any feel for ADB's limitations we would really appreciate guidance. Cheers, -Damian On Mon, May 4, 2009 at 6:55 PM, Sudhir Mongia sudhir.mon...@gmail.com wrote: Hi Amila, Any word on this. Damian any thing from your side. Sudhir On Thu, Apr 30, 2009 at 7:55 PM, Sudhir Mongia sudhir.mon...@gmail.com wrote: Hi Amila, I am also running into the same issue. Could you please confirm which version of Axis2-ADB support both extension and restrictions? I can see the following on http://ws.apache.org/axis2/1_4_1/adb/adb-howto.html Known Limitations ADB is meant to be a 'Simple' databinding framework and was not meant to compile all types of schemas. The following limitations are the most highlighted. Complex Type Extensions and Restrictions. The documentation says, it is a known limitation. Thanks, Sudhir On Thu, Apr 30, 2009 at 3:42 PM, Amila Suriarachchi amilasuriarach...@gmail.com wrote: On Thu, Apr 30, 2009 at 8:58 AM, Damian Carey jami...@gmail.com wrote: Hello, I'm moderately experience Java Desktop (Swing/RMI/DB/Hibernate etc) developer with some XML experience, but no SOAP experience. My current Axis2 problem is just that I do not have experienced eyes, and so I can't accurately sniff potential problems. I would be most appreciative of any suggestions / guidance / advice regarding these beginners issues. We have a task to connect ourselves to an existing webservice, and we have been given a WSDL file to develop our web services client. Question 1: Limitations of ADB: Firstly after reading http://ws.apache.org/axis2/1_4_1/userguide-creatingclients.html#choosingclient I decided on ADB as a client as it seems to be the simplest. However, that web page has the following intriguing comment regarding ADB : ... and has difficulty with structures such as XML Schema element extensions and restrictions. For what it is worth I have scanned the WSDL file and found zero instances of the string extension, and 26 instances of the string restriction. All the restrictions are of the form simpleType name=WorkType restriction base=xsd:string enumeration value=LABR/ enumeration value=OTH/ /restriction /simpleType Is it easy to tell if these potential ADB difficulties applies to us? Can experienced eyes look through a WSDL and recognise where ADB will/may have a problem? Or is it just a matter of waiting until testing to discover problems? Currently ADB supports both extension and restrictions. Question 2: Size of the stub: Going through the process on the Axis2 web site I created the stub. The WSDL file is 50KB, and the generated STUB is more than 50,000 lines long and 2.4MB in size!!! Now I was surprised by the size, but browsing through the stub it all seems reasonable and in order - even if it is a touch verbose. I really don't care about the size if it is going to work OK. I only care about the size if it may indicate that there may be a problem. use -u option. Does the massive size of the stub indicate any problem? Does it suggest that ADB may not cope and perhaps we should pursue one of the other methods? (such as XMLBeans or JiBX) thanks, Amila. Any guidance would be much appreciated. Thanks for your time. -Damian -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: Limitations in using ADB for our ws-clent
Hi; ADB has some limitations like not being able to adapt itself for the changing services. I mean that is suitable for the contract first approach. If your service provider make some changes on the wsdl. As an example add some more outpur parameters or changed the order of response elements. ADB fails. (There were lots of threads in this mail group complaining about the Unexpected subelement exceptions) On the other hand if your service provider finalized its service than it is simple to use. I 'm using it for integrating a very very core point like customer module of an finance project with Axis2. 1.4.1 ADB and I had no problem upto now. Yours. Ibrahim DEMIR From: Damian Carey jami...@gmail.com To: axis-user@ws.apache.org Sent: Monday, May 4, 2009 12:44:11 PM Subject: Re: Limitations in using ADB for our ws-clent Sudhir, Sorry, no progress from my end. Currently I just have the WSDL and we are building our sw-client against that. Unfortunately we will not have an opportunity to test against the server until later, so we will not discover if ADB has a limitation until we have chewed up a lot of time. I am really happy with ADB - I think I have wrapped my head around it's main ideas - but there is still that lingering concern to discover if it will work. As I mentioned earlier in the thread we do have several instances of restriction in our WDSL - ubt it looks to be at the simple end of the spectrum. If anyone has any feel for ADB's limitations we would really appreciate guidance. Cheers, -Damian On Mon, May 4, 2009 at 6:55 PM, Sudhir Mongia sudhir.mon...@gmail.com wrote: Hi Amila, Any word on this. Damian any thing from your side. Sudhir On Thu, Apr 30, 2009 at 7:55 PM, Sudhir Mongia sudhir.mon...@gmail.com wrote: Hi Amila, I am also running into the same issue. Could you please confirm which version of Axis2-ADB support both extension and restrictions? I can see the following on http://ws.apache.org/axis2/1_4_1/adb/adb-howto.html Known Limitations ADB is meant to be a 'Simple' databinding framework and was not meant to compile all types of schemas. The following limitations are the most highlighted. Complex Type Extensions and Restrictions. The documentation says, it is a known limitation. Thanks, Sudhir On Thu, Apr 30, 2009 at 3:42 PM, Amila Suriarachchi amilasuriarach...@gmail.com wrote: On Thu, Apr 30, 2009 at 8:58 AM, Damian Carey jami...@gmail.com wrote: Hello, I'm moderately experience Java Desktop (Swing/RMI/DB/Hibernate etc) developer with some XML experience, but no SOAP experience. My current Axis2 problem is just that I do not have experienced eyes, and so I can't accurately sniff potential problems. I would be most appreciative of any suggestions / guidance / advice regarding these beginners issues. We have a task to connect ourselves to an existing webservice, and we have been given a WSDL file to develop our web services client. Question 1: Limitations of ADB: Firstly after reading http://ws.apache.org/axis2/1_4_1/userguide-creatingclients.html#choosingclient I decided on ADB as a client as it seems to be the simplest. However, that web page has the following intriguing comment regarding ADB : ... and has difficulty with structures such as XML Schema element extensions and restrictions. For what it is worth I have scanned the WSDL file and found zero instances of the string extension, and 26 instances of the string restriction. All the restrictions are of the form simpleType name=WorkType restriction base=xsd:string enumeration value=LABR/ enumeration value=OTH/ /restriction /simpleType Is it easy to tell if these potential ADB difficulties applies to us? Can experienced eyes look through a WSDL and recognise where ADB will/may have a problem? Or is it just a matter of waiting until testing to discover problems? Currently ADB supports both extension and restrictions. Question 2: Size of the stub: Going through the process on the Axis2 web site I created the stub. The WSDL file is 50KB, and the generated STUB is more than 50,000 lines long and 2.4MB in size!!! Now I was surprised by the size, but browsing through the stub it all seems reasonable and in order - even if it is a touch verbose. I really don't care about the size if it is going to work OK. I only care about the size if it may indicate that there may be a problem. use -u option. Does the massive size of the stub indicate any problem? Does it suggest that ADB may not cope and perhaps we should pursue one of the other methods? (such as XMLBeans or JiBX) thanks, Amila. Any guidance would be much appreciated. Thanks for your time. -Damian -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
RE: Error communicating between two websevice
Hi Asankha, The reason I am going with the nhttp transport, is that I have these services running over HTTPS as well and I am not sure if there is any other way to use HTTPS with Axis2 without using nio connectors. Please do let me know if there is an alternative available. Thanks, -Salman _ From: Asankha Perera [mailto:asankha.apa...@gmail.com] On Behalf Of Asankha C. Perera Sent: Wednesday, April 29, 2009 7:44 AM To: axis-user@ws.apache.org Subject: Re: Error communicating between two websevice Hi Salman I am working on a web service which acts as a client as well as server. I am trying to deploy two instances of this web service on separate servers and try and setup a communication link between them. [ERROR] Received an internal server error : Internal Server Error Exception in thread HttpCoreNIOSender java.lang.NullPointerException at org.apache.axis2.transport.nhttp.ClientHandler.inputReady(ClientHandler.java :236) To Configure Axis2 I have made following changes to Axis2.xml: transportReceiver name=http class=org.apache.axis2.transport.nhttp.HttpCoreNIOListener parameter name=port locked=false9000/parameter parameter name=non-blocking locked=falsetrue/parameter /transportReceiver The org.apache.axis2.transport.nhttp transports are no longer bundled with vanilla Axis2. Unless you have any specific requirement, please switch over to the normal http transports, and possibly your problems would go away. cheers asankha -- Asankha C. Perera AdroitLogic, http://adroitlogic.org http://esbmagic.blogspot.com
Re: Limitations in using ADB for our ws-clent
Ibrahim, Thanks for your reply! That has increased my understanding of ADB. Do you know anything about this Axis2 website comment (http://ws.apache.org/axis2/1_4_1/userguide-creatingclients.html#choosingclient) that says the following regarding ADB: ... and has difficulty with structures such as XML Schema element extensions and restrictions. Is there anyway to find out if ADB may may have a problem with our restrictions??? I can't locate any further information about when or where it may have the problem. Thanks again, -Damian On Mon, May 4, 2009 at 8:22 PM, ibrahim demir ibrahimdem...@yahoo.com wrote: Hi; ADB has some limitations like not being able to adapt itself for the changing services. I mean that is suitable for the contract first approach. If your service provider make some changes on the wsdl. As an example add some more outpur parameters or changed the order of response elements. ADB fails. (There were lots of threads in this mail group complaining about the Unexpected subelement exceptions) On the other hand if your service provider finalized its service than it is simple to use. I 'm using it for integrating a very very core point like customer module of an finance project with Axis2. 1.4.1 ADB and I had no problem upto now. Yours. Ibrahim DEMIR From: Damian Carey jami...@gmail.com To: axis-user@ws.apache.org Sent: Monday, May 4, 2009 12:44:11 PM Subject: Re: Limitations in using ADB for our ws-clent Sudhir, Sorry, no progress from my end. Currently I just have the WSDL and we are building our sw-client against that. Unfortunately we will not have an opportunity to test against the server until later, so we will not discover if ADB has a limitation until we have chewed up a lot of time. I am really happy with ADB - I think I have wrapped my head around it's main ideas - but there is still that lingering concern to discover if it will work. As I mentioned earlier in the thread we do have several instances of restriction in our WDSL - ubt it looks to be at the simple end of the spectrum. If anyone has any feel for ADB's limitations we would really appreciate guidance. Cheers, -Damian On Mon, May 4, 2009 at 6:55 PM, Sudhir Mongia sudhir.mon...@gmail.com wrote: Hi Amila, Any word on this. Damian any thing from your side. Sudhir On Thu, Apr 30, 2009 at 7:55 PM, Sudhir Mongia sudhir.mon...@gmail.com wrote: Hi Amila, I am also running into the same issue. Could you please confirm which version of Axis2-ADB support both extension and restrictions? I can see the following on http://ws.apache.org/axis2/1_4_1/adb/adb-howto.html Known Limitations ADB is meant to be a 'Simple' databinding framework and was not meant to compile all types of schemas. The following limitations are the most highlighted. Complex Type Extensions and Restrictions. The documentation says, it is a known limitation. Thanks, Sudhir On Thu, Apr 30, 2009 at 3:42 PM, Amila Suriarachchi amilasuriarach...@gmail.com wrote: On Thu, Apr 30, 2009 at 8:58 AM, Damian Carey jami...@gmail.com wrote: Hello, I'm moderately experience Java Desktop (Swing/RMI/DB/Hibernate etc) developer with some XML experience, but no SOAP experience. My current Axis2 problem is just that I do not have experienced eyes, and so I can't accurately sniff potential problems. I would be most appreciative of any suggestions / guidance / advice regarding these beginners issues. We have a task to connect ourselves to an existing webservice, and we have been given a WSDL file to develop our web services client. Question 1: Limitations of ADB: Firstly after reading http://ws.apache.org/axis2/1_4_1/userguide-creatingclients.html#choosingclient I decided on ADB as a client as it seems to be the simplest. However, that web page has the following intriguing comment regarding ADB : ... and has difficulty with structures such as XML Schema element extensions and restrictions. For what it is worth I have scanned the WSDL file and found zero instances of the string extension, and 26 instances of the string restriction. All the restrictions are of the form simpleType name=WorkType restriction base=xsd:string enumeration value=LABR/ enumeration value=OTH/ /restriction /simpleType Is it easy to tell if these potential ADB difficulties applies to us? Can experienced eyes look through a WSDL and recognise where ADB will/may have a problem? Or is it just a matter of waiting until testing to discover problems? Currently ADB supports both extension and restrictions. Question 2: Size of the stub: Going through the process on the Axis2 web site I created the stub. The WSDL file is 50KB, and the generated STUB is more than 50,000 lines long and 2.4MB in size!!! Now I was surprised by the size, but browsing through the stub it all seems reasonable and in order - even if it is a touch verbose. I
Re: Limitations in using ADB for our ws-clent
Hi; ... and has difficulty with structures such as XML Schema element extensions and restrictions. has the same meaning with what I habe said. It can not dinamically adapt itself to the changes on the schema definitions. For example if a service returning these information name surname customer_code one day it starts returning: customer_second_name name surname customer_code than ADB fails till you regenrate the client. It can not get the name,surname,customer_code elements form the response because of the parsing structure. It really has a hard_coded parsing mecanism. There are some tricks to ignore these runtime exceptions but I really do not advice it. Yours. Ibrahim DEMIR CyberSoft Yazilim Muh. http://www.ibrahimdemir.org From: Damian Carey jami...@gmail.com To: axis-user@ws.apache.org Sent: Monday, May 4, 2009 1:45:44 PM Subject: Re: Limitations in using ADB for our ws-clent Ibrahim, Thanks for your reply! That has increased my understanding of ADB. Do you know anything about this Axis2 website comment (http://ws.apache.org/axis2/1_4_1/userguide-creatingclients.html#choosingclient) that says the following regarding ADB: ... and has difficulty with structures such as XML Schema element extensions and restrictions. Is there anyway to find out if ADB may may have a problem with our restrictions??? I can't locate any further information about when or where it may have the problem. Thanks again, -Damian On Mon, May 4, 2009 at 8:22 PM, ibrahim demir ibrahimdem...@yahoo.com wrote: Hi; ADB has some limitations like not being able to adapt itself for the changing services. I mean that is suitable for the contract first approach. If your service provider make some changes on the wsdl. As an example add some more outpur parameters or changed the order of response elements. ADB fails. (There were lots of threads in this mail group complaining about the Unexpected subelement exceptions) On the other hand if your service provider finalized its service than it is simple to use. I 'm using it for integrating a very very core point like customer module of an finance project with Axis2. 1.4.1 ADB and I had no problem upto now. Yours. Ibrahim DEMIR From: Damian Carey jami...@gmail.com To: axis-user@ws.apache.org Sent: Monday, May 4, 2009 12:44:11 PM Subject: Re: Limitations in using ADB for our ws-clent Sudhir, Sorry, no progress from my end. Currently I just have the WSDL and we are building our sw-client against that. Unfortunately we will not have an opportunity to test against the server until later, so we will not discover if ADB has a limitation until we have chewed up a lot of time. I am really happy with ADB - I think I have wrapped my head around it's main ideas - but there is still that lingering concern to discover if it will work. As I mentioned earlier in the thread we do have several instances of restriction in our WDSL - ubt it looks to be at the simple end of the spectrum. If anyone has any feel for ADB's limitations we would really appreciate guidance. Cheers, -Damian On Mon, May 4, 2009 at 6:55 PM, Sudhir Mongia sudhir.mon...@gmail.com wrote: Hi Amila, Any word on this. Damian any thing from your side. Sudhir On Thu, Apr 30, 2009 at 7:55 PM, Sudhir Mongia sudhir.mon...@gmail.com wrote: Hi Amila, I am also running into the same issue. Could you please confirm which version of Axis2-ADB support both extension and restrictions? I can see the following on http://ws.apache.org/axis2/1_4_1/adb/adb-howto.html Known Limitations ADB is meant to be a 'Simple' databinding framework and was not meant to compile all types of schemas. The following limitations are the most highlighted. Complex Type Extensions and Restrictions. The documentation says, it is a known limitation. Thanks, Sudhir On Thu, Apr 30, 2009 at 3:42 PM, Amila Suriarachchi amilasuriarach...@gmail.com wrote: On Thu, Apr 30, 2009 at 8:58 AM, Damian Carey jami...@gmail.com wrote: Hello, I'm moderately experience Java Desktop (Swing/RMI/DB/Hibernate etc) developer with some XML experience, but no SOAP experience. My current Axis2 problem is just that I do not have experienced eyes, and so I can't accurately sniff potential problems. I would be most appreciative of any suggestions / guidance / advice regarding these beginners issues. We have a task to connect ourselves to an existing webservice, and we have been given a WSDL file to develop our web services client. Question 1: Limitations of ADB: Firstly after reading http://ws.apache.org/axis2/1_4_1/userguide-creatingclients.html#choosingclient I decided on ADB as a client as it seems to be the simplest. However, that web page has the following intriguing comment regarding ADB : ... and has difficulty with structures such as XML Schema element extensions and restrictions. For
Re: Limitations in using ADB for our ws-clent
Excellent explanation. The more you explain the more the fog in my head is lifting!!! I really appreciate your input. Thank you, -Damian On Mon, May 4, 2009 at 9:13 PM, ibrahim demir ibrahimdem...@yahoo.com wrote: Hi; ... and has difficulty with structures such as XML Schema element extensions and restrictions. has the same meaning with what I habe said. It can not dinamically adapt itself to the changes on the schema definitions. For example if a service returning these information name surname customer_code one day it starts returning: customer_second_name name surname customer_code than ADB fails till you regenrate the client. It can not get the name,surname,customer_code elements form the response because of the parsing structure. It really has a hard_coded parsing mecanism. There are some tricks to ignore these runtime exceptions but I really do not advice it. Yours. Ibrahim DEMIR CyberSoft Yazilim Muh. http://www.ibrahimdemir.org From: Damian Carey jami...@gmail.com To: axis-user@ws.apache.org Sent: Monday, May 4, 2009 1:45:44 PM Subject: Re: Limitations in using ADB for our ws-clent Ibrahim, Thanks for your reply! That has increased my understanding of ADB. Do you know anything about this Axis2 website comment (http://ws.apache.org/axis2/1_4_1/userguide-creatingclients.html#choosingclient) that says the following regarding ADB: ... and has difficulty with structures such as XML Schema element extensions and restrictions. Is there anyway to find out if ADB may may have a problem with our restrictions??? I can't locate any further information about when or where it may have the problem. Thanks again, -Damian On Mon, May 4, 2009 at 8:22 PM, ibrahim demir ibrahimdem...@yahoo.com wrote: Hi; ADB has some limitations like not being able to adapt itself for the changing services. I mean that is suitable for the contract first approach. If your service provider make some changes on the wsdl. As an example add some more outpur parameters or changed the order of response elements. ADB fails. (There were lots of threads in this mail group complaining about the Unexpected subelement exceptions) On the other hand if your service provider finalized its service than it is simple to use. I 'm using it for integrating a very very core point like customer module of an finance project with Axis2. 1.4.1 ADB and I had no problem upto now. Yours. Ibrahim DEMIR From: Damian Carey jami...@gmail.com To: axis-user@ws.apache.org Sent: Monday, May 4, 2009 12:44:11 PM Subject: Re: Limitations in using ADB for our ws-clent Sudhir, Sorry, no progress from my end. Currently I just have the WSDL and we are building our sw-client against that. Unfortunately we will not have an opportunity to test against the server until later, so we will not discover if ADB has a limitation until we have chewed up a lot of time. I am really happy with ADB - I think I have wrapped my head around it's main ideas - but there is still that lingering concern to discover if it will work. As I mentioned earlier in the thread we do have several instances of restriction in our WDSL - ubt it looks to be at the simple end of the spectrum. If anyone has any feel for ADB's limitations we would really appreciate guidance. Cheers, -Damian On Mon, May 4, 2009 at 6:55 PM, Sudhir Mongia sudhir.mon...@gmail.com wrote: Hi Amila, Any word on this. Damian any thing from your side. Sudhir On Thu, Apr 30, 2009 at 7:55 PM, Sudhir Mongia sudhir.mon...@gmail.com wrote: Hi Amila, I am also running into the same issue. Could you please confirm which version of Axis2-ADB support both extension and restrictions? I can see the following on http://ws.apache.org/axis2/1_4_1/adb/adb-howto.html Known Limitations ADB is meant to be a 'Simple' databinding framework and was not meant to compile all types of schemas. The following limitations are the most highlighted. Complex Type Extensions and Restrictions. The documentation says, it is a known limitation. Thanks, Sudhir On Thu, Apr 30, 2009 at 3:42 PM, Amila Suriarachchi amilasuriarach...@gmail.com wrote: On Thu, Apr 30, 2009 at 8:58 AM, Damian Carey jami...@gmail.com wrote: Hello, I'm moderately experience Java Desktop (Swing/RMI/DB/Hibernate etc) developer with some XML experience, but no SOAP experience. My current Axis2 problem is just that I do not have experienced eyes, and so I can't accurately sniff potential problems. I would be most appreciative of any suggestions / guidance / advice regarding these beginners issues. We have a task to connect ourselves to an existing webservice, and we have been given a WSDL file to develop our web services client. Question 1: Limitations of ADB: Firstly after reading http://ws.apache.org/axis2/1_4_1/userguide-creatingclients.html#choosingclient I decided
Re: Limitations in using ADB for our ws-clent
... and has difficulty with structures such as XML Schema element extensions and restrictions. has the same meaning with what I habe said. It can not dinamically adapt itself to the changes on the schema definitions. I'm not an expert of ADB, but this statement doesn't seem correct to me. The ADB documentation obviously refers to the XML Schema concepts of extension and restriction, which allow to derive new types from existing types. It has nothing to do with the behavior of ADB with respect to changes to the schema (which cause problems to any databinding framework). Probably ADB doesn't (fully) support extensions and restrictions on complex types, but for simple types this should work (but again, I'm not very familiar with ADB). Andreas
[Session Id:axis2]
Hi All, I'm going to work on a web service, in which I need to get the session Id for the currently accessing client. I've little knowledge of session management in axis2 web service. But I'm pretty aware of service life cycle (init (), destroy () methods). I've decided to use scope 'soapsession' for the web service. In this scenario, can anybody tell me please, how to set or get session id for a particular client? Or how to fetch session id from soap header (I realize that session id is available in soap header). Also, is it possible to get 'request' and 'response' objects for the Http Clients? Quick response will be appreciated, Thanks in advance. Vaibhav Kumar Arya Associate Software Engineer === Private, Confidential and Privileged. This e-mail and any files and attachments transmitted with it are confidential and/or privileged. They are intended solely for the use of the intended recipient. The content of this e-mail and any file or attachment transmitted with it may have been changed or altered without the consent of the author. If you are not the intended recipient, please note that any review, dissemination, disclosure, alteration, printing, circulation or Transmission of this e-mail and/or any file or attachment transmitted with it, is prohibited and may be unlawful. If you have received this e-mail or any file or attachment transmitted with it in error please notify OTS Solutions at i...@otssolutions.com ===
Re: [Session Id:axis2]
Hi, You can access the session id at the server side using following method (method is there in the message context) getServiceGroupContextId And for the client side you can not set the session id, what you can do is when you do the first call you can set the manage session, or call setManageSession(true) in option object. And if you really want to pass the session id between clients then you can have a look at following KB. http://wso2.org/library/3185 Thank you! Deepal Hi All, I’m going to work on a web service, in which I need to get the session Id for the currently accessing client. I’ve little knowledge of session management in axis2 web service. But I’m pretty aware of *service life cycle (init (), destroy () methods)*. I’ve decided to use scope ‘*soapsession’* for the web service. In this scenario, can anybody tell me please, how to set or get session id for a particular client? Or how to fetch session id from soap header (*I realize that session id is available in soap header*). / Also, is it possible to get ‘request’ and ‘response’ objects for the Http Clients?/ Quick response will be appreciated, Thanks in advance. **Vaibhav Kumar Arya** **Associate Software Engineer** === Private, Confidential and Privileged. This e-mail and any files and attachments transmitted with it are confidential and/or privileged. They are intended solely for the use of the intended recipient. The content of this e-mail and any file or attachment transmitted with it may have been changed or altered without the consent of the author. If you are not the intended recipient, please note that any review, dissemination, disclosure, alteration, printing, circulation or Transmission of this e-mail and/or any file or attachment transmitted with it, is prohibited and may be unlawful. If you have received this e-mail or any file or attachment transmitted with it in error please notify OTS Solutions at i...@otssolutions.com === -- Thank you! http://blogs.deepal.org http://deepal.org
Handlers
Hi All, I need some resources to learn about handlers. I have a vogue idea about it, but i would like to know more about how to write handlers for security, addressing, logging etc. using Axis2 Thanks Kris -- View this message in context: http://www.nabble.com/Handlers-tp23370955p23370955.html Sent from the Axis - User mailing list archive at Nabble.com.
RE: Handlers
This will help clarify the reason to use handlers as well as illustrating how to write a simple Handler http://www.packtpub.com/article/handler-and-phase-in-apache-axis HTH Martin __ Disclaimer and Confidentiality/Verzicht und Vertraulichkeitanmerkung / Note de déni et de confidentialité This message is confidential. If you should not be the intended receiver, then we ask politely to report. Each unauthorized forwarding or manufacturing of a copy is inadmissible. This message serves only for the exchange of information and has no legal binding effect. Due to the easy manipulation of emails we cannot take responsibility over the the contents. Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Mon, 4 May 2009 08:37:55 -0700 From: kit...@gmail.com To: axis-user@ws.apache.org Subject: Handlers Hi All, I need some resources to learn about handlers. I have a vogue idea about it, but i would like to know more about how to write handlers for security, addressing, logging etc. using Axis2 Thanks Kris -- View this message in context: http://www.nabble.com/Handlers-tp23370955p23370955.html Sent from the Axis - User mailing list archive at Nabble.com. _ Windows Live™: Keep your life in sync. http://windowslive.com/explore?ocid=TXT_TAGLM_BR_life_in_synch_052009
RE: [axis2] MTOM Performance
Hello All, With the lack of any response from the group, should I assume that there has been NO benchmarking done on Axis2/MTOM at all? If there has been some, can somebody please point me to it? Sowmi From: Thallapragada, Sowmi Sent: Sunday, May 03, 2009 9:52 PM To: axis-user@ws.apache.org Subject: RE: [axis2] MTOM Performance I'd appreciate any pointers regarding this. Thanks! From: Thallapragada, Sowmi Sent: Saturday, May 02, 2009 12:34 AM To: 'axis-user@ws.apache.org' Subject: [axis2] MTOM Performance Can anyone point me to recent performance metrics on Axis2 (1.4.x) /MTOM? - Sowmi
RE: What is the status of Axis?
Florian, I guess there is no development on Axis after the 1.4 release. There is a new version of Axis called Axis2 and right now it is in release 1.4.1, you can get more details on Axis2 at http://ws.apache.org/axis2/ Thanks Raghu -Original Message- From: Florian Kirchhoff [mailto:florian.kirchh...@qwest.com] Sent: Monday, May 04, 2009 2:22 PM To: axis-user@ws.apache.org Subject: What is the status of Axis? Hi, since the last release of Axis (Axis 1) was 1.4 in november 2006 what is the status of development on Axis? Is it in bugs-fix-only mode? Thanks, Florian -- View this message in context: http://www.nabble.com/What-is-the-status-of-Axis--tp23374857p23374857.ht ml Sent from the Axis - User mailing list archive at Nabble.com.
calling Call.setClientHandlers from Stub causes SAXException
Hello everyone, and thanks in advance for your help.
I'm developing a client to consume a web service. I used WSDL2Java
(axis1-4) to produce stub classes and everything works great - I
successfully process the service. However, I'm required to store the actual
request/response documents with the transaction, and this is where I've run
into trouble.
The only way I could figure out how to do this properly was to modify the
generated service stub.
I added:
public void setClientHandlers(org.apache.axis.Handler requestHandler,
org.apache.axis.Handler responseHandler) {
this.requestHandler = requestHandler;
this.responseHandler = responseHandler;
}
And modified the webservice method stub as follows:
org.apache.axis.client.Call _call = createCall(); //Added these lines...
if (requestHandler != null responseHandler != null)
_call.setClientHandlers(requestHandler, responseHandler); //end add
_call.setOperation(_operations[0]);
try {
java.lang.Object _resp = _call.invoke(new java.lang.Object[]
{parameters});
I created the following classes:
public class MyRequestHandler extends
org.apache.axis.handlers.LogHandler {
public void invoke(org.apache.axis.MessageContext
msgContext) throws org.apache.axis.AxisFault {
try {
SOAPMessageContext smc =
(SOAPMessageContext)msgContext;
SOAPMessage msg = smc.getMessage();
System.out.println(request:);
msg.writeTo(System.out);
}
catch (Exception e) {
e.printStackTrace();
throw new
org.apache.axis.AxisFault(e.getMessage());
}
}
}
//super.invoke(msgContext);
public class MyResponseHandler extends
org.apache.axis.handlers.LogHandler {
public void invoke(org.apache.axis.MessageContext
msgContext) throws org.apache.axis.AxisFault {
try {
SOAPMessageContext smc =
(SOAPMessageContext)msgContext;
SOAPMessage msg = smc.getMessage();
System.out.println(response:);
msg.writeTo(System.out);
}
catch (Exception e) {
e.printStackTrace();
throw new
org.apache.axis.AxisFault(e.getMessage());
}
}
}
And then set the handlers from the client code. With this code in place, I
get the following exception:
org.xml.sax.SAXException: SimpleDeserializer encountered a child element,
which is NOT expected, in something it was trying to deserialize.
at
org.apache.axis.encoding.ser.SimpleDeserializer.onStartChild(SimpleDeseriali
zer.java:145)
at
org.apache.axis.encoding.DeserializationContext.startElement(Deserialization
Context.java:1035)
at
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165)
at
org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:
1141)
at
org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
at org.apache.axis.client.Call.invoke(Call.java:2467)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)...
I've experimented with different version of handler classes (which are run
by the way - I access the request and response), and even tried setting the
handler explicitly to null (in the stub class). The bottom line: if I have
the Call.setClientHandlers(handler, handler) in place, the exception is
returned. Obviously I'm screwing something up, but not sure what.
I did, but the way, consider setting handlers the more conventional way
(handler chain from the client code), but this method only allows me to
specify a class, not an instance, so I loose all context (which I need to be
able to store the request/response along with the other transactional
information).
Please let me know if more information is needed.
Michael Lee
Axis2/Rampart 1.4 - Ecrypt header information
Hello, Does anybody know how I can tell rampart to encrypt header information in the SOAP response? Regards, Mohannad
RE: calling Call.setClientHandlers from Stub causes SAXException
back out all the customised code in setClientHandlers to acquire servletRequest
and servletResponse
use this instead
HttpServletResponse response =
(HttpServletResponse)
msgContext.getProperty(HTTPConstants.MC_HTTP_SERVLETRESPONSE);
HttpServletRequest req = (HttpServletRequest)
messageContext.getProperty(
HTTPConstants.MC_HTTP_SERVLETREQUEST);
Martin
__
Disclaimer and Confidentiality/Verzicht und Vertraulichkeitanmerkung / Note de
déni et de confidentialité
This message is confidential. If you should not be the intended receiver, then
we ask politely to report. Each unauthorized forwarding or manufacturing of a
copy is inadmissible. This message serves only for the exchange of information
and has no legal binding effect. Due to the easy manipulation of emails we
cannot take responsibility over the the contents.
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
From: m...@myriad-development.com
To: axis-user@ws.apache.org
Subject: calling Call.setClientHandlers from Stub causes SAXException
Date: Mon, 4 May 2009 15:34:15 -0500
calling Call.setClientHandlers from Stub causes SAXException
Hello everyone, and thanks in advance for your help.
I'm developing a client to consume a web service. I used WSDL2Java
(axis1-4) to produce stub classes and everything works great - I successfully
process the service. However, I'm required to store the actual
request/response documents with the transaction, and this is where I've run
into trouble.
The only way I could figure out how to do this properly was to modify the
generated service stub.
I added:
public void setClientHandlers(org.apache.axis.Handler requestHandler,
org.apache.axis.Handler responseHandler) {
this.requestHandler = requestHandler;
this.responseHandler = responseHandler;
}
And modified the webservice method stub as follows:
org.apache.axis.client.Call _call = createCall(); //Added these lines...
if (requestHandler != null responseHandler != null)
_call.setClientHandlers(requestHandler, responseHandler); //end add
_call.setOperation(_operations[0]);
try {
java.lang.Object _resp = _call.invoke(new java.lang.Object[]
{parameters});
I created the following classes:
public class MyRequestHandler extends
org.apache.axis.handlers.LogHandler {
public void invoke(org.apache.axis.MessageContext
msgContext) throws org.apache.axis.AxisFault {
try {
SOAPMessageContext smc =
(SOAPMessageContext)msgContext;
SOAPMessage msg = smc.getMessage();
System.out.println(request:);
msg.writeTo(System.out);
}
catch (Exception e) {
e.printStackTrace();
throw new
org.apache.axis.AxisFault(e.getMessage());
}
}
}
//super.invoke(msgContext);
public class MyResponseHandler extends
org.apache.axis.handlers.LogHandler {
public void invoke(org.apache.axis.MessageContext
msgContext) throws org.apache.axis.AxisFault {
try {
SOAPMessageContext smc =
(SOAPMessageContext)msgContext;
SOAPMessage msg = smc.getMessage();
System.out.println(response:);
msg.writeTo(System.out);
}
catch (Exception e) {
e.printStackTrace();
throw new
org.apache.axis.AxisFault(e.getMessage());
}
}
}
And then set the handlers from the client code. With this code in place, I get
the following exception:
org.xml.sax.SAXException:
RE: Axis2/Rampart 1.4 - Ecrypt header information
you want to look at implmenting OnlySignEntireHeadersAndBody element e.g.
sp:OnlySignEntireHeadersAndBody/
this is included in policy-mtom-security.xml
the OnlySignEntireHeadersAndBody element would need to be included in a binding
which references http://schemas.xmlsoap.org/ws/2005/07/securitypolicy namespace
e.g.
sp:AsymmetricBinding
xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy;
Axis2-1.3 has a MTOMAssertionTestCase sample testcase you can use
package org.apache.axis2.policy.model;
import junit.framework.TestCase;
import org.apache.axiom.om.OMElement;
import org.apache.axiom.om.impl.builder.StAXOMBuilder;
import org.apache.neethi.Assertion;
import org.apache.neethi.Policy;
import org.apache.neethi.PolicyEngine;
import java.util.Iterator;
import java.util.List;
public class MTOMAssertionTest extends TestCase {
public void testSymmBinding() {
try {
Policy p = this.getPolicy(System.getProperty(basedir, .) +
/test-resources/policy-mtom-security.xml);
List assertions = (List)p.getAlternatives().next();
boolean isMTOMAssertionFound = false;
for (Iterator iter = assertions.iterator(); iter.hasNext();) {
Assertion assertion = (Assertion)iter.next();
if (assertion instanceof MTOMAssertion) {
isMTOMAssertionFound = true;
MTOMAssertion mtomModel = (MTOMAssertion)assertion;
assertEquals(MIME Serialization assertion not processed,
false,
mtomModel.isOptional());
}
}
//The Asymm binding mean is not built in the policy processing :-(
assertTrue(MTOM Assertion not found., isMTOMAssertionFound);
} catch (Exception e) {
e.printStackTrace();
fail(e.getMessage());
}
}
private Policy getPolicy(String filePath) throws Exception {
StAXOMBuilder builder = new StAXOMBuilder(filePath);
OMElement elem = builder.getDocumentElement();
return PolicyEngine.getPolicy(elem);
}
}
Martin Gainty
United Health Group Medicode publishers 2002-2003
deNovisMedicalSystems HIPAA EDI 2004
Curaspan the eDischarge Company HL7 Interfaces 2006
USCitizen(Contractor)
__
Disclaimer and Confidentiality/Verzicht und Vertraulichkeitanmerkung / Note de
déni et de confidentialité
This message is confidential. If you should not be the intended receiver, then
we ask politely to report. Each unauthorized forwarding or manufacturing of a
copy is inadmissible. This message serves only for the exchange of information
and has no legal binding effect. Due to the easy manipulation of emails we
cannot take responsibility over the the contents.
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
Date: Tue, 5 May 2009 09:08:52 +1200
From: mohannad.hamma...@orionhealth.com
To: axis-user@ws.apache.org
Subject: Axis2/Rampart 1.4 - Ecrypt header information
Hello,
Does anybody know how I can tell rampart to encrypt header information in the
SOAP response?
Regards,
Mohannad
_
Hotmail® has a new way to see what's up with your friends.
http://windowslive.com/Tutorial/Hotmail/WhatsNew?ocid=TXT_TAGLM_WL_HM_Tutorial_WhatsNew1_052009
Re: Axis2/Rampart 1.4 - Ecrypt header information
Thank you for your reply Martin, I am trying to use WS Policy to encrypt the
header as well as the body. I saw that element in the samples that came with
rampart. Do you know if the example (sample 3) is equivalent to a set of
actions of 'Signature Encrypt Timestamp'?
Regards,
Mohannad
- Original Message -
From: Martin Gainty mgai...@hotmail.com
To: axis-user@ws.apache.org
Sent: Tuesday, 5 May, 2009 11:32:34 GMT +12:00 New Zealand
Subject: RE: Axis2/Rampart 1.4 - Ecrypt header information
you want to look at implmenting OnlySignEntireHeadersAndBody element e.g.
sp:OnlySignEntireHeadersAndBody/
this is included in policy-mtom-security.xml
the OnlySignEntireHeadersAndBody element would need to be included in a binding
which references http://schemas.xmlsoap.org/ws/2005/07/securitypolicy namespace
e.g.
sp:AsymmetricBinding
xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy;
Axis2-1.3 has a MTOMAssertionTestCase sample testcase you can use
package org.apache.axis2.policy.model;
import junit.framework.TestCase;
import org.apache.axiom.om.OMElement;
import org.apache.axiom.om.impl.builder.StAXOMBuilder;
import org.apache.neethi.Assertion;
import org.apache.neethi.Policy;
import org.apache.neethi.PolicyEngine;
import java.util.Iterator;
import java.util.List;
public class MTOMAssertionTest extends TestCase {
public void testSymmBinding() {
try {
Policy p = this.getPolicy(System.getProperty(basedir, .) +
/test-resources/policy-mtom-security.xml);
List assertions = (List)p.getAlternatives().next();
boolean isMTOMAssertionFound = false;
for (Iterator iter = assertions.iterator(); iter.hasNext();) {
Assertion assertion = (Assertion)iter.next();
if (assertion instanceof MTOMAssertion) {
isMTOMAssertionFound = true;
MTOMAssertion mtomModel = (MTOMAssertion)assertion;
assertEquals(MIME Serialization assertion not processed, false,
mtomModel.isOptional());
}
}
//The Asymm binding mean is not built in the policy processing :-(
assertTrue(MTOM Assertion not found., isMTOMAssertionFound);
} catch (Exception e) {
e.printStackTrace();
fail(e.getMessage());
}
}
private Policy getPolicy(String filePath) throws Exception {
StAXOMBuilder builder = new StAXOMBuilder(filePath);
OMElement elem = builder.getDocumentElement();
return PolicyEngine.getPolicy(elem);
}
}
Martin Gainty
United Health Group Medicode publishers 2002-2003
deNovisMedicalSystems HIPAA EDI 2004
Curaspan the eDischarge Company HL7 Interfaces 2006
USCitizen(Contractor)
__
Disclaimer and Confidentiality/Verzicht und Vertraulichkeitanmerkung / Note de
déni et de confidentialité
This message is confidential. If you should not be the intended receiver, then
we ask politely to report. Each unauthorized forwarding or manufacturing of a
copy is inadmissible. This message serves only for the exchange of information
and has no legal binding effect. Due to the easy manipulation of emails we
cannot take responsibility over the the contents.
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
Date: Tue, 5 May 2009 09:08:52 +1200
From: mohannad.hamma...@orionhealth.com
To: axis-user@ws.apache.org
Subject: Axis2/Rampart 1.4 - Ecrypt header information
Hello,
Does anybody know how I can tell rampart to encrypt header information in the
SOAP response?
Regards,
Mohannad
Hotmail® has a new way to see what's up with your friends. Check it out.
