It is part of bugfix 687902.
To get the bug fixed, the new "using" sections in ChannelDispatcher.cs to
explicitly dispose channels. But this causes regression in PerSession-based
tests. So some new session management code is (likely) required as well.
It will also alter "mixed" MaxConcurrentCalls and MaxConcurrentSessions with
correct management code.
The problem is that DispatchRuntime.Type is a service implementation type
that could implement two or more contract interfaces, and it was in random
order how ServiceProxyGenerator picks up the contract type. Now it looks
for correct contract type instead of the service type by exactly looking
for the target contract in the endpoint (dispatcher).
* InputOrReplyProcessor.cs : remove SecurityHandler. WS-Trust must
be handled before endpoint dispatching (it must not pass contract
filter) and doesn't make sense to be here.
* SecurityHandler.cs : move to old-code.
* SecurityReplyChannel.cs : handle WS-Trust message here.
* SecurityRequestContext.cs : so, do not pass those messages here.
* SslSecurityTokenAuthenticator.cs,
AuthenticatorCommunicationObject.cs,
SecureConversationSecurityTokenAuthenticator.cs :
add timeout argument to negotication requests.
* System.ServiceModel.dll.sources: remove SecurityHandler.cs
svn path=/trunk/mcs/; revision=160244
* ContractDescriptionGenerator.cs : Now callback contract methods are
also reflected into OperationDescription as well as those from non-
callback contract. Callback methods have reverse MessageDirection,
so adjust them.
* ContractDescription.cs, ServiceEndpoint.cs, TypedMessageConverter.cs :
A bit of renaming / reflect method call changes.
* EndpointDispatcher.cs, DispatchRuntime.cs, ClientRuntime.cs :
now Callback[Dispatch|Client]Runtime properties are always filled
so that users can configure the callback runtimes (not sure such
configured runtimes work fine yet, but it is a required step).
* InputOrReplyRequestProcessor.cs : instead of HasCallbackRuntime
hack, use CallbackClientRuntime.CallbackContractType for checking
callback existence.
* ClientProxyGenerator.cs : CreateProxyType now carefully considers
requested proxy type, contract type and callback contract type.
i.e. now the resulting proxy has implemented methods for callbacks
that are also filled at ContractDescription.
* ClientRuntimeChannel.cs : reflect some method call changes.
svn path=/trunk/mcs/; revision=158412
* ServiceRuntimeChannel.cs, ServiceProxyGenerator.cs:
make them public and add Contract property for service callback
proxies too for the same reason.
* InputOrReplyRequestProcessor.cs : now ServiceRuntimeChannel is
moved to fake public namespace.
svn path=/trunk/mcs/; revision=152523
* ContractDescriptionGenerator.cs : fix GetCallbackContract() to
correctly retrieve ServiceContractAttribute from the service type,
not the callback type. This ended up to get the bug #567672 sample
working (but it will break at some stage as it involves some
non-implemented classes).
* EndpointDispatcher.cs, InputOrReplyRequestProcessor.cs :
Pass service type to correctly retrieve ServiceContractAttribute
from the service type, not callback type.
* ServiceProxyGenerator.cs, ServiceRuntimeChannel.cs :
Pass service type to correctly retrieve ServiceContractAttribute
from the service type, not callback type.
* CallbackBehaviorAttributeTest.cs : added callback example from
bug #567672.
svn path=/trunk/mcs/; revision=149226
* EndpointDispatcher.cs : AddressFilter is always non-null.
* DispatchRuntime.cs : CallbackClientRuntime seems to be created even
for non-callback dispatchers. Fixing this also results in fixes in
couple of nunit regressions.
* InputOrReplyRequestProcessor.cs : the change above required fix
here too (it has null check).
svn path=/trunk/mcs/; revision=141743
* OperationInvokerHandler.cs, ReplyHandler.cs :
- Eliminate ReplyHandler use. What is does is simple reply, while
it brings inconsistency between sync and async models.
What reply handler used to do are now integrated.
- Support ErrorHandlers and InputSessionShutdownHandlers.
Actually ErrorHandlers were processed at wrong place and they
weren't called where they are expected.
* InputOrReplyRequestProcessor.cs : hence eliminated ReplyHandler.
* BaseRequestProcessor.cs : add FIXME notes on ErrorHandlers.
svn path=/trunk/mcs/; revision=141326
* ServiceRuntimeChannel.cs : change .ctor() args.
Add proxy hook methods that simply calls those in callback
ClientRuntimeChannel.
* InputOrReplyRequestProcessor.cs : now it could return an instance
of dynamically generated proxy over DuplexServiceRuntimeChannel.
svn path=/trunk/mcs/; revision=139550
* ReplyHandler.cs, InputOrReplyRequestProcessor.cs,
MessageProcessingContext.cs : reply processing is also needed by
non-request channels (i.e. duplex). Current code basis lacked
such possibility. Quick fix by adding duplex support in
ReplyHandler so far.
svn path=/trunk/mcs/; revision=134046
* ChannelDispatcher.cs, SecurityHandler.cs,
InputOrReplyRequestProcessor.cs, MessageProcessingContext.cs :
remove default communication timeouts from several types. They
bring bogus NRE. Instead, fill timeouts in ChannelDispatcher and
use it when required (it was actually *only* request processor).
* ChannelDispatcherTest.cs : make sure ctor args are nullable.
svn path=/trunk/mcs/; revision=134044