Ted Leung wrote: > > I've just committed some changes which should allow WSDL2Java to > operate correctly. I'm still failing one of the Axis unit tests under X2, > so > I'll be working on tracking that down. If someone from Axis is adventurous > enough to get the latest X2 from CVS and look at the failed unit test, that > would probably help me find the bug. I'm interested in learning more about > Axis, but I need to climb the curve.
I've taken a quick glance, and something weird is going on. I'll dig in a bit. Essentially, the purpose of engine.invoke is to send a request and get a response. With Xerces 1 it works, but with Xerces 2, no message is produced. Not clear whether or not that implies a bug in Xerces 2, but it certainly implies a bug in Axis. FYI: http://nagoya.apache.org/~rubys/gump/xerces2/index.html has been updated with the latest. It looks like the compilation problems with Xalan2 and Xerces2 are resolved. Some of the other errors look interesting. Another portion of Xalan2 (Xalan1 compat) still has an issue as does dom4j, and other builds that actually involve an XSLT transformation (dom4j, cactus, struts, fop, test-ant, etc.) are all seeing null pointer exceptions when running with Xerces 2. - Sam Ruby --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
