Last week, we had the author of TDD for a Shopping Website LiveProject. Friday at 11am Ranch time, Steven Solomon will be hosting a live TDD session just for us. See for the agenda and registration link
Business methods are declared in component interfaces. You cannot have static methods in an interface. If methods in stateless session beans are static then the instance variable must be static as well and this will create synchronization problems when there are several instances of the bean. Static methods cannot be overridden but only hidden. The conatiner specific class usually overrides your bean class to provide container services which cannot be done if your business methods are static(since the superclass method is hidden and not overridden). You can have non business methods as static but it is of no use.
well the problem is from a session bean we are calling static method of a third party work router API and are facing constant database deadlock problems. I wanted to know if this could be a possible reason
OK, synchronization won't work if you are deploying this application into a cluster -- you'll still get the database deadlock across JVMs. It seems to me that the only way to solve this is to open a trouble ticket with the vendor of your third-party router software and make it THEIR problem (which it is!). Kyle