Custom pipeline component properties values reset when setting one of them in the admin console

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Custom pipeline component properties values reset when setting one of them in the admin console

Viewing 2 reply threads
  • Author
    Posts
    • August 12, 2008 at 12:09 PM #20395
      community-content

        Hi all

        I have written a pipeline component to which I set the properties at design-time in a custom pipeline. Once deployed, if I change one of the properties from the Administration Console, the remaining properties have their values reset to nothing, although they seem to be set in the pipeline’s property page?

        Is there a way to prevent this?

        Thank you. 

      • August 12, 2008 at 8:17 PM #20397
        community-content

          If you just want to set default values for the pipeline component properties then you can set them directly in the pipeline component code.  However, if you want to add the component into multiple pipelines and set different default values, then I don’t know if that works so well….

        • August 13, 2008 at 6:23 AM #20404
          community-content

            Have you tried checking how your pipeline component loads its properties in its IPersistPropertyBag implementation? From what I remember, the XML that gets saved by the management console in the port/location configuration only contains the values for the properties that differ from the original pipeline definition, so it might be that it works by calling IPersistPropertyBag twice (one for the pipeline XML, one for the custom configuration XML).

        • Author
          Posts
        Viewing 2 reply threads
        • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.