Ask a Question related to Coldfusion - Advanced Techniques, Design and Development.
-
liuzh #1
Web services not working after upgrading from mx 6.1 tomx 7
Hihi,
We have some Web services codes written in Java, running in a Web application
together ColdFusion and JRun4. Previously, we have deployed ColdFusion MX 6.1
as an enterprise application in JRun4 and the Web services code worked fine.
After upgrading to MX 7, the Web services code do not work at all.
We use server-config.wsdd to deploy the Web services, using
provider="java:RPC". The wsdl file is accessed in a manner similar to
[url]http://localhost/services/MyService?wsdl[/url] . In MX 7, a 404 error occurs.
We compared the MX 7 and 6.1 configuration and found some differences. Most
notably is that the servlet definition and mapping for AxisServlet are missing
in web.xml in MX 7. We added them into the web.xml in MX 7.
<servlet id="macromedia_servlet_8">
<servlet-name>AxisServlet</servlet-name>
<display-name>Apache-Axis Servlet</display-name>
<servlet-class>coldfusion.bootstrap.BootstrapServlet</servlet-class>
<init-param id="InitParam_1034013110658x">
<param-name>servlet.class</param-name>
<param-value>org.apache.axis.transport.http.AxisServlet</param-value>
</init-param>
</servlet>
<servlet-mapping id="macromedia_mapping_6">
<servlet-name>AxisServlet</servlet-name>
<url-pattern>servlet/AxisServlet</url-pattern>
</servlet-mapping>
<servlet-mapping id="macromedia_mapping_7">
<servlet-name>AxisServlet</servlet-name>
<url-pattern>*.jws</url-pattern>
</servlet-mapping>
<servlet-mapping id="macromedia_mapping_8">
<servlet-name>AxisServlet</servlet-name>
<url-pattern>/services/*</url-pattern>
</servlet-mapping>
But it still didn't work. the same 404 error occurs. We tested with a simple
..jws, and it works fine. This seems to tell us that only the last mapping (for
/services/*) is not working properly. When accessing
[url]http://localhost/servlet/AxisServlet[/url] , we could even see AxisServlet responding
with:
And now... Some Services
MyService (wsdl)
....
It seems that AxisServlet has found the Java class for the Web Service, since
it has correctly printed the list of all methods exposed, which was not
specified in server-config.wsdd (we only specify allowedMethods"*" ).
In the JRun4 installation from MX 7, there is a sample application
ws-ear/ws-war, we copied ws-war to our own ear and it didn't work either.
However, ws-war did work in ws-ear/ws-war, but that was without ColdFusion MX 7
ear codes..
Does anyone encounter similar problems before?
Thanks,
Zehua
liuzh Guest
-
web services - not working
hi all, i am using a web service to retrieve city names by country but it is not working it throws an error - Error opening URL... -
Web Services not working on new MX7 install
We are busy rolling out a new application for a customer. A couple of other apps use webservices in this app. It was all working 100% on MX6.1,... -
Terminal Services still not working on Win2003
Hello, I have set up a Terminal Server role in Windows 2003 Standard and registered the 5 user CAL. However, when I connect from a different... -
VBA web services call not working in office XP
Hi I am calling a web service call from VBA and it is working good with the machines having office 2003. I tried to run the same excel template... -
DNS not working after upgrading to OS X 10.2 (Wallstreet PB)
DNS does not work, but TCP/IP is functioning - I can do anything by IP Address, but nothing by domain name. I ran 10.1.5 with no problems.... -
Tom Jordahl #2
Re: Web services not working after upgrading from mx 6.1 to mx 7
Note that the Axis engine in ColdFusion is Axis 1.2 RC2 and the Axis engine
in JRun is Axis 1.1.
They may not play well together in the same web application.
--
Tom Jordahl
Macromedia Server Development
Tom Jordahl Guest



Reply With Quote

