Re: Refactoring Wish List
To jump into this discussion at a non-linear place, another useful addition to the jdee would be the ability to add custom javadoc tags for xdoclet. Xdoclet comes with a java gui tool for this (xdocletgui) which modifies the source files. It would be considerably easier to use in emacs if the functionality was directly available. The rules for which tags are allowed when using a particular module are contained in xml files. Typically the conditions involve what kind of item you are commenting (class, method, or field, sometimes whether it is a getter/setter) and what other tags are present. I think in order to do this in elisp one would need an xml parser and a parsed version of the java file indicating what kind of element you are at and what javadoc tags are already present. So far I haven't tried doing any lisp programming (since about 1968) so I have no idea how practical this would be. Any advice? Thanks david jencks
Fwd: Re: J2EE/JBoss [davidjencks@directvinternet.com]
JBoss officially supports and recommends using xdoclet for generating home, remote, local, localhome interfaces and the ejb-jar.xml and vendor specific deployment descriptors. I have yet to hear of anyone trying xdoclet and wanting a gui-like or wizard based solution for this stuff. What _is_ extremely handy is jde code generation templates that generate the xdoclet tags with the methods. For instance, I have some for mbean attributes, that generate get/set pairs with the @jmx managed-attribute tags in the javadoc. Ones for ejb methods and get-set pairs would also be extremely handy. I'd like these to be part of jde if there is interest, otherwise I will try to figure out how to include it in jboss. I think to officially support something like this effectively in jde there would need to be a way of swapping sets of templates in and out of the menu and keyboard shortcut system, depending on the template mode you are in: ejb, mbean, jdo, jsp, etc. There already is a little j2ee support in jde, you can get some code generation for basic session and entity beans. I find generating a new class as an entity or session bean is more convenient. My current templates are for I think one or 2 jde releases ago, I haven't had time to upgrade to the latest yet. david jencks On 2002.07.22 17:42:20 -0400 [EMAIL PROTECTED] wrote: Does anyone know of or is anyone interested in there being J2EE (ie EJB) support in JDEE? I am told by the O'Reilly book I'm learning EJB with that IDEs do things like creating ejb-jar.xml (or whatever it is) files etc -- In Jbuilder Personal that whole section is greyed out, it says that it is a JBuilder Enterprise feature- now that O'Reilly is supporting JBOSS this seems like a worthy thing for JDEE to do -a case for Open Source! If it doesn't exist yet I'd be interested in trying to work on it, I've been through the emacs-lisp tutorial and done a bit of coding. John Holland -- I made a killing on Wall Street a few years ago...I shot my broker. --Groucho Marx
Re: Compile all open Java buffers
I find a modular build system works well, and finds files i've modified, saved, and closed. It also works with more complicated build processes such as code generation and packaging. I can compile only the module I'm working on in 15-30 seconds, whereas the whole project build takes 2-5 minutes. The only modular build system I know of is the jboss buildmagic system. I'd like to hear of others. david jencks On 2002.07.22 19:43:06 -0400 WATSON Matt wrote: Does anyone know a JDEE command that compiles all open Java buffers that are in the current project? Something like C-c C-v C-c, except that it finds and compiles multiple files... I have similar problems with compile times and I think a command like that would be quite cool. I imagine it's not too difficult, if only I had the time. While I'm waiting for those compiles, my machine is trashed, otherwise I'd be doing it then! Matt IMPORTANT NOTICE: This e-mail and any attachment to it is intended only to be read or used by the named addressee. It is confidential and may contain legally privileged information. No confidentiality or privilege is waived or lost by any mistaken transmission to you. If you receive this e-mail in error, please immediately delete it from your system and notify the sender. You must not disclose, copy or use any part of this e-mail if you are not the intended recipient. The RTA is not responsible for any unauthorised alterations to this e-mail or attachment to it.
