Hi, I know this wasn't written to me, but thought I'd offer my thoughts (o:
> Also, until you complete your test in your development environment, you > don't have to build an installation of your application. EJB's deployment > requirement is like requiring people to build installation disk. And, you > must install the system to have the other half the system be generated. How > can you call this productive or conducive to iterative development? yes, its different to writing client-side code, which is what it sounds like you are comparing it to. Without wanting to seem rude, I'm wondering if you've had experience with servlets, or other components that require a container. I was working on servlets prior to ejb, so the requirement of a container seemed natural, although I can see how if one was writing swing apps, then it might seem very odd. > My complaint with EJB is that much of "what the system does for you" is > generated during deployment time and is hidden away from the developer. thats the idea. you said before that you didn't like the idea of debugging the MFC framework, well, consider these container generated classes to be like the framework - you shouldn't need to worry about them. essentially, you write the business logic (the bean class) tell the container what to expose (home and component interfaces) and the container will plug it all together. as I suggested before, XDoclet (http://sf.net/projects/xdoclet) makes the cycle _much_ quicker, and has a nice set of samples to introduce you to it. > This is certainly the case with Sun's reference EJB server implementation > which I've been working with. Perhaps it's a bit better with open source > stuff like JBOSS. But the fact remains: deployment/installation must be > done before you can test your modules with the rest of the system. The > other half ("better half") doesn't even come into existence until you > deploy. just as with a client side app, you rely on the window manager to do a fair chunk of the work. > How do I unit test a CMP bean before it's deployed? Could you share some > concrete ideas based on your experience, instead of empty talk? personally I have no experience in prior deployment testing. but I assume it would be possible to create a dummy container, and test in that. but if you're going to do that, then you may as well just deploy the real thing. junit (http://junit.org) has some testing support for j2ee, that might be useful (I haven't used it myself). cheers dim =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
