Giter Site home page Giter Site logo

wolips's People

Contributors

avendasora avatar darkv avatar dependabot[bot] avatar fbarthez avatar getsharp avatar hprange avatar hugithordarson avatar johnthuss avatar lbane avatar maiksd avatar markusstoll avatar nullterminated avatar nur-sgaertner avatar qdolan avatar spelletier avatar swklein avatar wolfy42 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

wolips's Issues

OGNL and static variables

The code completion for static variables in OGNL notation does not work. By typing

tag="~@

and hitting the code completion key only local ivars/methods are displayed though this should show a list of possible java classes. After typing manually the full class name and another "@" there should be a list of all static ivars and methods of that class but again only the local ivars/mehtods show up. These OGNL expressions don't get validated either. Putting a typo into the class name or ivar name doesn't show up as error until runtime.

[PATCH] renaming a component leaves old java class name in api file

In Eclipse using Refactor->Rename WOComponent... renames the .wo file and its subfiles, the related java class and the optional api file.

The api file contains also the name of the java class that is not updated and thus points to the old class file. The contents of an api file begins with:

<?xml version="1.0" encoding="UTF-8"?>
<wodefinitions>
        <wo class="WOComponent_name.java" wocomponentcontent="false">
[...]

The patch is available at http://www.oyosys.com/dl/rename_wocomponent.patch

WOL-973 Validation for Owns Destination

Reported by David Avendasora

Trigger a validation error for setting Owns Destination on a relationship where the inverse relationship is optional. This should be impossible.

I think the only acceptable Delete Rule is "Cascade" when "Owns Destination" is selected. Maybe "Do Nothing" is acceptable too, but I don't think so. I think "Owns Destination" is basically another way of saying "Cascade Delete Related Objects when the inverse relationship (if it exists) is set to null"

WOD binding validation should check for setters as well as getters where dynamic elements require setter [WOL-684]

The following bindings require setter as well as getter. Currently the validation only checks for getter.

WOCheckBox: selection, checked
WOCheckBoxList: item, index
WOFileUpload: data
WOHiddenField: value
WOPasswordField: value
WOPopUpButton: item, value, selection
WORadioButton: selection, checked
WORadioButtonList: item, index, selection
WORepetition: item, index
WOText: value
WOTextField: value
WOTable: item, index
WOCheckBoxList: item, index, selections
WOCheckBoxMatrix: item, selections

WOL-1183 Add ability to copy default EOGenerator templates to project

Reported by David LeBer

It would be really nice if there was an option in the EOGenerator Editor to be able to copy/update the current default templates into the the project. i.e: If you have a relative Templates Folder defined, there would be a "Copy Default Templates" button that would copy WOLips' default templates into the it.

WOL-962 Warn on foreign key/primary key type mismatch in Entity Modeler

Reported by Michael Sharp

Wonder recently started throwing runtime exceptions in the case of a foreign key type not matching the target type, eg:

"java.lang.RuntimeException: The attribute personId in Person (java.lang.Number, i) is a foreign key to personId in Role (java.lang.Number, l) but their class names or value types do not match. If this is actually OK, you can set er.extensions.ERXModelGroup. Person.personId.ignoreTypeMismatch=true in your Properties file"

It would be helpful to have warnings raised in Entity Modeler to highlight these cases.

WOL-668 Entity Modeler should prevent usage of reserved keywords

Reported by Johann Werner

Would be nice if Entity Modeler would prevent or at least show a warning if someone uses a reserved keyword for entities/attributes.

I mean names that conflict with database keywords as "select", "alter", ...
These two are apparent to be bad names for a model but some may be not and these could be potentially a source of error in SQL execution.

I had one case some time ago where I had a conflicting name in FB (I think it was using "User" for a table name) and I had some erratic behaviour (I had never to do with SQL before so it took quite some time to get hold of the error).

Had an eomodel with an attribute 'left' that caused an exception during migrations for postgresql. Same thing for 'right'.

Caused by: org.postgresql.util.PSQLException: ERROR: syntax error at or near "left"

Reformat HTML deletes CDATA [WOL-1191]

I have the following in the WOComponent html file

<?xml version="1.0" encoding="UTF-8"?>
<soap-env:Envelope xmlns:soap-env = "http://schemas.xmlsoap.org/soap/envelope/">
  <soap-env:Body>
    <eg:example xmlns:eg = "http://example.com" >
      <![CDATA[my <b>html></b> snippet]]>
    </eg:example>
  </soap-env:Body>
</soap-env:Envelope>

After I select menu item Edit -> Refactor -> Format (cmd-shift-f) I get

<?xml version="1.0" encoding="UTF-8"?>
<soap-env:Envelope xmlns:soap-env = "http://schemas.xmlsoap.org/soap/envelope/">
  <soap-env:Body>
    <eg:example xmlns:eg = "http://example.com">
    </eg:example>
  </soap-env:Body>
</soap-env:Envelope>

Note that the CDATA has been completely deleted. I would expect the CDATA to be left untouched by the reformat process.

WOL-1075 Related view does not display wod, woo and html for every localization

Reported by Ralf Schuchardt

In the past the "Related" view did show for every localization the *.html, *.wod and *.woo files.
This is apparently not the case anymore, instead only one instance of every such file is displayed.

(On the other hand every localization of a *.wo folder still gets its entry in the view.)

WOL-898 It's not possible to create a Component on the project root

Reported by Miguel Arroz, and somewhat related to issue 42.

When I try to create a component on the project root, clicking on the Finish button (in the New WebObjects Component window) does nothing, the window remains visible and no component is created. I must click on Cancel to close the window.

Here's the stack trace that shows on error log:

java.lang.IllegalArgumentException: Path must include project and resource name: /Survey
at org.eclipse.core.runtime.Assert.isLegal(Assert.java:64)
at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:1628)
at org.eclipse.core.internal.resources.Container.getFolder(Container.java:137)
at org.objectstyle.wolips.wizards.WOComponentCreationPage.createComponent(WOComponentCreationPage.java:436)
at org.objectstyle.wolips.wizards.WOComponentCreationWizard.performFinish(WOComponentCreationWizard.java:87)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:742)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:373)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1561)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1585)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1570)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1360)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3474)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3064)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.ui.internal.actions.NewWizardShortcutAction.run(NewWizardShortcutAction.java:135)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1561)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1585)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1570)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1360)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3474)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3064)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)

WOL-1047 Wonder App template: Set er.extensions.ERXApplication.DefaultEncoding=UTF-8 by default

Reported by Timo Höpfner

The default encoding of new wonder apps should be set to UTF-8. Shouldn't change much for the english speaking world and would make the life of the remaining "minority" easier in most cases.

Please add the following to the Properties template:

This is the one-stop-shop for setting the default encoding everywhere.

When in doubt, set this one.

er.extensions.ERXApplication.DefaultEncoding=UTF-8

Creating a new component don't add it to Components folder by default

If you right-click on the project name or any folder and you select New -> WOComponent, the folder where the component will be added in the selected folder. For example, if you right-click on Resources, the component will be created in the Resources folder. It would be best to make the default folder to be the Components folder.

New -> EOModel already do that (e.g. no matter where you try to add a EOModel, it's the Resources folder who is selected by default), New -> WOComponent behavior should be similar.

Delete a component in one step

Renaming a component can be done in a single step by right-clicking the component wo- or api-file and choosing Refactor->Rename WOComponent. It would be nice to have an additional menu item to delete a complete component, that is the wo-, api- and java-file, in one step. Now every file has to be manually deleted.

change occurrences of component name when renaming a component

Using Refactor->Rename WOComponent there should be an option like "Update textual occurences in comments and strings" from the standard Eclipse renaming dialog where you can check to search e.g. your wod files for the old component name to rename those occurences too.

Deprecation in component editor

The component editor should show a warning when a binding refers to a method / variable that has been marked as deprecated.

Exception when trying to build relationship on missing PK on one of the entities

If you try to join two entities together but one of the entity don't have a primary key, the following exception will be raised when you click OK.

org.eclipse.core.commands.ExecutionException: While executing the operation, an exception occurred
at org.eclipse.core.commands.operations.DefaultOperationHistory.execute(DefaultOperationHistory.java:521)
at org.objectstyle.wolips.eomodeler.editors.entity.CreateRelationshipDialog.okPressed(CreateRelationshipDialog.java:568)
at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:472)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.objectstyle.wolips.eomodeler.actions.NewRelationshipAction.run(NewRelationshipAction.java:77)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
Caused by: java.util.NoSuchElementException
at java.util.LinkedHashMap$LinkedHashIterator.nextEntry(LinkedHashMap.java:375)
at java.util.LinkedHashMap$KeyIterator.next(LinkedHashMap.java:384)
at org.objectstyle.wolips.eomodeler.core.model.EOEntity.getSinglePrimaryKeyAttribute(EOEntity.java:441)
at org.objectstyle.wolips.eomodeler.core.model.EOEntity.createForeignKeyTo(EOEntity.java:446)
at org.objectstyle.wolips.eomodeler.actions.NewOneToManyRelationshipOperation.execute(NewOneToManyRelationshipOperation.java:79)
at org.eclipse.core.commands.operations.DefaultOperationHistory.execute(DefaultOperationHistory.java:513)
... 47 more

WOL-742 EOGen UI should use radio buttons for Java and Java Client options

Reported by David Avendasora

In the EOGenerator Editor, change the "Java" and "Java Client" options to be a radio-button set as only one or the other should be selected because each requires different templates so one run of Veogen cannot be for both, and it has to be for at least one, defaulting to "Java" (obviously :)

Opening a localized component always open the same tab

If you use localized component (Main.wo in Chinese.lproj, Main.wo in English.lproj, etc.), no matter which component you are opening, the tab in Component Editor is always the same. For example, the HelloWorld example from Apple have components in Chinese, French, German, Japanese and Spanish. If I double-click on Main.wo in Chinese.lproj, it's the Spanish tab that opens. Same thing if I open the component in French.

In summary, when you open a localized component, the tab in Component Editor should be the selected component.

WOL-567 Problems when renaming a project

If I try to rename a WO project (created as a "Wonder Application") and I rename the project with "Refactor -> Rename...", the following problems appears :

  • The run configuration still have the old name
  • in the run configuration -> Arguments -> Working directory, the "Other" radio button is set (this is the default ?) and the variable still have the old name. Example, I renamed my project "JoeNothing" to "JoeBlow" (don't worry about the name, it's French-Canadian thing) and the variable is set like this :

${working_dir_loc_WOLips:JoeNothing}

  • the build.properties file still have the old name

project.name = JoeNothing
project.name.lowercase = joenothing

  • the project name in build.xml is the old one :

WOL-1122 Entity Modeler's userInfo dictionary editor won't allow types other than String

Reported by Paul Hoadley

To reproduce:

  • Create a test project.
  • Create an EOModel.
  • Open the model in Entity Modeler.
  • Add an entity.
  • Select User Info tab.
  • Select Root, hit return to get "New Key 1" key.
  • Change the type drop-down to Boolean for "New Key 1".
  • Enter "true".
  • Select the Basic tab.
  • Re-select User Info tab.
  • Observe that type for "New Key 1" is now "String". (Expected behaviour: "New Key 1" would still be of type Boolean.)

Same happens for other data types: try Number as well.

WOL-718 Binding with slashes in key path breaks validation

When using binding with slashes in them, like this:

String1: WOString {
value = @urlPourResource.images/entete_bgrnd.jpg;
}

Component Editor will complain with the following errors:

Description Resource Path Location Type
There is no key '' in Main Main.wod /Test2/Components/Main.wo line 1 WebObjects Template Problems

WOLips HTML editor templates don't work

In the WOLips preferences you can define templates for the HTML editor (Preferences->WOLips->HTML Editor->Code Assist->Templates). Clicking on the button 'New...' produces neither a change nor an error.

Component editor is confused by escaped backslash

If you have a binding with a text value and want a backslash to appear on the final html you have to escape that backslash with another one:

<wo:textfield value="$aValue" onkeyup="if(/^.*\\w+.*$/.test(this.value){ alert('character found'); }" />

The component editor then shows lots of errors stating "<..> start tag is not found." for all following tags that are not self-closing.

WOL-966 Can't add WO framework in Classpath of debug configuration

Steps to reproduce:

  • Edit a debug configuration
  • Open the "Classpath" tab
  • Click "Advanced"
  • Click "Add Library"
  • Select "WebObjects Frameworks"

Clicking "Next" do nothing, and trying to add another type of library will result in a NPE. If you come back and try to add another type of library, it works fine.

Issues with opening the Entity Modeler perspective

"Open Entity Modeler in a new window" was selected in my setup, and to check up a reported issue on Jira, I unchecked that option. Alas, now Entity Modeler open in the main window with my model, but a blank Entity Modeler window is also opened.

The other issue is a bit similar. If you check "Open Entity Modeler in a new window" and you close Eclipse while having a Entity Modeler opened, when you start back Eclipse, the Entity Modeler window with the model will open, that's fine, but a blank Entity Modeler window will also open.

WOL-1092 Entity Modeler - Relationship Wizard NPE when you don't select a destination entity

Reported by John Huss

Entity Modeler - Relationship Wizard NPE when you don't select a destination entity

Steps to reproduce:

  1. Select an entity
  2. Click the new relationship button
  3. Click OK without selecting a destination entity

org.eclipse.core.commands.ExecutionException: While executing the operation, an exception occurred
at org.eclipse.core.commands.operations.DefaultOperationHistory.execute(DefaultOperationHistory.java:519)
at org.objectstyle.wolips.eomodeler.editors.entity.CreateRelationshipDialog.okPressed(CreateRelationshipDialog.java:568)
at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:472)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1561)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1585)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1570)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1360)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3482)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3068)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.objectstyle.wolips.eomodeler.actions.NewRelationshipAction.run(NewRelationshipAction.java:79)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:229)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500)
at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:452)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1561)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1585)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1570)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1360)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3482)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3068)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2384)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2348)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2200)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:495)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:490)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
Caused by: java.lang.NullPointerException
at org.objectstyle.wolips.eomodeler.core.model.EOEntity.createForeignKeyTo(EOEntity.java:421)
at org.objectstyle.wolips.eomodeler.actions.NewOneToManyRelationshipOperation.execute(NewOneToManyRelationshipOperation.java:79)
at org.eclipse.core.commands.operations.DefaultOperationHistory.execute(DefaultOperationHistory.java:511)
... 46 more

WOL-908 Display connection information in generate SQL window

It would be nice if the modal window that is displayed when you click generate SQL for an EOModel displayed the connection information that it is going to fire the SQL against. It always makes me a little nervous when firing it :-)

(That information is show when you have more than one database config).

add autocompletion for pagename-bindings in component editor

When defining the API for components you can set the value set of a binding to 'Page Names'. It would be really cool then to get an autocompletion in the component editor for that binding like there is for the 'wo:...' part of tags by showing a drop down with all possible component names.

Bug with WOLips.framework and WOLips 3.7

While trying out all templates, I found that the Wonder D2W App template won't launch the app because of this exception:

[2011-9-18 22:54:59 EDT]

A fatal exception occurred: ERXExtensions have not been initialized. Please report the classpath and the rest of the bundles to the Wonder mailing list:
Remaining frameworks: [WOLips]
Classpath:
..

at er.extensions.appserver.ERXApplication.<init>(ERXApplication.java:1056)
at your.app.Application.<init>(Application.java:10)

If I remove WOLips from the list of frameworks, it works fine. Now, if I open the WOLips framework project in Eclipse, the problem goes away. If I use WOLips 3.6, problem goes away too.

So this exception arises when you use WOLips 3.7 with the build WOLips.framework. I also tried to revert the WOLips 3.7 code base to the first commit for 3.7, and I get the same problem. David Holt reported the same problem.

"Add key" does not generate correct java source code is second character of key is upper case [WOL-774]

This issue is WOL-774 from Jira. The behavior has changed since first described in Jira but is still wrong. I am describing the new wrong behavior below.

If my WOD file contains

MyString: WOTextField {
    value = aString;
}

and I cmd-click on "aString" to generate the java source code, I get the source code below. Note that the setter method should be "setAString" not "setaString". This problem only occurs if the second character of the key is upper case!

    private String _aString;

    /**
     * @return the aString
     */
    public String aString() {
        return _aString;
    }

    /**
     * @param aString the aString to set
     */
    public void setaString(String aString) {
        _aString = aString;
    }

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.