Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Next is 13.0.0.Beta4

  1. … 77 more files in changeset.
Prepare for 13.0.0.Beta3 release

  1. … 77 more files in changeset.
Next is 13.0.0.Beta3-SNAPSHOT

Signed-off-by: Jeff Mesnil <jmesnil@redhat.com>

  1. … 77 more files in changeset.
Prepare for the 13.0.0.Beta2 release

  1. … 77 more files in changeset.
[WFCORE-5037] Tighten access a bit

[WFCORE-5037] Pass in the AttributeDefinition where possible to the JMX TypeConverters

Note that for the main work we still use the descriptor. This fix is

mainly to make it possible to check which kind of Object with complex

values we have.

ObjectTypeAttributeDefinition and ObjectMapAttributeDefinition both

return the same r-r-d output for attributes but are different. The first

one has defined key/value pairs where the keys are all known. e.g. the

following would be an allowed value:

{"my-attr" => {"one" => 100L}}

ObjectMapAttributeDefinition on the other hand is a map of unknown keys

containing those entries, e.g. the following would be an allowed value:

{"my-attr" => {"a" => {"one" => 100L}}}

In both cases the r-r-d output for the attribute would look like:

"description" => "description",

"attributes" => {"my-attr" => {

"type" => OBJECT,

"description" => "map-of-maps",

"expressions-allowed" => false,

"required" => false,

"nillable" => true,

"value-type" => {"one" => {

"type" => LONG,

"description" => "map-of-maps.one",

"expressions-allowed" => false,

"required" => true,

"nillable" => false

}},

"access-type" => "metric",

"storage" => "runtime"

}},

....

So there is no way for JMX yet to know which of the two cases we have.

Passing in the AttributeDefinition is an attempt at figuring that out.

[WFCORE-5037] Get JMX conversion working for maps of complex types

Prepare for the 12.0.3.Final release

Signed-off-by: Jeff Mesnil <jmesnil@redhat.com>

  1. … 73 more files in changeset.
Next is 12.0.3 release

Signed-off-by: Jeff Mesnil <jmesnil@redhat.com>

  1. … 73 more files in changeset.
Prepare for the 12.0.2.Final release

Signed-off-by: Jeff Mesnil <jmesnil@redhat.com>

  1. … 73 more files in changeset.
Prepare for the 12.0.2.Final release

Signed-off-by: Jeff Mesnil <jmesnil@redhat.com>

  1. … 73 more files in changeset.
Next version is 12.0.2.Final

Signed-off-by: Jeff Mesnil <jmesnil@redhat.com>

  1. … 73 more files in changeset.
Next is 13.0.0.Beta2-SNAPSHOT release

  1. … 77 more files in changeset.
Prepare for the 13.0.0.Beta1 release

  1. … 77 more files in changeset.
Next is 13.0.0.Beta1-SNAPSHOT release

Signed-off-by: Jeff Mesnil <jmesnil@redhat.com>

  1. … 73 more files in changeset.
Next is 12.0.2.Final-SNAPSHOT release

  1. … 73 more files in changeset.
Prepare for the 12.0.1.Final release

  1. … 73 more files in changeset.
Next is 12.0.1.Final-SNAPSHOT release

  1. … 73 more files in changeset.
Prepare for the 12.0.0.Final release

  1. … 73 more files in changeset.
Next is 12.0.0.CR1-SNAPSHOT release

  1. … 73 more files in changeset.
Prepare for the 12.0.0.Beta4 release

  1. … 73 more files in changeset.
Next is 12.0.0.Beta4-SNAPSHOT release

  1. … 73 more files in changeset.
Prepare for the 12.0.0.Beta3 release

  1. … 73 more files in changeset.
Next is 11.1.2.Final-SNAPSHOT release

  1. … 70 more files in changeset.
Prepare for the 11.1.1.Final release

  1. … 70 more files in changeset.
Next is 12.0.0.Beta3-SNAPSHOT release

  1. … 70 more files in changeset.
Prepare for the 12.0.0.Beta2 release

  1. … 70 more files in changeset.
Next version is 11.1.1.Final

Signed-off-by: Jeff Mesnil <jmesnil@redhat.com>

  1. … 70 more files in changeset.
Prepare release 11.1.0.Final

  1. … 70 more files in changeset.
[WFCORE-4901] TCCL not set to application classloader when MBean Notification is invoked

[WFCORE-4901] TCCL not set to application classloader when MBean Notification is invoked