2061 J2EE - YUK!

Ummm guys, we're going backwards here. You've just added a new way of working in IDEA which exists in NONE of the rest of the interfaces of the IDE and it completely caught me off guard!

Now when you want to add a Tomcat instance you click on the + and you have a POPUP??? What the heck???

You've also added advanced settings, and we still setup a serverDK then we setup our app server AGAIN. Why do we have to go through so many steps and have interfaces which don't conform with anything else in the app???

The solution is VERY simple guys:
1- Setup the app server with ALL settings in the J2EE IDE config section. Add as many App server and configuration combos as you want there.

2- When you have your project, go into run/debug config, choose webapp tab, click the + button, show me a window with a drop down that shows me which app server I want to use. When I choose that app server, show more config options that are specific to the project or this web app. In Tomcat's case, that would end up being the context drop down. That's it! No crazyness.

I don't know if anyone cares anymore, but this interface is going backwards not forward and it's getting harder and harder to use... even for someone like myself who's been through a lot of EAPs. new comers will cause you a support nightmare with this kind of process.

You can beat me up all you want for saying this. I just don't think anyone at JB is listening anymore.

R

8 comments

Well, I haven't tried 2061 yet because I've been so frustrated with 2057
but I agree with Robert. You keep making J2EE dev harder. K.I.S.S.

Robert S. Sfeir wrote:

Ummm guys, we're going backwards here. You've just added a new way of working in IDEA which exists in NONE of the rest of the interfaces of the IDE and it completely caught me off guard!

Now when you want to add a Tomcat instance you click on the + and you have a POPUP??? What the heck???

You've also added advanced settings, and we still setup a serverDK then we setup our app server AGAIN. Why do we have to go through so many steps and have interfaces which don't conform with anything else in the app???

The solution is VERY simple guys:
1- Setup the app server with ALL settings in the J2EE IDE config section. Add as many App server and configuration combos as you want there.

2- When you have your project, go into run/debug config, choose webapp tab, click the + button, show me a window with a drop down that shows me which app server I want to use. When I choose that app server, show more config options that are specific to the project or this web app. In Tomcat's case, that would end up being the context drop down. That's it! No crazyness.

I don't know if anyone cares anymore, but this interface is going backwards not forward and it's getting harder and harder to use... even for someone like myself who's been through a lot of EAPs. new comers will cause you a support nightmare with this kind of process.

You can beat me up all you want for saying this. I just don't think anyone at JB is listening anymore.

R

0

Hello Robert,

Where did you get 2061 from? Did they release a new EAP build?

Thanks,
--Venkat.

Ummm guys, we're going backwards here. You've just added a new way of
working in IDEA which exists in NONE of the rest of the interfaces of
the IDE and it completely caught me off guard!

Now when you want to add a Tomcat instance you click on the + and you
have a POPUP??? What the heck???

You've also added advanced settings, and we still setup a serverDK
then we setup our app server AGAIN. Why do we have to go through so
many steps and have interfaces which don't conform with anything else
in the app???

The solution is VERY simple guys:
1- Setup the app server with ALL settings in the J2EE IDE config
section. Add as many App server and configuration combos as you want
there.
2- When you have your project, go into run/debug config, choose webapp
tab, click the + button, show me a window with a drop down that shows
me which app server I want to use. When I choose that app server,
show more config options that are specific to the project or this web
app. In Tomcat's case, that would end up being the context drop down.
That's it! No crazyness.

I don't know if anyone cares anymore, but this interface is going
backwards not forward and it's getting harder and harder to use...
even for someone like myself who's been through a lot of EAPs. new
comers will cause you a support nightmare with this kind of process.

You can beat me up all you want for saying this. I just don't think
anyone at JB is listening anymore.

R


0

I completely agree with Robert on his proposed solution.
I just downloaded 2061 so I cannot comment on it yet but you can be sure I will if it is as bad as he makes it sound like.

Jacques

0

I agree entirely - there is really no reason for this baroque setup.
As for the popup - since it is so completely different from anything
else in IDEA, I can only hope it's a temporary solution until the UI
stabilizes...

CU,
Edwin

0

Im I right, you want
1. one tab for all the App Servers. When you click '+' in it you're showed a dialog where you select the configuration type.
2. Tomcat & Weblogic servers should reuse home paths from AppServer Configuration?

0

BINGO! Lex you're my man, you always get me :)

Also the drop down for the various configs still point to the setups which you perform in the IDE preferences, and just move all the path, start/stop files, etc... there. No need for all this crazy stuff which we need to setup every time we setup a new web app run config. It's all one time setup. And since we can setup as many app servers as we want, then we can always have different startup scripts for example and just give it a new name. Then when you create your run config, you just pick from a dropdown which configuration you want to run with. Done. Should cut setup time in half at least.

R

0

Lex, I'll add some more options here just to be sure:

1- Click on IDE Settings
2- Click on J2EE Setup
3- This popups the setup window with no app servers.
4- Click + to add an appserver.
5- App Server list window popups up
6- Choose your app server of choice (say it's Tomcat)
7- Go to next screen and there you show:
a- Remote or Local (yes pic it here, and save it that way)
b- Path to Catalina Home
c- Path to Catalina Config
d- Start/Stop Script
e- Paths to load (Not 100% convinced that one belongs here)
8- Save it.
9- If possible add a button to pick an app server you want to be the default app server you use when creating new webapps. (See steps below)
(At this point say you want to setup a new Tomcat instance for remote, we need a copy button to copy the config I setup above to replicate it with a new name, and we need to be able to edit it to change step 7a to remote from local)
Add as many app servers as you want here.

Now say you have a project and you want to setup a webapp run config:
1- Click on edit run/debug config
2- Click webapp tab (yes one tab, no other)
3- Click the + button (no dropdown here please)
4- Create a blank web app with a dropdown menu with a choice of app servers setup in the above steps. If only ONE exists, pick it by default, if there are more than one, and we have an app server checked off to be the default app server, pick it by default.
5- Once the app server is picked by default (Tomcat in this case), then show the Context drop down, and show the webapp list.
6- Pick context
7- Pick webapp to run.
8- Click apply and you're done.
(See how incredibly fast this part is?)

To create a new webapp run config, click + and start the last couple of steps. No need to resetup an app server over and over and over and over.

Thanks
R

0

Please sign in to leave a comment.