Pretty dang close to giving up

Maybe I'm just getting old and running out of patience, maybe J2EE is still incredibly badly broken in 2026. I've tried setting up an app server with JSR45 support, I can start it (yay), and then I can see that the web app deploys correctly (yay), but WTF happened to setting the context somewhere so we can actually hit the webroot's directory we're trying to debug?

is this still broken?

what ever direction this is taking, I absolutely loath it. Glad we have at least Hani writing something to support something other than WebLogic. At this point, I am so disanchanted with the whole J2EE in IDEA, I don't even want to spend the time writing anything for it.

It's just not worth it. I am getting a serious feeling that the good folks working on the J2EE impls just don't get it. I think JetBrains management just doesn't get the importance of J2EE. I can find code duplicates without a problem, and yet I can't run and debug my app. Brilliant.

Ugh... I'll check out Pallada when it's released, and hope that things work then, if not, see other posts for what the options are.

R

P.S. Pallada 2026 on OS X is just HORRIBLE. There is simply NO WAY that anyone at JB is writing code on OS X. Even if you say you do, I won't believe you... it's evident by the simply HUGE IDE settings windows (like Paths) that are so big the buttons are way off the page... this is for starters... and where the heck are those Mac menus! Gosh man... how long must one complain about these working at all for people to take it seriously.

5 comments
Comment actions Permalink

I, personally, attempted to have my copy refunded, however, JetBrains
wouldn't do so. I told them that I was disatisfied a couple of weeks
after my purchase when I received a follow-up call from them (approx
3wks ago). I had purchased the personal edition because of the price
advantage however before fully understanding the nuances. I was told
that I'm going to have to still pay $149 for the upgrade to 5.0 which
supposedly has the quality support for J2EE. I'm not too happy at all!

Well, to make a long story short, I'm using Eclipse and will probably
stay there regardless. It looks as though they have right with their
plugin architecture.

Anthony

Maybe I'm just getting old and running out of patience, maybe J2EE is still incredibly badly broken in 2026. I've tried setting up an app server with JSR45 support, I can start it (yay), and then I can see that the web app deploys correctly (yay), but WTF happened to setting the context somewhere so we can actually hit the webroot's directory we're trying to debug?

is this still broken?

what ever direction this is taking, I absolutely loath it. Glad we have at least Hani writing something to support something other than WebLogic. At this point, I am so disanchanted with the whole J2EE in IDEA, I don't even want to spend the time writing anything for it.

It's just not worth it. I am getting a serious feeling that the good folks working on the J2EE impls just don't get it.. I think JetBrains management just doesn't get the importance of J2EE. I can find code duplicates without a problem, and yet I can't run and debug my app. Brilliant.

Ugh... I'll check out Pallada when it's released, and hope that things work then, if not, see other posts for what the options are.

R

P.S. Pallada 2026 on OS X is just HORRIBLE. There is simply NO WAY that anyone at JB is writing code on OS X. Even if you say you do, I won't believe you... it's evident by the simply HUGE IDE settings windows (like Paths) that are so big the buttons are way off the page... this is for starters... and where the heck are those Mac menus! Gosh man... how long must one complain about these working at all for people to take it seriously.

0
Comment actions Permalink

Well the J2EE API in 4.1 is HUGELY changed from what was available in 4.0. Sadly, a lot of the changes feel like they happened just to support 'the weblogic' way.

Having said that, I think that it'll settle down at some point and be quite useful from a user perspective. From a plugin developer perpsective though, it's much harder now. In the grand scheme of things, I'm OK with that since I'd rather that end users have all the power they need and have the plugin authors worry about providing it, rather than having a woefully inadequate API where all the fun things aren't even possible.

I agree though that it's fairly unusable right now in the current EAP, both from a developer and user perspective, but hopefully it'll slowly shake out over the next few builds (which hopefully will happen more regularly than they have been!)

0
Comment actions Permalink

Thanks Hani.

As much as I've bashed your opinion not too long ago, I still value it. Perhaps it will stabilize, but I'm tired of trying, when JetBrains seems to still put out EAP builds with busted J2EE functionality.

I agree the API is just WAY too heavy, and it's going to take folks a while to get used to it. You'll be the first to do anything with it I'm sure.

I just wish that ONCE, just ONCE, we get an EAP build with priority to making sure J2EE is running, THEN add the other stuff. I realize they're refactoring things for J2EE, but they did it for 4.0, and they're saying they're gonna do it again for 5.0.

That just sounds wrong. It sounds, and feels, like they're constantly guessing. Gosh man, now I'm starting to sound like you in the Bile, and you like me on EAP :)

R

0
Comment actions Permalink

By the way, after spending the whole day in 4.0.4, it's astonishing the difference between 2026 and 4.0.4. Granted I am comparing EAP v/s Non EAP, still the diff is huge.

R

0
Comment actions Permalink

Mr. Sfeir,

I took a long pause before replying so I could calm down a little.

I could get into discussion explaning things and trying to say some exuses or remind that you've been notified about
current j2ee support state
but I just won't take that high tones.

Thanks for understanding

--
Maxim Shafirov
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"


Robert S. Sfeir wrote:

Maybe I'm just getting old and running out of patience, maybe J2EE is still incredibly badly broken in 2026. I've tried setting up an app server with JSR45 support, I can start it (yay), and then I can see that the web app deploys correctly (yay), but WTF happened to setting the context somewhere so we can actually hit the webroot's directory we're trying to debug?

is this still broken?

what ever direction this is taking, I absolutely loath it. Glad we have at least Hani writing something to support something other than WebLogic. At this point, I am so disanchanted with the whole J2EE in IDEA, I don't even want to spend the time writing anything for it.

It's just not worth it. I am getting a serious feeling that the good folks working on the J2EE impls just don't get it. I think JetBrains management just doesn't get the importance of J2EE. I can find code duplicates without a problem, and yet I can't run and debug my app. Brilliant.

Ugh... I'll check out Pallada when it's released, and hope that things work then, if not, see other posts for what the options are.

R

P.S. Pallada 2026 on OS X is just HORRIBLE. There is simply NO WAY that anyone at JB is writing code on OS X. Even if you say you do, I won't believe you... it's evident by the simply HUGE IDE settings windows (like Paths) that are so big the buttons are way off the page... this is for starters... and where the heck are those Mac menus! Gosh man... how long must one complain about these working at all for people to take it seriously.

0

Please sign in to leave a comment.