[jira] Commented: (SM-1204) add jbi extension support in saxon component

["Kevin kalmbach (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/SM-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41206#action_41206 ] 

Kevin kalmbach commented on SM-1204:
------------------------------------

All of the files in the zip are new files (nothing to diff against).  Do I
need to do anything for that?

For changes I want in the XsltEndpoints, I will add in the svn diffs (not
sure when I will get around to it, hopefully next week).

For the ASF header, is there a template for that (or just copy it from
anywhere)?.  Do I need to add that in myself or can I just giver permission
for someone else to add it in?.

For the junit, I'm not sure how to write one that goes against an endpoint.
Do you have any tutorials/etc for writing a junit test case against a
servicemix component?

(In case you can't tell) I'm new to this submitting stuff, so if these are
dumb questions, forgive me.
-Kevin






> add jbi extension support in saxon component
> --------------------------------------------
>
>                 Key: SM-1204
>                 URL: https://issues.apache.org/activemq/browse/SM-1204
>             Project: ServiceMix
>          Issue Type: Improvement
>          Components: servicemix-saxon
>    Affects Versions: 3.2.1
>         Environment: all
>            Reporter: Kevin kalmbach
>         Attachments: saxon.zip
>
>   Original Estimate: 2 days
>  Remaining Estimate: 2 days
>
> In the lw container there were jbi extensions for xalan xsl transformations.
> We would like this functionality reproduced in the Saxon transformers.
> I attached all new files.
> The only change to xsl files is that in the header, there needs to be this line.. (indicating the class for the extensions).
> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
> 	xmlns:jbi="saxon://org.apache.servicemix.saxon.JBIExtension"
>         extension-element-prefixes="jbi"
> >
> Also in XsltEndpoint.java (Both in saxon and xalan), at the bottom of the file, there are sets for in, exchange and component.
> out needs to be set here as well (This looks like an old bug even from the xalan days).  This is needed for setProperties and copyOut.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.