How to Master MxEclipse in Five Easy Steps

MxEclipse is an open-source development plugin for the Eclipse IDE designed to streamline business modeling and schema management for the Dassault Systèmes ENOVIA / MatrixOne PLM (Product Lifecycle Management) platform. The philosophy of “Getting Better Results Fast” with MxEclipse centers around eliminating the friction of context-switching. Instead of jumping between command-line interfaces and thick clients, developers can perform all data modeling, object query, and code deployments natively within a single workspace. Core Features that Accelerate Development

MxEclipse organizes your PLM workflow into specific IDE views, reducing manual coding overhead:

MxBusiness View (Schema Modeling): This view interfaces directly with Matrix metadata. Developers can view, modify, and build business object schemas natively within Eclipse, cutting down the time spent bouncing back and forth into external administration tools.

MxObject View (Object Handling & Query): Features a dedicated tree-table UI that lets you query and search for Matrix PLM database objects by Type, Name, Revision, or ID.

Fast Expansion: Double-clicking an object fires an “Expand Object” call, revealing all multi-directional relationships and connected objects in a single click.

MxMQL View (Embedded Client): Serves as an integrated Matrix Query Language (MQL) editor. It bypasses the need for external shell clients, supports statement execution without strict semicolon terminations, and tracks execution history via standard keyboard arrows.

MxGraphclipse (Visual Modeling): An extension built on the Eclipse Graphical Modeling Framework (GMF). It generates interactive parent-child diagrams of your live Matrix data model, enabling rapid visual code reviews and schema architecture tracing. Best Practices for Getting “Better Results Fast”

To unlock maximum performance and speed out of MxEclipse, implement these core optimization steps: 1. Eliminate Double-Logins

In your MxEclipse connection properties, check the auto-login options. Bypassing standard credential dialogs is the single fastest way to skip initialization delays when testing localized environments.