Child pages
  • WOLips bugfix/feature request priorization list

To edit or add content to this Wiki, you can simply create a new account at

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »



Bug "There's something called the "WOLips server", in olden days its purpose was to listen to requests on a certain port, allowing named files to be opened at a specified line number. It stopped working long ago"
Bug Line numbers keep disappearing in WOLips perspective
Bug WOLips reports fake binding errors in large components

In a Maven project, the New > WOComponent dialog does not honour destination folder chosen by right click. To reproduce:

  1. Right click any folder under src/main/components, or even just src/main/components itself.
  2. Observe that you get a "New WebObjects Component" dialog.
  3. Then:
    1. Expected: The "parent folder" tree should be expanded and the folder right-clicked above should be selected.
    2. Observed: The "parent folder" tree is collapsed, and the project's root folder is selected.

I regularly trip over this and end up with a new component in the project's root folder. I've already selected a destination folder, because I right-clicked on it. Additionally, I am reasonably sure this works as intended (that is, the right-clicked folder is shown selected by the dialog) in non-Maven projects.


In a Maven project, new .eogen files for EOGenerator are created with inappropriate default destination paths. To reproduce:

  1. Add a new EO Model in src/main/resources.
  2. Ensure "Use EOGenerator" is checked.
  3. Open the new .eogen file in EOGenerator Editor, then:
    1. Expected: Under Destination Paths, both Destination and Subclass Destination should be "src/main/java".
    2. Observed: Under Destination Paths, both Destination and Subclass Destination are "src/test/resources", which is just completely wrong.

When copying an attribute from one model to another in Entity Modeler, the "Prototype" selection (in the "Basic" tab) is dropped. This wouldn't be a huge deal except that subsequently selecting the prototype that wasn't copied then resets every other relevant field in that form to the prototype's defaults. For example:

  1. Open two EOModels.
  2. Copy an attribute that uses a prototype from an entity in one model to an entity in another—e.g., find (or create) a javaEnum attribute that has a custom enum class in "Value Class".
  3. Then:
    1. Expected: attribute copies over and form fields populated to match source attribute.
    2. Observed: "Prototype" selection is not copied. In the example above, if you select "javaEnum" manually, any enum specified in "Value Class" is now cleared and replaced with "java.lang.Enum".
  • No labels