June 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-817) Extremely poor performance of the topological sorting implementation for type declarations performs

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-817: ------------------------------------- Summary: Extremely poor performance of the topological sorting implementation for type declarations performs Key: DROOLS-817 URL: https://issues.jboss.org/browse/DROOLS-817 Project: Drools Issue Type: Enhancement Components: core engine Affects Versions: 6.3.0.Beta1, 6.2.0.Final, 6.1.0.Final, 6.0.1.Final, 6.0.0.Final Reporter: Davide Sottara Assignee: Davide Sottara Priority: Critical Fix For: 6.3.0.Beta2 The current implementation suffers from thrashing. In case of large business object models (e.g. derived from an ontology), the analysis at package build time may take orders of magnitude more than necessary -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-816) Support internal only methods in trait interfaces

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-816: ------------------------------------- Summary: Support internal only methods in trait interfaces Key: DROOLS-816 URL: https://issues.jboss.org/browse/DROOLS-816 Project: Drools Issue Type: Enhancement Reporter: Davide Sottara Assignee: Davide Sottara Priority: Minor Fix For: 6.3.0.Beta2 When used as traits, interfaces expose all getter/setter pair as virtual members. It should be possible to hide accessor pairs that are meant for internal use. The proposal is to annotate the getter method -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4780) Provide a migration management operation for JBossWeb to Undertow

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4780?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4780: ------------------------------- Fix Version/s: 10.0.0.Beta1 > Provide a migration management operation for JBossWeb to Undertow > ------------------------------------------------------------------ > > Key: WFLY-4780 > URL: https://issues.jboss.org/browse/WFLY-4780 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Reporter: Jason Greene > Assignee: Stuart Douglas > Fix For: 10.0.0.Beta1 > > > Provide a management operation that performs a one-time conversion from the JBossWeb subsystem into the Undertow subsystem. This allows users using the CLI to perform a migration, as well as tools such as WindUp to also execute the change. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4780) Provide a migration management operation for JBossWeb to Undertow

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4780?page=com.atlassian.jira.plugin.... ] Jason Greene moved EAP7-437 to WFLY-4780: ----------------------------------------- Project: WildFly (was: EAP 7 Planning Pilot) Key: WFLY-4780 (was: EAP7-437) Issue Type: Feature Request (was: Requirement) Workflow: GIT Pull Request workflow (was: CDW v1) Component/s: Web (Undertow) (was: Undertow) Target Release: (was: 7.0.0.GA) > Provide a migration management operation for JBossWeb to Undertow > ------------------------------------------------------------------ > > Key: WFLY-4780 > URL: https://issues.jboss.org/browse/WFLY-4780 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Reporter: Jason Greene > Assignee: Stuart Douglas > > Provide a management operation that performs a one-time conversion from the JBossWeb subsystem into the Undertow subsystem. This allows users using the CLI to perform a migration, as well as tools such as WindUp to also execute the change. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-815) Ensure type declarations can handle inner classes

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-815: ------------------------------------- Summary: Ensure type declarations can handle inner classes Key: DROOLS-815 URL: https://issues.jboss.org/browse/DROOLS-815 Project: Drools Issue Type: Bug Affects Versions: 6.3.0.Beta1 Reporter: Davide Sottara Assignee: Davide Sottara Priority: Minor Verify that deeply nested classes can be handled correclty, even in edge cases {code} public class Foo { public static class $X { public static class $Y { } } } {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4695) Remove infinispan-query module and its dependencies

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/WFLY-4695?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on WFLY-4695: --------------------------------------- Actually we need one more commit, the infinispan-query was not deleted yet: https://github.com/wildfly/wildfly/commit/b1333f1f6c0f1fb8aa9314ff14cb9dc... > Remove infinispan-query module and its dependencies > --------------------------------------------------- > > Key: WFLY-4695 > URL: https://issues.jboss.org/browse/WFLY-4695 > Project: WildFly > Issue Type: Task > Components: Clustering > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > > We generally expect people to use the version bundled by the Infinispan project, and there are no strong reasons to include this in WildFly. > Also it makes it much harder to upgrade components such as Hibernate and Infinispan as this components introduces strong coupling on several of these components, essentially mandating that these are all upgraded in lock step. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4751) JNDI lookups of JMS topics/queues can lead to null return values due to a missing service dependency

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/WFLY-4751?page=com.atlassian.jira.plugin.... ] jaikiran pai updated WFLY-4751: ------------------------------- Fix Version/s: 10.0.0.Alpha3 > JNDI lookups of JMS topics/queues can lead to null return values due to a missing service dependency > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-4751 > URL: https://issues.jboss.org/browse/WFLY-4751 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 9.0.0.CR1, 10.0.0.Alpha2 > Reporter: jaikiran pai > Assignee: jaikiran pai > Fix For: 9.0.0.CR2, 10.0.0.Alpha3 > > > The HornetQ subsystem allows for defining jms-topic(s) and jms-queus(s) for a hornetq-server. The jms-topic(s) and jms-queue(s) allow for JNDI names to be specified for each of those JMS destinations. For each of these jms-topic(s) and jms-queues(s) the HornetQ subsystem does the following: > - Set up JMSTopicService and JMSQueueService depending on the destination type. > - These services in their start method use HornetQ APIs to create the destinations. Note that JNDI binding of these destinations is *not* > done at this point via the HornetQ APIs and instead (is rightly) left for the (WildFly) BinderService(s) to take care off. > - The getValue() method of these services return the Topic/Queue that was created by the services' start using HornetQ API > > - For each of the destinations, the HornetQ subsystem sets up a BinderService each for the JNDI names specified for those destinations. The BinderService is configured to fetch the bound value via the JMSTopicService/JMSQueueService (i.e. they use ValueManagedReferenceFactory which ultimately ends up in a call to getValue() of those services). > Looks fine, except that the BinderService(s) have *not* been setup to "depend" on the JMSTopicService/JMSQueueService. > As a result, in theory (and I suspect in reality here https://developer.jboss.org/thread/259981?start=0&tstart=0) JNDI lookups for the topic/queue (even when proper dependencies are setup between the deployments and the BinderService) can end up returning null values, since although the BinderService is up and running, the backing JMSTopicService or JMSQueueService which are responsible for providing the bound value are not yet started and the topic/queue hasn't yet been created. > P.S: I don't have a way to reproduce this, since it all depends on the service startup timings. I however do suspect that this is what is causing those issues in that thread. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4695) Remove infinispan-query module and its dependencies

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/WFLY-4695?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on WFLY-4695: --------------------------------------- BTW thanks a lot for taking over, I wouldn't have known how to do all those changes to the model and configuration tests. > Remove infinispan-query module and its dependencies > --------------------------------------------------- > > Key: WFLY-4695 > URL: https://issues.jboss.org/browse/WFLY-4695 > Project: WildFly > Issue Type: Task > Components: Clustering > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > > We generally expect people to use the version bundled by the Infinispan project, and there are no strong reasons to include this in WildFly. > Also it makes it much harder to upgrade components such as Hibernate and Infinispan as this components introduces strong coupling on several of these components, essentially mandating that these are all upgraded in lock step. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4695) Remove infinispan-query module and its dependencies

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/WFLY-4695?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on WFLY-4695: --------------------------------------- [~pferraro] If you could amend your commit by applying this one then I think we're good: https://github.com/wildfly/wildfly/commit/e3e2e6cf511886736fd3dee6bb99f38... Please squash my changes in yours? they literally just revert some sections of your commit, so it should make your patch smaller. > Remove infinispan-query module and its dependencies > --------------------------------------------------- > > Key: WFLY-4695 > URL: https://issues.jboss.org/browse/WFLY-4695 > Project: WildFly > Issue Type: Task > Components: Clustering > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > > We generally expect people to use the version bundled by the Infinispan project, and there are no strong reasons to include this in WildFly. > Also it makes it much harder to upgrade components such as Hibernate and Infinispan as this components introduces strong coupling on several of these components, essentially mandating that these are all upgraded in lock step. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4695) Remove infinispan-query module and its dependencies

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/WFLY-4695?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on WFLY-4695: --------------------------------------- [~alesj] we're not stopping the Infinispan Query project, you just have to use the modules provided by the Infinispan project. That also better matches the model of the products: Infinispan Query is an add-on feature which isn't included in EAP but requires an optional layer. To configure it, you configure Infinispan as usual but that is done either programmatically or using a dedicated Infinispan configuration file, not by editing the configuration of the app server. That's an important difference as the Cache configuration sections of the app server related to the Infinispan version (module slot) as shipped with WildFly, while you want to use the Infinispan version which you're adding as a layer. That will benefit CapeDwarf in terms of speed: it means you can always pick and choose which version of Infinispan suits you best, so you can use any Infinispan version tagged last night without having to wait for a WildFly release to include it. Means you can benefit from Infinispan fixes overnight, that should speed us up all and remove quite some alignment overhead. > Remove infinispan-query module and its dependencies > --------------------------------------------------- > > Key: WFLY-4695 > URL: https://issues.jboss.org/browse/WFLY-4695 > Project: WildFly > Issue Type: Task > Components: Clustering > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > > We generally expect people to use the version bundled by the Infinispan project, and there are no strong reasons to include this in WildFly. > Also it makes it much harder to upgrade components such as Hibernate and Infinispan as this components introduces strong coupling on several of these components, essentially mandating that these are all upgraded in lock step. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2015