I have a java web application using axis2 stub to call a .net webservice that receieves a string parameter. When I run the web application using tomcat server, it works fine.
But when I use Oracle weblogic server I get the following error :
org.apache.axis2.AxisFault:
First Element must contain the local name, Envelope , but found html
What could be the cause to get this error? Please help me. I really need to fix this but I can't.
Follow the steps # http://axis.apache.org/axis2/java/core/docs/app_server.html for deploying axis2 onto weblogic
Related
I developed a very simple web service using eclipse for edit the code and tomcat 8.5 for deploy the web service. The Name of maven project is PruebaMaven and I can deploy that with success getting the classic hello world.
My problem is that when I want to access an a method associate to localhost:8080/PruebaMaven/Services/Login/Validate, the tomcat response is HTTP 404 - Not found
The method that I want to access is a POST type, so I'm expecting that the response of the tomcat server be a HTTP 405.
I dont know if my thinking is correct or im wrong and the response of tomcat is apropiate. In the case that my thinking is correct, somebody know where is my issue?
I have a web service, where I am required to make a contract change. The contract change is the easier part, and I was able to make the changes to service and deploy it on the WAS 8.5 application server.
When I triggered a sample request from SOAPUI to validate my changes, I saw that my request from SOAPUI could not be successfully parsed and that is when I noticed that *_Deser.class, *_ser.class and *_helper.class for my services objects are not created after the change. Due to this, the SOAPUI request could not be processed by the SAXParser.
Here is the technology stack that I am using:
Rational Application Developer : 8.5.5
Websphere Application Server: 8.5
Java: 1.6
Webservice Runtime: IBM Websphere JAX-RPC
Note: I have to stick to this runtime :(
Any idea, why these classes/java files to not be generated?
Thanks,
RS
Found the reason behind the issue after lot of research on internet :) . https://www.ibm.com/support/knowledgecenter/en/SS8PJ7_9.1.1/com.ibm.webservice.doc/topics/core/cruntimes.html
I'm trying to upgrade a legacy webservice from Axis1 to JaxWS. I've been trying out various tutorials to see if I can add a JaxWS Webservice to the existing WebSphere server we use. I'd like to use the WebService Wizard since that seems like the most likely way to get everything running smoothly, however I've encountered the following problem. When I change the Web Service Runtime from AXIS to WebSphere JAX-WS I get the message
The IBM WebSphere JAX-WS Web service runtime in WebSphere Application
Server V8.5 Liberty Profile does not support the service project <
jax-ws project name >
So far google has failed to find a solution or even an explanation of this error for me. Does anyone here understand what my error is?
Thanks,
I am trying to create a sample web service by using the following link:
https://metro.java.net/guide/ch02.html#using_metro-developing_with_nb
I have followed all the steps mentioned in the above link and deployed my application successfully.
But when I run my application its showing "HTTP Status 404 - Not Found" error on the browser without showing any logs in the server console.
I am using GlassFish 4.0 and Netbeans 7.4
In the tutorial, they have asked us to use either GlassFish V2 or V3. Am I getting the above error because of using GlassFish 4.0?
Or am I missing anything here? How to get rid of 404 error?
got it!! In the Metro User Guide, Relative URL field is given as /CalculatorWSService?wsdl but it should be /CalculatorWS?wsdl. Hence, the issue is resolved :)
we have recently experienced a strange behavior when trying to use web service with MTOM. When Webservice method is annotated #MTOM, application fails to deploy with strange message:
Certificate Alias not supplied
This happens only on Weblogic that has no access to internet, when we deploy the same application to Weblogic that has internet connection, everything is OK.
We managed to find a note in a forum, saying that this error happens when Weblogic is trying to unsuccessfully access remote resource (like xsd). This might be true because mtom.xml file (policy in weblogic) references remote xsd: http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization/optimizedmimeserialization-policy.xsd
The webservices are created using standard J2EE 6 annotations (#WebService).
Has anyone experience similiar problem? We would appreciate any help.
MF & VH