Unable to use XinhaNodePlugin on a different nodetype

For my project I tried to create a different nodetype ( custom:html ) that also uses the XinhaNodePlugin. My custom:html node has custom:content as a property. I tried to do this because I did not want the richt text content to end up in the lucene index. If I use the normal hippostd:content I would exclude all other rich text fields.

The patch I provided changes the access modifier of the getContentModel method to protected instead of private, which means you would only have to override this method with your extended XinhaNodePlugin. The getContentModel now uses a fixed property name. Maybe it would even be nicer to have it configurable from the plugin config, but for now this should not break backwards compatibility.

The thing now is that I have to fork the entire class to get this to work.

My new nodetype looks like this:

[common:customhtml] > nt:base

• common:content (string) primary mandatory
  + * (hippo:facetselect)