Skip to content

Commit 6532620

Browse files
adding 2.4.0 release notes (#1231)
* adding 2.4.0 release notes * edits
1 parent a04b34d commit 6532620

File tree

1 file changed

+38
-0
lines changed

1 file changed

+38
-0
lines changed
Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
+++
2+
title = "Release 2.4.0"
3+
date = 2022-11-02T15:27:38-05:00
4+
weight = 5
5+
pre = "<b> </b>"
6+
+++
7+
8+
### Changes in Release 2.4.0
9+
- [Major New Features](#major-new-features)
10+
- [Other Changes](#other-changes)
11+
- [Bugs Fixes](#bug-fixes)
12+
- [Known Issues](#known-issues)
13+
14+
15+
#### Major New Features
16+
- None
17+
18+
#### Other Changes
19+
- #1193 - Added support for changing the RCU Data Source type during JRF domain creation (WDT-636).
20+
- #1210 - Improved the speed of remote discovery by bypassing remote calls to determine if a field was set (WDT-663).
21+
- #1218 - Added `-target` support for WebLogic Kubernetes Operator 4.0 to generate the domain and cluster schema resources.
22+
- #1220 - Added support for application modules for JDBC, JMS, and WLDF with normal WDT tokenization mechanisms (WDT-675).
23+
24+
#### Bug Fixes
25+
- #1194: Resolved an ordering issue when setting the `FrontendHost` and `FrontendHTTPPort` with dynamic clusters (WDT-668).
26+
- #1196: Fixed issue #1170 which was causing an unexpected `NameError`.
27+
- #1197: Log a warning when the security provider schematype file is missing (WDT-645) .
28+
- #1208: Refactored tool exit handling to simplify the logic and resolve various errors.
29+
- #1209: Resolved an issue with structured applications where the model data was not being honored for the deployment plan file name.
30+
- #1214: Resolved an issue with structured application discovery causing duplicate override files to show up in the archive file.
31+
- #1217: Resolved an issue with ATP database support that was not handling connect strings with multiple description fields.
32+
- #1229: Resolved an alias issue where the `TopicSubscriptionParams` was incorrectly available on `UniformDistributedQueue` and not `UniformDistributedTopic`.
33+
34+
#### Known Issues
35+
- Due to the changes made for WDT-663, the resulting remotely discovered model contains extra fields that would not normally be there.
36+
This is an area of ongoing work to clean up the online aliases to not depend on these extra remote calls to produce a clean model.
37+
38+

0 commit comments

Comments
 (0)