The end of next week will be 8 weeks since 2.1.1 was released and we've fixed
a BUNCH of things (something like 58 jira's so far) that would be good to
get into peoples hands.
Are there any objections to that? If not, I'll get it built monday afternoon
and call the votes.
--
Daniel Kulp
Hmm.. I'm not really sure, but this MAY be correct behavior.
I'm thinking something like the MTOM policy. For that, there has to be
something on the outgoing side to see if the MTOM policy is there and turn on
MTOM if so.
It's somewhat like some policies are "enforced" on the incoming chain
Well I can definitely work around the problem, just by configuring my
interceptors to check off the same assertions on the outbound side.
This requires though, that I stick a reference to some request state
information on the exchange, and that I ensure that an OutInterceptor
is installed
dkulp wrote:
>
> The end of next week will be 8 weeks since 2.1.1 was released and we've
> fixed
> a BUNCH of things (something like 58 jira's so far) that would be good to
> get into peoples hands.
>
> Are there any objections to that? If not, I'll get it built monday
> afternoon
> and c
On Friday 08 August 2008 7:01:27 pm Glen Mazza wrote:
> dkulp wrote:
> > The end of next week will be 8 weeks since 2.1.1 was released and we've
> > fixed
> > a BUNCH of things (something like 58 jira's so far) that would be good
> > to get into peoples hands.
> >
> > Are there any objections to t
