[ 
https://issues.apache.org/jira/browse/AXIS2-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508393
 ] 

Amila Chinthaka Suriarachchi commented on AXIS2-2749:
-----------------------------------------------------

the above exception is caused by the 'externalTemplate' variable used by some 
templates. Actually this variable sometimes may not be present. So hide an 
exception because of this is not a good approach.
I change the code to check this and acommadate your requriement. please see the 
patch and check it make your requirement. 

> Improved codegen XSLTIncludeResolver support for <xsl:include>
> --------------------------------------------------------------
>
>                 Key: AXIS2-2749
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2749
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Improvement
>          Components: codegen
>            Reporter: Peter Danielsen
>            Assignee: Amila Chinthaka Suriarachchi
>         Attachments: XSLTIncludeResolver.java.svn.diff, 
> XSLTIncludeResolver.patch.txt, XSLTIncludeResolverTest.java, 
> XSLTIncludeResolverTestTemplate.xsl
>
>
> I've been trying to create my own Axis2 codegen XSLT templates and would like 
> to factor out some common templates to a separate file that can be included 
> by others.  An example is a template that generates a method signature.  It 
> would be included in a template that generates an interface and in one that 
> generates an implementation class.
> The current URI resolver used by the AxisServiceBasedMultiLanguageEmitter, 
> XSLTIncludeResolver, requires the value of an <xsl:include>'s href attribute 
> to be a property that's in its CodeGenConfiguration object. It looks like the 
> only way to set the property is to write code. It would be preferable refer 
> to it directly in a template by setting the href to a value that can be 
> resolved by XSLTIncludeResolver using getResourceAsStream.  Such a change to 
> XSLTIncludeResolver will enable easier maintenance of the existing templates, 
> once refactored, and easier development of new templates since there won't be 
> multiple copies of the same code to update when something changes.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to