Wishful thinking: WebSphere integration

I know WebSphere integration is planned for Demetra, so here's my really long list of features I wish to see:

- Do everything WSAD/RSDP does, so I can dump them.

That's it. Really long, eh? Okay, I'll expand a little: IDEA needs to take care of server (and test environments) configuration and deployment, even if WSAD has to be installed for that. I want to be able to create a new server, select the runtime environment, edit the server configuration, generate the deployment code, and run the server.

I won't get much into this, really -- if you want to be serious about WebSphere integration, you need to use WSAD for a while, and make sure IDEA is an apt replacement. Currently you just -can't- develop to WebSphere without WSAD, and if IDEA could help me stop using them, it would be great.

Again, I don't even mind if IDEA requires me to have WSAD installed to make use of the bundled runtime environments. Any company stupid enough to use WebSphere gets free WSAD licenses anyway.

4 comments
Comment actions Permalink

I tried the WebSphere integration in Demetra with WSAD and it didn't work quite right. I wasn't really expecting it to since I'm sure it was built to handle a standalone websphere instance. But yeah, if they could support WSAD too, that would be awesome.

0
Comment actions Permalink

Even when targeting a standalone installation, the current level of integration is very awkward -- for example, it doesn't automatically generate EJB deployment code.

0
Comment actions Permalink

- Do everything WSAD/RSDP does, so I can dump them.


Tip: be wise on what you are gonna replicate, or you risk producing the same amount of crap WSAD/RAD currently is.

IDEA needs to take care of server (and test

environments) configuration and deployment, even if
WSAD has to be installed for that.


Well, see no reason to have WSAD installed if you have a standalone WAS anyway.

I want to be able

to create a new server, select the runtime
environment, edit the server configuration, generate
the deployment code, and run the server.

That is possible today, though you must be prepared to learn some WAS scripting magic :)

Currently you just -can't- develop to

WebSphere without WSAD,


I'm sorry, but this is not true. These are almost 2 years of practice developing in IDEA for WebSphere speaking up in me..

Now, think why you dislike WSAD and address those, do not replay all its traits/bugs. If you really dig into the management API for WebSphere (some JACL or Jython scripting through wsadmin here), IDEA only needs to bundle those in a GUI (config params). Given that Ant tasks are already available for calling those it's mostly scripts and GUI that's left.

0
Comment actions Permalink

Tip: be wise on what you are gonna replicate, or you
risk producing the same amount of crap WSAD/RAD
currently is.


Word. When I said that, I was referring to the bits concerning WebSphere integration -only-.

Well, see no reason to have WSAD installed if you
have a standalone WAS anyway.


True. It's just that in a large WebSphere shop, everyone will have WSAD installed on their machines, but few people will have a standalone WebSphere installation. Nothing big, thou.

That is possible today, though you must be prepared to
learn some WAS scripting magic :)


I know, I know, and that's a pain in the ass. I've tried to write some scripts, but they're slow as hell, compared to what WSAD does (which isn't exactly blazing fast to start with).

I'm sorry, but this is not true. These are almost 2
years of practice developing in IDEA for WebSphere
speaking up in me..


I'd be glad if you could share some of your experience. I've been working on a WebSphere shop for a couple months now. I couldn't get rid of WSAD, and have to keep both IDEA and WSAD open, at best (and that introduces some quite synchronization problems).

0

Please sign in to leave a comment.