[JBoss JIRA] (WFLY-5196) Downgrade PicketLink to 2.5.5.CR1
by Harald Wellmann (JIRA)
[ https://issues.jboss.org/browse/WFLY-5196?page=com.atlassian.jira.plugin.... ]
Harald Wellmann commented on WFLY-5196:
---------------------------------------
WildFly 9 already contains PicketLink 2.7.0. HTTP URL Security is a major new feature in PicketLink 2.7.0 which is not available in 2.6.0 or older.
This downgrade would break things for users working with PicketLink in WildFly 9.
If EAP 7 requires this downgrade, it should be done in EAP but not in WildFly. (And I don't really see the point anyway.)
Are there any more details about "deprecation of PicketLink in WildFly"?
> Downgrade PicketLink to 2.5.5.CR1
> ---------------------------------
>
> Key: WFLY-5196
> URL: https://issues.jboss.org/browse/WFLY-5196
> Project: WildFly
> Issue Type: Component Upgrade
> Components: Build System
> Affects Versions: 10.0.0.Beta2
> Reporter: Peter Skopek
> Assignee: Peter Skopek
>
> We have to downgrade PicketLink to 2.5.x to be in sync with EAP 7 and deprecation of PicketLink in WildFly.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (WFCORE-926) wildfly-core uses an older version of jboss-metadata-common than wildfly
by Fernando Nasser (JIRA)
[ https://issues.jboss.org/browse/WFCORE-926?page=com.atlassian.jira.plugin... ]
Fernando Nasser updated WFCORE-926:
-----------------------------------
Summary: wildfly-core uses an older version of jboss-metadata-common than wildfly (was: wildfly-core uses an older version of jboss-metadata-common than wildly)
> wildfly-core uses an older version of jboss-metadata-common than wildfly
> ------------------------------------------------------------------------
>
> Key: WFCORE-926
> URL: https://issues.jboss.org/browse/WFCORE-926
> Project: WildFly Core
> Issue Type: Component Upgrade
> Components: Test Suite
> Affects Versions: 2.0.0.Beta4
> Reporter: Fernando Nasser
> Assignee: Tomaz Cerar
> Priority: Minor
>
> Both wildfly-core and wildfly have a <artifactId>jboss-metadata-common from <groupId>org.jboss.metadata but they use different properties for the version and the versions differ
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (WFCORE-924) Factor out common code for management interface definitions.
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-924?page=com.atlassian.jira.plugin... ]
Darran Lofthouse updated WFCORE-924:
------------------------------------
Labels: affects_elytron (was: )
> Factor out common code for management interface definitions.
> ------------------------------------------------------------
>
> Key: WFCORE-924
> URL: https://issues.jboss.org/browse/WFCORE-924
> Project: WildFly Core
> Issue Type: Task
> Components: Domain Management
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Labels: affects_elytron
> Fix For: 3.0.0.Alpha1
>
>
> These interfaces started off very simple and initially their attributes were fairly distinct due to the running mode they operated in - however as more and more attributes are added there is more common code than unique code and this is tending to mean all changes are being made in duplicate - double that if a change also impacts on the native definition.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (DROOLS-897) Binding variable or condition
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-897?page=com.atlassian.jira.plugin... ]
Mario Fusco edited comment on DROOLS-897 at 8/27/15 2:05 PM:
-------------------------------------------------------------
I have reproduced the problem you described in this way.
{code}
public static class Parent {
public String value;
public String getValue() {
return value;
}
public void setValue( String value ) {
this.value = value;
}
}
public static class ChildA extends Parent { }
public static class ChildB extends Parent { }
@Test
public void testInheritance() throws Exception {
// DROOLS-897
String drl =
"import " + Parent.class.getCanonicalName() + "\n" +
"import " + ChildA.class.getCanonicalName() + "\n" +
"import " + ChildB.class.getCanonicalName() + "\n" +
"rule \"Variable matches field\" when\n" +
" (\n" +
" ChildA(value == null, $entity : this) or \n" +
" ChildB(value == null, $entity : this)\n" +
" )\n" +
"then\n" +
" modify( $entity ) { setValue(\"Done!\"); }\n" +
"end\n";
KieSession ksession = new KieHelper().addContent( drl, ResourceType.DRL )
.build()
.newKieSession();
ksession.insert( new ChildB() );
ksession.fireAllRules();
}
{code}
I'll try to fix this issue asap. However since all your classes extend the same base class the correct way to do this is pattern matching directly on that base classes as it follows, thus avoiding all the ugly ORs in your rule.
{code}
@Test
public void testInheritance2() throws Exception {
// DROOLS-897
String drl =
"import " + Parent.class.getCanonicalName() + "\n" +
"import " + ChildA.class.getCanonicalName() + "\n" +
"import " + ChildB.class.getCanonicalName() + "\n" +
"rule \"Variable matches field\" when\n" +
" Parent(value == null, $entity : this)\n" +
"then\n" +
" modify( $entity ) { setValue(\"Done!\"); }\n" +
"end\n";
KieSession ksession = new KieHelper().addContent( drl, ResourceType.DRL )
.build()
.newKieSession();
ksession.insert( new ChildB() );
ksession.fireAllRules();
}
{code}
was (Author: mfusco):
I have reproduced the problem you described in this way.
{code}
public static class Parent {
public String value;
public String getValue() {
return value;
}
public void setValue( String value ) {
this.value = value;
}
}
public static class ChildA extends Parent { }
public static class ChildB extends Parent { }
@Test
public void testInheritance() throws Exception {
// DROOLS-897
String drl =
"import " + Parent.class.getCanonicalName() + "\n" +
"import " + ChildA.class.getCanonicalName() + "\n" +
"import " + ChildB.class.getCanonicalName() + "\n" +
"rule \"Variable matches field\" when\n" +
" (\n" +
" ChildA(value == null, $entity : this) or \n" +
" ChildB(value == null, $entity : this)\n" +
" )\n" +
"then\n" +
" modify( $entity ) { setValue(\"Done!\"); }\n" +
"end\n";
KieSession ksession = new KieHelper().addContent( drl, ResourceType.DRL )
.build()
.newKieSession();
ksession.insert( new ChildB() );
ksession.fireAllRules();
}
{code}
I'll try to fix this issue asap. However since all your classes extend the same base class the correct way to do this is pattern matching directly on that base classes as it follows, thus avoiding all the ugly ORs in your rule.
{code}
@Test
public void testInheritance2() throws Exception {
// DROOLS-897
String drl =
"import " + Parent.class.getCanonicalName() + "\n" +
"import " + ChildA.class.getCanonicalName() + "\n" +
"import " + ChildB.class.getCanonicalName() + "\n" +
"rule \"Variable matches field\" when\n" +
" (\n" +
" Parent(value == null, $entity : this)\n" +
" )\n" +
"then\n" +
" modify( $entity ) { setValue(\"Done!\"); }\n" +
"end\n";
KieSession ksession = new KieHelper().addContent( drl, ResourceType.DRL )
.build()
.newKieSession();
ksession.insert( new ChildB() );
ksession.fireAllRules();
}
{code}
> Binding variable or condition
> -----------------------------
>
> Key: DROOLS-897
> URL: https://issues.jboss.org/browse/DROOLS-897
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.2.0.Final
> Environment: Windows 8
> Reporter: Sante Stanisci
> Assignee: Mario Fusco
> Labels: dynamic, instanciation, variable
> Attachments: rule.drl, workaround.drl
>
>
> In this example I have more classes that extends EntityBase (my class). In my intention, i would assign to variable $entity one of this class that is inserted in Ksession fact.
> I insert fact of CtbMovrCoan class
> In when statement of the rule at row 16, variable $entity is correctely,
> but in then statement variable $entity becomes JtbRLavt class (first declared in then cond) and this behavior throw a ClassCastException, obviously.
> Can Help me?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (DROOLS-897) Binding variable or condition
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-897?page=com.atlassian.jira.plugin... ]
Mario Fusco commented on DROOLS-897:
------------------------------------
I have reproduced the problem you described in this way.
{code}
public static class Parent {
public String value;
public String getValue() {
return value;
}
public void setValue( String value ) {
this.value = value;
}
}
public static class ChildA extends Parent { }
public static class ChildB extends Parent { }
@Test
public void testInheritance() throws Exception {
// DROOLS-897
String drl =
"import " + Parent.class.getCanonicalName() + "\n" +
"import " + ChildA.class.getCanonicalName() + "\n" +
"import " + ChildB.class.getCanonicalName() + "\n" +
"rule \"Variable matches field\" when\n" +
" (\n" +
" ChildA(value == null, $entity : this) or \n" +
" ChildB(value == null, $entity : this)\n" +
" )\n" +
"then\n" +
" modify( $entity ) { setValue(\"Done!\"); }\n" +
"end\n";
KieSession ksession = new KieHelper().addContent( drl, ResourceType.DRL )
.build()
.newKieSession();
ksession.insert( new ChildB() );
ksession.fireAllRules();
}
{code}
I'll try to fix this issue asap. However since all your classes extend the same base class the correct way to do this is pattern matching directly on that base classes as it follows, thus avoiding all the ugly ORs in your rule.
{code}
@Test
public void testInheritance2() throws Exception {
// DROOLS-897
String drl =
"import " + Parent.class.getCanonicalName() + "\n" +
"import " + ChildA.class.getCanonicalName() + "\n" +
"import " + ChildB.class.getCanonicalName() + "\n" +
"rule \"Variable matches field\" when\n" +
" (\n" +
" Parent(value == null, $entity : this)\n" +
" )\n" +
"then\n" +
" modify( $entity ) { setValue(\"Done!\"); }\n" +
"end\n";
KieSession ksession = new KieHelper().addContent( drl, ResourceType.DRL )
.build()
.newKieSession();
ksession.insert( new ChildB() );
ksession.fireAllRules();
}
{code}
> Binding variable or condition
> -----------------------------
>
> Key: DROOLS-897
> URL: https://issues.jboss.org/browse/DROOLS-897
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.2.0.Final
> Environment: Windows 8
> Reporter: Sante Stanisci
> Assignee: Mario Fusco
> Labels: dynamic, instanciation, variable
> Attachments: rule.drl, workaround.drl
>
>
> In this example I have more classes that extends EntityBase (my class). In my intention, i would assign to variable $entity one of this class that is inserted in Ksession fact.
> I insert fact of CtbMovrCoan class
> In when statement of the rule at row 16, variable $entity is correctely,
> but in then statement variable $entity becomes JtbRLavt class (first declared in then cond) and this behavior throw a ClassCastException, obviously.
> Can Help me?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (DROOLS-897) Binding variable or condition
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-897?page=com.atlassian.jira.plugin... ]
Mario Fusco updated DROOLS-897:
-------------------------------
Issue Type: Bug (was: Enhancement)
> Binding variable or condition
> -----------------------------
>
> Key: DROOLS-897
> URL: https://issues.jboss.org/browse/DROOLS-897
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.2.0.Final
> Environment: Windows 8
> Reporter: Sante Stanisci
> Assignee: Mario Fusco
> Labels: dynamic, instanciation, variable
> Attachments: rule.drl, workaround.drl
>
>
> In this example I have more classes that extends EntityBase (my class). In my intention, i would assign to variable $entity one of this class that is inserted in Ksession fact.
> I insert fact of CtbMovrCoan class
> In when statement of the rule at row 16, variable $entity is correctely,
> but in then statement variable $entity becomes JtbRLavt class (first declared in then cond) and this behavior throw a ClassCastException, obviously.
> Can Help me?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (WFLY-3174) Add view of batch jobs with ability to view
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-3174?page=com.atlassian.jira.plugin.... ]
James Perkins commented on WFLY-3174:
-------------------------------------
It hasn't been added to the web console yet. At this point it's only accessible from CLI or other management API's.
> Add view of batch jobs with ability to view
> -------------------------------------------
>
> Key: WFLY-3174
> URL: https://issues.jboss.org/browse/WFLY-3174
> Project: WildFly
> Issue Type: Feature Request
> Components: Batch
> Reporter: James Perkins
> Assignee: James Perkins
> Fix For: 9.0.0.CR1
>
> Attachments: admin.console-runtime.png
>
>
> Currently there is no way to view batch jobs for a deployment with in the batch subsystem management. There should be a way to view the batch jobs that have run on various deployments.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (WFLY-4515) Fix clustering transformers and reenable in mixed-domain tests
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4515?page=com.atlassian.jira.plugin.... ]
Radoslav Husar edited comment on WFLY-4515 at 8/27/15 1:10 PM:
---------------------------------------------------------------
There is a whole lot of new problems in the subsystem tests:
remote servers changed types but are not transformed
https://gist.github.com/rhusar/68a6e2a206f0ebab5539
jdbc store changed but is not transformed
https://gist.github.com/rhusar/3328c813eea42db683e6
update: solution
discard and transofrmations are missing in org.jboss.as.clustering.infinispan.subsystem.MixedKeyedJDBCStoreResourceDefinition#buildTransformation
was (Author: rhusar):
There is a whole lot of new problems in the subsystem tests:
remote servers changed types but are not transformed
https://gist.github.com/rhusar/68a6e2a206f0ebab5539
jdbc store changed but is not transformed
https://gist.github.com/rhusar/3328c813eea42db683e6
> Fix clustering transformers and reenable in mixed-domain tests
> --------------------------------------------------------------
>
> Key: WFLY-4515
> URL: https://issues.jboss.org/browse/WFLY-4515
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering
> Affects Versions: 9.0.0.Beta2
> Reporter: Kabir Khan
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: 10.0.0.CR1
>
>
> When running the jgroups and infinispan subsystem tests with -Djboss.test.transformers.eap there are some failures in the transformers tests.
> Also, in the mixed domain tests it is not possible to enable these subsystems, so I have removed them from DomainAdjuster620 in https://github.com/wildfly/wildfly/pull/7350. They should be reenabled again as part of this Jira.
> Some info from private mail:
> {quote}
> However, when transforming that to 7.2.0 by running:
> mvn clean install -DallTests -Djboss.test.mixed.domain.dir=/Users/kabir/old-as7-releases/ -pl testsuite/mixed-domain/ -Dtest=MixedDomain_7_2_0_Final_TestSuite
> I get the following error:
> 11:59:43,682 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010901: Could not connect to master. Aborting. Error was: java.io.IOException: 1-$-WFLYCTL0300: Transforming resource [
> ("profile" => "full-ha"),
> ("subsystem" => "infinispan"),
> ("cache-container" => "server"),
> ("transport" => "TRANSPORT")
> ] for host controller 'slave' to subsystem 'infinispan' model version '1.4.0' --there were problems with some of the attributes and this resource will need to be ignored on that host. Details of problems: [WFLYCLINF0027: Could not determine 'stack' attribute from JGroups subsystem]
> I am not totally sure if this is the right solution, but I attempted to add a stack attribute to the transport, but it does not seem to get persisted so it goes away after reloading the DC (out of admin-only to normal mode). I also tried in standalone mode, and executing
> /subsystem=infinispan/cache-container=server/transport=TRANSPORT:write-attribute(name=stack, value=udp)
> and the stack does not get persisted.
> It is probably a simple fix, but since I am not sure if it is the right fix or not, especially since adding this to the writer it also seems to be ignored by the parser. Perhaps this is a candidate for something along the lines of https://github.com/wildfly/wildfly/blob/master/clustering/jgroups/extensi... so that we can support old configs, but not actually use it on a server using the current version?
> {quote}
> Note that the above is when I was working on this, the 7.2.0 test has been removed. We now test EAP 6.2.0 and 6.3.0 compatibility. I believe the problem is similar there although I have not dug in very deeply.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (WFLY-5201) Do not use newly disallowed characters in jgroups runtime metric attributes names
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-5201?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-5201:
---------------------------------
Component/s: Clustering
> Do not use newly disallowed characters in jgroups runtime metric attributes names
> ---------------------------------------------------------------------------------
>
> Key: WFLY-5201
> URL: https://issues.jboss.org/browse/WFLY-5201
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering, Domain Management
> Affects Versions: 10.0.0.Beta2
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Blocker
> Fix For: 10.0.0.CR1
>
>
> When doing a :read-resource(include-runtime=true,recursive=true) this blows up. Debugging shows that to be because e.g. the resource /subsystem=jgroups/channel=ee/protocol=UDP contains metrics called things like
> {code}
> "timer.keep_alive_time" => {
> "type" => LONG,
> "description" => "Timeout in ms to remove idle threads from the timer pool",
> "expressions-allowed" => false,
> "nillable" => false,
> "access-type" => "metric",
> "storage" => "runtime"
> },
> "timer.max_threads" => {
> "type" => INT,
> "description" => "Max thread pool size for the timer thread pool",
> "expressions-allowed" => false,
> "nillable" => false,
> "access-type" => "metric",
> "storage" => "runtime"
> },
> "timer.min_threads" => {
> "type" => INT,
> "description" => "Minimum thread pool size for the timer thread pool",
> "expressions-allowed" => false,
> "nillable" => false,
> "access-type" => "metric",
> "storage" => "runtime"
> },
> {code}
> i.e. they have a dot in their name. So when the r-r handler wants to read the attributes it in effect tries to do the following demonstrated by CLI commands:
> {code}
> [standalone@localhost:9990 /] /subsystem=jgroups/channel=ee/protocol=UDP:read-attribute(name=timer
> timer.keep_alive_time timer.min_threads timer.rejection_policy timer.wheel_size timer_queue_size timer_threads
> timer.max_threads timer.queue_max_size timer.tick_time timer_class timer_tasks timer_type
> [standalone@localhost:9990 /] /subsystem=jgroups/channel=ee/protocol=UDP:read-attribute(name=timer.max_threads)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0201: Unknown attribute 'timer'",
> "rolled-back" => true
> }
> {code}
> I see ReadResourceHandler has some stuff to extract the attribute name if 'extended syntax' is used. So we have two options:
> 1) Ban dots in metric/attribute names
> 2) Add a workaround to fall back. In other words if ReadAttributeHandler thinks extended syntax is being used, and cannot find the extracted 'timer' attribute, then try the full non-extracted name, e.g. timer.max_threads, and only then error.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months