|
|
|
1-10 of 20
< Previous Next >
|
The Codegenerator does not take the available AttributeValues of the ServiceContract Interface.
For example I have an Interface:
[ServiceContract(Namespace = "http://TO.Test.ServiceContracts/2...
id# 3235 | Planned Release: None | Last Updated: Sep 3 2007 at 4:28 PM
by peroxide20
curently the implementation of the service cotnrat has the name <workflowTypeName>_wcfContractImpl
This name should be made configurable on the workflow. Same as the ServiceName and Namespace prope...
id# 2328 | Planned Release: WCF activities 1.01 | Last Updated: Jun 26 2007 at 9:28 PM
by vriesmarcel
based on the question posed in the discussion, add a behaviour that fixes the problem of the code being generated that handles the call.
Solution is IEndpointBehaviour that binds appdomain typere...
id# 2560 | Planned Release: None | Last Updated: Jun 22 2007 at 9:00 PM
by vriesmarcel
In able to add additional attributes to the generated WCF contract, extend the baseactivity of all workflows (StateMachine and all derived + Sequential and all derived) to have at least the Uri pro...
id# 1915 | Planned Release: WCF activities 1.0 | Last Updated: May 8 2007 at 9:15 PM
by vriesmarcel
THe WCF activity will throw an Index Out of Bonds exception when running in a high load scenario
id# 1737 | Planned Release: WCF activities 1.0 | Last Updated: May 8 2007 at 9:15 PM
by vriesmarcel
Retrurn the workflow id as a message header, so there is no requirement of a initiating call that returns the workflowID
id# 902 | Planned Release: WCF activities 1.0 | Last Updated: May 8 2007 at 9:15 PM
by vriesmarcel
Current implementatin always returns on void return type, but should wait so an execption can be returned when stufff goes wrong
id# 901 | Planned Release: WCF activities 1.0 | Last Updated: May 8 2007 at 9:15 PM
by vriesmarcel
|
|
1-10 of 20
< Previous 1 2 Next >
|
|
|
|
|
|
|