|
| |
|
| java.lang.Object
 org.directwebremoting.jms.Unsupported
| Unsupported | | public class Unsupported (Code) | | This class tracks the parts of the JMS spec that DWR to not support.
In some respects this is hugely over-engineered, we could simply inline all
these methods and delete the class, however the advantage of this approach is
that we can track what needs to be done to add support for some feature.
author:
Joe Walker [joe at getahead dot ltd dot uk] |
| noBinaryMessages | | static UnsupportedOperationException noBinaryMessages()(Code) | | DWR does not support binary messages.
It could by making use of the file download feature, however we need to
bed things in a bit first
|
| noManualAcknowledgment | | static UnsupportedOperationException noManualAcknowledgment()(Code) | | DWR does not support manual acknowledgment.
When DWR supports Gears properly then we might be able to add this
|
| noMessageExpiry | | static UnsupportedOperationException noMessageExpiry()(Code) | | We don't expire messages other than beyond the script session timeout
which is not set at a message level
|
| noMessageSelectors | | static UnsupportedOperationException noMessageSelectors()(Code) | | Since it's not clear how we will map message properties to JSON messages,
we are likely to ignore this in the short term
|
| noPointToPoint | | static UnsupportedOperationException noPointToPoint()(Code) | | Publish of point to point messages aimed at browsers seems like a very
broken concept. Maybe this will never be implemented.
|
|
|
|