Anyone pulling ChannelFactories from container-integration?

["Trustin Lee (이희승)"]

Hi folks,

Netty provides some pre-constructed ChannelFactories when integrated
into Guice, JBossMC, Spring, and OSGi.  For example, there is a Spring
beans XML file in the JAR:

    http://is.gd/aVojf

Netty also changes the default logging framework to the default choice
of the container (e.g. JCL for Spring).  Since JBossMC and OSGi
activated a bundle automatically, the logging is configured without any
additional coding.

All users I talked to seem to call the constructor and create a
ChannelFactory by themselves rather than pulling the pre-constructed
ones from the container via injection.

If there is no objection, I'd like to remove the pre-construction code
from the container integration and leave only logging framework
auto-configuration to get rid of the overhead of maintaining the
pre-construction code when a new transport is added or when a new
container support is added.

Thanks,
Trustin
-- 
what we call human nature in actuality is human habit
http://gleamynode.net/


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
Url : http://lists.jboss.org/pipermail/netty-users/attachments/20100324/c63cdb5b/attachment-0001.bin