Honestly, I think your best bet is to just grab woodstox and use it. It's a faster parser by far and it's also the most tested with CXF.
I know the Axiom guys have spent a LOT of time the last couple weeks trying to workaround issues with the way IBM tried to interpret the Stax spec which causes their stax writers to behave very differently than the Sun and Woodstox parsers. This might be one of those areas. I'll trying building cxf with the IBM jdk/parsers and seeing if anything obvious jumps out. Dan On Tue August 25 2009 3:14:48 pm youngm wrote: > Thanks for the tip. I tried it and got the same error. :( I'm going to > try submitting a bug to IBM about that. If anyone has any other ideas I'll > gladly try them. > > Thanks, > Mike > > Glen Mazza wrote: > > The heart of your problem seems to be the "The namespace URI > > "http://www.w3.org/2005/05/xmlmime"; has not been bound to a prefix." > > message. Googling that message without the URI appears to suggest > > there's an isRepairingNamespace() property that can be set to fix that > > problem, but I'm not certain: > > > > http://java.sun.com/javase/6/docs/api/javax/xml/stream/XMLStreamWriter.ht > >ml#writeStartElement(java.lang.String,%20java.lang.String) > > > > HTH, > > Glen > > > > youngm wrote: > >> I'm using CXF in Websphere 7. I'm trying to use the IBM JDK's stax > >> library. Everything seems to work fine but when I try to get a WSDL > >> with a schema that is using MTOM I get the following stack trace. > >> > >> It appears to work fine when using the Sun JDK. Any thoughts? I'm not > >> the best at Stax but does this look like a CXF bug? -- Daniel Kulp [email protected] http://www.dankulp.com/blog
