Note that there are some explanatory texts on larger screens.

plurals
  1. POCreating own scaffold plugin: metawidget resource loading exception only when run within forge console
    primarykey
    data
    text
    <p>I try to rebuild a scaffold faces plugin separately for some reasons, but found a really annoying bug, that I cannot solve.</p> <pre><code>java.lang.NoSuchMethodException: class org.metawidget.inspector.impl.BaseObjectInspectorConfig.setPropertyStyle(ForgePropertyStyle). Did you mean setPropertyStyle(PropertyStyle)? at org.metawidget.config.impl.BaseConfigReader$ConfigHandler.classGetMethod(BaseConfigReader.java:1633) </code></pre> <p>After trying some tricks, review the metawidget config codes, not found how to solve the problem.</p> <pre><code>scaffold setup --scaffoldType customfaces </code></pre> <p>works fine, but the</p> <pre><code>scaffold from-entity com.domain.entity.* --scaffoldType customfaces </code></pre> <p>fails.</p> <p>Is anybody has a same issue? May I mess-up something?</p> <hr> <p><strong>Update#1</strong>:</p> <p>The resource loading fails only, when run within forge console. JUnit test works fine. I assume, that metawidget plugin resource loader try to load metawidget-*.xml not from the new plugin but from the original scaffold-api's context. </p> <p><strong>Update#2</strong>:</p> <p>The problem is somewehere deep in metawidget and forge relation. I found that if I use directly the <code>SimpleResourceResolver.openResource()</code>, the result is valid. But If I add the <code>StaticHtmlWidget.setConfig()</code>, the result is <code>Unable to locate com/domain/customfaces/metawidget-entity.xml on CLASSPATH</code> at the firs <code>write()</code> call. I have no idea, how to resolve this behavior.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload