*nod* Hani mentioned it - it's called XDoclet ;) Basically all your EJBs are written in a single class, with all deployment information in JavaDoc comments, then an Ant task parses your beans and creates all the interfaces, J2Ee deployment descriptors and app server deployment descriptors. It's a life saver for managing EJBs IMHO.
-mike On Fri, 2001-12-07 at 09:06, Michael Descher wrote: > Well, there are two ways you can do stuff. Either put everything in a single > fat application (like JBuilder) or have specialized tools for each task. I > think specialized tools are the way to go since you can startup the things > you need and don't need to load tens of megs no matter if you need them all > the time or just sometimes. > > IDEAs file synchronization makes it easy to have multiple tools open even > editing the same files. This way you can have your favourite UML tool for > example running together with IDEA, using the UML tool for things it is good > at and using IDEA for the "hardcore" coding. > > In the same manner I'd rather like to have a standalone EJB tool for > creating base classes, deployment descriptor, etc. and keep IDEA clean and > simple (yet powerful) for editing Java source (in the first place), > compiling projects, running ant tasks. > > By the way, is there any (good) such EJB tool that is made just for (and > therefore specialized on) managing EJBs and related stuff (like deployment > descriptors)? > > Michael > > > -----Ursprungliche Nachricht----- > > Von: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]Im Auftrag von Ingi Gauti > > Ragnarsson > > Gesendet: Donnerstag, 6. Dezember 2001 22:34 > > An: [EMAIL PROTECTED] > > Betreff: [Eap-features] Re: EJB wizard > > > > > > I can hear that you are not that happy with my suggestion, I'm not a > > wizard guy, the application I used before IntelliJ was TextPad, and I > > still use it for lot's of other editing other than Java files. > > > > But do you realize how quicker you would be programming CMP beans, if > > the Entity bean, ejb-jar.xml file and helper classes would all be > > connected. Change one variable, and it would change all the files. Also > > all the debugging trouble you get sometimes with EJB beans. Like if a > > method in the remote interface isn't the same as in the as in the EJB > > bean, you get an error and lot's of other things. I have no doubt that > > if you have developed a EJB bean you know that everything has to be > > perfect. > > > > Well that's my thought. > > Ingi > > > > > > _______________________________________________ > > Eap-features mailing list > > [EMAIL PROTECTED] > > http://www.intellij.com/mailman/listinfo/eap-features > > > > > _______________________________________________ > Eap-features mailing list > [EMAIL PROTECTED] > http://www.intellij.com/mailman/listinfo/eap-features -- Cheers, Mike -- Mike Cannon-Brookes :: [EMAIL PROTECTED] Atlassian :: http://www.atlassian.com Supporting YOUR J2EE World _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-features
