[JBoss JIRA] (WFLY-11722) Internal Server Error (500) when using directory-listing in FileHandler
by Adam Krajcik (Jira)
Adam Krajcik created WFLY-11722:
-----------------------------------
Summary: Internal Server Error (500) when using directory-listing in FileHandler
Key: WFLY-11722
URL: https://issues.jboss.org/browse/WFLY-11722
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 15.0.1.Final
Reporter: Adam Krajcik
Assignee: Flavia Rainone
When I added a bad symlink to the *welcome-content* and allowed *directory-listing* in the file handler of the welcome-content.
However, no exception is thrown when the Internal Server Error (500) is returned on WildFly.
The following exception is thrown when using _http2_ in _undertow-examples_:
{code}
ava.lang.RuntimeException: java.nio.file.NoSuchFileException: /home/akrajcik/Pictures/pictures
at io.undertow.server.handlers.resource.PathResource.getLastModified(PathResource.java:62)
at io.undertow.server.handlers.resource.DirectoryUtils.renderDirectoryListing(DirectoryUtils.java:139)
at io.undertow.server.handlers.resource.DirectoryUtils.renderDirectoryListing(DirectoryUtils.java:162)
at io.undertow.server.handlers.resource.ResourceHandler$1.handleRequest(ResourceHandler.java:233)
at io.undertow.server.Connectors.executeRootHandler(Connectors.java:364)
at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.lang.Thread.run(Thread.java:811)
Caused by: java.nio.file.NoSuchFileException: /home/akrajcik/Pictures/pictures
at sun.nio.fs.UnixException.translateToIOException(UnixException.java:98)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:114)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:119)
at sun.nio.fs.UnixFileAttributeViews$Basic.readAttributes(UnixFileAttributeViews.java:67)
at sun.nio.fs.UnixFileSystemProvider.readAttributes(UnixFileSystemProvider.java:156)
at sun.nio.fs.LinuxFileSystemProvider.readAttributes(LinuxFileSystemProvider.java:111)
at java.nio.file.Files.readAttributes(Files.java:1748)
at java.nio.file.Files.getLastModifiedTime(Files.java:2277)
at io.undertow.server.handlers.resource.PathResource.getLastModified(PathResource.java:60)
... 8 more
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (WFLY-11723) Internal Server Error (500) when using directory-listing in FileHandler
by Adam Krajcik (Jira)
Adam Krajcik created WFLY-11723:
-----------------------------------
Summary: Internal Server Error (500) when using directory-listing in FileHandler
Key: WFLY-11723
URL: https://issues.jboss.org/browse/WFLY-11723
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 15.0.1.Final
Reporter: Adam Krajcik
Assignee: Flavia Rainone
When I added a bad symlink to the *welcome-content* and allowed *directory-listing* in the file handler of the welcome-content.
However, no exception is thrown when the Internal Server Error (500) is returned on WildFly.
The following exception is thrown when using _http2_ in _undertow-examples_:
{code}
ava.lang.RuntimeException: java.nio.file.NoSuchFileException: /home/akrajcik/Pictures/pictures
at io.undertow.server.handlers.resource.PathResource.getLastModified(PathResource.java:62)
at io.undertow.server.handlers.resource.DirectoryUtils.renderDirectoryListing(DirectoryUtils.java:139)
at io.undertow.server.handlers.resource.DirectoryUtils.renderDirectoryListing(DirectoryUtils.java:162)
at io.undertow.server.handlers.resource.ResourceHandler$1.handleRequest(ResourceHandler.java:233)
at io.undertow.server.Connectors.executeRootHandler(Connectors.java:364)
at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.lang.Thread.run(Thread.java:811)
Caused by: java.nio.file.NoSuchFileException: /home/akrajcik/Pictures/pictures
at sun.nio.fs.UnixException.translateToIOException(UnixException.java:98)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:114)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:119)
at sun.nio.fs.UnixFileAttributeViews$Basic.readAttributes(UnixFileAttributeViews.java:67)
at sun.nio.fs.UnixFileSystemProvider.readAttributes(UnixFileSystemProvider.java:156)
at sun.nio.fs.LinuxFileSystemProvider.readAttributes(LinuxFileSystemProvider.java:111)
at java.nio.file.Files.readAttributes(Files.java:1748)
at java.nio.file.Files.getLastModifiedTime(Files.java:2277)
at io.undertow.server.handlers.resource.PathResource.getLastModified(PathResource.java:60)
... 8 more
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (WFLY-11719) Redo how we test mod_cluster transformers to improve test coverage
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFLY-11719?page=com.atlassian.jira.plugin... ]
Radoslav Husar updated WFLY-11719:
----------------------------------
Description:
The typical way subsystems test transformers is with a single transform xml file which contains all *transformable* attributes and resources to the oldest version (EAP 6.4 atm). However, as subsystems evolve certain attributes are not transformable *but* are missing from subsequent test coverage. For instance, attribute not present in EAP 6.4, but available since 7.0: the tests for EAP 7.1 could still test the transformation to EAP 7.0 but this is typically missed in the subsystems test coverage.
The solution is to use a specific file for *each* EAP controller version we are transforming to.
was:
The typical way subsystems test transformers is with a single transform xml file which contains all *transformable* attributes and resources. However, as subsystems evolve certain attributes are not transformable *but* are missing from later test coverage; e.g. attribute not present in EAP 6.4, but available since 7.0, the tests for EAP 7.1 could still test the tranformation to EAP 7.0 while this is typically missed in the subsystems test coverage.
The solution is to use a specific file for *each* EAP controller version we are transforming to.
> Redo how we test mod_cluster transformers to improve test coverage
> ------------------------------------------------------------------
>
> Key: WFLY-11719
> URL: https://issues.jboss.org/browse/WFLY-11719
> Project: WildFly
> Issue Type: Task
> Components: mod_cluster
> Affects Versions: 16.0.0.Beta1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Major
>
> The typical way subsystems test transformers is with a single transform xml file which contains all *transformable* attributes and resources to the oldest version (EAP 6.4 atm). However, as subsystems evolve certain attributes are not transformable *but* are missing from subsequent test coverage. For instance, attribute not present in EAP 6.4, but available since 7.0: the tests for EAP 7.1 could still test the transformation to EAP 7.0 but this is typically missed in the subsystems test coverage.
> The solution is to use a specific file for *each* EAP controller version we are transforming to.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (WFLY-11719) Redo how we test mod_cluster transformers to improve test coverage
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFLY-11719?page=com.atlassian.jira.plugin... ]
Radoslav Husar updated WFLY-11719:
----------------------------------
Description:
The typical way subsystems test transformers is with a single transform xml file which contains all *transformable* attributes and resources to the oldest version (EAP 6.4 at the moment). However, as subsystems evolve certain attributes are not transformable *but* are missing from subsequent test coverage. For instance, attribute not present in EAP 6.4, but available since 7.0: the tests for EAP 7.1 could still test the transformation to EAP 7.0 but this is typically missed in the subsystems test coverage.
The solution is to use a specific file for *each* EAP controller version we are transforming to.
was:
The typical way subsystems test transformers is with a single transform xml file which contains all *transformable* attributes and resources to the oldest version (EAP 6.4 atm). However, as subsystems evolve certain attributes are not transformable *but* are missing from subsequent test coverage. For instance, attribute not present in EAP 6.4, but available since 7.0: the tests for EAP 7.1 could still test the transformation to EAP 7.0 but this is typically missed in the subsystems test coverage.
The solution is to use a specific file for *each* EAP controller version we are transforming to.
> Redo how we test mod_cluster transformers to improve test coverage
> ------------------------------------------------------------------
>
> Key: WFLY-11719
> URL: https://issues.jboss.org/browse/WFLY-11719
> Project: WildFly
> Issue Type: Task
> Components: mod_cluster
> Affects Versions: 16.0.0.Beta1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Major
>
> The typical way subsystems test transformers is with a single transform xml file which contains all *transformable* attributes and resources to the oldest version (EAP 6.4 at the moment). However, as subsystems evolve certain attributes are not transformable *but* are missing from subsequent test coverage. For instance, attribute not present in EAP 6.4, but available since 7.0: the tests for EAP 7.1 could still test the transformation to EAP 7.0 but this is typically missed in the subsystems test coverage.
> The solution is to use a specific file for *each* EAP controller version we are transforming to.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (WFLY-11720) Cannot invoke EJB over HTTP on JDK 11
by Jan Kašík (Jira)
[ https://issues.jboss.org/browse/WFLY-11720?page=com.atlassian.jira.plugin... ]
Jan Kašík updated WFLY-11720:
-----------------------------
Tester: Jan Kašík
> Cannot invoke EJB over HTTP on JDK 11
> -------------------------------------
>
> Key: WFLY-11720
> URL: https://issues.jboss.org/browse/WFLY-11720
> Project: WildFly
> Issue Type: Bug
> Components: Remoting
> Affects Versions: 16.0.0.Beta1
> Environment: JDK 11
> Reporter: Jan Kašík
> Priority: Major
>
> Run of client app calling EJB over HTTP fails on JDK 11 with following log:
> {noformat}
> Feb 14, 2019 12:49:30 PM org.wildfly.naming.client.Version <clinit>
> INFO: WildFly Naming version 1.0.6.Final
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.wildfly.security.manager.GetAccessibleDeclaredFieldAction (file:/home/hudson/hudson_workspace/mod_cluster/client/wildfly-elytron-1.1.3.Final.jar) to field java.security.AccessControlContext.context
> WARNING: Please consider reporting this to the maintainers of org.wildfly.security.manager.GetAccessibleDeclaredFieldAction
> 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
> Feb 14, 2019 12:49:30 PM org.wildfly.security.Version <clinit>
> INFO: ELY00001: WildFly Elytron version 1.1.3.Final
> Feb 14, 2019 12:49:30 PM org.jboss.ejb.client.EJBClient <clinit>
> INFO: JBoss EJB Client version 4.0.2.Final
> Feb 14, 2019 12:49:30 PM org.xnio.Xnio <clinit>
> INFO: XNIO version 3.6.5.Final
> Feb 14, 2019 12:49:30 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.6.5.Final
> Feb 14, 2019 12:49:30 PM org.jboss.threads.Version <clinit>
> INFO: JBoss Threads version 2.3.0.Beta2
> Feb 14, 2019 12:49:30 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 5.0.0.Final
> Feb 14, 2019 12:49:30 PM org.jboss.threads.LoggingUncaughtExceptionHandler uncaughtException
> ERROR: Thread Thread[XNIO-1 task-1,5,main] threw an uncaught exception
> java.lang.ExceptionInInitializerError
> at org.jboss.marshalling.river.RiverMarshaller.<clinit>(RiverMarshaller.java:1335)
> at org.jboss.marshalling.river.RiverMarshallerFactory.createMarshaller(RiverMarshallerFactory.java:54)
> at org.wildfly.httpclient.common.HttpTargetContext.createMarshaller(HttpTargetContext.java:132)
> at org.wildfly.httpclient.ejb.HttpEJBReceiver.marshalEJBRequest(HttpEJBReceiver.java:367)
> at org.wildfly.httpclient.ejb.HttpEJBReceiver.lambda$processInvocation$1(HttpEJBReceiver.java:185)
> at org.wildfly.httpclient.common.HttpTargetContext$1.lambda$completed$0(HttpTargetContext.java:338)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1871)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1400)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.lang.IllegalStateException: No standard field found for reverse order comparator!
> at org.jboss.marshalling.river.Protocol.<clinit>(Protocol.java:287)
> ... 9 more
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (WFLY-11719) Redo how we test mod_cluster transformers to improve test coverage
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFLY-11719?page=com.atlassian.jira.plugin... ]
Radoslav Husar updated WFLY-11719:
----------------------------------
Summary: Redo how we test mod_cluster transformers to improve test coverage (was: Improve mod_cluster transformer test coverage)
> Redo how we test mod_cluster transformers to improve test coverage
> ------------------------------------------------------------------
>
> Key: WFLY-11719
> URL: https://issues.jboss.org/browse/WFLY-11719
> Project: WildFly
> Issue Type: Task
> Components: mod_cluster
> Affects Versions: 16.0.0.Beta1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Major
>
> The typical way subsystems test transformers is with a single transform xml file which contains all *transformable* attributes and resources. However, as subsystems evolve certain attributes are not transformable *but* are missing from later test coverage; e.g. attribute not present in EAP 6.4, but available since 7.0, the tests for EAP 7.1 could still test the tranformation to EAP 7.0 while this is typically missed in the subsystems test coverage.
> The solution is to use a specific file for *each* EAP controller version we are transforming to.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (WFLY-11721) Cannot invoke EJB over HTTP on JDK 11
by Jan Kašík (Jira)
Jan Kašík created WFLY-11721:
--------------------------------
Summary: Cannot invoke EJB over HTTP on JDK 11
Key: WFLY-11721
URL: https://issues.jboss.org/browse/WFLY-11721
Project: WildFly
Issue Type: Bug
Components: Remoting
Affects Versions: 16.0.0.Beta1
Environment: JDK 11
Reporter: Jan Kašík
Run of client app calling EJB over HTTP fails on JDK 11 with following log:
{noformat}
Feb 14, 2019 12:49:30 PM org.wildfly.naming.client.Version <clinit>
INFO: WildFly Naming version 1.0.6.Final
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.wildfly.security.manager.GetAccessibleDeclaredFieldAction (file:/home/hudson/hudson_workspace/mod_cluster/client/wildfly-elytron-1.1.3.Final.jar) to field java.security.AccessControlContext.context
WARNING: Please consider reporting this to the maintainers of org.wildfly.security.manager.GetAccessibleDeclaredFieldAction
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
Feb 14, 2019 12:49:30 PM org.wildfly.security.Version <clinit>
INFO: ELY00001: WildFly Elytron version 1.1.3.Final
Feb 14, 2019 12:49:30 PM org.jboss.ejb.client.EJBClient <clinit>
INFO: JBoss EJB Client version 4.0.2.Final
Feb 14, 2019 12:49:30 PM org.xnio.Xnio <clinit>
INFO: XNIO version 3.6.5.Final
Feb 14, 2019 12:49:30 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.6.5.Final
Feb 14, 2019 12:49:30 PM org.jboss.threads.Version <clinit>
INFO: JBoss Threads version 2.3.0.Beta2
Feb 14, 2019 12:49:30 PM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 5.0.0.Final
Feb 14, 2019 12:49:30 PM org.jboss.threads.LoggingUncaughtExceptionHandler uncaughtException
ERROR: Thread Thread[XNIO-1 task-1,5,main] threw an uncaught exception
java.lang.ExceptionInInitializerError
at org.jboss.marshalling.river.RiverMarshaller.<clinit>(RiverMarshaller.java:1335)
at org.jboss.marshalling.river.RiverMarshallerFactory.createMarshaller(RiverMarshallerFactory.java:54)
at org.wildfly.httpclient.common.HttpTargetContext.createMarshaller(HttpTargetContext.java:132)
at org.wildfly.httpclient.ejb.HttpEJBReceiver.marshalEJBRequest(HttpEJBReceiver.java:367)
at org.wildfly.httpclient.ejb.HttpEJBReceiver.lambda$processInvocation$1(HttpEJBReceiver.java:185)
at org.wildfly.httpclient.common.HttpTargetContext$1.lambda$completed$0(HttpTargetContext.java:338)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1871)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1400)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: java.lang.IllegalStateException: No standard field found for reverse order comparator!
at org.jboss.marshalling.river.Protocol.<clinit>(Protocol.java:287)
... 9 more
{noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (WFLY-11720) Cannot invoke EJB over HTTP on JDK 11
by Jan Kašík (Jira)
Jan Kašík created WFLY-11720:
--------------------------------
Summary: Cannot invoke EJB over HTTP on JDK 11
Key: WFLY-11720
URL: https://issues.jboss.org/browse/WFLY-11720
Project: WildFly
Issue Type: Bug
Components: Remoting
Affects Versions: 16.0.0.Beta1
Environment: JDK 11
Reporter: Jan Kašík
Run of client app calling EJB over HTTP fails on JDK 11 with following log:
{noformat}
Feb 14, 2019 12:49:30 PM org.wildfly.naming.client.Version <clinit>
INFO: WildFly Naming version 1.0.6.Final
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.wildfly.security.manager.GetAccessibleDeclaredFieldAction (file:/home/hudson/hudson_workspace/mod_cluster/client/wildfly-elytron-1.1.3.Final.jar) to field java.security.AccessControlContext.context
WARNING: Please consider reporting this to the maintainers of org.wildfly.security.manager.GetAccessibleDeclaredFieldAction
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
Feb 14, 2019 12:49:30 PM org.wildfly.security.Version <clinit>
INFO: ELY00001: WildFly Elytron version 1.1.3.Final
Feb 14, 2019 12:49:30 PM org.jboss.ejb.client.EJBClient <clinit>
INFO: JBoss EJB Client version 4.0.2.Final
Feb 14, 2019 12:49:30 PM org.xnio.Xnio <clinit>
INFO: XNIO version 3.6.5.Final
Feb 14, 2019 12:49:30 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.6.5.Final
Feb 14, 2019 12:49:30 PM org.jboss.threads.Version <clinit>
INFO: JBoss Threads version 2.3.0.Beta2
Feb 14, 2019 12:49:30 PM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 5.0.0.Final
Feb 14, 2019 12:49:30 PM org.jboss.threads.LoggingUncaughtExceptionHandler uncaughtException
ERROR: Thread Thread[XNIO-1 task-1,5,main] threw an uncaught exception
java.lang.ExceptionInInitializerError
at org.jboss.marshalling.river.RiverMarshaller.<clinit>(RiverMarshaller.java:1335)
at org.jboss.marshalling.river.RiverMarshallerFactory.createMarshaller(RiverMarshallerFactory.java:54)
at org.wildfly.httpclient.common.HttpTargetContext.createMarshaller(HttpTargetContext.java:132)
at org.wildfly.httpclient.ejb.HttpEJBReceiver.marshalEJBRequest(HttpEJBReceiver.java:367)
at org.wildfly.httpclient.ejb.HttpEJBReceiver.lambda$processInvocation$1(HttpEJBReceiver.java:185)
at org.wildfly.httpclient.common.HttpTargetContext$1.lambda$completed$0(HttpTargetContext.java:338)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1871)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1400)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: java.lang.IllegalStateException: No standard field found for reverse order comparator!
at org.jboss.marshalling.river.Protocol.<clinit>(Protocol.java:287)
... 9 more
{noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (WFLY-11719) Improve mod_cluster transformer test coverage
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFLY-11719?page=com.atlassian.jira.plugin... ]
Radoslav Husar updated WFLY-11719:
----------------------------------
Description:
The typical way subsystems test transformers is with a single transform xml file which contains all *transformable* attributes and resources. However, as subsystems evolve certain attributes are not transformable *but* are missing from later test coverage; e.g. attribute not present in EAP 6.4, but available since 7.0, the tests for EAP 7.1 could still test the tranformation to EAP 7.0 while this is typically missed in the subsystems test coverage.
The solution is to use a specific file for *each* EAP controller version we are transforming to.
was:
The typical way subsystems test transformers is with a single transform xml file which contains all *transformable* attributes and resources. However, as subsystems evolve certain attributes are not transformable *but* are missing from later test coverage; e.g. attribute not present in EAP 6.4, but available since 7.0, the tests for EAP 7.1 could still test the tranformation to EAP 7.0 while this is typically missed in the test coverage.
The solution is to use a specific file for *each* EAP controller version we are transforming to.
> Improve mod_cluster transformer test coverage
> ---------------------------------------------
>
> Key: WFLY-11719
> URL: https://issues.jboss.org/browse/WFLY-11719
> Project: WildFly
> Issue Type: Task
> Components: mod_cluster
> Affects Versions: 16.0.0.Beta1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Major
>
> The typical way subsystems test transformers is with a single transform xml file which contains all *transformable* attributes and resources. However, as subsystems evolve certain attributes are not transformable *but* are missing from later test coverage; e.g. attribute not present in EAP 6.4, but available since 7.0, the tests for EAP 7.1 could still test the tranformation to EAP 7.0 while this is typically missed in the subsystems test coverage.
> The solution is to use a specific file for *each* EAP controller version we are transforming to.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (WFLY-11719) Improve mod_cluster transformer test coverage
by Radoslav Husar (Jira)
Radoslav Husar created WFLY-11719:
-------------------------------------
Summary: Improve mod_cluster transformer test coverage
Key: WFLY-11719
URL: https://issues.jboss.org/browse/WFLY-11719
Project: WildFly
Issue Type: Task
Components: mod_cluster
Affects Versions: 16.0.0.Beta1
Reporter: Radoslav Husar
Assignee: Radoslav Husar
The typical way subsystems test transformers is with a single transform xml file which contains all *transformable* attributes and resources. However, as subsystems evolve certain attributes are not transformable *but* are missing from later test coverage; e.g. attribute not present in EAP 6.4, but available since 7.0, the tests for EAP 7.1 could still test the tranformation to EAP 7.0 while this is typically missed in the test coverage.
The solution is to use a specific file for *each* EAP controller version we are transforming to.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months