You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Don Brown (JIRA)" <ji...@apache.org> on 2008/04/20 05:52:05 UTC

[jira] Resolved: (WW-1550) XSLT Result matchingPattern and excludingPattern missing

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

Don Brown resolved WW-1550.
---------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.1.x)
                   2.1.2
         Assignee: Don Brown

Since the parameters didn't do anything, I deprecated the accessors and removed them from the docs.  Feel free to open a new feature ticket to add them back.

> XSLT Result matchingPattern and excludingPattern missing
> --------------------------------------------------------
>
>                 Key: WW-1550
>                 URL: https://issues.apache.org/struts/browse/WW-1550
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Plugin - Tags
>    Affects Versions: 2.0.1
>            Reporter: David H. DeWolf
>            Assignee: Don Brown
>             Fix For: 2.1.2
>
>
> The xslt result is documented to have matchingPattern and excludingPattern properties which allow elements of the object graph to be excluded from the resulting DOM.   This were removed (inadvertently?) in revision 423995.  This can be troublesome when used in conjunction with the spring plugin - especially when the action is injected with a DAO, or something that can contain quite a large graph.  In one example, an entire jdbc driver was being interrogated.

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