[JBoss JIRA] (WFLY-6531) 'unsupported' is not a valid jboss.api value upstream
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-6531?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-6531:
-----------------------------------
Issue Type: Bug (was: Component Upgrade)
> 'unsupported' is not a valid jboss.api value upstream
> -----------------------------------------------------
>
> Key: WFLY-6531
> URL: https://issues.jboss.org/browse/WFLY-6531
> Project: WildFly
> Issue Type: Bug
> 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
[JBoss JIRA] (ELY-498) Add base class for permission collections with action bits
by David Lloyd (JIRA)
David Lloyd created ELY-498:
-------------------------------
Summary: Add base class for permission collections with action bits
Key: ELY-498
URL: https://issues.jboss.org/browse/ELY-498
Project: WildFly Elytron
Issue Type: Enhancement
Reporter: David Lloyd
Assignee: David Lloyd
Fix For: 1.1.0.Beta6
Permissions which extend the {{AbstractActionSetPermission}} class support coalescence of permission actions. An optimized permission collection will merge permissions whenever a new permission is added that has a name which equals the name of another permission in the collection.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (LOGTOOL-104) FQCN and an import improperly deconflicted - FQCN lost
by Arcadiy Ivanov (JIRA)
[ https://issues.jboss.org/browse/LOGTOOL-104?page=com.atlassian.jira.plugi... ]
Arcadiy Ivanov commented on LOGTOOL-104:
----------------------------------------
Thanks!
> 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
[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:
-------------------------------------
Yes I released it to Nexus. It might take some time to propagate to Maven Central.
> 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
[JBoss JIRA] (LOGTOOL-104) FQCN and an import improperly deconflicted - FQCN lost
by Arcadiy Ivanov (JIRA)
[ https://issues.jboss.org/browse/LOGTOOL-104?page=com.atlassian.jira.plugi... ]
Arcadiy Ivanov commented on LOGTOOL-104:
----------------------------------------
Appreciate it. Just to confirm, the release was cut, right? I think it's still making its way through the repository as 2.0.2.Final is not yet available.
> 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
[JBoss JIRA] (WFLY-6529) Wrong value of atomic types in standard configuration XML files
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-6529?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-6529:
----------------------------------------
WFCORE-337 is the issue for coming up with a way to document this.
> Wrong value of atomic types in standard configuration XML files
> ---------------------------------------------------------------
>
> Key: WFLY-6529
> URL: https://issues.jboss.org/browse/WFLY-6529
> Project: WildFly
> Issue Type: Bug
> Reporter: Radovan Netuka
> Assignee: Radovan Netuka
>
> Description of problem:
> XSD schema doesn't support "${variable}" values of some attributes.
> XSD schema: docs/schema/wildfly-config_4.0.xsd
> Affected attributes:
> port-offset
> port
> multicast-port
>
> Affected files:
> standalone/configuration/standalone.xml
> standalone/configuration/standalone-full.xml
> ... and others
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (WFLY-6489) Distributable session may not exist after redirect to same node with optimistic locking.
by Gabriel Lavoie (JIRA)
[ https://issues.jboss.org/browse/WFLY-6489?page=com.atlassian.jira.plugin.... ]
Gabriel Lavoie edited comment on WFLY-6489 at 4/18/16 2:40 PM:
---------------------------------------------------------------
I've a tested a new build with your pull request and the NPE has been fixed.
{quote}"So long as you don't have referential integrity constraints across session attributes (e.g. a given object isn't referenced by multiple session attributes), you can use attribute replication without issue."{quote}
I don't understand your statement, if I have a mutable complex object and I get it and modifies it within a request, it will not get replicated at the end of the request with transactions disabled unless I explicitly call session.setAttribute() on it again.
There is another example where the session attribute application doesn't work at all with batch disabled: use of the <jsp:useBean/> tag.
In the following sample, we never see the Date update on the second node:
{code}
<%@ page import="java.util.Date" %>
<%@ page contentType="text/html;charset=UTF-8" language="java" %>
<jsp:useBean id="complexAttr" scope="session" class="bean.ComplexAttr"/>
<%
complexAttr.value = new Date();
%>
{code}
{code}
<%@ page contentType="text/html;charset=UTF-8" language="java" %>
<jsp:useBean id="complexAttr" scope="session" class="bean.ComplexAttr"/>
<html>
<head>
<title></title>
</head>
<body>
Date is: <%=complexAttr.value%>
</body>
</html>
{code}
{code}
package bean;
import java.io.Serializable;
import java.util.Date;
public class ComplexAttr implements Serializable {
public Date value;
}
{code}
This second pattern is critical to us as we also have a lot of usage of session scoped bean in our JSPs.
was (Author: glavoie):
I've a tested a new build with your pull request and the NPE has been fixed.
{quote}"So long as you don't have referential integrity constraints across session attributes (e.g. a given object isn't referenced by multiple session attributes), you can use attribute replication without issue."{quote}
I don't understand your statement, if I have a mutable complex object and I get it and modifies it within a request, it will not get replicated at the end of the request with transactions disabled unless I explicitly call session.setAttribute() on it again.
There is another example where the session attribute application doesn't work at all with batch disabled: use of the <jsp:useBean/> tag.
In the following sample, we never see the Date update on the second node:
{code}
<%@ page import="java.util.Date" %>
<%@ page contentType="text/html;charset=UTF-8" language="java" %>
<jsp:useBean id="complexAttr" scope="session" class="bean.ComplexAttr"/>
<%
complexAttr.value = new Date();
%>
{code}
{code}
<%@ page contentType="text/html;charset=UTF-8" language="java" %>
<jsp:useBean id="complexAttr" scope="session" class="bean.ComplexAttr"/>
<html>
<head>
<title></title>
</head>
<body>
Date is: <%=complexAttr.value%>
</body>
</html>
{code}
{code}
package bean;
import java.io.Serializable;
import java.util.Date;
public class ComplexAttr implements Serializable {
public Date value;
}
{code}
> Distributable session may not exist after redirect to same node with optimistic locking.
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-6489
> URL: https://issues.jboss.org/browse/WFLY-6489
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 8.2.1.Final, 10.0.0.Final, 10.1.0.Final
> Reporter: Gabriel Lavoie
> Assignee: Paul Ferraro
> Priority: Critical
> Attachments: wfly-6489-showcase.zip, wildfly-10-session-issue.zip
>
>
> I'm currently working on porting an application running on EAP 6.1 to WildFly 10 and am encountering multiple session/authentication issues with clustering enabled. Our login flow currently starts from a servlet that accepts the credentials, creates the session, then redirect to the welcome page.
> The first time we execute this flow after the startup of a node, the welcome page can't see at all the session created previously.
> - request.getSession() creates yet another session and a new session cookie is returned.
> - request.getSession(false) returns "null"
> On the second attempt, the flow works as expected.
> The issue can be reproduced on both a single node or a two nodes cluster, as long as <distributable /> is enabled in web.xml.
> We are currently using the master build https://ci.jboss.org/hudson/job/WildFly-latest-master/2244/, but the problem has been noticed on 10.0.0-Final and also 8.2.1-Final.
> I attached a sample web application that I used to reproduce the issue. Our standalone.xml is also included with the clustering configuration we've been using for the web/session cache.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years