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

Guillaume Nodet commented on SM-1204:
-------------------------------------

Usually, the way to create a good patch is the following:
   * check out the sources using svn
   * modify the sources as needed
   * svn add all the new files
   * use svn diff to create a patch
   
For junit, there are already some tests in the component that you can look at.  
There is no real guide, but looking at the existing is usually a good way to 
learn. 

> 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.

Reply via email to