Hi Andy -
You alluded to this in your posting, but I think it's worth
mentioning. Each NotificationClass can have multiple delivery
protocols defined, but only one ContentFormatter.
In your case, a single NotificationClass can be used for multiple
device types and can use 3 or more different XSLT files to format the
notifications based on the different device types. But all must use
the XsltFormatter Content Formatter.
A single NotificationClass cannot use, for example, an XSLT transform
to format notifications for email and a custom content formatter to
format notifications for SMS.
HTH...
--
Joe Webb
SQL Server MVP
~~~
Get up to speed quickly with SQLNS
http://www.amazon.com/exec/obidos/tg/detail/-/0972688811 I support PASS, the Professional Association for SQL Server.
(
www.sqlpass.org)
--
Joe Webb
SQL Server MVP
~~~
Get up to speed quickly with SQLNS
http://www.amazon.com/exec/obidos/tg/detail/-/0972688811 I support PASS, the Professional Association for SQL Server.
(
www.sqlpass.org)
On Wed, 20 Jul 2005 04:38:02 -0700, "andyjax"
[quoted text, click to view] <andyjax@newsgroup.nospam> wrote:
>Thanks. I did not spend much time in the book there, but for those who have
>the book p 368 -370. There is so much info in the book and is sometimes hard
>to remember where I read something.
>
>This group is great!
>
>"kate" wrote:
>
>> You can specify a different xslt template for each device type. This is
>> well explained in Shyam's book. To summarise, in the base directory
>> folder where the default xslt is placed. If you create sub-folders
>> whose names match the device type names, the xslt from the relevant
>> folder will be used in preference to the default one. eg. a sub folder
>> called SMS would contain the message formatting for the SMS device
>> type.
>>
>> you can also subdivide by language locale as well.
>>
>> hope that helps
>>
>> Kate MBCS
>>
>> Alert Technologies
>>
http://www.alert-technologies.co.uk >> Get your notification services implementation going in minutes not
>> weeks ......
>>
>>
