J2EE Support

I know this should have been posted on the EJB forum, but it seems noone reads that.

Folks, we're nearing the end of EAP and J2EE support is still troublesome at best. We can't define J2EE modules for existing code without hacking around a lot, and this limits how much we can test the features.

I haven't used any real EJB support since the first few Aurora builds, and I'm sure I'm not the only one who's not testing EJB support at all. We need at least the same level of J2EE support we had in Ariadna, and be able to work with existing source and deployment descriptors.

Not to mention extension points for third party application servers, but I'll leave that for later.

3 comments

+10. Totally agree.

For us it is especially important, as we work on EJB a lot. As a matter of fact we cannot use eap. I would appreciate that jetbrains provides server side programmers, an eap that they could use. And for me there is two big things :
- project and build infrastructure that must be achieved in a consistent way as server side projects are ususally a lot more complex to package, deploy, run, debug.
- and J2EE support with at least the same level that we have in 3.0.5 (especially refactorings...).

Hope we will be heard before the end of the eap !!!

0

Same here. I mentioned it before: I wonder why the hell such a
fundamental feature like project/module/j2ee/web configuration made it
into EAP that late. Only the last two builds or so gave a "preview" of
what it is supposed to be. And it seems to be far from being finished to me.

Richard De Falco wrote:

+10. Totally agree.

For us it is especially important, as we work on EJB a lot. As a matter of fact we cannot use eap. I would appreciate that jetbrains provides server side programmers, an eap that they could use. And for me there is two big things :
- project and build infrastructure that must be achieved in a consistent way as server side projects are ususally a lot more complex to package, deploy, run, debug.
- and J2EE support with at least the same level that we have in 3.0.5 (especially refactorings...).

Hope we will be heard before the end of the eap !!!


0

Please look for the response in the jetbrains.intellij.eap.j2ee

--
regards,
Alexey Kudravtsev.
JetBrains, Inc
http://www.intellij.com
"Develop with pleasure!"


"Marcus Brito" <pazu@animegaiden.com.br> wrote in message news:14037194.1070281142189.JavaMail.javamailuser@localhost...

I know this should have been posted on the EJB forum, but it seems noone reads that.

>

Folks, we're nearing the end of EAP and J2EE support is still troublesome at best. We can't define J2EE modules for existing code

without hacking around a lot, and this limits how much we can test the features.
>

I haven't used any real EJB support since the first few Aurora builds, and I'm sure I'm not the only one who's not testing EJB

support at all. We need at least the same level of J2EE support we had in Ariadna, and be able to work with existing source and
deployment descriptors.
>

Not to mention extension points for third party application servers, but I'll leave that for later.



0

Please sign in to leave a comment.