Are you really using jboss-4.0.2, it is not out yet.
If you are sure this is a bug in the current Branch_4_0 , please create a jira issue for it and attach a simple sample deployment
Hi - I get the same error with 4.0.3SP1 and jdk5_06. Running my client with jdk1.4.2_10 instead of the 1.5.0 removes the error.
I have the exact same problem. I am running JBoss 4.0.3 with JBoss Portal. I've tried running it with 1.4.3 and 1.5_06 and I get that error with both VM's. Has anyone managed to get this service running?
I am using JAXM libraries from Sun. I placed them in $JBOSS_HOME/server/default/lib.
If anyone has gotten beyond this point, please, say something...
While I do get those warnings, truth is, I can access the content of the SOAPBody.
I was doing it using old documentation (btw, does anyone know why the JAXM documentation is so scarce and so badly written?), which made me think I was doing everything the right way, and if I couldn't see the content of the SOAPBody then it was JBoss's fault.
Of course this mistake will never happen again. At least not with the JAXM docs.
Once again, my apologies.
I am new in JBoss. I have deployed an EAR, which contains one jar file containg the bean files and one war file containg the webservice related files, including web.xml,wsdl and mapping files.
now when i am trying to access this webservice, i m getting error in client side but its showing no error in server side except only a warning.The incoming datas are also handled successfully.
The warning is similar to the posted warning.
I am including it again,
WARN [DeserializationContextImpl] Ignoring invalid namespace mapping: [prefix=,uri=]
Its really frustrating, couse i am not sure what to do... I have used WSDL2Java tool of AXIS
for client side.. This tool worked fine when i deployed my application using IBM Websphere.
For Server side i have used JWSDP pack's WSCOMPILE tools to generate the necessary artifacts.
Can anyone tell me whts the problem??