[wildfly-dev] Persisting attributes explicitly set to default values

[Tomaž Cerar]

There is also https://issues.jboss.org/browse/WFCORE-836 to change current
behavior
for parsers that are using PersistentResourceXMLParser  /
PersistentResourceXMLDescription

But basically we didn't have any rule about it, at least not in older
subsystems, above jira is result
of discussion we had recently on the topic.

--
tomaz


On Wed, Aug 26, 2015 at 3:24 PM, Darran Lofthouse <
darran.lofthouse at jboss.com> wrote:

> The current approach is to let the attribute definition handle writing
> the attribute and this automatically skips writing if the value is the
> default value.
>
> The legacy web subsystem was written before we had this ability.
>
> On 26/08/15 14:17, Dominik Pospisil wrote:
> > Is there any rule saying if an attribute should be persisted if it is
> > explicitly set to it's default value or not?
> >
> > At least some attributes in the legacy web subsystem are persisted in
> such
> > case and some are not.
> >
> > It seems that the API encourages to choose any of the options. Is there
> any
> > reason for that?
> >
> > Many thanks,
> >
> > - Dominik
> > _______________________________________________
> > wildfly-dev mailing list
> > wildfly-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/wildfly-dev
> >
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20150826/95afffb6/attachment.html