[ http://nagoya.apache.org/jira/browse/XALANJ-838?page=history ]

Henry Zongaro updated XALANJ-838:
---------------------------------

      Assign To:     (was: Xalan Developers Mailing List)
           type: New Feature  (was: Bug)
    Description: 
When using XSLT I am calling my own Java extension code to return an String 
which is actually nodes to insert into the result DOM (Very nasty  - I know!). 

This works fine when using Xalan 2.2.0 or Saxon 6.5 as the String is converted 
automagically into nodes in my DOM strucuture. When using XSLTC however, the 
result from the Java extension is created as a text node with all the correct 
entity mappings (i.e. < changes to &lt; etc).

I guess this is a bug in XSLTC as the other two support such features.

Cheers,

Tim Elcott

  was:
When using XSLT I am calling my own Java extension code to return an String 
which is actually nodes to insert into the result DOM (Very nasty  - I know!). 

This works fine when using Xalan 2.2.0 or Saxon 6.5 as the String is converted 
automagically into nodes in my DOM strucuture. When using XSLTC however, the 
result from the Java extension is created as a text node with all the correct 
entity mappings (i.e. < changes to &lt; etc).

I guess this is a bug in XSLTC as the other two support such features.

Cheers,

Tim Elcott

    Environment: 
Operating System: Windows NT/2K
Platform: PC

  was:
Operating System: Windows NT/2K
Platform: PC

       Priority: Major
    Bugzilla Id:   (was: 6418)

> Java Extension class produces different results between Xalan and XSLTC
> -----------------------------------------------------------------------
>
>          Key: XALANJ-838
>          URL: http://nagoya.apache.org/jira/browse/XALANJ-838
>      Project: XalanJ2
>         Type: New Feature
>   Components: XSLTC
>     Versions: 2.2.0
>  Environment: Operating System: Windows NT/2K
> Platform: PC
>     Reporter: Tim D Elcott

>
> When using XSLT I am calling my own Java extension code to return an String 
> which is actually nodes to insert into the result DOM (Very nasty  - I 
> know!). 
> This works fine when using Xalan 2.2.0 or Saxon 6.5 as the String is 
> converted 
> automagically into nodes in my DOM strucuture. When using XSLTC however, the 
> result from the Java extension is created as a text node with all the correct 
> entity mappings (i.e. < changes to &lt; etc).
> I guess this is a bug in XSLTC as the other two support such features.
> Cheers,
> Tim Elcott

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

Reply via email to