[JBoss JIRA] (RF-13164) Skinning of standard inputs not consistent
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13164?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13164:
------------------------------------
the tricky part here will be to define the use cases we want to support and come up with the right configuration set to choose between:
* RF 4 style control skinning
* RF 4 style control skinning classes
* RF 5 bootstrap
* No skins
Questions to be answered include:
* What combination of the above control skins will be supported?
* Will we support dynamically toggling between control skins?
Note: control skinning classes are currently added early in the view build lifecycle, during the RESTORE_VIEW phase:
https://github.com/richfaces/richfaces/blob/master/framework/src/main/jav...
> Skinning of standard inputs not consistent
> ------------------------------------------
>
> Key: RF-13164
> URL: https://issues.jboss.org/browse/RF-13164
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: skinning
> Affects Versions: 5.0.0.Alpha2
> Reporter: Pavol Pitonak
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> In 5.0.0-SNAPSHOT standard JSF inputs (such as h:inputText) are skinned by RichFaces or by Bootstrap depending on which components are used on page.
> When a new component (e.g. autocomplete) is used, it includes Bootstrap CSS file which overrides RichFaces skinning.
> Bootstrap CSS file should be probably included for each component.
--
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
10 years, 9 months
[JBoss JIRA] (RF-13164) Skinning of standard inputs not consistent
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13164?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13164:
-------------------------------
Original Estimate: 2 hours
Remaining Estimate: 2 hours
> Skinning of standard inputs not consistent
> ------------------------------------------
>
> Key: RF-13164
> URL: https://issues.jboss.org/browse/RF-13164
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: skinning
> Affects Versions: 5.0.0.Alpha2
> Reporter: Pavol Pitonak
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> In 5.0.0-SNAPSHOT standard JSF inputs (such as h:inputText) are skinned by RichFaces or by Bootstrap depending on which components are used on page.
> When a new component (e.g. autocomplete) is used, it includes Bootstrap CSS file which overrides RichFaces skinning.
> Bootstrap CSS file should be probably included for each component.
--
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
10 years, 9 months
[JBoss JIRA] (RF-13148) RichFaces project from archetype can not be built without JBoss repositories
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13148?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13148:
-------------------------------
Original Estimate: 1 hour
Remaining Estimate: 1 hour
> RichFaces project from archetype can not be built without JBoss repositories
> ----------------------------------------------------------------------------
>
> Key: RF-13148
> URL: https://issues.jboss.org/browse/RF-13148
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: archetype, build/distribution
> Affects Versions: 5.0.0.Alpha1
> Reporter: Juraj Húska
> Priority: Blocker
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> Projects created from RichFaces archetypes can not be built without JBoss repositories (using just Maven Central).
> The reason is that they depend on {{org.jboss.test-jsf:jsf-test:pom:1.1.6}} which is deployed only to JBoss repos.
--
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
10 years, 9 months
[JBoss JIRA] (RF-13071) Undeploying Showcase from Tomcat6/7 can cause memory leak
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13071?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13071:
-------------------------------
Fix Version/s: 5-Tracking
(was: 5.0.0.Alpha2)
> Undeploying Showcase from Tomcat6/7 can cause memory leak
> ---------------------------------------------------------
>
> Key: RF-13071
> URL: https://issues.jboss.org/browse/RF-13071
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-push/poll, showcase
> Affects Versions: 4.1.0.Final, 5.0.0.Alpha1
> Reporter: Juraj Húska
> Priority: Minor
> Labels: memory_leak, performance
> Fix For: 5-Tracking
>
>
> When undeploying showcase from Tomcat 6/7 then following log is present on the server console:
> {code}
> SEVERE: The web application [/richfaces-showcase-tomcat6] appears to have started a thread named [Thread-0 (group:HornetQ-client-factory-threads-1831192424-1080990297)] but has failed to stop it. This is very likely to create a memory leak.
> {code}
> There is lot of such logs, just the _Thread-counter_ is changing.
> * 11 such logs just with showcase deploying and then right after undeploying
> * bit more when after deploying playing a little bit with {{r:push}}
> IMHO it is not just warning. I am experiencing {{Out of Memory}} issues when testing on Tomcat. I need to use quite big {{Perm Gen}} and {{Heap size}}
--
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
10 years, 9 months