[JBoss JIRA] Created: (RF-4351) rich:tree ampersand is sometimes not escaped properly causing parse error
3:35 a.m.
rich:tree ampersand is sometimes not escaped properly causing parse error
-------------------------------------------------------------------------
Key: RF-4351
URL: https://jira.jboss.org/jira/browse/RF-4351
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.1
Environment: Seam 2.0.1.GA, Facelets 1.1.14, jsf mojarra 1.2_07-b03-FCS
Reporter: Mikael
Hi
My nodes in my tree may contain ampersand and other crazy German characters.
Currently I'm getting an XML parse error pointing to the ampersand.
Had a look at the generated source and discovered that the node content is used as part of
the element id. Mostly the ampersand is escaped properly but in at least one place it
isn't which is causing a parse error on the client side.
Using the NEKO parser.
The forum link contains more information, especially the a4j log.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:22 p.m.
New subject: [JBoss JIRA] Updated: (RF-4351) rich:tree ampersand is sometimes not escaped properly causing parse error
[
https://jira.jboss.org/jira/browse/RF-4351?page=com.atlassian.jira.plugin...
]
Nick Belaevski updated RF-4351:
-------------------------------
Fix Version/s: Future
Assignee: Nick Belaevski
rich:tree ampersand is sometimes not escaped properly causing parse
error
-------------------------------------------------------------------------
Key: RF-4351
URL: https://jira.jboss.org/jira/browse/RF-4351
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.1
Environment: Seam 2.0.1.GA, Facelets 1.1.14, jsf mojarra 1.2_07-b03-FCS
Reporter: Mikael
Assignee: Nick Belaevski
Fix For: Future
Hi
My nodes in my tree may contain ampersand and other crazy German characters.
Currently I'm getting an XML parse error pointing to the ampersand.
Had a look at the generated source and discovered that the node content is used as part
of the element id. Mostly the ampersand is escaped properly but in at least one place it
isn't which is causing a parse error on the client side.
Using the NEKO parser.
The forum link contains more information, especially the a4j log.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:38 p.m.
New subject: [JBoss JIRA] Updated: (RF-4351) rich:tree ampersand is sometimes not escaped properly causing parse error
[
https://jira.jboss.org/jira/browse/RF-4351?page=com.atlassian.jira.plugin...
]
Nick Belaevski updated RF-4351:
-------------------------------
Fix Version/s: 3.3.1
(was: Future)
rich:tree ampersand is sometimes not escaped properly causing parse
error
-------------------------------------------------------------------------
Key: RF-4351
URL: https://jira.jboss.org/jira/browse/RF-4351
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.1
Environment: Seam 2.0.1.GA, Facelets 1.1.14, jsf mojarra 1.2_07-b03-FCS
Reporter: Mikael
Assignee: Nick Belaevski
Fix For: 3.3.1
Hi
My nodes in my tree may contain ampersand and other crazy German characters.
Currently I'm getting an XML parse error pointing to the ampersand.
Had a look at the generated source and discovered that the node content is used as part
of the element id. Mostly the ampersand is escaped properly but in at least one place it
isn't which is causing a parse error on the client side.
Using the NEKO parser.
The forum link contains more information, especially the a4j log.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:30 a.m.
New subject: [JBoss JIRA] Work started: (RF-4351) rich:tree ampersand is sometimes not escaped properly causing parse error
[
https://jira.jboss.org/jira/browse/RF-4351?page=com.atlassian.jira.plugin...
]
Work on RF-4351 started by Nick Belaevski.
rich:tree ampersand is sometimes not escaped properly causing parse
error
-------------------------------------------------------------------------
Key: RF-4351
URL: https://jira.jboss.org/jira/browse/RF-4351
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.1
Environment: Seam 2.0.1.GA, Facelets 1.1.14, jsf mojarra 1.2_07-b03-FCS
Reporter: Mikael
Assignee: Nick Belaevski
Fix For: 3.3.1
Hi
My nodes in my tree may contain ampersand and other crazy German characters.
Currently I'm getting an XML parse error pointing to the ampersand.
Had a look at the generated source and discovered that the node content is used as part
of the element id. Mostly the ampersand is escaped properly but in at least one place it
isn't which is causing a parse error on the client side.
Using the NEKO parser.
The forum link contains more information, especially the a4j log.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:09 p.m.
New subject: [JBoss JIRA] Work stopped: (RF-4351) rich:tree ampersand is sometimes not escaped properly causing parse error
[
https://jira.jboss.org/jira/browse/RF-4351?page=com.atlassian.jira.plugin...
]
Work on RF-4351 stopped by Nick Belaevski.
rich:tree ampersand is sometimes not escaped properly causing parse
error
-------------------------------------------------------------------------
Key: RF-4351
URL: https://jira.jboss.org/jira/browse/RF-4351
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.1
Environment: Seam 2.0.1.GA, Facelets 1.1.14, jsf mojarra 1.2_07-b03-FCS
Reporter: Mikael
Assignee: Nick Belaevski
Fix For: 3.3.1
Hi
My nodes in my tree may contain ampersand and other crazy German characters.
Currently I'm getting an XML parse error pointing to the ampersand.
Had a look at the generated source and discovered that the node content is used as part
of the element id. Mostly the ampersand is escaped properly but in at least one place it
isn't which is causing a parse error on the client side.
Using the NEKO parser.
The forum link contains more information, especially the a4j log.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:54 a.m.
New subject: [JBoss JIRA] Work started: (RF-4351) rich:tree ampersand is sometimes not escaped properly causing parse error
[
https://jira.jboss.org/jira/browse/RF-4351?page=com.atlassian.jira.plugin...
]
Work on RF-4351 started by Nick Belaevski.
rich:tree ampersand is sometimes not escaped properly causing parse
error
-------------------------------------------------------------------------
Key: RF-4351
URL: https://jira.jboss.org/jira/browse/RF-4351
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.1
Environment: Seam 2.0.1.GA, Facelets 1.1.14, jsf mojarra 1.2_07-b03-FCS
Reporter: Mikael
Assignee: Nick Belaevski
Fix For: 3.3.1
Hi
My nodes in my tree may contain ampersand and other crazy German characters.
Currently I'm getting an XML parse error pointing to the ampersand.
Had a look at the generated source and discovered that the node content is used as part
of the element id. Mostly the ampersand is escaped properly but in at least one place it
isn't which is causing a parse error on the client side.
Using the NEKO parser.
The forum link contains more information, especially the a4j log.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:37 p.m.
New subject: [JBoss JIRA] Work stopped: (RF-4351) rich:tree ampersand is sometimes not escaped properly causing parse error
[
https://jira.jboss.org/jira/browse/RF-4351?page=com.atlassian.jira.plugin...
]
Work on RF-4351 stopped by Nick Belaevski.
rich:tree ampersand is sometimes not escaped properly causing parse
error
-------------------------------------------------------------------------
Key: RF-4351
URL: https://jira.jboss.org/jira/browse/RF-4351
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.1
Environment: Seam 2.0.1.GA, Facelets 1.1.14, jsf mojarra 1.2_07-b03-FCS
Reporter: Mikael
Assignee: Nick Belaevski
Fix For: 3.3.1
Hi
My nodes in my tree may contain ampersand and other crazy German characters.
Currently I'm getting an XML parse error pointing to the ampersand.
Had a look at the generated source and discovered that the node content is used as part
of the element id. Mostly the ampersand is escaped properly but in at least one place it
isn't which is causing a parse error on the client side.
Using the NEKO parser.
The forum link contains more information, especially the a4j log.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:10 p.m.
New subject: [JBoss JIRA] Updated: (RF-4351) rich:tree ampersand is sometimes not escaped properly causing parse error
[
https://jira.jboss.org/jira/browse/RF-4351?page=com.atlassian.jira.plugin...
]
Nick Belaevski updated RF-4351:
-------------------------------
Affects: [Documentation (Ref Guide, User Guide, etc.)]
rich:tree ampersand is sometimes not escaped properly causing parse
error
-------------------------------------------------------------------------
Key: RF-4351
URL: https://jira.jboss.org/jira/browse/RF-4351
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.1
Environment: Seam 2.0.1.GA, Facelets 1.1.14, jsf mojarra 1.2_07-b03-FCS
Reporter: Mikael
Assignee: Nick Belaevski
Fix For: 3.3.1
Hi
My nodes in my tree may contain ampersand and other crazy German characters.
Currently I'm getting an XML parse error pointing to the ampersand.
Had a look at the generated source and discovered that the node content is used as part
of the element id. Mostly the ampersand is escaped properly but in at least one place it
isn't which is causing a parse error on the client side.
Using the NEKO parser.
The forum link contains more information, especially the a4j log.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:12 p.m.
New subject: [JBoss JIRA] Commented: (RF-4351) rich:tree ampersand is sometimes not escaped properly causing parse error
[
https://jira.jboss.org/jira/browse/RF-4351?page=com.atlassian.jira.plugin...
]
Nick Belaevski commented on RF-4351:
------------------------------------
2Doc: "rowKeyConverter" attribute was unhidden
rich:tree ampersand is sometimes not escaped properly causing parse
error
-------------------------------------------------------------------------
Key: RF-4351
URL: https://jira.jboss.org/jira/browse/RF-4351
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.1
Environment: Seam 2.0.1.GA, Facelets 1.1.14, jsf mojarra 1.2_07-b03-FCS
Reporter: Mikael
Assignee: Nick Belaevski
Fix For: 3.3.1
Hi
My nodes in my tree may contain ampersand and other crazy German characters.
Currently I'm getting an XML parse error pointing to the ampersand.
Had a look at the generated source and discovered that the node content is used as part
of the element id. Mostly the ampersand is escaped properly but in at least one place it
isn't which is causing a parse error on the client side.
Using the NEKO parser.
The forum link contains more information, especially the a4j log.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:20 p.m.
New subject: [JBoss JIRA] Commented: (RF-4351) rich:tree ampersand is sometimes not escaped properly causing parse error
[
https://jira.jboss.org/jira/browse/RF-4351?page=com.atlassian.jira.plugin...
]
Nick Belaevski commented on RF-4351:
------------------------------------
2Doc: three bundled converters were added:
converterId = org.richfaces.TreeRowKeyConverter - for
org.richfaces.model.TreeNode<T> - based trees; key is assumed to be
java.lang.String
converterId = org.richfaces.TreeAdaptorRowKeyConverter - for adaptor-based trees; key is
assumed to be java.lang.String
converterId = org.richfaces.TreeAdaptorIntegerRowKeyConverter - for adaptor-based trees;
key is assumed to be java.lang.Integer; practically it is not necessary, but can serve as
example for implementing custom converters
rich:tree ampersand is sometimes not escaped properly causing parse
error
-------------------------------------------------------------------------
Key: RF-4351
URL: https://jira.jboss.org/jira/browse/RF-4351
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.1
Environment: Seam 2.0.1.GA, Facelets 1.1.14, jsf mojarra 1.2_07-b03-FCS
Reporter: Mikael
Assignee: Nick Belaevski
Fix For: 3.3.1
Hi
My nodes in my tree may contain ampersand and other crazy German characters.
Currently I'm getting an XML parse error pointing to the ampersand.
Had a look at the generated source and discovered that the node content is used as part
of the element id. Mostly the ampersand is escaped properly but in at least one place it
isn't which is causing a parse error on the client side.
Using the NEKO parser.
The forum link contains more information, especially the a4j log.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:20 p.m.
New subject: [JBoss JIRA] Commented: (RF-4351) rich:tree ampersand is sometimes not escaped properly causing parse error
[
https://jira.jboss.org/jira/browse/RF-4351?page=com.atlassian.jira.plugin...
]
Nick Belaevski commented on RF-4351:
------------------------------------
Examples of usage:
http://anonsvn.jboss.org/repos/richfaces/trunk/samples/tree-demo/src/main...
http://anonsvn.jboss.org/repos/richfaces/trunk/samples/treeModelDemo/src/...
rich:tree ampersand is sometimes not escaped properly causing parse
error
-------------------------------------------------------------------------
Key: RF-4351
URL: https://jira.jboss.org/jira/browse/RF-4351
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.1
Environment: Seam 2.0.1.GA, Facelets 1.1.14, jsf mojarra 1.2_07-b03-FCS
Reporter: Mikael
Assignee: Nick Belaevski
Fix For: 3.3.1
Hi
My nodes in my tree may contain ampersand and other crazy German characters.
Currently I'm getting an XML parse error pointing to the ampersand.
Had a look at the generated source and discovered that the node content is used as part
of the element id. Mostly the ampersand is escaped properly but in at least one place it
isn't which is causing a parse error on the client side.
Using the NEKO parser.
The forum link contains more information, especially the a4j log.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:24 p.m.
New subject: [JBoss JIRA] Resolved: (RF-4351) rich:tree ampersand is sometimes not escaped properly causing parse error
[
https://jira.jboss.org/jira/browse/RF-4351?page=com.atlassian.jira.plugin...
]
Nick Belaevski resolved RF-4351.
--------------------------------
Resolution: Done
Assignee: Tsikhon Kuprevich (was: Nick Belaevski)
Users should use one of newly-introduced converters or implement their own.
rich:tree ampersand is sometimes not escaped properly causing parse
error
-------------------------------------------------------------------------
Key: RF-4351
URL: https://jira.jboss.org/jira/browse/RF-4351
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.1
Environment: Seam 2.0.1.GA, Facelets 1.1.14, jsf mojarra 1.2_07-b03-FCS
Reporter: Mikael
Assignee: Tsikhon Kuprevich
Fix For: 3.3.1
Hi
My nodes in my tree may contain ampersand and other crazy German characters.
Currently I'm getting an XML parse error pointing to the ampersand.
Had a look at the generated source and discovered that the node content is used as part
of the element id. Mostly the ampersand is escaped properly but in at least one place it
isn't which is causing a parse error on the client side.
Using the NEKO parser.
The forum link contains more information, especially the a4j log.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:47 p.m.
New subject: [JBoss JIRA] Updated: (RF-4351) rich:tree ampersand is sometimes not escaped properly causing parse error
[
https://jira.jboss.org/jira/browse/RF-4351?page=com.atlassian.jira.plugin...
]
Svetlana mukhina updated RF-4351:
---------------------------------
Component/s: docs updated
rich:tree ampersand is sometimes not escaped properly causing parse
error
-------------------------------------------------------------------------
Key: RF-4351
URL: https://jira.jboss.org/jira/browse/RF-4351
Project: RichFaces
Issue Type: Bug
Components: docs updated
Affects Versions: 3.2.1
Environment: Seam 2.0.1.GA, Facelets 1.1.14, jsf mojarra 1.2_07-b03-FCS
Reporter: Mikael
Assignee: Tsikhon Kuprevich
Fix For: 3.3.1
Hi
My nodes in my tree may contain ampersand and other crazy German characters.
Currently I'm getting an XML parse error pointing to the ampersand.
Had a look at the generated source and discovered that the node content is used as part
of the element id. Mostly the ampersand is escaped properly but in at least one place it
isn't which is causing a parse error on the client side.
Using the NEKO parser.
The forum link contains more information, especially the a4j log.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:19 a.m.
New subject: [JBoss JIRA] Closed: (RF-4351) rich:tree ampersand is sometimes not escaped properly causing parse error
[
https://jira.jboss.org/jira/browse/RF-4351?page=com.atlassian.jira.plugin...
]
Mikhail Vitenkov closed RF-4351.
--------------------------------
Assignee: Nick Belaevski (was: Tsikhon Kuprevich)
Verified at 3.3.1.CR1
rich:tree ampersand is sometimes not escaped properly causing parse
error
-------------------------------------------------------------------------
Key: RF-4351
URL: https://jira.jboss.org/jira/browse/RF-4351
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.1
Environment: Seam 2.0.1.GA, Facelets 1.1.14, jsf mojarra 1.2_07-b03-FCS
Reporter: Mikael
Assignee: Nick Belaevski
Fix For: 3.3.1
Hi
My nodes in my tree may contain ampersand and other crazy German characters.
Currently I'm getting an XML parse error pointing to the ampersand.
Had a look at the generated source and discovered that the node content is used as part
of the element id. Mostly the ampersand is escaped properly but in at least one place it
isn't which is causing a parse error on the client side.
Using the NEKO parser.
The forum link contains more information, especially the a4j log.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6100
days inactive
6340
days old
richfaces-issues@lists.jboss.org
13 comments
4 participants
participants (4)
-
Mikael (JIRA) -
Mikhail Vitenkov (JIRA)
-
Nick Belaevski (JIRA)
-
Svetlana mukhina (JIRA)