Closed glassfishrobot closed 11 years ago
@glassfishrobot Commented Reported by swchan2@java.net
@glassfishrobot Commented jfarcand@java.net said: Fix target.
@glassfishrobot Commented jfarcand@java.net said: Re-assign.
@glassfishrobot Commented jfarcand@java.net said: Next release..
@glassfishrobot Commented jfarcand@java.net said: Fix target
@glassfishrobot Commented jfarcand@java.net said: Bump version.
@glassfishrobot Commented jfarcand@java.net said: Next release
@glassfishrobot Commented jfarcand@java.net said: Bump millestone
@glassfishrobot Commented jfarcand@java.net said: Bump version
@glassfishrobot Commented jfarcand@java.net said: Bump version
@glassfishrobot Commented jfarcand@java.net said: Bump version
@glassfishrobot Commented jfarcand@java.net said: Bump version...sorry we had a glassfish firedrill.
@glassfishrobot Commented jfarcand@java.net said: Bump to the proper version
@glassfishrobot Commented jfarcand@java.net said: Bump version
@glassfishrobot Commented jfarcand@java.net said: Bump version
@glassfishrobot Commented jfarcand@java.net said: Bump version
@glassfishrobot Commented jfarcand@java.net said: Bump millestones
@glassfishrobot Commented jfarcand@java.net said: Bump version
@glassfishrobot Commented This issue was imported from java.net JIRA GRIZZLY-262
@glassfishrobot Commented Marked as won't fix on Monday, April 8th 2013, 1:45:16 pm
In Bayeux protocol, the clientId may be null in publish request. It is working fine now as Jetty and Dojo clients seem to always have clientId. We need to handle the null clientId properly. For instance, in the case of resume comet handler.
Environment
Operating System: All Platform: All
Affected Versions
[1.9.22]