I tried that, but - at least in this case - it makes no difference on the generated webservice-call. And I'm still getting the very same AxisFault about a xmlns in the envelope. Strangely enough, the header looks fine:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns0="http://signup.ull.tiscali.netpioneer.de/types">
Ok, I investigated this case a little further: This does not look like its a problem of JBoss - I tried to generate my Client with Axis - the Axis-Client works. It shows some warnings about "Ignoring invalid namespace mapping: [prefix=,uri=]", that come from the empty namespaces for elements (e.g. ) that axis generates - but the rest looks ok.
The Call gets validated against the XSD *before* it arrives in the Port-Implementation, which is fine. Now I have my SOAPElement in
public void signup(SOAPElement orderElement) throws RemoteException { ... }
Solved this one: SOAPkit from Soapical (http://soapical.sourceforge.net/soapkit/) has some very nice utilities, that allow you to go from SOAPElement -> String and vice-versa. Converting the SOAPElement to String and then parsing it with XMLBeans now gives me validated&correctly mapped XMLBeans.
I think I'm done now, so thx to everybody who helped me out!
cheers
stf