June 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4822) Consolidate cache store configuration flags into more sensible use case enums.

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-4822: ---------------------------------- Summary: Consolidate cache store configuration flags into more sensible use case enums. Key: WFLY-4822 URL: https://issues.jboss.org/browse/WFLY-4822 Project: WildFly Issue Type: Feature Request Components: Clustering Affects Versions: 10.0.0.Alpha3 Reporter: Paul Ferraro Assignee: Paul Ferraro Infinispan cache stores have several boolean flags for defining behavior. There are several combinations of values for these flags that do not make sense (e.g. purge="true" & preload="true" makes no sense). I'd like to consolidate as many of these flags as possible into a set of enumerated values. The enumerated values would more closely map to use cases. This should help eliminate a lot of user confusion. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JGRP-1935) TCP: unneeded copy when receiving single message

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1935?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1935. ---------------------------- Resolution: Done > TCP: unneeded copy when receiving single message > ------------------------------------------------ > > Key: JGRP-1935 > URL: https://issues.jboss.org/browse/JGRP-1935 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.6.4 > > > In {{TCPConnectionMap$TCPConnection$Receiver}}, we create a new byte[] buffer for each received message, based on the length sent before the message. > This buffer is subsequently passed to {{BasicTCP}} which calls {{TP.receive()}}. > {{TP.receive()}} makes a copy of the buffer if it is a single message (batches are deserialized in the same thread), before passing the copy to one the thread pools to get deserialized and processed. > This is an unneeded copy. > SOLUTION: add a flag {{needs_copy}} to the {{TP.receive()}} call and don't copy if true. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-608) Using ? as control character in .inputrc causes CLI to terminate immediately.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-608?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-608: ------------------------------------------------ Marek Kopecky <mkopecky(a)redhat.com> changed the Status of [bug 1203997|https://bugzilla.redhat.com/show_bug.cgi?id=1203997] from ON_QA to VERIFIED > Using ? as control character in .inputrc causes CLI to terminate immediately. > ------------------------------------------------------------------------------ > > Key: WFCORE-608 > URL: https://issues.jboss.org/browse/WFCORE-608 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Environment: Linux > Reporter: Jay Kumar SenSharma > Assignee: Alexey Loubyansky > Fix For: 1.0.0.CR4, 2.0.0.Alpha1 > > > - When using *[wildfly-8.2.0.Final]* When user has a '.inputrc' in the user home directory with the following content: > {code} > # Control characters > "\C-?": backward-delete-char > {code} > - The it fails with the the following Stack Trace: > {code} > ./jboss-cli.sh > java.lang.RuntimeException: ERROR parsing ? keys to aesh. Check your inputrc. > at org.jboss.aesh.edit.mapper.KeyMapper.convertRandomControlKeys(KeyMapper.java:161) > at org.jboss.aesh.edit.mapper.KeyMapper.mapRandomKeys(KeyMapper.java:138) > at org.jboss.aesh.edit.mapper.KeyMapper.mapKeys(KeyMapper.java:108) > at org.jboss.aesh.edit.mapper.KeyMapper.mapQuoteKeys(KeyMapper.java:49) > at org.jboss.aesh.console.Config.parseInputrc(Config.java:127) > at org.jboss.aesh.console.Console.reset(Console.java:150) > at org.jboss.aesh.console.Console.<init>(Console.java:105) > at org.jboss.aesh.console.Console.<init>(Console.java:101) > at org.jboss.as.cli.impl.Console$Factory.getConsole(Console.java:85) > at org.jboss.as.cli.impl.Console$Factory.getConsole(Console.java:78) > at org.jboss.as.cli.impl.CommandContextImpl.initBasicConsole(CommandContextImpl.java:349) > at org.jboss.as.cli.impl.CommandContextImpl.<init>(CommandContextImpl.java:296) > at org.jboss.as.cli.impl.CommandContextFactoryImpl.newCommandContext(CommandContextFactoryImpl.java:76) > at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:273) > at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:253) > at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.modules.Module.run(Module.java:312) > at org.jboss.modules.Main.main(Main.java:460) > {code} > - Expectation is that CLI should not have terminated suddenly rather the exception should have been handled in a proper way. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JGRP-1929) Add a simple properties-based CallbackHandler for the SASL protocol

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JGRP-1929?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JGRP-1929: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1176161|https://bugzilla.redhat.com/show_bug.cgi?id=1176161] from VERIFIED to CLOSED > Add a simple properties-based CallbackHandler for the SASL protocol > ------------------------------------------------------------------- > > Key: JGRP-1929 > URL: https://issues.jboss.org/browse/JGRP-1929 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 3.6.3 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 3.6.4 > > > Add a properties-based CallbackHandler for the SASL protocol which supports a properties file for credentials and one for roles so that nodes can be authenticated and authorized in a simple way -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4821) BusinessViewAnnotationProcessor doesn't consider annotation index

by Jan Martiska (JIRA)

[ https://issues.jboss.org/browse/WFLY-4821?page=com.atlassian.jira.plugin.... ] Jan Martiska closed WFLY-4821. ------------------------------ Resolution: Rejected Oh, you're right. I was betrayed by the fact that javax.api doesn't contain javax.ejb.api. Sorry and thanks for quick explanation. > BusinessViewAnnotationProcessor doesn't consider annotation index > ----------------------------------------------------------------- > > Key: WFLY-4821 > URL: https://issues.jboss.org/browse/WFLY-4821 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Alpha3 > Reporter: Jan Martiska > Assignee: Stuart Douglas > > When parsing EJB view-related annotations (@Local, @Remote), BusinessViewAnnotationProcessor accesses these annotations only via reflection. Therefore, when processing a deployment which imports EJB beans from another module using an annotation index, BusinessViewAnnotationProcessor doesn't see them. Consequently, no @Local or @Remote interfaces are found, therefore all implemented interfaces are treated as @Local - EJB 3.2 4.9.7: > ??if the bean class is annotated with neither the Local nor the Remote annotation, all implemented interfaces (excluding the interfaces listed above) are assumed to be local business interfaces of the bean?? > @Remote interfaces are therefore not available remotely. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4821) BusinessViewAnnotationProcessor doesn't consider annotation index

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-4821?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-4821: -------------------------------------- This sounds like you have just forgotten to add a dependency on the EJB API to your module, the current code should work fine. > BusinessViewAnnotationProcessor doesn't consider annotation index > ----------------------------------------------------------------- > > Key: WFLY-4821 > URL: https://issues.jboss.org/browse/WFLY-4821 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Alpha3 > Reporter: Jan Martiska > Assignee: Stuart Douglas > > When parsing EJB view-related annotations (@Local, @Remote), BusinessViewAnnotationProcessor accesses these annotations only via reflection. Therefore, when processing a deployment which imports EJB beans from another module using an annotation index, BusinessViewAnnotationProcessor doesn't see them. Consequently, no @Local or @Remote interfaces are found, therefore all implemented interfaces are treated as @Local - EJB 3.2 4.9.7: > ??if the bean class is annotated with neither the Local nor the Remote annotation, all implemented interfaces (excluding the interfaces listed above) are assumed to be local business interfaces of the bean?? > @Remote interfaces are therefore not available remotely. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4496) Upgrade AESH from 0.33.14 to 0.33.15

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4496?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4496: ----------------------------------------------- Jitka Kozana <jkudrnac(a)redhat.com> changed the Status of [bug 1210556|https://bugzilla.redhat.com/show_bug.cgi?id=1210556] from ON_QA to VERIFIED > Upgrade AESH from 0.33.14 to 0.33.15 > ------------------------------------ > > Key: WFLY-4496 > URL: https://issues.jboss.org/browse/WFLY-4496 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Bartosz Baranowski > Assignee: Jason Greene > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4821) BusinessViewAnnotationProcessor doesn't consider annotation index

by Jan Martiska (JIRA)

[ https://issues.jboss.org/browse/WFLY-4821?page=com.atlassian.jira.plugin.... ] Jan Martiska commented on WFLY-4821: ------------------------------------ My suggestion for fix: https://github.com/wildfly/wildfly/pull/7641 [~swd847] could you take a look? > BusinessViewAnnotationProcessor doesn't consider annotation index > ----------------------------------------------------------------- > > Key: WFLY-4821 > URL: https://issues.jboss.org/browse/WFLY-4821 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Alpha3 > Reporter: Jan Martiska > Assignee: Stuart Douglas > > When parsing EJB view-related annotations (@Local, @Remote), BusinessViewAnnotationProcessor accesses these annotations only via reflection. Therefore, when processing a deployment which imports EJB beans from another module using an annotation index, BusinessViewAnnotationProcessor doesn't see them. Consequently, no @Local or @Remote interfaces are found, therefore all implemented interfaces are treated as @Local - EJB 3.2 4.9.7: > ??if the bean class is annotated with neither the Local nor the Remote annotation, all implemented interfaces (excluding the interfaces listed above) are assumed to be local business interfaces of the bean?? > @Remote interfaces are therefore not available remotely. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4821) BusinessViewAnnotationProcessor doesn't consider annotation index

by Jan Martiska (JIRA)

Jan Martiska created WFLY-4821: ---------------------------------- Summary: BusinessViewAnnotationProcessor doesn't consider annotation index Key: WFLY-4821 URL: https://issues.jboss.org/browse/WFLY-4821 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 10.0.0.Alpha3 Reporter: Jan Martiska Assignee: Stuart Douglas When parsing EJB view-related annotations (@Local, @Remote), BusinessViewAnnotationProcessor accesses these annotations only via reflection. Therefore, when processing a deployment which imports EJB beans from another module using an annotation index, BusinessViewAnnotationProcessor doesn't see them. Consequently, no @Local or @Remote interfaces are found, therefore all implemented interfaces are treated as @Local - EJB 3.2 4.9.7: ??if the bean class is annotated with neither the Local nor the Remote annotation, all implemented interfaces (excluding the interfaces listed above) are assumed to be local business interfaces of the bean?? @Remote interfaces are therefore not available remotely. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-821) Review and update the drools-osgi integration modules

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-821?page=com.atlassian.jira.plugin... ] Geoffrey De Smet commented on DROOLS-821: ----------------------------------------- Note that drools-osgi contains jbpm too (and now optaplanner too), hence the rename to kie-osgi proposal. > Review and update the drools-osgi integration modules > ----------------------------------------------------- > > Key: DROOLS-821 > URL: https://issues.jboss.org/browse/DROOLS-821 > Project: Drools > Issue Type: Enhancement > Components: core engine > Affects Versions: 6.2.0.Final, 6.3.0.Beta1 > Reporter: Petr Široký > Assignee: Petr Široký > > As discussed with [~virchete] there are few things we need to improve in our drools-osgi integration modules: > - add back the drools-osgi-integration. PR already sent https://github.com/droolsjbpm/droolsjbpm-integration/pull/138 > - add back the drools-osgi integration tests that were moved to fuse-bxms-integ: https://github.com/jboss-integration/fuse-bxms-integ/tree/master/release/... . The fuse-bxms-integ repo should contain only the tests related to Camel > - fix some minor issues in the drools-karaf-features module: remove no longer needed version props, fix the features file name > - review the use of CXF. It seems it is not needed for the core engine. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

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