anonymous wrote : | You call the EJB from a servlet, thus servlet is client. | On your servlet, you will have some class of your EJB. | If you make some changes to your EJB and redeploy your EJB, but didn't update your WAR app, your servlet will connect to the EJB expecting the old version of the class, and thus cause the Exception. | You may wish to try to update both the EJB and WAR. |
While dealing with entrprise application this is quite correct: the fact is that this is prescribed by specifications. However with Eclipse plugin it is look like design problem. The versions of jar files supported by plugin can be different from server side counterparts, due to the natural software developemnt cycle. This introduce a problem of synchronizing the plugin's jars with each new versions of the server. Very elegant and, from my point of view, correct approach have Eclipse WTP project: you shift the responsibility to the user. In order to run/develop against some server user must define the server "runtime", that in turn contributes required jars directly from the server. BTW: do you plan to support WTP? Alex. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869230#3869230 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869230 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
