WebLogic Workshop 8.1 included both an application framework and an IDE to support developing enterprise applications using Page Flows, Controls, and annotated web services. This article describes some of the differences between the 8.1 Workshop runtime and the Apache Beehive project.

A J2EE application deployed in the WebLogic server may be debugged in the Eclipse IDE with the remote debugger provided by Eclipse. Without a debugger the error message has to be obtained from the application server error log to debug the application.

It wasn't all that long ago, the last issue of WLDJ if I am not mistaken, that I expressed my dismay over why so few projects in my travels were using WebLogic Workshop as the primary development IDE. And only a few readers sent in e-mails regarding their reasons for choosing another IDE over Workshop - some of which had a lot of merit (actually, all of them did). And, not being too far removed from the subject, I just happen to be on a WebLogic development project where I came in midpoint through development, and - you guessed it - Workshop was not being used.

With Web services usage on the rise, organizations are seeing a growing complexity in the enterprise systems being built. The need for a robust management solution is critical, as organizations look for better ways to monitor and control their IT environment.

This article explores using MySQL as the database engine where the application is developed using BEA WebLogic Workshop 8.1 and deployed to BEA WebLogic Server 8.1. Using an archetypical J2EE architecture, I evaluate the impact of using MySQL from various aspects such as choosing the correct version of MySQL, setting-up the server, and making development adjustments.

MySQL is a small, fast, and efficient database. This article discusses leveraging MySQL as the database with BEA WebLogic Server 8.1. We will look at using MySQL as the database engine where the application is developed using BEA WebLogic Workshop 8.1 and deployed to BEA WebLogic Server 8.1.

You can create a Java Page Flow application in BEA WebLogic Workshop that utilizes a Service control generated from a Web service. This article uses the example of an external Web service listed on the XMethods.net site. We will import the WSDL for the Web service into BEA WebLogic Workshop and see the custom Service control that is generated.

As a software architect and developer, I've used a number of IDEs for my J2EE development. I have my priority list of features that I look for in all the IDEs but I wasn't able to find one that gave me everything I wanted.

BEA WebLogic Workshop 8.1 provides a wide range of tools for creating Web server applications. Components integrated using Workshop's extensible component model include Java controls, page flows, and source and design views that are available to any software vendor or Web application developer.

Web application development is hard. Or rather, Web application development used to be hard. Web application development used to be an activity that required developers to learn and use complex programming models.

The initial focus of Weblogic Workshop was on Web services applications, but the core mission of the Workshop team has always been to deliver unprecedented productivity building enterprise-class applications. Many of the innovations introduced in the first version, such as visual designers, controls to simplify access to resources, and declarative annotations in Java code, apply to many applications, not just Web services.