|
Home > Archive > BizTalk Server General > December 2004 > Using Custom XSLT in Message Construction Shape
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Using Custom XSLT in Message Construction Shape
|
|
| cneuwirt 2004-12-02, 7:50 am |
| I have a custom XSLT document that I would like to use in the Transform step
of Message Construction Shape. Is the possible without having to do this
programatically within the Construction Shape. Anotherwords, I would like it
to behave just as if I used a map.
thanks,
craig
| |
|
|
| Greg Forsythe 2004-12-02, 5:48 pm |
| There are limitiations in Matts technique, the mapper generates wrapping
XSLT i.e the root node and 2 <xsl:template> nodes, but probably the biggest
limitation is the size of the edit window 
If your XSLT is self contained, there is an better way.
Add the XSLT document to your project.
Create a map - specify the input and output schemas
Click on the grid.
Go to the properties window and set the "Custom XSLT Path" to the relative
file name of your XSLT
i.e. ./MyXSLTFile.xslt.
You can edit the XSLT in a sizeable, syntax-colored window and you can still
validate and test the map
The created map can be used in a Transform shape or in a send /receive
pipeline
Check out this example which has an 800 line XSLT file. I would have gone
postal if I had had to edit this inside a functoid.
http://www.gotdotnet.com/Community/...23-fe72f317891a
Greg
"Matt Meleski" <MattMeleski@discussions.microsoft.com> wrote in message
news:16B29E66-31BE-4C62-8495-6E6B621964ED@microsoft.com...
> Craig,
>
> Place your custom XSLT in a Scripting
> Functoid in a map , Some examples are :
>
>
http://msdn.microsoft.com/library/d...ltools_eprq.asp[vbcol=seagreen]
>
> http://objectsharp.com/Blogs/matt/a...11/24/1031.aspx
> http://dotnetjunkies.com/WebLog/jly...7/13/19240.aspx
>
> Matt.
>
> "cneuwirt" wrote:
>
step[vbcol=seagreen]
this[vbcol=seagreen]
like it[vbcol=seagreen]
| |
| Bob Corcoran 2004-12-03, 5:52 pm |
| I would add that if one is a competent XSLT developer, it is always better to
use 'Custom XSLT'. I mean, why waste your time trying to figure out the
functoids, since it all ends up being XSLT in the end anyway? And, if you
roll your own, it's portable.
"Greg Forsythe" wrote:
> There are limitiations in Matts technique, the mapper generates wrapping
> XSLT i.e the root node and 2 <xsl:template> nodes, but probably the biggest
> limitation is the size of the edit window
>
> If your XSLT is self contained, there is an better way.
> Add the XSLT document to your project.
> Create a map - specify the input and output schemas
> Click on the grid.
> Go to the properties window and set the "Custom XSLT Path" to the relative
> file name of your XSLT
> i.e. ./MyXSLTFile.xslt.
>
> You can edit the XSLT in a sizeable, syntax-colored window and you can still
> validate and test the map
>
> The created map can be used in a Transform shape or in a send /receive
> pipeline
>
> Check out this example which has an 800 line XSLT file. I would have gone
> postal if I had had to edit this inside a functoid.
> http://www.gotdotnet.com/Community/...23-fe72f317891a
>
> Greg
>
> "Matt Meleski" <MattMeleski@discussions.microsoft.com> wrote in message
> news:16B29E66-31BE-4C62-8495-6E6B621964ED@microsoft.com...
> http://msdn.microsoft.com/library/d...ltools_eprq.asp
> step
> this
> like it
>
>
>
|
|
|
|
|