7:38 p.m.
I am trying to deploy unmanaged content with the management console on beta1. The runtime
name field is locked but validation fails so it is impossible to deploy unmanaged
content. Should this be a bug against HAL or WildFly and RBAC?
3:31 p.m.
Hi Ben,
If you can do it using the CLI, then file against HAL please. If not, or
you don't have time to experiment, then against WFLY, with component set
to Domain Management.
Heiko and Harald on the HAL team and the folks working on server-side
management stuff are in constant interaction these days, so either way
we can move the issue in JIRA to the right place quickly once we
investigate it.
Cheers,
Brian
On 10/12/13 7:38 PM, Ben Schofield wrote:
I am trying to deploy unmanaged content with the management console
on
beta1. The runtime name field is locked but validation fails so it is
impossible to deploy unmanaged content. Should this be a bug against
HAL or WildFly and RBAC?
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
1:26 a.m.
Thanks Ben,
that's a known issue.
It's already fixed in upstream and the release is scheduled for this week.
On Oct 13, 2013, at 2:38 AM, Ben Schofield <dbschofield(a)yahoo.com> wrote:
I am trying to deploy unmanaged content with the management console
on beta1. The runtime name field is locked but validation fails so it is impossible to
deploy unmanaged content. Should this be a bug against HAL or WildFly and RBAC?
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
4058
days inactive
4059
days old
2 comments
3 participants
participants (3)
-
Ben Schofield -
Brian Stansberry -
Heiko Braun