Matt Pavlovich

xew key features: Part 1. Remove inner collection wrapper-only classes (ie. 'items') Part 2. Delete unused wrapper-only classes Use cases for 'keep' (ie sometimes do not do part 2): [Scenario...

@laurentschoelens @SebasHein XSD has a gap in the spec where there is not a way to define an 'interface' type concept. ``` Order + Collection getItems()

Other xew-related plugins have an option to define which classes to 'keep'. For example, you would want to keep 'Order', but usually delete the wrapper-only object 'Orders'

The use case for annotate + xew makes more sense for inner collections. The order object in this schema is eligble for xew deletion since it is defined only as...

@cshannon thanks for taking the time to review and providing the thoughtful feedback. I agree, the threading model can be improved and leveraging more modern Java constructs would improve performance...

> My initial comments of not to include it were because I thought you meant with Tech Preview as it's just for testing, etc and not really intended for users...

@hutchig I'm with you.. I think a JMS v3.0 is long over due. There are a couple other initiatives looking to do something similar-- OpenMessaging, MicroProfile, etc. Kafka not having...

@bshannon You bring up some good points. I've been amp'd up to get this addressed for a while, so my injecting of some humor (punting the spec into the sun)...

@bshannon I've scanned the JMS specs, and it looks like you are right. While the notion that PTP and PubSub are separate domains, the naming needing to be distinct isn't...

Yah! We have a milestone =) Seems like there is sufficient room for discussion on improvements and growing interest to make a JMS v3.0 move forward. How about we move...