At the moment we have a lot of effort going into populating the
wildfly-proposals repository with the proposals for new features as they
are added to the application server - but at the end other than them
sitting in the repository we don't really do anything with them.
I was wondering if we could maybe do something to add a table of contents
per WildFly release cross referencing the proposals added in that release
and at the end we could generate publishable documentation.
This could give us some quite detailed release notes without a huge amount
of additional effort taking advantage of the effort that goes into writing
these in the first place.
SnapshotRestoreSetupTask is a nice testsuite convenience, but it needs to
be used with great care.
What it does is save you the hassle of writing cleanup code to revert any
configuration changes your test makes. It saves a snapshot of the xml
config before your test runs and then when the test class is done reloads
the server using that snapshot. Voila, all config changes magically gone!
But like all dark magic, there's a hidden cost.
The problem is reloading to an earlier snapshot is not the same thing as
executing management ops to reverse out changes. Management ops don't just
change the model, they change runtime resources, and those runtime resource
may persist state outside the xml file, e.g. in the data dir. A management
op like a 'remove' may result in that persisted state being cleaned up, but
a simple reload to a snapshot will not. And that leftover state may have
mysterious side effects later.
The messaging-activemq subsystem seems like a place to be particularly
Manager, Senior Principal Software Engineer
I have a web frontend application that is communicating with a beckend REST
service. I would like the web frontend to automatically
authenticate/authorize with the REST services by including the username and
roles of the authenticated user as HTTP headers in the REST call. I found a
wildfly quickstart (http-custom-mechanism) which allows me to the
authentication part. However, I haven't not been able to figure out how to
provide the roles in the same fashion. In the case of the quickstart I
mentioned, it would be something like adding an additional HTTP header to
the curl call, like so:
which would result in the user being assigned the "admin" and "ops" roles
in the REST service.
Does anyone have any pointers on how I can do this?
Thanks in advance.
This may not be exactly the right forum / audience to ask this question, and if so please accept my apologies in advance. That being said, I need to understand what actions or events inside of Wildfly / Undertow are recognized as valid activity relating to the session timeout. I'm battling some issues in a web application where a user is doing legitimate actions via ajax that are being processed through wildfly, but they still end up getting their session terminated even though they are legitimately active. Is it a limited class or category of session event that is recognized as activity, which should result in resetting the timer for the session timeout?
Does anyone know, or can you point me to the information that explains it?
J. Boyd Nolan, P.E.
Director of Technical Development
Tyler Technologies, Inc.