[JBoss JIRA] (RF-13046) EDT in EDT: when @frozenColumns is equal to number of columns then there is no vertical scroller in EDT
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13046?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak updated RF-13046:
-------------------------------
Labels: (was: needs-qe)
> EDT in EDT: when @frozenColumns is equal to number of columns then there is no vertical scroller in EDT
> -------------------------------------------------------------------------------------------------------
>
> Key: RF-13046
> URL: https://issues.jboss.org/browse/RF-13046
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> GlassFish Server Open Source Edition 3.1.2.2
> Java(TM) SE Runtime Environment 1.7.0_21-b11 @ Linux
> Firefox 18.0 @ Linux x86_64
> Reporter: Jiří Štefek
> Assignee: Brian Leathem
> Fix For: 4.3.4
>
> Attachments: EDTinEDTmaxFrozenColumnsNoScrollers.png, EDTinEDTmaxFrozenColumnsScrollersAfterColumnReposition.png, EDTinEDTWhenNoFrozenColsOrWhenFrozenColsLesserThanMaxCols.png
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> EDT(1st) in EDT(2nd), when @frozenColumns (of 1st) is equal to number of columns (of 1st), then there is no vertical scroller in EDT (1st). But when you reorganize the columns (of 1st), the scroller and the 'footer' facet appears (1st).
--
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-13142) Showcase: mediaOutput sample is not working with MyFaces
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13142?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak reopened RF-13142:
--------------------------------
I see this error when I deploy richfaces-showcase-4.3.4.Final-myfaces.war to Tomcat 7.0.42:
{quote}
Sep 16, 2013 4:55:40 PM org.richfaces.util.Util decodeObjectData
SEVERE: Input error for deserialize data
java.io.InvalidClassException: Unauthorized deserialization attempt; javax.faces.view.Location
at org.richfaces.util.LookAheadObjectInputStream.resolveClass(LookAheadObjectInputStream.java:97)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1610)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1771)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
at org.apache.myfaces.view.facelets.el.ContextAwareTagMethodExpression.readExternal(ContextAwareTagMethodExpression.java:162)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1837)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1796)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348)
at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1704)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1342)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
at org.richfaces.util.Util.decodeObjectData(Util.java:237)
at org.richfaces.resource.DefaultCodecResourceRequestData.getData(DefaultCodecResourceRequestData.java:97)
at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:337)
at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:156)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:191)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.richfaces.webapp.PushFilter.doFilter(PushFilter.java:129)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1023)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
{quote}
> Showcase: mediaOutput sample is not working with MyFaces
> --------------------------------------------------------
>
> Key: RF-13142
> URL: https://issues.jboss.org/browse/RF-13142
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.3, 4.3.4
> Environment: MyFaces 2.1.10
> Apache Tomcat 7.0.34
> Reporter: Jiří Štefek
> Assignee: Brian Leathem
> Labels: needs-qe
> Fix For: 4.3.4
>
>
> The generated image from media output is not displayed.
> Stack trace from logs:
> {code}
> java.lang.ClassNotFoundException: javax.faces.component.StateHolderSaver
> at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1714)
> at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1559)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:188)
> at org.richfaces.util.LookAheadObjectInputStream.loadWhitelist(LookAheadObjectInputStream.java:141)
> at org.richfaces.util.LookAheadObjectInputStream.<clinit>(LookAheadObjectInputStream.java:76)
> at org.richfaces.util.Util.decodeObjectData(Util.java:236)
> at org.richfaces.resource.DefaultCodecResourceRequestData.getData(DefaultCodecResourceRequestData.java:97)
> at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:337)
> at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:156)
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:191)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at org.richfaces.webapp.PushFilter.doFilter(PushFilter.java:129)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
> at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
> at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
> at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:722)
> {code}
> {code}
> java.lang.NoClassDefFoundError: Could not initialize class org.richfaces.util.LookAheadObjectInputStream
> at org.richfaces.util.Util.decodeObjectData(Util.java:236)
> at org.richfaces.resource.DefaultCodecResourceRequestData.getData(DefaultCodecResourceRequestData.java:97)
> at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:337)
> at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:156)
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:191)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at org.richfaces.webapp.PushFilter.doFilter(PushFilter.java:129)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
> at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
> at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
> at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:722)
> {code}
--
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-13150) Remove JMS functionality from the RichFaces showcase
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13150?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak commented on RF-13150:
------------------------------------
Verified in 4.3.4.Final respin. Demo doesn't contain JMS sample and doesn't require user to configure JMS before deploying war on application server.
However, there are few artefacts that are not necessary anymore or need update:
* HornetQ jars should be removed from war for Tomcat.
* Unnecessary classes JMSInitializer, JMSMessage* should be removed.
* Readme file should be updated - no manual steps are required from users anymore.
> Remove JMS functionality from the RichFaces showcase
> ----------------------------------------------------
>
> Key: RF-13150
> URL: https://issues.jboss.org/browse/RF-13150
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: component-push/poll, showcase
> Reporter: Brian Leathem
> Assignee: Brian Leathem
> Fix For: 4.3.4
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> The RichFaces showcase currently includes a demo of RichFaces push backed by JMS. The JMS security configuration however is not portable, and leads to difficulties in running the RichFaces showcase in other containers.
> We target the showcase at demonstrating component capabilities, and leave the JMS integration to be demonstrated as a developer example. The caveat here is that we do a better job promoting the availability of our developer examples.
--
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-13150) Remove JMS functionality from the RichFaces showcase
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13150?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak updated RF-13150:
-------------------------------
Labels: (was: needs-qe)
> Remove JMS functionality from the RichFaces showcase
> ----------------------------------------------------
>
> Key: RF-13150
> URL: https://issues.jboss.org/browse/RF-13150
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: component-push/poll, showcase
> Reporter: Brian Leathem
> Assignee: Brian Leathem
> Fix For: 4.3.4
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> The RichFaces showcase currently includes a demo of RichFaces push backed by JMS. The JMS security configuration however is not portable, and leads to difficulties in running the RichFaces showcase in other containers.
> We target the showcase at demonstrating component capabilities, and leave the JMS integration to be demonstrated as a developer example. The caveat here is that we do a better job promoting the availability of our developer examples.
--
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-13155) Unable to trigger hidden FileUpload in IE with an associated Label: missing Id on generated <input type=“file“>
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13155?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak commented on RF-13155:
------------------------------------
I verified it in 4.3.4.Final respin. The component works correct but when a user uploads one or more files then there are multiple input tags with the same id.
> Unable to trigger hidden FileUpload in IE with an associated Label: missing Id on generated <input type=“file“>
> ---------------------------------------------------------------------------------------------------------------
>
> Key: RF-13155
> URL: https://issues.jboss.org/browse/RF-13155
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.3.2
> Environment: Internet Explorer 8
> Reporter: Benoit Pflieger
> Assignee: Brian Leathem
> Priority: Minor
> Labels: low_hanging_fruit
> Fix For: 4.3.4
>
>
> A hidden FileUpload was triggered by clicking an associated label to the generated tag <input type=“file“>.
> That's the security workaround to trigger an <input type=“file“> under Internet Explorer.
> It worked with Richfaces 3.3.
> This workaround can't be achieved anymore with Richfaces 4.3.2 because the <input type=“file“> is only generated without the attribute "id".
--
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-13155) Unable to trigger hidden FileUpload in IE with an associated Label: missing Id on generated <input type=“file“>
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13155?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak updated RF-13155:
-------------------------------
Labels: low_hanging_fruit (was: low_hanging_fruit needs-qe)
> Unable to trigger hidden FileUpload in IE with an associated Label: missing Id on generated <input type=“file“>
> ---------------------------------------------------------------------------------------------------------------
>
> Key: RF-13155
> URL: https://issues.jboss.org/browse/RF-13155
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.3.2
> Environment: Internet Explorer 8
> Reporter: Benoit Pflieger
> Assignee: Brian Leathem
> Priority: Minor
> Labels: low_hanging_fruit
> Fix For: 4.3.4
>
>
> A hidden FileUpload was triggered by clicking an associated label to the generated tag <input type=“file“>.
> That's the security workaround to trigger an <input type=“file“> under Internet Explorer.
> It worked with Richfaces 3.3.
> This workaround can't be achieved anymore with Richfaces 4.3.2 because the <input type=“file“> is only generated without the attribute "id".
--
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-13189) Update jquery-atmosphere.js to 1.0.17 in 4.3.x
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13189?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak commented on RF-13189:
------------------------------------
Verified in respin of 4.3.4.Final. Issue is ready to be closed.
> Update jquery-atmosphere.js to 1.0.17 in 4.3.x
> ----------------------------------------------
>
> Key: RF-13189
> URL: https://issues.jboss.org/browse/RF-13189
> Project: RichFaces
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: component-push/poll
> Affects Versions: 4.3.4
> Reporter: Lukáš Fryč
> Assignee: Brian Leathem
> Priority: Critical
> Fix For: 4.3.4
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> The Atmosphere was upgraded to 1.0.17 in RF-13154, but jquery-atmosphere.js (JS) in {{components/core/ui}} project wasn't.
> The problem is jquery-atmosphere.js doesn't even exists in 1.0.17, it was removed after 1.0.13 (i.e. doesn't exist since 1.0.14).
> The new project atmosphere-javascript which contains jquery.atmosphere.js was created instead, but it has different versioning: 2.0.0 and 2.0.1 are available as of today.
> Few notes:
> * I have tried the showcase with Atmosphere 1.0.17 + JS 1.0.13
> ** it works
> ** JS got some changes here which could potentially stabilize
> * I have tried the showcase with Atmosphere 1.0.17 + JS 2.0.1
> ** it works
> ** JS was completely refactored but since it works, it seems API-compatible
--
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-13189) Update jquery-atmosphere.js to 1.0.17 in 4.3.x
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13189?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak updated RF-13189:
-------------------------------
Labels: (was: needs-qe)
> Update jquery-atmosphere.js to 1.0.17 in 4.3.x
> ----------------------------------------------
>
> Key: RF-13189
> URL: https://issues.jboss.org/browse/RF-13189
> Project: RichFaces
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: component-push/poll
> Affects Versions: 4.3.4
> Reporter: Lukáš Fryč
> Assignee: Brian Leathem
> Priority: Critical
> Fix For: 4.3.4
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> The Atmosphere was upgraded to 1.0.17 in RF-13154, but jquery-atmosphere.js (JS) in {{components/core/ui}} project wasn't.
> The problem is jquery-atmosphere.js doesn't even exists in 1.0.17, it was removed after 1.0.13 (i.e. doesn't exist since 1.0.14).
> The new project atmosphere-javascript which contains jquery.atmosphere.js was created instead, but it has different versioning: 2.0.0 and 2.0.1 are available as of today.
> Few notes:
> * I have tried the showcase with Atmosphere 1.0.17 + JS 1.0.13
> ** it works
> ** JS got some changes here which could potentially stabilize
> * I have tried the showcase with Atmosphere 1.0.17 + JS 2.0.1
> ** it works
> ** JS was completely refactored but since it works, it seems API-compatible
--
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-12894) The richfaces-framework is not reloadable by JRebel
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12894?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-12894:
---------------------------------
Verified locally that re-loading now works okay with:
JBoss EAP 6.1.1.GA
JRebel 5.3.1
> The richfaces-framework is not reloadable by JRebel
> ---------------------------------------------------
>
> Key: RF-12894
> URL: https://issues.jboss.org/browse/RF-12894
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: third-party
> Affects Versions: 5.0.0.Alpha1
> Reporter: Lukáš Fryč
> Assignee: Lukáš Fryč
> Original Estimate: 3 hours
> Remaining Estimate: 3 hours
>
> It seems when you compile the framework with CDK, the faces-config.xml is re-generated and re-loaded by JRebel.
> However the other configuration files stored in {{META-INF/}} (e.g. [core.faces-config.xml|https://github.com/richfaces/richfaces5/blob/master...]) directly (without CDK processing) are not taken into consideration in reloaded configuration, thus this configuration is ignored. As the result, no Core configuration is loaded and no RichFaces Core feature does work.
> ----
> The JRebel reload and quick turnaround is one of the features we wanted to enable by build re-structure thus I consider this high priority to cooperate with JRebel team and make it work.
--
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-12909) Aggregate all *.faces-config.xml in richfaces.jar:/META-INF to one faces-config.xml
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12909?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-12909:
---------------------------------
Note that there are no other reasons for merging configs to one than polishing.
It seems JRebel works fine now, as noted in RF-12894.
> Aggregate all *.faces-config.xml in richfaces.jar:/META-INF to one faces-config.xml
> -----------------------------------------------------------------------------------
>
> Key: RF-12909
> URL: https://issues.jboss.org/browse/RF-12909
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Affects Versions: 5.0.0.Alpha1
> Reporter: Lukáš Fryč
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> These config files are not in src/main/config and thus they are not processed by CDK - they are included in the META-INF and thus they are processed by JSF in runtime.
> It makes the META-INF unpolished.
--
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