Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Position of defaultjvmserver parameter is confusing. #230

Open
davenice opened this issue Mar 21, 2024 · 1 comment
Open

Position of defaultjvmserver parameter is confusing. #230

davenice opened this issue Mar 21, 2024 · 1 comment

Comments

@davenice
Copy link
Member

If you're packaging an existing WAR as a bundle by extending the config, you specify the defaultjvmserver within the execution config.

If you create a separate module for the CICS bundle, you specify the defaultjvmserver outside the execution config.

This is confusing and has caught new users out several times.

@davenice
Copy link
Member Author

Also the JVM server is set by default to MYJVMS in

@Parameter(property="cicsbundle.defaultjvmserver", defaultValue = "MYJVMS", required = false, readonly = false)

In #138 it looked like decided to stop providing a default JVM server if the user didn't specify one, because anything we supply is unlikely to be useful. However we didn't make this change in the code.

I think the behaviour needs a bit of investigating to propose the correct fix.
If you configure your individual Java projects (war/ear etc) with a jvmserver parameter, I guess we shouldn't give an error about the JVM server being missing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant