Open jmls opened 8 months ago
To answer by way of a follow-up, do you currently use it or need to use it? Is there anything which has broken since the last release if used with a version of OpenEdge 12.6 or later?
I was just looking - didn't want to get into something that wasn't going to be updated. There's been some new features (generic lists etc) in later versions of openedge and was wondering if the toolkit was going to be updated to take into account the features that 12.8 LTS has
If there is a distinct feature that needs to be captured as part of this implementation, then it can be requested specifically and we can look at whether it's worthwhile to customers to implement. At present, there are no issues or feedback offered prior to your question, so it's not clear if customers even still desire to use this as a template/solution.
cool, thanks. I was also surprised at the lack of feedback - if OERA is still being pushed as best practice then having a template like this as a base is really useful
The good news is that the artifacts shipped with the product use more and more of what is available in the ABL. So the OpenEdge.Core and OpenEdge.Net classes in general are using things like the HashMap and Collections classes where it makes sense. So in terms of demonstrating usage within ABL we do that on a more embedded level--you may not see it, but it's there and you can look at the source to see how we use it. Meanwhile, in so far I am aware there's no need to update anything here, unless there's a direct report about something which needs attention.
Curious to know, as there hasn't been an update since 12.5 ...