I have been working on a project which uses Spring 3.0 for all middle tier activities and JBOSS App. Server for deployment. In that, we encountered a weird issue while using Spring’s Security Implementation, everything works fine in the customer end where as in vendor place the site was not at all working if we include this security implementation, when we remove that and launch the application everything works fine. Since this is a intranet web app and used only for testing a huge data transfer we revoked the security implementation in vendor end and they were doing their job without any issue.
Last week when myself and on-site person decided to work on this to find out at the root cause of this issue. After around 4 hrs of head ache, we found that the entire issue was due to JBOSS Server, both of us are using 5.0 GA Release but the only difference vendor launched it in a Community edition (open source) where as customer launch from Enterprise edition. As soon as we change the server, everything works fine in both end.
I found this a weird issue from JBOSS. No where in JBOSS site, it has been mentioned that community and enterprise edition has different implementation and even the error message JBOSS throws doesn’t say anything about these things, instead it states some error in Spring’s Security XSD Schema. From this, we learn a lesson that whenever a tested piece of code doesn’t work on other end always check the entire software list used on the other end w.r.t every minute detail and then look into your deployment steps.
