Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

when WOComponent error occurs from EO change, cannot clear the error #83

Open
rkiddy opened this issue Feb 9, 2012 · 0 comments
Open

Comments

@rkiddy
Copy link
Member

rkiddy commented Feb 9, 2012

When I want to add a new attribute to an EO, I may start by adding a wo:str on a page I am working on with that attribute as the value. Then I put in the method or the column or whatever.

When I am adding a method to a component class, this works fine. You save the java file, the WOComponent updates itself when you navigate to it, or you might have to select Refresh on the WOComponent. And the WOComponent error is cleared.

If I am changing the EO and re-running EOGenerate, the error marker stays in the WOComponent. If I run the app, it works fine, so the problem is not a real one. But the WOComponent will continue to have the error marker.

I can click on the WOComponent and select Refresh from the context menu. The WOComponent does not clear the error.

I can clean the project. The project is then re-built. Then I can click on the WOComponent and select Refresh from the context menu. The WOComponent does not clear the error.

I can close and open the project. Then I can clean the project. The project is then re-built. Then I can click on the WOComponent and select Refresh from the context menu. The WOComponent does not clear the error.

I can clean the project, close the project, quit Eclipse, then re-launch Eclipse, then open the project and then re-fresh the WOComponent. Now, the WOComponent error is cleared.

Wow. What a PITA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant