[jboss-dev-forums] [Design of Management Features on JBoss] - Re: JBAS-6672, null values and defaults

[emuckenhuber]

Yeah the uses cases are fine. Although i still think doing managedProperty.setValue(null); should not replace it with a default value.

I guess a default value is also nice for the template generation.
Additionally we should leverage managedProperty.isModified() to skip not modified properties.
So that we dispatch and update only changed values.

Scott, we might want to remove the managedProperty.isRemoved(), managedProperty.setRemoved()?
i think i requested that once, but now thinking about that again it does not make much sense.

So we could provide setModified(boolean) - and setValue() could compare the original value with the new value and also update this flag.
And if needed a flag to indicate to reset the value to the default one. Although i'm not really sure if this is needed, as the template should have populated the default values anyway?

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221743#4221743

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221743