Skip to end of metadata
Go to start of metadata

Do you allow your developers to mess up the message?

  • Exploring three different technologies in message driven architecture.
  • Based on three "strong" brand Glassfish ESB, BEA Weblogic and OSWorkflow/Active Mq Combo.

How do you avoid that future development diverges from the design you intended?

  • Ensure that the natural choice is the right choice.
  • Ensure that you spend your time on development, not on "hancking" testabillity.

Example of moving from "untestable" to automatic testing of Glassfish ESB.

  1. Stub your endpoints
  2. Script your unit tests, automatic on CI server.
  3. Dissect Glassfish ESB libs. Find bare minmum code needed for running test out of container.
  4. Finally: Unit test Workflow and Sub-flows.

Presentation

You need flash player installed to preview ppt and pdf files

Get Adobe Flash player

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. May 05, 2011

    GF ESB gir pek-og-klikk, det gir ikke OSWorkflow+ActiveMQ.
    GF ESN gir deg god støtte for ulike endepunkter. God på transformering.

    Foredrag på Roots 2011 om hvordan få GF ESB testbar.

    BEA Weblogic: EJB-tilnærming

    Litt samme syndrom som ESB -> stor klump med mye logikk, all ordrefunksjonalitet inni produktet.
    Testing avhenger av å se resultater senere i kjeden. "tungt" å teste.
    Interfacer ikke tilpasset ulike klienter.

  2. May 05, 2011

    Q: Hvordan kan man som innkjøper sette krav om testbarhet til et produkt?
    A: Kreve at subflows skal kunne tests ouf-of-container.

    Shiraz kommenterer at det finnes egne verktøy for å teste Biztalk direkte fra VS. BizUnit.