I love the new console, congratulations!  

Should the new application deployment view (Content + Management Model), order be reversed or will users look at Content more often than Management Model?  The first item should probably be whatever is looked at more often, hard to know what that is but personally I prefer to see the Management model first and Content second. :)

I tried to edit the JPA enabled (equivalent of issuing :write-attribute(name=enabled,value=true)) flag for a deployment persistence unit but wasn't quite sure what to do after choosing the 'edit' option.  I tried entering 'true' in the edit control but didn't know what to do to accept the change.  I figured out to press the little Oo control but that gives me an invalid expression error, pressing help on that, shows: "The expression as ${key} or ${key:default} Required field."


On Thu, Apr 19, 2018 at 9:12 AM, Claudio Miranda <claudio@claudius.com.br> wrote:
Hi, just to let you know, HAL 3.0 is already merged in wildfly master
branch, so you may run it and give some feedback.

On Fri, Mar 2, 2018 at 6:29 AM, Harald Pehl <hpehl@redhat.com> wrote:
> The development of HAL.next [1] has reached a point where we can replace the
> existing console with HAL.next. We'd like to make this transition for
> WildFly 13.
> HAL.next ships with everything which is available in the current console.
> In addition there are plenty new and enhanced features. I'm currently
> preparing a website which will include basic user documentation and a list
> of new and enhanced features.
> Although we believe the new console is stable enough, we could add an
> additional endpoint in WildFly 13 for the old console. This would enable
> users to switch back and forth between the new and old console.
> What do you think?
> .: Harald
> [1] https://github.com/hal/hal.next

  Claudio Miranda

wildfly-dev mailing list