[wildfly-dev] Need write to standalone.xml after parsing
James Perkins
jperkins at redhat.com
Wed Aug 3 15:58:20 EDT 2016
On Wed, Aug 3, 2016 at 6:53 AM, Stan Silvert <ssilvert at redhat.com> wrote:
> The Keycloak server is currently configured via a keycloak-server.json
> file. We are converting this to configuration through
> standalone.xml/domain.xml.
>
> To automatically upgrade, I need to read keycloak-server.json and write
> back to standalone.xml. I can easily add the operations to do this at
> parse time. The parser has this method:
>
> @Override
> public void readElement(final XMLExtendedStreamReader reader, final
> List<ModelNode> list) throws XMLStreamException
>
Reading an external resource from the subsystem parsing doesn't feel right
to me. Is the goal to move away from the keycloak-server.json to using the
management model?
If that is the goal then a better solution might be to have some sort of
migration operation that would read the file and create the subsystem
model. Then after that the keycloak-server.json is ignored and the *.xml
file will be used.
>
> So one way to do this is to parse keycloak-server.json at this time and
> add operations to the list.
>
> That puts everything into the management model. But nothing will be
> written to standalone.xml unless someone manually does a write operation
> from CLI.
>
A write will be triggered if you make a change to the management model.
>
> So my question is, what is the best way to accomplish this? Is there a
> good, safe way to manually trigger a flush to standalone.xml at this
> point or at some later point during startup?
>
Not really an answer, but I hope there is not a way to trigger a write :)
>
> Stan
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
--
James R. Perkins
JBoss by Red Hat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20160803/1234826f/attachment.html
More information about the wildfly-dev
mailing list