You are correct. Thereâ€™s no general problem with WCF; itâ€™s just this
particular API that Orion is using thatâ€™s problematic.
[mailto:firstname.lastname@example.org] On Behalf Of Ivan Porto
Sent: Thursday, March 12, 2009 11:54 AM
Subject: Re: [Ironruby-core] More WCF fail
But in the case of WCF this doesn’t have to be the case right?
You can create a different behavior where you tell WCF how to create
instances and you can create a service host that also knows how to
handle dynamic objects. After all if you can get an IoC container to
provide the instances, surely you can hook IronRuby in there too.
Wouldn’t creating a servicehostfactory, servicehost and behavior solve
I wasn’t expecting to use the plain vanilla WCF stuff but rather with a
slightly customized infrastructure.
On Thu, Mar 12, 2009 at 6:15 PM, Curt H.
Thereâ€™s no CLR Type object that can fully represent your Ruby class, so
you canâ€™t meaningfully pass the type to any API that wants to be able to
create an object from it. This is still an area of active investigation
and thought for us.
On Behalf Of Orion E.
Sent: Wednesday, March 11, 2009 4:44 PM
Subject: [Ironruby-core] More WCF fail
Had time to get back to the WCF stuff: Here’s the latest
uri = Uri.new “http://localhost:8700/MyService”
binding = WSHttpBinding.new
host = ServiceHost.new MyService
host.add_service_endpoint(IWcfContract.to_clr_type, binding, uri);
=> Now raises the following error (new and different from last time,
The contract name ‘IWcfContract’ could not be found in the list of
contracts implemented by the service ‘IronRuby.Builtins.RubyClass’.
I also tried creating an abstract C# class as follows:
public abstract class WcfContractClass : IWcfContract
public abstract string Ping(string input);
and then having the ruby class do this:
class MyService < WcfContractClass
however the same error occurs. Still running the dlr nightly v12211
Ironruby-core mailing list