Heh, ok. Jarek
On Thu, Apr 2, 2009 at 12:07 PM, Andreas Veithen <andreas.veit...@gmail.com> wrote: > Note that the tests applied to the (default Axis2) HTTP transport > initially were not meant to test the transport but to validate the > generic HTTP tests in the testkit. The purpose was to apply these > generic tests to the NIO HTTP transport. This allows to compare the > behavior of both transports. From that perspective we may leave the > tests in the transports project ... as tests for the testkit :-) > > Andreas > > On Thu, Apr 2, 2009 at 17:08, Jarek Gawor <jga...@gmail.com> wrote: >> On Wed, Apr 1, 2009 at 5:50 PM, Glen Daniels <g...@thoughtcraft.com> wrote: >>> Jarek Gawor wrote: >>>>> Also, I'd really like to get 1.5 out the door ASAP, it's lingered way too >>>>> long already. So whatever solution gets us there soonest with consensus >>>>> is >>>>> the one I'll be happy with. >>>> >>>> Yes, I agree. Sounds like we already agree on a solution (moving http >>>> and local back to Axis2). >>> >>> OK, I'm on this tomorrow. If anyone has issues with it, please pipe up! >> >> I already moved some of the utility classes and methods back to Axis2 >> and eliminated a direct dependency on transport base from http and >> local. But once I was actually looking into moving the http module to >> Axis2 I realized the the http transport tests have dependency on the >> testki module which has dependencies on the transport base module.... >> So we can easily move the transport http code itself but not the >> tests... anybody have ideas how to deal with this now? >> >> Jarek >> >
