[JBossWS-Metro] - jax-ws-catalog.xml fails on Linux
by bmsantos
Hi all!
We've created an end-point under MS windows. When deploying it on Linux we get the following error:
anonymous wrote :
| Caused by: javax.xml.ws.WebServiceException: Failed to access the WSDL at: file:/C:/path/to/client//META-INF/wsdl/Webservice.wsdl. It failed with:
| /C:/path/to/client//META-INF/wsdl/Webservice.wsdl.
|
The same error appear on MS Windows platform but the addition of the jax-ws-catalog.xml was enough to fix it and everything works just fine on this platform.
Here is the META-INF/jax-ws-catalog.xml data:
|
| <catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog" prefer="system">
| <system systemId="file:/C:/path/to/client//META-INF/wsdl/Webservice.wsdl" uri="wsdl/Webservice.wsdl"/>
| </catalog>
|
|
We are running JBoss 4.2.3 GA with METRO 3.1.1 GA WS stack.
Is there any work around for this? Am I missing anything?
Thanks,
Bruno
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247114#4247114
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247114
14 years, 11 months
[JBossWS-Metro] - Preventing STDERR in log for Metro 2.0 jars in webservice cl
by akpandey
I am running webservice client which runs on Jboss 4.2.2.GA. The client is written using basic JAXWS api( the source is not generated using wsimport or any other utility).
For implementing webservice timeout I had to use :
requestContext.put( "com.sun.xml.ws.connect.timeout", timeout ).
It did not worked untill I added webservices-rt.jar from metro 2.0. (The jars from metro 1.5 were also working fine , but they were throwing broken pipe exception , however the results from webservices were coming fine.)
When I run the webservice client from eclipse as standalone, outside Jboss it prints:
Jul 22, 2009 12:13:05 PM [com.sun.xml.ws.assembler.MetroConfigLoader]
INFO: Default metro-default.xml configuration file located at: 'jar/webservices-rt-1.0.jar!/META-INF/metro-default.xml'
However when i run the webservice client inside Jboss container it prints in log:
ERROR [STDERR] Jul 20, 2009 5:33:08 PM
[com.sun.xml.ws.assembler.MetroConfigLoader]
INFO: Default metro-default.xml configuration file located at: ...................
The webservice is hosted on mule and is a CXF webservice
How to prevent the jBOSS from printing the info as STDERR, the webservice runs fine and gets all result there is no error
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4245372#4245372
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4245372
14 years, 11 months
[JBossWS-Metro] - Unsupported Content-Type: application/soap+xml Supported one
by mtirumalreddy
Hi,
Iam using JBoss AS 4.2.3 GA and JBossWS-Metro 3.1.1GA. I successfully generated service artifacts using wsconsume task (top-down approach) and provided implementation.
When i deploy the service, it publishes successfully. But when iam trying to access the service from client code, it is giving the following error and successfully executing the methods.
| 20:12:44,361 ERROR [HttpAdapter] Unsupported Content-Type: application/soap+xml Supported ones are: [text/xml]
| com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: application/soap+xml Supported ones are: [text/xml]
| at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:291)
| at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:128)
| at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:287)
| at com.sun.xml.ws.transport.http.HttpAdapter.decodePacket(HttpAdapter.java:276)
| at com.sun.xml.ws.transport.http.HttpAdapter.access$500(HttpAdapter.java:93)
| at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:432)
| at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
| at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135)
| at org.jboss.wsf.stack.metro.RequestHandlerImpl.doPost(RequestHandlerImpl.java:225)
| at org.jboss.wsf.stack.metro.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:82)
| at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
| at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
| at java.lang.Thread.run(Thread.java:619)
|
Please provide me some inputs regarding, where we are dealing with Content-Types? I think iam not handling any thing related to content types specifically.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4245030#4245030
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4245030
14 years, 11 months