DDS code will be easier to integrate into third-party I/O code if the Entity, ReadCondition, and TopicDescription interfaces implement the java.util.Closeable interface. This is especially true under Java 7, which provides specific new language constructs for dealing with this interface.

The only method in the interface is a no-argument close(), which all of these interfaces already have.

Proposed Resolution:
Update Entity, ReadCondition, and TopicDescription to inherit from java.io.Closeable.

The base interface for all Entity-level QoS objects (e.g. DataReaderQos) is org.omg.dds.core.EntityQos. At one time during the evolution of the specification, this interface was called org.omg.dds.core.Qos. Due to an editorial oversight, this obsolete name persists in the specification document and should be updated.

• Section 7.2.5, "QoS and QoS Policies"
• Section 7.2.5.2, "Entity QoS"

Update the specification document.

ContentFiltered topics, QueryCondition, and MultiTopic all require a "Query" parameter made by an expression and a set of parameters. The current API, however treats the expression and the parameter as individual parameters and does not provide any abstraction of what could represent a generic DDS query. This makes the API more verbose and more error prone.

Resolution
---------------
Add a Query class that abstracts over the concept of a DDS query: an expression and a collection of mutable parameters

Add a Query class that abstracts over the concept of a DDS query: an expression and a collection of mutable parameters

Java 7 has a try-with-resources construct that allows a close() method to be called automatically when a certain code block ends. Java PSM can support this construct with sample loans in a way that's backwards compatible with Java 5. All we have to do is to rename the Sample.Iterator.returnLoan() method to close() and make Sample.Iterator implement the interface java.io.Closeable. Note: java.lang.AutoCloseable is available only since 1.7

Proposed Resolution:
Inherit Sample.Iterator from Java.io.Closeable and rename the Sample.Iterator.returnLoan() method to close()

The second FTF of the DDS-XTypes spec introduced several API changes that should be incorporated into the DDS-PSM-Java spec.

At the same time, the contents of the relevant portions of the DDS-XTypes spec should be incorporated as JavaDoc comments, just as has already been done for DDS itself.

No Data Available

The dds-psm-java uses a superfluous "QoSPolicy" suffix to name the DDS policies which themselves are already included in a "policy" namespace.

This issue is identical to issue #16530. This issue is created to revote on the decision taken on issue #16530 in the earlier FTF.

Proposed Resolution:

This suffix should be removed. This resolution will also make Java PSM consistent with the C++ PSM, which does not use "QosPolicy" suffix.

This suffix should be removed. This resolution will also make Java PSM consistent with the C++ PSM, which does not use "QosPolicy" suffix. This issue requires no changes to the specification document

The EntityQos interface implements java.util.Map. However, all checking of which policies apply to which Entity types is deferred to run time. The extension of Map should be updated to constrain which policies may legally be used.

Proposal: Introduce marker interfaces for each Entity type and parameterize Map with these interfaces.

Introduce marker interfaces for each Entity type and parameterize Map with these interfaces. This issue requires no changes in the specification document.