It appears that the cometd component will consume messages even if a browser client is not subscribed to the channel the cometd component is providing. Essentially any message delivered to the component before a browser client connects is sent to never-never land.
Is this be the expected behavior, or should the cometd component wait to consume messages until it has a connected client to send them to? -- View this message in context: http://www.nabble.com/Cometd-message-consumption-tp21355768s22882p21355768.html Sent from the Camel - Users mailing list archive at Nabble.com.
