Soap/SoapStub not generated
I am using Axis 1.2RC3(thats what is in production and the powers that be don't want to change it without a compelling reason) and the ant task axis-wsdl2java to generate a web service client. I have used this combination in the past to generate clients with no problems. Now I am running into a problem where all the classes are generated except the Soap/SoapStub classes. We recently changed the proxy configuration here and I am wondering if that could have any impact on the generation? (I added a setproxy task before the axis task to get it to run). Is there any reason this might be occurring? What can I do to fix it? Michael - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Soap/SoapStub not generated
looks like this was a classpath problem. I was running the ant script in eclipse, and moving it to command line seems to have fixed the problem. Michael On 2/15/07, Michael Rasmussen [EMAIL PROTECTED] wrote: I am using Axis 1.2RC3(thats what is in production and the powers that be don't want to change it without a compelling reason) and the ant task axis-wsdl2java to generate a web service client. I have used this combination in the past to generate clients with no problems. Now I am running into a problem where all the classes are generated except the Soap/SoapStub classes. We recently changed the proxy configuration here and I am wondering if that could have any impact on the generation? (I added a setproxy task before the axis task to get it to run). Is there any reason this might be occurring? What can I do to fix it? Michael - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Certificate Expired
We have several servers in our production environment running the same code. Each of these servers has a cacerts file with an identical checksum. Despite this some of our servers get an axis fault:certificate expired and some of them do not. Does anyone know if there are reasons other than an actual expired cert that would cause this? Thanks, Michael - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Runtime?
What are the runtime requirements for Zxis 2 as far as the JDK Version? Will this still work on JDK 1.3? I could not find this information on the site after much searching. Still I could have just overlooked it. Michael
Handlers and Dynamic Header info
Hi, I have just written a handler to insert an element into my header. This works fine. Now I need to be able to insert a value into the header on a per call basis ( I need a different value determined by the caller). I should note here that I don't know why this isn't a parameter in the method, but then again I didn't write the service, so I don't have any control over it. Basically what I need is a way for the caller to either insert into the MessageContext or something similar. As expected whatever solution I use has to be threadsafe. One thing I considered was to create a hash map that is the value with the thread id as the hash. Does anyone know how to accomplish what I am talking about? Thanks in advance,Michael Rasmussen
Re: Handlers and Dynamic Header info
Hmm...maybe caller is not the best term. I'm not talking about the caller of the service and reading it on the server side. I am talking about the caller of the SOAP method (the one generated by axis) passing the value to the handler (Still on the client side) so that it can be inserted into the request header. I could do all this by modifying the wsdl2java generated code, but that would be a suboptimal solution in my mind. MichaelOn 3/22/06, Soactive Inc [EMAIL PROTECTED] wrote: Have the caller enter this data into the SOAP header when they make the service call and then read it from the message header in your server-side handler to use/process it. By design, standard (Axis/RPC) handlers are thread-safe. On 3/22/06, Michael Rasmussen [EMAIL PROTECTED] wrote: Hi, I have just written a handler to insert an element into my header. This works fine. Now I need to be able to insert a value into the header on a per call basis ( I need a different value determined by the caller). I should note here that I don't know why this isn't a parameter in the method, but then again I didn't write the service, so I don't have any control over it. Basically what I need is a way for the caller to either insert into the MessageContext or something similar. As expected whatever solution I use has to be threadsafe. One thing I considered was to create a hash map that is the value with the thread id as the hash. Does anyone know how to accomplish what I am talking about? Thanks in advance,Michael Rasmussen
Re: Handlers and Dynamic Header info
Thanks for the responses, I found a solution herehttp://ws.apache.org/axis/faq.html#faq18I got rid of the handler and just cast the Soap object to a Stub where I had access to the header. MichaelOn 3/22/06, Michael Rasmussen [EMAIL PROTECTED] wrote: Hmm...maybe caller is not the best term. I'm not talking about the caller of the service and reading it on the server side. I am talking about the caller of the SOAP method (the one generated by axis) passing the value to the handler (Still on the client side) so that it can be inserted into the request header. I could do all this by modifying the wsdl2java generated code, but that would be a suboptimal solution in my mind. MichaelOn 3/22/06, Soactive Inc [EMAIL PROTECTED] wrote: Have the caller enter this data into the SOAP header when they make the service call and then read it from the message header in your server-side handler to use/process it. By design, standard (Axis/RPC) handlers are thread-safe. On 3/22/06, Michael Rasmussen [EMAIL PROTECTED] wrote: Hi, I have just written a handler to insert an element into my header. This works fine. Now I need to be able to insert a value into the header on a per call basis ( I need a different value determined by the caller). I should note here that I don't know why this isn't a parameter in the method, but then again I didn't write the service, so I don't have any control over it. Basically what I need is a way for the caller to either insert into the MessageContext or something similar. As expected whatever solution I use has to be threadsafe. One thing I considered was to create a hash map that is the value with the thread id as the hash. Does anyone know how to accomplish what I am talking about? Thanks in advance,Michael Rasmussen
