[ http://issues.apache.org/jira/browse/TUSCANY-61?page=all ]

Jean-Sebastien Delfino updated TUSCANY-61:
------------------------------------------

    Fix Version: Java-Mx
                     (was: Java-M1)
        Version: Java-Mx
                     (was: Java-M1)

Ok, looks like this is really flaky at this point. I recommend that we look at 
this again after M1. After all it's easy to publish your own WSDL, you just 
need to put it under the webapp context to allow people to download it. If we 
had support for entry points without a pre-authored or pre-generated WSDL then 
it would be important to have this feature, but we don't support this in M1 so 
we always have the WSDL file handy, and again it's easy to publish it in your 
web app.

> ?WSDL on WS binding entryPoints fails
> -------------------------------------
>
>          Key: TUSCANY-61
>          URL: http://issues.apache.org/jira/browse/TUSCANY-61
>      Project: Tuscany
>         Type: Bug

>   Components: Java SCA Axis Binding
>     Versions: Java-Mx
>     Reporter: ant elder
>     Assignee: Raymond Feng
>      Fix For: Java-Mx

>
> Appending ?WSDL to the url of a entryPoint with a WS binding should return 
> the WSDL, but it fails, first as its missing the xmlschema jar then once 
> thats available with the following exception. Looks like its trying to gen a 
> new wsdl but it should be able to use the definition from the model.
> org.apache.axis2.AxisFault: no scheam found for the service; nested exception 
> is: 
>       java.lang.Exception: no scheam found for the service
>       at 
> org.apache.axis2.description.AxisService.printUsingWOM(AxisService.java:373)
>       at 
> org.apache.axis2.description.AxisService.printWSDL(AxisService.java:322)
>       at 
> org.apache.axis2.transport.http.ListingAgent.listService(ListingAgent.java:469)
>       at 
> org.apache.axis2.transport.http.ListingAgent.handle(ListingAgent.java:393)
>       at 
> org.apache.tuscany.binding.axis2.handler.WebServiceEntryPointServlet.doGet(WebServiceEntryPointServlet.java:140)
>       at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
>       at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>       at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
>       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.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:868)
>       at 
> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:663)
>       at 
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
>       at 
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
>       at 
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
>       at java.lang.Thread.run(Thread.java:595)
> Caused by: java.lang.Exception: no scheam found for the service
>       at 
> org.apache.axis2.description.AxisService2WOM.generateWOM(AxisService2WOM.java:86)
>       at 
> org.apache.axis2.description.AxisService.printUsingWOM(AxisService.java:362)
>       ... 20 more

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to