Yesterday a coworker and myself where receiving 500 Internal Server Errors when sending test SOAP requests to our muse web service. After several frustrating days we eventually discovered our value for the Resource ID name in our SOAP Header was incorrect compared to the expected value, ResourceIdentifier, in the jndi-config.xml file. Eventually we set the log4j levels to DEBUG in the muse webapp under tomcat, and 1,000 lines later we noticed the ResourceKeyNotFoundException. But this was a server side error. As the client, the only error I received was a 500 Internal Server Error. The reason this occurred was because in older versions of muse (I believe pre-beta) the default jdni-config.xml value was ResourceID. Consequently all our test SOAP requests had ResourceID in it as well. Then when we started using beta and newer versions, we tested with our old SOAP requests with the conflicting Resource Id value. Ian and Sal, I believe we discussed this issue when Keith and I visited. What I think would be beneficial, would be a more descriptive specific exception returned to the client. Perhaps even returning the ResourceKeyNotFoundException with the explanation that the client should verify that the Resource Id values match up. Just an idea. Thanks, James.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
