Jim, Irregardless of wss4j, we need to get this working with xalan. xalan is used by a LOT of different applications and JDK's so it really needs to work. Example: it's included as is in the IBM JDK. It's also stuck on the classpath in most app servers like Geronimo and WebSphere. Thus, we need to get this to work.
Looking at your code, you are using a StringWriter and calling the jaxbContext.marshal(...) with that. How about creating a W3CDOMStreamWriter and calling marshal with that and then returning a DOMSource instead? Basically, have you tried the other various flavors or marshal in JAXB? Dan On Wednesday 19 December 2007, Jim Ma wrote: > Hi , > > I am modifying the classes related to call back system tests to use > the new JAXWS2.1 specified W3CEndpointReference . > During this JAXWS2.1 api update , i ran into an interesting issue . > W3CEndpointReference always marshals unexpected > xml for me : some namespaces is missing in the generated xml when it > is running in systest module , but it generated well in > other module. > > After I investigation , I found the systest indirectly refers to xalan > jar through ws-security. dependency . This will cause > JAXB generated error xml . > > Does our WSsecurity invoke some classes in xalan.jar? or wss4j > implementation needs to depend on xalan.jar ? > > Thanks > > Jim -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog
