The WsdlImporter can now import Bindings and Endpoints
from the WSDL, currently supporting BasicHttpBinding,
BasicHttpsBinding and NetTcpBinding.
There is also - limited and still experimental - support
for WS-Policy 1.5. I only did the very basic pieces so
far, for instance things like TransportWithMessageCredentials
are not supported yet.
The policy importer will emit lots of warnings via
`MetadataImporter.Errors` (as warnings, not errors) whenever
it encounters something that it doesn't understand and
is also forgiving towards unknown and/or mal-formed
policy assertions.
This behavior is different from the MS runtime, which is
very strict, but there are simply too many missing pieces
to be more pedentic here. Check whether Errors.Count == 0
to see whether all policy assertions have been correctly
imported.
There are also a few metadata samples, which are part of the
new nunit tests. These are currently working:
BasicHttp.xml, BasicHttp_Mtom.xml, BasicHttp_NtlmAuth.xml,
BasicHttp_TransportSecurity.xml, BasicHttps.xml,
BasicHttps_NtlmAuth.xml, NetTcp.xml, NetTcp_TransferMode.xml,
NetTcp_TransportSecurity.xml
There are a few more in the Tests/MetadataTests/Resources/
directory which demonstrate missing pieces.
XmlMessagesFormatter will be used in Sys.Xml.Serialization.dll and this
type should not be excluded by !NET_2_1 or !MOONLIGHT. It is not doable
if this class is in BaseMessagesFormatter.cs.
There were several issues here:
- The IChannelDispatcherBoundListener was defined twice, in two different namespaces, and it caused code in
ChannelDispatcher.Attach not to set its associated listener's ChannelDispatcher property to the correct value.
This, in turn, caused incorrect HttpListenerManagerTable operation, where it would put the "/js" and "/jsdebug"
dispatchers in separate HttpListenerManagers, instead of in the main (base) service's one.
- After fixing the above, it turned out that SvcHttpHandler selected the manager based on the host's base address,
when it should first try to find one whose URL matches the current request exactly.
* 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
* HttpTransportBindingElement.cs :
Use new HTTP channel listener implementation.
* ChannelDispatcher.cs : enable service throttling again.
This time Http(Listener), ASP.NET and TCP listeners all work.
* System.ServiceModel.dll.sources :
add new HTTP channel listener implementation sources.
Old sources will be kept for a while, won't entirely vanish as
ASP.NET support will live there.
svn path=/trunk/mcs/; revision=159491
* System.ServiceModel.dll.sources: add SL config loader here
for easy debugging under 2.0 profile.
* SilverlightClientConfigLoader.cs : add another loop blocker.
Do not reject binding configuration with no basic http binding.
In SL3 it may be custom and such configuration should be valid.
svn path=/trunk/mcs/; revision=149606
* System.ServiceModel.dll.sources: add VirtualPathExtension.cs.
* VirtualPathExtension.cs : new file.
* HttpTransportBindingElement.cs, SvcHttpHandlerFactory.cs :
revert the change, to use internal asp.net state again.
* SvcHttpHandler.cs : add VirtualPathExtension.
* ConfigUtil.cs : revert the change, to use ServiceHostingEnvironment
internal member again.
* ServiceHostingEnvironment.cs : revert the change, to use
internal asp.net state again.
svn path=/trunk/mcs/; revision=143277
* ClientRuntimeChannel.cs, DuplexClientRuntimeChannel.cs : split out
from former to latter and implemented most part of listener part.
Make sure to open internal channel at base ClientRuntimeChannel.
* ClientProxyGenerator.cs : minimize !NET_2_1 to here.
* System.ServiceModel.dll.sources: added
DuplexClientRuntimeChannel.cs and CallbackInstanceContextProvider.cs.
svn path=/trunk/mcs/; revision=140478
* NamedPipeReplyChannel.cs, NamedPipeRequestChannel.cs,
NamedPipeChannelFactory.cs, NamedPipeChannelListener.cs :
ongoing works, not working at all yet.
* System.ServiceModel.dll.sources: add more named pipe files.
svn path=/trunk/mcs/; revision=140341
* TcpDuplexSessionChannel.cs, TcpBinaryFrameManager.cs:
split out binary frame manager class into separate file.
* System.ServiceModel.dll.sources:
split out binary frame manager class into separate file.
svn path=/trunk/mcs/; revision=138489
* TcpReplyChannel.cs : new reply channel implementation.
* TcpChannelListener.cs : use above for streamed reply channel.
* TcpDuplexSessionChannel.cs : more streaming mode support.
* TcpRequestChannel.cs : a couple of updates to get it working
with the reply channel above. Still some issues on .NET interop.
* System.ServiceModel.dll.sources: add TcpReplyChannel.
svn path=/trunk/mcs/; revision=138299
* TcpRequestChannel.cs : new channel file (TCP for request/reply
messaging pattern). The messaging part is not working yet.
* TcpChannelFactory.cs : support IRequestChannel.
* TcpDuplexSessionChannel.cs : add unsized message support.
* System.ServiceModel.dll.sources: add TcpRequestChannel.
svn path=/trunk/mcs/; revision=138125
* CustomPeerResolverService.cs, LocalPeerResolverService.cs,
ICustomPeerResolverContract.cs : add local machine peer resolver
implementation that can work across appdomains (based on
dispatching peer resolver that communicates with a ServiceHost
which is either locally started or running as a different process).
* System.ServiceModel.dll.sources:
Added new custom peer resolver files.
svn path=/trunk/mcs/; revision=137504