----- Original Message -----
From: "Bill Burke" <bburke(a)redhat.com>
To: keycloak-dev(a)lists.jboss.org
Sent: Tuesday, 19 May, 2015 4:04:17 PM
Subject: Re: [keycloak-dev] Why does WildFly CLI suck?
CLI is a UI. Generically rendered UIs generally suck. For example, did
not managing JBoss 4.x and earlier suck using some generic JMX UI
renderer? CLI falls into this category IMO.
+1 I've never been able to achieve anything without googling for a recipe
The fact that there's alternative commands for doing common tasks suggests that
I'm not the only one. For example adding a data-source can be done with:
/subsystem=datasources/data-source=MigrateDS:add(jndi-name=java:jboss/datasources/MigrateDS,
pool-name=MigrateDS, driver-name=h2, connection-url=jdbc:h2:mem:test;DB_CLOSE_DELAY=-1)
or
data-source add ...
The first auto-generated one is very hard to use, the whole syntax of the cli is weird in
the first place and figuring how to puzzle that together is hopeless. The last one is much
better, but there's very few of those easy to use commands available.
On 5/19/2015 9:42 AM, Stan Silvert wrote:
> I've probably been too involved with it to be objective. What are the
> usability issues?
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
>
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev