[JBoss JIRA] (WFLY-10029) bean-discovery-mode="annotated" is not working like described in the spec
by Martin Kouba (JIRA)
[ https://issues.jboss.org/browse/WFLY-10029?page=com.atlassian.jira.plugin... ]
Martin Kouba edited comment on WFLY-10029 at 3/15/18 9:29 AM:
--------------------------------------------------------------
Well, this really depends on where the {{SomeClass}} comes from, i.e. in which bean archive it resides. If it's an implicit bean archive then it's defintely a bug.
-I did a quick test and it seems the problem occurs if {{SomeClass}} is located in an implicit bean archive with no {{beans.xml}}. In this case, WildFly creates a synthetic beans.xml with {{bean-discovery-mode=all}}-. I've just retested this and it works as expected - a class without a bean defining annotation was not discovered (even if no beans.xml is used).
[~rsoika] If possible pls provide a "failing" app so that we could inspect the deployment structure.
was (Author: mkouba):
Well, this really depends on where the {{SomeClass}} comes from, i.e. in which bean archive it resides. If it's an implicit bean archive then it's defintely a bug. I did a quick test and it seems the problem occurs if {{SomeClass}} is located in an implicit bean archive with no {{beans.xml}}. In this case, WildFly creates a synthetic beans.xml with {{bean-discovery-mode=all}}.
> bean-discovery-mode="annotated" is not working like described in the spec
> -------------------------------------------------------------------------
>
> Key: WFLY-10029
> URL: https://issues.jboss.org/browse/WFLY-10029
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 10.1.0.Final
> Reporter: Ralph Soika
> Assignee: Martin Kouba
> Priority: Minor
> Labels: beans.xml
>
> I think we have a problem in Wildfly 10 concerning scanning of CDI Beans. Take a look at the following example:
> {code:java}
> @Stateless
> @LocalBean
> public class SomeService {
> ...
> }
> public class SomeClass {
> @EJB
> SomeService someService;
> ....
> }
> {code}
> We have a stateless session ejb an a bean which is not annotated with a scope but is injecting the service EJB. If you use a beans.xml with the tag:
> {noformat}
> bean-discovery-mode="annotated"
> {noformat}
> this works in wildfly 10 - the _someService_ is injected into the _someClass_ which is treated as a CDI bean. But this is not a correct behavior as stated in the specification. It says, that in this case only beans with a scope annotation should be treated as CDI which is not the case for SomeClass. Normally, as a developer, you would not complain much about this. So this is only a minor issue.
> I recognized this after I tried to run my application on Glassfish/Payara4 which did no longer work until I changed the beans.xml tag to:
> {noformat}
> bean-discovery-mode="all"
> {noformat}
> Now it works in both application servers. I think in wildfly we are misinterpreting the attribute "bean-discovery-mode". I think this should be changed in the next versions for EE8. I don't know if this behavior is a known issue and maybe it is still under development.
> I know also that with such a change some projects (also my own ones) will break. So maybe a new configuration switch like "strict-cdi-scanning" is helpful. What do you think?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-10028) Move XML/XSD validation test case to dist module
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-10028?page=com.atlassian.jira.plugin... ]
Jeff Mesnil reassigned WFLY-10028:
----------------------------------
Assignee: Jeff Mesnil
> Move XML/XSD validation test case to dist module
> ------------------------------------------------
>
> Key: WFLY-10028
> URL: https://issues.jboss.org/browse/WFLY-10028
> Project: WildFly
> Issue Type: Task
> Components: Test Suite
> Affects Versions: 12.0.0.Final
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
>
> The StandardConfigsXMLValidationUnitTestCase and XSDValidationUnitTestCase tests validates that the XML and XSD files that are shipped with WildFly are valid.
> However, these tests are run by the smoke test suite and it is possible that previous tests have modified the configuration file that is used by the running WildFly server for the tests.
> This is mostly harmless (as these tests should cleaned up any modification when they are teared down) except when WildFly core is changing its schemas and the WildFly integration CI job is checking that WildFly core snapshots behave correctly.
> At this point, the WildFly XML configuration files references the latest XML version that is released with Core but the core snapshots introduced more recent versions.
> The tests uses the special property jboss.test.xml.validation.future.schemas to ignore the latest schema when using core snapshots.
> Unfortunately, the previous smoke tests may have modified the configuration file that will be written with the latest core schema version.
> To fix this issue, these 2 tests should be moved to the dist maven module so that they validate the *actual* configuration files shipped with WildFly before any test has an opportunity to modify them.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-10031) Scripts throws "illegal reflective access" warning on JDK9
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFLY-10031?page=com.atlassian.jira.plugin... ]
Marek Kopecký updated WFLY-10031:
---------------------------------
Description:
*Description of the issue:*
Scripts throws "illegal reflective access" warning on JDK9.
*How reproducible:*
Always with JDK9
*Steps to Reproduce:*
* ./jboss-cli.sh "echo test"
* ./add-user.sh -u test4 -p Test123* -s
* ./appclient.sh -v
* ./wsconsume.sh
* ./wsprovide.sh
* ./domain.sh
* ./standalone.sh
*Actual results:*
{noformat}
[hudson@rhel7-large-9887 bin]$ java --version
java 9.0.4
Java(TM) SE Runtime Environment (build 9.0.4+11)
Java HotSpot(TM) 64-Bit Server VM (build 9.0.4+11, mixed mode)
[hudson@rhel7-large-9887 bin]$
{noformat}
{noformat}
[hudson@rhel7-large-9887 bin]$ ./jboss-cli.sh "echo test"
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.jboss.logmanager.LogManager$2 (jar:file:/home/hudson/hudson_workspace/workspace/early-testing-scripts-unix/9774dccf/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.9.Final.jar!/) to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogManager$2
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
test
[hudson@rhel7-large-9887 bin]$
{noformat}
{noformat}
[hudson@rhel7-large-9887 bin]$ ./add-user.sh -u test4 -p Test123* -s
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.jboss.logmanager.LogManager$2 (jar:file:/home/hudson/hudson_workspace/workspace/early-testing-scripts-unix/9774dccf/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.9.Final.jar!/) to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogManager$2
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
[hudson@rhel7-large-9887 bin]$ cat ../standalone/configuration/mgmt-users.properties | tail -n 1
test4=a95aa9d159b7afe0cc9d3795061551ad
[hudson@rhel7-large-9887 bin]$
{noformat}
{noformat}
[hudson@rhel7-large-9887 bin]$ ./appclient.sh -v
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.jboss.logmanager.LogManager$2 (jar:file:/home/hudson/hudson_workspace/workspace/early-testing-scripts-unix/9774dccf/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.9.Final.jar!/) to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogManager$2
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
06:11:52,205 INFO [org.jboss.modules] (main) JBoss Modules version 1.7.0.Final
WildFly Full 13.0.0.Alpha1-SNAPSHOT (WildFly Core 4.0.0.Final)
[hudson@rhel7-large-9887 bin]$
{noformat}
*Expected results:*
No warnings
was:
*Description of the issue:*
Scripts throws "illegal reflective access" warning on JDK9.
*How reproducible:*
Always with JDK9
*Steps to Reproduce:*
* ./jboss-cli.sh "echo test"
* ./add-user.sh -u test4 -p Test123* -s
* ./appclient.sh -v
*Actual results:*
{noformat}
[hudson@rhel7-large-9887 bin]$ java --version
java 9.0.4
Java(TM) SE Runtime Environment (build 9.0.4+11)
Java HotSpot(TM) 64-Bit Server VM (build 9.0.4+11, mixed mode)
[hudson@rhel7-large-9887 bin]$
{noformat}
{noformat}
[hudson@rhel7-large-9887 bin]$ ./jboss-cli.sh "echo test"
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.jboss.logmanager.LogManager$2 (jar:file:/home/hudson/hudson_workspace/workspace/early-testing-scripts-unix/9774dccf/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.9.Final.jar!/) to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogManager$2
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
test
[hudson@rhel7-large-9887 bin]$
{noformat}
{noformat}
[hudson@rhel7-large-9887 bin]$ ./add-user.sh -u test4 -p Test123* -s
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.jboss.logmanager.LogManager$2 (jar:file:/home/hudson/hudson_workspace/workspace/early-testing-scripts-unix/9774dccf/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.9.Final.jar!/) to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogManager$2
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
[hudson@rhel7-large-9887 bin]$ cat ../standalone/configuration/mgmt-users.properties | tail -n 1
test4=a95aa9d159b7afe0cc9d3795061551ad
[hudson@rhel7-large-9887 bin]$
{noformat}
{noformat}
[hudson@rhel7-large-9887 bin]$ ./appclient.sh -v
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.jboss.logmanager.LogManager$2 (jar:file:/home/hudson/hudson_workspace/workspace/early-testing-scripts-unix/9774dccf/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.9.Final.jar!/) to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogManager$2
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
06:11:52,205 INFO [org.jboss.modules] (main) JBoss Modules version 1.7.0.Final
WildFly Full 13.0.0.Alpha1-SNAPSHOT (WildFly Core 4.0.0.Final)
[hudson@rhel7-large-9887 bin]$
{noformat}
*Expected results:*
No warnings
> Scripts throws "illegal reflective access" warning on JDK9
> ----------------------------------------------------------
>
> Key: WFLY-10031
> URL: https://issues.jboss.org/browse/WFLY-10031
> Project: WildFly
> Issue Type: Bug
> Components: Scripts, Security
> Reporter: Marek Kopecký
> Assignee: Darran Lofthouse
> Priority: Blocker
>
> *Description of the issue:*
> Scripts throws "illegal reflective access" warning on JDK9.
> *How reproducible:*
> Always with JDK9
> *Steps to Reproduce:*
> * ./jboss-cli.sh "echo test"
> * ./add-user.sh -u test4 -p Test123* -s
> * ./appclient.sh -v
> * ./wsconsume.sh
> * ./wsprovide.sh
> * ./domain.sh
> * ./standalone.sh
> *Actual results:*
> {noformat}
> [hudson@rhel7-large-9887 bin]$ java --version
> java 9.0.4
> Java(TM) SE Runtime Environment (build 9.0.4+11)
> Java HotSpot(TM) 64-Bit Server VM (build 9.0.4+11, mixed mode)
> [hudson@rhel7-large-9887 bin]$
> {noformat}
> {noformat}
> [hudson@rhel7-large-9887 bin]$ ./jboss-cli.sh "echo test"
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.jboss.logmanager.LogManager$2 (jar:file:/home/hudson/hudson_workspace/workspace/early-testing-scripts-unix/9774dccf/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.9.Final.jar!/) to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
> WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogManager$2
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> test
> [hudson@rhel7-large-9887 bin]$
> {noformat}
> {noformat}
> [hudson@rhel7-large-9887 bin]$ ./add-user.sh -u test4 -p Test123* -s
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.jboss.logmanager.LogManager$2 (jar:file:/home/hudson/hudson_workspace/workspace/early-testing-scripts-unix/9774dccf/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.9.Final.jar!/) to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
> WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogManager$2
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [hudson@rhel7-large-9887 bin]$ cat ../standalone/configuration/mgmt-users.properties | tail -n 1
> test4=a95aa9d159b7afe0cc9d3795061551ad
> [hudson@rhel7-large-9887 bin]$
> {noformat}
> {noformat}
> [hudson@rhel7-large-9887 bin]$ ./appclient.sh -v
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.jboss.logmanager.LogManager$2 (jar:file:/home/hudson/hudson_workspace/workspace/early-testing-scripts-unix/9774dccf/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.9.Final.jar!/) to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
> WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogManager$2
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> 06:11:52,205 INFO [org.jboss.modules] (main) JBoss Modules version 1.7.0.Final
> WildFly Full 13.0.0.Alpha1-SNAPSHOT (WildFly Core 4.0.0.Final)
> [hudson@rhel7-large-9887 bin]$
> {noformat}
> *Expected results:*
> No warnings
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (DROOLS-2390) Use drools-compiler tests to test drools-model-compiler
by Tibor Zimányi (JIRA)
Tibor Zimányi created DROOLS-2390:
-------------------------------------
Summary: Use drools-compiler tests to test drools-model-compiler
Key: DROOLS-2390
URL: https://issues.jboss.org/browse/DROOLS-2390
Project: Drools
Issue Type: Enhancement
Components: core engine
Affects Versions: 7.6.0.Final
Reporter: Tibor Zimányi
Assignee: Tibor Zimányi
We have a large test coverage that could test the executable model compiler.
The problem is we cannot use the tests jar in the executable model, because it will be a circular dependency. One option is to move the tests to an independent module and then parametrize the tests so they test both original and new model compiler.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-10029) bean-discovery-mode="annotated" is not working like described in the spec
by Martin Kouba (JIRA)
[ https://issues.jboss.org/browse/WFLY-10029?page=com.atlassian.jira.plugin... ]
Martin Kouba commented on WFLY-10029:
-------------------------------------
Well, this really depends on where the {{SomeClass}} comes from, i.e. in which bean archive it resides. If it's an implicit bean archive then it's defintely a bug. I did a quick test and it seems the problem occurs if {{SomeClass}} is located in an implicit bean archive with no {{beans.xml}}. In this case, WildFly creates a synthetic beans.xml with {{bean-discovery-mode=all}}.
> bean-discovery-mode="annotated" is not working like described in the spec
> -------------------------------------------------------------------------
>
> Key: WFLY-10029
> URL: https://issues.jboss.org/browse/WFLY-10029
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 10.1.0.Final
> Reporter: Ralph Soika
> Assignee: Martin Kouba
> Priority: Minor
> Labels: beans.xml
>
> I think we have a problem in Wildfly 10 concerning scanning of CDI Beans. Take a look at the following example:
> {code:java}
> @Stateless
> @LocalBean
> public class SomeService {
> ...
> }
> public class SomeClass {
> @EJB
> SomeService someService;
> ....
> }
> {code}
> We have a stateless session ejb an a bean which is not annotated with a scope but is injecting the service EJB. If you use a beans.xml with the tag:
> {noformat}
> bean-discovery-mode="annotated"
> {noformat}
> this works in wildfly 10 - the _someService_ is injected into the _someClass_ which is treated as a CDI bean. But this is not a correct behavior as stated in the specification. It says, that in this case only beans with a scope annotation should be treated as CDI which is not the case for SomeClass. Normally, as a developer, you would not complain much about this. So this is only a minor issue.
> I recognized this after I tried to run my application on Glassfish/Payara4 which did no longer work until I changed the beans.xml tag to:
> {noformat}
> bean-discovery-mode="all"
> {noformat}
> Now it works in both application servers. I think in wildfly we are misinterpreting the attribute "bean-discovery-mode". I think this should be changed in the next versions for EE8. I don't know if this behavior is a known issue and maybe it is still under development.
> I know also that with such a change some projects (also my own ones) will break. So maybe a new configuration switch like "strict-cdi-scanning" is helpful. What do you think?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-9561) HttpServletRequest.login(username, password) not creating HttpSession if it doesn't already exist. (Elytron)
by Stanislav Grushevskiy (JIRA)
[ https://issues.jboss.org/browse/WFLY-9561?page=com.atlassian.jira.plugin.... ]
Stanislav Grushevskiy updated WFLY-9561:
----------------------------------------
Fix Version/s: 12.0.0.Final
> HttpServletRequest.login(username, password) not creating HttpSession if it doesn't already exist. (Elytron)
> ------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9561
> URL: https://issues.jboss.org/browse/WFLY-9561
> Project: WildFly
> Issue Type: Bug
> Components: Security, Web (Undertow)
> Affects Versions: 11.0.0.Final
> Reporter: Stanislav Grushevskiy
> Assignee: Darran Lofthouse
> Fix For: 12.0.0.Final
>
> Attachments: test.zip
>
>
> If Elytron security domain (in WildFly 11, default "standalone.xml") is used for programmatic login, cookie "JSESSIONID" is not set in response. So following requests are sent without "JSESSIONID".
> @Path("login")
> public class LoginService {
> @Context
> private HttpServletRequest request;
> @POST
> public void login(LoginForm form) throws ServletException {
> request.login(form.getLogin(), form.getPassword());
> }
> }
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-web>
> <security-domain>application-security-domain</security-domain>
> </jboss-web>
> If I add manual interaction with Session in login method, "JSESSIONID" is set.
> OR
> If I delete "jboss-web.xml" and default old "ApplicationRealm" is used, "JSESSIONID" is set.
> "JSESSIONID" is set in WildFly 10.0.0.Final and in 10.1.0.Final, because there is no Elytron there and "ApplicationRealm" is used.
> Test project is attached, create application user (add-user.sh) with username "wildfly" and password "wildfly".
> Run "mvn wildfly:deploy".
> Go to http://localhost:8080/test/test.html and press "Login" button and then "Check Auth".
> In this project you can uncomment code below (// uncomment the row below to get it working with elytron) to add session interaction or comment code below (<!-- comment the row below to use default ApplicationRealm from old security system, not elytron -->) to use old "ApplicationRealm".
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFCORE-3568) Allow CLI output scrolling
by Marek Marusic (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3568?page=com.atlassian.jira.plugi... ]
Marek Marusic commented on WFCORE-3568:
---------------------------------------
[~soul2zimate] You can use {{Shift}} + {{PgUp}} / {{PgDn}} to scroll up / down in common terminals like gonem-terminal, terminator etc. That could be useful for You until the issue is fixed.
> Allow CLI output scrolling
> --------------------------
>
> Key: WFCORE-3568
> URL: https://issues.jboss.org/browse/WFCORE-3568
> Project: WildFly Core
> Issue Type: Enhancement
> Components: CLI
> Affects Versions: 4.0.0.Alpha8
> Reporter: Chao Wang
> Assignee: Marek Marusic
>
> Mouse scrolling is forbidden to large CLI out. User has to press {{Down}} or {{Enter}} to navigate.
> It would be nice to allow fast scrolling or {{PgUp}} / {{PgDn}}. e.g.
> {noformat}
> [standalone@localhost:9990 /] /core-service=capability-registry:read-resource
> {
> "outcome" => "success",
> "result" => {
> "capabilities" => [
> {
> "name" => "org.wildfly.batch.configuration",
> "dynamic" => false,
> "scope" => "global",
> "registration-points" => ["/subsystem=batch-jberet"]
> },
> {
> "name" => "org.wildfly.batch.job.repository.in-memory",
> "dynamic" => false,
> "scope" => "global",
> "registration-points" => ["/subsystem=batch-jberet/in-memory-job-repository=in-memory"]
> },
> {
> "name" => "org.wildfly.batch.thread.pool.batch",
> "dynamic" => false,
> "scope" => "global",
> "registration-points" => ["/subsystem=batch-jberet/thread-pool=batch"]
> },
> {
> "name" => "org.wildfly.clustering.cache.default-group.ejb",
> "dynamic" => false,
> "scope" => "global",
> "registration-points" => ["/subsystem=infinispan/cache-container=ejb"]
> },
> {
> "name" => "org.wildfly.clustering.cache.default-group.server",
> "dynamic" => false,
> "scope" => "global",
> "registration-points" => ["/subsystem=infinispan/cache-container=server"]
> },
> {
> "name" => "org.wildfly.clustering.cache.default-group.web",
> "dynamic" => false,
> "scope" => "global",
> "registration-points" => ["/subsystem=infinispan/cache-container=web"]
> },
> {
> "name" => "org.wildfly.clustering.cache.default-node-factory.ejb",
> "dynamic" => false,
> "scope" => "global",
> "registration-points" => ["/subsystem=infinispan/cache-container=ejb"]
> },
> {
> "name" => "org.wildfly.clustering.cache.default-node-factory.server",
> "dynamic" => false,
> --More(2%)--
> {noformat}
> Also, after pressing {{Down}} or {{Enter}} to display more output, user can not press {{up}} to go up. User has to inconveniently use scroll up.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-10032) Wildfly 12 Final (RestEASy 3.5 Final) can't discover JsonBindingProvider for Jax-RS
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/WFLY-10032?page=com.atlassian.jira.plugin... ]
Alessio Soldano updated WFLY-10032:
-----------------------------------
Fix Version/s: 13.0.0.Beta1
> Wildfly 12 Final (RestEASy 3.5 Final) can't discover JsonBindingProvider for Jax-RS
> ------------------------------------------------------------------------------------
>
> Key: WFLY-10032
> URL: https://issues.jboss.org/browse/WFLY-10032
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 12.0.0.Final
> Reporter: Alessandro Moscatelli
> Assignee: Alessio Soldano
> Fix For: 13.0.0.Beta1
>
>
> Even if started in JavaEE8 Preview Mode :
>
> <property name="ee8.preview.mode" value="true"/>
>
> Wildfly 12 + RestEasy 3.5 Final can't find this MessageBodyWriter (or Reader) :
>
> org.jboss.resteasy.plugins.providers.jsonb.JsonBindingProvider
>
> Such is provided inside this dependecy :
>
> <dependency>
> <groupId>org.jboss.resteasy</groupId>
> <artifactId>resteasy-json-binding-provider</artifactId>
> <version>3.5.0.Final</version>
> </dependency>
>
> resteasy-json-binding-provider.jar is already provided inside WIldfly 12.
>
> RestEASY 3.5 Final documentation stats that JsonBindingProvider should be automatically loaded :
>
> RESTEasy JAX-RS
>
> If you forcefully exclude Jackson with NoJackson annotation an error will appear stating no MessageWrite is found for json media type when serializing objects for Jax-RS.
>
> I debugged a little to try and find out what was happening and I can confirm that in
>
> org.jboss.resteasy.spi.ResteasyProviderFactory at row 2592
>
> JsonBindingProvider won't be discovered
>
> Can you reproduce/fix this issue ?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months