Error Fetching http headers
I have some web services running on axis 1.4 and a client who is trying to access it via php soap. He is running into problems with an error that says "Caught exception: Error Fetching http headers. Exiting." I am not sure what's causing this problem. I have tried using his code on my local laptop and have been unable to replicate the error. Does anybody know what causes this sort of error and what potential solutions to this problem are? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
axis background thread?
I am trying to implement a web service which does a large number of things. For instance, it can make on the order of 40,000 sql queries depending on what needs to be done. Because this takes such a long time to do, and because the user is only needed to give the information necessary to start the thread, I'd prefer to just start a thread, send a response to the user that this thread has been initiated, and have this thread run long after the user has gone on their merry way. I guess my question is, is it possible to implement a background process like this where the process continues long after the response has been sent back to the user, or can this only be implemented as a process which does not give a response back to the user? I've been looking for information on this, but really haven't found much. Perhaps because I'm not using the right terminology. I'm quite new to axis and web services. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: target namespace
That makes sense. I deployed this web service using jws deployment. Under that deployment method where exactly does the web service get the namespace from? Also, is it possible to alter the namespace so it is something different? Anne Thomas Manes wrote: The WSDL targetNamespace is not the same as the URL of your service. A namespace is just a name -- it's not a path to file. If you host the same service in two different domains, the WSDL namespace should remain the same. Anne On 6/6/06, tom mccarthy <[EMAIL PROTECTED]> wrote: I am using axis 1.4. The company I work for has deployed this service on one of our servers. What we want to do is let this code be available on our domain and on another domain as well. The problem that we are running into is that when we point another domain to the same location, the wsdl still shows the primary domain of the server in the target namespace of the wsdl. What would be the best way to publish the same web service under two separate urls without having this occur? - 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]
target namespace
I am using axis 1.4. The company I work for has deployed this service on one of our servers. What we want to do is let this code be available on our domain and on another domain as well. The problem that we are running into is that when we point another domain to the same location, the wsdl still shows the primary domain of the server in the target namespace of the wsdl. What would be the best way to publish the same web service under two separate urls without having this occur? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
No such operation 'getCallDetailRecords'
I am trying to access the method "getCallDetailRecords at the following endpoint: http://production.services.bevocal.com/CDRAccessService_v2/services/CDRAccessService_v2 However, for whatever reason I keep getting the error: No such operation 'getCallDetailRecords' despite the fact that such a method does, I fully believe, exist at that location. Can anyone shed any light on possible reasons this might occur? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: javax.xml.rpc.service
nevermind. I hadn't realized I needed to add the axis jar files to my servlet lib directory. tom mccarthy wrote: I am writing an applet which accesses a web client to send information to a web service. However, I am getting the following exception: java.lang.NoClassDefFoundError: javax/xml/rpc/Service I believe I have all of the axis jars in my classpath and the application compiles correctly, so this problem troubles me. What could cause this problem? Are there any potential solutions you can think of? Thanks. - 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]
javax.xml.rpc.service
I am writing an applet which accesses a web client to send information to a web service. However, I am getting the following exception: java.lang.NoClassDefFoundError: javax/xml/rpc/Service I believe I have all of the axis jars in my classpath and the application compiles correctly, so this problem troubles me. What could cause this problem? Are there any potential solutions you can think of? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Server did not recognize the value of HTTP Header SOAPAction
I am trying to write a client for this wsdl: http://jmhotlinewsstg.jmfamily.com/JMHotlinews.asmx?WSDL However, when I write a simple axis client that goes something like this: String method = "SMSCheckIn"; Service service = new Service(); Call call = (Call) service.createCall(); call.setTargetEndpointAddress(new java.net.URL(endpoint)); call.setOperationName(method); call.addParameter("SourceAddr", XMLType.XSD_STRING, ParameterMode.IN); call.addParameter("DestinationAddr", XMLType.XSD_STRING, ParameterMode.IN); call.addParameter("CarrierName", XMLType.XSD_STRING, ParameterMode.IN); call.addParameter("CarrierID", XMLType.XSD_STRING, ParameterMode.IN); call.addParameter("IsNumberPorted", XMLType.XSD_STRING, ParameterMode.IN); call.addParameter("LocationRegistered", XMLType.XSD_STRING, ParameterMode.IN); call.addParameter("MessageText", XMLType.XSD_STRING, ParameterMode.IN); call.addParameter("DeliveryStatusDescription", XMLType.XSD_STRING, ParameterMode.IN); call.addParameter("DeliveryStatusCode", XMLType.XSD_STRING, ParameterMode.IN); call.setReturnType(XMLType.XSD_STRING); Object parameters[] = new Object[] {null, null, null, null, null, null, message, null, null}; return (String)call.invoke(parameters); I get a long error along the lines of: Exception in thread "main" AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client faultSubcode: faultString: Server did not recognize the value of HTTP Header SOAPAction: . I am not sure what this means or how to correct it. Or, indeed, if it is correctable. I have tried running WSDL2Java in order to help generate a client with little success. In that instance I was told that The prefix "wsdl" for element "wsdl:definitions" is not bound. I am assuming that the web service works correctly. However, I am having issues creating a java client for it. If anybody has any input concerning these problems I'd love to hear it.
axis class path issues
I am having some issues associated with the mysql drivers on my server. I am able to compile the webservices I am trying to deploy alright and run them as java classes, but when I move them over to axis I get a no suitable driver error. The mysql drivers are currently part of CLASSPATH, which apparently axis doesn't like. Does anybody have any idea how to make these drivers available to the code within axis? I am right now just copying the java class over to a jws in the axis folder.
vexing path issues
I am a very new user to axis. My installation of axis seems to have gone well. Am able to deploy web services and see that they are there. Things seem to compile well. I get no huge errors associated with mandatory things on the happyaxis page. My issue is related to the fact that whenever I try to call a web service from the command line I get: Exception in thread "main" java.lang.NoClassDefFoundError: samples/userguide/example2/CalcClient What I am specifically trying to run is example2 from the axis user's guide. I can deploy it (copy it to the axis directory), and I can see it is there (at localhost:8080/axis/Calculator.jws) and see the WSDL file associated with it. Sadly, when I type in java samples.userguide.example2.CalcClient -p8080 add 2 5 I get the error I mentioned earlier. I can also deploy as per example3 from the users guide using java -cp $AXISCLASSPATH org.apache.axis.client.AdminClient deploy.wsdd however, when I try to run it using java samples.userguide.example3.Client -lhttp://localhost:8080/axis/services/MyService "test me" I get the error I mentioned above. Also interesting is that I have to use -cp $AXISCLASSPATH while I have added $AXISCLASSPATH to my path. Because I am of the belief that this is all associated with a classpath error somehow I will show you what I have done with my path for axis: export AXIS_HOME="/usr/share/tomcat/webapps/axis" export AXIS_LIB="$AXIS_HOME/WEB-INF/lib" export AXISCLASSPATH="$AXIS_LIB/axis.jar:$AXIS_LIB/commons-discovery-0.2.jar:$AXIS_LIB/commons-logging-1.0.4.jar:$AXIS_LIB/jaxrpc.jar:$AXIS_LIB/saaj.jar:$AXIS_LIB/log4j-1.2.8.jar" export PATH="$PATH:$AXISCLASSPATH" These things, so far as I know, point to the right places. I would appreciate any help that can be given me in sorting out these issues.