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.
Tads ----- Original Message ----- From: "Sam Ruby" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, October 13, 2001 4:37 AM Subject: Re: [Xerces2] Beta3 Release Plan > Ted Leung wrote: > > > > Axis is just using SAX, now right? > > Yes. > > > It should be possible to take care of this size issue. > > The issue is moot if it doesn't work. > > I started to take a look at it, but was discouraged when the symptoms > changed three times with three different snapshots of Xerces 2. I just > rebuilt xerces2 from cvs, and at the moment, the symptoms haven't changed > since my last look, so checking in deeper is now back on my todo list. > > >From the looks of the failure, it would be easier to debug if there were > somebody familiar with xerces 2 and axis implementation. In other words, > the empty set. > > My specific goal here is to get it working once, update gump so that it > build that way repeatedly, and that way we will be able to know quickly if > the situation ever changes. From that point, I can generally isolate the > individual change that caused the problem to surface, and we can address it > at that time. I have mentioned that goal a few times on this mailing list, > but I saw no evidence that the sentiment resonated. > > My more general goal is to get projects to work together. Case in point: > while Xalan can work with any JAXP compliant parser, it appears to have > specific code in it to exploit Xerces if it is present. Unfortunately, > Xerces 2 looks sufficiently like Xerces 1 that Xalan is fooled into trying > apis that are no longer present. Relevant lines from xalan's build.xml: > > <available property="xerces.present" > classname="org.apache.xerces.parsers.SAXParser"/> > > <exclude name="**/CoroutineSAXFilterTest.java" > unless="xerces.present" /> > <exclude name="**/CoroutineSAXParser_Xerces.java" > unless="xerces.present" /> > <exclude name="**/IncrementalSAXSource_Xerces.java" > unless="xerces.present" /> > > Personally, I can think of no higher testimonial to the viability and worth > of Xerces 2 that if it could not only work for Xalan2 but if Xalan2 could > exploit the new design. It would also seem to me that someone who was > knowlegable on the new Xerces2 design could download Xalan, quickly code up > the equivalent to these three sources for Xerces2, update the build.xml to > compile different sources based on whether xerces1 or xerces 2 were > present. You could even run their smoketests to see if there were any > other bugs or compatibility issues. When done, submit a patch to the Xalan > team. Joe Kesselman seemed like he would be interested. > > Then perhaps the process could be repeated with Axis. ;-) > > - Sam Ruby > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
