Re: Serialization of Wrapped WSDL Parameter Objects
On Sun, Jul 20, 2008 at 7:00 AM, Samisa Abeysinghe [EMAIL PROTECTED] wrote: Curtis Jensen wrote: Thanks. I'll look into client side modules. Any suggestions on where to look for a good example? Everything I've found so far was setting up for server side modules. You can see how addressing is engaged on client side. Do you have a URL or know of one of the samples that describes this? How about the return trip? When we recieve the response string, how would that get deserialized back into an object? The axis engine isn't involved at that point. You can build the full OM tree in the module if you wish so in the in path handler of the module. Which module? How would I invoke the path handler with just a string? On Sun, Jul 20, 2008 at 12:43 AM, Samisa Abeysinghe [EMAIL PROTECTED] wrote: Curtis Jensen wrote: Thanks for the suggestion. I assume you meant the lOggin module sample. It was promising. However, this looks like a server side solution. I'm looking for a client side solution. It is not. It is a module, and hence can be engaged on client side as well. Maybe the logging solution can be turned into a client solution, but I'm not sure how. When our application attempts to call a web service, we would like to save the SOAP message off before it contacts the web service. We pass that SOAP message String to a third party who handles the actual communication to the web service. This is for the case when our communications is down for some reason or we are behind a restrictive firewall that is blocking http. The third party passes back the response SOAP message. This is the interface we have been given. I need to be able to generate the SOAP xml as it would have been sent to a web service. I then need to turn a response XML message back into a Java object just as Axis would. All on the client side. Again, you can use a module similar to the logging module to get this job done. Thanks, Samisa... Is this possible? Thanks again, Curtis On Fri, Jul 18, 2008 at 11:17 PM, Samisa Abeysinghe [EMAIL PROTECTED] wrote: Curtis Jensen wrote: I'm using Axis2 to generate web service clients. Everything is working fine. Now, I need to generate the SOAP XML string of what would be sent through HTTP so that I can save it for processing later. I can get a handle to the the java object Axis generated to represent the web service parameter. I can create the Call object and the OperationDescription for the call. I'm having trouble generating the SOAP XML. I've tried a couple of different things (some hackish, some less hackish). I can never quite generate the exact XML that Axis is sending (I created a proxy service to capture the exact SOAP that Axis is sending). Does someone have experience with this? Can they're share a little code example to get me going? Have you had a look at the ligging module sample. That shows you how you could capture the SOAP messages, incomming and out going. You may improve that sample to fit your needs. Samisa... Also, I then need to do the reverse. Take the response SOAP XML string and convert it into its Java object class instance. Thanks, Curtis -- Samisa Abeysinghe http://people.apache.org/~samisa/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Samisa Abeysinghe http://people.apache.org/~samisa/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Samisa Abeysinghe http://people.apache.org/~samisa/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Serialization of Wrapped WSDL Parameter Objects
Curtis Jensen wrote: Thanks for the suggestion. I assume you meant the lOggin module sample. It was promising. However, this looks like a server side solution. I'm looking for a client side solution. It is not. It is a module, and hence can be engaged on client side as well. Maybe the logging solution can be turned into a client solution, but I'm not sure how. When our application attempts to call a web service, we would like to save the SOAP message off before it contacts the web service. We pass that SOAP message String to a third party who handles the actual communication to the web service. This is for the case when our communications is down for some reason or we are behind a restrictive firewall that is blocking http. The third party passes back the response SOAP message. This is the interface we have been given. I need to be able to generate the SOAP xml as it would have been sent to a web service. I then need to turn a response XML message back into a Java object just as Axis would. All on the client side. Again, you can use a module similar to the logging module to get this job done. Thanks, Samisa... Is this possible? Thanks again, Curtis On Fri, Jul 18, 2008 at 11:17 PM, Samisa Abeysinghe [EMAIL PROTECTED] wrote: Curtis Jensen wrote: I'm using Axis2 to generate web service clients. Everything is working fine. Now, I need to generate the SOAP XML string of what would be sent through HTTP so that I can save it for processing later. I can get a handle to the the java object Axis generated to represent the web service parameter. I can create the Call object and the OperationDescription for the call. I'm having trouble generating the SOAP XML. I've tried a couple of different things (some hackish, some less hackish). I can never quite generate the exact XML that Axis is sending (I created a proxy service to capture the exact SOAP that Axis is sending). Does someone have experience with this? Can they're share a little code example to get me going? Have you had a look at the ligging module sample. That shows you how you could capture the SOAP messages, incomming and out going. You may improve that sample to fit your needs. Samisa... Also, I then need to do the reverse. Take the response SOAP XML string and convert it into its Java object class instance. Thanks, Curtis -- Samisa Abeysinghe http://people.apache.org/~samisa/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Samisa Abeysinghe http://people.apache.org/~samisa/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Serialization of Wrapped WSDL Parameter Objects
Thanks. I'll look into client side modules. Any suggestions on where to look for a good example? Everything I've found so far was setting up for server side modules. How about the return trip? When we recieve the response string, how would that get deserialized back into an object? The axis engine isn't involved at that point. Thanks, Curtis On Sun, Jul 20, 2008 at 12:43 AM, Samisa Abeysinghe [EMAIL PROTECTED] wrote: Curtis Jensen wrote: Thanks for the suggestion. I assume you meant the lOggin module sample. It was promising. However, this looks like a server side solution. I'm looking for a client side solution. It is not. It is a module, and hence can be engaged on client side as well. Maybe the logging solution can be turned into a client solution, but I'm not sure how. When our application attempts to call a web service, we would like to save the SOAP message off before it contacts the web service. We pass that SOAP message String to a third party who handles the actual communication to the web service. This is for the case when our communications is down for some reason or we are behind a restrictive firewall that is blocking http. The third party passes back the response SOAP message. This is the interface we have been given. I need to be able to generate the SOAP xml as it would have been sent to a web service. I then need to turn a response XML message back into a Java object just as Axis would. All on the client side. Again, you can use a module similar to the logging module to get this job done. Thanks, Samisa... Is this possible? Thanks again, Curtis On Fri, Jul 18, 2008 at 11:17 PM, Samisa Abeysinghe [EMAIL PROTECTED] wrote: Curtis Jensen wrote: I'm using Axis2 to generate web service clients. Everything is working fine. Now, I need to generate the SOAP XML string of what would be sent through HTTP so that I can save it for processing later. I can get a handle to the the java object Axis generated to represent the web service parameter. I can create the Call object and the OperationDescription for the call. I'm having trouble generating the SOAP XML. I've tried a couple of different things (some hackish, some less hackish). I can never quite generate the exact XML that Axis is sending (I created a proxy service to capture the exact SOAP that Axis is sending). Does someone have experience with this? Can they're share a little code example to get me going? Have you had a look at the ligging module sample. That shows you how you could capture the SOAP messages, incomming and out going. You may improve that sample to fit your needs. Samisa... Also, I then need to do the reverse. Take the response SOAP XML string and convert it into its Java object class instance. Thanks, Curtis -- Samisa Abeysinghe http://people.apache.org/~samisa/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Samisa Abeysinghe http://people.apache.org/~samisa/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Serialization of Wrapped WSDL Parameter Objects
Curtis Jensen wrote: Thanks. I'll look into client side modules. Any suggestions on where to look for a good example? Everything I've found so far was setting up for server side modules. You can see how addressing is engaged on client side. How about the return trip? When we recieve the response string, how would that get deserialized back into an object? The axis engine isn't involved at that point. You can build the full OM tree in the module if you wish so in the in path handler of the module. Samisa... Thanks, Curtis On Sun, Jul 20, 2008 at 12:43 AM, Samisa Abeysinghe [EMAIL PROTECTED] wrote: Curtis Jensen wrote: Thanks for the suggestion. I assume you meant the lOggin module sample. It was promising. However, this looks like a server side solution. I'm looking for a client side solution. It is not. It is a module, and hence can be engaged on client side as well. Maybe the logging solution can be turned into a client solution, but I'm not sure how. When our application attempts to call a web service, we would like to save the SOAP message off before it contacts the web service. We pass that SOAP message String to a third party who handles the actual communication to the web service. This is for the case when our communications is down for some reason or we are behind a restrictive firewall that is blocking http. The third party passes back the response SOAP message. This is the interface we have been given. I need to be able to generate the SOAP xml as it would have been sent to a web service. I then need to turn a response XML message back into a Java object just as Axis would. All on the client side. Again, you can use a module similar to the logging module to get this job done. Thanks, Samisa... Is this possible? Thanks again, Curtis On Fri, Jul 18, 2008 at 11:17 PM, Samisa Abeysinghe [EMAIL PROTECTED] wrote: Curtis Jensen wrote: I'm using Axis2 to generate web service clients. Everything is working fine. Now, I need to generate the SOAP XML string of what would be sent through HTTP so that I can save it for processing later. I can get a handle to the the java object Axis generated to represent the web service parameter. I can create the Call object and the OperationDescription for the call. I'm having trouble generating the SOAP XML. I've tried a couple of different things (some hackish, some less hackish). I can never quite generate the exact XML that Axis is sending (I created a proxy service to capture the exact SOAP that Axis is sending). Does someone have experience with this? Can they're share a little code example to get me going? Have you had a look at the ligging module sample. That shows you how you could capture the SOAP messages, incomming and out going. You may improve that sample to fit your needs. Samisa... Also, I then need to do the reverse. Take the response SOAP XML string and convert it into its Java object class instance. Thanks, Curtis -- Samisa Abeysinghe http://people.apache.org/~samisa/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Samisa Abeysinghe http://people.apache.org/~samisa/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Samisa Abeysinghe http://people.apache.org/~samisa/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Serialization of Wrapped WSDL Parameter Objects
Curtis Jensen wrote: I'm using Axis2 to generate web service clients. Everything is working fine. Now, I need to generate the SOAP XML string of what would be sent through HTTP so that I can save it for processing later. I can get a handle to the the java object Axis generated to represent the web service parameter. I can create the Call object and the OperationDescription for the call. I'm having trouble generating the SOAP XML. I've tried a couple of different things (some hackish, some less hackish). I can never quite generate the exact XML that Axis is sending (I created a proxy service to capture the exact SOAP that Axis is sending). Does someone have experience with this? Can they're share a little code example to get me going? Have you had a look at the ligging module sample. That shows you how you could capture the SOAP messages, incomming and out going. You may improve that sample to fit your needs. Samisa... Also, I then need to do the reverse. Take the response SOAP XML string and convert it into its Java object class instance. Thanks, Curtis -- Samisa Abeysinghe http://people.apache.org/~samisa/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Serialization of Wrapped WSDL Parameter Objects
Thanks for the suggestion. I assume you meant the lOggin module sample. It was promising. However, this looks like a server side solution. I'm looking for a client side solution. Maybe the logging solution can be turned into a client solution, but I'm not sure how. When our application attempts to call a web service, we would like to save the SOAP message off before it contacts the web service. We pass that SOAP message String to a third party who handles the actual communication to the web service. This is for the case when our communications is down for some reason or we are behind a restrictive firewall that is blocking http. The third party passes back the response SOAP message. This is the interface we have been given. I need to be able to generate the SOAP xml as it would have been sent to a web service. I then need to turn a response XML message back into a Java object just as Axis would. All on the client side. Is this possible? Thanks again, Curtis On Fri, Jul 18, 2008 at 11:17 PM, Samisa Abeysinghe [EMAIL PROTECTED] wrote: Curtis Jensen wrote: I'm using Axis2 to generate web service clients. Everything is working fine. Now, I need to generate the SOAP XML string of what would be sent through HTTP so that I can save it for processing later. I can get a handle to the the java object Axis generated to represent the web service parameter. I can create the Call object and the OperationDescription for the call. I'm having trouble generating the SOAP XML. I've tried a couple of different things (some hackish, some less hackish). I can never quite generate the exact XML that Axis is sending (I created a proxy service to capture the exact SOAP that Axis is sending). Does someone have experience with this? Can they're share a little code example to get me going? Have you had a look at the ligging module sample. That shows you how you could capture the SOAP messages, incomming and out going. You may improve that sample to fit your needs. Samisa... Also, I then need to do the reverse. Take the response SOAP XML string and convert it into its Java object class instance. Thanks, Curtis -- Samisa Abeysinghe http://people.apache.org/~samisa/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Serialization of Wrapped WSDL Parameter Objects
I'm using Axis2 to generate web service clients. Everything is working fine. Now, I need to generate the SOAP XML string of what would be sent through HTTP so that I can save it for processing later. I can get a handle to the the java object Axis generated to represent the web service parameter. I can create the Call object and the OperationDescription for the call. I'm having trouble generating the SOAP XML. I've tried a couple of different things (some hackish, some less hackish). I can never quite generate the exact XML that Axis is sending (I created a proxy service to capture the exact SOAP that Axis is sending). Does someone have experience with this? Can they're share a little code example to get me going? Also, I then need to do the reverse. Take the response SOAP XML string and convert it into its Java object class instance. Thanks, Curtis
