April 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (LOGTOOL-104) FQCN and an import improperly deconflicted - FQCN lost

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/LOGTOOL-104?page=com.atlassian.jira.plugi... ] David Lloyd commented on LOGTOOL-104: ------------------------------------- I think this is caused either by a bug in the import handling in JDeparser, or a bug in the tooling where the JType is being built from an unqualified String rather than the FQCN string which would in turn prevent the import logic from detecting the conflict. > FQCN and an import improperly deconflicted - FQCN lost > ------------------------------------------------------ > > Key: LOGTOOL-104 > URL: https://issues.jboss.org/browse/LOGTOOL-104 > Project: Log Tool > Issue Type: Bug > Affects Versions: 2.0.1.Final > Reporter: Arcadiy Ivanov > > Given: > {code} > import org.osgi.framework.hooks.service.EventHook; > @MessageLogger(projectCode = "JBOSGI") > public interface FrameworkLogger extends BasicLogger { > @LogMessage(level = WARN) > @Message(id = 11019, value = "Error while calling event hook: %s") > void warnErrorWhileCallingEventHook(@Cause Throwable cause, EventHook hook); > @LogMessage(level = WARN) > @Message(id = 11040, value = "Error while calling bundle event hook: %s") > void warnErrorWhileCallingBundleEventHook(@Cause Throwable cause, org.osgi.framework.hooks.bundle.EventHook hook); > } > {code} > Compilation failure: > {quote} > ERROR] COMPILATION ERROR : > [INFO] ------------------------------------------------------------- > [ERROR] /Users/arcivanov/Documents/src/jbosgi/jbosgi-framework/core/target/generated-sources/annotations/org/jboss/osgi/framework/FrameworkLogger_$logger.java:[26,8] org.jboss.osgi.framework.FrameworkLogger_$logger is not abstract and does not override abstract method warnErrorWhileCallingBundleEventHook(java.lang.Throwable,org.osgi.framework.hooks.bundle.EventHook) in org.jboss.osgi.framework.FrameworkLogger > [ERROR] /Users/arcivanov/Documents/src/jbosgi/jbosgi-framework/core/target/generated-sources/annotations/org/jboss/osgi/framework/FrameworkLogger_$logger.java:[336,5] method does not override or implement a method from a supertype > {quote} > Cause: > {code} > import org.osgi.framework.hooks.service.EventHook; > @Generated(value = "org.jboss.logging.processor.generator.model.MessageLoggerImplementor", date = "2016-04-18T04:40:24-0400") > public class FrameworkLogger_$logger extends DelegatingBasicLogger implements FrameworkLogger,BasicLogger,Serializable { > @Override > public final void warnErrorWhileCallingEventHook(final Throwable cause, final EventHook hook) { > super.log.logf(FQCN, org.jboss.logging.Logger.Level.WARN, cause, warnErrorWhileCallingEventHook$str(), hook); > } > @Override > public final void warnErrorWhileCallingBundleEventHook(final Throwable cause, final EventHook hook) { > super.log.logf(FQCN, org.jboss.logging.Logger.Level.WARN, cause, warnErrorWhileCallingBundleEventHook$str(), hook); > } > } > {code} > As you can see the cause of the failure is that {{EventHook}} argument FQCN is lost in the generated {{warnErrorWhileCallingBundleEventHook}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1119) Timers serialization not working with huge ids

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1119?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on DROOLS-1119: ------------------------------------------------- Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1326863|https://bugzilla.redhat.com/show_bug.cgi?id=1326863] from NEW to MODIFIED > Timers serialization not working with huge ids > ---------------------------------------------- > > Key: DROOLS-1119 > URL: https://issues.jboss.org/browse/DROOLS-1119 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 7.0.0.Final > > > Using huge ids for KieSessions corrupts timers serialization -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1119) Timers serialization not working with huge ids

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1119?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on DROOLS-1119: ------------------------------------------------- Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1326814|https://bugzilla.redhat.com/show_bug.cgi?id=1326814] from ASSIGNED to MODIFIED > Timers serialization not working with huge ids > ---------------------------------------------- > > Key: DROOLS-1119 > URL: https://issues.jboss.org/browse/DROOLS-1119 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 7.0.0.Final > > > Using huge ids for KieSessions corrupts timers serialization -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ELY-340) Keystore based CredentialSorage SPI implementation

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-340?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-340: --------------------------------- Fix Version/s: 1.1.0.Beta5 (was: 1.1.0.CR1) > Keystore based CredentialSorage SPI implementation > -------------------------------------------------- > > Key: ELY-340 > URL: https://issues.jboss.org/browse/ELY-340 > Project: WildFly Elytron > Issue Type: Sub-task > Components: API / SPI > Reporter: Peter Skopek > Assignee: Peter Skopek > Fix For: 1.1.0.Beta5 > > > Supply Keystore based CredentialSorage SPI implementation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ELY-492) Add a generic HttpScope implementation with Builder

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-492?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-492. ---------------------------------- Resolution: Rejected After discussion this will provide no benefits over just implementing the interface directly. > Add a generic HttpScope implementation with Builder > --------------------------------------------------- > > Key: ELY-492 > URL: https://issues.jboss.org/browse/ELY-492 > Project: WildFly Elytron > Issue Type: Feature Request > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta6 > > > The HttpScope implementations can easily be built using functions, this task is to provide a generic implementation that can be built from a set of functions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6531) 'unsupported' is not a valid jboss.api value upstream

by Kabir Khan (JIRA)

Kabir Khan created WFLY-6531: -------------------------------- Summary: 'unsupported' is not a valid jboss.api value upstream Key: WFLY-6531 URL: https://issues.jboss.org/browse/WFLY-6531 Project: WildFly Issue Type: Component Upgrade Components: Build System Reporter: Kabir Khan Assignee: Kabir Khan {code} $git grep unsupported -- feature-pack/src/main/resources/modules/system/layers/base/ feature-pack/src/main/resources/modules/system/layers/base/io/undertow/js/main/module.xml: <property name="jboss.api" value="unsupported"/> feature-pack/src/main/resources/modules/system/layers/base/org/jgroups/azure/main/module.xml: <property name="jboss.api" value="unsupported"/> {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6523) org.jboss.narayana.compensations and org.jboss.narayana.rts modules should be unsupported

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-6523?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-6523. ---------------------------- Fix Version/s: (was: 10.1.0.Final) Resolution: Rejected > org.jboss.narayana.compensations and org.jboss.narayana.rts modules should be unsupported > ----------------------------------------------------------------------------------------- > > Key: WFLY-6523 > URL: https://issues.jboss.org/browse/WFLY-6523 > Project: WildFly > Issue Type: Task > Components: Transactions > Reporter: Amos Feng > Assignee: Amos Feng > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6523) org.jboss.narayana.compensations and org.jboss.narayana.rts modules should be unsupported

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-6523?page=com.atlassian.jira.plugin.... ] Kabir Khan reopened WFLY-6523: ------------------------------ > org.jboss.narayana.compensations and org.jboss.narayana.rts modules should be unsupported > ----------------------------------------------------------------------------------------- > > Key: WFLY-6523 > URL: https://issues.jboss.org/browse/WFLY-6523 > Project: WildFly > Issue Type: Task > Components: Transactions > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 10.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-5050) JSP Cross-Context Include Not Working

by Srikanth Reddy Mudiganti (JIRA)

[ https://issues.jboss.org/browse/WFLY-5050?page=com.atlassian.jira.plugin.... ] Srikanth Reddy Mudiganti commented on WFLY-5050: ------------------------------------------------ Hi Brett, I am also facing the same issue on Wildfly 9.0.2. Could you please let me know how to apply(instructions) the fix to Undertow 2.0 ? Thanks > JSP Cross-Context Include Not Working > ------------------------------------- > > Key: WFLY-5050 > URL: https://issues.jboss.org/browse/WFLY-5050 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.2.1.Final, 9.0.1.Final > Environment: Java 8 > Reporter: Brett Prucha > Assignee: Stuart Douglas > Fix For: 10.0.0.Beta1 > > Attachments: test.ear > > > Including JSP files from a cross-context application results in various errors depending on how it's executed and which version of Wildfly (8 or 9) is being used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1159) Add a runtime operation which shows filesystem usage and availability for known server locations

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1159?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet commented on WFCORE-1159: ------------------------------------------- After some intense discussions on naming this operation will be called path-info. It should also display a bunch of filesystem metadata like : resolved path, creation date, last modified. > Add a runtime operation which shows filesystem usage and availability for known server locations > ------------------------------------------------------------------------------------------------ > > Key: WFCORE-1159 > URL: https://issues.jboss.org/browse/WFCORE-1159 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management, Server > Affects Versions: 2.0.2.Final > Reporter: Tristan Tarrant > Assignee: ehsavoie Hugonnet > Fix For: 3.0.0.Alpha1 > > > For management purposes it would be very useful to report runtime metrics for filesystem usage and availability for known server locations (data, tmp, logs, etc). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 April 2016