Tony, If you want to test your session beans and MDBs you can use the JBoss microcontainer. It starts up very quickly. No need for a long running server. Its been discussed a few times on this mailing list - I also have an example in my book's source code.
EJB3 entity beans (aka JPA) can easily be tested outside of the container. I hope this helps Chris -- Enterprise POJO consulting - http://www.chrisrichardson.net Author, POJOs in Action - http://www.manning.com/crichardson Enterprise POJOs blog - http://chris-richardson.blog-city.com On 7/14/06, Tony Hillerson <[EMAIL PROTECTED]> wrote:
Hello all, I have a project that will use EJB3.0, and as far as I know only a few containers support that. I'm using jBoss now. My question is along the lines of the "Improving Web Development Productivity" section of the Maven Book. I've tried the jetty6 plugin and it's perfect for development; it lets me make changes to the working copy of the source, test them locally, and check them in. I don't have to deploy every time I make a change to the code, etc. The only problem is that I don't think the EJB3.0 part will work with jetty. Am I wrong there? Is there any way to let me easily deploy and view my web file changes with the cargo plugin somewhat like the jetty6 plugin? Can I start a development server, make working copy changes and see them without running maven and deploying every time I make a change? Thanks, Tony --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
