Drop a comment if this article helped you to solve your problem
Thursday, 19 May 2011
Monday, 16 May 2011
Cshap Transform embedded XSLT from Resource .resx and convert to Class/Object
Thursday, 28 April 2011
LINQ Group By Query - Cannot implicitly convert System.Collections.Generic.List
Cannot implicitly convert type 'System.Collections.Generic.List
My method looks like below which is throwing an error

The Fix is very simple , Add Class before writing new list.

You can reach me @ raj.webjunky@yahoo.com
Wednesday, 23 March 2011
BizTalk ESB UDDI Resolver /Static Resolver WCF-BasicHttp Adapter - ContractFilter mismatch
The message with Action 'http://ExternalWCFSErvice/ManagementService/IdentiyService' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None)
In general Static resolver has Action Property Field to fill the action value for wcf service. However this has not been recognised by ESB and thrown an error below.
Fault Response
Fix is very simpley, Instead of writing Action value at action property filed, write at EndpointConfiguration.

Drop a comment if this article helped you to solve your problem
You can reach me @ raj.webjunky@yahoo.com
Wednesday, 9 March 2011
UDDI3 TestResolver Configuration Error
I have been observing many guys facing the issue while working with UDDI resolver. One of the common error was mentioned below. This error is very generic error and it does not provide any clue for whare to fix. Hope this article might be helpful to resolve this issue quickly.
Error 1 Could not connect to service 'http://localhost/ESB.ResolverServices.WCF/ResolverService.svc' with configuration data 'UDDI3:\\searchQualifiers=andAllKeys;categorySearch=;bindingKey=uddi:esb:GetMasterOrderTransofrms;serviceKey=;'. Error message = An unexpected error occurred attempting to Resolve.Error ID = 5c17d526-d4d5-4ba3-a20f-14ecfb95366aNOTE: Alternatively you can check the Application Event log for the Error ID and on the other hand also check for the current resolver type entry in esb.config file or verify if the configuration data is correct.
Solution:
All you need to is
Open your UDDI Configuration Binding Instance and add 2 custom categories like
1. BizTalk Application 2. Transport Type.
now test your UDDI Resolver , Hope you will not get above error.
Enjoy ESB::-)
You can reach me @ raj.webjunky@yahoo.com
Friday, 21 January 2011
Schema referenced by Map has been deleted. BizTalk Server group configuration is out of date
While doing a Development with Oracle Extracted Schemas my Visual Studio 2010 fired an below error when I tried to deploy my solution.
Schema referenced by Map "mapOrders" has been deleted. The local, cached version of the BizTalk Server group configuration is out of date. You must refresh the BizTalk Server group configuration before making further changes.
I tried
1.refreshing the BizTalk Group - No Luck
2.Close Visual Studio and BizTalk Admin Console - No use
3.Restarted SQL Service - No Use
I still facing same error.
Finally I removed an Entry at BizTalk management Datbase and it worked.
First Check your BizTalk Object name in bt_mapSpec Table
Select * from bt_mapspec
Delete an entry from bt_mapSpec table.
Delete from bt_mapspec Where itemid=
Drop a comment if this article helped you to solve your problem
You can reach me @ raj.webjunky@yahoo.com
Friday, 14 January 2011
ESB Remove ,Add Namespace Pipeline Components usage-Restful Service
ESB Remove ,Add Namespace Pipeline Components usage -Restful Service
This is an simple example for "How use Remove and Namespace of ESB Pipeline Components"
I received a message from Restful service which is a string format.
I tried to assign this message into predefined XSD structure on my ESB Offramp Receive.
However I endupt with different errors.
After a good amount of study in ESB pipeline ComponentsI found the best way to achive this is utilize existing Remove namespace and add namespace components.
My Restful response message
My Predefined output message Structure
Create Custom pipeline and add Components as mentioned below
Name : ReceivePipeline
Decode : ESB RemoveNamespace
Decode : ESB Add Namespace
Decode :ESB Itinerary Cache
Disassemble : XML Disassembler
ResolveParty : ESB Dispatcher
ESB Add Namespace Component Configuration properties
ExtractionNodeXpath = /string
NameSpaceBase =http://TestOrder.Schemas.RestResponse
NamespacePrefix =ns9 ( do not enter from ns0 to ns6)
Refere further details of add Namespacehttp://msdn.microsoft.com/en-us/library/ff649945.aspx
Drop a comment if this article helped you to solve your problem
You can reach me @ Raj.webjunky@yahoo.com
