cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Liu, Jervis" <j...@iona.com>
Subject RE: cxf Cruisecontrol Build Result: cxf Build Failed
Date Wed, 20 Dec 2006 10:14:36 GMT
Hi, I just tried failed test on the cruise control machine pdceltix, I found this SpringServletTest test failed only when run the whole test suite together (from rt/frontend/jaxws), it passed if run this test alone. Haven't figured out what's wrong. I commented out this test for the time being.

Cheers,
Jervis  

> -----Original Message-----
> From: Dan Diephouse [mailto:dan@envoisolutions.com]
> Sent: Wednesday, December 20, 2006 5:05 PM
> To: cxf-dev@incubator.apache.org
> Subject: Fwd: cxf Cruisecontrol Build Result: cxf Build Failed
> 
> 
> Hi All - There seems to be some issue with either a) running my latest
> commit on Linux or b) CruiseControl. I can't reproduce the 
> error and on IRC
> Jervis said the tests passed on his Windows box as well, so I 
> suspect its CC
> and not my commit... I am about to disconnect though for the 
> evening, so if
> the issue is not CC related, could someone please disable the 
> test and i
> will look at it first thing in the morning. Thanks,
> 
> - Dan
> 
> ---------- Forwarded message ----------
> From: cxf Build Machine <eng-celtix-dev@iona.com>
> Date: Dec 20, 2006 12:16 AM
> Subject: cxf Cruisecontrol Build Result:  cxf Build Failed
> To: dandiep@apache.org, eng-celtix-dev@iona.com
> 
>  View results here ->
> http://pdceltix.boston.amer.iona.com:8080/cruisecontrol/buildr
> esults/cxf?log=log20061220030954
> 
>  BUILD FAILED  Ant Error 
> Message:/x1/iona_cruisecontrol/cxf/build.xml:48:
> Build Failed  Date of build:12/20/2006 03:09:54  Time to 
> build:7 minutes 1
> second  Last changed:12/20/2006 03:07:54  Last log entry:o Renamed
> SoapDestinationFactory to SoapTransportFactory as it now can work as a
> conduit too when creating client proxies. o Refactor Holder logic to
> interceptors. This is to help the seperation of JAX-WS logic from the
> EndpointInvocationHandler and also so we can support the XFire Aegis
> databinding Holder class (coming once I get the XFire Aegis support
> finished). I don't like the way I implemented this at all. 
> Especially since
> SoapOutInterceptor needs to look for -1 in the type index. I 
> think we should
> probably come up with a better method. o Separated JAX-WS
> EndpointInvocationHandler logic out so the Simple frontend 
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client. o 
> Add a bunch of
> toString() methods to the service model to make debugging 
> easier. o Move
> HeaderTest to jax-ws module and use local transport. Test now takes .3
> seconds instead of 8. Makes for much faster debugging. o Support
> get/setServerBean on ServerFactoryBean o Add logging to 
> PhaseInteceptorChain
> so it can be visualized. Just turn logging up to Fine and it 
> will print out
> a diagram of the phases and the interceptors in that phase. o Fix race
> condition with PhaseInterceptorChain's pause/resume. There 
> was a problem
> with WS-A/RM in that the executor was resuming the flow 
> before the current
> interceptor had returned and the pausedMessage was set. Now 
> doInterceptor
> notifies resume() once its finished pausing. resume() will 
> wait for one
> second for the chain to finish pausing. A couple thoughts 
> from things I
> noticed while going through the code: - we seem to be removing the
> ws-a/ws-rm headers from the header tree. Why?? People will 
> want to see these
> IMO and they'll be surprised that they're gone. - As noticed 
> on the mailing
> list a few days ago, I think there are issues with the
> JaxwsInterceptorRemover approach long term. I had to add the holder
> interceptors to the list so that they were removed as well. - 
> SequencetTest
> was failing sporadically depending on whether or not logging 
> was turned up
> before I fixed the race condition. This took a very long time 
> to figure
> out... Anyone have hints on how to best debug RM? I started 
> adding a server
> side only test which played messages against the server and 
> that helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)
> 
>    Errors/Warnings: (2)
> 
> Result: 1Tail of log: [surefire]
> 
> [surefire] Running org.apache.cxf.jaxws.ServiceImplTest
> [surefire] Tests run: 1, Failures: 0, Errors: 0, Time 
> elapsed: 0.044 sec
> [surefire]
> 
> [surefire] Running org.apache.cxf.jaxws.URIMappingInterceptorRPCTest
> [surefire] Tests run: 6, Failures: 0, Errors: 0, Time 
> elapsed: 0.372 sec
> [surefire]
> 
> 
> Results :
> [surefire] Tests run: 109, Failures: 0, Errors: 1
> 
> [INFO] 
> --------------------------------------------------------------
> ----------
> [ERROR] BUILD ERROR
> [INFO] 
> --------------------------------------------------------------
> ----------
> [INFO] There are test failures.
> [INFO] 
> --------------------------------------------------------------
> ----------
> [INFO] For more information, run Maven with the -e switch
> [INFO] 
> --------------------------------------------------------------
> ----------
> [INFO] Total time: 6 minutes 35 seconds
> [INFO] Finished at: Wed Dec 20 03:16:46 EST 2006
> [INFO] Final Memory: 69M/268M
> [INFO] 
> --------------------------------------------------------------
> ----------
> 
>      Unit Tests: (525)    error testInvokingSpringBeans
> org.apache.cxf.jaxws.servlet.SpringServletTest        Unit Test Error
> Details: (1)    Test: testInvokingSpringBeans  Class:
> org.apache.cxf.jaxws.servlet.SpringServletTest
>    com.meterware.httpunit.HttpNotFoundException: Error on 
> HTTP request: 404
> OK [http://localhost/services/Greeter]
> at 
> com.meterware.httpunit.WebClient.validateHeaders(WebClient.java:575)
> at com.meterware.httpunit.WebClient.updateClient(WebClient.java:464)
> at com.meterware.httpunit.WebWindow.updateWindow(WebWindow.java:139)
> at 
> com.meterware.httpunit.WebWindow.getSubframeResponse(WebWindow
> .java:130)
> 
> at com.meterware.httpunit.WebWindow.getResponse(WebWindow.java:121)
> at com.meterware.httpunit.WebClient.getResponse(WebClient.java:113)
> at 
> org.apache.cxf.jaxws.servlet.SpringServletTest.testInvokingSpr
> ingBeans(
> SpringServletTest.java:41)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess
> orImpl.java:39)
> 
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at junit.framework.TestCase.runTest(TestCase.java:154)
> at junit.framework.TestCase.runBare(TestCase.java:127)
> at junit.framework.TestResult$1.protect(TestResult.java:106)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.framework.TestResult.run(TestResult.java:109)
> at junit.framework.TestCase.run(TestCase.java:118)
> at junit.framework.TestSuite.runTest(TestSuite.java:208)
> at junit.framework.TestSuite.run(TestSuite.java:203)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess
> orImpl.java:39)
> 
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.apache.maven.surefire.battery.JUnitBattery.executeJUnit(
> JUnitBattery.java:242)
> at 
> org.apache.maven.surefire.battery.JUnitBattery.execute(JUnitBa
> ttery.java:216)
> 
> at 
> org.apache.maven.surefire.Surefire.executeBattery(Surefire.java:215)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:163)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:87)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:63)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess
> orImpl.java:39)
> 
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at 
> org.apache.maven.surefire.SurefireBooter.main(SurefireBooter.java:785)
> 
>    Modifications since last successful build:  (104)  addeddandiep
> /incubator/cxf/trunk/rt/core/src/main/java/org/apache/cxf/fron
> tend/MethodDispatcher.java12/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up before I fixed the race condition. This took a 
> very long time
> to
> figure out... Anyone have hints on how to best debug RM? I 
> started adding a
> server side only test which played messages against the 
> server and that
> helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> 
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)  modifieddandiep
> /incubator/cxf/trunk/rt/frontend/jaxws/src/test/java/org/apach
> e/cxf/jaxws/SoapFaultTest.java12/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up before I fixed the race condition. This took a 
> very long time
> to
> figure out... Anyone have hints on how to best debug RM? I 
> started adding a
> server side only test which played messages against the 
> server and that
> helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> 
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)  modifieddandiep
> /incubator/cxf/trunk/rt/frontend/jaxws/src/test/java/org/apach
> e/cxf/jaxws/URIMappingInterceptorRPCTest.java12/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up before I fixed the race condition. This took a 
> very long time
> to
> figure out... Anyone have hints on how to best debug RM? I 
> started adding a
> server side only test which played messages against the 
> server and that
> helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> 
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)  modifieddandiep
> /incubator/cxf/trunk/rt/ws/rm/src/main/java/org/apache/cxf/ws/
> rm/RMInInterceptor.java12/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up before I fixed the race condition. This took a 
> very long time
> to
> figure out... Anyone have hints on how to best debug RM? I 
> started adding a
> server side only test which played messages against the 
> server and that
> helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> 
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)  modifieddandiep
> /incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache
> /cxf/binding/soap/model/SoapHeaderInfo.java12/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up before I fixed the race condition. This took a 
> very long time
> to
> figure out... Anyone have hints on how to best debug RM? I 
> started adding a
> server side only test which played messages against the 
> server and that
> helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> 
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)  modifieddandiep
> /incubator/cxf/trunk/integration/jca/src/test/java/org/apache/
> cxf/jca/cxf/JCABusFactoryTest.java12/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up before I fixed the race condition. This took a 
> very long time
> to
> figure out... Anyone have hints on how to best debug RM? I 
> started adding a
> server side only test which played messages against the 
> server and that
> helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> 
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)  modifieddandiep
> /incubator/cxf/trunk/rt/frontend/jaxws/src/main/java/org/apach
> e/cxf/jaxws/JAXWSMethodInvoker.java12/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up before I fixed the race condition. This took a 
> very long time
> to
> figure out... Anyone have hints on how to best debug RM? I 
> started adding a
> server side only test which played messages against the 
> server and that
> helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> 
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)  modifieddandiep
> /incubator/cxf/trunk/systests/src/test/java/org/apache/cxf/sys
> test/ws/rm/JaxwsInterceptorRemover.java12/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up before I fixed the race condition. This took a 
> very long time
> to
> figure out... Anyone have hints on how to best debug RM? I 
> started adding a
> server side only test which played messages against the 
> server and that
> helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> 
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)  deleteddandiep
> /incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache
> /cxf/binding/soap/SoapDestinationFactory.java12/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up before I fixed the race condition. This took a 
> very long time
> to
> figure out... Anyone have hints on how to best debug RM? I 
> started adding a
> server side only test which played messages against the 
> server and that
> helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> 
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)  addeddandiep
> /incubator/cxf/trunk/rt/frontend/jaxws/src/test/java/org/apach
> e/cxf/jaxws/header/HeaderClientServerTest.java12/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up before I fixed the race condition. This took a 
> very long time
> to
> figure out... Anyone have hints on how to best debug RM? I 
> started adding a
> server side only test which played messages against the 
> server and that
> helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> 
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)  modifieddandiep
> /incubator/cxf/trunk/rt/frontend/jaxws/src/test/java/org/apach
> e/cxf/jaxws/support/JaxWsServiceFactoryBeanTest.java12/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up before I fixed the race condition. This took a 
> very long time
> to
> figure out... Anyone have hints on how to best debug RM? I 
> started adding a
> server side only test which played messages against the 
> server and that
> helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> 
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)  modifieddandiep
> /incubator/cxf/trunk/rt/core/src/main/java/org/apache/cxf/test
> /AbstractCXFTest.java12/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up before I fixed the race condition. This took a 
> very long time
> to
> figure out... Anyone have hints on how to best debug RM? I 
> started adding a
> server side only test which played messages against the 
> server and that
> helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> 
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)  deleteddandiep
> /incubator/cxf/trunk/rt/frontend/simple/src/main/java/org/apac
> he/cxf/service/factory/ClientFactoryBean.java12/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up before I fixed the race condition. This took a 
> very long time
> to
> figure out... Anyone have hints on how to best debug RM? I 
> started adding a
> server side only test which played messages against the 
> server and that
> helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> 
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)  addeddandiep
> /incubator/cxf/trunk/rt/frontend/jaxws/src/main/java/org/apach
> e/cxf/jaxws/interceptors/HolderOutInterceptor.java12/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up before I fixed the race condition. This took a 
> very long time
> to
> figure out... Anyone have hints on how to best debug RM? I 
> started adding a
> server side only test which played messages against the 
> server and that
> helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> 
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)  modifieddandiep
> /incubator/cxf/trunk/rt/frontend/simple/src/test/java/org/apac
> he/cxf/service/factory/ReflectionServiceFactoryTest.java12/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up before I fixed the race condition. This took a 
> very long time
> to
> figure out... Anyone have hints on how to best debug RM? I 
> started adding a
> server side only test which played messages against the 
> server and that
> helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> 
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)  addeddandiep
> /incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache
> /cxf/binding/soap/SoapTransportFactory.java12/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up before I fixed the race condition. This took a 
> very long time
> to
> figure out... Anyone have hints on how to best debug RM? I 
> started adding a
> server side only test which played messages against the 
> server and that
> helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> 
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)  modifieddandiep
> /incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache
> /cxf/binding/soap/interceptor/SoapOutInterceptor.java12/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up before I fixed the race condition. This took a 
> very long time
> to
> figure out... Anyone have hints on how to best debug RM? I 
> started adding a
> server side only test which played messages against the 
> server and that
> helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> 
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)  addeddandiep
> /incubator/cxf/trunk/rt/frontend/simple/src/main/java/org/apac
> he/cxf/frontend/ClientFactoryBean.java12/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up before I fixed the race condition. This took a 
> very long time
> to
> figure out... Anyone have hints on how to best debug RM? I 
> started adding a
> server side only test which played messages against the 
> server and that
> helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> 
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)  modifieddandiep
> /incubator/cxf/trunk/rt/core/src/main/java/org/apache/cxf/inte
> rceptor/AbstractInDatabindingInterceptor.java12/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up before I fixed the race condition. This took a 
> very long time
> to
> figure out... Anyone have hints on how to best debug RM? I 
> started adding a
> server side only test which played messages against the 
> server and that
> helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> 
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)  addeddandiep
> /incubator/cxf/trunk/rt/frontend/simple/src/main/java/org/apac
> he/cxf/frontend/ClientProxyFactoryBean.java12/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up before I fixed the race condition. This took a 
> very long time
> to
> figure out... Anyone have hints on how to best debug RM? I 
> started adding a
> server side only test which played messages against the 
> server and that
> helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> 
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)  modifieddandiep
> /incubator/cxf/trunk/rt/frontend/jaxws/src/main/java/org/apach
> e/cxf/jaxws/binding/soap/JaxWsSoapBindingInfoFactoryBean.java1
> 2/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up before I fixed the race condition. This took a 
> very long time
> to
> figure out... Anyone have hints on how to best debug RM? I 
> started adding a
> server side only test which played messages against the 
> server and that
> helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> 
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)  modifieddandiep
> /incubator/cxf/trunk/rt/frontend/jaxws/src/main/java/org/apach
> e/cxf/jaxws/ServiceImpl.java12/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up before I fixed the race condition. This took a 
> very long time
> to
> figure out... Anyone have hints on how to best debug RM? I 
> started adding a
> server side only test which played messages against the 
> server and that
> helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> 
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)  modifieddandiep
> /incubator/cxf/trunk/rt/frontend/jaxws/src/test/java/org/apach
> e/cxf/jaxws/URIMappingInterceptorDocLitTest.java12/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up before I fixed the race condition. This took a 
> very long time
> to
> figure out... Anyone have hints on how to best debug RM? I 
> started adding a
> server side only test which played messages against the 
> server and that
> helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> 
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)  unknowndandiep
> /incubator/cxf/trunk/rt/frontend/jaxws/src/main/java/org/apach
> e/cxf/jaxws/AsyncCallbackFuture.java12/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up before I fixed the race condition. This took a 
> very long time
> to
> figure out... Anyone have hints on how to best debug RM? I 
> started adding a
> server side only test which played messages against the 
> server and that
> helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> 
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)  addeddandiep
> /incubator/cxf/trunk/rt/frontend/simple/src/test/java/org/apac
> he/cxf/service/factory/RountripTest.java12/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up before I fixed the race condition. This took a 
> very long time
> to
> figure out... Anyone have hints on how to best debug RM? I 
> started adding a
> server side only test which played messages against the 
> server and that
> helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> 
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)  deleteddandiep
> /incubator/cxf/trunk/systests/src/test/java/org/apache/cxf/sys
> test/jaxws/HeaderClientServerTest.java12/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up before I fixed the race condition. This took a 
> very long time
> to
> figure out... Anyone have hints on how to best debug RM? I 
> started adding a
> server side only test which played messages against the 
> server and that
> helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> 
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)  modifieddandiep
> /incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache
> /cxf/binding/soap/SoapBindingFactory.java12/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up before I fixed the race condition. This took a 
> very long time
> to
> figure out... Anyone have hints on how to best debug RM? I 
> started adding a
> server side only test which played messages against the 
> server and that
> helped.
> Single threaded tests are so much easier to debug. But I need 
> to clean it up
> 
> yet and get it fully working before I can commit. (only tests 
> CreateSequence
> right now)  modifieddandiep
> /incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache
> /cxf/binding/soap/SoapBindingInfoFactoryBean.java12/20/2006
> 03:07:54o Renamed SoapDestinationFactory to 
> SoapTransportFactory as it now
> can work
> as a conduit too when creating client proxies.
> o Refactor Holder logic to interceptors. This is to help the 
> seperation of
> JAX-WS logic from the EndpointInvocationHandler and also so 
> we can support
> the XFire Aegis databinding Holder class (coming once I get the XFire
> Aegis support finished). I don't like the way I implemented 
> this at all.
> Especially since SoapOutInterceptor needs to look for -1 in 
> the type index.
> I think we should probably come up with a better method.
> o Separated JAX-WS EndpointInvocationHandler logic out so the Simple
> frontend
> can have clients.
> o Rename EndpointInvocationHandler to ClientProxy and add
> ClientProxy.getClient(Object) to make it easy to get the 
> underlying client.
> This will make it easier to add interceptors to a Client.
> o Add a bunch of toString() methods to the service model to 
> make debugging
> easier.
> o Move HeaderTest to jax-ws module and use local transport. 
> Test now takes
> .3 seconds instead of 8. Makes for much faster debugging.
> o Support get/setServerBean on ServerFactoryBean
> o Add logging to PhaseInteceptorChain so it can be 
> visualized. Just turn
> logging up to Fine and it will print out a diagram of the 
> phases and the
> interceptors in that phase.
> o Fix race condition with PhaseInterceptorChain's 
> pause/resume. There was a
> problem with WS-A/RM in that the executor was resuming the flow before
> the current interceptor had returned and the pausedMessage 
> was set. Now
> doInterceptor notifies resume() once its finished pausing. 
> resume() will
> wait for one second for the chain to finish pausing.
> 
> A couple thoughts from things I noticed while going through the code:
> - we seem to be removing the ws-a/ws-rm headers from the 
> header tree. Why??
> People will want to see these IMO and they'll be surprised 
> that they're
> gone.
> - As noticed on the mailing list a few days ago, I think 
> there are issues
> with the JaxwsInterceptorRemover approach long term. I had to 
> add the holder
> interceptors to the list so that they were removed as well.
> - SequencetTest was failing sporadically depending on whether 
> or not logging
> was turned up bef
> 
> ...
> 
> [Message clipped]
> 
> -- 
> Dan Diephouse
> Envoi Solutions
> http://envoisolutions.com | http://netzooid.com/blog
> 

Mime
View raw message