Using plain java classes instead of using SessionBeans would actually make testing the component easier. You can write component tests as normal Junit tests. You can run them outside the container (IDE, build script etc) by using mocks for the dependent entity beans and if you want to test in a container environment you can use the same tests to run inside the container by using the Cactus framework.
Look at option B, reuse Junit testcase. http://jakarta.apache.org/cactus/writing/howto_testcase.html I would also suggest that you relook your decision to use Entity bean for persistence. Going with Hibernate for persistence is a better alternative. That would make it really easy to test your code outside of a container. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867797#3867797 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867797 ------------------------------------------------------- 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-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
