[jira] Updated: (AXIS2-2749) Improved codegen XSLTIncludeResolver support for

["Peter Danielsen (JIRA)" <ji...@apache.org>]

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

Peter Danielsen updated AXIS2-2749:
-----------------------------------

    Attachment: XSLTIncludeResolverTestTemplate.xsl
                XSLTIncludeResolverTest.java
                XSLTIncludeResolver.patch.txt

There are three files attached:
1. XSLTIncludeResolver.patch.txt - a patch containing an implementation of a solution.
2. XSLTIncludeResolverTest.java - a JUnit test for XSLTIncludeResolver once the patch is applied.
3. XSLTIncludeResolverTestTemplate.xsl - a template to be used by XSLTIncludeResolverTest.  It should be placed in tests/org/apache/axis2/wsdl/util/resources (a new directory)

I've run the test successfully in my own ant environment.  I'm unfamiliar with maven, so I didn't modify the codegen maven files.  It looks like a change will be needed there so that the template will be found on the classpath at test run-time.

> 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
>         Attachments: 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org