Commit Graph
14 Commits
Author SHA1 Message Date
Atsushi Eno 0c7a1a1f5c Fix the issue that callback contract often gets confused by picking unexpected contract type.
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).
2010-09-29 16:41:59 +09:00
Atsushi Eno 66cda586dc 2010-07-12 Atsushi Enomoto <[email protected]>
* 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
2010-07-12 13:17:58 +00:00
Atsushi Eno 3966750e29 2010-06-03 Atsushi Enomoto <[email protected]>
* 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
2010-06-03 16:33:31 +00:00
Atsushi Eno d7a25cf1a4 2010-02-26 Atsushi Enomoto <[email protected]>
* 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
2010-02-26 05:12:22 +00:00
Atsushi Eno 5c3aa1b73a 2010-01-08 Atsushi Enomoto <[email protected]>
* 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
2010-01-08 10:40:46 +00:00
Atsushi Eno 8110699760 2009-09-11 Atsushi Enomoto <[email protected]>
* 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
2009-09-11 10:33:15 +00:00
Atsushi Eno 006af1c9f7 2009-09-04 Atsushi Enomoto <[email protected]>
* 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
2009-09-04 13:51:22 +00:00
Atsushi Eno 0c22cb44ff 2009-08-07 Atsushi Enomoto <[email protected]>
* 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
2009-08-07 06:33:38 +00:00
Atsushi Eno 5846997eef 2009-06-23 Atsushi Enomoto <[email protected]>
* InputOrReplyRequestProcessor.cs : bogus initialization.


svn path=/trunk/mcs/; revision=136672
2009-06-23 03:00:24 +00:00
Atsushi Eno b430f47799 svn:eol-style native.
svn path=/trunk/mcs/; revision=135653
2009-06-08 09:21:35 +00:00
Atsushi Eno af538f251c 2009-05-18 Atsushi Enomoto <[email protected]>
* ErrorProcessingHandler.cs, InputOrReplyRequestProcessor.cs :
	  they also premise request-reply channel and broke duplex channels.


svn path=/trunk/mcs/; revision=134319
2009-05-18 13:29:28 +00:00
Atsushi Eno ec6df7fbdb 2009-05-13 Atsushi Enomoto <[email protected]>
* 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
2009-05-13 10:30:23 +00:00
Atsushi Eno 7bcaf9bbbc 2009-05-13 Atsushi Enomoto <[email protected]>
* 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
2009-05-13 10:08:46 +00:00
Jb Evain bdd0809c70 move to from olive to mcs
svn path=/trunk/mcs/; revision=111187
2008-08-20 21:24:37 +00:00