Mindblown: a blog about philosophy.

Scenario is I am to copy my file based configuration to the BizTalk installation folder (reason being in runtime I can access the registry to get the path without touching the BizTalk configuration) I am using BTDF, cannot find an existing implementation to do this. So I added the following section to BTDF msbuild target…

The bus, is definitely definitely a popular word now. If you want to show off, told them you build ‘the bus’. What is it and its relationship to ESB toolkit, in my opinion, is totally not related. The messaging bus is nothing more than a design pattern concept. It does not mean you have to…

On current project, we chose the business rules engine called inRule. The product itself, compared to the BizTalk one, is very interesting, in my two days of learning, compared to BizTalk Rules Engine, it provides enhancements on a much much much more fancy environment for creating the rules, being the irAuthor, word plugin, visual studio…

This is interesting,  

Had this problem before, the CForwardOnlyEventingReadStream instance returned from pipeline component does not fire the Read event. After checking Microsoft’s implementation, it turns out my custom stream object has to implement the Position property. After update my custom stream class to return a valid position, the read event is working again.

  BizTalk deciding if a receive location has transaction support BizTalk deciding which contract to call So, all these said, request-response transaction is not supported. To ensure BizTalk create the inbound transaction, the port must have TransactionFlowBinding element attached.

Have to write a disassembler component to wrap flat file disassembler to disassemble incoming SAP flat file then validate the disassembled XML upon BRE, if validated then promote some properties dynamically and pump individual validated messages to the output stream. I followed the standard template, using a Queue instance to hold the output messages in…

So it took me almost three hours to find out why my pipeline component does not work correctly in the design time. It turns out its constructor has problem while initialize the enterprise library due to the ESB 2.1 installation. The problem is easy to fix but hard to discover, just a note.

So I refactored the bizunit a bit to allow for the following test step, source code I really like the NUnit.That asserts, look much comfortable compared to the old ones

These are lesson learnt, scope to set to synchronized once the delivery notification occurs, it seems the orchestration continues its workflow, but it did trigger the exception handler block later if suspend the orchestration after delivery failure, use an orchestration instead of send port to handle the failed routing message, this is based on thread.…