We are utilizing Unix version 10 of webMethods and I had a quick question about XSLT.
In our environment, we have different xslt services within our packages, but every time there’s a slight modication needed for the xslt, this puts us through a lot of paperwork on our end in order to make a production change. We would not have to be concerned about this if the XSLT lived like within a unix file directory or within a database. If the XSLT lived there, instead of within the webMethods package, things are much more flexible over here when it comes to modifications.
Anyone aware or currently doing what I’m asking about? If an external XSLT is built, could the XSLT perhaps live elsewhere like in a file directory or database and be pulled/imported into the flow code to do the transformation, versus having to create and rely on the xslt service built in Designer? Trying to see if this is even possible
Thanks.