Conversation
|
@Manvi-55 the workflow for building the repo will need to be updated to specify only Java 17 |
PhilWakelin
left a comment
There was a problem hiding this comment.
Does the web.xml need updating to Jakarta EE 10 xsd i.e.
| compileOnly ("javax.transaction:javax.transaction-api") | ||
|
|
||
| // Java Transaction API - don't include in the final build | ||
| implementation 'jakarta.transaction:jakarta.transaction-api' |
There was a problem hiding this comment.
Why is this implementation I think compileOnly is more suitable as the Liberty runtime should provide the JTA runtime.
| <dependency> | ||
| <groupId>javax.transaction</groupId> | ||
| <artifactId>javax.transaction-api</artifactId> | ||
| <version>1.3</version> |
There was a problem hiding this comment.
The javax.transaction-api dependency needs to be changed to jakarta, similar to the Gradle change.
There was a problem hiding this comment.
There is no version 1.3 of jakarta.transaction-api so this doesn't build.
There was a problem hiding this comment.
The CICS TS BOM should be upgraded to 6.1 to match the maven pom.xml
|
|
||
| ### Check dependencies | ||
|
|
||
| Before building this sample, you should verify that the correct CICS TS bill of materials (BOM) is specified for your target release of CICS. The BOM specifies a consistent set of artifacts, and adds information about their scope. In the example below the version specified is compatible with CICS TS V5.5 with JCICS APAR PH25409, or newer. That is, the Java byte codes built by compiling against this version of JCICS will be compatible with later CICS TS versions and subsequent JCICS APARs. |
There was a problem hiding this comment.
@Manvi-55 can you update the references here to CICS TS 5.5 to refer to CICS TS 6.1, in order to match the min prereqs.
|
|
||
| >Tip: *In Eclipse, Gradle (buildship) is able to fully refresh and resolve the local classpath even if the project was previously updated by Maven. However, Maven (m2e) does not currently reciprocate that capability. If you previously refreshed the project with Gradle, you'll need to manually remove the 'Project Dependencies' entry on the Java build-path of your Project Properties to avoid duplication errors when performing a Maven Project Update.* | ||
|
|
||
| #### Gradle Wrapper (command line) |
|
|
||
| This creates a WAR file inside the `target` directory. | ||
|
|
||
| ## Deploying |
| distributionBase=GRADLE_USER_HOME | ||
| distributionPath=wrapper/dists | ||
| distributionUrl=https\://services.gradle.org/distributions/gradle-7.5-rc-1-bin.zip | ||
| distributionUrl=https\://services.gradle.org/distributions/gradle-8.7-bin.zip |
There was a problem hiding this comment.
Should we be using Gradle 8.14 here as this is the latest V8 release?
| plugins | ||
| { | ||
| id 'org.springframework.boot' version '2.7.0' | ||
| id 'org.springframework.boot' version '3.5.9' |
There was a problem hiding this comment.
Should we upgrade to the latest release of 3.5 namely 3.5.13?
|
The Gradle build does not work on my win11 machine and complains about the Java toolchain. With Java 17 set as my JAVA_HOME I get My Java setup is: |
|
Issuing a GET to the context root for the application: i.e. http://host:port/cics-java-liberty-springboot-transactions-0.1.0 does not return the Usage Guide as documented in the README Instead the browser returns:
|
I had a look at the TransactionController Class and it has a mapping for the "/" URL, so the trailing slash is required to obtain the Usage Guide. So I think the usage instructions just need updating to cover this. |
No description provided.