[JBoss JIRA] (RF-13020) Showcase 5.Alpha1 wars are 5 MB bigger than 4.3.x wars
by Juraj Húska (JIRA)
Juraj Húska created RF-13020:
--------------------------------
Summary: Showcase 5.Alpha1 wars are 5 MB bigger than 4.3.x wars
Key: RF-13020
URL: https://issues.jboss.org/browse/RF-13020
Project: RichFaces
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: build/distribution, showcase
Affects Versions: 5.0.0.Alpha1
Reporter: Juraj Húska
RichFaces 5.Alpha1 Showcase {{.wars}} are 5 MB bigger than 4.3.x {{.wars}}.
The difference is mainly in the {{WEB-INF/lib}} folder. IMHO there was not such a change which requires additional libraries.
Here is the comparison of the libraries.
{{RF 5}} wars have these *additional* libraries (size around 3.5 MB)
* serializer-2.7.1.jar
* xalan-2.7.1.jar
* xml-apis-1.0.b2.jar
These {{RF 5}} dependencies were included in {{RF 4.x}} as well, however with *different name*:
* jboss-jms-api_1.1_spec-1.0.1.Final.jar
* jboss-jstl-api_1.2_spec-1.0.3.Final.jar
These dependencies are *missing* in RF5 (1.2 MB):
* commons-beanutils-1.8.3.jar
* commons-codec-1.6.jar
* commons-digester-1.8.jar
* commons-logging-1.1.1.jar
* jsr250-api-1.0.jar
Note that richfaces-5.Alpha1.jar (7.5 MB) has similar size as all richfaces*.jar together (7.8 MB).
--
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
12 years, 10 months
[JBoss JIRA] (RF-13020) Showcase 5.Alpha1 wars are 5 MB bigger than 4.3.x wars
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13020?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-13020:
-----------------------------
Description:
RichFaces 5.Alpha1 Showcase {{.wars}} are 5 MB bigger than 4.3.x {{.wars}}.
The difference is mainly in the {{WEB-INF/lib}} folder. IMHO there was not such a change which requires additional libraries.
Here is the comparison of the libraries.
{{RF 5}} wars have these *additional* libraries (size around 3.5 MB)
* serializer-2.7.1.jar
* xalan-2.7.1.jar
* xml-apis-1.0.b2.jar
These {{RF 5}} dependencies were included in {{RF 4.x}} as well, however with *different name*:
* jboss-jms-api_1.1_spec-1.0.1.Final.jar
* jboss-jstl-api_1.2_spec-1.0.3.Final.jar
These dependencies are *missing* in RF5 (1.2 MB):
* commons-beanutils-1.8.3.jar
* commons-codec-1.6.jar
* commons-digester-1.8.jar
* commons-logging-1.1.1.jar
* jsr250-api-1.0.jar
Note that *richfaces-5.Alpha1.jar* (7.5 MB) has *similar* size as all *richfaces*.jar* together (7.8 MB).
was:
RichFaces 5.Alpha1 Showcase {{.wars}} are 5 MB bigger than 4.3.x {{.wars}}.
The difference is mainly in the {{WEB-INF/lib}} folder. IMHO there was not such a change which requires additional libraries.
Here is the comparison of the libraries.
{{RF 5}} wars have these *additional* libraries (size around 3.5 MB)
* serializer-2.7.1.jar
* xalan-2.7.1.jar
* xml-apis-1.0.b2.jar
These {{RF 5}} dependencies were included in {{RF 4.x}} as well, however with *different name*:
* jboss-jms-api_1.1_spec-1.0.1.Final.jar
* jboss-jstl-api_1.2_spec-1.0.3.Final.jar
These dependencies are *missing* in RF5 (1.2 MB):
* commons-beanutils-1.8.3.jar
* commons-codec-1.6.jar
* commons-digester-1.8.jar
* commons-logging-1.1.1.jar
* jsr250-api-1.0.jar
Note that richfaces-5.Alpha1.jar (7.5 MB) has similar size as all richfaces*.jar together (7.8 MB).
> Showcase 5.Alpha1 wars are 5 MB bigger than 4.3.x wars
> ------------------------------------------------------
>
> Key: RF-13020
> URL: https://issues.jboss.org/browse/RF-13020
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: build/distribution, showcase
> Affects Versions: 5.0.0.Alpha1
> Reporter: Juraj Húska
>
> RichFaces 5.Alpha1 Showcase {{.wars}} are 5 MB bigger than 4.3.x {{.wars}}.
> The difference is mainly in the {{WEB-INF/lib}} folder. IMHO there was not such a change which requires additional libraries.
> Here is the comparison of the libraries.
> {{RF 5}} wars have these *additional* libraries (size around 3.5 MB)
> * serializer-2.7.1.jar
> * xalan-2.7.1.jar
> * xml-apis-1.0.b2.jar
> These {{RF 5}} dependencies were included in {{RF 4.x}} as well, however with *different name*:
> * jboss-jms-api_1.1_spec-1.0.1.Final.jar
> * jboss-jstl-api_1.2_spec-1.0.3.Final.jar
> These dependencies are *missing* in RF5 (1.2 MB):
> * commons-beanutils-1.8.3.jar
> * commons-codec-1.6.jar
> * commons-digester-1.8.jar
> * commons-logging-1.1.1.jar
> * jsr250-api-1.0.jar
> Note that *richfaces-5.Alpha1.jar* (7.5 MB) has *similar* size as all *richfaces*.jar* together (7.8 MB).
--
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
12 years, 10 months
[JBoss JIRA] (RF-12533) UIDataAdaptor throws NPE with disabled PSS (webflow 2.3)
by Christoph Stampfel (JIRA)
[ https://issues.jboss.org/browse/RF-12533?page=com.atlassian.jira.plugin.s... ]
Christoph Stampfel edited comment on RF-12533 at 5/27/13 7:45 AM:
------------------------------------------------------------------
We have exactly the same problem. Please see the attached logfile.
The problem already exists in RichFaces 4.3.0 Release
It would be very important for us that this bug will be fixed soon.
was (Author: christophs):
We have exactly the same problem. Please see the attached logfile.
The problem already exists in RichFaces 4.3.0.
It would be very important for us that this bug will be fixed soon.
> UIDataAdaptor throws NPE with disabled PSS (webflow 2.3)
> --------------------------------------------------------
>
> Key: RF-12533
> URL: https://issues.jboss.org/browse/RF-12533
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.2.2.Final, 4.2.3.CR1, 4.3.0.M1
> Environment: spring webflow 2.3.1, myfaces-impl 2.1.8
> Reporter: Anton Zukovskij
> Priority: Critical
> Labels: partial_state_saving, spring
> Fix For: 5-Tracking
>
> Attachments: log-2.txt, log.txt, swf-rf4.zip
>
>
> When partial state saving is disabled(javax.faces.PARTIAL_STATE_SAVING=false), nullpointer exception is thrown during restore state phase of webflow rendered view that contains UIDataAdaptor component. In other words NPE exception is thrown on every page submit of webflow rendered views that contain components that exted UIDataAdaptor. Please see log attached and sample application.
--
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
12 years, 10 months
[JBoss JIRA] (RF-12533) UIDataAdaptor throws NPE with disabled PSS (webflow 2.3)
by Christoph Stampfel (JIRA)
[ https://issues.jboss.org/browse/RF-12533?page=com.atlassian.jira.plugin.s... ]
Christoph Stampfel edited comment on RF-12533 at 5/27/13 7:39 AM:
------------------------------------------------------------------
We have exactly the same problem. Please see the attached logfile.
The problem already exists in RichFaces 4.3.0.
It would be very important for us that this bug will be fixed soon.
was (Author: christophs):
We have exactly the same problem. Please see the attached logfile.
It would be very important for us that this bug will be fixed soon.
> UIDataAdaptor throws NPE with disabled PSS (webflow 2.3)
> --------------------------------------------------------
>
> Key: RF-12533
> URL: https://issues.jboss.org/browse/RF-12533
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.2.2.Final, 4.2.3.CR1, 4.3.0.M1
> Environment: spring webflow 2.3.1, myfaces-impl 2.1.8
> Reporter: Anton Zukovskij
> Priority: Critical
> Labels: partial_state_saving, spring
> Fix For: 5-Tracking
>
> Attachments: log-2.txt, log.txt, swf-rf4.zip
>
>
> When partial state saving is disabled(javax.faces.PARTIAL_STATE_SAVING=false), nullpointer exception is thrown during restore state phase of webflow rendered view that contains UIDataAdaptor component. In other words NPE exception is thrown on every page submit of webflow rendered views that contain components that exted UIDataAdaptor. Please see log attached and sample application.
--
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
12 years, 10 months
[JBoss JIRA] (RF-12533) UIDataAdaptor throws NPE with disabled PSS (webflow 2.3)
by Christoph Stampfel (JIRA)
[ https://issues.jboss.org/browse/RF-12533?page=com.atlassian.jira.plugin.s... ]
Christoph Stampfel updated RF-12533:
------------------------------------
Attachment: log-2.txt
We have exactly the same problem. Please see the attached logfile.
It would be very important for us that this bug will be fixed soon.
> UIDataAdaptor throws NPE with disabled PSS (webflow 2.3)
> --------------------------------------------------------
>
> Key: RF-12533
> URL: https://issues.jboss.org/browse/RF-12533
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.2.2.Final, 4.2.3.CR1, 4.3.0.M1
> Environment: spring webflow 2.3.1, myfaces-impl 2.1.8
> Reporter: Anton Zukovskij
> Priority: Critical
> Labels: partial_state_saving, spring
> Fix For: 5-Tracking
>
> Attachments: log-2.txt, log.txt, swf-rf4.zip
>
>
> When partial state saving is disabled(javax.faces.PARTIAL_STATE_SAVING=false), nullpointer exception is thrown during restore state phase of webflow rendered view that contains UIDataAdaptor component. In other words NPE exception is thrown on every page submit of webflow rendered views that contain components that exted UIDataAdaptor. Please see log attached and sample application.
--
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
12 years, 10 months
[JBoss JIRA] (RF-13019) Placeholder disappears after form reset
by Atanu Mukherjee (JIRA)
Atanu Mukherjee created RF-13019:
------------------------------------
Summary: Placeholder disappears after form reset
Key: RF-13019
URL: https://issues.jboss.org/browse/RF-13019
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.3.2
Reporter: Atanu Mukherjee
I have the following code inside a form -
<h:inputText id="userName" styleClass="span6" >
<f:validateLength maximum="255"/>
<rich:placeholder value="ID / Username" />
</h:inputText>
The placeholder value disappears if I reset the form. Comes back up after I click the control and tab out.
--
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
12 years, 10 months
[JBoss JIRA] (RF-12428) File delete exception for rich:fileUpload in 4.2.2
by Danilo Piazzalunga (JIRA)
[ https://issues.jboss.org/browse/RF-12428?page=com.atlassian.jira.plugin.s... ]
Danilo Piazzalunga commented on RF-12428:
-----------------------------------------
I encountered the same issue. Closing the InputStream worked for me.
> File delete exception for rich:fileUpload in 4.2.2
> --------------------------------------------------
>
> Key: RF-12428
> URL: https://issues.jboss.org/browse/RF-12428
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.2.2.Final
> Environment: Jboss 7.1.1 Application server, Richfaces 4.2.2 Final, JSF 2.0, Java 1.6, All browsers
> Reporter: prakash t
> Priority: Critical
> Labels: 4.2.2, Final, ie, ie7, richfaces
> Fix For: 5-Tracking
>
>
> I am using richfaces 4.2 in my application.I have following issues with rich:fileUpload component.
> 1.The component behaves in a different way with IE 7. When a single file is added, it displays that 2 files are uploaded.
> 2. After the file is uploaded, it tries to delete the temporary file and throws the following exception :
> {code}
> SEVERE [org.richfaces.log.Application] (http--0.0.0.0-8080-5) File delete failed: java.io.IOException: File delete failed
> at org.richfaces.request.FileUploadDiscResource.delete(FileUploadDiscResource.java:74) [richfaces-components-ui-4.2.2.Final.jar:4.2.2.Final]
> at org.richfaces.request.UploadedFile25.delete(UploadedFile25.java:54) [richfaces-components-ui-4.2.2.Final.jar:4.2.2.Final]
> at org.richfaces.request.MultipartRequest25.release(MultipartRequest25.java:163) [richfaces-components-ui-4.2.2.Final.jar:4.2.2.Final]
> at org.richfaces.context.FileUploadFacesContextFactory$FileUploadFacesContext.release(FileUploadFacesContextFactory.java:70) [richfaces-components-ui-4.2.2.Final.jar:4.2.2.Final]
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:612) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
> at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_20]
> {code}
> Could you help us in resolving these issues as soon as possible?
--
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
12 years, 10 months