[JBossWS] - New to JBoss and JBoss WS
by Yueh2k6
Hi,
I'm new to JBoss. I have recently generated WebService Java Inteface proxies using Axis 1.4. I was able to code a Java client (JSP) on top of it and run it on Tomcat 5.0 smoothly, simply by placing the appropriate axis libraries under \lib
I assumed a similiar process would apply to JBoss4.0 but I encountered some challenges. It seems that JBoss 4.0 has its own version of Axis library (axis-ws4ee.jar) under \client, and this JAR doesnt seem to support the interfaces generated by Axis 1.4 .
Question is : Does Jboss4.0 support Axis? if so, what version ?
I couuldnt work around the issue, so I decided to download JBoss WS 1.0.3 GA and hope to use it to generate the Java intefaces using it. but I dont know if there is a similar (WSDL to Java) tool I could use. i'm sure there is, just need to figure out how.
could someone answer my questions ? Thanks for any help !
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992876#3992876
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992876
17 years, 9 months
[JBossWS] - Issue with .NET ws clients
by palin
We have some .NET ws clients using our ws endpoint implemented on jbossws 1.0.3.SP1 (patched with http://jira.jboss.com/jira/browse/JBWS-1178). They sometimes (not always?!) get an error while calling us: Exception: System.InvalidOperationException
| Message: Client found response content type of '', but expected 'text/xml"
At the same time, on the server side, we get the following exception:
2006-12-09 19:49:20,898 ERROR [org.jboss.ws.server.StandardEndpointServlet] Error processing web service request
| java.lang.IllegalStateException: Cannot create a session after the response has been committed
| at org.apache.catalina.connector.Request.doGetSession(Request.java:2214)
| at org.apache.catalina.connector.Request.getSession(Request.java:2024)
| at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:831)
| at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:842)
| at org.jboss.ws.server.ServletEndpointContextImpl.getHttpSession(ServletEndpointContextImpl.java:57)
| at org.jboss.ws.server.ServiceEndpointManager.processSOAPRequest(ServiceEndpointManager.java:375)
| at org.jboss.ws.server.StandardEndpointServlet.doPost(StandardEndpointServlet.java:115)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
| at org.jboss.ws.server.StandardEndpointServlet.service(StandardEndpointServlet.java:76)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
| at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
| at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Thread.java:595)
|
Did anybody ever had the same problem? Or at least know why jbossws could try to open a session after the response has been commited?
Thank you
Alessio Soldano
http://www.javalinux.it/blogs
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992825#3992825
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992825
17 years, 9 months