Skip to content

Instantly share code, notes, and snippets.

@jwmatthews

jwmatthews/output.yaml

Created June 13, 2024 16:25
Show Gist options
  • Save jwmatthews/fbef32a1995fd85aaa8a9f7553283bf0 to your computer and use it in GitHub Desktop.
Save jwmatthews/fbef32a1995fd85aaa8a9f7553283bf0 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
output.yaml
- name: azure/springboot
description: Recommend OpenFeign instead of Feign.
violations:
spring-boot-to-azure-static-content-01000:
description: Static content found in the application
category: optional
labels:
- konveyor.io/source=springboot
- konveyor.io/target=azure-aks
- konveyor.io/target=azure-appservice
- konveyor.io/target=azure-container-apps
- konveyor.io/target=azure-spring-apps
- static-content
incidents:
- uri: file:///opt/input/source/README.html
message: "Your application currently serves static content, you'll need an alternate location for it. You may wish to consider moving static content to Azure Blob Storage and adding Azure CDN for lightning-fast downloads globally.\n \n For more information, see Static website hosting in Azure Storage and Quickstart: Integrate an Azure storage account with Azure CDN."
links:
- url: https://docs.microsoft.com/azure/cdn/cdn-create-a-storage-account-with-cdn
title: 'Quickstart: Integrate an Azure Storage account with Azure CDN'
- url: https://learn.microsoft.com/azure/developer/java/migration/migrate-spring-boot-to-azure-spring-apps#read-only-static-content
title: Static content found in the application
- url: https://docs.microsoft.com/azure/storage/blobs/storage-blob-static-website
title: Static website hosting in Azure Storage
effort: 5
unmatched:
- azure-aws-config-credential-01000
- azure-aws-config-region-02000
- azure-aws-config-s3-03000
- azure-aws-config-secret-manager-05000
- azure-aws-config-sqs-04000
- azure-file-system-01000
- azure-file-system-02000
- azure-file-system-03000
- azure-java-version-01000
- azure-java-version-02000
- azure-logging-0000
- azure-logging-0000
- azure-os-specific-00001
- azure-os-specific-00002
- azure-password-01000
- eap-to-azure-appservice-certificates-001
- eap-to-azure-appservice-certificates-001
- eap-to-azure-appservice-datasource-driver-01000
- eap-to-azure-appservice-environment-variables-001
- eap-to-azure-appservice-pom-001
- spring-boot-to-azure-cache-redis-01000
- spring-boot-to-azure-cache-redis-02000
- spring-boot-to-azure-config-server-01000
- spring-boot-to-azure-database-jdbc-01000
- spring-boot-to-azure-database-mongodb-02000
- spring-boot-to-azure-database-r2dbc-03000
- spring-boot-to-azure-eureka-01000
- spring-boot-to-azure-eureka-02000
- spring-boot-to-azure-feign-01000
- spring-boot-to-azure-identity-provider-01000
- spring-boot-to-azure-java-fx-01000
- spring-boot-to-azure-jks-01000
- spring-boot-to-azure-jms-broker-01000
- spring-boot-to-azure-mq-config-artemis-01000
- spring-boot-to-azure-mq-config-kafka-01000
- spring-boot-to-azure-mq-config-rabbitmq-01000
- spring-boot-to-azure-mq-config-rabbitmq-01000
- spring-boot-to-azure-port-01000
- spring-boot-to-azure-schedule-job-01000
- spring-boot-to-azure-swing-01000
- spring-boot-to-azure-system-config-01000
- spring-boot-to-azure-version-01000
- spring-boot-to-azure-version-02000
- spring-boot-to-azure-version-03000
- spring-boot-to-azure-zipkin-01000
- spring-cloud-to-azure-version-01000
- spring-cloud-to-azure-version-02000
- spring-cloud-to-azure-version-03000
- tomcat-to-azure-external-resources-01000
- name: camel3
description: Rules for changes between Camel 3.0 and Camel 4.0
unmatched:
- xml-changed-camel41-00003
- xml-changed-camel41-00004
- xml-changed-camel41-00005
- xml-changed-camel41-00006
- xml-changed-camel41-00007
- xml-changed-camel41-00008
- xml-changed-camel41-00009
- xml-changed-camel41-00010
- xml-changed-camel41-00011
- xml-changed-camel41-00012
- xml-changed-camel41-00013
- xml-changed-camel41-00014
- xml-changed-camel41-00015
- xml-changedcomponent-camel4-00001
- xml-changedcomponent-camel4-00002
- xml-removed-camel4-00001
- xml-removed-camel4-00002
- xml-removed-camel4-00003
- xml-removed-camel4-00004
- xml-removed-camel4-00005
- xml-removed-camel4-00006
- xml-removed-camel4-00007
- xml-removed-camel4-00008
- xml-removed-camel4-00010
- xml-removed-camel4-00011
- xml-removed-camel4-00012
- xml-removed-camel4-00013
- xml-removed-camel4-00014
- xml-removed-camel4-00015
- xml-removed-camel4-00016
- xml-removed-camel4-00017
- xml-removed-camel4-00018
- xml-removed-camel4-00019
- xml-removed-camel4-00020
- xml-removed-camel4-00021
- xml-removed-camel4-00022
- xml-removed-camel4-00023
- xml-removed-camel4-00024
- xml-removed-camel4-00025
- xml-removed-camel4-00026
- xml-removed-camel4-00027
- xml-removed-camel4-00028
- xml-removed-camel4-00029
- xml-removed-camel4-00030
- xml-removed-camel4-00031
- xml-removed-camel4-00032
- xml-removed-camel4-00033
- xml-removed-camel4-00034
- xml-removed-camel41-00000
- xml-removed-camel41-00001
- xml-removed-camel41-00002
- xml-removed-camel41-00016
- xml-removed-camel41-00017
- xml-removed-camel41-00018
- name: camel3/camel2
description: Rules for changes in XML file (e.g. pom.xml) to run on Apache Camel 3
violations:
xml-java-versions-00001:
description: '''jaxb-api'' Maven dependency missing'
category: potential
labels:
- konveyor.io/source=camel
- konveyor.io/source=camel2
- konveyor.io/target=camel
- konveyor.io/target=camel3+
incidents:
- uri: file:///opt/input/source/client/pom.xml
message: |-
`jaxb-api` Maven dependency missing.
Apache Camel 3 supports Java 11 and in this Java version JAXB modules have been removed from the JDK, therefore you will need to add them as Maven dependencies since there are couple of components rely on them:
```Xml
<dependency>
<groupId>javax.xml.bind</groupId>
<artifactId>jaxb-api</artifactId>
<version>2.3.1</version>
</dependency>
```
codeSnip: "35 \n36 <dependencies>\n37 <!-- The EJB Client BOM provides application server-compatible dependency management,\n38 used for building, testing or debugging EJB client applications. Import the BOM to the\n39 dependency management section of the app's pom.xml file and then set dependencies on specific artifacts.\n40 Alternatively, as shown in the following example, set a single dependency on the BOM for the app to depend\n41 on all the artifacts it manages.\n42 -->\n43 <dependency>\n44 <groupId>org.jboss.eap</groupId>\n45 <artifactId>wildfly-ejb-client-bom</artifactId>\n46 <type>pom</type>\n47 <scope>compile</scope>\n48 </dependency>\n49 \n50 <!-- We depend on the EJB remote business interfaces of this application -->\n51 <dependency>\n52 <groupId>${project.groupId}</groupId>\n53 <artifactId>ejb-remote-server-side</artifactId>\n54 <version>${project.version}</version>\n55 <type>ejb-client</type>"
lineNumber: 44
variables:
data: dependencies
innerText: "\n \n \n org.jboss.eap\n wildfly-ejb-client-bom\n pom\n compile\n \n\n \n \n ${project.groupId}\n ejb-remote-server-side\n ${project.version}\n ejb-client\n \n\n "
matchingXML: |-
<!-- The EJB Client BOM provides application server-compatible dependency management,
used for building, testing or debugging EJB client applications. Import the BOM to the
dependency management section of the app's pom.xml file and then set dependencies on specific artifacts.
Alternatively, as shown in the following example, set a single dependency on the BOM for the app to depend
on all the artifacts it manages.
--><dependency><groupId>org.jboss.eap</groupId><artifactId>wildfly-ejb-client-bom</artifactId><type>pom</type><scope>compile</scope></dependency><!-- We depend on the EJB remote business interfaces of this application --><dependency><groupId>${project.groupId}</groupId><artifactId>ejb-remote-server-side</artifactId><version>${project.version}</version><type>ejb-client</type></dependency>
- uri: file:///opt/input/source/server-side/pom.xml
message: |-
`jaxb-api` Maven dependency missing.
Apache Camel 3 supports Java 11 and in this Java version JAXB modules have been removed from the JDK, therefore you will need to add them as Maven dependencies since there are couple of components rely on them:
```Xml
<dependency>
<groupId>javax.xml.bind</groupId>
<artifactId>jaxb-api</artifactId>
<version>2.3.1</version>
</dependency>
```
codeSnip: "34 <url>http://www.apache.org/licenses/LICENSE-2.0.html</url>\n35 <distribution>repo</distribution>\n36 </license>\n37 </licenses>\n38 \n39 <dependencies>\n40 \n41 <!-- Import the Common Annotations API (JSR-250), we use provided scope\n42 as the API is included in JBoss EAP -->\n43 <dependency>\n44 <groupId>org.jboss.spec.javax.annotation</groupId>\n45 <artifactId>jboss-annotations-api_1.3_spec</artifactId>\n46 <scope>provided</scope>\n47 </dependency>\n48 \n49 <!-- Import the EJB API, we use provided scope as the API is included in JBoss EAP -->\n50 <dependency>\n51 <groupId>org.jboss.spec.javax.ejb</groupId>\n52 <artifactId>jboss-ejb-api_3.2_spec</artifactId>\n53 <scope>provided</scope>\n54 </dependency>"
lineNumber: 43
variables:
data: dependencies
innerText: "\n\n \n \n org.jboss.spec.javax.annotation\n jboss-annotations-api_1.3_spec\n provided\n \n\n \n \n org.jboss.spec.javax.ejb\n jboss-ejb-api_3.2_spec\n provided\n \n\n "
matchingXML: |-
<!-- Import the Common Annotations API (JSR-250), we use provided scope
as the API is included in JBoss EAP --><dependency><groupId>org.jboss.spec.javax.annotation</groupId><artifactId>jboss-annotations-api_1.3_spec</artifactId><scope>provided</scope></dependency><!-- Import the EJB API, we use provided scope as the API is included in JBoss EAP --><dependency><groupId>org.jboss.spec.javax.ejb</groupId><artifactId>jboss-ejb-api_3.2_spec</artifactId><scope>provided</scope></dependency>
links:
- url: https://camel.apache.org/manual/latest/camel-3-migration-guide.html#_java_versions
title: 'Camel 3 - Migration Guide: Java Versions'
effort: 1
xml-java-versions-00002:
description: '''jaxb-core'' Maven dependency missing'
category: potential
labels:
- konveyor.io/source=camel
- konveyor.io/source=camel2
- konveyor.io/target=camel
- konveyor.io/target=camel3+
incidents:
- uri: file:///opt/input/source/client/pom.xml
message: |-
`jaxb-core` Maven dependency missing.
Apache Camel 3 supports Java 11 and in this Java version JAXB modules have been removed from the JDK, therefore you will need to add them as Maven dependencies since there are couple of components rely on them:
```Xml
<dependency>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-core</artifactId>
<version>2.3.0.1</version>
</dependency>
```
codeSnip: "35 \n36 <dependencies>\n37 <!-- The EJB Client BOM provides application server-compatible dependency management,\n38 used for building, testing or debugging EJB client applications. Import the BOM to the\n39 dependency management section of the app's pom.xml file and then set dependencies on specific artifacts.\n40 Alternatively, as shown in the following example, set a single dependency on the BOM for the app to depend\n41 on all the artifacts it manages.\n42 -->\n43 <dependency>\n44 <groupId>org.jboss.eap</groupId>\n45 <artifactId>wildfly-ejb-client-bom</artifactId>\n46 <type>pom</type>\n47 <scope>compile</scope>\n48 </dependency>\n49 \n50 <!-- We depend on the EJB remote business interfaces of this application -->\n51 <dependency>\n52 <groupId>${project.groupId}</groupId>\n53 <artifactId>ejb-remote-server-side</artifactId>\n54 <version>${project.version}</version>\n55 <type>ejb-client</type>"
lineNumber: 44
variables:
data: dependencies
innerText: "\n \n \n org.jboss.eap\n wildfly-ejb-client-bom\n pom\n compile\n \n\n \n \n ${project.groupId}\n ejb-remote-server-side\n ${project.version}\n ejb-client\n \n\n "
matchingXML: |-
<!-- The EJB Client BOM provides application server-compatible dependency management,
used for building, testing or debugging EJB client applications. Import the BOM to the
dependency management section of the app's pom.xml file and then set dependencies on specific artifacts.
Alternatively, as shown in the following example, set a single dependency on the BOM for the app to depend
on all the artifacts it manages.
--><dependency><groupId>org.jboss.eap</groupId><artifactId>wildfly-ejb-client-bom</artifactId><type>pom</type><scope>compile</scope></dependency><!-- We depend on the EJB remote business interfaces of this application --><dependency><groupId>${project.groupId}</groupId><artifactId>ejb-remote-server-side</artifactId><version>${project.version}</version><type>ejb-client</type></dependency>
- uri: file:///opt/input/source/server-side/pom.xml
message: |-
`jaxb-core` Maven dependency missing.
Apache Camel 3 supports Java 11 and in this Java version JAXB modules have been removed from the JDK, therefore you will need to add them as Maven dependencies since there are couple of components rely on them:
```Xml
<dependency>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-core</artifactId>
<version>2.3.0.1</version>
</dependency>
```
codeSnip: "34 <url>http://www.apache.org/licenses/LICENSE-2.0.html</url>\n35 <distribution>repo</distribution>\n36 </license>\n37 </licenses>\n38 \n39 <dependencies>\n40 \n41 <!-- Import the Common Annotations API (JSR-250), we use provided scope\n42 as the API is included in JBoss EAP -->\n43 <dependency>\n44 <groupId>org.jboss.spec.javax.annotation</groupId>\n45 <artifactId>jboss-annotations-api_1.3_spec</artifactId>\n46 <scope>provided</scope>\n47 </dependency>\n48 \n49 <!-- Import the EJB API, we use provided scope as the API is included in JBoss EAP -->\n50 <dependency>\n51 <groupId>org.jboss.spec.javax.ejb</groupId>\n52 <artifactId>jboss-ejb-api_3.2_spec</artifactId>\n53 <scope>provided</scope>\n54 </dependency>"
lineNumber: 43
variables:
data: dependencies
innerText: "\n\n \n \n org.jboss.spec.javax.annotation\n jboss-annotations-api_1.3_spec\n provided\n \n\n \n \n org.jboss.spec.javax.ejb\n jboss-ejb-api_3.2_spec\n provided\n \n\n "
matchingXML: |-
<!-- Import the Common Annotations API (JSR-250), we use provided scope
as the API is included in JBoss EAP --><dependency><groupId>org.jboss.spec.javax.annotation</groupId><artifactId>jboss-annotations-api_1.3_spec</artifactId><scope>provided</scope></dependency><!-- Import the EJB API, we use provided scope as the API is included in JBoss EAP --><dependency><groupId>org.jboss.spec.javax.ejb</groupId><artifactId>jboss-ejb-api_3.2_spec</artifactId><scope>provided</scope></dependency>
links:
- url: https://camel.apache.org/manual/latest/camel-3-migration-guide.html#_java_versions
title: 'Camel 3 - Migration Guide: Java Versions'
effort: 1
xml-java-versions-00003:
description: '''jaxb-impl'' Maven dependency missing'
category: potential
labels:
- konveyor.io/source=camel
- konveyor.io/source=camel2
- konveyor.io/target=camel
- konveyor.io/target=camel3+
incidents:
- uri: file:///opt/input/source/client/pom.xml
message: |-
`jaxb-impl` Maven dependency missing.
Apache Camel 3 supports Java 11 and in this Java version JAXB modules have been removed from the JDK, therefore you will need to add them as Maven dependencies since there are couple of components rely on them:
```Xml
<dependency>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-impl</artifactId>
<version>2.3.2</version>
</dependency>
```
codeSnip: "35 \n36 <dependencies>\n37 <!-- The EJB Client BOM provides application server-compatible dependency management,\n38 used for building, testing or debugging EJB client applications. Import the BOM to the\n39 dependency management section of the app's pom.xml file and then set dependencies on specific artifacts.\n40 Alternatively, as shown in the following example, set a single dependency on the BOM for the app to depend\n41 on all the artifacts it manages.\n42 -->\n43 <dependency>\n44 <groupId>org.jboss.eap</groupId>\n45 <artifactId>wildfly-ejb-client-bom</artifactId>\n46 <type>pom</type>\n47 <scope>compile</scope>\n48 </dependency>\n49 \n50 <!-- We depend on the EJB remote business interfaces of this application -->\n51 <dependency>\n52 <groupId>${project.groupId}</groupId>\n53 <artifactId>ejb-remote-server-side</artifactId>\n54 <version>${project.version}</version>\n55 <type>ejb-client</type>"
lineNumber: 44
variables:
data: dependencies
innerText: "\n \n \n org.jboss.eap\n wildfly-ejb-client-bom\n pom\n compile\n \n\n \n \n ${project.groupId}\n ejb-remote-server-side\n ${project.version}\n ejb-client\n \n\n "
matchingXML: |-
<!-- The EJB Client BOM provides application server-compatible dependency management,
used for building, testing or debugging EJB client applications. Import the BOM to the
dependency management section of the app's pom.xml file and then set dependencies on specific artifacts.
Alternatively, as shown in the following example, set a single dependency on the BOM for the app to depend
on all the artifacts it manages.
--><dependency><groupId>org.jboss.eap</groupId><artifactId>wildfly-ejb-client-bom</artifactId><type>pom</type><scope>compile</scope></dependency><!-- We depend on the EJB remote business interfaces of this application --><dependency><groupId>${project.groupId}</groupId><artifactId>ejb-remote-server-side</artifactId><version>${project.version}</version><type>ejb-client</type></dependency>
- uri: file:///opt/input/source/server-side/pom.xml
message: |-
`jaxb-impl` Maven dependency missing.
Apache Camel 3 supports Java 11 and in this Java version JAXB modules have been removed from the JDK, therefore you will need to add them as Maven dependencies since there are couple of components rely on them:
```Xml
<dependency>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-impl</artifactId>
<version>2.3.2</version>
</dependency>
```
codeSnip: "34 <url>http://www.apache.org/licenses/LICENSE-2.0.html</url>\n35 <distribution>repo</distribution>\n36 </license>\n37 </licenses>\n38 \n39 <dependencies>\n40 \n41 <!-- Import the Common Annotations API (JSR-250), we use provided scope\n42 as the API is included in JBoss EAP -->\n43 <dependency>\n44 <groupId>org.jboss.spec.javax.annotation</groupId>\n45 <artifactId>jboss-annotations-api_1.3_spec</artifactId>\n46 <scope>provided</scope>\n47 </dependency>\n48 \n49 <!-- Import the EJB API, we use provided scope as the API is included in JBoss EAP -->\n50 <dependency>\n51 <groupId>org.jboss.spec.javax.ejb</groupId>\n52 <artifactId>jboss-ejb-api_3.2_spec</artifactId>\n53 <scope>provided</scope>\n54 </dependency>"
lineNumber: 43
variables:
data: dependencies
innerText: "\n\n \n \n org.jboss.spec.javax.annotation\n jboss-annotations-api_1.3_spec\n provided\n \n\n \n \n org.jboss.spec.javax.ejb\n jboss-ejb-api_3.2_spec\n provided\n \n\n "
matchingXML: |-
<!-- Import the Common Annotations API (JSR-250), we use provided scope
as the API is included in JBoss EAP --><dependency><groupId>org.jboss.spec.javax.annotation</groupId><artifactId>jboss-annotations-api_1.3_spec</artifactId><scope>provided</scope></dependency><!-- Import the EJB API, we use provided scope as the API is included in JBoss EAP --><dependency><groupId>org.jboss.spec.javax.ejb</groupId><artifactId>jboss-ejb-api_3.2_spec</artifactId><scope>provided</scope></dependency>
links:
- url: https://camel.apache.org/manual/latest/camel-3-migration-guide.html#_java_versions
title: 'Camel 3 - Migration Guide: Java Versions'
effort: 1
errors:
component-changes-00010: 'could not parse provided xpath query ''//*[c:crypto and not(b:crypto/@algorithm)]/c:crypto'': prefix b not defined.'
component-changes-00011: 'could not parse provided xpath query ''//*[c:secureXML and (count(c:secureXML/@passPhrase)+count(c:secureXML/@passPhraseByte))<1]/c:secureXML/'': expression must evaluate to a node-set'
unmatched:
- classes-removed-camel31-00001
- component-changes-00001
- component-changes-00002
- component-changes-00003
- component-changes-00004
- component-changes-00005
- component-changes-00006
- component-changes-00007
- component-changes-00008
- component-changes-00009
- component-changes-00012
- component-changes-00013
- component-changes-00014
- component-changes-00015
- component-changes-00016
- component-changes-00017
- component-changes-00018
- component-changes-00019
- java-camel33-00001
- java-camel36-00001
- java-dsl-changes-00001
- java-generic-information-00000
- java-generic-information-00001
- java-generic-information-00002
- java-generic-information-00004
- java-generic-information-00005
- java-generic-information-00006
- java-generic-information-00008
- java-generic-information-00009
- java-generic-information-00010
- java-generic-information-00011
- java-generic-information-00012
- java-generic-information-00013
- java-generic-information-00014
- java-generic-information-00015
- java-generic-information-00016
- java-generic-information-00017
- java-generic-information-00018
- java-generic-information-00019
- java-generic-information-00021
- java-generic-information-00022
- java-generic-information-00023
- java-generic-information-00024
- java-generic-information-00025
- java-generic-information-00026
- java-generic-information-00027
- java-generic-information-00028
- java-generic-information-00029
- java-generic-information-00030
- java-generic-information-00031
- java-generic-information-00032
- java-generic-information-00033
- java-generic-information-00034
- java-generic-information-00035
- java-generic-information-00036
- java-generic-information-00037
- java-generic-information-00038
- java-generic-information-00039
- java-generic-information-00040
- java-generic-information-00041
- java-generic-information-00042
- java-generic-information-00043
- java-generic-information-00044
- java-generic-information-00045
- java-generic-information-00046
- java-generic-information-00047
- java-generic-information-00048
- java-generic-information-00049
- java-generic-information-00050
- java-generic-information-00051
- java-generic-information-00052
- java-generic-information-camel37-00000
- java-generic-information-camel37-00001
- java-generic-information-camel37-00002
- java-generic-information-camel37-00003
- java-generic-information-camel37-00004
- java-generic-information-camel37-00005
- java-generic-information-camel37-00006
- java-generic-information-camel37-00007
- java-generic-information-camel37-00007-01
- java-generic-information-camel37-00008
- java-generic-information-camel37-00009
- java-generic-information-camel37-00010
- java-generic-information-camel37-00011
- java-generic-information-camel37-00012
- java-generic-information-camel37-00013
- java-generic-information-camel37-00014
- java-generic-information-camel37-00015
- java-generic-information-camel37-00016
- java-multiple-camelcontexts-per-application-not-supported-00000
- java-multiple-camelcontexts-per-application-not-supported-00001
- jndiregistry-removed-camel32-00001
- properties-removed-camel310-00002
- properties-removed-camel310-00003
- properties-removed-camel310-00004
- properties-removed-camel310-00005
- properties-removed-camel310-00006
- properties-removed-camel310-00007
- properties-removed-camel310-00008
- properties-removed-camel310-00009
- properties-removed-camel310-00010
- properties-removed-camel310-00011
- properties-removed-camel310-00012
- properties-removed-camel310-00013
- properties-removed-camel311-00001
- properties-removed-camel311-00002
- properties-removed-camel315-00001
- properties-removed-camel315-00002
- properties-removed-camel315-00003
- properties-removed-camel315-00004
- properties-removed-camel315-00005
- properties-removed-camel315-00006
- properties-removed-camel315-00007
- properties-removed-camel315-00008
- properties-removed-camel315-00009
- properties-removed-camel315-00010
- properties-removed-camel315-00011
- properties-removed-camel315-00012
- properties-removed-camel315-00013
- properties-removed-camel315-00014
- properties-removed-camel315-00015
- properties-removed-camel38-00001
- properties-removed-camel38-00002
- properties-removed-camel38-00003
- xml-314-00001
- xml-315-00001
- xml-changed-camel311-00001
- xml-changed-camel320-00001
- xml-changed-camel320-00002
- xml-changed-camel320-00003
- xml-changed-camel320-00004
- xml-changed-camel320-00005
- xml-changed-camel321-00001
- xml-changed-camel321-00002
- xml-changed-camel321-00003
- xml-changed-camel321-00004
- xml-changed-camel321-00005
- xml-dsl-changes-00001
- xml-dsl-changes-00002
- xml-dsl-changes-00003
- xml-dsl-changes-00004
- xml-dsl-changes-00005
- xml-dsl-changes-00006
- xml-dsl-changes-00007
- xml-dsl-changes-00008
- xml-dsl-changes-00009
- xml-legacy-camel317-00001
- xml-legacy-camel317-00002
- xml-legacy-camel317-00003
- xml-legacy-camel317-00004
- xml-moved-camel31-00001
- xml-moved-camel31-00002
- xml-moved-camel31-00003
- xml-moved-camel32-00003
- xml-moved-camel32-00004
- xml-moved-camel32-00005
- xml-moved-camel34-00001
- xml-moved-components-00012
- xml-moved-components-00013
- xml-moved-components-00014
- xml-moved-components-00015
- xml-removed-camel31-00001
- xml-removed-camel31-00002
- xml-removed-camel310-00001
- xml-removed-camel311-00001
- xml-removed-camel312-00001
- xml-removed-camel312-00002
- xml-removed-camel312-00003
- xml-removed-camel312-00004
- xml-removed-camel313-00001
- xml-removed-camel313-00003
- xml-removed-camel315-00001
- xml-removed-camel315-00002
- xml-removed-camel316-00001
- xml-removed-camel316-00002
- xml-removed-camel317-00001
- xml-removed-camel317-00002
- xml-removed-camel317-00003
- xml-removed-camel317-00004
- xml-removed-camel317-00005
- xml-removed-camel317-00006
- xml-removed-camel317-00007
- xml-removed-camel317-00008
- xml-removed-camel317-00009
- xml-removed-camel317-00010
- xml-removed-camel317-00011
- xml-removed-camel317-00012
- xml-removed-camel317-00013
- xml-removed-camel317-00014
- xml-removed-camel317-00015
- xml-removed-camel317-00016
- xml-removed-camel317-00017
- xml-removed-camel318-00001
- xml-removed-camel318-00002
- xml-removed-camel318-00003
- xml-removed-camel318-00004
- xml-removed-camel319-00001
- xml-removed-camel319-00002
- xml-removed-camel319-00003
- xml-removed-camel319-00004
- xml-removed-camel319-00005
- xml-removed-camel319-00006
- xml-removed-camel32-00001
- xml-removed-camel32-00002
- xml-removed-camel32-00003
- xml-removed-camel32-00004
- xml-removed-camel32-00005
- xml-removed-camel32-00006
- xml-removed-camel32-00007
- xml-removed-camel32-00008
- xml-removed-camel32-00010
- xml-removed-camel34-00001
- xml-removed-camel35-00001
- xml-removed-camel36-00001
- xml-removed-camel39-00002
- xml-removed-camel39-00004
- xml-removed-camel39-00005
- xml-removed-camel39-00006
- xml-removed-camel39-00007
- xml-removed-camel39-00008
- xml-removed-camel39-00009
- xml-removed-camel39-00010
- xml-removed-camel39-00011
- xml-removed-camel39-00012
- xml-removed-camel39-00013
- xml-removed-camel39-00014
- xml-removed-camel39-00015
- xml-removed-camel39-00016
- xml-removed-camel39-00017
- xml-removed-camel39-00018
- xml-removed-camel39-00019
- xml-removed-camel39-00020
- xml-removed-components-00000
- xml-removed-components-00001
- xml-removed-components-00002
- xml-removed-components-00003
- xml-removed-components-00004
- xml-removed-components-00005
- xml-removed-components-00005-01
- xml-removed-components-00006
- xml-removed-components-00007
- xml-removed-components-00007-01
- xml-removed-components-00008
- xml-removed-components-00008-01
- xml-renamed-components-00000
- xml-renamed-components-00001
- xml-renamed-components-000019
- xml-renamed-components-00002
- xml-renamed-components-000020
- xml-renamed-components-000023
- xml-renamed-components-000024
- xml-renamed-components-000027
- xml-renamed-components-000028
- xml-renamed-components-000029
- xml-renamed-components-00003
- xml-renamed-components-00004
- xml-renamed-components-00005
- xml-renamed-components-00006
- xml-renamed-components-00007
- xml-renamed-components-00008
- xml-renamed-components-00009
- xml-renamed-components-00010
- xml-renamed-components-00011
- xml-renamed-components-00012
- xml-renamed-components-00013
- xml-renamed-components-00014
- xml-renamed-components-00015
- xml-renamed-components-00016
- xml-renamed-components-00017
- xml-renamed-components-00018
- xml-renamed-components-00021
- xml-renamed-components-00022
- xml-renamed-components-00025
- xml-renamed-components-00026
- name: cloud-readiness
description: This ruleset detects logging configurations that may be problematic when migrating an application to a cloud environment.
violations:
localhost-http-00001:
description: Local HTTP Calls
category: mandatory
labels:
- konveyor.io/source
- konveyor.io/target=cloud-readiness
- localhost
incidents:
- uri: file:///opt/input/source/client/src/main/java/org/jboss/as/quickstarts/ejb/remote/client/RemoteEJBClient.java
message: The app is trying to access local resource by HTTP, please try to migrate the resource to cloud
codeSnip: " 16 */\n 17 package org.jboss.as.quickstarts.ejb.remote.client;\n 18 \n 19 import org.jboss.as.quickstarts.ejb.remote.stateful.RemoteCounter;\n 20 import org.jboss.as.quickstarts.ejb.remote.stateless.RemoteCalculator;\n 21 \n 22 import javax.naming.Context;\n 23 import javax.naming.InitialContext;\n 24 import javax.naming.NamingException;\n 25 \n 26 import java.util.Hashtable;\n 27 \n 28 /**\n 29 * A sample program which acts a remote client for a EJB deployed on JBoss EAP server. This program shows how to lookup stateful and\n 30 * stateless beans via JNDI and then invoke on them\n 31 *\n 32 * @author Jaikiran Pai\n 33 */\n 34 public class RemoteEJBClient {\n 35 \n 36 private static final String HTTP = \"http\";\n 37 \n 38 public static void main(String[] args) throws Exception {\n 39 // Invoke a stateless bean\n 40 invokeStatelessBean();\n 41 \n 42 // Invoke a stateful bean\n 43 invokeStatefulBean();\n 44 }\n 45 \n 46 /**\n 47 * Looks up a stateless bean and invokes on it\n 48 *\n 49 * @throws NamingException\n 50 */\n 51 private static void invokeStatelessBean() throws NamingException {\n 52 // Let's lookup the remote stateless calculator\n 53 final RemoteCalculator statelessRemoteCalculator = lookupRemoteStatelessCalculator();\n 54 System.out.println(\"Obtained a remote stateless calculator for invocation\");\n 55 // invoke on the remote calculator\n 56 int a = 204;\n 57 int b = 340;\n 58 System.out.println(\"Adding \" + a + \" and \" + b + \" via the remote stateless calculator deployed on the server\");\n 59 int sum = statelessRemoteCalculator.add(a, b);\n 60 System.out.println(\"Remote calculator returned sum = \" + sum);\n 61 if (sum != a + b) {\n 62 throw new RuntimeException(\"Remote stateless calculator returned an incorrect sum \" + sum + \" ,expected sum was \"\n 63 + (a + b));\n 64 }\n 65 // try one more invocation, this time for subtraction\n 66 int num1 = 3434;\n 67 int num2 = 2332;\n 68 System.out.println(\"Subtracting \" + num2 + \" from \" + num1\n 69 + \" via the remote stateless calculator deployed on the server\");\n 70 int difference = statelessRemoteCalculator.subtract(num1, num2);\n 71 System.out.println(\"Remote calculator returned difference = \" + difference);\n 72 if (difference != num1 - num2) {\n 73 throw new RuntimeException(\"Remote stateless calculator returned an incorrect difference \" + difference\n 74 + \" ,expected difference was \" + (num1 - num2));\n 75 }\n 76 }\n 77 \n 78 /**\n 79 * Looks up a stateful bean and invokes on it\n 80 *\n 81 * @throws NamingException\n 82 */\n 83 private static void invokeStatefulBean() throws NamingException {\n 84 // Let's lookup the remote stateful counter\n 85 final RemoteCounter statefulRemoteCounter = lookupRemoteStatefulCounter();\n 86 System.out.println(\"Obtained a remote stateful counter for invocation\");\n 87 // invoke on the remote counter bean\n 88 final int NUM_TIMES = 5;\n 89 System.out.println(\"Counter will now be incremented \" + NUM_TIMES + \" times\");\n 90 for (int i = 0; i < NUM_TIMES; i++) {\n 91 System.out.println(\"Incrementing counter\");\n 92 statefulRemoteCounter.increment();\n 93 System.out.println(\"Count after increment is \" + statefulRemoteCounter.getCount());\n 94 }\n 95 // now decrementing\n 96 System.out.println(\"Counter will now be decremented \" + NUM_TIMES + \" times\");\n 97 for (int i = NUM_TIMES; i > 0; i--) {\n 98 System.out.println(\"Decrementing counter\");\n 99 statefulRemoteCounter.decrement();\n100 System.out.println(\"Count after decrement is \" + statefulRemoteCounter.getCount());\n101 }\n102 }\n103 \n104 /**\n105 * Looks up and returns the proxy to remote stateless calculator bean\n106 *\n107 * @return\n108 * @throws NamingException\n109 */\n110 private static RemoteCalculator lookupRemoteStatelessCalculator() throws NamingException {\n111 final Hashtable<String, String> jndiProperties = new Hashtable<>();\n112 jndiProperties.put(Context.INITIAL_CONTEXT_FACTORY, \"org.wildfly.naming.client.WildFlyInitialContextFactory\");\n113 if(Boolean.getBoolean(HTTP)) {\n114 //use HTTP based invocation. Each invocation will be a HTTP request\n115 jndiProperties.put(Context.PROVIDER_URL,\"http://localhost:8080/wildfly-services\");\n116 } else {\n117 //use HTTP upgrade, an initial upgrade requests is sent to upgrade to the remoting protocol\n118 jndiProperties.put(Context.PROVIDER_URL,\"remote+http://localhost:8080\");\n119 }\n120 final Context context = new InitialContext(jndiProperties);\n121 \n122 // The JNDI lookup name for a stateless session bean has the syntax of:\n123 // ejb:<appName>/<moduleName>/<distinctName>/<beanName>!<viewClassName>\n124 //\n125 // <appName> The application name is the name of the EAR that the EJB is deployed in\n126 // (without the .ear). If the EJB JAR is not deployed in an EAR then this is\n127 // blank. The app name can also be specified in the EAR's application.xml\n128 //\n129 // <moduleName> By the default the module name is the name of the EJB JAR file (without the\n130 // .jar suffix). The module name might be overridden in the ejb-jar.xml\n131 //\n132 // <distinctName> : EAP allows each deployment to have an (optional) distinct name.\n133 // This example does not use this so leave it blank.\n134 //\n135 // <beanName> : The name of the session been to be invoked.\n136 //\n137 // <viewClassName>: The fully qualified classname of the remote interface. Must include\n138 // the whole package name.\n139 \n140 // let's do the lookup\n141 return (RemoteCalculator) context.lookup(\"ejb:/ejb-remote-server-side/CalculatorBean!\"\n142 + RemoteCalculator.class.getName());\n143 }\n144 \n145 /**\n146 * Looks up and returns the proxy to remote stateful counter bean\n147 *\n148 * @return\n149 * @throws NamingException\n150 */\n151 private static RemoteCounter lookupRemoteStatefulCounter() throws NamingException {\n152 final Hashtable<String, String> jndiProperties = new Hashtable<>();\n153 //jndiProperties.put(Context.URL_PKG_PREFIXES, \"org.jboss.ejb.client.naming\");\n154 jndiProperties.put(Context.INITIAL_CONTEXT_FACTORY, \"org.wildfly.naming.client.WildFlyInitialContextFactory\");\n155 if(Boolean.getBoolean(HTTP)) {\n156 //use HTTP based invocation. Each invocation will be a HTTP request\n157 jndiProperties.put(Context.PROVIDER_URL,\"http://localhost:8080/wildfly-services\");\n158 } else {\n159 //use HTTP upgrade, an initial upgrade requests is sent to upgrade to the remoting protocol\n160 jndiProperties.put(Context.PROVIDER_URL,\"remote+http://localhost:8080\");\n161 }\n162 final Context context = new InitialContext(jndiProperties);\n163 \n164 // The JNDI lookup name for a stateful session bean has the syntax of:\n165 // ejb:<appName>/<moduleName>/<distinctName>/<beanName>!<viewClassName>?stateful\n166 //\n167 // <appName> The application name is the name of the EAR that the EJB is deployed in\n168 // (without the .ear). If the EJB JAR is not deployed in an EAR then this is\n169 // blank. The app name can also be specified in the EAR's application.xml\n170 //\n171 // <moduleName> By the default the module name is the name of the EJB JAR file (without the\n172 // .jar suffix). The module name might be overridden in the ejb-jar.xml\n173 //\n174 // <distinctName> : EAP allows each deployment to have an (optional) distinct name.\n175 // This example does not use this so leave it blank.\n176 //\n177 // <beanName> : The name of the session been to be invoked.\n178 //\n179 // <viewClassName>: The fully qualified classname of the remote interface. Must include\n180 // the whole package name.\n181 \n182 // let's do the lookup\n183 return (RemoteCounter) context.lookup(\"ejb:/ejb-remote-server-side/CounterBean!\"\n184 + RemoteCounter.class.getName() + \"?stateful\");\n185 }\n186 }\n"
lineNumber: 115
variables:
matchingText: http://localhost:8080/wildfly-services");
- uri: file:///opt/input/source/client/src/main/java/org/jboss/as/quickstarts/ejb/remote/client/RemoteEJBClient.java
message: The app is trying to access local resource by HTTP, please try to migrate the resource to cloud
codeSnip: " 19 import org.jboss.as.quickstarts.ejb.remote.stateful.RemoteCounter;\n 20 import org.jboss.as.quickstarts.ejb.remote.stateless.RemoteCalculator;\n 21 \n 22 import javax.naming.Context;\n 23 import javax.naming.InitialContext;\n 24 import javax.naming.NamingException;\n 25 \n 26 import java.util.Hashtable;\n 27 \n 28 /**\n 29 * A sample program which acts a remote client for a EJB deployed on JBoss EAP server. This program shows how to lookup stateful and\n 30 * stateless beans via JNDI and then invoke on them\n 31 *\n 32 * @author Jaikiran Pai\n 33 */\n 34 public class RemoteEJBClient {\n 35 \n 36 private static final String HTTP = \"http\";\n 37 \n 38 public static void main(String[] args) throws Exception {\n 39 // Invoke a stateless bean\n 40 invokeStatelessBean();\n 41 \n 42 // Invoke a stateful bean\n 43 invokeStatefulBean();\n 44 }\n 45 \n 46 /**\n 47 * Looks up a stateless bean and invokes on it\n 48 *\n 49 * @throws NamingException\n 50 */\n 51 private static void invokeStatelessBean() throws NamingException {\n 52 // Let's lookup the remote stateless calculator\n 53 final RemoteCalculator statelessRemoteCalculator = lookupRemoteStatelessCalculator();\n 54 System.out.println(\"Obtained a remote stateless calculator for invocation\");\n 55 // invoke on the remote calculator\n 56 int a = 204;\n 57 int b = 340;\n 58 System.out.println(\"Adding \" + a + \" and \" + b + \" via the remote stateless calculator deployed on the server\");\n 59 int sum = statelessRemoteCalculator.add(a, b);\n 60 System.out.println(\"Remote calculator returned sum = \" + sum);\n 61 if (sum != a + b) {\n 62 throw new RuntimeException(\"Remote stateless calculator returned an incorrect sum \" + sum + \" ,expected sum was \"\n 63 + (a + b));\n 64 }\n 65 // try one more invocation, this time for subtraction\n 66 int num1 = 3434;\n 67 int num2 = 2332;\n 68 System.out.println(\"Subtracting \" + num2 + \" from \" + num1\n 69 + \" via the remote stateless calculator deployed on the server\");\n 70 int difference = statelessRemoteCalculator.subtract(num1, num2);\n 71 System.out.println(\"Remote calculator returned difference = \" + difference);\n 72 if (difference != num1 - num2) {\n 73 throw new RuntimeException(\"Remote stateless calculator returned an incorrect difference \" + difference\n 74 + \" ,expected difference was \" + (num1 - num2));\n 75 }\n 76 }\n 77 \n 78 /**\n 79 * Looks up a stateful bean and invokes on it\n 80 *\n 81 * @throws NamingException\n 82 */\n 83 private static void invokeStatefulBean() throws NamingException {\n 84 // Let's lookup the remote stateful counter\n 85 final RemoteCounter statefulRemoteCounter = lookupRemoteStatefulCounter();\n 86 System.out.println(\"Obtained a remote stateful counter for invocation\");\n 87 // invoke on the remote counter bean\n 88 final int NUM_TIMES = 5;\n 89 System.out.println(\"Counter will now be incremented \" + NUM_TIMES + \" times\");\n 90 for (int i = 0; i < NUM_TIMES; i++) {\n 91 System.out.println(\"Incrementing counter\");\n 92 statefulRemoteCounter.increment();\n 93 System.out.println(\"Count after increment is \" + statefulRemoteCounter.getCount());\n 94 }\n 95 // now decrementing\n 96 System.out.println(\"Counter will now be decremented \" + NUM_TIMES + \" times\");\n 97 for (int i = NUM_TIMES; i > 0; i--) {\n 98 System.out.println(\"Decrementing counter\");\n 99 statefulRemoteCounter.decrement();\n100 System.out.println(\"Count after decrement is \" + statefulRemoteCounter.getCount());\n101 }\n102 }\n103 \n104 /**\n105 * Looks up and returns the proxy to remote stateless calculator bean\n106 *\n107 * @return\n108 * @throws NamingException\n109 */\n110 private static RemoteCalculator lookupRemoteStatelessCalculator() throws NamingException {\n111 final Hashtable<String, String> jndiProperties = new Hashtable<>();\n112 jndiProperties.put(Context.INITIAL_CONTEXT_FACTORY, \"org.wildfly.naming.client.WildFlyInitialContextFactory\");\n113 if(Boolean.getBoolean(HTTP)) {\n114 //use HTTP based invocation. Each invocation will be a HTTP request\n115 jndiProperties.put(Context.PROVIDER_URL,\"http://localhost:8080/wildfly-services\");\n116 } else {\n117 //use HTTP upgrade, an initial upgrade requests is sent to upgrade to the remoting protocol\n118 jndiProperties.put(Context.PROVIDER_URL,\"remote+http://localhost:8080\");\n119 }\n120 final Context context = new InitialContext(jndiProperties);\n121 \n122 // The JNDI lookup name for a stateless session bean has the syntax of:\n123 // ejb:<appName>/<moduleName>/<distinctName>/<beanName>!<viewClassName>\n124 //\n125 // <appName> The application name is the name of the EAR that the EJB is deployed in\n126 // (without the .ear). If the EJB JAR is not deployed in an EAR then this is\n127 // blank. The app name can also be specified in the EAR's application.xml\n128 //\n129 // <moduleName> By the default the module name is the name of the EJB JAR file (without the\n130 // .jar suffix). The module name might be overridden in the ejb-jar.xml\n131 //\n132 // <distinctName> : EAP allows each deployment to have an (optional) distinct name.\n133 // This example does not use this so leave it blank.\n134 //\n135 // <beanName> : The name of the session been to be invoked.\n136 //\n137 // <viewClassName>: The fully qualified classname of the remote interface. Must include\n138 // the whole package name.\n139 \n140 // let's do the lookup\n141 return (RemoteCalculator) context.lookup(\"ejb:/ejb-remote-server-side/CalculatorBean!\"\n142 + RemoteCalculator.class.getName());\n143 }\n144 \n145 /**\n146 * Looks up and returns the proxy to remote stateful counter bean\n147 *\n148 * @return\n149 * @throws NamingException\n150 */\n151 private static RemoteCounter lookupRemoteStatefulCounter() throws NamingException {\n152 final Hashtable<String, String> jndiProperties = new Hashtable<>();\n153 //jndiProperties.put(Context.URL_PKG_PREFIXES, \"org.jboss.ejb.client.naming\");\n154 jndiProperties.put(Context.INITIAL_CONTEXT_FACTORY, \"org.wildfly.naming.client.WildFlyInitialContextFactory\");\n155 if(Boolean.getBoolean(HTTP)) {\n156 //use HTTP based invocation. Each invocation will be a HTTP request\n157 jndiProperties.put(Context.PROVIDER_URL,\"http://localhost:8080/wildfly-services\");\n158 } else {\n159 //use HTTP upgrade, an initial upgrade requests is sent to upgrade to the remoting protocol\n160 jndiProperties.put(Context.PROVIDER_URL,\"remote+http://localhost:8080\");\n161 }\n162 final Context context = new InitialContext(jndiProperties);\n163 \n164 // The JNDI lookup name for a stateful session bean has the syntax of:\n165 // ejb:<appName>/<moduleName>/<distinctName>/<beanName>!<viewClassName>?stateful\n166 //\n167 // <appName> The application name is the name of the EAR that the EJB is deployed in\n168 // (without the .ear). If the EJB JAR is not deployed in an EAR then this is\n169 // blank. The app name can also be specified in the EAR's application.xml\n170 //\n171 // <moduleName> By the default the module name is the name of the EJB JAR file (without the\n172 // .jar suffix). The module name might be overridden in the ejb-jar.xml\n173 //\n174 // <distinctName> : EAP allows each deployment to have an (optional) distinct name.\n175 // This example does not use this so leave it blank.\n176 //\n177 // <beanName> : The name of the session been to be invoked.\n178 //\n179 // <viewClassName>: The fully qualified classname of the remote interface. Must include\n180 // the whole package name.\n181 \n182 // let's do the lookup\n183 return (RemoteCounter) context.lookup(\"ejb:/ejb-remote-server-side/CounterBean!\"\n184 + RemoteCounter.class.getName() + \"?stateful\");\n185 }\n186 }\n"
lineNumber: 118
variables:
matchingText: http://localhost:8080
- uri: file:///opt/input/source/client/src/main/java/org/jboss/as/quickstarts/ejb/remote/client/RemoteEJBClient.java
message: The app is trying to access local resource by HTTP, please try to migrate the resource to cloud
codeSnip: " 58 System.out.println(\"Adding \" + a + \" and \" + b + \" via the remote stateless calculator deployed on the server\");\n 59 int sum = statelessRemoteCalculator.add(a, b);\n 60 System.out.println(\"Remote calculator returned sum = \" + sum);\n 61 if (sum != a + b) {\n 62 throw new RuntimeException(\"Remote stateless calculator returned an incorrect sum \" + sum + \" ,expected sum was \"\n 63 + (a + b));\n 64 }\n 65 // try one more invocation, this time for subtraction\n 66 int num1 = 3434;\n 67 int num2 = 2332;\n 68 System.out.println(\"Subtracting \" + num2 + \" from \" + num1\n 69 + \" via the remote stateless calculator deployed on the server\");\n 70 int difference = statelessRemoteCalculator.subtract(num1, num2);\n 71 System.out.println(\"Remote calculator returned difference = \" + difference);\n 72 if (difference != num1 - num2) {\n 73 throw new RuntimeException(\"Remote stateless calculator returned an incorrect difference \" + difference\n 74 + \" ,expected difference was \" + (num1 - num2));\n 75 }\n 76 }\n 77 \n 78 /**\n 79 * Looks up a stateful bean and invokes on it\n 80 *\n 81 * @throws NamingException\n 82 */\n 83 private static void invokeStatefulBean() throws NamingException {\n 84 // Let's lookup the remote stateful counter\n 85 final RemoteCounter statefulRemoteCounter = lookupRemoteStatefulCounter();\n 86 System.out.println(\"Obtained a remote stateful counter for invocation\");\n 87 // invoke on the remote counter bean\n 88 final int NUM_TIMES = 5;\n 89 System.out.println(\"Counter will now be incremented \" + NUM_TIMES + \" times\");\n 90 for (int i = 0; i < NUM_TIMES; i++) {\n 91 System.out.println(\"Incrementing counter\");\n 92 statefulRemoteCounter.increment();\n 93 System.out.println(\"Count after increment is \" + statefulRemoteCounter.getCount());\n 94 }\n 95 // now decrementing\n 96 System.out.println(\"Counter will now be decremented \" + NUM_TIMES + \" times\");\n 97 for (int i = NUM_TIMES; i > 0; i--) {\n 98 System.out.println(\"Decrementing counter\");\n 99 statefulRemoteCounter.decrement();\n100 System.out.println(\"Count after decrement is \" + statefulRemoteCounter.getCount());\n101 }\n102 }\n103 \n104 /**\n105 * Looks up and returns the proxy to remote stateless calculator bean\n106 *\n107 * @return\n108 * @throws NamingException\n109 */\n110 private static RemoteCalculator lookupRemoteStatelessCalculator() throws NamingException {\n111 final Hashtable<String, String> jndiProperties = new Hashtable<>();\n112 jndiProperties.put(Context.INITIAL_CONTEXT_FACTORY, \"org.wildfly.naming.client.WildFlyInitialContextFactory\");\n113 if(Boolean.getBoolean(HTTP)) {\n114 //use HTTP based invocation. Each invocation will be a HTTP request\n115 jndiProperties.put(Context.PROVIDER_URL,\"http://localhost:8080/wildfly-services\");\n116 } else {\n117 //use HTTP upgrade, an initial upgrade requests is sent to upgrade to the remoting protocol\n118 jndiProperties.put(Context.PROVIDER_URL,\"remote+http://localhost:8080\");\n119 }\n120 final Context context = new InitialContext(jndiProperties);\n121 \n122 // The JNDI lookup name for a stateless session bean has the syntax of:\n123 // ejb:<appName>/<moduleName>/<distinctName>/<beanName>!<viewClassName>\n124 //\n125 // <appName> The application name is the name of the EAR that the EJB is deployed in\n126 // (without the .ear). If the EJB JAR is not deployed in an EAR then this is\n127 // blank. The app name can also be specified in the EAR's application.xml\n128 //\n129 // <moduleName> By the default the module name is the name of the EJB JAR file (without the\n130 // .jar suffix). The module name might be overridden in the ejb-jar.xml\n131 //\n132 // <distinctName> : EAP allows each deployment to have an (optional) distinct name.\n133 // This example does not use this so leave it blank.\n134 //\n135 // <beanName> : The name of the session been to be invoked.\n136 //\n137 // <viewClassName>: The fully qualified classname of the remote interface. Must include\n138 // the whole package name.\n139 \n140 // let's do the lookup\n141 return (RemoteCalculator) context.lookup(\"ejb:/ejb-remote-server-side/CalculatorBean!\"\n142 + RemoteCalculator.class.getName());\n143 }\n144 \n145 /**\n146 * Looks up and returns the proxy to remote stateful counter bean\n147 *\n148 * @return\n149 * @throws NamingException\n150 */\n151 private static RemoteCounter lookupRemoteStatefulCounter() throws NamingException {\n152 final Hashtable<String, String> jndiProperties = new Hashtable<>();\n153 //jndiProperties.put(Context.URL_PKG_PREFIXES, \"org.jboss.ejb.client.naming\");\n154 jndiProperties.put(Context.INITIAL_CONTEXT_FACTORY, \"org.wildfly.naming.client.WildFlyInitialContextFactory\");\n155 if(Boolean.getBoolean(HTTP)) {\n156 //use HTTP based invocation. Each invocation will be a HTTP request\n157 jndiProperties.put(Context.PROVIDER_URL,\"http://localhost:8080/wildfly-services\");\n158 } else {\n159 //use HTTP upgrade, an initial upgrade requests is sent to upgrade to the remoting protocol\n160 jndiProperties.put(Context.PROVIDER_URL,\"remote+http://localhost:8080\");\n161 }\n162 final Context context = new InitialContext(jndiProperties);\n163 \n164 // The JNDI lookup name for a stateful session bean has the syntax of:\n165 // ejb:<appName>/<moduleName>/<distinctName>/<beanName>!<viewClassName>?stateful\n166 //\n167 // <appName> The application name is the name of the EAR that the EJB is deployed in\n168 // (without the .ear). If the EJB JAR is not deployed in an EAR then this is\n169 // blank. The app name can also be specified in the EAR's application.xml\n170 //\n171 // <moduleName> By the default the module name is the name of the EJB JAR file (without the\n172 // .jar suffix). The module name might be overridden in the ejb-jar.xml\n173 //\n174 // <distinctName> : EAP allows each deployment to have an (optional) distinct name.\n175 // This example does not use this so leave it blank.\n176 //\n177 // <beanName> : The name of the session been to be invoked.\n178 //\n179 // <viewClassName>: The fully qualified classname of the remote interface. Must include\n180 // the whole package name.\n181 \n182 // let's do the lookup\n183 return (RemoteCounter) context.lookup(\"ejb:/ejb-remote-server-side/CounterBean!\"\n184 + RemoteCounter.class.getName() + \"?stateful\");\n185 }\n186 }\n"
lineNumber: 157
variables:
matchingText: http://localhost:8080/wildfly-services");
- uri: file:///opt/input/source/client/src/main/java/org/jboss/as/quickstarts/ejb/remote/client/RemoteEJBClient.java
message: The app is trying to access local resource by HTTP, please try to migrate the resource to cloud
codeSnip: " 61 if (sum != a + b) {\n 62 throw new RuntimeException(\"Remote stateless calculator returned an incorrect sum \" + sum + \" ,expected sum was \"\n 63 + (a + b));\n 64 }\n 65 // try one more invocation, this time for subtraction\n 66 int num1 = 3434;\n 67 int num2 = 2332;\n 68 System.out.println(\"Subtracting \" + num2 + \" from \" + num1\n 69 + \" via the remote stateless calculator deployed on the server\");\n 70 int difference = statelessRemoteCalculator.subtract(num1, num2);\n 71 System.out.println(\"Remote calculator returned difference = \" + difference);\n 72 if (difference != num1 - num2) {\n 73 throw new RuntimeException(\"Remote stateless calculator returned an incorrect difference \" + difference\n 74 + \" ,expected difference was \" + (num1 - num2));\n 75 }\n 76 }\n 77 \n 78 /**\n 79 * Looks up a stateful bean and invokes on it\n 80 *\n 81 * @throws NamingException\n 82 */\n 83 private static void invokeStatefulBean() throws NamingException {\n 84 // Let's lookup the remote stateful counter\n 85 final RemoteCounter statefulRemoteCounter = lookupRemoteStatefulCounter();\n 86 System.out.println(\"Obtained a remote stateful counter for invocation\");\n 87 // invoke on the remote counter bean\n 88 final int NUM_TIMES = 5;\n 89 System.out.println(\"Counter will now be incremented \" + NUM_TIMES + \" times\");\n 90 for (int i = 0; i < NUM_TIMES; i++) {\n 91 System.out.println(\"Incrementing counter\");\n 92 statefulRemoteCounter.increment();\n 93 System.out.println(\"Count after increment is \" + statefulRemoteCounter.getCount());\n 94 }\n 95 // now decrementing\n 96 System.out.println(\"Counter will now be decremented \" + NUM_TIMES + \" times\");\n 97 for (int i = NUM_TIMES; i > 0; i--) {\n 98 System.out.println(\"Decrementing counter\");\n 99 statefulRemoteCounter.decrement();\n100 System.out.println(\"Count after decrement is \" + statefulRemoteCounter.getCount());\n101 }\n102 }\n103 \n104 /**\n105 * Looks up and returns the proxy to remote stateless calculator bean\n106 *\n107 * @return\n108 * @throws NamingException\n109 */\n110 private static RemoteCalculator lookupRemoteStatelessCalculator() throws NamingException {\n111 final Hashtable<String, String> jndiProperties = new Hashtable<>();\n112 jndiProperties.put(Context.INITIAL_CONTEXT_FACTORY, \"org.wildfly.naming.client.WildFlyInitialContextFactory\");\n113 if(Boolean.getBoolean(HTTP)) {\n114 //use HTTP based invocation. Each invocation will be a HTTP request\n115 jndiProperties.put(Context.PROVIDER_URL,\"http://localhost:8080/wildfly-services\");\n116 } else {\n117 //use HTTP upgrade, an initial upgrade requests is sent to upgrade to the remoting protocol\n118 jndiProperties.put(Context.PROVIDER_URL,\"remote+http://localhost:8080\");\n119 }\n120 final Context context = new InitialContext(jndiProperties);\n121 \n122 // The JNDI lookup name for a stateless session bean has the syntax of:\n123 // ejb:<appName>/<moduleName>/<distinctName>/<beanName>!<viewClassName>\n124 //\n125 // <appName> The application name is the name of the EAR that the EJB is deployed in\n126 // (without the .ear). If the EJB JAR is not deployed in an EAR then this is\n127 // blank. The app name can also be specified in the EAR's application.xml\n128 //\n129 // <moduleName> By the default the module name is the name of the EJB JAR file (without the\n130 // .jar suffix). The module name might be overridden in the ejb-jar.xml\n131 //\n132 // <distinctName> : EAP allows each deployment to have an (optional) distinct name.\n133 // This example does not use this so leave it blank.\n134 //\n135 // <beanName> : The name of the session been to be invoked.\n136 //\n137 // <viewClassName>: The fully qualified classname of the remote interface. Must include\n138 // the whole package name.\n139 \n140 // let's do the lookup\n141 return (RemoteCalculator) context.lookup(\"ejb:/ejb-remote-server-side/CalculatorBean!\"\n142 + RemoteCalculator.class.getName());\n143 }\n144 \n145 /**\n146 * Looks up and returns the proxy to remote stateful counter bean\n147 *\n148 * @return\n149 * @throws NamingException\n150 */\n151 private static RemoteCounter lookupRemoteStatefulCounter() throws NamingException {\n152 final Hashtable<String, String> jndiProperties = new Hashtable<>();\n153 //jndiProperties.put(Context.URL_PKG_PREFIXES, \"org.jboss.ejb.client.naming\");\n154 jndiProperties.put(Context.INITIAL_CONTEXT_FACTORY, \"org.wildfly.naming.client.WildFlyInitialContextFactory\");\n155 if(Boolean.getBoolean(HTTP)) {\n156 //use HTTP based invocation. Each invocation will be a HTTP request\n157 jndiProperties.put(Context.PROVIDER_URL,\"http://localhost:8080/wildfly-services\");\n158 } else {\n159 //use HTTP upgrade, an initial upgrade requests is sent to upgrade to the remoting protocol\n160 jndiProperties.put(Context.PROVIDER_URL,\"remote+http://localhost:8080\");\n161 }\n162 final Context context = new InitialContext(jndiProperties);\n163 \n164 // The JNDI lookup name for a stateful session bean has the syntax of:\n165 // ejb:<appName>/<moduleName>/<distinctName>/<beanName>!<viewClassName>?stateful\n166 //\n167 // <appName> The application name is the name of the EAR that the EJB is deployed in\n168 // (without the .ear). If the EJB JAR is not deployed in an EAR then this is\n169 // blank. The app name can also be specified in the EAR's application.xml\n170 //\n171 // <moduleName> By the default the module name is the name of the EJB JAR file (without the\n172 // .jar suffix). The module name might be overridden in the ejb-jar.xml\n173 //\n174 // <distinctName> : EAP allows each deployment to have an (optional) distinct name.\n175 // This example does not use this so leave it blank.\n176 //\n177 // <beanName> : The name of the session been to be invoked.\n178 //\n179 // <viewClassName>: The fully qualified classname of the remote interface. Must include\n180 // the whole package name.\n181 \n182 // let's do the lookup\n183 return (RemoteCounter) context.lookup(\"ejb:/ejb-remote-server-side/CounterBean!\"\n184 + RemoteCounter.class.getName() + \"?stateful\");\n185 }\n186 }\n"
lineNumber: 160
variables:
matchingText: http://localhost:8080
effort: 7
unmatched:
- embedded-cache-libraries-01000
- embedded-cache-libraries-02000
- embedded-cache-libraries-03000
- embedded-cache-libraries-04000
- embedded-cache-libraries-04000
- embedded-cache-libraries-05000
- embedded-cache-libraries-06000
- embedded-cache-libraries-07000
- embedded-cache-libraries-08000
- embedded-cache-libraries-09000
- embedded-cache-libraries-10000
- embedded-cache-libraries-11000
- embedded-cache-libraries-12000
- embedded-cache-libraries-13000
- embedded-cache-libraries-14000
- embedded-cache-libraries-15000
- embedded-cache-libraries-16000
- java-corba-00000
- java-rmi-00000
- java-rmi-00000
- java-rmi-00001
- java-rpc-00000
- jca-00000
- jni-native-code-00000
- jni-native-code-00001
- local-storage-00001
- local-storage-00002
- local-storage-00003
- local-storage-00004
- local-storage-00005
- local-storage-00006
- localhost-jdbc-00002
- localhost-ws-00003
- logging-0000
- logging-0000
- logging-0001
- logging-0001
- mail-00000
- session-00000
- session-00001
- socket-communication-00000
- socket-communication-00001
- name: discovery-rules
tags:
- EJB XML
- Java Source
- Maven XML
unmatched:
- discover-license
- discover-manifest-file
- discover-properties-file
- hardcoded-ip-address
- windup-discover-jpa-configuration
- windup-discover-spring-configuration
- windup-discover-web-configuration
- name: droolsjbpm
description: This ruleset provides help for migrating to a unified KIE (Knowledge Is Everything) API in the upgrade from version 5 to 6.
unmatched:
- kie-api-01000
- kie-api-01001
- kie-api-01002
- kie-api-01003
- kie-api-01004
- kie-api-01005
- kie-api-01006
- kie-api-01007
- kie-api-01008
- kie-api-01009
- kie-api-01010
- kie-api-01011
- kie-api-01012
- kie-api-01013
- kie-api-01014
- kie-api-01015
- kie-api-01016
- name: eap6/java-ee/seam
description: This ruleset provides generic migration knowledge from the Seam 2 UI controls to pure JSF 2 UI Controls
unmatched:
- commonj-01000
- commonj-02000
- commonj-03000
- commonj-04000
- commonj-05000
- commonj-06000
- commonj-07000
- eap4-eap6-25000
- eap4-eap6-26000
- eap4-eap6-27000
- eap4-eap6-28000
- eap4-eap6-29000
- eap4-eap6-30000
- eap4-eap6-31000
- eap4-eap6-32000
- eap4-eap6-33000
- eap4-eap6-34000
- eap4-eap6-35000
- eap4-eap6-36000
- eap4-eap6-37000
- eap4-eap6-38000
- eap4-eap6-39000
- eap4-eap6-40000
- eap4-eap6-41000
- eap4-eap6-42000
- environment-dependent-calls-01000
- environment-dependent-calls-02000
- environment-dependent-calls-03000
- environment-dependent-calls-03500
- environment-dependent-calls-03500
- environment-dependent-calls-04000
- environment-dependent-calls-04001
- environment-dependent-calls-05000
- generic-catchall-00000
- generic-catchall-00001
- generic-catchall-00002
- generic-catchall-00003
- generic-catchall-00100
- generic-catchall-00200
- generic-catchall-00300
- generic-catchall-00400
- generic-catchall-00500
- generic-catchall-00600
- generic-catchall-00700
- generic-catchall-00900
- java-ee-jaxrpc-00000
- jboss-eap5-7-xml-10000
- jboss-eap5-7-xml-10000
- jboss-eap5-java-01000
- jboss-eap5-java-02000
- jboss-eap5-java-04000
- jboss-eap5-java-05000
- jboss-eap5-java-06000
- jboss-eap5-java-07000
- jboss-eap5-java-08000
- jboss-eap5-java-08100
- jboss-eap5-java-08200
- jboss-eap5-java-08300
- jboss-eap5-java-08400
- jboss-eap5-java-08500
- jboss-eap5-java-08600
- jboss-eap5-java-08700
- jboss-eap5-java-08800
- jboss-eap5-java-08900
- jboss-eap5-java-09000
- jboss-eap5-java-09100
- jboss-eap5-xml-01000
- jboss-eap5-xml-02000
- jboss-eap5-xml-03000
- jboss-eap5-xml-05000
- jboss-eap5-xml-06000
- jboss-eap5-xml-07000
- jboss-eap5-xml-08000
- jboss-eap5-xml-09000
- jboss-eap5-xml-11000
- jboss-eap5-xml-12000
- jboss-eap5-xml-13000
- jboss-eap5-xml-14000
- jboss-eap5-xml-16000
- jboss-eap5-xml-16000
- jboss-eap5-xml-17000
- jboss-eap5-xml-18000
- jboss-eap5-xml-20000
- jotm-00001
- jrun-catchall-00000
- jrun-catchall-00001
- jsp-01000
- log4j-01000
- log4j-02000
- log4j-03000
- resteasy-eap5-000001
- seam-java-00000
- seam-java-00000
- seam-java-00010
- seam-java-00030
- seam-java-00040
- seam-java-00050
- seam-java-00060
- seam-java-00061
- seam-java-00070
- seam-java-00071
- seam-java-00080
- seam-java-00090
- seam-java-00091
- seam-java-00100
- seam-java-00110
- seam-java-00120
- seam-java-00130
- seam-java-00140
- seam-java-00150
- seam-java-00160
- seam-java-00170
- seam-java-00170
- seam-java-00180
- seam-java-00190
- seam-java-00200
- seam-java-00210
- seam-java-00220
- seam-java-00230
- seam-java-00240
- seam-java-00250
- seam-java-00260
- seam-java-00270
- seam-ui-jsf-00001
- seam-ui-jsf-00001-01
- seam-ui-jsf-00002
- seam-ui-jsf-01000
- seam-ui-jsf-01001
- seam-ui-jsf-01002
- seam-ui-jsf-01003
- seam-ui-jsf-01004
- seam-ui-jsf-01005
- seam-ui-jsf-01006
- seam-ui-jsf-01007
- seam-ui-jsf-01008
- seam-ui-jsf-01009
- seam-ui-jsf-01010
- seam-ui-jsf-01011
- seam-ui-jsf-01012
- seam-ui-jsf-01013
- seam-ui-jsf-01014
- seam-ui-jsf-01015
- seam-ui-jsf-01016
- seam-ui-jsf-01017
- seam-ui-jsf-01018
- seam-ui-jsf-01019
- seam-ui-jsf-01020
- seam-ui-jsf-01021
- seam-ui-jsf-01022
- seam-ui-jsf-01023
- seam-ui-jsf-01024
- seam-ui-jsf-01025
- seam-ui-jsf-01026
- seam-ui-jsf-01027
- seam-ui-jsf-01028
- seam-ui-jsf-01029
- xml-glassfish-01000
- xml-glassfish-02000
- xml-glassfish-03000
- xml-jonas-01000
- xml-jrun-01000
- xml-jrun-02000
- xml-orion-01000
- xml-orion-01000
- xml-orion-02000
- xml-orion-02000
- xml-orion-03000
- xml-orion-03000
- xml-resin-01000
- xml-resin-01000
- xml-webservices-01000
- xml-webservices-02000
- xml-webservices-03000
- xml-webservices-04000
- xml-webservices-05000
- xml-webservices-06000
- xml-webservices-06001
- xml-webservices-07000
- xml-webservices-08000
- xml-webservices-09000
- xml-webservices-10000
- name: eap7/weblogic/tests/data
unmatched:
- base64-01000
- deprecated-singletonpolicy-00001
- eap6-08000
- eap6-08001
- eap6-08002
- eap6-11000
- eap6-12000
- eap6-xml-05000
- eap6-xml-05000
- eap6-xml-06000
- eap6-xml-06000
- eap7-websphere-xml-01000
- eap7-websphere-xml-01000
- eap7-websphere-xml-02000
- eap7-websphere-xml-02000
- eap7-websphere-xml-03500
- eap7-websphere-xml-06000
- eap7-websphere-xml-07000
- eap7-websphere-xml-08000
- eap7-websphere-xml-09000
- elytron-eap71-00000
- elytron-eap71-00010
- embedded-framework-libraries-01000
- embedded-framework-libraries-01000
- embedded-framework-libraries-02000
- embedded-framework-libraries-02000
- embedded-framework-libraries-04000
- embedded-framework-libraries-04000
- embedded-framework-libraries-05000
- embedded-framework-libraries-05000
- embedded-framework-libraries-06000
- embedded-framework-libraries-06000
- hibernate4-00001
- hibernate4-00002
- hibernate4-00003
- hibernate4-00004
- hibernate4-00005
- hibernate4-00006
- hibernate4-00007
- hibernate4-00008
- hibernate4-00009
- hibernate4-00010
- hibernate4-00011
- hibernate4-00012
- hibernate4-00013
- hibernate4-00014
- hibernate4-00015
- hibernate4-00016
- hibernate4-00017
- hibernate4-00018
- hibernate4-00021
- hibernate4-00022
- hibernate4-00023
- hibernate4-00024
- hibernate4-00025
- hibernate4-00026
- hibernate4-00027
- hibernate4-00028
- hibernate4-00030
- hibernate4-00031
- hibernate4-00032
- hibernate4-00033
- hibernate4-00034
- hibernate4-00035
- hibernate4-00036
- hibernate4-00037
- hibernate4-00038
- hibernate4-00039
- hibernate4-00040
- hibernate4-xml-00001
- hibernate4-xml-00002
- hibernate4-xml-00003
- hibernate4-xml-00004
- hibernate4-xml-00005
- hibernate50-51-00000
- hibernate50-51-00100
- hibernate51-53-00001
- hibernate51-53-00100
- hibernate51-53-00300
- hibernate51-53-00400
- hibernate51-53-00401
- hibernate51-53-00402
- hibernate51-53-00403
- hibernate51-53-00404
- hibernate51-53-00405
- hibernate51-53-00406
- hibernate51-53-00407
- hibernate51-53-00500
- hibernate51-53-00600
- hibernate51-53-00700
- hibernate51-53-00701
- hibernate51-53-00702
- hibernate51-53-00800
- hibernate51-53-01000
- hibernate51-53-01001
- hibernate51-53-01100
- hibernate51-53-01200
- hsearch-00000
- hsearch-00000
- hsearch-00001
- hsearch-00002
- hsearch-00003
- hsearch-00004
- hsearch-00005
- hsearch-00006
- hsearch-00007
- hsearch-00008
- hsearch-00009
- hsearch-00010
- hsearch-00011
- hsearch-00100
- hsearch-00101
- hsearch-00103
- hsearch-00104
- hsearch-00106
- hsearch-00107
- hsearch-00108
- hsearch-00109
- hsearch-00110
- hsearch-00111
- hsearch-00112
- hsearch-00113
- hsearch-00114
- hsearch-00115
- hsearch-00116
- hsearch-00117
- hsearch-00118
- hsearch-00119
- hsearch-00200
- hsearch-00201
- hsearch-00210
- hsearch-00211
- hsearch-00213
- hsearch-00214
- hsearch-00215
- hsearch-00216
- hsearch-00217
- hsearch-00218
- hsearch-00219
- hsearch-00220
- hsearch-00221
- hsearch-00222
- hsearch-00224
- hsearch-00225
- hsearch-00226
- hsearch-00227
- hsearch-00228
- hsearch-00229
- hsearch-00230
- hsearch-00231
- hsearch-00232
- hsearch-00233
- hsearch-00234
- hsearch-00235
- hsearch-00236
- hsearch-00237
- hsearch-00238
- hsearch-00239
- hsearch-00240
- jax-ws-00000
- jaxrpc-00000
- jboss-eap4and5to6and7-java-01000
- jboss-eap4and5to6and7-java-02000
- jboss-eap4and5to6and7-java-03000
- jboss-eap4and5to6and7-xml-01000
- jboss-eap4and5to6and7-xml-02000
- jboss-eap4and5to6and7-xml-03000
- jboss-eap4and5to6and7-xml-04000
- jboss-eap4and5to6and7-xml-05000
- jboss-eap4and5to6and7-xml-06000
- jboss-eap4and5to6and7-xml-07000
- jboss-eap5-7-java-02000
- jboss-eap5-7-java-03000
- jboss-eap5-7-java-05000
- jboss-eap5-7-java-06000
- jboss-eap5-7-java-07000
- jboss-eap5-7-java-08000
- jboss-eap5-7-java-08100
- jboss-eap5-7-java-08200
- jboss-eap5-7-java-08300
- jboss-eap5-7-java-08400
- jboss-eap5-7-java-08500
- jboss-eap5-7-java-08600
- jboss-eap5-7-java-08700
- jboss-eap5-7-java-08800
- jboss-eap5-7-java-08900
- jboss-eap5-7-java-09000
- jboss-eap5-7-java-09100
- jboss-eap5-7-xml-01000
- jboss-eap5-7-xml-01000
- jboss-eap5-7-xml-02000
- jboss-eap5-7-xml-02000
- jboss-eap5-7-xml-10000
- jboss-eap5-7-xml-10000
- jboss-eap5-7-xml-13000
- jboss-eap5-7-xml-13000
- jboss-eap5-7-xml-14000
- jboss-eap5-7-xml-16000
- jboss-eap5-7-xml-16000
- jboss-eap5and6to7-java-01000
- jboss-eap5and6to7-java-01000
- jboss-eap5and6to7-java-02000
- jboss-eap5and6to7-java-02000
- jboss-eap5and6to7-java-03000
- jboss-eap5and6to7-java-04000
- jboss-eap5and6to7-java-04000
- jboss-eap5and6to7-java-05000
- jboss-eap5and6to7-java-06000
- jboss-eap5and6to7-java-07000
- jboss-eap5and6to7-java-08000
- jboss-eap5and6to7-java-08000
- jboss-eap5and6to7-java-09000
- jboss-eap5and6to7-xml-05000
- jboss-eap5and6to7-xml-05000
- jboss-eap5and6to7-xml-06000
- jboss-eap5and6to7-xml-06000
- jboss-eap5and6to7-xml-07000
- jboss-eap5and6to7-xml-09000
- jboss-eap5and6to7-xml-09000
- jboss-eap5and6to7-xml-12000
- jboss-eap5and6to7-xml-12000
- jboss-eap5and6to7-xml-17000
- jboss-eap5and6to7-xml-17000
- jboss-eap5and6to7-xml-18000
- jboss-eap5and6to7-xml-18000
- jboss-eap5and6to7-xml-31000
- jboss-eap5and6to7-xml-31500
- jboss-eap5and6to7-xml-32000
- jboss-eap5and6to7-xml-33000
- jboss-eap5and6to7-xml-34000
- jboss-eap5and6to7-xml-34000
- jboss-eap5and6to7-xml-37000
- jboss-eap5and6to7-xml-38000
- jboss-eap5and6to7-xml-38001
- jboss-eap5and6to7-xml-38002
- jboss-eap5and6to7-xml-38003
- jboss-eap5and6to7-xml-38004
- jboss-eap5and6to7-xml-38005
- jboss-eap5and6to7-xml-38006
- jboss-eap5and6to7-xml-38007
- jboss-eap5and6to7-xml-39000
- jboss-eap5and6to7-xml-40000
- maven-artemis-jms-client-00001
- maven-javax-to-jakarta-00001
- maven-javax-to-jakarta-00002
- maven-javax-to-jakarta-00003
- maven-javax-to-jakarta-00004
- maven-javax-to-jakarta-00005
- maven-javax-to-jakarta-00006
- maven-javax-to-jakarta-00007
- maven-javax-to-jakarta-00008
- maven-javax-to-jakarta-00010
- maven-javax-to-jakarta-00011
- maven-javax-to-jakarta-00012
- maven-javax-to-jakarta-00013
- maven-javax-to-jakarta-00014
- maven-javax-to-jakarta-00015
- maven-javax-to-jakarta-00016
- maven-javax-to-jakarta-00017
- maven-jboss-rmi-api_1.0_spec-00001
- microprofile_removed_from_eap-00001
- microprofile_removed_from_eap-00001-01
- microprofile_removed_from_eap-00002
- microprofile_removed_from_eap-00003
- microprofile_removed_from_eap-00004
- move-to-microprofile-rest-client-1.3-00001
- picketlink25-00000
- resteasy-eap5and6to7-000018
- resteasy-eap6-000001
- resteasy-eap6-000002
- resteasy-eap6-000003
- resteasy-eap6-000004
- resteasy-eap6-000005
- resteasy-eap6-000006
- resteasy-eap6-000007
- resteasy-eap6-000008
- resteasy-eap6-000009
- resteasy-eap6-000010
- resteasy-eap6-000011
- resteasy-eap6-000012
- resteasy-eap6-000013
- resteasy-eap6-000014
- resteasy-eap6-000015
- resteasy-eap6-000017
- resteasy-eap6-000019
- resteasy-eap6-000020
- resteasy-eap6-000021
- resteasy-eap6-000022
- resteasy-eap6-000023
- resteasy-eap6-000024
- resteasy-eap6-000025
- resteasy-eap6-000029
- resteasy-eap6-000030
- resteasy-eap6-000032
- resteasy-eap6-000101
- resteasy-eap6-000103
- resteasy-eap6-000104
- resteasy-eap6-000105
- resteasy-eap6-000106
- resteasy-eap6-000107
- resteasy-eap6-000118
- resteasy-eap6-000119
- resteasy-eap6-000120
- resteasy-eap6-000121
- resteasy-eap6-000122
- resteasy-eap6-000123
- resteasy-eap6-000125
- resteasy-eap6-000126
- resteasy-eap6-000127
- resteasy-eap6-000128
- resteasy-eap6-000129
- resteasy-eap6-000130
- resteasy-eap6-000131
- resteasy-eap6-000140
- resteasy-eap6-000141
- resteasy-eap6-000142
- resteasy30-36-00001
- singleton-sessionbean-00001
- weblogic-catchall-01000
- weblogic-catchall-02000
- weblogic-catchall-03000
- weblogic-catchall-06000
- weblogic-catchall-06500
- weblogic-eap7-01000
- weblogic-eap7-01000
- weblogic-eap7-016000
- weblogic-eap7-017000
- weblogic-eap7-02000
- weblogic-eap7-03000
- weblogic-eap7-04000
- weblogic-eap7-05000
- weblogic-eap7-06000
- weblogic-eap7-07000
- weblogic-eap7-08000
- weblogic-eap7-09000
- weblogic-eap7-10000
- weblogic-eap7-11000
- weblogic-eap7-12000
- weblogic-eap7-13000
- weblogic-eap7-15000
- weblogic-ejb-01000
- weblogic-ejb-02000
- weblogic-ejb-03000
- weblogic-ejb-04000
- weblogic-jms-eap7-00000
- weblogic-jms-eap7-01000
- weblogic-jms-eap7-02000
- weblogic-jms-eap7-03000
- weblogic-jms-eap7-04000
- weblogic-jms-eap7-05000
- weblogic-jms-eap7-06000
- weblogic-jms-eap7-07000
- weblogic-jms-eap7-08000
- weblogic-services-eap7-01000
- weblogic-services-eap7-02000
- weblogic-services-eap7-03000
- weblogic-webapp-eap7-01000
- weblogic-webapp-eap7-02000
- weblogic-webapp-eap7-03000
- weblogic-webapp-eap7-04000
- weblogic-webapp-eap7-05000
- weblogic-webapp-eap7-06000
- weblogic-webapp-eap7-07000
- weblogic-webapp-eap7-08000
- weblogic-webapp-eap7-09000
- weblogic-webservices-07000
- weblogic-webservices-eap7-01000
- weblogic-webservices-eap7-02000
- weblogic-webservices-eap7-03000
- weblogic-webservices-eap7-04000
- weblogic-webservices-eap7-05000
- weblogic-webservices-eap7-06000
- weblogic-xml-descriptor-19000
- weblogic-xml-descriptor-eap7-01000
- weblogic-xml-descriptor-eap7-01000
- weblogic-xml-descriptor-eap7-02000
- weblogic-xml-descriptor-eap7-02000
- weblogic-xml-descriptor-eap7-03000
- weblogic-xml-descriptor-eap7-04000
- weblogic-xml-descriptor-eap7-06001
- weblogic-xml-descriptor-eap7-07000
- weblogic-xml-descriptor-eap7-08000
- weblogic-xml-descriptor-eap7-09000
- weblogic-xml-descriptor-eap7-10000
- weblogic-xml-descriptor-eap7-11000
- weblogic-xml-descriptor-eap7-11000
- weblogic-xml-descriptor-eap7-12000
- weblogic-xml-descriptor-eap7-12000
- weblogic-xml-descriptor-eap7-13000
- weblogic-xml-descriptor-eap7-14000
- weblogic-xml-descriptor-eap7-15000
- weblogic-xml-descriptor-eap7-15000
- weblogic-xml-descriptor-eap7-16000
- weblogic-xml-descriptor-eap7-17000
- weblogic-xml-descriptor-eap7-17000
- weblogic-xml-descriptor-eap7-18000
- weblogic-xml-descriptor-eap7-18000
- websphere-catchall-00000
- websphere-catchall-00001
- websphere-catchall-db2-00000
- websphere-jms-eap7-00000
- websphere-jms-eap7-00000
- websphere-jms-eap7-01000
- websphere-jms-eap7-02000
- websphere-jms-eap7-02500
- websphere-jms-eap7-03000
- websphere-jms-eap7-04000
- websphere-mq-eap7-00000
- websphere-mq-eap7-00000
- websphere-mq-eap7-01000
- websphere-mq-eap7-01000
- websphere-mq-eap7-02000
- websphere-mq-eap7-02000
- websphere-mqe-eap7-00000
- websphere-mqe-eap7-01000
- websphere-mqe-eap7-02000
- websphere-mqe-eap7-03000
- websphere-mqe-eap7-04000
- websphere-other-eap7-01000
- websphere-other-eap7-02000
- ws-security-00000
- ws-security-00001
- ws-security-00002
- name: eap8/eap7
description: This ruleset provides analysis of Java EE applications that need to change certain CDI-related method calls.
unmatched:
- deprecated-initialcontextfactory-is-removed-00001
- eap8-ejb-00001
- eap8-ejb-00002
- eap8-ejb-00003
- eap8-faces-00001
- eap8-faces-00002
- eap8-faces-00003
- eap8-faces-00004
- eap8-faces-00005
- eap8-faces-00006
- eap8-faces-00007
- eap8-faces-00008
- eap8-faces-00009
- eap8-resteasy-00001
- eap8-resteasy-00002
- eap8-resteasy-00003
- eap8-resteasy-00004
- eap8-resteasy-00005
- eap8-resteasy-00006
- eap8-resteasy-00007
- eap8-resteasy-00008
- eap8-resteasy-00009
- eap8-resteasy-00010
- eap8-resteasy-00011
- eap8-xml-binding-00001
- eap8-xml-binding-00002
- eap8-xml-binding-00003
- eap8-xml-binding-00004
- eap8-xml-binding-00005
- eap8-xml-binding-00006
- eap8-xml-binding-00007
- eap8-xml-binding-00008
- eap8-xml-binding-00009
- empty-beans-xml-00001
- hibernate-00005
- hibernate-00010
- hibernate-6.2-00010
- hibernate-6.2-00020
- hibernate-6.2-00030
- hibernate-6.2-00040
- hibernate-6.2-00050
- hibernate-search-00010
- hibernate-search-00020
- hibernate-search-00030
- hibernate-search-00040
- hibernate-search-00050
- hibernate-search-00060
- hibernate-search-00070
- hibernate-search-00080
- hibernate-search-00090
- hibernate-search-00100
- hibernate-search-00105
- hibernate-search-00110
- hibernate-search-00120
- hibernate-search-00140
- hibernate-search-00150
- hibernate-search-00160
- hibernate-search-00170
- hibernate-search-00180
- hibernate-search-00190
- hibernate-search-00200
- hibernate-search-00210
- hibernate-search-00220
- hibernate-search-00230
- hibernate-search-00240
- hibernate-search-00250
- hibernate-search-00260
- hibernate-search-00270
- hibernate-search-00280
- hibernate-search-00290
- hibernate-search-00300
- hibernate-search-00310
- hibernate-search-00320
- hibernate-search-00330
- hibernate-search-00340
- hibernate-search-00350
- hibernate-search-00360
- hibernate-search-00370
- hibernate-search-00380
- hibernate-search-00390
- hibernate-search-00400
- hibernate-search-00410
- hibernate-search-00420
- hibernate-search-00430
- hibernate-search-00440
- hibernate-search-00450
- hibernate-search-00460
- hibernate-search-00470
- hibernate-search-00480
- hibernate-search-00490
- hibernate-search-00500
- hibernate-search-00510
- hibernate-search-00520
- hibernate-search-00530
- hibernate-search-00540
- hibernate-search-00550
- hibernate-search-00560
- hibernate-search-00570
- hibernate-search-00580
- hibernate-search-00590
- hibernate-search-00600
- hibernate-search-00610
- hibernate-search-00620
- hibernate-search-00630
- hibernate-search-00640
- hibernate-search-00650
- hibernate-search-00660
- hibernate-search-00670
- hibernate-search-00680
- hibernate-search-00690
- hibernate-search-00700
- hibernate-search-00710
- hibernate-search-00720
- hibernate-search-00730
- hibernate-search-00740
- hibernate-search-00750
- hibernate-search-00760
- hibernate-search-00770
- hibernate-search-00780
- hibernate-search-00790
- hibernate-search-00800
- hibernate-search-00810
- hibernate-search-00820
- hibernate-search-00830
- hibernate-search-00840
- hibernate-search-00850
- hibernate-search-00860
- hibernate-search-00870
- hibernate-search-00880
- hibernate-search-00890
- hibernate-search-00900
- hibernate-search-00910
- hibernate-search-00920
- hibernate-search-00930
- hibernate-search-00940
- hibernate-search-00950
- hibernate-search-00960
- hibernate-search-00970
- hibernate-search-00980
- hibernate-search-00990
- hibernate-search-01000
- hibernate-search-01010
- hibernate-search-01020
- hibernate-search-01030
- hibernate-search-01040
- hibernate-search-6.1-00010
- hibernate-search-6.1-00020
- hibernate-search-6.1-00030
- hibernate-search-6.1-00040
- hibernate-search-6.1-00050
- hibernate-search-6.1-00060
- hibernate-search-6.1-00070
- hibernate-search-6.1-00080
- hibernate-search-6.1-00090
- hibernate-search-6.1-00100
- hibernate-search-6.1-00120
- hibernate-search-6.1-00130
- hibernate-search-6.1-00140
- hibernate-search-6.1-00150
- hibernate-search-6.1-00160
- hibernate-search-6.1-00170
- hibernate-search-6.1-00180
- hibernate-search-6.1-00190
- hibernate6-00020
- hibernate6-00030
- hibernate6-00040
- hibernate6-00050
- hibernate6-00060
- hibernate6-00070
- hibernate6-00080
- hibernate6-00090
- hibernate6-00100
- hibernate6-00110
- hibernate6-00120
- hibernate6-00130
- hibernate6-00140
- hibernate6-00150
- hibernate6-00160
- hibernate6-00170
- hibernate6-00180
- hibernate6-00190
- hibernate6-00200
- hibernate6-00210
- hibernate6-00220
- hibernate6-00230
- hibernate6-00240
- hibernate6-00250
- hibernate6-00251
- hibernate6-00252
- hibernate6-00253
- hibernate6-00254
- hibernate6-00255
- hibernate6-00257
- hibernate6-00270
- hibernate6-00280
- jakarta-cdi-00001
- jakarta-cdi-00002
- jakarta-cdi-00003
- jakarta-cdi-00004
- jakarta-el-00010
- jakarta-el-00020
- jakarta-faces-00001
- jakarta-json-binding-00010
- jakarta-soap-00010
- jakarta-soap-00020
- jakarta-ws-rs-00001
- javaee-to-jakarta-namespaces-00001
- javaee-to-jakarta-namespaces-00002
- javaee-to-jakarta-namespaces-00003
- javaee-to-jakarta-namespaces-00004
- javaee-to-jakarta-namespaces-00005
- javaee-to-jakarta-namespaces-00006
- javaee-to-jakarta-namespaces-00007
- javaee-to-jakarta-namespaces-00008
- javaee-to-jakarta-namespaces-00009
- javaee-to-jakarta-namespaces-00010
- javaee-to-jakarta-namespaces-00011
- javaee-to-jakarta-namespaces-00012
- javaee-to-jakarta-namespaces-00013
- javaee-to-jakarta-namespaces-00014
- javaee-to-jakarta-namespaces-00015
- javaee-to-jakarta-namespaces-00016
- javaee-to-jakarta-namespaces-00017
- javaee-to-jakarta-namespaces-00018
- javaee-to-jakarta-namespaces-00019
- javaee-to-jakarta-namespaces-00020
- javaee-to-jakarta-namespaces-00021
- javaee-to-jakarta-namespaces-00022
- javaee-to-jakarta-namespaces-00023
- javaee-to-jakarta-namespaces-00024
- javaee-to-jakarta-namespaces-00025
- javaee-to-jakarta-namespaces-00026
- javaee-to-jakarta-namespaces-00027
- javaee-to-jakarta-namespaces-00028
- javaee-to-jakarta-namespaces-00029
- javaee-to-jakarta-namespaces-00030
- javaee-to-jakarta-namespaces-00031
- javaee-to-jakarta-namespaces-00032
- javaee-to-jakarta-namespaces-00033
- javaee-to-jakarta-namespaces-00034
- javaee-to-jakarta-namespaces-00035
- javaee-to-jakarta-namespaces-00036
- javaee-to-jakarta-namespaces-00037
- javaee-to-jakarta-namespaces-00038
- javaee-to-jakarta-namespaces-00039
- javaee-to-jakarta-namespaces-00040
- javaee-to-jakarta-namespaces-00041
- javaee-to-jakarta-namespaces-00042
- javaee-to-jakarta-namespaces-00043
- javaee-to-jakarta-namespaces-00044
- javaee-to-jakarta-namespaces-00045
- javaee-to-jakarta-namespaces-00046
- javaee-to-jakarta-namespaces-00047
- javaee-to-jakarta-namespaces-00048
- javaee-to-jakarta-namespaces-00049
- javaee-to-jakarta-namespaces-00050
- javaee-to-jakarta-namespaces-00051
- javaee-to-jakarta-namespaces-00052
- javaee-to-jakarta-namespaces-00053
- javaee-to-jakarta-namespaces-00054
- javaee-to-jakarta-namespaces-00055
- javaee-to-jakarta-namespaces-00056
- javax-to-jakarta-bootstrapping-files-00001
- javax-to-jakarta-dependencies-00001
- javax-to-jakarta-dependencies-00002
- javax-to-jakarta-dependencies-00003
- javax-to-jakarta-dependencies-00004
- javax-to-jakarta-dependencies-00005
- javax-to-jakarta-dependencies-00006
- javax-to-jakarta-dependencies-00007
- javax-to-jakarta-dependencies-00008
- javax-to-jakarta-import-00001
- javax-to-jakarta-properties-00001
- javax-to-jakarta-servlet-00010
- javax-to-jakarta-servlet-00020
- javax-to-jakarta-servlet-00030
- javax-to-jakarta-servlet-00040
- javax-to-jakarta-servlet-00041
- javax-to-jakarta-servlet-00042
- javax-to-jakarta-servlet-00043
- javax-to-jakarta-servlet-00050
- javax-to-jakarta-servlet-00060
- javax-to-jakarta-servlet-00070
- javax-to-jakarta-servlet-00071
- javax-to-jakarta-servlet-00072
- javax-to-jakarta-servlet-00080
- javax-to-jakarta-servlet-00090
- javax-to-jakarta-servlet-00100
- javax-to-jakarta-servlet-00101
- javax-to-jakarta-servlet-00102
- javax-to-jakarta-servlet-00110
- javax-to-jakarta-servlet-00111
- javax-to-jakarta-servlet-00112
- javax-to-jakarta-servlet-00120
- javax-to-jakarta-servlet-00121
- javax-to-jakarta-servlet-00122
- javax-to-jakarta-servlet-00123
- javax-to-jakarta-servlet-00130
- jboss-dependencies-00001
- jboss-dependencies-00002
- jboss-dependencies-00003
- jboss-dependencies-00004
- jboss-dependencies-00005
- jboss-dependencies-00006
- jboss-dependencies-00007
- jboss-dependencies-00008
- jboss-dependencies-00009
- jboss-dependencies-00010
- jboss-dependencies-00011
- jboss-dependencies-00012
- jboss-dependencies-00013
- jboss-dependencies-00014
- jboss-dependencies-00015
- jboss-dependencies-00016
- jboss-dependencies-00017
- jboss-dependencies-00018
- jboss-dependencies-00019
- jboss-dependencies-00020
- jboss-dependencies-00021
- jboss-dependencies-00022
- jboss-dependencies-00023
- jboss-dependencies-00024
- jboss-dependencies-00025
- jboss-dependencies-00026
- jboss-dependencies-00027
- jboss-dependencies-00028
- jboss-dependencies-00030
- jboss-dependencies-00031
- jboss-dependencies-00032
- keycloak-openid-00001
- keycloak-openid-00010
- legacy-vault-00010
- log4j-removed-00001
- log4j-removed-00002
- log4j-removed-00003
- log4j-removed-00004
- log4j-removed-00005
- login-modules-00001
- picketlink-00010
- picketlink-00020
- name: eapxp/thorntail
description: This ruleset provides analysis of Maven built applications that use Thorntail Maven Plugin, which should be replaced by JBoss EAP XP Bootable JAR Maven Plugin, when migrating to JBoss EAP XP.
unmatched:
- eapxp_bootable_jar_maven_plugin_configuration_changes-1
- eapxp_microprofile_metrics_not_supported-00001
- eapxp_microprofile_opentracing_not_supported-00001
- remove_thorntail_yaml_configuration_files-1
- replace_thorntail_boms-1
- replace_thorntail_boms-2
- replace_thorntail_fractions-01
- replace_thorntail_fractions-02
- replace_thorntail_fractions-03
- replace_thorntail_fractions-04
- replace_thorntail_fractions-05
- replace_thorntail_fractions-06
- replace_thorntail_fractions-07
- replace_thorntail_fractions-08
- replace_thorntail_fractions-09
- replace_thorntail_fractions-10
- replace_thorntail_fractions-11
- replace_thorntail_fractions-12
- replace_thorntail_fractions-13
- replace_thorntail_fractions-14
- replace_thorntail_fractions-15
- replace_thorntail_fractions-16
- replace_thorntail_fractions-17
- replace_thorntail_fractions-18
- replace_thorntail_fractions-19
- replace_thorntail_fractions-20
- replace_thorntail_fractions-21
- replace_thorntail_fractions-22
- replace_thorntail_fractions-23
- replace_thorntail_fractions-24
- replace_thorntail_fractions-25
- replace_thorntail_fractions-26
- replace_thorntail_fractions-27
- replace_thorntail_fractions-28
- replace_thorntail_fractions-29
- replace_thorntail_fractions-30
- replace_thorntail_fractions-31
- replace_thorntail_fractions-32
- replace_thorntail_fractions-33
- replace_thorntail_fractions-34
- replace_thorntail_fractions-35
- replace_thorntail_fractions-36
- replace_thorntail_fractions-37
- replace_thorntail_fractions-38
- replace_thorntail_fractions-39
- replace_thorntail_fractions-40
- replace_thorntail_fractions-41
- replace_thorntail_fractions-42
- replace_thorntail_fractions-43
- replace_thorntail_fractions-44
- replace_thorntail_fractions-45
- replace_thorntail_fractions-46
- replace_thorntail_fractions-47
- replace_thorntail_fractions-48
- replace_thorntail_fractions-49
- replace_thorntail_fractions-50
- replace_thorntail_maven_plugin-1
- name: filemappings
description: This rule set configures the organization matching functionality, using known root-package prefixes to identify libraries and other code.
- name: fuse-service-works/soa-p-5
description: This ruleset provides analysis of JBoss SOA Platform 5 applications and provides information on how to migrate these to Red Hat JBoss Fuse Service Works
unmatched:
- soa-p-16000
- soa-p-17000
- soa-p-18000
- soa-p-19000
- soa-p-20000
- soa-p-21000
- soa-p-22000
- soa-p-23000
- soa-p-24000
- soa-p-25000
- soa-p-26000
- soa-p-27000
- soa-p-28000
- soa-p-29000
- soa-p-30000
- soa-p-31000
- soa-p-32000
- soa-p-33000
- soa-p-34000
- soa-p-35000
- soa-p-36000
- soa-p-37000
- soa-p-38000
- soa-p-39000
- soa-p-40000
- soa-p-41000
- soa-p-42000
- soa-p-43000
- soa-p-44000
- soa-p-45000
- soa-p-46000
- soa-p-47000
- soa-p-48000
- soa-p-49000
- soa-p-5-01000
- soa-p-5-01000
- soa-p-5-02000
- soa-p-5-03000
- soa-p-5-04000
- soa-p-5-05000
- soa-p-5-06000
- soa-p-5-07000
- soa-p-5-08000
- soa-p-5-09000
- soa-p-5-10000
- soa-p-5-11000
- soa-p-5-12000
- soa-p-5-13000
- soa-p-5-14000
- soa-p-5-15000
- soa-p-50000
- name: fuse/sonicesb
description: This ruleset contains rules that assist in migrating from Sonic ESB to Apache Camel.
unmatched:
- sonic-catchall-00000
- sonic-esb-01000
- sonic-esb-01000
- sonic-esb-02000
- sonic-esb-03000
- sonic-esb-04000
- sonic-esb-05000
- sonic-esb-06000
- sonic-esb-07000
- sonic-esb-08000
- sonic-esb-09000
- sonic-esb-10000
- sonic-esb-11000
- sonic-esb-12000
- sonic-esb-13000
- sonic-esb-14000
- sonic-esb-15000
- sonic-esb-16000
- sonic-esb-17000
- sonic-esb-18000
- sonic-esb-19000
- sonic-esb-20000
- sonic-esb-21000
- xml-sonic-esb-01000
- name: hibernate
description: This ruleset provides analysis of deprecated Hibernate java constructs and their migration to newer one.
unmatched:
- hibernate-01000
- hibernate-02000
- hibernate-03000
- hibernate-04000
- hibernate-05000
- hibernate-06000
- hibernate-07000
- hibernate-08000
- hibernate-09000
- hibernate-10000
- hibernate-10100
- hibernate-10100
- hibernate-catchall-00000
- hibernate-catchall-00000
- hibernate-xml-01000
- hibernate-xml-02000
- hibernate-xml-03000
- hibernate-xml-04000
- hibernate-xml-04000
- hibernate-xml-05000
- hibernate-xml-05000
- name: jakarta-ee9
unmatched:
- spring-components-00001
- spring-components-00002
- name: jws5
description: This ruleset provides analysis of applications that need to change their pom dependencies to upgrade dependencies that belong to the groupId `org.apache.tomcat`
unmatched:
- upgrade-tomcat-dependencies-00001
- name: kai/quarkus
description: Quarkus focused rules to help migrate from Java EE
unmatched:
- remote-ejb-to-quarkus-00000
- name: openjdk11/openjdk8
description: This ruleset provides analysis with respect to API removals between OpenJDK 8 and 11.
unmatched:
- java-removals-00000
- java-removals-00010
- java-removals-00020
- java-removals-00030
- java-removals-00040
- java-removals-00041
- java-removals-00050
- java-removals-00060
- java-removals-00100
- java-removals-00110
- java-removals-00120
- java-removals-00130
- java-removals-00140
- java-removals-00150
- removed-javaee-modules-00000
- removed-javaee-modules-00010
- removed-javaee-modules-00020
- name: openjdk17
description: This ruleset provides analysis regarding deprecated APIs in OpenJDK 21.
unmatched:
- deprecation-00000
- deprecation-00005
- deprecation-00010
- deprecation-00020
- deprecation-00030
- dynamic-agents-00000
- finalization-deprecation-00000
- finalization-deprecation-00010
- removed-apis-00000
- removed-apis-00005
- removed-apis-00010
- removed-apis-00015
- utf-8-by-default-00000
- utf-8-by-default-00010
- utf-8-by-default-00020
- utf-8-by-default-00030
- name: openjdk17/openjdk11
description: This ruleset provides analysis Security Manager classes and methods deprecated between OpenJDK 11 to 17.
unmatched:
- applet-api-deprecation-00000
- lombok-incompatibility-00001
- removed-classes-00000
- removed-packages-00000
- removed-packages-00010
- security-manager-deprecation-00000
- security-manager-deprecation-00010
- security-manager-deprecation-00020
- security-manager-deprecation-00030
- security-manager-deprecation-00040
- security-manager-deprecation-00050
- security-manager-deprecation-00060
- security-manager-deprecation-00070
- name: openjdk7/oraclejdk7
description: This ruleset provides analysis with respect to the migration from OracleJDK to OpenJDK.
unmatched:
- oracle2openjdk-00000
- oracle2openjdk-00001
- oracle2openjdk-00002
- oracle2openjdk-00003
- oracle2openjdk-00004
- oracle2openjdk-00005
- oracle2openjdk-00006
- name: openliberty/websphere
description: This ruleset identifies usage of Java APIs and technologies which are not provided by Open Liberty.
unmatched:
- ActivitySessionRule
- AppProfileRule
- AsyncBeansSchedulerRule
- BatchFeaturePackRule
- DetectEJBEntityBeansXML
- DetectJAXRJava
- DetectJAXRPC
- DetectJavaApplicationDeploymentJava
- DetectJavaPortlet
- DetectPolicySetAndWsSecurity
- DetectRemoteBundleRepositoriesJava
- DetectRemoteServicesJava
- DetectTransactionPropagationEJBRemote
- DetectWSATXML
- DetectWSBAJava
- DetectWSNotificationJava
- DynamicCacheRule
- DynamicQueryRule
- I18nRule
- MTOMRule
- SOAPOverJMSRule
- ServerName
- StartupBeanRule
- WOLAMissingClassesRule
- WOLARule
- WSNotificationRuleJava
- WebSphereSchedulerRule
- WebSphereSdoRule
- WebSphereServletRule
- WebSphereUnavailableAPIsAppClient
- WebSphereUnavailableAPIsConnectorArchitecture
- WebSphereUnavailableAPIsEnterpriseJavaBeans
- WebSphereUnavailableAPIsExceptions
- WebSphereUnavailableAPIsExtHelper
- WebSphereUnavailableAPIsExtensionRegistry
- WebSphereUnavailableAPIsISC
- WebSphereUnavailableAPIsLoggingAndRAS
- WebSphereUnavailableAPIsManagement
- WebSphereUnavailableAPIsORB
- WebSphereUnavailableAPIsPMI
- WebSphereUnavailableAPIsPortal
- WebSphereUnavailableAPIsResourceAdapter
- WebSphereUnavailableAPIsSIB
- WebSphereUnavailableAPIsSMF
- WebSphereUnavailableAPIsSecurity
- WebSphereUnavailableAPIsTPV
- WebSphereUnavailableAPIsUDDI
- WebSphereUnavailableAPIsWLM
- WebSphereUnavailableAPIsWSADIE
- WebSphereUnavailableAPIsWSSecurityHelper
- WebSphereUnavailableSPIsRRD
- WebSphereUnavailableSSOCookieMethod
- WebSphereUnavailableSSOTokenMethod
- WebSphereWebServicesGeneratedClassesRule
- WebSphereWebServicesRule
- WorkAreaRule
- XMLFeaturePackRule
- name: os/windows
description: This is a ruleset for Windows operating system specific rules while migrating to Linux operating system.
unmatched:
- os-specific-00001
- os-specific-00002
- name: quarkus/springboot
description: This ruleset gives hints to migrate from SpringBoot devtools to Quarkus
violations:
javaee-pom-to-quarkus-00000:
description: The expected project artifact's extension is `jar`
category: mandatory
labels:
- konveyor.io/source=java-ee
- konveyor.io/target=quarkus
incidents:
- uri: file:///opt/input/source/pom.xml
message: The project artifact's current extension (i.e. `<packaging>` tag value) is `` but the expected value should be `jar`
codeSnip: " 1 <?xml version=\"1.0\" encoding=\"UTF-8\"?>\n 2 <!--\n 3 JBoss, Home of Professional Open Source\n 4 Copyright 2015, Red Hat, Inc. and/or its affiliates, and individual\n 5 contributors by the @authors tag. See the copyright.txt in the\n 6 distribution for a full listing of individual contributors.\n 7 \n 8 Licensed under the Apache License, Version 2.0 (the \"License\");\n 9 you may not use this file except in compliance with the License.\n 10 You may obtain a copy of the License at\n 11 http://www.apache.org/licenses/LICENSE-2.0\n 12 Unless required by applicable law or agreed to in writing, software\n 13 distributed under the License is distributed on an \"AS IS\" BASIS,\n 14 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n 15 See the License for the specific language governing permissions and\n 16 limitations under the License.\n 17 -->\n 18 <project xmlns=\"http://maven.apache.org/POM/4.0.0\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd\">\n 19 <modelVersion>4.0.0</modelVersion>\n 20 <parent>\n 21 <groupId>org.jboss.eap.quickstarts</groupId>\n 22 <artifactId>quickstart-parent</artifactId>\n 23 <!--\n 24 Maintain separation between the artifact id and the version to help prevent\n 25 merge conflicts between commits changing the GA and those changing the V.\n 26 -->\n 27 <version>7.4.0.GA</version>\n 28 <relativePath>../pom.xml</relativePath>\n 29 </parent>\n 30 <artifactId>ejb-remote</artifactId>\n 31 <packaging>pom</packaging>\n 32 <name>Quickstart: ejb-remote</name>\n 33 <description>This project demonstrates how to access an EJB from a remote client</description>\n 34 \n 35 <licenses>\n 36 <license>\n 37 <name>Apache License, Version 2.0</name>\n 38 <url>http://www.apache.org/licenses/LICENSE-2.0.html</url>\n 39 <distribution>repo</distribution>\n 40 </license>\n 41 </licenses>\n 42 \n 43 <!-- This quickstart consists of a server side component and a client that accesses\n 44 the server side component. Each component has its own self contain pom. However,\n 45 you can add these modules here to keep things modular.\n 46 -->\n 47 <modules>\n 48 <module>server-side</module>\n 49 <module>client</module>\n 50 </modules>\n 51 \n 52 <build>\n 53 <plugins>\n 54 <plugin>\n 55 <groupId>org.wildfly.plugins</groupId>\n 56 <artifactId>wildfly-maven-plugin</artifactId>\n 57 <configuration>\n 58 <skip>true</skip>\n 59 </configuration>\n 60 </plugin>\n 61 </plugins>\n 62 </build>\n 63 </project>\n"
lineNumber: 28
variables:
data: pom
innerText: pom
matchingXML: ""
- uri: file:///opt/input/source/server-side/pom.xml
message: The project artifact's current extension (i.e. `<packaging>` tag value) is `` but the expected value should be `jar`
codeSnip: " 1 <?xml version=\"1.0\" encoding=\"UTF-8\"?>\n 2 <!--\n 3 JBoss, Home of Professional Open Source\n 4 Copyright 2015, Red Hat, Inc. and/or its affiliates, and individual\n 5 contributors by the @authors tag. See the copyright.txt in the\n 6 distribution for a full listing of individual contributors.\n 7 \n 8 Licensed under the Apache License, Version 2.0 (the \"License\");\n 9 you may not use this file except in compliance with the License.\n 10 You may obtain a copy of the License at\n 11 http://www.apache.org/licenses/LICENSE-2.0\n 12 Unless required by applicable law or agreed to in writing, software\n 13 distributed under the License is distributed on an \"AS IS\" BASIS,\n 14 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n 15 See the License for the specific language governing permissions and\n 16 limitations under the License.\n 17 -->\n 18 <project xmlns=\"http://maven.apache.org/POM/4.0.0\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd\">\n 19 <modelVersion>4.0.0</modelVersion>\n 20 <parent>\n 21 <groupId>org.jboss.eap.quickstarts</groupId>\n 22 <artifactId>ejb-remote</artifactId>\n 23 <version>7.4.0.GA</version>\n 24 <relativePath>../pom.xml</relativePath>\n 25 </parent>\n 26 <artifactId>ejb-remote-server-side</artifactId>\n 27 <packaging>ejb</packaging>\n 28 <name>Quickstart: ejb-remote - server-side</name>\n 29 <description>This project demonstrates how to access an EJB from a remote client; this is the server side POM file</description>\n 30 \n 31 <licenses>\n 32 <license>\n 33 <name>Apache License, Version 2.0</name>\n 34 <url>http://www.apache.org/licenses/LICENSE-2.0.html</url>\n 35 <distribution>repo</distribution>\n 36 </license>\n 37 </licenses>\n 38 \n 39 <dependencies>\n 40 \n 41 <!-- Import the Common Annotations API (JSR-250), we use provided scope\n 42 as the API is included in JBoss EAP -->\n 43 <dependency>\n 44 <groupId>org.jboss.spec.javax.annotation</groupId>\n 45 <artifactId>jboss-annotations-api_1.3_spec</artifactId>\n 46 <scope>provided</scope>\n 47 </dependency>\n 48 \n 49 <!-- Import the EJB API, we use provided scope as the API is included in JBoss EAP -->\n 50 <dependency>\n 51 <groupId>org.jboss.spec.javax.ejb</groupId>\n 52 <artifactId>jboss-ejb-api_3.2_spec</artifactId>\n 53 <scope>provided</scope>\n 54 </dependency>\n 55 \n 56 </dependencies>\n 57 \n 58 <build>\n 59 <plugins>\n 60 <!-- WildFly plug-in to deploy the application -->\n 61 <plugin>\n 62 <groupId>org.wildfly.plugins</groupId>\n 63 <artifactId>wildfly-maven-plugin</artifactId>\n 64 <configuration>\n 65 <skip>false</skip>\n 66 <filename>${project.build.finalName}.jar</filename>\n 67 </configuration>\n 68 </plugin>\n 69 <plugin>\n 70 <groupId>org.apache.maven.plugins</groupId>\n 71 <artifactId>maven-ejb-plugin</artifactId>\n 72 <configuration>\n 73 <ejbVersion>3.2</ejbVersion>\n 74 <!-- this is false by default -->\n 75 <generateClient>true</generateClient>\n 76 </configuration>\n 77 </plugin>\n 78 \n 79 </plugins>\n 80 </build>\n 81 \n 82 </project>\n"
lineNumber: 22
variables:
data: ejb
innerText: ejb
matchingXML: ""
links:
- url: https://quarkus.io/guides/maven-tooling#build-tool-maven;
title: Quarkus - Guide;
effort: 1
javaee-pom-to-quarkus-00010:
description: Adopt Quarkus BOM
category: mandatory
labels:
- konveyor.io/source=java-ee
- konveyor.io/target=quarkus
incidents:
- uri: file:///opt/input/source/client/pom.xml
message: "Use the Quarkus BOM to omit the version of the different Quarkus dependencies. \n Add the following sections to the `pom.xml` file: \n\n ```xml\n <properties> \n <quarkus.platform.artifact-id>quarkus-bom</quarkus.platform.artifact-id> \n <quarkus.platform.group-id>io.quarkus.platform</quarkus.platform.group-id> \n <quarkus.platform.version>3.1.0.Final</quarkus.platform.version>\n </properties> \n <dependencyManagement> \n <dependencies> \n <dependency> \n <groupId>$</groupId> \n <artifactId>$</artifactId> \n <version>$</version> \n <type>pom</type> \n <scope>import</scope> \n </dependency> \n </dependencies> \n </dependencyManagement> \n ```\n Check the latest Quarkus version available from the `Quarkus - Releases` link below."
codeSnip: " 1 <?xml version=\"1.0\" encoding=\"UTF-8\"?>\n 2 <!--\n 3 JBoss, Home of Professional Open Source\n 4 Copyright 2015, Red Hat, Inc. and/or its affiliates, and individual\n 5 contributors by the @authors tag. See the copyright.txt in the\n 6 distribution for a full listing of individual contributors.\n 7 \n 8 Licensed under the Apache License, Version 2.0 (the \"License\");\n 9 you may not use this file except in compliance with the License.\n 10 You may obtain a copy of the License at\n 11 http://www.apache.org/licenses/LICENSE-2.0\n 12 Unless required by applicable law or agreed to in writing, software\n 13 distributed under the License is distributed on an \"AS IS\" BASIS,\n 14 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n 15 See the License for the specific language governing permissions and\n 16 limitations under the License.\n 17 -->\n 18 <project xmlns=\"http://maven.apache.org/POM/4.0.0\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd\">\n 19 <modelVersion>4.0.0</modelVersion>\n 20 \n 21 <parent>\n 22 <groupId>org.jboss.eap.quickstarts</groupId>\n 23 <artifactId>ejb-remote</artifactId>\n 24 <version>7.4.0.GA</version>\n 25 <relativePath>../pom.xml</relativePath>\n 26 </parent>\n 27 <artifactId>ejb-remote-client</artifactId>\n 28 <packaging>jar</packaging>\n 29 <name>Quickstart: ejb-remote - client</name>\n 30 <description>This project demonstrates how to access an EJB from a remote client; this is the client POM file</description>\n 31 \n 32 <properties>\n 33 <http>false</http>\n 34 </properties>\n 35 \n 36 <dependencies>\n 37 <!-- The EJB Client BOM provides application server-compatible dependency management,\n 38 used for building, testing or debugging EJB client applications. Import the BOM to the\n 39 dependency management section of the app's pom.xml file and then set dependencies on specific artifacts.\n 40 Alternatively, as shown in the following example, set a single dependency on the BOM for the app to depend\n 41 on all the artifacts it manages.\n 42 -->\n 43 <dependency>\n 44 <groupId>org.jboss.eap</groupId>\n 45 <artifactId>wildfly-ejb-client-bom</artifactId>\n 46 <type>pom</type>\n 47 <scope>compile</scope>\n 48 </dependency>\n 49 \n 50 <!-- We depend on the EJB remote business interfaces of this application -->\n 51 <dependency>\n 52 <groupId>${project.groupId}</groupId>\n 53 <artifactId>ejb-remote-server-side</artifactId>\n 54 <version>${project.version}</version>\n 55 <type>ejb-client</type>\n 56 </dependency>\n 57 \n 58 </dependencies>\n 59 \n 60 <build>\n 61 <plugins>\n 62 \n 63 <!-- Add the maven exec plug-in to allow us to run a java program\n 64 via maven -->\n 65 <plugin>\n 66 <groupId>org.codehaus.mojo</groupId>\n 67 <artifactId>exec-maven-plugin</artifactId>\n 68 <configuration>\n 69 <executable>java</executable>\n 70 <workingDirectory>${project.build.directory}/exec-working-directory</workingDirectory>\n 71 <arguments>\n 72 <argument>-Dhttp=${http}</argument>\n 73 <argument>-classpath</argument>\n 74 <classpath />\n 75 <argument>org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient</argument>\n 76 </arguments>\n 77 <!--<detail>true</detail>-->\n 78 </configuration>\n 79 </plugin>\n 80 <!-- build standalone exe jar -->\n 81 <plugin>\n 82 <groupId>org.apache.maven.plugins</groupId>\n 83 <artifactId>maven-assembly-plugin</artifactId>\n 84 <configuration>\n 85 <descriptorRefs>\n 86 <descriptorRef>jar-with-dependencies</descriptorRef>\n 87 </descriptorRefs>\n 88 <archive>\n 89 <manifest>\n 90 <mainClass>org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient</mainClass>\n 91 </manifest>\n 92 <manifestEntries>\n 93 <Multi-Release>true</Multi-Release>\n 94 </manifestEntries>\n 95 </archive>\n 96 </configuration>\n 97 </plugin>\n 98 </plugins>\n 99 \n100 </build>\n101 \n102 </project>\n"
lineNumber: 19
variables:
data: project
innerText: "\n 4.0.0\n\n \n org.jboss.eap.quickstarts\n ejb-remote\n 7.4.0.GA\n ../pom.xml\n \n ejb-remote-client\n jar\n Quickstart: ejb-remote - client\n This project demonstrates how to access an EJB from a remote client; this is the client POM file\n\n \n false\n \n\n \n \n \n org.jboss.eap\n wildfly-ejb-client-bom\n pom\n compile\n \n\n \n \n ${project.groupId}\n ejb-remote-server-side\n ${project.version}\n ejb-client\n \n\n \n\n \n \n\n \n \n org.codehaus.mojo\n exec-maven-plugin\n \n java\n ${project.build.directory}/exec-working-directory\n \n -Dhttp=${http}\n -classpath\n \n org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient\n \n \n \n \n \n \n org.apache.maven.plugins\n maven-assembly-plugin\n \n \n jar-with-dependencies\n \n \n \n org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient\n \n \n true\n \n \n \n \n \n\n \n\n"
matchingXML: |-
<modelVersion>4.0.0</modelVersion><parent><groupId>org.jboss.eap.quickstarts</groupId><artifactId>ejb-remote</artifactId><version>7.4.0.GA</version><relativePath>../pom.xml</relativePath></parent><artifactId>ejb-remote-client</artifactId><packaging>jar</packaging><name>Quickstart: ejb-remote - client</name><description>This project demonstrates how to access an EJB from a remote client; this is the client POM file</description><properties><http>false</http></properties><dependencies><!-- The EJB Client BOM provides application server-compatible dependency management,
used for building, testing or debugging EJB client applications. Import the BOM to the
dependency management section of the app's pom.xml file and then set dependencies on specific artifacts.
Alternatively, as shown in the following example, set a single dependency on the BOM for the app to depend
on all the artifacts it manages.
--><dependency><groupId>org.jboss.eap</groupId><artifactId>wildfly-ejb-client-bom</artifactId><type>pom</type><scope>compile</scope></dependency><!-- We depend on the EJB remote business interfaces of this application --><dependency><groupId>${project.groupId}</groupId><artifactId>ejb-remote-server-side</artifactId><version>${project.version}</version><type>ejb-client</type></dependency></dependencies><build><plugins><!-- Add the maven exec plug-in to allow us to run a java program
via maven --><plugin><groupId>org.codehaus.mojo</groupId><artifactId>exec-maven-plugin</artifactId><configuration><executable>java</executable><workingDirectory>${project.build.directory}/exec-working-directory</workingDirectory><arguments><argument>-Dhttp=${http}</argument><argument>-classpath</argument><classpath></classpath><argument>org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient</argument></arguments><!--<detail>true</detail>--></configuration></plugin><!-- build standalone exe jar --><plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-assembly-plugin</artifactId><configuration><descriptorRefs><descriptorRef>jar-with-dependencies</descriptorRef></descriptorRefs><archive><manifest><mainClass>org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient</mainClass></manifest><manifestEntries><Multi-Release>true</Multi-Release></manifestEntries></archive></configuration></plugin></plugins></build>
- uri: file:///opt/input/source/pom.xml
message: "Use the Quarkus BOM to omit the version of the different Quarkus dependencies. \n Add the following sections to the `pom.xml` file: \n\n ```xml\n <properties> \n <quarkus.platform.artifact-id>quarkus-bom</quarkus.platform.artifact-id> \n <quarkus.platform.group-id>io.quarkus.platform</quarkus.platform.group-id> \n <quarkus.platform.version>3.1.0.Final</quarkus.platform.version>\n </properties> \n <dependencyManagement> \n <dependencies> \n <dependency> \n <groupId>$</groupId> \n <artifactId>$</artifactId> \n <version>$</version> \n <type>pom</type> \n <scope>import</scope> \n </dependency> \n </dependencies> \n </dependencyManagement> \n ```\n Check the latest Quarkus version available from the `Quarkus - Releases` link below."
codeSnip: " 1 <?xml version=\"1.0\" encoding=\"UTF-8\"?>\n 2 <!--\n 3 JBoss, Home of Professional Open Source\n 4 Copyright 2015, Red Hat, Inc. and/or its affiliates, and individual\n 5 contributors by the @authors tag. See the copyright.txt in the\n 6 distribution for a full listing of individual contributors.\n 7 \n 8 Licensed under the Apache License, Version 2.0 (the \"License\");\n 9 you may not use this file except in compliance with the License.\n 10 You may obtain a copy of the License at\n 11 http://www.apache.org/licenses/LICENSE-2.0\n 12 Unless required by applicable law or agreed to in writing, software\n 13 distributed under the License is distributed on an \"AS IS\" BASIS,\n 14 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n 15 See the License for the specific language governing permissions and\n 16 limitations under the License.\n 17 -->\n 18 <project xmlns=\"http://maven.apache.org/POM/4.0.0\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd\">\n 19 <modelVersion>4.0.0</modelVersion>\n 20 <parent>\n 21 <groupId>org.jboss.eap.quickstarts</groupId>\n 22 <artifactId>quickstart-parent</artifactId>\n 23 <!--\n 24 Maintain separation between the artifact id and the version to help prevent\n 25 merge conflicts between commits changing the GA and those changing the V.\n 26 -->\n 27 <version>7.4.0.GA</version>\n 28 <relativePath>../pom.xml</relativePath>\n 29 </parent>\n 30 <artifactId>ejb-remote</artifactId>\n 31 <packaging>pom</packaging>\n 32 <name>Quickstart: ejb-remote</name>\n 33 <description>This project demonstrates how to access an EJB from a remote client</description>\n 34 \n 35 <licenses>\n 36 <license>\n 37 <name>Apache License, Version 2.0</name>\n 38 <url>http://www.apache.org/licenses/LICENSE-2.0.html</url>\n 39 <distribution>repo</distribution>\n 40 </license>\n 41 </licenses>\n 42 \n 43 <!-- This quickstart consists of a server side component and a client that accesses\n 44 the server side component. Each component has its own self contain pom. However,\n 45 you can add these modules here to keep things modular.\n 46 -->\n 47 <modules>\n 48 <module>server-side</module>\n 49 <module>client</module>\n 50 </modules>\n 51 \n 52 <build>\n 53 <plugins>\n 54 <plugin>\n 55 <groupId>org.wildfly.plugins</groupId>\n 56 <artifactId>wildfly-maven-plugin</artifactId>\n 57 <configuration>\n 58 <skip>true</skip>\n 59 </configuration>\n 60 </plugin>\n 61 </plugins>\n 62 </build>\n 63 </project>\n"
lineNumber: 19
variables:
data: project
innerText: "\n 4.0.0\n \n org.jboss.eap.quickstarts\n quickstart-parent\n \n 7.4.0.GA\n ../pom.xml\n \n ejb-remote\n pom\n Quickstart: ejb-remote\n This project demonstrates how to access an EJB from a remote client\n\n \n \n Apache License, Version 2.0\n http://www.apache.org/licenses/LICENSE-2.0.html\n repo\n \n \n\n \n \n server-side\n client\n \n\n \n \n \n org.wildfly.plugins\n wildfly-maven-plugin\n \n true\n \n \n \n \n"
matchingXML: |-
<modelVersion>4.0.0</modelVersion><parent><groupId>org.jboss.eap.quickstarts</groupId><artifactId>quickstart-parent</artifactId><!--
Maintain separation between the artifact id and the version to help prevent
merge conflicts between commits changing the GA and those changing the V.
--><version>7.4.0.GA</version><relativePath>../pom.xml</relativePath></parent><artifactId>ejb-remote</artifactId><packaging>pom</packaging><name>Quickstart: ejb-remote</name><description>This project demonstrates how to access an EJB from a remote client</description><licenses><license><name>Apache License, Version 2.0</name><url>http://www.apache.org/licenses/LICENSE-2.0.html</url><distribution>repo</distribution></license></licenses><!-- This quickstart consists of a server side component and a client that accesses
the server side component. Each component has its own self contain pom. However,
you can add these modules here to keep things modular.
--><modules><module>server-side</module><module>client</module></modules><build><plugins><plugin><groupId>org.wildfly.plugins</groupId><artifactId>wildfly-maven-plugin</artifactId><configuration><skip>true</skip></configuration></plugin></plugins></build>
- uri: file:///opt/input/source/server-side/pom.xml
message: "Use the Quarkus BOM to omit the version of the different Quarkus dependencies. \n Add the following sections to the `pom.xml` file: \n\n ```xml\n <properties> \n <quarkus.platform.artifact-id>quarkus-bom</quarkus.platform.artifact-id> \n <quarkus.platform.group-id>io.quarkus.platform</quarkus.platform.group-id> \n <quarkus.platform.version>3.1.0.Final</quarkus.platform.version>\n </properties> \n <dependencyManagement> \n <dependencies> \n <dependency> \n <groupId>$</groupId> \n <artifactId>$</artifactId> \n <version>$</version> \n <type>pom</type> \n <scope>import</scope> \n </dependency> \n </dependencies> \n </dependencyManagement> \n ```\n Check the latest Quarkus version available from the `Quarkus - Releases` link below."
codeSnip: " 1 <?xml version=\"1.0\" encoding=\"UTF-8\"?>\n 2 <!--\n 3 JBoss, Home of Professional Open Source\n 4 Copyright 2015, Red Hat, Inc. and/or its affiliates, and individual\n 5 contributors by the @authors tag. See the copyright.txt in the\n 6 distribution for a full listing of individual contributors.\n 7 \n 8 Licensed under the Apache License, Version 2.0 (the \"License\");\n 9 you may not use this file except in compliance with the License.\n 10 You may obtain a copy of the License at\n 11 http://www.apache.org/licenses/LICENSE-2.0\n 12 Unless required by applicable law or agreed to in writing, software\n 13 distributed under the License is distributed on an \"AS IS\" BASIS,\n 14 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n 15 See the License for the specific language governing permissions and\n 16 limitations under the License.\n 17 -->\n 18 <project xmlns=\"http://maven.apache.org/POM/4.0.0\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd\">\n 19 <modelVersion>4.0.0</modelVersion>\n 20 <parent>\n 21 <groupId>org.jboss.eap.quickstarts</groupId>\n 22 <artifactId>ejb-remote</artifactId>\n 23 <version>7.4.0.GA</version>\n 24 <relativePath>../pom.xml</relativePath>\n 25 </parent>\n 26 <artifactId>ejb-remote-server-side</artifactId>\n 27 <packaging>ejb</packaging>\n 28 <name>Quickstart: ejb-remote - server-side</name>\n 29 <description>This project demonstrates how to access an EJB from a remote client; this is the server side POM file</description>\n 30 \n 31 <licenses>\n 32 <license>\n 33 <name>Apache License, Version 2.0</name>\n 34 <url>http://www.apache.org/licenses/LICENSE-2.0.html</url>\n 35 <distribution>repo</distribution>\n 36 </license>\n 37 </licenses>\n 38 \n 39 <dependencies>\n 40 \n 41 <!-- Import the Common Annotations API (JSR-250), we use provided scope\n 42 as the API is included in JBoss EAP -->\n 43 <dependency>\n 44 <groupId>org.jboss.spec.javax.annotation</groupId>\n 45 <artifactId>jboss-annotations-api_1.3_spec</artifactId>\n 46 <scope>provided</scope>\n 47 </dependency>\n 48 \n 49 <!-- Import the EJB API, we use provided scope as the API is included in JBoss EAP -->\n 50 <dependency>\n 51 <groupId>org.jboss.spec.javax.ejb</groupId>\n 52 <artifactId>jboss-ejb-api_3.2_spec</artifactId>\n 53 <scope>provided</scope>\n 54 </dependency>\n 55 \n 56 </dependencies>\n 57 \n 58 <build>\n 59 <plugins>\n 60 <!-- WildFly plug-in to deploy the application -->\n 61 <plugin>\n 62 <groupId>org.wildfly.plugins</groupId>\n 63 <artifactId>wildfly-maven-plugin</artifactId>\n 64 <configuration>\n 65 <skip>false</skip>\n 66 <filename>${project.build.finalName}.jar</filename>\n 67 </configuration>\n 68 </plugin>\n 69 <plugin>\n 70 <groupId>org.apache.maven.plugins</groupId>\n 71 <artifactId>maven-ejb-plugin</artifactId>\n 72 <configuration>\n 73 <ejbVersion>3.2</ejbVersion>\n 74 <!-- this is false by default -->\n 75 <generateClient>true</generateClient>\n 76 </configuration>\n 77 </plugin>\n 78 \n 79 </plugins>\n 80 </build>\n 81 \n 82 </project>\n"
lineNumber: 19
variables:
data: project
innerText: "\n 4.0.0\n \n org.jboss.eap.quickstarts\n ejb-remote\n 7.4.0.GA\n ../pom.xml\n \n ejb-remote-server-side\n ejb\n Quickstart: ejb-remote - server-side\n This project demonstrates how to access an EJB from a remote client; this is the server side POM file\n\n \n \n Apache License, Version 2.0\n http://www.apache.org/licenses/LICENSE-2.0.html\n repo\n \n \n\n \n\n \n \n org.jboss.spec.javax.annotation\n jboss-annotations-api_1.3_spec\n provided\n \n\n \n \n org.jboss.spec.javax.ejb\n jboss-ejb-api_3.2_spec\n provided\n \n\n \n\n \n \n \n \n org.wildfly.plugins\n wildfly-maven-plugin\n \n false\n ${project.build.finalName}.jar\n \n \n \n org.apache.maven.plugins\n maven-ejb-plugin\n \n 3.2\n \n true\n \n \n\n \n \n\n"
matchingXML: |-
<modelVersion>4.0.0</modelVersion><parent><groupId>org.jboss.eap.quickstarts</groupId><artifactId>ejb-remote</artifactId><version>7.4.0.GA</version><relativePath>../pom.xml</relativePath></parent><artifactId>ejb-remote-server-side</artifactId><packaging>ejb</packaging><name>Quickstart: ejb-remote - server-side</name><description>This project demonstrates how to access an EJB from a remote client; this is the server side POM file</description><licenses><license><name>Apache License, Version 2.0</name><url>http://www.apache.org/licenses/LICENSE-2.0.html</url><distribution>repo</distribution></license></licenses><dependencies><!-- Import the Common Annotations API (JSR-250), we use provided scope
as the API is included in JBoss EAP --><dependency><groupId>org.jboss.spec.javax.annotation</groupId><artifactId>jboss-annotations-api_1.3_spec</artifactId><scope>provided</scope></dependency><!-- Import the EJB API, we use provided scope as the API is included in JBoss EAP --><dependency><groupId>org.jboss.spec.javax.ejb</groupId><artifactId>jboss-ejb-api_3.2_spec</artifactId><scope>provided</scope></dependency></dependencies><build><plugins><!-- WildFly plug-in to deploy the application --><plugin><groupId>org.wildfly.plugins</groupId><artifactId>wildfly-maven-plugin</artifactId><configuration><skip>false</skip><filename>${project.build.finalName}.jar</filename></configuration></plugin><plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-ejb-plugin</artifactId><configuration><ejbVersion>3.2</ejbVersion><!-- this is false by default --><generateClient>true</generateClient></configuration></plugin></plugins></build>
links:
- url: https://quarkus.io/guides/maven-tooling#build-tool-maven;
title: Quarkus - Guide;
- url: https://quarkus.io/blog/tag/release/
title: Quarkus - Releases
effort: 1
javaee-pom-to-quarkus-00020:
description: Adopt Quarkus Maven plugin
category: mandatory
labels:
- konveyor.io/source=java-ee
- konveyor.io/target=quarkus
incidents:
- uri: file:///opt/input/source/client/pom.xml
message: "Use the Quarkus Maven plugin adding the following sections to the `pom.xml` file: \n\n ```xml\n <properties> \n <quarkus.platform.group-id>io.quarkus.platform</quarkus.platform.group-id> \n <quarkus.platform.version>3.1.0.Final</quarkus.platform.version>\n </properties> \n <build>\n <plugins>\n <plugin>\n <groupId>$</groupId>\n <artifactId>quarkus-maven-plugin</artifactId>\n <version>$</version>\n <extensions>true</extensions>\n <executions>\n <execution>\n <goals>\n <goal>build</goal>\n <goal>generate-code</goal>\n <goal>generate-code-tests</goal>\n </goals>\n </execution>\n </executions>\n </plugin>\n </plugins>\n </build>\n ```"
codeSnip: " 1 <?xml version=\"1.0\" encoding=\"UTF-8\"?>\n 2 <!--\n 3 JBoss, Home of Professional Open Source\n 4 Copyright 2015, Red Hat, Inc. and/or its affiliates, and individual\n 5 contributors by the @authors tag. See the copyright.txt in the\n 6 distribution for a full listing of individual contributors.\n 7 \n 8 Licensed under the Apache License, Version 2.0 (the \"License\");\n 9 you may not use this file except in compliance with the License.\n 10 You may obtain a copy of the License at\n 11 http://www.apache.org/licenses/LICENSE-2.0\n 12 Unless required by applicable law or agreed to in writing, software\n 13 distributed under the License is distributed on an \"AS IS\" BASIS,\n 14 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n 15 See the License for the specific language governing permissions and\n 16 limitations under the License.\n 17 -->\n 18 <project xmlns=\"http://maven.apache.org/POM/4.0.0\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd\">\n 19 <modelVersion>4.0.0</modelVersion>\n 20 \n 21 <parent>\n 22 <groupId>org.jboss.eap.quickstarts</groupId>\n 23 <artifactId>ejb-remote</artifactId>\n 24 <version>7.4.0.GA</version>\n 25 <relativePath>../pom.xml</relativePath>\n 26 </parent>\n 27 <artifactId>ejb-remote-client</artifactId>\n 28 <packaging>jar</packaging>\n 29 <name>Quickstart: ejb-remote - client</name>\n 30 <description>This project demonstrates how to access an EJB from a remote client; this is the client POM file</description>\n 31 \n 32 <properties>\n 33 <http>false</http>\n 34 </properties>\n 35 \n 36 <dependencies>\n 37 <!-- The EJB Client BOM provides application server-compatible dependency management,\n 38 used for building, testing or debugging EJB client applications. Import the BOM to the\n 39 dependency management section of the app's pom.xml file and then set dependencies on specific artifacts.\n 40 Alternatively, as shown in the following example, set a single dependency on the BOM for the app to depend\n 41 on all the artifacts it manages.\n 42 -->\n 43 <dependency>\n 44 <groupId>org.jboss.eap</groupId>\n 45 <artifactId>wildfly-ejb-client-bom</artifactId>\n 46 <type>pom</type>\n 47 <scope>compile</scope>\n 48 </dependency>\n 49 \n 50 <!-- We depend on the EJB remote business interfaces of this application -->\n 51 <dependency>\n 52 <groupId>${project.groupId}</groupId>\n 53 <artifactId>ejb-remote-server-side</artifactId>\n 54 <version>${project.version}</version>\n 55 <type>ejb-client</type>\n 56 </dependency>\n 57 \n 58 </dependencies>\n 59 \n 60 <build>\n 61 <plugins>\n 62 \n 63 <!-- Add the maven exec plug-in to allow us to run a java program\n 64 via maven -->\n 65 <plugin>\n 66 <groupId>org.codehaus.mojo</groupId>\n 67 <artifactId>exec-maven-plugin</artifactId>\n 68 <configuration>\n 69 <executable>java</executable>\n 70 <workingDirectory>${project.build.directory}/exec-working-directory</workingDirectory>\n 71 <arguments>\n 72 <argument>-Dhttp=${http}</argument>\n 73 <argument>-classpath</argument>\n 74 <classpath />\n 75 <argument>org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient</argument>\n 76 </arguments>\n 77 <!--<detail>true</detail>-->\n 78 </configuration>\n 79 </plugin>\n 80 <!-- build standalone exe jar -->\n 81 <plugin>\n 82 <groupId>org.apache.maven.plugins</groupId>\n 83 <artifactId>maven-assembly-plugin</artifactId>\n 84 <configuration>\n 85 <descriptorRefs>\n 86 <descriptorRef>jar-with-dependencies</descriptorRef>\n 87 </descriptorRefs>\n 88 <archive>\n 89 <manifest>\n 90 <mainClass>org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient</mainClass>\n 91 </manifest>\n 92 <manifestEntries>\n 93 <Multi-Release>true</Multi-Release>\n 94 </manifestEntries>\n 95 </archive>\n 96 </configuration>\n 97 </plugin>\n 98 </plugins>\n 99 \n100 </build>\n101 \n102 </project>\n"
lineNumber: 19
variables:
data: project
innerText: "\n 4.0.0\n\n \n org.jboss.eap.quickstarts\n ejb-remote\n 7.4.0.GA\n ../pom.xml\n \n ejb-remote-client\n jar\n Quickstart: ejb-remote - client\n This project demonstrates how to access an EJB from a remote client; this is the client POM file\n\n \n false\n \n\n \n \n \n org.jboss.eap\n wildfly-ejb-client-bom\n pom\n compile\n \n\n \n \n ${project.groupId}\n ejb-remote-server-side\n ${project.version}\n ejb-client\n \n\n \n\n \n \n\n \n \n org.codehaus.mojo\n exec-maven-plugin\n \n java\n ${project.build.directory}/exec-working-directory\n \n -Dhttp=${http}\n -classpath\n \n org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient\n \n \n \n \n \n \n org.apache.maven.plugins\n maven-assembly-plugin\n \n \n jar-with-dependencies\n \n \n \n org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient\n \n \n true\n \n \n \n \n \n\n \n\n"
matchingXML: |-
<modelVersion>4.0.0</modelVersion><parent><groupId>org.jboss.eap.quickstarts</groupId><artifactId>ejb-remote</artifactId><version>7.4.0.GA</version><relativePath>../pom.xml</relativePath></parent><artifactId>ejb-remote-client</artifactId><packaging>jar</packaging><name>Quickstart: ejb-remote - client</name><description>This project demonstrates how to access an EJB from a remote client; this is the client POM file</description><properties><http>false</http></properties><dependencies><!-- The EJB Client BOM provides application server-compatible dependency management,
used for building, testing or debugging EJB client applications. Import the BOM to the
dependency management section of the app's pom.xml file and then set dependencies on specific artifacts.
Alternatively, as shown in the following example, set a single dependency on the BOM for the app to depend
on all the artifacts it manages.
--><dependency><groupId>org.jboss.eap</groupId><artifactId>wildfly-ejb-client-bom</artifactId><type>pom</type><scope>compile</scope></dependency><!-- We depend on the EJB remote business interfaces of this application --><dependency><groupId>${project.groupId}</groupId><artifactId>ejb-remote-server-side</artifactId><version>${project.version}</version><type>ejb-client</type></dependency></dependencies><build><plugins><!-- Add the maven exec plug-in to allow us to run a java program
via maven --><plugin><groupId>org.codehaus.mojo</groupId><artifactId>exec-maven-plugin</artifactId><configuration><executable>java</executable><workingDirectory>${project.build.directory}/exec-working-directory</workingDirectory><arguments><argument>-Dhttp=${http}</argument><argument>-classpath</argument><classpath></classpath><argument>org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient</argument></arguments><!--<detail>true</detail>--></configuration></plugin><!-- build standalone exe jar --><plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-assembly-plugin</artifactId><configuration><descriptorRefs><descriptorRef>jar-with-dependencies</descriptorRef></descriptorRefs><archive><manifest><mainClass>org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient</mainClass></manifest><manifestEntries><Multi-Release>true</Multi-Release></manifestEntries></archive></configuration></plugin></plugins></build>
- uri: file:///opt/input/source/pom.xml
message: "Use the Quarkus Maven plugin adding the following sections to the `pom.xml` file: \n\n ```xml\n <properties> \n <quarkus.platform.group-id>io.quarkus.platform</quarkus.platform.group-id> \n <quarkus.platform.version>3.1.0.Final</quarkus.platform.version>\n </properties> \n <build>\n <plugins>\n <plugin>\n <groupId>$</groupId>\n <artifactId>quarkus-maven-plugin</artifactId>\n <version>$</version>\n <extensions>true</extensions>\n <executions>\n <execution>\n <goals>\n <goal>build</goal>\n <goal>generate-code</goal>\n <goal>generate-code-tests</goal>\n </goals>\n </execution>\n </executions>\n </plugin>\n </plugins>\n </build>\n ```"
codeSnip: " 1 <?xml version=\"1.0\" encoding=\"UTF-8\"?>\n 2 <!--\n 3 JBoss, Home of Professional Open Source\n 4 Copyright 2015, Red Hat, Inc. and/or its affiliates, and individual\n 5 contributors by the @authors tag. See the copyright.txt in the\n 6 distribution for a full listing of individual contributors.\n 7 \n 8 Licensed under the Apache License, Version 2.0 (the \"License\");\n 9 you may not use this file except in compliance with the License.\n 10 You may obtain a copy of the License at\n 11 http://www.apache.org/licenses/LICENSE-2.0\n 12 Unless required by applicable law or agreed to in writing, software\n 13 distributed under the License is distributed on an \"AS IS\" BASIS,\n 14 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n 15 See the License for the specific language governing permissions and\n 16 limitations under the License.\n 17 -->\n 18 <project xmlns=\"http://maven.apache.org/POM/4.0.0\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd\">\n 19 <modelVersion>4.0.0</modelVersion>\n 20 <parent>\n 21 <groupId>org.jboss.eap.quickstarts</groupId>\n 22 <artifactId>quickstart-parent</artifactId>\n 23 <!--\n 24 Maintain separation between the artifact id and the version to help prevent\n 25 merge conflicts between commits changing the GA and those changing the V.\n 26 -->\n 27 <version>7.4.0.GA</version>\n 28 <relativePath>../pom.xml</relativePath>\n 29 </parent>\n 30 <artifactId>ejb-remote</artifactId>\n 31 <packaging>pom</packaging>\n 32 <name>Quickstart: ejb-remote</name>\n 33 <description>This project demonstrates how to access an EJB from a remote client</description>\n 34 \n 35 <licenses>\n 36 <license>\n 37 <name>Apache License, Version 2.0</name>\n 38 <url>http://www.apache.org/licenses/LICENSE-2.0.html</url>\n 39 <distribution>repo</distribution>\n 40 </license>\n 41 </licenses>\n 42 \n 43 <!-- This quickstart consists of a server side component and a client that accesses\n 44 the server side component. Each component has its own self contain pom. However,\n 45 you can add these modules here to keep things modular.\n 46 -->\n 47 <modules>\n 48 <module>server-side</module>\n 49 <module>client</module>\n 50 </modules>\n 51 \n 52 <build>\n 53 <plugins>\n 54 <plugin>\n 55 <groupId>org.wildfly.plugins</groupId>\n 56 <artifactId>wildfly-maven-plugin</artifactId>\n 57 <configuration>\n 58 <skip>true</skip>\n 59 </configuration>\n 60 </plugin>\n 61 </plugins>\n 62 </build>\n 63 </project>\n"
lineNumber: 19
variables:
data: project
innerText: "\n 4.0.0\n \n org.jboss.eap.quickstarts\n quickstart-parent\n \n 7.4.0.GA\n ../pom.xml\n \n ejb-remote\n pom\n Quickstart: ejb-remote\n This project demonstrates how to access an EJB from a remote client\n\n \n \n Apache License, Version 2.0\n http://www.apache.org/licenses/LICENSE-2.0.html\n repo\n \n \n\n \n \n server-side\n client\n \n\n \n \n \n org.wildfly.plugins\n wildfly-maven-plugin\n \n true\n \n \n \n \n"
matchingXML: |-
<modelVersion>4.0.0</modelVersion><parent><groupId>org.jboss.eap.quickstarts</groupId><artifactId>quickstart-parent</artifactId><!--
Maintain separation between the artifact id and the version to help prevent
merge conflicts between commits changing the GA and those changing the V.
--><version>7.4.0.GA</version><relativePath>../pom.xml</relativePath></parent><artifactId>ejb-remote</artifactId><packaging>pom</packaging><name>Quickstart: ejb-remote</name><description>This project demonstrates how to access an EJB from a remote client</description><licenses><license><name>Apache License, Version 2.0</name><url>http://www.apache.org/licenses/LICENSE-2.0.html</url><distribution>repo</distribution></license></licenses><!-- This quickstart consists of a server side component and a client that accesses
the server side component. Each component has its own self contain pom. However,
you can add these modules here to keep things modular.
--><modules><module>server-side</module><module>client</module></modules><build><plugins><plugin><groupId>org.wildfly.plugins</groupId><artifactId>wildfly-maven-plugin</artifactId><configuration><skip>true</skip></configuration></plugin></plugins></build>
- uri: file:///opt/input/source/server-side/pom.xml
message: "Use the Quarkus Maven plugin adding the following sections to the `pom.xml` file: \n\n ```xml\n <properties> \n <quarkus.platform.group-id>io.quarkus.platform</quarkus.platform.group-id> \n <quarkus.platform.version>3.1.0.Final</quarkus.platform.version>\n </properties> \n <build>\n <plugins>\n <plugin>\n <groupId>$</groupId>\n <artifactId>quarkus-maven-plugin</artifactId>\n <version>$</version>\n <extensions>true</extensions>\n <executions>\n <execution>\n <goals>\n <goal>build</goal>\n <goal>generate-code</goal>\n <goal>generate-code-tests</goal>\n </goals>\n </execution>\n </executions>\n </plugin>\n </plugins>\n </build>\n ```"
codeSnip: " 1 <?xml version=\"1.0\" encoding=\"UTF-8\"?>\n 2 <!--\n 3 JBoss, Home of Professional Open Source\n 4 Copyright 2015, Red Hat, Inc. and/or its affiliates, and individual\n 5 contributors by the @authors tag. See the copyright.txt in the\n 6 distribution for a full listing of individual contributors.\n 7 \n 8 Licensed under the Apache License, Version 2.0 (the \"License\");\n 9 you may not use this file except in compliance with the License.\n 10 You may obtain a copy of the License at\n 11 http://www.apache.org/licenses/LICENSE-2.0\n 12 Unless required by applicable law or agreed to in writing, software\n 13 distributed under the License is distributed on an \"AS IS\" BASIS,\n 14 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n 15 See the License for the specific language governing permissions and\n 16 limitations under the License.\n 17 -->\n 18 <project xmlns=\"http://maven.apache.org/POM/4.0.0\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd\">\n 19 <modelVersion>4.0.0</modelVersion>\n 20 <parent>\n 21 <groupId>org.jboss.eap.quickstarts</groupId>\n 22 <artifactId>ejb-remote</artifactId>\n 23 <version>7.4.0.GA</version>\n 24 <relativePath>../pom.xml</relativePath>\n 25 </parent>\n 26 <artifactId>ejb-remote-server-side</artifactId>\n 27 <packaging>ejb</packaging>\n 28 <name>Quickstart: ejb-remote - server-side</name>\n 29 <description>This project demonstrates how to access an EJB from a remote client; this is the server side POM file</description>\n 30 \n 31 <licenses>\n 32 <license>\n 33 <name>Apache License, Version 2.0</name>\n 34 <url>http://www.apache.org/licenses/LICENSE-2.0.html</url>\n 35 <distribution>repo</distribution>\n 36 </license>\n 37 </licenses>\n 38 \n 39 <dependencies>\n 40 \n 41 <!-- Import the Common Annotations API (JSR-250), we use provided scope\n 42 as the API is included in JBoss EAP -->\n 43 <dependency>\n 44 <groupId>org.jboss.spec.javax.annotation</groupId>\n 45 <artifactId>jboss-annotations-api_1.3_spec</artifactId>\n 46 <scope>provided</scope>\n 47 </dependency>\n 48 \n 49 <!-- Import the EJB API, we use provided scope as the API is included in JBoss EAP -->\n 50 <dependency>\n 51 <groupId>org.jboss.spec.javax.ejb</groupId>\n 52 <artifactId>jboss-ejb-api_3.2_spec</artifactId>\n 53 <scope>provided</scope>\n 54 </dependency>\n 55 \n 56 </dependencies>\n 57 \n 58 <build>\n 59 <plugins>\n 60 <!-- WildFly plug-in to deploy the application -->\n 61 <plugin>\n 62 <groupId>org.wildfly.plugins</groupId>\n 63 <artifactId>wildfly-maven-plugin</artifactId>\n 64 <configuration>\n 65 <skip>false</skip>\n 66 <filename>${project.build.finalName}.jar</filename>\n 67 </configuration>\n 68 </plugin>\n 69 <plugin>\n 70 <groupId>org.apache.maven.plugins</groupId>\n 71 <artifactId>maven-ejb-plugin</artifactId>\n 72 <configuration>\n 73 <ejbVersion>3.2</ejbVersion>\n 74 <!-- this is false by default -->\n 75 <generateClient>true</generateClient>\n 76 </configuration>\n 77 </plugin>\n 78 \n 79 </plugins>\n 80 </build>\n 81 \n 82 </project>\n"
lineNumber: 19
variables:
data: project
innerText: "\n 4.0.0\n \n org.jboss.eap.quickstarts\n ejb-remote\n 7.4.0.GA\n ../pom.xml\n \n ejb-remote-server-side\n ejb\n Quickstart: ejb-remote - server-side\n This project demonstrates how to access an EJB from a remote client; this is the server side POM file\n\n \n \n Apache License, Version 2.0\n http://www.apache.org/licenses/LICENSE-2.0.html\n repo\n \n \n\n \n\n \n \n org.jboss.spec.javax.annotation\n jboss-annotations-api_1.3_spec\n provided\n \n\n \n \n org.jboss.spec.javax.ejb\n jboss-ejb-api_3.2_spec\n provided\n \n\n \n\n \n \n \n \n org.wildfly.plugins\n wildfly-maven-plugin\n \n false\n ${project.build.finalName}.jar\n \n \n \n org.apache.maven.plugins\n maven-ejb-plugin\n \n 3.2\n \n true\n \n \n\n \n \n\n"
matchingXML: |-
<modelVersion>4.0.0</modelVersion><parent><groupId>org.jboss.eap.quickstarts</groupId><artifactId>ejb-remote</artifactId><version>7.4.0.GA</version><relativePath>../pom.xml</relativePath></parent><artifactId>ejb-remote-server-side</artifactId><packaging>ejb</packaging><name>Quickstart: ejb-remote - server-side</name><description>This project demonstrates how to access an EJB from a remote client; this is the server side POM file</description><licenses><license><name>Apache License, Version 2.0</name><url>http://www.apache.org/licenses/LICENSE-2.0.html</url><distribution>repo</distribution></license></licenses><dependencies><!-- Import the Common Annotations API (JSR-250), we use provided scope
as the API is included in JBoss EAP --><dependency><groupId>org.jboss.spec.javax.annotation</groupId><artifactId>jboss-annotations-api_1.3_spec</artifactId><scope>provided</scope></dependency><!-- Import the EJB API, we use provided scope as the API is included in JBoss EAP --><dependency><groupId>org.jboss.spec.javax.ejb</groupId><artifactId>jboss-ejb-api_3.2_spec</artifactId><scope>provided</scope></dependency></dependencies><build><plugins><!-- WildFly plug-in to deploy the application --><plugin><groupId>org.wildfly.plugins</groupId><artifactId>wildfly-maven-plugin</artifactId><configuration><skip>false</skip><filename>${project.build.finalName}.jar</filename></configuration></plugin><plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-ejb-plugin</artifactId><configuration><ejbVersion>3.2</ejbVersion><!-- this is false by default --><generateClient>true</generateClient></configuration></plugin></plugins></build>
links:
- url: https://quarkus.io/guides/maven-tooling#build-tool-maven;
title: Quarkus - Guide;
effort: 1
javaee-pom-to-quarkus-00030:
description: Adopt Maven Compiler plugin
category: mandatory
labels:
- konveyor.io/source=java-ee
- konveyor.io/target=quarkus
incidents:
- uri: file:///opt/input/source/client/pom.xml
message: "Use the Maven Compiler plugin adding the following sections to the `pom.xml` file: \n\n ```xml\n <properties> \n <compiler-plugin.version>3.10.1</compiler-plugin.version>\n <maven.compiler.release>11</maven.compiler.release>\n </properties> \n <build>\n <plugins>\n <plugin>\n <artifactId>maven-compiler-plugin</artifactId>\n <version>$</version>\n <configuration>\n <compilerArgs>\n <arg>-parameters</arg>\n </compilerArgs>\n </configuration>\n </plugin>\n </plugins>\n </build>\n ```"
codeSnip: " 1 <?xml version=\"1.0\" encoding=\"UTF-8\"?>\n 2 <!--\n 3 JBoss, Home of Professional Open Source\n 4 Copyright 2015, Red Hat, Inc. and/or its affiliates, and individual\n 5 contributors by the @authors tag. See the copyright.txt in the\n 6 distribution for a full listing of individual contributors.\n 7 \n 8 Licensed under the Apache License, Version 2.0 (the \"License\");\n 9 you may not use this file except in compliance with the License.\n 10 You may obtain a copy of the License at\n 11 http://www.apache.org/licenses/LICENSE-2.0\n 12 Unless required by applicable law or agreed to in writing, software\n 13 distributed under the License is distributed on an \"AS IS\" BASIS,\n 14 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n 15 See the License for the specific language governing permissions and\n 16 limitations under the License.\n 17 -->\n 18 <project xmlns=\"http://maven.apache.org/POM/4.0.0\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd\">\n 19 <modelVersion>4.0.0</modelVersion>\n 20 \n 21 <parent>\n 22 <groupId>org.jboss.eap.quickstarts</groupId>\n 23 <artifactId>ejb-remote</artifactId>\n 24 <version>7.4.0.GA</version>\n 25 <relativePath>../pom.xml</relativePath>\n 26 </parent>\n 27 <artifactId>ejb-remote-client</artifactId>\n 28 <packaging>jar</packaging>\n 29 <name>Quickstart: ejb-remote - client</name>\n 30 <description>This project demonstrates how to access an EJB from a remote client; this is the client POM file</description>\n 31 \n 32 <properties>\n 33 <http>false</http>\n 34 </properties>\n 35 \n 36 <dependencies>\n 37 <!-- The EJB Client BOM provides application server-compatible dependency management,\n 38 used for building, testing or debugging EJB client applications. Import the BOM to the\n 39 dependency management section of the app's pom.xml file and then set dependencies on specific artifacts.\n 40 Alternatively, as shown in the following example, set a single dependency on the BOM for the app to depend\n 41 on all the artifacts it manages.\n 42 -->\n 43 <dependency>\n 44 <groupId>org.jboss.eap</groupId>\n 45 <artifactId>wildfly-ejb-client-bom</artifactId>\n 46 <type>pom</type>\n 47 <scope>compile</scope>\n 48 </dependency>\n 49 \n 50 <!-- We depend on the EJB remote business interfaces of this application -->\n 51 <dependency>\n 52 <groupId>${project.groupId}</groupId>\n 53 <artifactId>ejb-remote-server-side</artifactId>\n 54 <version>${project.version}</version>\n 55 <type>ejb-client</type>\n 56 </dependency>\n 57 \n 58 </dependencies>\n 59 \n 60 <build>\n 61 <plugins>\n 62 \n 63 <!-- Add the maven exec plug-in to allow us to run a java program\n 64 via maven -->\n 65 <plugin>\n 66 <groupId>org.codehaus.mojo</groupId>\n 67 <artifactId>exec-maven-plugin</artifactId>\n 68 <configuration>\n 69 <executable>java</executable>\n 70 <workingDirectory>${project.build.directory}/exec-working-directory</workingDirectory>\n 71 <arguments>\n 72 <argument>-Dhttp=${http}</argument>\n 73 <argument>-classpath</argument>\n 74 <classpath />\n 75 <argument>org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient</argument>\n 76 </arguments>\n 77 <!--<detail>true</detail>-->\n 78 </configuration>\n 79 </plugin>\n 80 <!-- build standalone exe jar -->\n 81 <plugin>\n 82 <groupId>org.apache.maven.plugins</groupId>\n 83 <artifactId>maven-assembly-plugin</artifactId>\n 84 <configuration>\n 85 <descriptorRefs>\n 86 <descriptorRef>jar-with-dependencies</descriptorRef>\n 87 </descriptorRefs>\n 88 <archive>\n 89 <manifest>\n 90 <mainClass>org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient</mainClass>\n 91 </manifest>\n 92 <manifestEntries>\n 93 <Multi-Release>true</Multi-Release>\n 94 </manifestEntries>\n 95 </archive>\n 96 </configuration>\n 97 </plugin>\n 98 </plugins>\n 99 \n100 </build>\n101 \n102 </project>\n"
lineNumber: 19
variables:
data: project
innerText: "\n 4.0.0\n\n \n org.jboss.eap.quickstarts\n ejb-remote\n 7.4.0.GA\n ../pom.xml\n \n ejb-remote-client\n jar\n Quickstart: ejb-remote - client\n This project demonstrates how to access an EJB from a remote client; this is the client POM file\n\n \n false\n \n\n \n \n \n org.jboss.eap\n wildfly-ejb-client-bom\n pom\n compile\n \n\n \n \n ${project.groupId}\n ejb-remote-server-side\n ${project.version}\n ejb-client\n \n\n \n\n \n \n\n \n \n org.codehaus.mojo\n exec-maven-plugin\n \n java\n ${project.build.directory}/exec-working-directory\n \n -Dhttp=${http}\n -classpath\n \n org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient\n \n \n \n \n \n \n org.apache.maven.plugins\n maven-assembly-plugin\n \n \n jar-with-dependencies\n \n \n \n org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient\n \n \n true\n \n \n \n \n \n\n \n\n"
matchingXML: |-
<modelVersion>4.0.0</modelVersion><parent><groupId>org.jboss.eap.quickstarts</groupId><artifactId>ejb-remote</artifactId><version>7.4.0.GA</version><relativePath>../pom.xml</relativePath></parent><artifactId>ejb-remote-client</artifactId><packaging>jar</packaging><name>Quickstart: ejb-remote - client</name><description>This project demonstrates how to access an EJB from a remote client; this is the client POM file</description><properties><http>false</http></properties><dependencies><!-- The EJB Client BOM provides application server-compatible dependency management,
used for building, testing or debugging EJB client applications. Import the BOM to the
dependency management section of the app's pom.xml file and then set dependencies on specific artifacts.
Alternatively, as shown in the following example, set a single dependency on the BOM for the app to depend
on all the artifacts it manages.
--><dependency><groupId>org.jboss.eap</groupId><artifactId>wildfly-ejb-client-bom</artifactId><type>pom</type><scope>compile</scope></dependency><!-- We depend on the EJB remote business interfaces of this application --><dependency><groupId>${project.groupId}</groupId><artifactId>ejb-remote-server-side</artifactId><version>${project.version}</version><type>ejb-client</type></dependency></dependencies><build><plugins><!-- Add the maven exec plug-in to allow us to run a java program
via maven --><plugin><groupId>org.codehaus.mojo</groupId><artifactId>exec-maven-plugin</artifactId><configuration><executable>java</executable><workingDirectory>${project.build.directory}/exec-working-directory</workingDirectory><arguments><argument>-Dhttp=${http}</argument><argument>-classpath</argument><classpath></classpath><argument>org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient</argument></arguments><!--<detail>true</detail>--></configuration></plugin><!-- build standalone exe jar --><plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-assembly-plugin</artifactId><configuration><descriptorRefs><descriptorRef>jar-with-dependencies</descriptorRef></descriptorRefs><archive><manifest><mainClass>org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient</mainClass></manifest><manifestEntries><Multi-Release>true</Multi-Release></manifestEntries></archive></configuration></plugin></plugins></build>
- uri: file:///opt/input/source/pom.xml
message: "Use the Maven Compiler plugin adding the following sections to the `pom.xml` file: \n\n ```xml\n <properties> \n <compiler-plugin.version>3.10.1</compiler-plugin.version>\n <maven.compiler.release>11</maven.compiler.release>\n </properties> \n <build>\n <plugins>\n <plugin>\n <artifactId>maven-compiler-plugin</artifactId>\n <version>$</version>\n <configuration>\n <compilerArgs>\n <arg>-parameters</arg>\n </compilerArgs>\n </configuration>\n </plugin>\n </plugins>\n </build>\n ```"
codeSnip: " 1 <?xml version=\"1.0\" encoding=\"UTF-8\"?>\n 2 <!--\n 3 JBoss, Home of Professional Open Source\n 4 Copyright 2015, Red Hat, Inc. and/or its affiliates, and individual\n 5 contributors by the @authors tag. See the copyright.txt in the\n 6 distribution for a full listing of individual contributors.\n 7 \n 8 Licensed under the Apache License, Version 2.0 (the \"License\");\n 9 you may not use this file except in compliance with the License.\n 10 You may obtain a copy of the License at\n 11 http://www.apache.org/licenses/LICENSE-2.0\n 12 Unless required by applicable law or agreed to in writing, software\n 13 distributed under the License is distributed on an \"AS IS\" BASIS,\n 14 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n 15 See the License for the specific language governing permissions and\n 16 limitations under the License.\n 17 -->\n 18 <project xmlns=\"http://maven.apache.org/POM/4.0.0\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd\">\n 19 <modelVersion>4.0.0</modelVersion>\n 20 <parent>\n 21 <groupId>org.jboss.eap.quickstarts</groupId>\n 22 <artifactId>quickstart-parent</artifactId>\n 23 <!--\n 24 Maintain separation between the artifact id and the version to help prevent\n 25 merge conflicts between commits changing the GA and those changing the V.\n 26 -->\n 27 <version>7.4.0.GA</version>\n 28 <relativePath>../pom.xml</relativePath>\n 29 </parent>\n 30 <artifactId>ejb-remote</artifactId>\n 31 <packaging>pom</packaging>\n 32 <name>Quickstart: ejb-remote</name>\n 33 <description>This project demonstrates how to access an EJB from a remote client</description>\n 34 \n 35 <licenses>\n 36 <license>\n 37 <name>Apache License, Version 2.0</name>\n 38 <url>http://www.apache.org/licenses/LICENSE-2.0.html</url>\n 39 <distribution>repo</distribution>\n 40 </license>\n 41 </licenses>\n 42 \n 43 <!-- This quickstart consists of a server side component and a client that accesses\n 44 the server side component. Each component has its own self contain pom. However,\n 45 you can add these modules here to keep things modular.\n 46 -->\n 47 <modules>\n 48 <module>server-side</module>\n 49 <module>client</module>\n 50 </modules>\n 51 \n 52 <build>\n 53 <plugins>\n 54 <plugin>\n 55 <groupId>org.wildfly.plugins</groupId>\n 56 <artifactId>wildfly-maven-plugin</artifactId>\n 57 <configuration>\n 58 <skip>true</skip>\n 59 </configuration>\n 60 </plugin>\n 61 </plugins>\n 62 </build>\n 63 </project>\n"
lineNumber: 19
variables:
data: project
innerText: "\n 4.0.0\n \n org.jboss.eap.quickstarts\n quickstart-parent\n \n 7.4.0.GA\n ../pom.xml\n \n ejb-remote\n pom\n Quickstart: ejb-remote\n This project demonstrates how to access an EJB from a remote client\n\n \n \n Apache License, Version 2.0\n http://www.apache.org/licenses/LICENSE-2.0.html\n repo\n \n \n\n \n \n server-side\n client\n \n\n \n \n \n org.wildfly.plugins\n wildfly-maven-plugin\n \n true\n \n \n \n \n"
matchingXML: |-
<modelVersion>4.0.0</modelVersion><parent><groupId>org.jboss.eap.quickstarts</groupId><artifactId>quickstart-parent</artifactId><!--
Maintain separation between the artifact id and the version to help prevent
merge conflicts between commits changing the GA and those changing the V.
--><version>7.4.0.GA</version><relativePath>../pom.xml</relativePath></parent><artifactId>ejb-remote</artifactId><packaging>pom</packaging><name>Quickstart: ejb-remote</name><description>This project demonstrates how to access an EJB from a remote client</description><licenses><license><name>Apache License, Version 2.0</name><url>http://www.apache.org/licenses/LICENSE-2.0.html</url><distribution>repo</distribution></license></licenses><!-- This quickstart consists of a server side component and a client that accesses
the server side component. Each component has its own self contain pom. However,
you can add these modules here to keep things modular.
--><modules><module>server-side</module><module>client</module></modules><build><plugins><plugin><groupId>org.wildfly.plugins</groupId><artifactId>wildfly-maven-plugin</artifactId><configuration><skip>true</skip></configuration></plugin></plugins></build>
- uri: file:///opt/input/source/server-side/pom.xml
message: "Use the Maven Compiler plugin adding the following sections to the `pom.xml` file: \n\n ```xml\n <properties> \n <compiler-plugin.version>3.10.1</compiler-plugin.version>\n <maven.compiler.release>11</maven.compiler.release>\n </properties> \n <build>\n <plugins>\n <plugin>\n <artifactId>maven-compiler-plugin</artifactId>\n <version>$</version>\n <configuration>\n <compilerArgs>\n <arg>-parameters</arg>\n </compilerArgs>\n </configuration>\n </plugin>\n </plugins>\n </build>\n ```"
codeSnip: " 1 <?xml version=\"1.0\" encoding=\"UTF-8\"?>\n 2 <!--\n 3 JBoss, Home of Professional Open Source\n 4 Copyright 2015, Red Hat, Inc. and/or its affiliates, and individual\n 5 contributors by the @authors tag. See the copyright.txt in the\n 6 distribution for a full listing of individual contributors.\n 7 \n 8 Licensed under the Apache License, Version 2.0 (the \"License\");\n 9 you may not use this file except in compliance with the License.\n 10 You may obtain a copy of the License at\n 11 http://www.apache.org/licenses/LICENSE-2.0\n 12 Unless required by applicable law or agreed to in writing, software\n 13 distributed under the License is distributed on an \"AS IS\" BASIS,\n 14 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n 15 See the License for the specific language governing permissions and\n 16 limitations under the License.\n 17 -->\n 18 <project xmlns=\"http://maven.apache.org/POM/4.0.0\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd\">\n 19 <modelVersion>4.0.0</modelVersion>\n 20 <parent>\n 21 <groupId>org.jboss.eap.quickstarts</groupId>\n 22 <artifactId>ejb-remote</artifactId>\n 23 <version>7.4.0.GA</version>\n 24 <relativePath>../pom.xml</relativePath>\n 25 </parent>\n 26 <artifactId>ejb-remote-server-side</artifactId>\n 27 <packaging>ejb</packaging>\n 28 <name>Quickstart: ejb-remote - server-side</name>\n 29 <description>This project demonstrates how to access an EJB from a remote client; this is the server side POM file</description>\n 30 \n 31 <licenses>\n 32 <license>\n 33 <name>Apache License, Version 2.0</name>\n 34 <url>http://www.apache.org/licenses/LICENSE-2.0.html</url>\n 35 <distribution>repo</distribution>\n 36 </license>\n 37 </licenses>\n 38 \n 39 <dependencies>\n 40 \n 41 <!-- Import the Common Annotations API (JSR-250), we use provided scope\n 42 as the API is included in JBoss EAP -->\n 43 <dependency>\n 44 <groupId>org.jboss.spec.javax.annotation</groupId>\n 45 <artifactId>jboss-annotations-api_1.3_spec</artifactId>\n 46 <scope>provided</scope>\n 47 </dependency>\n 48 \n 49 <!-- Import the EJB API, we use provided scope as the API is included in JBoss EAP -->\n 50 <dependency>\n 51 <groupId>org.jboss.spec.javax.ejb</groupId>\n 52 <artifactId>jboss-ejb-api_3.2_spec</artifactId>\n 53 <scope>provided</scope>\n 54 </dependency>\n 55 \n 56 </dependencies>\n 57 \n 58 <build>\n 59 <plugins>\n 60 <!-- WildFly plug-in to deploy the application -->\n 61 <plugin>\n 62 <groupId>org.wildfly.plugins</groupId>\n 63 <artifactId>wildfly-maven-plugin</artifactId>\n 64 <configuration>\n 65 <skip>false</skip>\n 66 <filename>${project.build.finalName}.jar</filename>\n 67 </configuration>\n 68 </plugin>\n 69 <plugin>\n 70 <groupId>org.apache.maven.plugins</groupId>\n 71 <artifactId>maven-ejb-plugin</artifactId>\n 72 <configuration>\n 73 <ejbVersion>3.2</ejbVersion>\n 74 <!-- this is false by default -->\n 75 <generateClient>true</generateClient>\n 76 </configuration>\n 77 </plugin>\n 78 \n 79 </plugins>\n 80 </build>\n 81 \n 82 </project>\n"
lineNumber: 19
variables:
data: project
innerText: "\n 4.0.0\n \n org.jboss.eap.quickstarts\n ejb-remote\n 7.4.0.GA\n ../pom.xml\n \n ejb-remote-server-side\n ejb\n Quickstart: ejb-remote - server-side\n This project demonstrates how to access an EJB from a remote client; this is the server side POM file\n\n \n \n Apache License, Version 2.0\n http://www.apache.org/licenses/LICENSE-2.0.html\n repo\n \n \n\n \n\n \n \n org.jboss.spec.javax.annotation\n jboss-annotations-api_1.3_spec\n provided\n \n\n \n \n org.jboss.spec.javax.ejb\n jboss-ejb-api_3.2_spec\n provided\n \n\n \n\n \n \n \n \n org.wildfly.plugins\n wildfly-maven-plugin\n \n false\n ${project.build.finalName}.jar\n \n \n \n org.apache.maven.plugins\n maven-ejb-plugin\n \n 3.2\n \n true\n \n \n\n \n \n\n"
matchingXML: |-
<modelVersion>4.0.0</modelVersion><parent><groupId>org.jboss.eap.quickstarts</groupId><artifactId>ejb-remote</artifactId><version>7.4.0.GA</version><relativePath>../pom.xml</relativePath></parent><artifactId>ejb-remote-server-side</artifactId><packaging>ejb</packaging><name>Quickstart: ejb-remote - server-side</name><description>This project demonstrates how to access an EJB from a remote client; this is the server side POM file</description><licenses><license><name>Apache License, Version 2.0</name><url>http://www.apache.org/licenses/LICENSE-2.0.html</url><distribution>repo</distribution></license></licenses><dependencies><!-- Import the Common Annotations API (JSR-250), we use provided scope
as the API is included in JBoss EAP --><dependency><groupId>org.jboss.spec.javax.annotation</groupId><artifactId>jboss-annotations-api_1.3_spec</artifactId><scope>provided</scope></dependency><!-- Import the EJB API, we use provided scope as the API is included in JBoss EAP --><dependency><groupId>org.jboss.spec.javax.ejb</groupId><artifactId>jboss-ejb-api_3.2_spec</artifactId><scope>provided</scope></dependency></dependencies><build><plugins><!-- WildFly plug-in to deploy the application --><plugin><groupId>org.wildfly.plugins</groupId><artifactId>wildfly-maven-plugin</artifactId><configuration><skip>false</skip><filename>${project.build.finalName}.jar</filename></configuration></plugin><plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-ejb-plugin</artifactId><configuration><ejbVersion>3.2</ejbVersion><!-- this is false by default --><generateClient>true</generateClient></configuration></plugin></plugins></build>
links:
- url: https://quarkus.io/guides/maven-tooling#build-tool-maven;
title: Quarkus - Guide;
effort: 1
javaee-pom-to-quarkus-00040:
description: Adopt Maven Surefire plugin
category: mandatory
labels:
- konveyor.io/source=java-ee
- konveyor.io/target=quarkus
incidents:
- uri: file:///opt/input/source/client/pom.xml
message: "Use the Maven Surefire plugin adding the following sections to the `pom.xml` file: \n\n ```xml\n <properties> \n <surefire-plugin.version>3.0.0</compiler-plugin.version>\n </properties> \n <build>\n <plugins>\n <plugin>\n <artifactId>maven-surefire-plugin</artifactId>\n <version>$</version>\n <configuration>\n <systemPropertyVariables>\n <java.util.logging.manager>org.jboss.logmanager.LogManager</java.util.logging.manager>\n <maven.home>$</maven.home>\n </systemPropertyVariables>\n </configuration>\n </plugin>\n </plugins>\n </build>\n ```"
codeSnip: " 1 <?xml version=\"1.0\" encoding=\"UTF-8\"?>\n 2 <!--\n 3 JBoss, Home of Professional Open Source\n 4 Copyright 2015, Red Hat, Inc. and/or its affiliates, and individual\n 5 contributors by the @authors tag. See the copyright.txt in the\n 6 distribution for a full listing of individual contributors.\n 7 \n 8 Licensed under the Apache License, Version 2.0 (the \"License\");\n 9 you may not use this file except in compliance with the License.\n 10 You may obtain a copy of the License at\n 11 http://www.apache.org/licenses/LICENSE-2.0\n 12 Unless required by applicable law or agreed to in writing, software\n 13 distributed under the License is distributed on an \"AS IS\" BASIS,\n 14 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n 15 See the License for the specific language governing permissions and\n 16 limitations under the License.\n 17 -->\n 18 <project xmlns=\"http://maven.apache.org/POM/4.0.0\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd\">\n 19 <modelVersion>4.0.0</modelVersion>\n 20 \n 21 <parent>\n 22 <groupId>org.jboss.eap.quickstarts</groupId>\n 23 <artifactId>ejb-remote</artifactId>\n 24 <version>7.4.0.GA</version>\n 25 <relativePath>../pom.xml</relativePath>\n 26 </parent>\n 27 <artifactId>ejb-remote-client</artifactId>\n 28 <packaging>jar</packaging>\n 29 <name>Quickstart: ejb-remote - client</name>\n 30 <description>This project demonstrates how to access an EJB from a remote client; this is the client POM file</description>\n 31 \n 32 <properties>\n 33 <http>false</http>\n 34 </properties>\n 35 \n 36 <dependencies>\n 37 <!-- The EJB Client BOM provides application server-compatible dependency management,\n 38 used for building, testing or debugging EJB client applications. Import the BOM to the\n 39 dependency management section of the app's pom.xml file and then set dependencies on specific artifacts.\n 40 Alternatively, as shown in the following example, set a single dependency on the BOM for the app to depend\n 41 on all the artifacts it manages.\n 42 -->\n 43 <dependency>\n 44 <groupId>org.jboss.eap</groupId>\n 45 <artifactId>wildfly-ejb-client-bom</artifactId>\n 46 <type>pom</type>\n 47 <scope>compile</scope>\n 48 </dependency>\n 49 \n 50 <!-- We depend on the EJB remote business interfaces of this application -->\n 51 <dependency>\n 52 <groupId>${project.groupId}</groupId>\n 53 <artifactId>ejb-remote-server-side</artifactId>\n 54 <version>${project.version}</version>\n 55 <type>ejb-client</type>\n 56 </dependency>\n 57 \n 58 </dependencies>\n 59 \n 60 <build>\n 61 <plugins>\n 62 \n 63 <!-- Add the maven exec plug-in to allow us to run a java program\n 64 via maven -->\n 65 <plugin>\n 66 <groupId>org.codehaus.mojo</groupId>\n 67 <artifactId>exec-maven-plugin</artifactId>\n 68 <configuration>\n 69 <executable>java</executable>\n 70 <workingDirectory>${project.build.directory}/exec-working-directory</workingDirectory>\n 71 <arguments>\n 72 <argument>-Dhttp=${http}</argument>\n 73 <argument>-classpath</argument>\n 74 <classpath />\n 75 <argument>org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient</argument>\n 76 </arguments>\n 77 <!--<detail>true</detail>-->\n 78 </configuration>\n 79 </plugin>\n 80 <!-- build standalone exe jar -->\n 81 <plugin>\n 82 <groupId>org.apache.maven.plugins</groupId>\n 83 <artifactId>maven-assembly-plugin</artifactId>\n 84 <configuration>\n 85 <descriptorRefs>\n 86 <descriptorRef>jar-with-dependencies</descriptorRef>\n 87 </descriptorRefs>\n 88 <archive>\n 89 <manifest>\n 90 <mainClass>org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient</mainClass>\n 91 </manifest>\n 92 <manifestEntries>\n 93 <Multi-Release>true</Multi-Release>\n 94 </manifestEntries>\n 95 </archive>\n 96 </configuration>\n 97 </plugin>\n 98 </plugins>\n 99 \n100 </build>\n101 \n102 </project>\n"
lineNumber: 19
variables:
data: project
innerText: "\n 4.0.0\n\n \n org.jboss.eap.quickstarts\n ejb-remote\n 7.4.0.GA\n ../pom.xml\n \n ejb-remote-client\n jar\n Quickstart: ejb-remote - client\n This project demonstrates how to access an EJB from a remote client; this is the client POM file\n\n \n false\n \n\n \n \n \n org.jboss.eap\n wildfly-ejb-client-bom\n pom\n compile\n \n\n \n \n ${project.groupId}\n ejb-remote-server-side\n ${project.version}\n ejb-client\n \n\n \n\n \n \n\n \n \n org.codehaus.mojo\n exec-maven-plugin\n \n java\n ${project.build.directory}/exec-working-directory\n \n -Dhttp=${http}\n -classpath\n \n org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient\n \n \n \n \n \n \n org.apache.maven.plugins\n maven-assembly-plugin\n \n \n jar-with-dependencies\n \n \n \n org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient\n \n \n true\n \n \n \n \n \n\n \n\n"
matchingXML: |-
<modelVersion>4.0.0</modelVersion><parent><groupId>org.jboss.eap.quickstarts</groupId><artifactId>ejb-remote</artifactId><version>7.4.0.GA</version><relativePath>../pom.xml</relativePath></parent><artifactId>ejb-remote-client</artifactId><packaging>jar</packaging><name>Quickstart: ejb-remote - client</name><description>This project demonstrates how to access an EJB from a remote client; this is the client POM file</description><properties><http>false</http></properties><dependencies><!-- The EJB Client BOM provides application server-compatible dependency management,
used for building, testing or debugging EJB client applications. Import the BOM to the
dependency management section of the app's pom.xml file and then set dependencies on specific artifacts.
Alternatively, as shown in the following example, set a single dependency on the BOM for the app to depend
on all the artifacts it manages.
--><dependency><groupId>org.jboss.eap</groupId><artifactId>wildfly-ejb-client-bom</artifactId><type>pom</type><scope>compile</scope></dependency><!-- We depend on the EJB remote business interfaces of this application --><dependency><groupId>${project.groupId}</groupId><artifactId>ejb-remote-server-side</artifactId><version>${project.version}</version><type>ejb-client</type></dependency></dependencies><build><plugins><!-- Add the maven exec plug-in to allow us to run a java program
via maven --><plugin><groupId>org.codehaus.mojo</groupId><artifactId>exec-maven-plugin</artifactId><configuration><executable>java</executable><workingDirectory>${project.build.directory}/exec-working-directory</workingDirectory><arguments><argument>-Dhttp=${http}</argument><argument>-classpath</argument><classpath></classpath><argument>org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient</argument></arguments><!--<detail>true</detail>--></configuration></plugin><!-- build standalone exe jar --><plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-assembly-plugin</artifactId><configuration><descriptorRefs><descriptorRef>jar-with-dependencies</descriptorRef></descriptorRefs><archive><manifest><mainClass>org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient</mainClass></manifest><manifestEntries><Multi-Release>true</Multi-Release></manifestEntries></archive></configuration></plugin></plugins></build>
- uri: file:///opt/input/source/pom.xml
message: "Use the Maven Surefire plugin adding the following sections to the `pom.xml` file: \n\n ```xml\n <properties> \n <surefire-plugin.version>3.0.0</compiler-plugin.version>\n </properties> \n <build>\n <plugins>\n <plugin>\n <artifactId>maven-surefire-plugin</artifactId>\n <version>$</version>\n <configuration>\n <systemPropertyVariables>\n <java.util.logging.manager>org.jboss.logmanager.LogManager</java.util.logging.manager>\n <maven.home>$</maven.home>\n </systemPropertyVariables>\n </configuration>\n </plugin>\n </plugins>\n </build>\n ```"
codeSnip: " 1 <?xml version=\"1.0\" encoding=\"UTF-8\"?>\n 2 <!--\n 3 JBoss, Home of Professional Open Source\n 4 Copyright 2015, Red Hat, Inc. and/or its affiliates, and individual\n 5 contributors by the @authors tag. See the copyright.txt in the\n 6 distribution for a full listing of individual contributors.\n 7 \n 8 Licensed under the Apache License, Version 2.0 (the \"License\");\n 9 you may not use this file except in compliance with the License.\n 10 You may obtain a copy of the License at\n 11 http://www.apache.org/licenses/LICENSE-2.0\n 12 Unless required by applicable law or agreed to in writing, software\n 13 distributed under the License is distributed on an \"AS IS\" BASIS,\n 14 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n 15 See the License for the specific language governing permissions and\n 16 limitations under the License.\n 17 -->\n 18 <project xmlns=\"http://maven.apache.org/POM/4.0.0\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd\">\n 19 <modelVersion>4.0.0</modelVersion>\n 20 <parent>\n 21 <groupId>org.jboss.eap.quickstarts</groupId>\n 22 <artifactId>quickstart-parent</artifactId>\n 23 <!--\n 24 Maintain separation between the artifact id and the version to help prevent\n 25 merge conflicts between commits changing the GA and those changing the V.\n 26 -->\n 27 <version>7.4.0.GA</version>\n 28 <relativePath>../pom.xml</relativePath>\n 29 </parent>\n 30 <artifactId>ejb-remote</artifactId>\n 31 <packaging>pom</packaging>\n 32 <name>Quickstart: ejb-remote</name>\n 33 <description>This project demonstrates how to access an EJB from a remote client</description>\n 34 \n 35 <licenses>\n 36 <license>\n 37 <name>Apache License, Version 2.0</name>\n 38 <url>http://www.apache.org/licenses/LICENSE-2.0.html</url>\n 39 <distribution>repo</distribution>\n 40 </license>\n 41 </licenses>\n 42 \n 43 <!-- This quickstart consists of a server side component and a client that accesses\n 44 the server side component. Each component has its own self contain pom. However,\n 45 you can add these modules here to keep things modular.\n 46 -->\n 47 <modules>\n 48 <module>server-side</module>\n 49 <module>client</module>\n 50 </modules>\n 51 \n 52 <build>\n 53 <plugins>\n 54 <plugin>\n 55 <groupId>org.wildfly.plugins</groupId>\n 56 <artifactId>wildfly-maven-plugin</artifactId>\n 57 <configuration>\n 58 <skip>true</skip>\n 59 </configuration>\n 60 </plugin>\n 61 </plugins>\n 62 </build>\n 63 </project>\n"
lineNumber: 19
variables:
data: project
innerText: "\n 4.0.0\n \n org.jboss.eap.quickstarts\n quickstart-parent\n \n 7.4.0.GA\n ../pom.xml\n \n ejb-remote\n pom\n Quickstart: ejb-remote\n This project demonstrates how to access an EJB from a remote client\n\n \n \n Apache License, Version 2.0\n http://www.apache.org/licenses/LICENSE-2.0.html\n repo\n \n \n\n \n \n server-side\n client\n \n\n \n \n \n org.wildfly.plugins\n wildfly-maven-plugin\n \n true\n \n \n \n \n"
matchingXML: |-
<modelVersion>4.0.0</modelVersion><parent><groupId>org.jboss.eap.quickstarts</groupId><artifactId>quickstart-parent</artifactId><!--
Maintain separation between the artifact id and the version to help prevent
merge conflicts between commits changing the GA and those changing the V.
--><version>7.4.0.GA</version><relativePath>../pom.xml</relativePath></parent><artifactId>ejb-remote</artifactId><packaging>pom</packaging><name>Quickstart: ejb-remote</name><description>This project demonstrates how to access an EJB from a remote client</description><licenses><license><name>Apache License, Version 2.0</name><url>http://www.apache.org/licenses/LICENSE-2.0.html</url><distribution>repo</distribution></license></licenses><!-- This quickstart consists of a server side component and a client that accesses
the server side component. Each component has its own self contain pom. However,
you can add these modules here to keep things modular.
--><modules><module>server-side</module><module>client</module></modules><build><plugins><plugin><groupId>org.wildfly.plugins</groupId><artifactId>wildfly-maven-plugin</artifactId><configuration><skip>true</skip></configuration></plugin></plugins></build>
- uri: file:///opt/input/source/server-side/pom.xml
message: "Use the Maven Surefire plugin adding the following sections to the `pom.xml` file: \n\n ```xml\n <properties> \n <surefire-plugin.version>3.0.0</compiler-plugin.version>\n </properties> \n <build>\n <plugins>\n <plugin>\n <artifactId>maven-surefire-plugin</artifactId>\n <version>$</version>\n <configuration>\n <systemPropertyVariables>\n <java.util.logging.manager>org.jboss.logmanager.LogManager</java.util.logging.manager>\n <maven.home>$</maven.home>\n </systemPropertyVariables>\n </configuration>\n </plugin>\n </plugins>\n </build>\n ```"
codeSnip: " 1 <?xml version=\"1.0\" encoding=\"UTF-8\"?>\n 2 <!--\n 3 JBoss, Home of Professional Open Source\n 4 Copyright 2015, Red Hat, Inc. and/or its affiliates, and individual\n 5 contributors by the @authors tag. See the copyright.txt in the\n 6 distribution for a full listing of individual contributors.\n 7 \n 8 Licensed under the Apache License, Version 2.0 (the \"License\");\n 9 you may not use this file except in compliance with the License.\n 10 You may obtain a copy of the License at\n 11 http://www.apache.org/licenses/LICENSE-2.0\n 12 Unless required by applicable law or agreed to in writing, software\n 13 distributed under the License is distributed on an \"AS IS\" BASIS,\n 14 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n 15 See the License for the specific language governing permissions and\n 16 limitations under the License.\n 17 -->\n 18 <project xmlns=\"http://maven.apache.org/POM/4.0.0\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd\">\n 19 <modelVersion>4.0.0</modelVersion>\n 20 <parent>\n 21 <groupId>org.jboss.eap.quickstarts</groupId>\n 22 <artifactId>ejb-remote</artifactId>\n 23 <version>7.4.0.GA</version>\n 24 <relativePath>../pom.xml</relativePath>\n 25 </parent>\n 26 <artifactId>ejb-remote-server-side</artifactId>\n 27 <packaging>ejb</packaging>\n 28 <name>Quickstart: ejb-remote - server-side</name>\n 29 <description>This project demonstrates how to access an EJB from a remote client; this is the server side POM file</description>\n 30 \n 31 <licenses>\n 32 <license>\n 33 <name>Apache License, Version 2.0</name>\n 34 <url>http://www.apache.org/licenses/LICENSE-2.0.html</url>\n 35 <distribution>repo</distribution>\n 36 </license>\n 37 </licenses>\n 38 \n 39 <dependencies>\n 40 \n 41 <!-- Import the Common Annotations API (JSR-250), we use provided scope\n 42 as the API is included in JBoss EAP -->\n 43 <dependency>\n 44 <groupId>org.jboss.spec.javax.annotation</groupId>\n 45 <artifactId>jboss-annotations-api_1.3_spec</artifactId>\n 46 <scope>provided</scope>\n 47 </dependency>\n 48 \n 49 <!-- Import the EJB API, we use provided scope as the API is included in JBoss EAP -->\n 50 <dependency>\n 51 <groupId>org.jboss.spec.javax.ejb</groupId>\n 52 <artifactId>jboss-ejb-api_3.2_spec</artifactId>\n 53 <scope>provided</scope>\n 54 </dependency>\n 55 \n 56 </dependencies>\n 57 \n 58 <build>\n 59 <plugins>\n 60 <!-- WildFly plug-in to deploy the application -->\n 61 <plugin>\n 62 <groupId>org.wildfly.plugins</groupId>\n 63 <artifactId>wildfly-maven-plugin</artifactId>\n 64 <configuration>\n 65 <skip>false</skip>\n 66 <filename>${project.build.finalName}.jar</filename>\n 67 </configuration>\n 68 </plugin>\n 69 <plugin>\n 70 <groupId>org.apache.maven.plugins</groupId>\n 71 <artifactId>maven-ejb-plugin</artifactId>\n 72 <configuration>\n 73 <ejbVersion>3.2</ejbVersion>\n 74 <!-- this is false by default -->\n 75 <generateClient>true</generateClient>\n 76 </configuration>\n 77 </plugin>\n 78 \n 79 </plugins>\n 80 </build>\n 81 \n 82 </project>\n"
lineNumber: 19
variables:
data: project
innerText: "\n 4.0.0\n \n org.jboss.eap.quickstarts\n ejb-remote\n 7.4.0.GA\n ../pom.xml\n \n ejb-remote-server-side\n ejb\n Quickstart: ejb-remote - server-side\n This project demonstrates how to access an EJB from a remote client; this is the server side POM file\n\n \n \n Apache License, Version 2.0\n http://www.apache.org/licenses/LICENSE-2.0.html\n repo\n \n \n\n \n\n \n \n org.jboss.spec.javax.annotation\n jboss-annotations-api_1.3_spec\n provided\n \n\n \n \n org.jboss.spec.javax.ejb\n jboss-ejb-api_3.2_spec\n provided\n \n\n \n\n \n \n \n \n org.wildfly.plugins\n wildfly-maven-plugin\n \n false\n ${project.build.finalName}.jar\n \n \n \n org.apache.maven.plugins\n maven-ejb-plugin\n \n 3.2\n \n true\n \n \n\n \n \n\n"
matchingXML: |-
<modelVersion>4.0.0</modelVersion><parent><groupId>org.jboss.eap.quickstarts</groupId><artifactId>ejb-remote</artifactId><version>7.4.0.GA</version><relativePath>../pom.xml</relativePath></parent><artifactId>ejb-remote-server-side</artifactId><packaging>ejb</packaging><name>Quickstart: ejb-remote - server-side</name><description>This project demonstrates how to access an EJB from a remote client; this is the server side POM file</description><licenses><license><name>Apache License, Version 2.0</name><url>http://www.apache.org/licenses/LICENSE-2.0.html</url><distribution>repo</distribution></license></licenses><dependencies><!-- Import the Common Annotations API (JSR-250), we use provided scope
as the API is included in JBoss EAP --><dependency><groupId>org.jboss.spec.javax.annotation</groupId><artifactId>jboss-annotations-api_1.3_spec</artifactId><scope>provided</scope></dependency><!-- Import the EJB API, we use provided scope as the API is included in JBoss EAP --><dependency><groupId>org.jboss.spec.javax.ejb</groupId><artifactId>jboss-ejb-api_3.2_spec</artifactId><scope>provided</scope></dependency></dependencies><build><plugins><!-- WildFly plug-in to deploy the application --><plugin><groupId>org.wildfly.plugins</groupId><artifactId>wildfly-maven-plugin</artifactId><configuration><skip>false</skip><filename>${project.build.finalName}.jar</filename></configuration></plugin><plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-ejb-plugin</artifactId><configuration><ejbVersion>3.2</ejbVersion><!-- this is false by default --><generateClient>true</generateClient></configuration></plugin></plugins></build>
links:
- url: https://quarkus.io/guides/maven-tooling#build-tool-maven;
title: Quarkus - Guide;
effort: 1
javaee-pom-to-quarkus-00050:
description: Adopt Maven Failsafe plugin
category: mandatory
labels:
- konveyor.io/source=java-ee
- konveyor.io/target=quarkus
incidents:
- uri: file:///opt/input/source/client/pom.xml
message: "Use the Maven Failsafe plugin adding the following sections to the `pom.xml` file: \n\n ```xml\n <properties> \n <surefire-plugin.version>3.0.0</compiler-plugin.version>\n </properties> \n <build>\n <plugins>\n <plugin>\n <artifactId>maven-failsafe-plugin</artifactId>\n <version>$</version>\n <executions>\n <execution>\n <goals>\n <goals>integration-test</goal>\n <goals>verify</goal>\n </goals>\n <configuration>\n <systemPropertyVariables>\n <native.image.path>$/$-runner</native.image.path>\n <java.util.logging.manager>org.jboss.logmanager.LogManager</java.util.logging.manager>\n <maven.home>$</maven.home>\n </systemPropertyVariables>\n </configuration>\n </execution>\n </executions>\n </plugin>\n </plugins>\n </build>\n ```"
codeSnip: " 1 <?xml version=\"1.0\" encoding=\"UTF-8\"?>\n 2 <!--\n 3 JBoss, Home of Professional Open Source\n 4 Copyright 2015, Red Hat, Inc. and/or its affiliates, and individual\n 5 contributors by the @authors tag. See the copyright.txt in the\n 6 distribution for a full listing of individual contributors.\n 7 \n 8 Licensed under the Apache License, Version 2.0 (the \"License\");\n 9 you may not use this file except in compliance with the License.\n 10 You may obtain a copy of the License at\n 11 http://www.apache.org/licenses/LICENSE-2.0\n 12 Unless required by applicable law or agreed to in writing, software\n 13 distributed under the License is distributed on an \"AS IS\" BASIS,\n 14 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n 15 See the License for the specific language governing permissions and\n 16 limitations under the License.\n 17 -->\n 18 <project xmlns=\"http://maven.apache.org/POM/4.0.0\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd\">\n 19 <modelVersion>4.0.0</modelVersion>\n 20 \n 21 <parent>\n 22 <groupId>org.jboss.eap.quickstarts</groupId>\n 23 <artifactId>ejb-remote</artifactId>\n 24 <version>7.4.0.GA</version>\n 25 <relativePath>../pom.xml</relativePath>\n 26 </parent>\n 27 <artifactId>ejb-remote-client</artifactId>\n 28 <packaging>jar</packaging>\n 29 <name>Quickstart: ejb-remote - client</name>\n 30 <description>This project demonstrates how to access an EJB from a remote client; this is the client POM file</description>\n 31 \n 32 <properties>\n 33 <http>false</http>\n 34 </properties>\n 35 \n 36 <dependencies>\n 37 <!-- The EJB Client BOM provides application server-compatible dependency management,\n 38 used for building, testing or debugging EJB client applications. Import the BOM to the\n 39 dependency management section of the app's pom.xml file and then set dependencies on specific artifacts.\n 40 Alternatively, as shown in the following example, set a single dependency on the BOM for the app to depend\n 41 on all the artifacts it manages.\n 42 -->\n 43 <dependency>\n 44 <groupId>org.jboss.eap</groupId>\n 45 <artifactId>wildfly-ejb-client-bom</artifactId>\n 46 <type>pom</type>\n 47 <scope>compile</scope>\n 48 </dependency>\n 49 \n 50 <!-- We depend on the EJB remote business interfaces of this application -->\n 51 <dependency>\n 52 <groupId>${project.groupId}</groupId>\n 53 <artifactId>ejb-remote-server-side</artifactId>\n 54 <version>${project.version}</version>\n 55 <type>ejb-client</type>\n 56 </dependency>\n 57 \n 58 </dependencies>\n 59 \n 60 <build>\n 61 <plugins>\n 62 \n 63 <!-- Add the maven exec plug-in to allow us to run a java program\n 64 via maven -->\n 65 <plugin>\n 66 <groupId>org.codehaus.mojo</groupId>\n 67 <artifactId>exec-maven-plugin</artifactId>\n 68 <configuration>\n 69 <executable>java</executable>\n 70 <workingDirectory>${project.build.directory}/exec-working-directory</workingDirectory>\n 71 <arguments>\n 72 <argument>-Dhttp=${http}</argument>\n 73 <argument>-classpath</argument>\n 74 <classpath />\n 75 <argument>org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient</argument>\n 76 </arguments>\n 77 <!--<detail>true</detail>-->\n 78 </configuration>\n 79 </plugin>\n 80 <!-- build standalone exe jar -->\n 81 <plugin>\n 82 <groupId>org.apache.maven.plugins</groupId>\n 83 <artifactId>maven-assembly-plugin</artifactId>\n 84 <configuration>\n 85 <descriptorRefs>\n 86 <descriptorRef>jar-with-dependencies</descriptorRef>\n 87 </descriptorRefs>\n 88 <archive>\n 89 <manifest>\n 90 <mainClass>org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient</mainClass>\n 91 </manifest>\n 92 <manifestEntries>\n 93 <Multi-Release>true</Multi-Release>\n 94 </manifestEntries>\n 95 </archive>\n 96 </configuration>\n 97 </plugin>\n 98 </plugins>\n 99 \n100 </build>\n101 \n102 </project>\n"
lineNumber: 19
variables:
data: project
innerText: "\n 4.0.0\n\n \n org.jboss.eap.quickstarts\n ejb-remote\n 7.4.0.GA\n ../pom.xml\n \n ejb-remote-client\n jar\n Quickstart: ejb-remote - client\n This project demonstrates how to access an EJB from a remote client; this is the client POM file\n\n \n false\n \n\n \n \n \n org.jboss.eap\n wildfly-ejb-client-bom\n pom\n compile\n \n\n \n \n ${project.groupId}\n ejb-remote-server-side\n ${project.version}\n ejb-client\n \n\n \n\n \n \n\n \n \n org.codehaus.mojo\n exec-maven-plugin\n \n java\n ${project.build.directory}/exec-working-directory\n \n -Dhttp=${http}\n -classpath\n \n org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient\n \n \n \n \n \n \n org.apache.maven.plugins\n maven-assembly-plugin\n \n \n jar-with-dependencies\n \n \n \n org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient\n \n \n true\n \n \n \n \n \n\n \n\n"
matchingXML: |-
<modelVersion>4.0.0</modelVersion><parent><groupId>org.jboss.eap.quickstarts</groupId><artifactId>ejb-remote</artifactId><version>7.4.0.GA</version><relativePath>../pom.xml</relativePath></parent><artifactId>ejb-remote-client</artifactId><packaging>jar</packaging><name>Quickstart: ejb-remote - client</name><description>This project demonstrates how to access an EJB from a remote client; this is the client POM file</description><properties><http>false</http></properties><dependencies><!-- The EJB Client BOM provides application server-compatible dependency management,
used for building, testing or debugging EJB client applications. Import the BOM to the
dependency management section of the app's pom.xml file and then set dependencies on specific artifacts.
Alternatively, as shown in the following example, set a single dependency on the BOM for the app to depend
on all the artifacts it manages.
--><dependency><groupId>org.jboss.eap</groupId><artifactId>wildfly-ejb-client-bom</artifactId><type>pom</type><scope>compile</scope></dependency><!-- We depend on the EJB remote business interfaces of this application --><dependency><groupId>${project.groupId}</groupId><artifactId>ejb-remote-server-side</artifactId><version>${project.version}</version><type>ejb-client</type></dependency></dependencies><build><plugins><!-- Add the maven exec plug-in to allow us to run a java program
via maven --><plugin><groupId>org.codehaus.mojo</groupId><artifactId>exec-maven-plugin</artifactId><configuration><executable>java</executable><workingDirectory>${project.build.directory}/exec-working-directory</workingDirectory><arguments><argument>-Dhttp=${http}</argument><argument>-classpath</argument><classpath></classpath><argument>org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient</argument></arguments><!--<detail>true</detail>--></configuration></plugin><!-- build standalone exe jar --><plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-assembly-plugin</artifactId><configuration><descriptorRefs><descriptorRef>jar-with-dependencies</descriptorRef></descriptorRefs><archive><manifest><mainClass>org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient</mainClass></manifest><manifestEntries><Multi-Release>true</Multi-Release></manifestEntries></archive></configuration></plugin></plugins></build>
- uri: file:///opt/input/source/pom.xml
message: "Use the Maven Failsafe plugin adding the following sections to the `pom.xml` file: \n\n ```xml\n <properties> \n <surefire-plugin.version>3.0.0</compiler-plugin.version>\n </properties> \n <build>\n <plugins>\n <plugin>\n <artifactId>maven-failsafe-plugin</artifactId>\n <version>$</version>\n <executions>\n <execution>\n <goals>\n <goals>integration-test</goal>\n <goals>verify</goal>\n </goals>\n <configuration>\n <systemPropertyVariables>\n <native.image.path>$/$-runner</native.image.path>\n <java.util.logging.manager>org.jboss.logmanager.LogManager</java.util.logging.manager>\n <maven.home>$</maven.home>\n </systemPropertyVariables>\n </configuration>\n </execution>\n </executions>\n </plugin>\n </plugins>\n </build>\n ```"
codeSnip: " 1 <?xml version=\"1.0\" encoding=\"UTF-8\"?>\n 2 <!--\n 3 JBoss, Home of Professional Open Source\n 4 Copyright 2015, Red Hat, Inc. and/or its affiliates, and individual\n 5 contributors by the @authors tag. See the copyright.txt in the\n 6 distribution for a full listing of individual contributors.\n 7 \n 8 Licensed under the Apache License, Version 2.0 (the \"License\");\n 9 you may not use this file except in compliance with the License.\n 10 You may obtain a copy of the License at\n 11 http://www.apache.org/licenses/LICENSE-2.0\n 12 Unless required by applicable law or agreed to in writing, software\n 13 distributed under the License is distributed on an \"AS IS\" BASIS,\n 14 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n 15 See the License for the specific language governing permissions and\n 16 limitations under the License.\n 17 -->\n 18 <project xmlns=\"http://maven.apache.org/POM/4.0.0\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd\">\n 19 <modelVersion>4.0.0</modelVersion>\n 20 <parent>\n 21 <groupId>org.jboss.eap.quickstarts</groupId>\n 22 <artifactId>quickstart-parent</artifactId>\n 23 <!--\n 24 Maintain separation between the artifact id and the version to help prevent\n 25 merge conflicts between commits changing the GA and those changing the V.\n 26 -->\n 27 <version>7.4.0.GA</version>\n 28 <relativePath>../pom.xml</relativePath>\n 29 </parent>\n 30 <artifactId>ejb-remote</artifactId>\n 31 <packaging>pom</packaging>\n 32 <name>Quickstart: ejb-remote</name>\n 33 <description>This project demonstrates how to access an EJB from a remote client</description>\n 34 \n 35 <licenses>\n 36 <license>\n 37 <name>Apache License, Version 2.0</name>\n 38 <url>http://www.apache.org/licenses/LICENSE-2.0.html</url>\n 39 <distribution>repo</distribution>\n 40 </license>\n 41 </licenses>\n 42 \n 43 <!-- This quickstart consists of a server side component and a client that accesses\n 44 the server side component. Each component has its own self contain pom. However,\n 45 you can add these modules here to keep things modular.\n 46 -->\n 47 <modules>\n 48 <module>server-side</module>\n 49 <module>client</module>\n 50 </modules>\n 51 \n 52 <build>\n 53 <plugins>\n 54 <plugin>\n 55 <groupId>org.wildfly.plugins</groupId>\n 56 <artifactId>wildfly-maven-plugin</artifactId>\n 57 <configuration>\n 58 <skip>true</skip>\n 59 </configuration>\n 60 </plugin>\n 61 </plugins>\n 62 </build>\n 63 </project>\n"
lineNumber: 19
variables:
data: project
innerText: "\n 4.0.0\n \n org.jboss.eap.quickstarts\n quickstart-parent\n \n 7.4.0.GA\n ../pom.xml\n \n ejb-remote\n pom\n Quickstart: ejb-remote\n This project demonstrates how to access an EJB from a remote client\n\n \n \n Apache License, Version 2.0\n http://www.apache.org/licenses/LICENSE-2.0.html\n repo\n \n \n\n \n \n server-side\n client\n \n\n \n \n \n org.wildfly.plugins\n wildfly-maven-plugin\n \n true\n \n \n \n \n"
matchingXML: |-
<modelVersion>4.0.0</modelVersion><parent><groupId>org.jboss.eap.quickstarts</groupId><artifactId>quickstart-parent</artifactId><!--
Maintain separation between the artifact id and the version to help prevent
merge conflicts between commits changing the GA and those changing the V.
--><version>7.4.0.GA</version><relativePath>../pom.xml</relativePath></parent><artifactId>ejb-remote</artifactId><packaging>pom</packaging><name>Quickstart: ejb-remote</name><description>This project demonstrates how to access an EJB from a remote client</description><licenses><license><name>Apache License, Version 2.0</name><url>http://www.apache.org/licenses/LICENSE-2.0.html</url><distribution>repo</distribution></license></licenses><!-- This quickstart consists of a server side component and a client that accesses
the server side component. Each component has its own self contain pom. However,
you can add these modules here to keep things modular.
--><modules><module>server-side</module><module>client</module></modules><build><plugins><plugin><groupId>org.wildfly.plugins</groupId><artifactId>wildfly-maven-plugin</artifactId><configuration><skip>true</skip></configuration></plugin></plugins></build>
- uri: file:///opt/input/source/server-side/pom.xml
message: "Use the Maven Failsafe plugin adding the following sections to the `pom.xml` file: \n\n ```xml\n <properties> \n <surefire-plugin.version>3.0.0</compiler-plugin.version>\n </properties> \n <build>\n <plugins>\n <plugin>\n <artifactId>maven-failsafe-plugin</artifactId>\n <version>$</version>\n <executions>\n <execution>\n <goals>\n <goals>integration-test</goal>\n <goals>verify</goal>\n </goals>\n <configuration>\n <systemPropertyVariables>\n <native.image.path>$/$-runner</native.image.path>\n <java.util.logging.manager>org.jboss.logmanager.LogManager</java.util.logging.manager>\n <maven.home>$</maven.home>\n </systemPropertyVariables>\n </configuration>\n </execution>\n </executions>\n </plugin>\n </plugins>\n </build>\n ```"
codeSnip: " 1 <?xml version=\"1.0\" encoding=\"UTF-8\"?>\n 2 <!--\n 3 JBoss, Home of Professional Open Source\n 4 Copyright 2015, Red Hat, Inc. and/or its affiliates, and individual\n 5 contributors by the @authors tag. See the copyright.txt in the\n 6 distribution for a full listing of individual contributors.\n 7 \n 8 Licensed under the Apache License, Version 2.0 (the \"License\");\n 9 you may not use this file except in compliance with the License.\n 10 You may obtain a copy of the License at\n 11 http://www.apache.org/licenses/LICENSE-2.0\n 12 Unless required by applicable law or agreed to in writing, software\n 13 distributed under the License is distributed on an \"AS IS\" BASIS,\n 14 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n 15 See the License for the specific language governing permissions and\n 16 limitations under the License.\n 17 -->\n 18 <project xmlns=\"http://maven.apache.org/POM/4.0.0\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd\">\n 19 <modelVersion>4.0.0</modelVersion>\n 20 <parent>\n 21 <groupId>org.jboss.eap.quickstarts</groupId>\n 22 <artifactId>ejb-remote</artifactId>\n 23 <version>7.4.0.GA</version>\n 24 <relativePath>../pom.xml</relativePath>\n 25 </parent>\n 26 <artifactId>ejb-remote-server-side</artifactId>\n 27 <packaging>ejb</packaging>\n 28 <name>Quickstart: ejb-remote - server-side</name>\n 29 <description>This project demonstrates how to access an EJB from a remote client; this is the server side POM file</description>\n 30 \n 31 <licenses>\n 32 <license>\n 33 <name>Apache License, Version 2.0</name>\n 34 <url>http://www.apache.org/licenses/LICENSE-2.0.html</url>\n 35 <distribution>repo</distribution>\n 36 </license>\n 37 </licenses>\n 38 \n 39 <dependencies>\n 40 \n 41 <!-- Import the Common Annotations API (JSR-250), we use provided scope\n 42 as the API is included in JBoss EAP -->\n 43 <dependency>\n 44 <groupId>org.jboss.spec.javax.annotation</groupId>\n 45 <artifactId>jboss-annotations-api_1.3_spec</artifactId>\n 46 <scope>provided</scope>\n 47 </dependency>\n 48 \n 49 <!-- Import the EJB API, we use provided scope as the API is included in JBoss EAP -->\n 50 <dependency>\n 51 <groupId>org.jboss.spec.javax.ejb</groupId>\n 52 <artifactId>jboss-ejb-api_3.2_spec</artifactId>\n 53 <scope>provided</scope>\n 54 </dependency>\n 55 \n 56 </dependencies>\n 57 \n 58 <build>\n 59 <plugins>\n 60 <!-- WildFly plug-in to deploy the application -->\n 61 <plugin>\n 62 <groupId>org.wildfly.plugins</groupId>\n 63 <artifactId>wildfly-maven-plugin</artifactId>\n 64 <configuration>\n 65 <skip>false</skip>\n 66 <filename>${project.build.finalName}.jar</filename>\n 67 </configuration>\n 68 </plugin>\n 69 <plugin>\n 70 <groupId>org.apache.maven.plugins</groupId>\n 71 <artifactId>maven-ejb-plugin</artifactId>\n 72 <configuration>\n 73 <ejbVersion>3.2</ejbVersion>\n 74 <!-- this is false by default -->\n 75 <generateClient>true</generateClient>\n 76 </configuration>\n 77 </plugin>\n 78 \n 79 </plugins>\n 80 </build>\n 81 \n 82 </project>\n"
lineNumber: 19
variables:
data: project
innerText: "\n 4.0.0\n \n org.jboss.eap.quickstarts\n ejb-remote\n 7.4.0.GA\n ../pom.xml\n \n ejb-remote-server-side\n ejb\n Quickstart: ejb-remote - server-side\n This project demonstrates how to access an EJB from a remote client; this is the server side POM file\n\n \n \n Apache License, Version 2.0\n http://www.apache.org/licenses/LICENSE-2.0.html\n repo\n \n \n\n \n\n \n \n org.jboss.spec.javax.annotation\n jboss-annotations-api_1.3_spec\n provided\n \n\n \n \n org.jboss.spec.javax.ejb\n jboss-ejb-api_3.2_spec\n provided\n \n\n \n\n \n \n \n \n org.wildfly.plugins\n wildfly-maven-plugin\n \n false\n ${project.build.finalName}.jar\n \n \n \n org.apache.maven.plugins\n maven-ejb-plugin\n \n 3.2\n \n true\n \n \n\n \n \n\n"
matchingXML: |-
<modelVersion>4.0.0</modelVersion><parent><groupId>org.jboss.eap.quickstarts</groupId><artifactId>ejb-remote</artifactId><version>7.4.0.GA</version><relativePath>../pom.xml</relativePath></parent><artifactId>ejb-remote-server-side</artifactId><packaging>ejb</packaging><name>Quickstart: ejb-remote - server-side</name><description>This project demonstrates how to access an EJB from a remote client; this is the server side POM file</description><licenses><license><name>Apache License, Version 2.0</name><url>http://www.apache.org/licenses/LICENSE-2.0.html</url><distribution>repo</distribution></license></licenses><dependencies><!-- Import the Common Annotations API (JSR-250), we use provided scope
as the API is included in JBoss EAP --><dependency><groupId>org.jboss.spec.javax.annotation</groupId><artifactId>jboss-annotations-api_1.3_spec</artifactId><scope>provided</scope></dependency><!-- Import the EJB API, we use provided scope as the API is included in JBoss EAP --><dependency><groupId>org.jboss.spec.javax.ejb</groupId><artifactId>jboss-ejb-api_3.2_spec</artifactId><scope>provided</scope></dependency></dependencies><build><plugins><!-- WildFly plug-in to deploy the application --><plugin><groupId>org.wildfly.plugins</groupId><artifactId>wildfly-maven-plugin</artifactId><configuration><skip>false</skip><filename>${project.build.finalName}.jar</filename></configuration></plugin><plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-ejb-plugin</artifactId><configuration><ejbVersion>3.2</ejbVersion><!-- this is false by default --><generateClient>true</generateClient></configuration></plugin></plugins></build>
links:
- url: https://quarkus.io/guides/maven-tooling#build-tool-maven;
title: Quarkus - Guide;
effort: 1
javaee-pom-to-quarkus-00060:
description: Add Maven profile to run the Quarkus native build
category: mandatory
labels:
- konveyor.io/source=java-ee
- konveyor.io/target=quarkus
incidents:
- uri: file:///opt/input/source/client/pom.xml
message: "Leverage a Maven profile to run the Quarkus native build adding the following section to the `pom.xml` file: \n\n ```xml\n <profiles>\n <profile>\n <id>native</id>\n <activation>\n <property>\n <name>native</name>\n </property>\n </activation>\n <properties>\n <skipITs>false</skipITs>\n <quarkus.package.type>native</quarkus.package.type>\n </properties>\n </profile>\n </profiles>\n ```"
codeSnip: " 1 <?xml version=\"1.0\" encoding=\"UTF-8\"?>\n 2 <!--\n 3 JBoss, Home of Professional Open Source\n 4 Copyright 2015, Red Hat, Inc. and/or its affiliates, and individual\n 5 contributors by the @authors tag. See the copyright.txt in the\n 6 distribution for a full listing of individual contributors.\n 7 \n 8 Licensed under the Apache License, Version 2.0 (the \"License\");\n 9 you may not use this file except in compliance with the License.\n 10 You may obtain a copy of the License at\n 11 http://www.apache.org/licenses/LICENSE-2.0\n 12 Unless required by applicable law or agreed to in writing, software\n 13 distributed under the License is distributed on an \"AS IS\" BASIS,\n 14 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n 15 See the License for the specific language governing permissions and\n 16 limitations under the License.\n 17 -->\n 18 <project xmlns=\"http://maven.apache.org/POM/4.0.0\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd\">\n 19 <modelVersion>4.0.0</modelVersion>\n 20 \n 21 <parent>\n 22 <groupId>org.jboss.eap.quickstarts</groupId>\n 23 <artifactId>ejb-remote</artifactId>\n 24 <version>7.4.0.GA</version>\n 25 <relativePath>../pom.xml</relativePath>\n 26 </parent>\n 27 <artifactId>ejb-remote-client</artifactId>\n 28 <packaging>jar</packaging>\n 29 <name>Quickstart: ejb-remote - client</name>\n 30 <description>This project demonstrates how to access an EJB from a remote client; this is the client POM file</description>\n 31 \n 32 <properties>\n 33 <http>false</http>\n 34 </properties>\n 35 \n 36 <dependencies>\n 37 <!-- The EJB Client BOM provides application server-compatible dependency management,\n 38 used for building, testing or debugging EJB client applications. Import the BOM to the\n 39 dependency management section of the app's pom.xml file and then set dependencies on specific artifacts.\n 40 Alternatively, as shown in the following example, set a single dependency on the BOM for the app to depend\n 41 on all the artifacts it manages.\n 42 -->\n 43 <dependency>\n 44 <groupId>org.jboss.eap</groupId>\n 45 <artifactId>wildfly-ejb-client-bom</artifactId>\n 46 <type>pom</type>\n 47 <scope>compile</scope>\n 48 </dependency>\n 49 \n 50 <!-- We depend on the EJB remote business interfaces of this application -->\n 51 <dependency>\n 52 <groupId>${project.groupId}</groupId>\n 53 <artifactId>ejb-remote-server-side</artifactId>\n 54 <version>${project.version}</version>\n 55 <type>ejb-client</type>\n 56 </dependency>\n 57 \n 58 </dependencies>\n 59 \n 60 <build>\n 61 <plugins>\n 62 \n 63 <!-- Add the maven exec plug-in to allow us to run a java program\n 64 via maven -->\n 65 <plugin>\n 66 <groupId>org.codehaus.mojo</groupId>\n 67 <artifactId>exec-maven-plugin</artifactId>\n 68 <configuration>\n 69 <executable>java</executable>\n 70 <workingDirectory>${project.build.directory}/exec-working-directory</workingDirectory>\n 71 <arguments>\n 72 <argument>-Dhttp=${http}</argument>\n 73 <argument>-classpath</argument>\n 74 <classpath />\n 75 <argument>org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient</argument>\n 76 </arguments>\n 77 <!--<detail>true</detail>-->\n 78 </configuration>\n 79 </plugin>\n 80 <!-- build standalone exe jar -->\n 81 <plugin>\n 82 <groupId>org.apache.maven.plugins</groupId>\n 83 <artifactId>maven-assembly-plugin</artifactId>\n 84 <configuration>\n 85 <descriptorRefs>\n 86 <descriptorRef>jar-with-dependencies</descriptorRef>\n 87 </descriptorRefs>\n 88 <archive>\n 89 <manifest>\n 90 <mainClass>org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient</mainClass>\n 91 </manifest>\n 92 <manifestEntries>\n 93 <Multi-Release>true</Multi-Release>\n 94 </manifestEntries>\n 95 </archive>\n 96 </configuration>\n 97 </plugin>\n 98 </plugins>\n 99 \n100 </build>\n101 \n102 </project>\n"
lineNumber: 19
variables:
data: project
innerText: "\n 4.0.0\n\n \n org.jboss.eap.quickstarts\n ejb-remote\n 7.4.0.GA\n ../pom.xml\n \n ejb-remote-client\n jar\n Quickstart: ejb-remote - client\n This project demonstrates how to access an EJB from a remote client; this is the client POM file\n\n \n false\n \n\n \n \n \n org.jboss.eap\n wildfly-ejb-client-bom\n pom\n compile\n \n\n \n \n ${project.groupId}\n ejb-remote-server-side\n ${project.version}\n ejb-client\n \n\n \n\n \n \n\n \n \n org.codehaus.mojo\n exec-maven-plugin\n \n java\n ${project.build.directory}/exec-working-directory\n \n -Dhttp=${http}\n -classpath\n \n org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient\n \n \n \n \n \n \n org.apache.maven.plugins\n maven-assembly-plugin\n \n \n jar-with-dependencies\n \n \n \n org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient\n \n \n true\n \n \n \n \n \n\n \n\n"
matchingXML: |-
<modelVersion>4.0.0</modelVersion><parent><groupId>org.jboss.eap.quickstarts</groupId><artifactId>ejb-remote</artifactId><version>7.4.0.GA</version><relativePath>../pom.xml</relativePath></parent><artifactId>ejb-remote-client</artifactId><packaging>jar</packaging><name>Quickstart: ejb-remote - client</name><description>This project demonstrates how to access an EJB from a remote client; this is the client POM file</description><properties><http>false</http></properties><dependencies><!-- The EJB Client BOM provides application server-compatible dependency management,
used for building, testing or debugging EJB client applications. Import the BOM to the
dependency management section of the app's pom.xml file and then set dependencies on specific artifacts.
Alternatively, as shown in the following example, set a single dependency on the BOM for the app to depend
on all the artifacts it manages.
--><dependency><groupId>org.jboss.eap</groupId><artifactId>wildfly-ejb-client-bom</artifactId><type>pom</type><scope>compile</scope></dependency><!-- We depend on the EJB remote business interfaces of this application --><dependency><groupId>${project.groupId}</groupId><artifactId>ejb-remote-server-side</artifactId><version>${project.version}</version><type>ejb-client</type></dependency></dependencies><build><plugins><!-- Add the maven exec plug-in to allow us to run a java program
via maven --><plugin><groupId>org.codehaus.mojo</groupId><artifactId>exec-maven-plugin</artifactId><configuration><executable>java</executable><workingDirectory>${project.build.directory}/exec-working-directory</workingDirectory><arguments><argument>-Dhttp=${http}</argument><argument>-classpath</argument><classpath></classpath><argument>org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient</argument></arguments><!--<detail>true</detail>--></configuration></plugin><!-- build standalone exe jar --><plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-assembly-plugin</artifactId><configuration><descriptorRefs><descriptorRef>jar-with-dependencies</descriptorRef></descriptorRefs><archive><manifest><mainClass>org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient</mainClass></manifest><manifestEntries><Multi-Release>true</Multi-Release></manifestEntries></archive></configuration></plugin></plugins></build>
- uri: file:///opt/input/source/pom.xml
message: "Leverage a Maven profile to run the Quarkus native build adding the following section to the `pom.xml` file: \n\n ```xml\n <profiles>\n <profile>\n <id>native</id>\n <activation>\n <property>\n <name>native</name>\n </property>\n </activation>\n <properties>\n <skipITs>false</skipITs>\n <quarkus.package.type>native</quarkus.package.type>\n </properties>\n </profile>\n </profiles>\n ```"
codeSnip: " 1 <?xml version=\"1.0\" encoding=\"UTF-8\"?>\n 2 <!--\n 3 JBoss, Home of Professional Open Source\n 4 Copyright 2015, Red Hat, Inc. and/or its affiliates, and individual\n 5 contributors by the @authors tag. See the copyright.txt in the\n 6 distribution for a full listing of individual contributors.\n 7 \n 8 Licensed under the Apache License, Version 2.0 (the \"License\");\n 9 you may not use this file except in compliance with the License.\n 10 You may obtain a copy of the License at\n 11 http://www.apache.org/licenses/LICENSE-2.0\n 12 Unless required by applicable law or agreed to in writing, software\n 13 distributed under the License is distributed on an \"AS IS\" BASIS,\n 14 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n 15 See the License for the specific language governing permissions and\n 16 limitations under the License.\n 17 -->\n 18 <project xmlns=\"http://maven.apache.org/POM/4.0.0\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd\">\n 19 <modelVersion>4.0.0</modelVersion>\n 20 <parent>\n 21 <groupId>org.jboss.eap.quickstarts</groupId>\n 22 <artifactId>quickstart-parent</artifactId>\n 23 <!--\n 24 Maintain separation between the artifact id and the version to help prevent\n 25 merge conflicts between commits changing the GA and those changing the V.\n 26 -->\n 27 <version>7.4.0.GA</version>\n 28 <relativePath>../pom.xml</relativePath>\n 29 </parent>\n 30 <artifactId>ejb-remote</artifactId>\n 31 <packaging>pom</packaging>\n 32 <name>Quickstart: ejb-remote</name>\n 33 <description>This project demonstrates how to access an EJB from a remote client</description>\n 34 \n 35 <licenses>\n 36 <license>\n 37 <name>Apache License, Version 2.0</name>\n 38 <url>http://www.apache.org/licenses/LICENSE-2.0.html</url>\n 39 <distribution>repo</distribution>\n 40 </license>\n 41 </licenses>\n 42 \n 43 <!-- This quickstart consists of a server side component and a client that accesses\n 44 the server side component. Each component has its own self contain pom. However,\n 45 you can add these modules here to keep things modular.\n 46 -->\n 47 <modules>\n 48 <module>server-side</module>\n 49 <module>client</module>\n 50 </modules>\n 51 \n 52 <build>\n 53 <plugins>\n 54 <plugin>\n 55 <groupId>org.wildfly.plugins</groupId>\n 56 <artifactId>wildfly-maven-plugin</artifactId>\n 57 <configuration>\n 58 <skip>true</skip>\n 59 </configuration>\n 60 </plugin>\n 61 </plugins>\n 62 </build>\n 63 </project>\n"
lineNumber: 19
variables:
data: project
innerText: "\n 4.0.0\n \n org.jboss.eap.quickstarts\n quickstart-parent\n \n 7.4.0.GA\n ../pom.xml\n \n ejb-remote\n pom\n Quickstart: ejb-remote\n This project demonstrates how to access an EJB from a remote client\n\n \n \n Apache License, Version 2.0\n http://www.apache.org/licenses/LICENSE-2.0.html\n repo\n \n \n\n \n \n server-side\n client\n \n\n \n \n \n org.wildfly.plugins\n wildfly-maven-plugin\n \n true\n \n \n \n \n"
matchingXML: |-
<modelVersion>4.0.0</modelVersion><parent><groupId>org.jboss.eap.quickstarts</groupId><artifactId>quickstart-parent</artifactId><!--
Maintain separation between the artifact id and the version to help prevent
merge conflicts between commits changing the GA and those changing the V.
--><version>7.4.0.GA</version><relativePath>../pom.xml</relativePath></parent><artifactId>ejb-remote</artifactId><packaging>pom</packaging><name>Quickstart: ejb-remote</name><description>This project demonstrates how to access an EJB from a remote client</description><licenses><license><name>Apache License, Version 2.0</name><url>http://www.apache.org/licenses/LICENSE-2.0.html</url><distribution>repo</distribution></license></licenses><!-- This quickstart consists of a server side component and a client that accesses
the server side component. Each component has its own self contain pom. However,
you can add these modules here to keep things modular.
--><modules><module>server-side</module><module>client</module></modules><build><plugins><plugin><groupId>org.wildfly.plugins</groupId><artifactId>wildfly-maven-plugin</artifactId><configuration><skip>true</skip></configuration></plugin></plugins></build>
- uri: file:///opt/input/source/server-side/pom.xml
message: "Leverage a Maven profile to run the Quarkus native build adding the following section to the `pom.xml` file: \n\n ```xml\n <profiles>\n <profile>\n <id>native</id>\n <activation>\n <property>\n <name>native</name>\n </property>\n </activation>\n <properties>\n <skipITs>false</skipITs>\n <quarkus.package.type>native</quarkus.package.type>\n </properties>\n </profile>\n </profiles>\n ```"
codeSnip: " 1 <?xml version=\"1.0\" encoding=\"UTF-8\"?>\n 2 <!--\n 3 JBoss, Home of Professional Open Source\n 4 Copyright 2015, Red Hat, Inc. and/or its affiliates, and individual\n 5 contributors by the @authors tag. See the copyright.txt in the\n 6 distribution for a full listing of individual contributors.\n 7 \n 8 Licensed under the Apache License, Version 2.0 (the \"License\");\n 9 you may not use this file except in compliance with the License.\n 10 You may obtain a copy of the License at\n 11 http://www.apache.org/licenses/LICENSE-2.0\n 12 Unless required by applicable law or agreed to in writing, software\n 13 distributed under the License is distributed on an \"AS IS\" BASIS,\n 14 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n 15 See the License for the specific language governing permissions and\n 16 limitations under the License.\n 17 -->\n 18 <project xmlns=\"http://maven.apache.org/POM/4.0.0\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd\">\n 19 <modelVersion>4.0.0</modelVersion>\n 20 <parent>\n 21 <groupId>org.jboss.eap.quickstarts</groupId>\n 22 <artifactId>ejb-remote</artifactId>\n 23 <version>7.4.0.GA</version>\n 24 <relativePath>../pom.xml</relativePath>\n 25 </parent>\n 26 <artifactId>ejb-remote-server-side</artifactId>\n 27 <packaging>ejb</packaging>\n 28 <name>Quickstart: ejb-remote - server-side</name>\n 29 <description>This project demonstrates how to access an EJB from a remote client; this is the server side POM file</description>\n 30 \n 31 <licenses>\n 32 <license>\n 33 <name>Apache License, Version 2.0</name>\n 34 <url>http://www.apache.org/licenses/LICENSE-2.0.html</url>\n 35 <distribution>repo</distribution>\n 36 </license>\n 37 </licenses>\n 38 \n 39 <dependencies>\n 40 \n 41 <!-- Import the Common Annotations API (JSR-250), we use provided scope\n 42 as the API is included in JBoss EAP -->\n 43 <dependency>\n 44 <groupId>org.jboss.spec.javax.annotation</groupId>\n 45 <artifactId>jboss-annotations-api_1.3_spec</artifactId>\n 46 <scope>provided</scope>\n 47 </dependency>\n 48 \n 49 <!-- Import the EJB API, we use provided scope as the API is included in JBoss EAP -->\n 50 <dependency>\n 51 <groupId>org.jboss.spec.javax.ejb</groupId>\n 52 <artifactId>jboss-ejb-api_3.2_spec</artifactId>\n 53 <scope>provided</scope>\n 54 </dependency>\n 55 \n 56 </dependencies>\n 57 \n 58 <build>\n 59 <plugins>\n 60 <!-- WildFly plug-in to deploy the application -->\n 61 <plugin>\n 62 <groupId>org.wildfly.plugins</groupId>\n 63 <artifactId>wildfly-maven-plugin</artifactId>\n 64 <configuration>\n 65 <skip>false</skip>\n 66 <filename>${project.build.finalName}.jar</filename>\n 67 </configuration>\n 68 </plugin>\n 69 <plugin>\n 70 <groupId>org.apache.maven.plugins</groupId>\n 71 <artifactId>maven-ejb-plugin</artifactId>\n 72 <configuration>\n 73 <ejbVersion>3.2</ejbVersion>\n 74 <!-- this is false by default -->\n 75 <generateClient>true</generateClient>\n 76 </configuration>\n 77 </plugin>\n 78 \n 79 </plugins>\n 80 </build>\n 81 \n 82 </project>\n"
lineNumber: 19
variables:
data: project
innerText: "\n 4.0.0\n \n org.jboss.eap.quickstarts\n ejb-remote\n 7.4.0.GA\n ../pom.xml\n \n ejb-remote-server-side\n ejb\n Quickstart: ejb-remote - server-side\n This project demonstrates how to access an EJB from a remote client; this is the server side POM file\n\n \n \n Apache License, Version 2.0\n http://www.apache.org/licenses/LICENSE-2.0.html\n repo\n \n \n\n \n\n \n \n org.jboss.spec.javax.annotation\n jboss-annotations-api_1.3_spec\n provided\n \n\n \n \n org.jboss.spec.javax.ejb\n jboss-ejb-api_3.2_spec\n provided\n \n\n \n\n \n \n \n \n org.wildfly.plugins\n wildfly-maven-plugin\n \n false\n ${project.build.finalName}.jar\n \n \n \n org.apache.maven.plugins\n maven-ejb-plugin\n \n 3.2\n \n true\n \n \n\n \n \n\n"
matchingXML: |-
<modelVersion>4.0.0</modelVersion><parent><groupId>org.jboss.eap.quickstarts</groupId><artifactId>ejb-remote</artifactId><version>7.4.0.GA</version><relativePath>../pom.xml</relativePath></parent><artifactId>ejb-remote-server-side</artifactId><packaging>ejb</packaging><name>Quickstart: ejb-remote - server-side</name><description>This project demonstrates how to access an EJB from a remote client; this is the server side POM file</description><licenses><license><name>Apache License, Version 2.0</name><url>http://www.apache.org/licenses/LICENSE-2.0.html</url><distribution>repo</distribution></license></licenses><dependencies><!-- Import the Common Annotations API (JSR-250), we use provided scope
as the API is included in JBoss EAP --><dependency><groupId>org.jboss.spec.javax.annotation</groupId><artifactId>jboss-annotations-api_1.3_spec</artifactId><scope>provided</scope></dependency><!-- Import the EJB API, we use provided scope as the API is included in JBoss EAP --><dependency><groupId>org.jboss.spec.javax.ejb</groupId><artifactId>jboss-ejb-api_3.2_spec</artifactId><scope>provided</scope></dependency></dependencies><build><plugins><!-- WildFly plug-in to deploy the application --><plugin><groupId>org.wildfly.plugins</groupId><artifactId>wildfly-maven-plugin</artifactId><configuration><skip>false</skip><filename>${project.build.finalName}.jar</filename></configuration></plugin><plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-ejb-plugin</artifactId><configuration><ejbVersion>3.2</ejbVersion><!-- this is false by default --><generateClient>true</generateClient></configuration></plugin></plugins></build>
links:
- url: https://quarkus.io/guides/maven-tooling#build-tool-maven;
title: Quarkus - Guide;
effort: 1
unmatched:
- cdi-to-quarkus-00000
- cdi-to-quarkus-00020
- cdi-to-quarkus-00030
- cdi-to-quarkus-00040
- cdi-to-quarkus-00050
- dependency-removal-for-quarkus-00000
- jakarta-cdi-to-quarkus-00000
- jakarta-cdi-to-quarkus-00020
- jakarta-cdi-to-quarkus-00030
- jakarta-cdi-to-quarkus-00040
- jakarta-cdi-to-quarkus-00050
- jakarta-faces-to-quarkus-00000
- jakarta-faces-to-quarkus-00010
- jakarta-jaxrs-to-quarkus-00010
- jakarta-jaxrs-to-quarkus-00020
- javaee-faces-to-quarkus-00000
- javaee-pom-to-quarkus-00070
- javaee-pom-to-quarkus-00080
- jaxrs-to-quarkus-00000
- jaxrs-to-quarkus-00010
- jaxrs-to-quarkus-00020
- jms-to-reactive-quarkus-00000
- jms-to-reactive-quarkus-00010
- jms-to-reactive-quarkus-00020
- jms-to-reactive-quarkus-00030
- jms-to-reactive-quarkus-00040
- jms-to-reactive-quarkus-00050
- springboot-actuator-to-quarkus-0100
- springboot-actuator-to-quarkus-0200
- springboot-annotations-to-quarkus-00000
- springboot-cache-to-quarkus-00000
- springboot-cloud-config-client-to-quarkus-00000
- springboot-devtools-to-quarkus-0000
- springboot-di-to-quarkus-00000
- springboot-di-to-quarkus-00001
- springboot-di-to-quarkus-00002
- springboot-generic-catchall-00100
- springboot-integration-to-quarkus-00010
- springboot-integration-to-quarkus-00020
- springboot-jmx-to-quarkus-00000
- springboot-jmx-to-quarkus-00001
- springboot-jpa-to-quarkus-00000
- springboot-metrics-to-quarkus-0100
- springboot-metrics-to-quarkus-0200
- springboot-metrics-to-quarkus-0300
- springboot-parent-pom-to-quarkus-00000
- springboot-plugins-to-quarkus-0000
- springboot-properties-to-quarkus-00000
- springboot-properties-to-quarkus-00001
- springboot-properties-to-quarkus-00002
- springboot-properties-to-quarkus-00003
- springboot-properties-to-quarkus-00004
- springboot-properties-to-quarkus-00005
- springboot-properties-to-quarkus-00006
- springboot-scheduled-to-quarkus-00000
- springboot-security-to-quarkus-00000
- springboot-shell-to-quarkus-00000
- springboot-web-to-quarkus-00000
- springboot-web-to-quarkus-00010
- springboot-webmvc-to-quarkus-00000
- springboot-webmvc-to-quarkus-01000
- name: rhr/springboot
description: Verify the version of the Spring Boot framework is compatible with those supported by Red Hat Runtimes
unmatched:
- springboot-associated-00001
- springboot-associated-00002
- springboot-associated-00003
- springboot-associated-00004
- springboot-associated-00005
- springboot-associated-00006
- springboot-associated-00007
- springboot-associated-00008
- springboot-associated-00009
- springboot-associated-00010
- springboot-associated-00011
- springboot-associated-00012
- springboot-associated-00013
- springboot-associated-00014
- springboot-associated-00015
- springboot-rhr-00001
- springboot-rhr-00002
- name: technology-usage
description: This ruleset provides analysis of logging libraries.
tags:
- Bean=EJB XML
- Connect=EJB XML
- Java EE=EJB XML
unmatched:
- 3rd-party-01000
- 3rd-party-02000
- 3rd-party-03000
- 3rd-party-04000
- 3rd-party-05000
- 3rd-party-06000
- 3rd-party-07000
- 3rd-party-08000
- 3rd-party-09000
- 3rd-party-10000
- 3rd-party-11000
- 3rd-party-12000
- 3rd-party-13000
- 3rd-party-14000
- 3rd-party-15000
- 3rd-party-16000
- 3rd-party-17000
- 3rd-party-18000
- 3rd-party-19000
- 3rd-party-spring-03001
- 3rd-party-spring-03002
- 3rd-party-spring-03002
- apm-00000
- apm-00000
- apm-00001
- apm-00001
- apm-00002
- apm-00002
- apm-00003
- apm-00003
- clustering-00000
- clustering-00001
- configuration-management-0100
- configuration-management-0200
- configuration-management-0300
- configuration-management-0400
- configuration-management-0500
- configuration-management-technology-usage-0100
- configuration-management-technology-usage-0200
- configuration-management-technology-usage-0300
- connect-01400
- connect-01500
- connect-01600
- connect-01700
- connect-01800
- connect-01900
- connect-02000
- connect-02100
- connect-02200
- connect-02300
- connect-02400
- connect-02500
- connect-02600
- connect-02700
- connect-02800
- connect-02900
- database-01400
- database-01400
- database-01400
- database-01500
- database-01600
- database-01700
- database-01800
- database-01805
- database-01900
- database-02000
- database-02100
- database-02200
- database-02300
- database-02400
- database-02500
- database-02600
- database-02700
- database-02800
- database-02900
- database-03000
- database-03100
- database-03100
- ejb-01000
- embedded-cache-libraries-01000
- embedded-cache-libraries-02000
- embedded-cache-libraries-03000
- embedded-cache-libraries-04000
- embedded-cache-libraries-05000
- embedded-cache-libraries-06000
- embedded-cache-libraries-07000
- embedded-cache-libraries-08000
- embedded-cache-libraries-09000
- embedded-cache-libraries-10000
- embedded-cache-libraries-11000
- embedded-cache-libraries-12000
- embedded-cache-libraries-13000
- embedded-cache-libraries-14000
- embedded-cache-libraries-15000
- embedded-cache-libraries-16000
- embedded-framework-01000
- embedded-framework-01010
- embedded-framework-01100
- embedded-framework-01200
- embedded-framework-01300
- embedded-framework-01400
- embedded-framework-01500
- embedded-framework-01600
- embedded-framework-01700
- embedded-framework-02000
- embedded-framework-02200
- embedded-framework-02300
- embedded-framework-02400
- embedded-framework-03000
- embedded-framework-03100
- embedded-framework-03200
- embedded-framework-03300
- embedded-framework-03400
- embedded-framework-04700
- embedded-framework-05000
- embedded-framework-05100
- embedded-framework-05300
- embedded-framework-05400
- embedded-framework-05500
- embedded-framework-05600
- embedded-framework-05700
- embedded-framework-05800
- embedded-framework-05900
- embedded-framework-06000
- embedded-framework-06100
- embedded-framework-06200
- embedded-framework-06300
- embedded-framework-06400
- embedded-framework-06500
- embedded-framework-06600
- embedded-framework-06700
- embedded-framework-06800
- embedded-framework-06900
- embedded-framework-07000
- embedded-framework-07100
- embedded-framework-07200
- embedded-framework-07300
- embedded-framework-07400
- embedded-framework-07500
- embedded-framework-07600
- embedded-framework-07700
- embedded-framework-07800
- embedded-framework-07900
- embedded-framework-08000
- embedded-framework-08100
- embedded-framework-08200
- embedded-framework-08300
- embedded-framework-08400
- embedded-framework-08500
- embedded-framework-08600
- embedded-framework-08700
- embedded-framework-08800
- embedded-framework-08900
- embedded-framework-09000
- embedded-framework-09100
- embedded-framework-09300
- embedded-framework-embedded-framework-02700
- embedded-framework-embedded-framework-02800
- embedded-framework-embedded-framework-02900
- embedded-framework-embedded-framework-03000
- embedded-framework-embedded-framework-03100
- embedded-framework-embedded-framework-03200
- embedded-framework-embedded-framework-03300
- embedded-framework-embedded-framework-03400
- embedded-framework-embedded-framework-03500
- embedded-framework-embedded-framework-03600
- embedded-framework-embedded-framework-03700
- embedded-framework-embedded-framework-03800
- embedded-framework-embedded-framework-03900
- embedded-framework-embedded-framework-04000
- embedded-framework-embedded-framework-04100
- embedded-framework-embedded-framework-04200
- embedded-framework-embedded-framework-04300
- embedded-framework-embedded-framework-04400
- embedded-framework-embedded-framework-04500
- embedded-framework-embedded-framework-04600
- embedded-framework-embedded-framework-09200
- embedded-framework-embedded-framework-09300
- integration-00001
- integration-00002
- integration-00003
- integration-00004
- integration-00005
- integration-00006
- integration-00007
- integration-00008
- integration-00009
- integration-00010
- integration-00011
- integration-00012
- integration-00013
- integration-00014
- integration-00015
- integration-00016
- integration-00017
- javaee-technology-usage-00010
- javaee-technology-usage-00011
- javaee-technology-usage-00012
- javaee-technology-usage-00013
- javaee-technology-usage-00020-jakarta
- javaee-technology-usage-00020-javax
- javaee-technology-usage-00021
- javaee-technology-usage-00030
- javaee-technology-usage-00031
- javaee-technology-usage-00040
- javaee-technology-usage-00050
- javaee-technology-usage-00060
- javaee-technology-usage-00070
- javaee-technology-usage-00080
- javaee-technology-usage-00090
- javaee-technology-usage-00100
- javaee-technology-usage-00110
- javaee-technology-usage-00120
- javaee-technology-usage-00130
- javaee-technology-usage-00140
- javaee-technology-usage-00150
- javaee-technology-usage-00160
- javaee-technology-usage-00170
- javaee-technology-usage-00180
- javaee-technology-usage-00190
- javaee-technology-usage-00200
- javaee-technology-usage-00210
- javaee-technology-usage-00220
- javaee-technology-usage-00230
- javaee-technology-usage-00902
- javaee-technology-usage-00903
- javaee-technology-usage-00905
- javaee-technology-usage-00906
- javaee-technology-usage-00910
- javaee-technology-usage-00911
- javaee-technology-usage-00912
- javaee-technology-usage-00913
- javaee-technology-usage-00914
- javaee-technology-usage-00915
- javaee-technology-usage-00916
- javaee-technology-usage-00917
- javaee-technology-usage-00918
- javaee-technology-usage-00926
- javaee-technology-usage-00927
- javaee-technology-usage-00928
- javaee-technology-usage-00930
- javaee-technology-usage-00931
- javaee-technology-usage-00932
- javaee-technology-usage-00950
- javaee-technology-usage-00951
- javaee-technology-usage-00952
- javaee-technology-usage-00953
- javaee-technology-usage-00954
- javaee-technology-usage-00955
- javaee-technology-usage-00956
- javaee-technology-usage-00957
- javaee-technology-usage-00958
- javase-01000
- javase-01100
- javase-technology-usage-01000
- jta-00020
- jta-00030
- jta-00040
- jta-00050
- jta-00060
- jta-00070
- jta-00080
- jta-00090
- jta-00100
- jta-00110
- jta-00120
- jta-00130
- jta-00140
- jta-00150
- jta-00160
- jta-00170
- jta-00180
- jta-00190
- jta-00200
- jta-00210
- logging-usage-00010
- logging-usage-00020
- logging-usage-00030
- logging-usage-00040
- logging-usage-00050
- logging-usage-00080
- logging-usage-00090
- logging-usage-00100
- logging-usage-00110
- logging-usage-00120
- logging-usage-00130
- logging-usage-00140
- logging-usage-00150
- logging-usage-00160
- logging-usage-00170
- logging-usage-00180
- logging-usage-00190
- logging-usage-00200
- logging-usage-00210
- logging-usage-00220
- logging-usage-00230
- logging-usage-00240
- logging-usage-00250
- logging-usage-00260
- logging-usage-00270
- logging-usage-00280
- logging-usage-00290
- mvc-01000
- mvc-01100
- mvc-01200
- mvc-01210
- mvc-01220
- mvc-01300
- mvc-01400
- mvc-01500
- mvc-01600
- mvc-01700
- mvc-01800
- mvc-01900
- mvc-02000
- mvc-02100
- mvc-02200
- mvc-02300
- mvc-02400
- mvc-02500
- mvc-02600
- mvc-02700
- mvc-02800
- mvc-02900
- mvc-03000
- mvc-03100
- mvc-03200
- mvc-03300
- mvc-03400
- mvc-03500
- mvc-03600
- mvc-03700
- mvc-03800
- mvc-03900
- mvc-04000
- mvc-04100
- mvc-04200
- mvc-04300
- mvc-04400
- mvc-04500
- mvc-04600
- mvc-04700
- mvc-04800
- mvc-04900
- mvc-05000
- mvc-05100
- mvc-05200
- mvc-05300
- mvc-05400
- mvc-05500
- mvc-05600
- mvc-05700
- mvc-05800
- mvc-05900
- mvc-06000
- non-xml-technology-usage-05000
- non-xml-technology-usage-06000
- non-xml-technology-usage-12000
- non-xml-technology-usage-13000
- non-xml-technology-usage-14000
- non-xml-technology-usage-17000
- non-xml-technology-usage-18000
- non-xml-technology-usage-19000
- non-xml-technology-usage-20000
- non-xml-technology-usage-21000
- non-xml-technology-usage-22000
- non-xml-technology-usage-23000
- non-xml-technology-usage-24000
- non-xml-technology-usage-25000
- non-xml-technology-usage-26000
- non-xml-technology-usage-27000
- observability-0100
- observability-0200
- observability-technology-usage-0100
- observability-technology-usage-0200
- security-01100
- security-01200
- security-01300
- security-01400
- security-01500
- security-01600
- security-01700
- security-01800
- security-01900
- security-02000
- security-02100
- security-02200
- security-02300
- security-02400
- security-02500
- security-02600
- security-02700
- security-02800
- security-02900
- security-03000
- security-03100
- security-03200
- security-03300
- security-03400
- security-03500
- security-03600
- spring-catchall-00001
- technology-usage-3rd-party-01000
- technology-usage-3rd-party-02000
- technology-usage-3rd-party-03000
- technology-usage-3rd-party-04000
- technology-usage-3rd-party-05000
- technology-usage-3rd-party-06000
- technology-usage-3rd-party-08000
- technology-usage-3rd-party-09000
- technology-usage-3rd-party-10000
- technology-usage-3rd-party-11000
- technology-usage-3rd-party-12000
- technology-usage-3rd-party-13000
- technology-usage-3rd-party-14000
- technology-usage-3rd-party-15000
- technology-usage-3rd-party-16000
- technology-usage-3rd-party-17000
- technology-usage-3rd-party-18000
- technology-usage-3rd-party-19000
- technology-usage-3rd-party-20000
- technology-usage-3rd-party-spring-03001-0
- technology-usage-3rd-party-spring-03001-1
- technology-usage-3rd-party-spring-03001-2
- technology-usage-3rd-party-spring-03002
- technology-usage-apm-00010
- technology-usage-apm-00020
- technology-usage-apm-00030
- technology-usage-apm-00040
- technology-usage-clustering-01000
- technology-usage-clustering-02000
- technology-usage-connect-01000
- technology-usage-connect-01100
- technology-usage-connect-01101
- technology-usage-connect-01200
- technology-usage-connect-01300
- technology-usage-connect-01400
- technology-usage-connect-01500
- technology-usage-connect-01600
- technology-usage-connect-01700
- technology-usage-connect-01800
- technology-usage-connect-01900
- technology-usage-connect-02000
- technology-usage-connect-02100
- technology-usage-connect-02200
- technology-usage-connect-02300
- technology-usage-connect-02400
- technology-usage-connect-02500
- technology-usage-connect-02600
- technology-usage-connect-02700
- technology-usage-connect-02800
- technology-usage-connect-02900
- technology-usage-database-01000
- technology-usage-database-01001
- technology-usage-database-01100
- technology-usage-database-01200
- technology-usage-database-01300
- technology-usage-database-01400
- technology-usage-database-01500
- technology-usage-database-01600
- technology-usage-database-01700
- technology-usage-database-01800
- technology-usage-database-01900
- technology-usage-database-02000
- technology-usage-database-02100
- technology-usage-database-02200
- technology-usage-database-02300
- technology-usage-database-02400
- technology-usage-database-02500
- technology-usage-database-02600
- technology-usage-database-02700
- technology-usage-database-02800
- technology-usage-database-02900
- technology-usage-database-03000
- technology-usage-database-03100
- technology-usage-database-03200
- technology-usage-ejb-01400
- technology-usage-embedded-framework-01000
- technology-usage-embedded-framework-01010
- technology-usage-embedded-framework-01100
- technology-usage-embedded-framework-01200
- technology-usage-embedded-framework-01300
- technology-usage-embedded-framework-01400
- technology-usage-embedded-framework-01500
- technology-usage-embedded-framework-01600
- technology-usage-embedded-framework-01700
- technology-usage-embedded-framework-02000
- technology-usage-embedded-framework-02100
- technology-usage-embedded-framework-02200
- technology-usage-embedded-framework-02300
- technology-usage-embedded-framework-02400
- technology-usage-embedded-framework-04700
- technology-usage-embedded-framework-05000
- technology-usage-embedded-framework-05100
- technology-usage-embedded-framework-05300
- technology-usage-embedded-framework-05400
- technology-usage-embedded-framework-05600
- technology-usage-embedded-framework-05700
- technology-usage-embedded-framework-05800
- technology-usage-embedded-framework-05900
- technology-usage-embedded-framework-06000
- technology-usage-embedded-framework-06100
- technology-usage-embedded-framework-06200
- technology-usage-embedded-framework-06300
- technology-usage-embedded-framework-06400
- technology-usage-embedded-framework-06500
- technology-usage-embedded-framework-06600
- technology-usage-embedded-framework-06700
- technology-usage-embedded-framework-06800
- technology-usage-embedded-framework-06900
- technology-usage-embedded-framework-07000
- technology-usage-embedded-framework-07100
- technology-usage-embedded-framework-07200
- technology-usage-embedded-framework-07300
- technology-usage-embedded-framework-07400
- technology-usage-embedded-framework-07500
- technology-usage-embedded-framework-07600
- technology-usage-embedded-framework-07700
- technology-usage-embedded-framework-07800
- technology-usage-embedded-framework-07900
- technology-usage-embedded-framework-08000
- technology-usage-embedded-framework-08100
- technology-usage-embedded-framework-08200
- technology-usage-embedded-framework-08300
- technology-usage-embedded-framework-08400
- technology-usage-embedded-framework-08500
- technology-usage-embedded-framework-08600
- technology-usage-embedded-framework-08700
- technology-usage-embedded-framework-08800
- technology-usage-embedded-framework-08900
- technology-usage-embedded-framework-09000
- technology-usage-embedded-framework-09100
- technology-usage-integration-00001
- technology-usage-integration-00002
- technology-usage-integration-00003
- technology-usage-integration-00004
- technology-usage-integration-00005
- technology-usage-integration-00006
- technology-usage-integration-00007
- technology-usage-integration-00008
- technology-usage-integration-00009
- technology-usage-integration-00010
- technology-usage-integration-00011
- technology-usage-integration-00012
- technology-usage-integration-00013
- technology-usage-integration-00014
- technology-usage-integration-00015
- technology-usage-jta-00020
- technology-usage-jta-00030
- technology-usage-jta-00040
- technology-usage-jta-00050
- technology-usage-jta-00060
- technology-usage-jta-00070
- technology-usage-jta-00080
- technology-usage-jta-00090
- technology-usage-jta-00100
- technology-usage-jta-00110
- technology-usage-jta-00120
- technology-usage-jta-00130
- technology-usage-jta-00140
- technology-usage-jta-00150
- technology-usage-jta-00160
- technology-usage-jta-00170
- technology-usage-jta-00180
- technology-usage-jta-00190
- technology-usage-jta-00200
- technology-usage-jta-00210
- technology-usage-logging-00010
- technology-usage-logging-000100
- technology-usage-logging-000110
- technology-usage-logging-000120
- technology-usage-logging-000130
- technology-usage-logging-000140
- technology-usage-logging-000150
- technology-usage-logging-000160
- technology-usage-logging-000170
- technology-usage-logging-000180
- technology-usage-logging-000190
- technology-usage-logging-00020
- technology-usage-logging-000200
- technology-usage-logging-000210
- technology-usage-logging-000220
- technology-usage-logging-000230
- technology-usage-logging-000240
- technology-usage-logging-000250
- technology-usage-logging-000260
- technology-usage-logging-000270
- technology-usage-logging-000280
- technology-usage-logging-000290
- technology-usage-logging-00030
- technology-usage-logging-00040
- technology-usage-logging-00050
- technology-usage-logging-00060
- technology-usage-logging-00070
- technology-usage-logging-00080
- technology-usage-logging-00090
- technology-usage-markup-01300
- technology-usage-mvc-01000
- technology-usage-mvc-01100
- technology-usage-mvc-01200
- technology-usage-mvc-01300
- technology-usage-mvc-01400
- technology-usage-mvc-01500
- technology-usage-mvc-01600
- technology-usage-mvc-01700
- technology-usage-mvc-01800
- technology-usage-mvc-01900
- technology-usage-mvc-02000
- technology-usage-mvc-02100
- technology-usage-mvc-02200
- technology-usage-mvc-02300
- technology-usage-mvc-02400
- technology-usage-mvc-02500
- technology-usage-mvc-02600
- technology-usage-mvc-02700
- technology-usage-mvc-02800
- technology-usage-mvc-02900
- technology-usage-mvc-03000
- technology-usage-mvc-03100
- technology-usage-mvc-03200
- technology-usage-mvc-03300
- technology-usage-mvc-03400
- technology-usage-mvc-03500
- technology-usage-mvc-03600
- technology-usage-mvc-03700
- technology-usage-mvc-03800
- technology-usage-mvc-03900
- technology-usage-mvc-04000
- technology-usage-mvc-04100
- technology-usage-mvc-04300
- technology-usage-mvc-04400
- technology-usage-mvc-04500
- technology-usage-mvc-04600
- technology-usage-mvc-04700
- technology-usage-mvc-04800
- technology-usage-mvc-04900
- technology-usage-mvc-05000
- technology-usage-mvc-05100
- technology-usage-mvc-05200
- technology-usage-mvc-05300
- technology-usage-mvc-05400
- technology-usage-mvc-05500
- technology-usage-mvc-05600
- technology-usage-mvc-05700
- technology-usage-mvc-05800
- technology-usage-mvc-05900
- technology-usage-mvc-06000
- technology-usage-mvc-0x4200
- technology-usage-security-01000
- technology-usage-security-01100
- technology-usage-security-01200
- technology-usage-security-01300
- technology-usage-security-01400
- technology-usage-security-01500
- technology-usage-security-01600
- technology-usage-security-01700
- technology-usage-security-01800
- technology-usage-security-01900
- technology-usage-security-02000
- technology-usage-security-02100
- technology-usage-security-02200
- technology-usage-security-02300
- technology-usage-security-02400
- technology-usage-security-02500
- technology-usage-security-02600
- technology-usage-security-02700
- technology-usage-security-02800
- technology-usage-security-02900
- technology-usage-security-03000
- technology-usage-security-03100
- technology-usage-security-03200
- technology-usage-security-03300
- technology-usage-security-03400
- technology-usage-security-03500
- technology-usage-test-frameworks-00010
- technology-usage-test-frameworks-00020
- technology-usage-test-frameworks-00030
- technology-usage-test-frameworks-00040
- technology-usage-test-frameworks-00050
- technology-usage-test-frameworks-00060
- technology-usage-test-frameworks-00070
- technology-usage-test-frameworks-00080
- technology-usage-test-frameworks-00090
- technology-usage-test-frameworks-00100
- technology-usage-test-frameworks-00110
- technology-usage-test-frameworks-00120
- technology-usage-test-frameworks-00130
- technology-usage-test-frameworks-00140
- technology-usage-test-frameworks-00150
- technology-usage-test-frameworks-00160
- technology-usage-test-frameworks-00170
- technology-usage-test-frameworks-00180
- technology-usage-test-frameworks-00190
- technology-usage-test-frameworks-00200
- technology-usage-test-frameworks-00210
- technology-usage-test-frameworks-00220
- technology-usage-test-frameworks-00230
- technology-usage-test-frameworks-00240
- technology-usage-test-frameworks-00250
- technology-usage-test-frameworks-00260
- technology-usage-test-frameworks-00270
- technology-usage-test-frameworks-00280
- technology-usage-test-frameworks-00290
- technology-usage-test-frameworks-00300
- technology-usage-test-frameworks-00310
- technology-usage-test-frameworks-00320
- technology-usage-test-frameworks-00330
- technology-usage-test-frameworks-00340
- technology-usage-test-frameworks-00350
- technology-usage-test-frameworks-00360
- technology-usage-test-frameworks-00370
- technology-usage-web-01000
- technology-usage-web-01100
- technology-usage-web-01100
- technology-usage-web-01200
- technology-usage-web-01300
- technology-usage-web-01300
- technology-usage-web-01400
- technology-usage-web-01400
- technology-usage-web-01500
- technology-usage-web-01500
- technology-usage-web-01600
- technology-usage-web-01600
- technology-usage-web-01700
- technology-usage-web-01700
- technology-usage-web-01800
- technology-usage-web-01800
- technology-usage-web-01900
- technology-usage-web-01900
- technology-usage-web-02000
- technology-usage-web-02000
- technology-usage-web-02100
- technology-usage-web-02100
- technology-usage-web-02200
- technology-usage-web-02200
- technology-usage-web-02300
- technology-usage-web-02300
- technology-usage-web-02400
- technology-usage-web-02400
- test-frameworks-sauge-00010
- test-frameworks-sauge-00020
- test-frameworks-sauge-00030
- test-frameworks-sauge-00040
- test-frameworks-sauge-00050
- test-frameworks-sauge-00060
- test-frameworks-sauge-00070
- test-frameworks-sauge-00080
- test-frameworks-sauge-00090
- test-frameworks-sauge-00100
- test-frameworks-sauge-00110
- test-frameworks-sauge-00120
- test-frameworks-sauge-00130
- test-frameworks-sauge-00140
- test-frameworks-sauge-00150
- test-frameworks-sauge-00160
- test-frameworks-sauge-00170
- test-frameworks-sauge-00180
- test-frameworks-sauge-00190
- test-frameworks-sauge-00200
- test-frameworks-sauge-00210
- test-frameworks-sauge-00220
- test-frameworks-sauge-00230
- test-frameworks-sauge-00240
- test-frameworks-sauge-00260
- test-frameworks-sauge-00270
- test-frameworks-sauge-00280
- test-frameworks-sauge-00290
- test-frameworks-sauge-00300
- test-frameworks-sauge-00310
- test-frameworks-sauge-00320
- test-frameworks-sauge-00330
- test-frameworks-sauge-00340
- test-frameworks-sauge-00350
- test-frameworks-sauge-00360
- test-frameworks-sauge-00370
- test-frameworks-sauge-00560
- web-01000
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment