deployment descriptors and other nuisances in 4.0

Hi all,

I'm a bit disappointed with the J2EE support with v4.0. I came to know IDEA that was extremely flexible and didn't force you to adapt any specific paradigm. That has changed with 4.0 at least with respect to J2EE development.

Apart from no longer auto-discovering ejbs setting up a module for each ejb ist a pain that should at least be automated.

I was also dispointed to note that (as suspected) the version of ant used is not configurable - meaning for example that the ]]> with cmpversion is not available.... sigh... patching it up to 1.6 still works for me, thank goodness...

But worst of all, there is only generic ejb support and web-logic... guys, would it really have been that difficult to be able to at least attach app server specific deployment descriptors (like jboss.xml, jbosscmp-jdbc.xml etc.) to an j2ee module to be packaged up in the META-INF directory as well?? Not that I'm using your EJB support a lot because XDoclet does a nice job, but checking the source files with J2EE panel was always helpfule to spot occasional errors and it would have been a great help to build the jars from the UI....

so please allow

4 comments

..oops, sorry for not finishing the post above - so, you can't edit posts anymore in these forums, huh?...

anyway, is there a chance of at least being able to specifiy additional files to be stuffed in the META-INF, please ;)

thanks, Oliver

0

Oliver Fink wrote:

..oops, sorry for not finishing the post above - so, you can't edit posts anymore in these forums, huh?...

anyway, is there a chance of at least being able to specifiy additional files to be stuffed in the META-INF, please ;)

thanks, Oliver


One easy approach to manage additional files in the META-INF folder is
to just add a META-INF directory to your source folder and put those
files in there. In case IDEA recognizes them as resources (e.g. XML
files) they get copied to the output folder as well. Since the output
folder gets packaged into an EJB JAR, you get all those additional
META-INF files as well. The benefit of this solution is that it works in
every IDE that is aware of resource files. Also using ANT is very easy
as well since you do not need to assemble your JAR from different places
but just package a single directory.

Michael

0

One easy approach to manage additional files in the
META-INF folder is to just add a META-INF directory to
your source folder and put those
files in there. In case IDEA recognizes them as
resources (e.g. XML files) they get copied to the
output folder as well. Since the output
folder gets packaged into an EJB JAR, you get all
those additional META-INF files as well.

Michael


Wow, this sucks. This means I have to keep switching between 'Package' view to be able to browse my additional deployment descriptors, and the 'J2EE' view to bring up the conceptual view of my EJB.

Intellij needs to set this up like in 3.0, where I can specifically designate a file as an 'additional deployment descriptor', and have it show up in the J2EE view alongside ejb-jar.xml.

Corby

0

yup, that's what I was after - it was good thinking in 3.x to have additional deployment descriptors but I didn't expect them to remove features, and that's what it feels like using 4.0 right now.

3.0 was really flexible in most respects, for now, 4.0 just has some clicky-fancy-gui for WebLogic only(?). Frankly, I don't care about WebLogic and would've rather seen it as a plug-in for those who use it...

oliver

0

Please sign in to leave a comment.