[
https://issues.jboss.org/browse/RF-13186?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč commented on RF-13186:
---------------------------------
[~manovotn], could you please create a nw issue? This one's history is little bit
polluted yet.
Showcase 4.5.x fails
--------------------
Key: RF-13186
URL:
https://issues.jboss.org/browse/RF-13186
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.5.0.Alpha1
Reporter: Michal Petrov
Assignee: Lukáš Fryč
Fix For: 4.5.0.Alpha1
[
https://github.com/michpetrov/richfaces/tree/showcase-4.5.x/examples/show...] -
showcase 4.5
[
https://github.com/richfaces4/components/tree/4.5.x] - 4.5.x components
[
https://github.com/richfaces4/dev-examples/tree/4.5.x] - 4.5 dev-examples
Builds and deploys fine.
Examples that do not work:
* -several examples (e.g. actionListener) produce "The form component needs to have
a UIForm in its ancestry. Suggestion: enclose the necessary components within
<h:form>"-
* validation - fails because rf.rf4.ui.Message is not defined, the resource is not being
included due to resource optimization
* trees/rich:tree - missing …/javax.faces.resource/node_icon.gif.jsf?ln=org.richfaces
* menus/rich:contextMenu and rich:dropDownMenu - not working, probably for the same
reason as validators (missing proper javascript resource)
* inputs/rich:inplaceInput - ditto
* selects/rich:inplaceSelect - ditto
* output/rich:tooltip - ditto
When resource optimization some components (dataTables) are missing background image
causing a badly generated CSS. {{background-image: url()}}
h5. resource optimization turned off
h6. Issue with Validator
- org.richfaces.validator.FacesObjectDescriptor.getMessage()
- collision between RF4.5 and RF5
the interface is the same in both versions but the Message class is in different
packages in the two
h6. Issue with menus
- org.richfaces.renderkit.html.MenuItemRendererBase.getUtils()
- probably the same problem
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira