Forgot to follow up with the solution :) It turns out that certain Spring application context files were being loaded twice, causing some XFire thingy to be instantiated multiple times and fail on the second attempt. I don't recall the precise point of failure, but if you are having this symptom make sure that your Spring beans aren't getting created twice.
Preston BTW.. I seem to be stuck in an infinite loop while trying to unsubscribe from the dev list. Is there someone I can contact to remove me? On 10/11/06 10:20 AM, "Preston Lee" <[EMAIL PROTECTED]> wrote: > I'm just getting started with Xfire, and am trying to added a service (via > Jsr181 annotations) to a pre-existing webapp using Spring, deployed into > JBoss with a bunch of other Struts, Hibernate and EJB stuff. > > Most of the tutorials seems pretty similar, and I've followed the one here > very closely.. > http://www.memestorm.com/blog/basic-spring-web-services-with-xfire-and-jsr-1 > 81/ > > On deployment, however, I'm getting a "Cannot map handler" .. "There's > already handler" error which I've yet to find reference to. > > I've attached the full stack trace. Thanks a ton for your help! > > Preston >
smime.p7s
Description: S/MIME cryptographic signature
