Hi Grizzly folks,
I've noticed that a dependency was recently introduced between the
Grizzly 2dot0 branch and Glassfish code. For example:
com.sun.grizzly.memory.jmx.ByteBufferManager:
import org.glassfish.gmbal.Description;
import org.glassfish.gmbal.ManagedAttribute;
import org.glassfish.gmbal.ManagedObject;
/**
* {_at_link com.sun.grizzly.memory.ByteBufferManager} JMX object.
*
* @author Alexey Stashok
*/
@ManagedObject
@Description("Grizzly Memory Manager")
public class ByteBufferManager extends MemoryManager {
...
}
Is this just a temporary state of the code? If not, how are
non-Glassfish applications supposed to compile/use Grizzly without
pulling in a bunch of unwanted code?
Also, it looks like a load of funky changes have been made in the 2dot0
core Grizzly APIs (e.g. probes) recently. Are there any which we should
be particularly aware of and use?
Many thanks,
Matt