Yes that would be a problem.  Mainly I'm trying to think of an alternative solution that doesn't involve a custom syntax though. Maybe a special variable called "default" could be used e.g. `${foo.bar:${default}}`? Is that too convoluted?

On Thu, Sep 9, 2021 at 6:23 AM Michal Petrov <mpetrov@redhat.com> wrote:

It's not, the attribute definition method would still have to be changed. But it would no longer be possible to set the attribute value to an empty string using this expression, isn't that a problem?

On Tue, Sep 7, 2021 at 6:55 PM David Lloyd <david.lloyd@redhat.com> wrote:

I think the proposed functionality should already mostly be present, as you can supply an empty default value. For example "${foo.bar:}" will not throw an exception if `foo.bar` is missing but rather return an empty string. Is an empty string sufficient to yield the default value of an attribute?

On Tue, Sep 7, 2021 at 11:32 AM Michal Petrov <mpetrov@redhat.com> wrote:

Hi,

I'm looking for feedback on my issue - https://issues.redhat.com/browse/WFCORE-5339, analysis document at https://github.com/wildfly/wildfly-proposals/pull/423

Thanks,

Michal

_______________________________________________
wildfly-dev mailing list -- wildfly-dev@lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave@lists.jboss.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

--

- DML • he/him

--

- DML • he/him