[
http://issues.apache.org/jira/browse/AXIS2-761?page=comments#action_12414609 ]
Chuck Williams commented on AXIS2-761:
--------------------------------------
Deepal and Oleg,
The new jar works great -- no issues with it.
However, I have run into a problem merging this patch with the latest svn head.
ServiceGroupContextTest now fails. All other tests succeed.
The problem is independent of which jar is used, so that is not the issue. The
issue may be due to a recent independent change by Deepal that introduced merge
conficts. I resolved these but perhaps not correctly. The change is:
r411162 | deepal | 2006-06-02 04:02:19 -1000 (Fri, 02 Jun 2006) | 6 lines
- fix security test failures
- make to change the axis2 configuration path
- no hard code path checking for services
- you can change the context path by just adding parameter in axis2.xml
- if you rename the war it will correctly generate wsdl
(there were few bugs)
ServiceGroupContextTest fails to recognize the second request sent as being the
same service group as the first, and therefore gets this assertion error:
Testcase: testEchoXMLSync(org.apache.axis2.engine.ServiceGroupContextTest):
FAILED
Number of requests should be 2 expected:<2> but was:<1>
junit.framework.AssertionFailedError: Number of requests should be 2
expected:<2> but was:<1>
at
org.apache.axis2.engine.ServiceGroupContextTest.testEchoXMLSync(ServiceGroupContextTest.java:108)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
I'm attaching a new version of the patch called
ConfigurableSimpleHTTPServer.complete.patch which applies against today's head
with my merges for Deepal's upates. This exhibits the test failure. The patch
applies against the top-level of the repository and makes all necessary
changes. It assumes the jar is available to maven as jakarta-httpcore with
version 4.0-20060602.
Deepal, I'm hoping you will know what the issue is? If not and I need to debug
it, I'll need to set up a special debugging environment. I don't understand
how and where the ServiceGroupContext is set for the incoming request and
couldn't find this easily with just source analysis tools. A hint about how
this works, and how a prior ServiceGroupContext is supposed to get discovered
even when there is a unique ServiceGroupContextId, would be helpful.
The failing test is in the integration module and for this one module I cannot
get mevenide to attach the debugger to a test run properly. The issue appears
to be that integration has a long start-up time and mevenide tries to attach
too soon. The purported fix, maven.netbeans.debug.delay. does not successfully
introduce a delay into the attach.
> SimpleHttpServer based on Jakarta HttpComponents HttpCore
> ---------------------------------------------------------
>
> Key: AXIS2-761
> URL: http://issues.apache.org/jira/browse/AXIS2-761
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Components: transports
> Versions: 1.0
> Reporter: Oleg Kalnichevski
> Attachments: ConfigurableSimpleHTTPServer.consolidated.patch,
> ConfigurableSimpleHTTPServer.patch, jakarta-httpcore-4.0-20060602.jar,
> simplehttpserver.patch
>
> The following patch replaces the SimpleHttpServer implementation based on the
> testing framework of Commons HttpClient 3.x with a one based on Jakarta
> HttpComponents HttpCore. Compiled against Axis2 trunk and HttpCore trunk
> * Removes all references to Commons HttpClient classes
> * Enables streaming of schema definitions and similar content
> * Improves content buffering of SOAP response
> * Improves handling of fault conditions and exception handling
> * Fixes a number of NPEs in AxisEngine
> * Improves performance and reliability of the HTTP transport
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
