[
https://issues.jboss.org/browse/RF-12802?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč commented on RF-12802:
---------------------------------
1. I think in this use case, the fragment should throw exception as one (if logic requires
that) should ask for presence of dialog and then close it if necessary
2. It depends whether you are programming against API or not at all. I would maintain
consistency - in case you use POJOs and don't expose interfaces, then it should be
wise to do that across whole API - it means using no *Impl suffixes etc. at all.
In opposite case, you would need to expose interfaces for all page fragments - is it
something you do or want to do?
Move page fragments from repository qa to richfaces5
----------------------------------------------------
Key: RF-12802
URL:
https://issues.jboss.org/browse/RF-12802
Project: RichFaces
Issue Type: Task
Security Level: Public(Everyone can see)
Components: build/distribution
Affects Versions: 5.0.0.Alpha1
Reporter: Pavol Pitonak
Assignee: Brian Leathem
Fix For: 5.0.0.Alpha2
As discussed on community meeting on Feb 12, we should move page fragments for RichFaces
components to richfaces5 repository so that they are distributed with framework.
We should find out how to prepare them so that they are easy to use for community
members. RichFaces QE/dev need to test internals of components, community members will
probably test only high-level functionality of components. One possible solution would be
to create package "internal" in which there would be page fragments extending
those from "public" package. QE team would then use "internal"
implementations.
--
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