Middleware.Biz

Connecting the Enterprise


 

             Web Logic Integration Troubles

On first glimpse the web logic integration tool seems very attractive. It lets you develop and deploy web services pretty fast and provides built in controls to hook to external systems through JMS, Databases. It is pretty good for Rapid Application Development (RAD) and prototyping.

 However the trouble starts once you sit down to do some heavy lifting. There are several quirks in the web logic work shop tool. The IDE freezes every so often. Even with a two gigabyte machine the tool is crawling slow.

  The web logic integration tool does not lend itself to object reuse.  The so called "Java  Process Definitions" (JPD) are not object oriented. The do not have a notion of a base and derived objects 

   The IDE tries to synch up the classes as you edit. Some times you have to wait  several  minutes for the IDE to respond after each key stroke.

 Since the tool does not support JPD inheritance, each JPD tends to bloated. It takes inordinate amount of man power to support them. This model does not scale from an IT factory sizing perspective.

 IBM's web sphere got ahead in the game by coming up with  an eclipse based IDE that integrates well with their suite of software development tools.

 It is time for BEA to revamp its WLI workshop.