Getting Started  

Novell exteNd Workbench
What's New

This page summarizes the new features of Novell exteNd Workbench and includes links to more detailed information in help.

    To get the latest and most complete information on software and hardware requirements for Workbench, see the Release Notes.

 
Top of page

What's new in Version 4.0

Feature Description
jBroker™ Web Workbench now includes Version 2.0 of jBroker Web, which provides the core facilities for developing and running Web Services in the Novell exteNd environment.

    For details on jBroker Web 2.0, see the jBroker Web help.

Web Service Wizard The Web Service Wizard has been enhanced to help you use the new features of jBroker Web 2.0, including:

  • JAX-RPC 1.0 support   jBroker Web now complies with JAX-RPC (Java API for XML-based RPC), the J2EE specification for developing and using Web Services. The jBroker Web compilers, which are invoked by the Web Service Wizard, now generate code based on JAX-RPC.

    When you use the Web Service Wizard, you'll see some changes related to JAX-RPC support:

    • New service interface and implementation classes (xxxService and xxxServiceImpl) generated to help clients access stubs

    • Corresponding modifications to stub access code in the generated client class (xxxClient)

    • New naming convention for the generated stub class (xxx_Stub instead of _xxx_ServiceStub)

    • Option for generating jBroker Web 1.x stubs, client code, and file names (for backward compatibility only)

    • New naming convention for the generated delegate class in a tie-based Web Service implementation (xxxDelegate instead of xxx_SERVICE)

    • Use of JAX-RPC, SAAJ, and other supporting Java API packages in the generated classes

  • XML Schema compiler   jBroker Web now includes the xsd2java compiler, which maps common XML Schema types into JavaBeans with accompanying marshalers (serializers and deserializers). In most cases, xsd2java takes care of all the programming work needed to handle complex types defined in a WSDL file, whether you're developing a Web Service implementation or a Web Service consumer.

    When you use the Web Service Wizard, it automatically invokes this compiler when needed to generate the appropriate type classes and mapping files. (For situations that require exchanging raw XML, an option is provided to turn off this type mapping.)

  • Document or RPC style   jBroker Web now supports both major SOAP message formats:

    • Document/literal/element format where the SOAP message body contains just the XML document being exchanged and message parts map to elements literally defined in the WSDL file's XML schema

    • RPC/encoded/type format where the SOAP message body contains argument and return values, individually wrapped in ad hoc elements that the recipient must interpret by applying specified encoding rules to each message part's type

    When you use the Web Service Wizard to generate a Web Service implementation from Java, it lets you choose one of these styles. When you use the Web Service Wizard to generate a Web Service implementation or consumer from WSDL, the appropriate style is determined from the WSDL contents.

    Support for document or RPC style facilitates interoperability with other Web Service environments (such as .NET, where the style is typically document).

Other enhancements include general usability improvements in the Web Service Wizard and Web Service Wizard Client Runner. Note these specific changes:

  • Project information is now consolidated on a new initial panel of the Web Service Wizard

  • The wizard now supports generating Web Service classes into a JAR subproject while mapping the Web Service's servlet in the parent WAR project

  • Generated files are now named according to a new pattern that is simpler and more consistent

  • For Web Services based on EJB session beans, the wizard now generates a remote interface with just the business methods and a tie delegate class that accesses the session bean (previously, the tie servlet class performed this access)

  • The Workbench Output Pane no longer displays a tab of Web Service Wizard messages

    For more information, see the Web Service Wizard chapter in the Tools Guide.

Undeploying archives You can now use Workbench to undeploy archives that you have deployed. Depending on the deployment server, you can disable and/or delete deployed archives.

    See the chapter on archive deployment in the Tools Guide.

Todo lists You can now maintain Todo lists in Workbench. You can associate Todo items with particular projects as well as maintain items that are independent of projects. In addition, various Workbench wizards and tools generate items in your Todo list to point you to areas where work needs to be done and to describe the nature of that work.

    See the chapter on Workbench basics in the Tools Guide.

XML facilities Workbench provides the following new facilities for working with XML and XML-related files:

  • A built-in XML catalog based on the OASIS standard

  • The following new editing facilities:

    • XML Catalog Editor to create catalog entry files

    • XSL Editor to edit, validate, and test XSL files

    • Schema Guide, which provides enhanced structured editing features

  • The following new wizards:

    • XML Wizard to create an XML file

    • XML Catalog Wizard to create a catalog entry file

    • DTD to Schema Wizard to convert a DTD to an XML Schema

    See the chapter on XML editors in the Tools Guide.

Classpath The Classpath tab in the Project Settings dialog has been generalized to Classpath/Dependencies. In this tab you can specify other projects that the current project depends on. Workbench will build the related projects (if needed) before building the current project.

    See the chapter on projects and archives in the Tools Guide.

Open files The Edit Pane now displays a tab for each open file. Also, there is now a More Documents item on the Documents menu, which displays a list of all open files. Because of these changes, the Open tab in the Navigation Pane has been removed.

    See the chapter on Workbench basics in the Tools Guide.

File operations You can now delete and rename files from within Workbench.

    See the chapter on Workbench basics in the Tools Guide.

Component wizards The Java Class, JavaBean, and Servlet wizards now let you specify interfaces to implement and classes/packages to import.

    See the chapter on component wizards in the Tools Guide.

New File dialog The New File dialog has been reorganized. The Basic tab was renamed J2EE and now includes the deployment items. The XML-related items are now in an XML tab.

    See the chapter on projects and archives in the Tools Guide.

Debugger You can now specify that Workbench launch your own debugger instead of the exteNd Debugger.

    See the chapter on Workbench basics in the Tools Guide.

Image Viewer You can now view .gif, .jpg, .jpeg, and .png files in Workbench.

    See the chapter on Workbench basics in the Tools Guide.

Class Viewer When you open a .class file, Workbench displays information about the file in the new Class Viewer.

    See the chapter on Workbench basics in the Tools Guide.

Subprojects You can now specify that the contents of a subproject not be included in the parent archive.

    See the chapter on projects and archives in the Tools Guide.

Backups during project migration When you migrate a project from J2EE 1.2 to 1.3, Workbench now backs up affected files if you have enabled backup in your Workbench preferences.

    See the chapter on how to handle J2EE versions in Getting Started.

Text editing preferences The Text editing preferences (Edit>Preferences) now apply to all Workbench editors, not just the native editors.

    See the chapter on Workbench basics in the Tools Guide.

Sample J2EE applications Workbench now comes with the J2EE 1.3 version (Version 1.3_01) of the Java Pet Store sample application, in addition to the J2EE 1.2 version (Version 1.1.2).

 
Top of page

What's new in Version 4.0.1

Feature Description
Deployment switches You can now pass switches to the following servers when deploying from Workbench:
  • Oracle9iAS
  • WebLogic
  • WebSphere

In particular, you can pass command-line arguments to the server's JVM and server-specific deployment options to the target server.

BEA WebLogic Server Workbench now supports deployment to WebLogic 7.0 (in addition to 6.x).
Jakarta Tomcat You can now use Workbench to undeploy J2EE applications from a Jakarta Tomcat server. Undeploying deletes the application.
Novell exteNd Application Server When deploying an EAR to an exteNd application server (Version 4.x or higher), you can now deploy a subset of the EAR's modules by passing the -m option to the SilverCmd DeployEAR command.
UDDI Version 2 support The Registry Manager now enables you to access registries that conform to UDDI Version 2.
Debugger's VM usage The exteNd Debugger now runs using the Java classic VM by default instead of the Java HotSpot VM. (HotSpot is known to have problems with debugging.)

 
Top of page

What's new in Version 4.1

Feature Description
Rebranding to Novell As of Version 4.1, this product is branded Novell exteNd Workbench. Earlier versions were branded SilverStream® eXtend Workbench. If you are upgrading from one of those earlier versions, see the Release Notes for details on how this product's rebranding affects you.
Novell exteNd Application Server Workbench now supports deployment to Version 5.0 of the Novell exteNd Application Server. It also continues to support deployment to earlier versions of this server: SilverStream eXtend Application Server 3.7.x and 4.x.

     For details on deployment support, see the Release Notes and the archive deployment chapter in the Tools Guide.

Class structure browser The Navigation Pane in Workbench now includes a Structure tab for examining and navigating the contents (classes, methods, fields) of the currently open Java file.

     See the chapter on Workbench basics in the Tools Guide.

JRE version for compiles The build preferences in Workbench now include a compiler version property for specifying the location of the JRE to use when compiling. This enables you to target an appropriate JRE version of your choice (such as 1.3 or 1.4).

     See the chapter on Workbench basics in the Tools Guide.

Ant The version of Apache Ant provided with Workbench for project builds has been upgraded to 1.5.

     For details on Ant usage in Workbench, see the chapter on Workbench basics in the Tools Guide.

Installation For your convenience, the Workbench CD now includes a JRE installer (for JRE version 1.3.1_06). You can use it if you haven't already installed a JRE that meets Workbench requirements.

     For details on the system requirements of Workbench, see the Release Notes.

Migration Workbench now provides an Update Deployment Plan Version command that you can use to migrate a project's exteNd deployment plan from J2EE 1.2 to 1.3. This command leaves other project characteristics unchanged.

     See the chapter on how to handle J2EE versions in Getting Started.


  Getting Started  

Copyright © 2001, 2002, 2003 SilverStream Software, LLC, a wholly owned subsidiary of Novell, Inc. All rights reserved.