error in the WSDLusing remoring portal

marcotonix posted on Tuesday, February 24, 2009

Hi

We have a remoting portal web  application using a web service with CLSA 3.0.4 and everything is working ok, so we sent our product to Microsoft certification but they found an error when they run the WSDL  tool “Error: Unable to import binding 'RemotingPortalBinding' from namespace 'http://s

chemas.microsoft.com/clr/nsassem/Csla.Server.Hosts/Csla%2C%20Version%3D3.0.4.0%2

C%20Culture%3Dneutral%2C%20PublicKeyToken%3D93be5fdc093e4c30'.

  - Unable to import operation 'Create'.

  - The datatype 'http://schemas.microsoft.com/clr/ns/System:Type' is missing.”  

 

I checked the wsdl file and all the namespaces are ok the problems are in all the data type definitions  that have relation with the namespace  

"http://schemas.microsoft.com/clr/ns/System"

“http://schemas.microsoft.com/clr/nsassem/System.Collections.Specialized/System%2C%20Version%3D2.0.0.0%2C%20Culture%3Dneutral%2C%20PublicKeyToken%3Db77a5c561934e089”

All these data type are used it in the CLSA  so I am wondering if you have some idea what could  be the reason about these error, I have been looking for the internet for a solution that resolves this problem but nothing yet, I appreciate any idea that you have about this issue.

 

I attached my wsdl and webconfig.

RockfordLhotka replied on Tuesday, February 24, 2009

There's a known issue that you can't request the wsdl for the RemotingHost for the data portal. This doesn't affect the operation of the data portal, because it never requests the wsdl. Additionally, since the data portal is a closed technology, no one should ever get the wsdl, much less try to use it. Only the data portal client can successfully invoke the data portal host.

In other words, this is technically a bug, but I've viewed it as a super low priority bug. First, because it doesn't affect the use of the data portal. Second, because it actually blocks people from doing something bad (getting and trying to use the wsdl), so the bug is "beneficial". And third, because Remoting is depreciated, and I recommend that people move to WCF.

marcotonix replied on Wednesday, February 25, 2009

Thanks for the reply, I agree with your because the application is working very well, so I will try to convince the guys so we can continue with the certification and in the future version we are goping to move to WCF.

marcotonix replied on Thursday, February 26, 2009

To avoid problems with the certification, I did changes in the configuration files to use WCF but I have an error so I ran the project tracker application to see how works but I receieve the same error 

Message="Could not load type 'Csla.DataPortalClient.WcfProxy' from assembly 'Csla, Version=3.0.4.0, Culture=neutral, PublicKeyToken=93be5fdc093e4c30'."

 Source="mscorlib"

 TypeName="Csla.DataPortalClient.WcfProxy"

 I modified in different way the configuration file but nothing works, any idea what am I doing wrong?

marcotonix replied on Friday, February 27, 2009

I found the problem for some reason the Clsa DLL was wrong so I just download the source code and re-build and every thing is working ok now.