[
https://issues.jboss.org/browse/RF-11582?page=com.atlassian.jira.plugin.s...
]
Juraj Huska updated RF-11582:
-----------------------------
Description:
Samples for rich:editor and rich:notify do use in .xhtml files names for this samples dash
notation.
For example samples for notify are: notify-attributes-sample.xhtml,
notify-messages-sample.xhtml, stacking-messages-sample.xhtml.
I would appreciate to name them using camel case, as it is done for all other components.
The reason is that in functional tests for showcase I am using this feature for loading
the appropriate page according to the test class name, and it is not possible to name java
classes with dashes.
The another reason is to have consistent names for all components.
was:
Samples for rich:editor and rich:notify do use in .xhtml files names for this samples dash
notation.
For example samples for notify are: notify-attributes-sample.xhtml,
notify-messages-sample.xhtml, stacking-messages-sample.xhtml.
I would appreciate to name them using camel case, as it is done for all other components.
The reason is that in functional tests smoke tests for showcase I am using this feature
for loading the appropriate page according to the test class name, and it is not possible
to name java classes with dashes.
The another reason is to have consistent names for all components.
showcase - rename names of xhtml pages for rich:notify and
rich:editor samples
------------------------------------------------------------------------------
Key: RF-11582
URL:
https://issues.jboss.org/browse/RF-11582
Project: RichFaces
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: qe, showcase
Affects Versions: 4.1.0.Milestone2
Environment: showcase
Reporter: Juraj Huska
Priority: Trivial
Samples for rich:editor and rich:notify do use in .xhtml files names for this samples
dash notation.
For example samples for notify are: notify-attributes-sample.xhtml,
notify-messages-sample.xhtml, stacking-messages-sample.xhtml.
I would appreciate to name them using camel case, as it is done for all other
components.
The reason is that in functional tests for showcase I am using this feature for loading
the appropriate page according to the test class name, and it is not possible to name java
classes with dashes.
The another reason is to have consistent names for all components.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira