9.x branch created; master is for WildFly 10
by Brian Stansberry
I've created a 9.x branch in the WildFly repo on github.[1] From this
point forward, work on the 'master' branch will be targeted toward the
WildFly 10 release.
If you have a change that needs to go into WildFly 9 (i.e. for
9.0.0.CR2), you will need to submit two pull requests: one against the
9.x branch, and one against master. The latter ensures your fix doesn't
get dropped in WildFly 10.
If you create a PR against 9.x, be careful in the github UI when you
submit it. Even if your local branch was based on 9.x, github doesn't
recognize that and by default will create the PR against master. You
need to use the pulldown to select 9.x.
For WildFly Core I created a 1.x branch last Friday, and master now
targets 2.0, which will be the core version using in WildFly 10.
Our intent is to produce a WildFly 10.0.0.Alpha1 on or around May 19,
with another alpha following every two weeks. These are meant to be
time-boxed releases, produced according to schedule with whatever is
ready included.
Best regards,
--
Brian Stansberry
Senior Principal Software Engineer
JBoss by Red Hat
[1] https://github.com/wildfly/wildfly/tree/9.x
8 years, 11 months
Starting Infinispan as Eager Mode
by Anselm Hou
Dear all experts,
I'm trying to migrate my current Wildfly 8.1.0 Final to WildFly 9.0.0.CR1.
While doing so I wish to configure the infinispan's hibernate cache to
configure as start as EAGER, but when I try it via the Admin Console, it
throws an error message and said it can not start as EAGER...
Any help will be high appreciated.
Thank you in advance.
Anselm
Following is my request & response that captured from console:
Request
{
"operation" => "composite",
"address" => [],
"steps" => [{
"address" => [
("profile" => "full"),
("subsystem" => "infinispan"),
("cache-container" => "hibernate")
],
"operation" => "write-attribute",
"name" => "start",
"value" => "EAGER"
}]
}
Response
Internal Server Error
{
"outcome" => "failed",
"failure-description" => {"domain-failure-description" =>
{"WFLYCTL0062: Composite operation failed and was rolled back. Steps that
failed:" => {"Operation step-1" => "WFLYCTL0248: Invalid value EAGER for
start; legal values are [LAZY]"}}},
"rolled-back" => true
}
8 years, 11 months
WildFly Core 1.0.0.CR1 is released
by Brian Stansberry
I've released the 1.0.0.CR1 version of WildFly Core and submitted a pull
request to move WildFly Full to it.
I've also created a 1.x branch of WildFly Core in github. From this
point forward, the 'master' branch is for work on WildFly Core 2.0,
while 1.x should be used for patches needed to get 1.0.0 to Final. PRs
for fixes to 1.x should also have a matching PR for master so we have no
regressions.
I plan to do a 1.0.0.CR2 release next Friday, if there are any necessary
changes to 1.0.0. Our target for 1.0.0.Final is May 15.
Enjoy, and thanks everyone for all the hard work!
--
Brian Stansberry
Senior Principal Software Engineer
JBoss by Red Hat
8 years, 12 months
