Schweter, Ryan wrote:
Yeah, I noticed that the class adds headers before I sent the email out. I am using release 1.0, which has the header logic in it. I am adding the property via an XSLT router. Here's a snippet:<jbi:invoke service="bwnet:dest"> <jbi:setOutProperty name="MyHeader" select="string(//@router-id)" /> <xsl:copy-of select="."/> </jbi:invoke> If I invoke the "Script" service, as in the online example, it does output my property as a member of the property collection.
Cool.
Does anyone have a working example that adds an HTTP header (preferably from an XSLT router)?
So are you saying if the 'bwnet:dest' component is a HttpInvoker component, your 'MyHeader' header does not appear in XSLT?
BTW the HttpInvoker (the client side HTTP invocation component) uses the HttpClientMarshaler class to append headers to the HTTP client invocation - again currently filtering via the headers which are of type String.
-- James ------- http://radio.weblogs.com/0112098/
