mockcentral / News: Recent posts

All MockCentral components have been substantially enhanced for release 2.0.0. New array, enum and constant value types, constructor arguments for instance and throwable value types, streamlined Mock Object and method expectation creation using new multi-step wizards and many more new features make using MockCentral significantly more powerful and efficient than ever before.

This release addresses a problem that caused the editor not to load properly in recent Ganymede versions of Eclipse, and was due to a change in the code within the org.eclipse.jdt.internal.core.JavaModel class.

These new releases work together to enable the definition of simple (non-Mock) Objects that will be bound in the NamingContext when a Fixture's Mock Object proxies are loaded by calling the server's "bindFixtureProxies" method.

Removed code (a bug) that prevented specifying primitive int return types for method expectations.

These releases work together to enhance the ui by allowing the user to select fully-qualified class names (for mock object interfaces, new Object instances and Throwable method expectation results) from a list generated after the user has entered a non-fully-qualified class name. As before, the core library is included with the plugin, it does not require a separate download.

This release contains a new classloading mechanism for locating interfaces to mock and classes to use as method parameters and return types and should solve any "Class not found" problems previously encountered. Essentially, any class on the build path of the java project containing the Mock Central configuration file is now accessible to the classloader. That includes classes from other projects, internal and external libraries and class folders, variables, etc.

These releases contain updates to the classloading mechanism to allow editors to find classes defined in an Eclipse workspace. The editor-core library now allows a fully "pluggable" classloader for finding interfaces to mock or classes used for new "instance" value types. The Plug-in now supplies a classloader that uses the jdt api for loading classes defined in the workspace.