How to configure WCF to work with JAX-WS client?

How to configure WCF to work with JAX-WS client?

Old forum URL:

joseph99 posted on Monday, October 01, 2012

We are using CSLA 3.6.2 with WCF.  I am not having any issues with Microsoft clients connecting to the service using the configuration from the Expert C# 2008 Business Objects book.  However, I cannot find anything on how to set up the WCF configuration for a JAX-WS client.  How can the WCF be configured to allow a JAX-WS client consume the web service and maintain the authentication? 

I am not an open source developer, but the issue the open source developer is having relates to the negotiateServiceCredential being set to true.



JonnyBee replied on Tuesday, October 02, 2012

If you are using the CSLA DataPortal for N-tier deployment you will NOT be able to use the CSLA DataPortal from a JAX-WS client.
CSLA only uses WCF as a transport mechanism - the actual payload is from a binary .NET serializer and cannot be used by a java client.

So your best option is to create a separate WCF Service with message contracts to expose those objects and actions that an external app may use. The recommandation is to create new message contract objects and map values to/from your CSLA business objects in order to reuse the logic. 

joseph99 replied on Tuesday, October 02, 2012

I have separate WCF classes that are filled using the CSLA business objects.  The area where I am having an issue the the custom authentication the CLSA uses.  I have not been able to find a work around.  Thanks for the help.


RockfordLhotka replied on Tuesday, October 02, 2012

Their SOAP service client API needs to support the right WS-* specs to interact with a service like that.

I don't know anything about that specific technology, but I do know that relatively few client stacks fully support WS-* because it is really hard to get right, so it wouldn't surprise me if they can't handle it.

You might need to switch to a basicHttp binding and use a less sophisticated authentication model.

Copyright (c) Marimer LLC