Enterprise Client Community

Hi everyone,

I tried your attribute macro feature and it really helps enforcing conventions in coding.

Everything works fine. But to help the developer see what attributes the macro brings, those attributes should be displayed in editor. So I copied the macro to the editor webapp:

...\EnterpriseClient\server\tomcat\webapps\editor\eclntjsfserver\config\macros

On startup, the server log tells me that the macro is read, but it is not displayed in the editor for the field (or combofield).

Can anyone tell me what goes wrong here?

Tobias

Could you add the content of the macro to your post?

BTW: the macro is excpected within the application's web application, not the editor's one. Background: the macro is executed in the web application of the application at runtime.

Björn

Hello,

here is the content of my macro definition:

<macro>
<applysto>
<tag name="t:field"/>
<tag name="t:combofield"/>
<tag name="t:password"/>
</applysto>
<parameters>
<parameter name="bean"/>
<parameter name="property"/>
</parameters>
<attributes>
<attribute name="text" value="#{${bean}${property}}"/>
<attribute name="value" value="#{${bean}${property}}"/>
<attribute name="bgpaint" value="#{${bean}props.${property}.bgpaint}"/>
<attribute name="enabled" value="#{${bean}props.${property}.enabled}"/>


</attributes>
</macro>

I more or less took your template and changed it according to our needs (that's why I skip the . between bean and property).

I know that the macro has to be in our web application, that works perfectly fine. The thing is that the developer does not see in the editor what the macro brings (which attributes).

I guess the editor has to know the macro as well to display this information. Or does the information come from our own web application?

Tobias

Tobias,

please use the macro combo field in the footer line of the grid. There the valid values are available. Do not use the one in the normal attribute list.

Björn