The AbstractMethodError I received with OC4J and EJB Session Beans.
We have this fairly screwed up development envirnment where there is only one OC4J instance for 5 developers which is really what caused this problem.
Someone would deploy the application, and before starting the application I would upload my version of the jar file which contains the EJB classes. Apparently , Oracle creates the wrapper classes which implement the remote interface at deployment, not when the OC4J instance is started and therefor my personal EJB classes was not having its additional methods wrapped.
Solution: Do not modify EJB classes once they are deployed.
No comments:
Post a Comment