-
Task
-
Resolution: Done
-
Undefined
-
MTR-1.0.0
-
None
-
None
-
False
-
None
-
False
-
-
-
AMM Sprint 229, AMM Sprint 232, AMM Sprint 231
-
None
This task originated from some feedback from Kabir Kahn
I've tried running MTA now against the war resulting from this simple application https://github.com/kabir/managed-wildfly-deployments/tree/main/postgres
/windup-cli --input ../../../sourcecontrol/wildfly/managed-server-deployments/postgres/target/ROOT.war --output ../samples/output/postgres-target --target eap:8 --packages com.acme org.apache --exportCSV
The ApplicationFileTechnologies doesn't show a lot in this case:
App Name | Manifest | Maven XML | Properties |
ROOT.war | Manifest | Maven XML | Properties |
If I look in the Technologies tab of the html report I see a single check under Connect/Other. I also get the same if I use the new 'discovery' target instead of 'eap:8'.
As for the actual application, and what it contains, here are some details:
- It uses Jakarta RESTful web services - PostgresDatasourceEndpoint.java / /PostgresDatasourceApp.java
- It uses CDI and transactions - TransactionalBean.java
- It uses JPA - TransactionalBean.java / ExampleEntity.java / persistence.xml
- In persistence.xml, it is referencing a datasource called java:jboss/datasources/PostgreSQLDS
So at least from my side, these are the kind of things that would be useful to have reported at the moment. We're starting small so this list will grow as we explore more advanced scenarios
- is duplicated by
-
WINDUPRULE-923 Jakarta EE 10 Technology Tags
- Closed
- is incorporated by
-
WINDUPRULE-922 Java EE / Jakarta EE / EAP to Quarkus migration
- New
- mentioned on