| Author |
Writing FileNames with Custom Pipeline
|
|
|
| Hi,
I have 2 different schemas with two properties i would like to read from.
If its type A then append "A" to the output filename if type B append "B" to
the filename. i have tried using a dynamic send port with a custom pipeline
but cannot get it to work.
Any help is much appreciated
| |
| dickdijkstra@hotmail.com 2005-09-12, 6:06 pm |
| You don't have to use a custom pipeline component to do the trick. You
can create a decide-shape in your orchestration that determines whether
your filetype is A or B. Then drag a send shape on each branch of your
decide shape, that connect to one dynamic send port. You can set the
filename programatically using an expression shape.
Use something like this: MyPort(Microsoft.XLANGs.BaseTypes.Address) =
"c:\\fileA.txt" for the expression shape at branch 1 and
MyPort(Microsoft.XLANGs.BaseTypes.Address) = "c:\\fileB.txt" for the
expression shape at branch 2.
| |
|
| Thanks! will try it out.
How do I work out what type of file it is, seeing that the schemas are
slightly differently?
"dickdijkstra@hotmail.com" wrote:
> You don't have to use a custom pipeline component to do the trick. You
> can create a decide-shape in your orchestration that determines whether
> your filetype is A or B. Then drag a send shape on each branch of your
> decide shape, that connect to one dynamic send port. You can set the
> filename programatically using an expression shape.
>
> Use something like this: MyPort(Microsoft.XLANGs.BaseTypes.Address) =
> "c:\\fileA.txt" for the expression shape at branch 1 and
> MyPort(Microsoft.XLANGs.BaseTypes.Address) = "c:\\fileB.txt" for the
> expression shape at branch 2.
>
>
| |
| Dick Dijkstra 2005-09-20, 7:48 am |
| Hi JP,
You can use "BTS.MessageType" to find out what message you are dealing
with. So, on the left branch, the expression should be:
BTS.MessageType = "targetnamespace#rootnode"
Dick Dijkstra (www.dickdijkstra.com)
| |
|
| Thanks!!
"dickdijkstra@hotmail.com" wrote:
> You don't have to use a custom pipeline component to do the trick. You
> can create a decide-shape in your orchestration that determines whether
> your filetype is A or B. Then drag a send shape on each branch of your
> decide shape, that connect to one dynamic send port. You can set the
> filename programatically using an expression shape.
>
> Use something like this: MyPort(Microsoft.XLANGs.BaseTypes.Address) =
> "c:\\fileA.txt" for the expression shape at branch 1 and
> MyPort(Microsoft.XLANGs.BaseTypes.Address) = "c:\\fileB.txt" for the
> expression shape at branch 2.
>
>
|
|
|
|