[JBoss JIRA] (DROOLS-3058) [DMN Designer] Decision Navigator dock is shown for business process
by Jozef Marko (JIRA)
Jozef Marko created DROOLS-3058:
-----------------------------------
Summary: [DMN Designer] Decision Navigator dock is shown for business process
Key: DROOLS-3058
URL: https://issues.jboss.org/browse/DROOLS-3058
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.13.0.Final
Reporter: Jozef Marko
Assignee: Michael Anstis
Attachments: Screenshot from 2018-10-01 10-04-33.png
DMN model designer shows additional *Decision Navigator* dock next to *Project Explorer*. The issue is this additional dock remains opened also for business process.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 3 months
[JBoss JIRA] (WFLY-11092) XtsAsLogger doesn't compile on JDK11, WildFly can't be build on Java 11
by Rostislav Svoboda (JIRA)
[ https://issues.jboss.org/browse/WFLY-11092?page=com.atlassian.jira.plugin... ]
Rostislav Svoboda updated WFLY-11092:
-------------------------------------
Component/s: Server
Summary: XtsAsLogger doesn't compile on JDK11, WildFly can't be build on Java 11 (was: XtsAsLogger doesn't compile on JDK11)
Priority: Blocker (was: Major)
> XtsAsLogger doesn't compile on JDK11, WildFly can't be build on Java 11
> -----------------------------------------------------------------------
>
> Key: WFLY-11092
> URL: https://issues.jboss.org/browse/WFLY-11092
> Project: WildFly
> Issue Type: Bug
> Components: Server, XTS
> Environment: {noformat}
> java version "11" 2018-09-25
> Java(TM) SE Runtime Environment 18.9 (build 11+28)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11+28, mixed mode)
> {noformat}
> Reporter: Petr Kremensky
> Assignee: Ondra Chaloupka
> Priority: Blocker
> Labels: Java11
>
> Compilation failure on JDK 11 introduced by https://github.com/wildfly/wildfly/pull/11702
> {noformat}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile (default-compile) on project wildfly-xts: Compilation failure
> [ERROR] /home/pkremens/devel/wildfly/xts/target/generated-sources/annotations/org/jboss/as/xts/logging/XtsAsLogger_$logger.java:[11,22] '.' expected
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 3 months
[JBoss JIRA] (WFLY-10319) NameBinding annotations on resources are ignored in subresources
by Michal Petrov (JIRA)
[ https://issues.jboss.org/browse/WFLY-10319?page=com.atlassian.jira.plugin... ]
Michal Petrov commented on WFLY-10319:
--------------------------------------
[~jestevezsanchez], I don't think this is a bug. By design nested classes do not inherit the annotations of their outer class and annotations are not inheritable by default. That is core Java not something in the JAX-RS subsystem or RESTEasy. In order to make something like this work you need to:
* make DemoSubResource extend DemoResource
* add \@Inherited to the name binding
> NameBinding annotations on resources are ignored in subresources
> ----------------------------------------------------------------
>
> Key: WFLY-10319
> URL: https://issues.jboss.org/browse/WFLY-10319
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 12.0.0.Final
> Reporter: Javier Estevez Sanchez
> Assignee: Jason Greene
>
> The following JAX-RS resource exposes two resources via a GET operation: /demo and /demo/subresource. The first one via a sub-resource method, the latter via a sub-resource locator. Additionally, a response filter is binded to the JAX-RS resource class to modify the response. From the JAX-RS 2.0 spec, §6.5.2 Name Binding:
> {quote}
> Binding annotations that decorate resource classes apply to all resource methods defined in them.
> {quote}
> However, the binding annotation is not applying to the sub-resource locator method. This happens when the name binding annotation is on the resource class or on the sub-resource locator method. Annotating the sub-resource class or the method within works as expected, though.
> Below is the code needed to reproduce this issue:
> {code:java|title=The resource and subresource}
> @DemoNameBinding
> @Produces(MediaType.APPLICATION_JSON)
> @Path("/demo")
> public class DemoResource {
> @GET
> public String getDemoValue() {
> return "A value";
> }
> @Path("/subresource")
> public DemoSubResource getSubResource() {
> return new DemoSubResource();
> }
> public class DemoSubResource {
> @GET
> public String getDemoValue() {
> return "A value";
> }
> }
> }
> {code}
> {code:java|title=The filter}
> @Provider
> @DemoNameBinding
> public class SomeFilter implements ContainerResponseFilter {
> @Override
> public void filter(ContainerRequestContext requestContext, ContainerResponseContext responseContext) {
> responseContext.setEntity("A filtered value");
> }
> }
> {code}
> {code:java|title=The binding}
> @NameBinding
> @Target({ElementType.TYPE, ElementType.METHOD})
> @Retention(RetentionPolicy.RUNTIME)
> public @interface DemoNameBinding {
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 3 months
[JBoss JIRA] (WFCORE-3996) GC logging is not working on Java 9
by Radovan Stancel (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3996?page=com.atlassian.jira.plugi... ]
Radovan Stancel updated WFCORE-3996:
------------------------------------
Git Pull Request: https://github.com/wildfly/wildfly-core/pull/3496, https://github.com/wildfly/wildfly-core/pull/3538 (was: https://github.com/wildfly/wildfly-core/pull/3496)
> GC logging is not working on Java 9
> -----------------------------------
>
> Key: WFCORE-3996
> URL: https://issues.jboss.org/browse/WFCORE-3996
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Reporter: Rostislav Svoboda
> Assignee: Radovan Stancel
> Priority: Blocker
> Labels: Java11, blocker-WF14
> Fix For: 7.0.0.Alpha2
>
>
> GC logging is not working on Java 9. This is related to the fact G1 GC is default and there are changes in configuration option.
> {code}
> GC_LOG="true" ./standalone.sh
> {code}
> Java 8:
> {code}
> JAVA_OPTS: -server -verbose:gc -Xloggc:"/Users/rsvoboda/TESTING/7.2.0.CD12.CR1/jboss-eap-7.2/standalone/log/gc.log"
> -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5
> -XX:GCLogFileSize=3M -XX:-TraceClassUnloading -Xms1303m -Xmx1303m -XX:MetaspaceSize=96M
> -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> {code}
> Java 9:
> {code}
> JAVA_OPTS: -server -Xms1303m -Xmx1303m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m
> -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 3 months