[Red Hat JIRA] (WFLY-14156) Remove MicroProfile REST Client from Wildfly ee
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-14156?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-14156:
------------------------------------
Description: The MicroProfile REST Client functionalities are expected to be provided in the full 'wildfly' feature pack only. (was: The MicroProfile REST Client functionalities are expected to be provided in EAP XP only.)
> Remove MicroProfile REST Client from Wildfly ee
> -----------------------------------------------
>
> Key: WFLY-14156
> URL: https://issues.redhat.com/browse/WFLY-14156
> Project: WildFly
> Issue Type: Feature Request
> Components: MP REST Client, REST
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
> Priority: Blocker
> Labels: EAP-CD22
>
> The MicroProfile REST Client functionalities are expected to be provided in the full 'wildfly' feature pack only.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[Red Hat JIRA] (WFLY-14132) jboss-ejb3.xml is ignored for exploded deployments
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-14132?page=com.atlassian.jira.plugi... ]
Brian Stansberry reassigned WFLY-14132:
---------------------------------------
Assignee: Cheng Fang (was: Brian Stansberry)
> jboss-ejb3.xml is ignored for exploded deployments
> --------------------------------------------------
>
> Key: WFLY-14132
> URL: https://issues.redhat.com/browse/WFLY-14132
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 14.0.1.Final, JBoss AS7 7.1.1.Final, 21.0.1.Final
> Reporter: Jan-Willem Gmelig Meyling
> Assignee: Cheng Fang
> Priority: Major
> Labels: ejb-jar.xml, jboss-ejb3.xml
>
> {{EjbJarParsingDeploymentUnitProcessor}} distinguishes between a WAR and JAR deployment based on the file extension of the name of the deployment root. For exploded deployments however, this deployment root may be a folder without any file extension. As a result the logic fails to detect either a JAR or WAR file and the {{ejb-jar.xml}} and {{jboss-ejb3.xml}} files are ignored. A better way could be to determine the extension from the name of {{DeploymentUnit}} instead.
> Code from: [https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jbo...]
> {code:java}
> private static VirtualFile getDescriptor(final VirtualFile deploymentRoot, final String descriptorName) {
> // Locate the descriptor
> final VirtualFile descriptor;
> // EJB 3.1 FR 20.4 Enterprise Beans Packaged in a .war
> if (isWar(deploymentRoot)) {
> // it's a .war file, so look for the ejb-jar.xml in WEB-INF
> descriptor = deploymentRoot.getChild(WEB_INF + "/" + descriptorName);
> } else if (deploymentRoot.getName().toLowerCase(Locale.ENGLISH).endsWith(JAR_FILE_EXTENSION)) {
> descriptor = deploymentRoot.getChild(META_INF + "/" + descriptorName);
> } else {
> // neither a .jar nor a .war. Return
> return null;
> }
> if (descriptor == null || !descriptor.exists()) {
> // no descriptor found, nothing to do!
> return null;
> }
> return descriptor;
> }
> {code}
>
> I encountered this issue on WildFly 14.0.1.Final, but the code is also present in the current master and goes back to versions as early as 7.1.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[Red Hat JIRA] (WFLY-14136) Activate MP Rest Client TCK with -Dts.ee9 profile; resolve failures
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-14136:
---------------------------------------
Summary: Activate MP Rest Client TCK with -Dts.ee9 profile; resolve failures
Key: WFLY-14136
URL: https://issues.redhat.com/browse/WFLY-14136
Project: WildFly
Issue Type: Task
Components: MP REST Client
Reporter: Brian Stansberry
Assignee: Alessio Soldano
When the ee-9 modules were added I thought I had enabled the MP Rest Client TCK when the -Dts.ee9 profile was executed. It turns out I had not. The profile does the various set up work but the default-test surefire execution was not enabled, so the tests aren't actually run. I discovered this when working on WFLY-14049.
I believe 16 test will fail if it is enabled, so part of this task is to sort out what that's about.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months