You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "David H. DeWolf (JIRA)" <ji...@apache.org> on 2006/12/08 15:23:57 UTC
[jira] Created: (WW-1550) XSLT Result matchingPattern and
excludingPattern missing
XSLT Result matchingPattern and excludingPattern missing
--------------------------------------------------------
Key: WW-1550
URL: http://issues.apache.org/struts/browse/WW-1550
Project: Struts 2
Issue Type: Bug
Components: Views
Affects Versions: 2.0.1
Reporter: David H. DeWolf
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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (WW-1550) XSLT Result matchingPattern and
excludingPattern missing
Posted by "Don Brown (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/WW-1550?page=all ]
Don Brown updated WW-1550:
--------------------------
The old version relied on internal sun classes, clearly a no-no for a portable framework. The filtering was performed by the internal DOMAdapter class, and I can't find any public api that accomplishes the same purpose. Therefore, filtering will probably have to be implemented from scratch. I'm moving this to 2.0.3 and will comment out those parameters.
> XSLT Result matchingPattern and excludingPattern missing
> --------------------------------------------------------
>
> Key: WW-1550
> URL: http://issues.apache.org/struts/browse/WW-1550
> Project: Struts 2
> Issue Type: Bug
> Components: Views
> Affects Versions: 2.0.1
> Reporter: David H. DeWolf
> Fix For: 2.0.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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (WW-1550) XSLT Result matchingPattern and
excludingPattern missing
Posted by "Don Brown (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/WW-1550?page=all ]
Don Brown updated WW-1550:
--------------------------
Fix Version/s: 2.0.3
(was: 2.0.2)
> XSLT Result matchingPattern and excludingPattern missing
> --------------------------------------------------------
>
> Key: WW-1550
> URL: http://issues.apache.org/struts/browse/WW-1550
> Project: Struts 2
> Issue Type: Bug
> Components: Views
> Affects Versions: 2.0.1
> Reporter: David H. DeWolf
> Fix For: 2.0.3
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (WW-1550) XSLT Result matchingPattern and
excludingPattern missing
Posted by "Don Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Don Brown updated WW-1550:
--------------------------
Fix Version/s: (was: 2.0.3)
2.0.x
> 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: Views
> Affects Versions: 2.0.1
> Reporter: David H. DeWolf
> Fix For: 2.0.x
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (WW-1550) XSLT Result matchingPattern and
excludingPattern missing
Posted by "Ted Husted (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/WW-1550?page=all ]
Ted Husted updated WW-1550:
---------------------------
Fix Version/s: 2.0.2
> XSLT Result matchingPattern and excludingPattern missing
> --------------------------------------------------------
>
> Key: WW-1550
> URL: http://issues.apache.org/struts/browse/WW-1550
> Project: Struts 2
> Issue Type: Bug
> Components: Views
> Affects Versions: 2.0.1
> Reporter: David H. DeWolf
> Fix For: 2.0.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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (WW-1550) XSLT Result matchingPattern and
excludingPattern missing
Posted by "Ted Husted (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Husted updated WW-1550:
---------------------------
Fix Version/s: (was: 2.0.x)
2.1.x
Bumping issues to 2.1.x, except those that involve backward-compatability with Struts 1 or WebWork 2.
> 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: Views
> Affects Versions: 2.0.1
> Reporter: David H. DeWolf
> Fix For: 2.1.x
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (WW-1550) XSLT Result matchingPattern and
excludingPattern missing
Posted by "Don Brown (JIRA)" <ji...@apache.org>.
[ 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.