Working with Java classes

Use WebSphere Commerce Developer to perform the following Java development tasks.


  • Creating and modifying Java classes
    Use the Rational Application Developer tools to create and modify Java classes.
    Tip: By default, saved changes are compiled automatically by the Java builder. If you are running the server in debug mode, it is typically not necessary to restart the WebSphere Commerce Test Server in order for the changes to become visible. For more information, see the "Hot Method Replace" section of WebSphere Application Server debug limitations.
  • Debugging Java classes

    You can set breakpoints in a Java class by double-clicking the left margin next to a valid line of Java code. If you are running the WebSphere Commerce Test Server in debug mode, the execution will stop when it reaches a breakpoint. You can then use the Debug perspective of Rational Application Developer to perform debugging tasks such as stepping through code and examining variables.

  • Adding new Java projects

    Although new Java classes intended for use as data beans, command beans, or helper classes should be created within the WebSphereCommerceServerExtensionsLogic project, you can use the New Project wizard of Rational Application Developer to create new Java projects. If you create a new Java project, ensure you add the new project as a Project Utility JAR file in the WC enterprise application's deployment descriptor. Edit the MANIFEST.MF of the Stores project (or any other Web project) and add newproject.jar to the line beginning Class-Path:. For more information, see Importing external application code.