----- Original Message ----- From: "Glen Daniels" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, December 03, 2002 7:05 AM Subject: RE: adding offline support to axis tests
> > They are indeed two separate issues. Eventually, I want to move most of the tests which currently access a service across the net to be local "XML playback" tests, to avoid problems with down servers / remote version skew /etc. However we'll always have a need for interop tests, and so we'll want the offline switch anyway (or perhaps an "online" switch?). > > I envision the future Axis user downloading the package and being able to completely build/test it with ant all-tests on a disconnected laptop with no config changes. Running ant interop-tests or somesuch would attempt the online stuff. yes, that would be the best > Hm. Actually, the more I think about this the less I'm convinced we need a switch as much as a set of separate ant targets....? we will need a separate target to refetch all the WSDL Files; then patterns of which build files to run when various conditions are met (such as JMS, real app server, etc) I have all the offline patterns working, but guess what rears its ugly head in the process: memory leaks in the build. Even with the compiler set to jikes, the only way the build is completing is to fork. So somehow either what I've done or some other changes has pushed us over the memory leak limits. I looked at foreach, <Ant> and ant.Project and nothing is obviously a problem, but there is still something out there that needs to be tracked down and dealt with. Who knows any good tools for determining Java memory leaks?
