itm/netty-handlerstack — Issue #40: Setting the FilterPipeline using XML results in reverse order
Author: danbim
Created: 2011-12-15 13:09:04+00:00
State: open
Labels: Task

The implementation of FilterPipeline now takes the first element of the list passed to setChannelPipeline as the bottommost handler so the behavior is consistent with what Netty does. However, if we use XML to configure the FilterPipeline this results in the reverse order than intended. The idea is to have an XML file that looks as follows:

```

```

to result in the dlestxetx-framing handler on bottom of the stack and the logging-handler on top of the stack as this is most intuitive.

In order for this to happen the logic interpreting the XML and setting the FilterPipelines handlers must be changed to behave inverse.