pb with soap msg generation axis 1.2rc3...empty namespaces

hello,
we have implemented a custom java extension in order to handle sessions with one of our partners. this session management implies that we call some web services to open/close/… these sessions.
we already have a soap client that works with axis 1.2 final release. but unfortunately, Mediator 7.4.2 works with release candidate axis 1.2 rc3, and there obviously is a difference between the 2 versions.
assuming that we execute the same java code, here’s what we get with the axis 1.2 final
[color=“blue”]
<soapenv:Envelope xmlns:eb=“http://www.ebxml.org/namespaces/messageHeader” xmlns:xlink=“http://www.w3.org/1999/xlink” xmlns:xsd=“http://www.w3.org/1999/XMLSchema” xmlns:soapenv=“http://schemas.xmlsoap.org/soap/envelope/” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
soapenv:Header
<eb:MessageHeader eb:version=“1.0” soapenv:mustUnderstand=“0” xmlns="">
eb:ConversationId2006-11-24-69545</eb:ConversationId>
eb:From
<eb:PartyId type=“urn:x12.org:IO5:01”>999999</eb:PartyId>
</eb:From>

(…)
[/color]

and then with axis 1.2 rc3
[color=“blue”]
<soapenv:Envelope xmlns:eb=“http://www.ebxml.org/namespaces/messageHeader” xmlns:xlink=“http://www.w3.org/1999/xlink” xmlns:xsd=“http://www.w3.org/1999/XMLSchema” xmlns:soapenv=“http://schemas.xmlsoap.org/soap/envelope/” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
soapenv:Header
<eb:MessageHeader eb:version=“1.0” soapenv:actor=“http://schemas.xmlsoap.org/soap/actor/next” soapenv:mustUnderstand=“0” xmlns="" xmlns:eb="">
<eb:ConversationId xmlns:eb="">2006-11-24-48764</eb:ConversationId>
<eb:From xmlns:eb="">
<eb:PartyId type=“urn:x12.org:IO5:01” xmlns:eb="">999999</eb:PartyId>
</eb:From>

(…)
[/color]
we can notice that with the rc3, some empty namespaces are added to header/body elements!!

this is apparently known as a bug in axis 1.2 beta releases…and we didn’t find how to solve it yet…
do you have any clue about how to get rid of these namespaces with the rc3??
the response might be in source code of the soap gateway, as this component is actually working with those versions!!..

just take note that, it is not conceivable for us to override the Mediator lib, by copying the final axis 1.2 jars in the Mediator/host/lib directory, as if we do so, SAG won’t support our Mediator installation anymore…

thanks for your help!!