Skip to main content

Interop with DOTNET?

3 replies [Last post]
onders
Offline
Joined: 2008-03-15

Hello, i have a DOTNET Security Token Service with a wsdl attached.

In netbeans, I try to create a web service reference in my client application but there are some warnings and no STS class generation is made by wsimport.

Only these 3 classes are generated,

MessageBody.java
ObjectFactory.java
package-info.java. and XXXSTSService.java or any class similar to this is not created. Naturally, in client side nothing is done related to DOTNET STS.

When we try to use wsimport to generate necessary java classes while referencing that STS on the client side, we get those warnings.

[WARNING] SOAP port "CustomBinding_ISecurityTokenService": uses a non-standard SOAP 1.2 binding.
line 1 of file:/C:/nbproj/BankClientApp/src/conf/xml-resources/web-service-references/service.svc/wsdl/localhost/WCFSecurityTokenService/service.svc.wsdl

[WARNING] ignoring operation "IssueToken": message part does not refer to a schema element declaration
line 1 of file:/C:/nbproj/BankClientApp/src/conf/xml-resources/web-service-references/service.svc/wsdl/localhost/WCFSecurityTokenService/service.svc.wsdl

[WARNING] Port "CustomBinding_ISecurityTokenService" does not contain any usable operations
line 1 of file:/C:/nbproj/BankClientApp/src/conf/xml-resources/web-service-references/service.svc/wsdl/localhost/WCFSecurityTokenService/service.svc.wsdl

[WARNING] Service "SamlSecureTokenService" does not contain any usable ports. try running wsimport with -extension switch.
line 1 of file:/C:/nbproj/BankClientApp/src/conf/xml-resources/web-service-references/service.svc/wsdl/localhost/WCFSecurityTokenService/service.svc.wsdl

What shoul we do to solve those problems. I Can not find anything? Any helps would be great!!

Thanks in advance....

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
jdg6688
Offline
Joined: 2005-11-02

All the client artifacts are already available in the Metro code for STS.

What you need is the policy in the WSDL.

Can you treat the WCF STS the same way as the Metro STS?

Cretae a reference to it and configure the security. Configura to use this STS in the service
wsdl.

onders
Offline
Joined: 2008-03-15

>Can you treat the WCF STS the same way as the Metro STS?

Actually, I wonder whether i can do or not!
p.s: I have no background in .net and WCF.

I have a sample code implementing STS functionality in .Net and providing the WSDL document which i sent in my previous post.

>Cretae a reference to it and configure the security. Configura to use this STS in the service wsdl.

Yes, i create the reference to that .net STS in client application in netbeans. But wsimport tool gives the warnings in my previous post and does not generate the client side artifacts according to the wsdl properly, in my opinion, considering the Java-Web service client side artifact creation by wsimport. I am not exactly sure. I just wonder at this point, do these warnings prevents my communication with .Net STS?

If yes, how can i get over this situation?

Thanks.

jdg6688
Offline
Joined: 2005-11-02

> wsimport. I am not exactly sure. I just wonder at
> this point, do these warnings prevents my
> communication with .Net STS?

No. The messages between the client and STS are defined in the spec. So don't worry
about the WSDL and the warning. Just configure the security of the refence to the STS and proceed as for a Metro STS.

Thanks!

>
> If yes, how can i get over this situation?
>
> Thanks.