axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amila Chinthaka Suriarachchi (JIRA)" <>
Subject [jira] Commented: (AXIS2-2749) Improved codegen XSLTIncludeResolver support for <xsl:include>
Date Wed, 20 Jun 2007 19:18:25 GMT


Amila Chinthaka Suriarachchi commented on AXIS2-2749:

sorry for late reply.

Are you suggesting something like this. 
currently we have used the href parameter as follows.
<xsl:include href="databindsupporter"/>
and you want to use it in 
<xsl:include href="org.apache.axis2.schema.template.ADBDatabindingTemplate.xsl"/>
like this.

Here the problem is the template we want have to use is known only at runtime. it depends
on the databinding use. 

On the other hand we can add that feature too if someone needs. 

if I appling your patch is it enogh to add only the XSLTIncludeResolver.patch.txt? does it
make any problem to the existing template processing system? This template processing code
was there from a long time and it worked properly. 

> Improved codegen XSLTIncludeResolver support for <xsl:include>
> --------------------------------------------------------------
>                 Key: AXIS2-2749
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Improvement
>          Components: codegen
>            Reporter: Peter Danielsen
>            Assignee: Amila Chinthaka Suriarachchi
>         Attachments: XSLTIncludeResolver.patch.txt,, 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

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:
For additional commands, e-mail:

View raw message