Save me! Save me from WSAD now!

+1
"Florian Hehlen" <florian.hehlen@ubsw.com> дÈëÓʼþ
news:12200676.1084261695925.JavaMail.itn@is.intellij.net...

hi all.

>

Excuse my humorous subject line. what is not so funny is that it's close

to being true. For those of you who do not know WSAD it stands for WebSphere
Application Developer IDE.
>

Anyways... it really stinks, especially when used in collaboration with

ClearCase! 2 slow, completely un-intuitive tools, that just do not deliver
the basic functionality a developer needs. If that weren't enough... WSAD is
full of unreliable (and sometimes simply buggy) behavior when it comes to
generating deploy code, handling classpaths, and caching what's on the FS!
>

So... I am pleading that JetBrains implements support for WebSphere.

WebSphere developers would probably come rushing to IntelliJ if you did!
>

Florian

+1

Has JetBrains expressed any intention to provide support for WebSphere? Anyone?

Florian

As far as I'm aware, they are opening up the API for the integration so other application servers can be supported.

Whether they'll provide support themselves, or whether someone will then provide a plug-in based on this API is another matter entirely :)

Does anyone know whether the API is already opened in Pallada? Can we start looking at the API to begin writing plug-ins against it?

It's marked as 'fixed' for the next release, but since their build is busted right now we can't get to it. So yes it's open, and no you can't use it yet :)

R

I'm not familar with WebSphere yet, but it seems WebSphere complies JSR 45 specification.
You may try to use JSR45 plugin with WebSphere.

For local debugging you will need build 2053 or later. For remote build 2063 or later.

Note. Usually you should turn on debug mode for the web server to make it generate debugging info.