[JBoss JIRA] (WFCORE-3718) mvn versions:set -DnewVersion=xxxx does not replace component-matrix/pom.xml
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3718?page=com.atlassian.jira.plugi... ]
Tomaz Cerar commented on WFCORE-3718:
-------------------------------------
Yes, idea is that component-matrix has no dependencies to anything, jboss-parent is there just to make sure the release process (plugin settings) is the same across the project.
Maybe solution for this would be to add configuration of versions plugin to pluginManagment to always have processAllModules configured, this way person doing release wouldn't need to be extra careful.
> mvn versions:set -DnewVersion=xxxx does not replace component-matrix/pom.xml
> ----------------------------------------------------------------------------
>
> Key: WFCORE-3718
> URL: https://issues.jboss.org/browse/WFCORE-3718
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 5.0.0.Alpha2
> Reporter: Kabir Khan
> Assignee: Tomaz Cerar
>
> {quote}
> [2:26 PM] Kabir Khan: @ctomc following https://developer.jboss.org/wiki/WildFlyCoreReleaseProcess, and using
> mvn versions:set -DnewVersion=5.0.0.Alpha2
> [2:26 PM] Kabir Khan: it seems to keep component-matrix/pom.xml as -SNAPSHOT
> [2:26 PM] Kabir Khan: $git grep "\-SNAPSHOT"
> component-matrix/pom.xml: <version>5.0.0.Alpha2-SNAPSHOT</version>
> [2:27 PM] Tomaz Cerar: damn, that is not good
> [2:27 PM] Tomaz Cerar: versions plugin is bit stupid in some cases
> [2:27 PM] Kabir Khan: Should it be in the list of modules?
> [2:27 PM] Tomaz Cerar: it is
> {quote}
> All other versions are correctly replaced. I'd hazard a guess that this also happens in WF full.
> CC [~brian.stansberry] - for the 5.0.0.Alpha2 release I'm using the old find/sed way
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months
[JBoss JIRA] (DROOLS-2441) DMN runtime not using the kiecontainer root classloader to load classes
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2441?page=com.atlassian.jira.plugi... ]
Edson Tirelli commented on DROOLS-2441:
---------------------------------------
I attached an example to reproduce this problem. This one also requires a dependency to apache commons, that also needs to work after changing the classloader:
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>commons-math3</artifactId>
<version>3.6.1</version>
</dependency>
> DMN runtime not using the kiecontainer root classloader to load classes
> -----------------------------------------------------------------------
>
> Key: DROOLS-2441
> URL: https://issues.jboss.org/browse/DROOLS-2441
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Affects Versions: 7.6.0.Final
> Reporter: Edson Tirelli
> Assignee: Matteo Mortari
> Priority: Blocker
> Fix For: 7.8.0.Final
>
> Attachments: Standard Deviation.dmn, StandardDeviation.java
>
>
> The FunctionDefNode is not using the kie container root classloader to load classes. I even added a comment for that, just a shame comments are not executable:
> https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-feel/src/m...
> {code:title=FunctionDefNode.java}
> // might need to explicitly use a classloader here
> Class<?> clazz = Class.forName( clazzName );
> {code}
> To reproduce the problem, create a java class with a static method, add it to the kjar, create a DMN model that invokes that model, and try to execute.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months
[JBoss JIRA] (DROOLS-2441) DMN runtime not using the kiecontainer root classloader to load classes
by Edson Tirelli (JIRA)
Edson Tirelli created DROOLS-2441:
-------------------------------------
Summary: DMN runtime not using the kiecontainer root classloader to load classes
Key: DROOLS-2441
URL: https://issues.jboss.org/browse/DROOLS-2441
Project: Drools
Issue Type: Bug
Components: dmn engine
Affects Versions: 7.6.0.Final
Reporter: Edson Tirelli
Assignee: Matteo Mortari
Priority: Blocker
Fix For: 7.8.0.Final
The FunctionDefNode is not using the kie container root classloader to load classes. I even added a comment for that, just a shame comments are not executable:
https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-feel/src/m...
{code:title=FunctionDefNode.java}
// might need to explicitly use a classloader here
Class<?> clazz = Class.forName( clazzName );
{code}
To reproduce the problem, create a java class with a static method, add it to the kjar, create a DMN model that invokes that model, and try to execute.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months
[JBoss JIRA] (WFLY-10156) Java EE 7 REST Service not called
by Viggo Navarsete (JIRA)
Viggo Navarsete created WFLY-10156:
--------------------------------------
Summary: Java EE 7 REST Service not called
Key: WFLY-10156
URL: https://issues.jboss.org/browse/WFLY-10156
Project: WildFly
Issue Type: Bug
Components: Server
Affects Versions: 12.0.0.Final
Reporter: Viggo Navarsete
Assignee: Jason Greene
Current setup that works:
Wildfly 10.0.0.Final
Keycloak 3.4.3.Final
- Deployed a REST endpoint (/zupplyio-orderservice/orders) to Wildfly 10.0.0.Final
- Access the endpoint through a React app with a token received from Keycloak.
- Returns a 200 http response with payload
- undertow server.log:
19:35:33,356 INFO [io.undertow.accesslog] (default task-1) 127.0.0.1 [30/Mar/2018:19:35:33 +0200] "OPTIONS /zupplyio-orderservice/orders HTTP/1.1" 200 "Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Mobile Safari/537.36"
19:35:33,994 INFO [stdout] (default task-2) *** Calling getOrders ***
19:35:34,121 INFO [io.undertow.accesslog] (default task-2) 127.0.0.1 [30/Mar/2018:19:35:34 +0200] "GET /zupplyio-orderservice/orders HTTP/1.1" 200 "Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Mobile Safari/537.36"
Setup that doesn't work:
Wildfly 12.0.0.Final
Keycloak 3.4.3.Final
- Deployed a REST endpoint (/zupplyio-orderservice/orders) to Wildfly 10.0.0.Final
- Access the endpoint through a React app with a token received from Keycloak.
- Returns a 200 http response with NO payload
- undertow server.log:
19:25:22,707 INFO [io.undertow.accesslog] (default task-1) 127.0.0.1 [30/Mar/2018:19:25:22 +0200] "OPTIONS /zupplyio-orderservice/orders HTTP/1.1" 200 "Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Mobile Safari/537.36"
19:25:23,491 INFO [io.undertow.accesslog] (default task-1) 127.0.0.1 [30/Mar/2018:19:25:23 +0200] "GET /zupplyio-orderservice/orders HTTP/1.1" 200 "Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Mobile Safari/537.36"
As you can see from the server.log, my endpoint is probably not called in Wildfly 12.0.0.Final since the log output isn't written to server.log
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months
[JBoss JIRA] (JBEE-191) JAXB API loading default impl fails in Java 9
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/JBEE-191?page=com.atlassian.jira.plugin.s... ]
David Lloyd resolved JBEE-191.
------------------------------
Resolution: Won't Fix
This doesn't need fixing. The platform JAXB provider can never be accessible from a non-platform API, so it's going to fail regardless. The correct fix is to ensure that the implementation is always on the API classpath no matter what.
> JAXB API loading default impl fails in Java 9
> ---------------------------------------------
>
> Key: JBEE-191
> URL: https://issues.jboss.org/browse/JBEE-191
> Project: JBoss JavaEE Spec APIs
> Issue Type: Bug
> Components: jboss-jaxb-api
> Affects Versions: jboss-jaxb-api_2.3_spec-1.0.1.Final
> Reporter: David Lloyd
> Assignee: David Lloyd
> Fix For: jboss-jaxb-api_2.3_spec-1.0.2.Final
>
>
> The platform default provider is instantiated with a null class loader, which is not likely to work since the JDK will be linking against the wrong API. In addition, these classes are private in Java 9+ so even if it did link correctly, the instantiation would fail due to the non-exported package.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months
[JBoss JIRA] (JBEE-191) JAXB API loading default impl fails in Java 9
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/JBEE-191?page=com.atlassian.jira.plugin.s... ]
David Lloyd updated JBEE-191:
-----------------------------
Fix Version/s: (was: jboss-jaxb-api_2.2_spec-1.0.5.Final)
> JAXB API loading default impl fails in Java 9
> ---------------------------------------------
>
> Key: JBEE-191
> URL: https://issues.jboss.org/browse/JBEE-191
> Project: JBoss JavaEE Spec APIs
> Issue Type: Bug
> Components: jboss-jaxb-api
> Affects Versions: jboss-jaxb-api_2.3_spec-1.0.1.Final
> Reporter: David Lloyd
> Assignee: David Lloyd
> Fix For: jboss-jaxb-api_2.3_spec-1.0.2.Final
>
>
> The platform default provider is instantiated with a null class loader, which is not likely to work since the JDK will be linking against the wrong API. In addition, these classes are private in Java 9+ so even if it did link correctly, the instantiation would fail due to the non-exported package.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months
[JBoss JIRA] (JBEE-191) JAXB API loading default impl fails in Java 9
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/JBEE-191?page=com.atlassian.jira.plugin.s... ]
David Lloyd updated JBEE-191:
-----------------------------
Affects Version/s: (was: jboss-jaxb-api_2.2_spec-1.0.4.Final)
> JAXB API loading default impl fails in Java 9
> ---------------------------------------------
>
> Key: JBEE-191
> URL: https://issues.jboss.org/browse/JBEE-191
> Project: JBoss JavaEE Spec APIs
> Issue Type: Bug
> Components: jboss-jaxb-api
> Affects Versions: jboss-jaxb-api_2.3_spec-1.0.1.Final
> Reporter: David Lloyd
> Assignee: David Lloyd
> Fix For: jboss-jaxb-api_2.3_spec-1.0.2.Final
>
>
> The platform default provider is instantiated with a null class loader, which is not likely to work since the JDK will be linking against the wrong API. In addition, these classes are private in Java 9+ so even if it did link correctly, the instantiation would fail due to the non-exported package.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months