Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Malformed XPath filters fail silently at client side. #33
I can start Comet with an XPath filter, like so:
which works fine. But, if the XPath is broken, e.g.
(note missing close brackets), then Comet will start up quietly and the filter will silently fail. Currently, the only way to check if the XPath translates to a successfully installed filter is to monitor the logs at the server end.
This is addressed by b1e83bd. In the event of an XPath syntax error, Comet will refuse to start as follows:
Note that this is just checking the XPath for syntax correctness. There's no mechanism for the broker to report back to the subscriber that the filter has been accepted and installed successfully; indeed, brokers which are not Comet should simply silently ignore the filter and you'll get no feedback that that's what they're doing.
Does this solve your problem?