[
https://issues.apache.org/jira/browse/TUSCANY-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528704
]
Simon Nash commented on TUSCANY-1755:
-------------------------------------
The r577089 change looks good, but I'm not convinced about the r577099 change.
Setting the service path to "/" in axis2.xml together with a context root of
"/" will cause Axis2 to compute a configuration service context path of "//".
See the algorithm in ConfigurationContext.internalGetServiceContextPath().
When Utils.parseRequestURLForServiceAndOperation() is called with this service
path, it will find a spurious match with the "//" in the URI scheme. The
results will be to parse the service URL
http://localhost:8085/HelloWorldServiceComponent/HelloWorldService
into a service name of
ocalhost:8085
and an operation name of
HelloWorldService
This removes the log message, but I'm not sure what other effects it will have.
These values are not correct and the effect on Axis2 of returning them from
the Utils.parseRequestURLForServiceAndOperation() method should be investigated
further.
> Spurious console output for Web Services tests and samples
> ----------------------------------------------------------
>
> Key: TUSCANY-1755
> URL: https://issues.apache.org/jira/browse/TUSCANY-1755
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Axis Binding Extension
> Affects Versions: Java-SCA-1.0
> Environment: Windows XP
> Reporter: Simon Nash
> Assignee: Raymond Feng
> Fix For: Java-SCA-1.0
>
>
> The Web Services samples and itests now produce additional console output
> that I have not seen before. The tests still work but there are two major
> usability issues.
> 1. Every invocation across the Web Service binding produces the following
> message:. For an application that does a large number of invocations, it is
> unacceptable for these messages to be displayed.
> 18-Sep-2007 21:52:33 org.apache.axis2.util.Utils
> parseRequestURLForServiceAndOperation
> INFO: Unable to parse request URL
> [http://localhost:8085/HelloWorldServiceComponent/HelloWorldService][/services]
> For an example of this, run samples/helloworld-ws-service
> 2. Business exceptions thrown and caught by the application (not an error)
> produce the following stack trace. This is highly confusing as it appears
> that there has been an error in Tuscany, whereas in fact everything is
> working correctly.
> 18-Sep-2007 21:54:08
> org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceInOutSyncMessageReceiver
> invokeBusinessLogic
> SEVERE: null
> org.apache.tuscany.sca.interfacedef.util.FaultException: <message-text>
> at
> org.apache.tuscany.sca.databinding.axiom.AxiomExceptionHandler.createException(AxiomExceptionHandler.java:37)
> at
> org.apache.tuscany.sca.core.databinding.transformers.Exception2ExceptionTransformer.transform(Exception2ExceptionTransformer.java:107)
> at
> org.apache.tuscany.sca.core.databinding.transformers.Exception2ExceptionTransformer.transform(Exception2ExceptionTransformer.java:38)
> at
> org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:73)
> at
> org.apache.tuscany.sca.core.databinding.wire.DataTransformationInteceptor.transformException(DataTransformationInteceptor.java:254)
> at
> org.apache.tuscany.sca.core.databinding.wire.DataTransformationInteceptor.invoke(DataTransformationInteceptor.java:147)
> at
> org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke(RuntimeWireInvoker.java:118)
> at
> org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke(RuntimeWireInvoker.java:89)
> at
> org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke(RuntimeWireInvoker.java:83)
> at
> org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.invoke(RuntimeWireImpl.java:127)
> at
> org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.invokeTarget(Axis2ServiceProvider.java:449)
> at
> org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceInOutSyncMessageReceiver.invokeBusinessLogic(Axis2ServiceInOutSyncMessageReceiver.java:58)
> at
> org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusinessLogic(AbstractInOutSyncMessageReceiver.java:42)
> at
> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:96)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145)
> at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
> at
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:120)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:228)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:216)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
> at
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:634)
> at
> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:352)
> at org.apache.tuscany.sca.core.work.Jsr237Work.run(Jsr237Work.java:61)
> at
> org.apache.tuscany.sca.core.work.ThreadPoolWorkManager$DecoratingWork.run(ThreadPoolWorkManager.java:205)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> at java.lang.Thread.run(Thread.java:595)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
