Eclipse Community Forums: Plugin Development Environment (PDE)

Help

Home

Home » Eclipse Projects » Plugin Development Environment (PDE) » "No property tester" CoreException

Show: Today's Messages :: Show Polls :: Message Navigator

"No property tester" CoreException [message #757345]

Thu, 17 November 2011 20:34

Mark Walters

Messages: 25
Registered: June 2011

Junior Member

Hi,
In our main project explorer view (a custom CNF view), if I right click and choose 'properties' for one of our folders (they're virtual but do adapt to resources) I get the properties dialog and it seems fine but I get a trace:

No property tester contributes a property org.eclipse.core.resources.contentTypeId to type class org.eclipse.core.internal.resources.Folder

I see scant references to this on the web - any ideas what's causing it?

Is it our 'propertyTesters' extension point? The class implementing that?

Any ideas would be great.

Thanks,
Mark.

Report message to a moderator

Re: "No property tester" CoreException [message #757490 is a reply to message #757345]

Fri, 18 November 2011 16:03

Curtis Windatt

Messages: 166
Registered: July 2009

Senior Member

Property testers are contributed via the org.eclipse.core.expressions.propertyTesters extension point. They specify one or more properties they can an object for. In your case something is testing a folder for the contentTypeId, but the property tester is missing. I don't know whether that is a property tester provided by you or the platform.

Report message to a moderator

Re: "No property tester" CoreException [message #757755 is a reply to message #757490]

Mon, 21 November 2011 13:57

Mark Walters

Messages: 25
Registered: June 2011

Junior Member

Hi Curtis,

thanks for this. I've added a property tester for the folder type, like this:

<propertyTester
id="xx.xx.xx.folderTester"
type="org.eclipse.core.internal.resources.Folder"
namespace="org.eclipse.core.resources"
properties="contentTypeId"
class="xxx.xxx.xxx.typeTester">
</propertyTester>

where the 'typeTester' class just throws away the contentTypeID property.

This stops the exception but perhaps doesn't explain the original problem.

Still, the defect was moaning about the exception, not any missing function, so job done AFAIK.

Ta,
Mark.

Report message to a moderator

Previous Topic:	PluginRegistry.getActiveModels() doesn't work properly
Next Topic:	parse and read data to/from existing editors

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Wed Sep 25 01:06:18 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter