[JBoss JIRA] (RF-13126) ExtendedDataTable Header Column Widths does not conform to Row Data Column Widths specified in TableState
by Steven W. (JIRA)
[ https://issues.jboss.org/browse/RF-13126?page=com.atlassian.jira.plugin.s... ]
Steven W. updated RF-13126:
---------------------------
Description:
In prior 3.x release the ExtendedDataTable control supported TableState data for sizing of columns - this worked relatively well *however* there is/was a bug such that the columns headers above the table did *not* align properly with the data rows of the table below; this could be partially accommodated by specifying a size for the column (in the TableState data) that was wider than the longest string in the column data as he initial / minimum size.
In subsequent release (in 4.x time frame I believe) the control was refactored and the TableState capability as a whole was lost - I saw this in another report on the forum or Jira though not the same but other related issues may be https://issues.jboss.org/browse/RF-4855 + https://issues.jboss.org/browse/RF-13094 and https://issues.jboss.org/browse/RF-13095 ; the report I remember reading, however, is that this TableState functionality was lost during the refactoring and was then said to be restored in a subsequent release.
I am now using Version 5 of RichFaces to include the first milestone and latest (overnight) snapshot and am confirming this column header sizing AND/OR TableState table header sizing issue(s) still remain, regardless of prior attempts to include TableState data recognition and, if/as so, the widths of the column headers does not respect the TableState data nor do they conform to the column widths of the data in the rows below.
was:
In prior 3.x release the ExtendedDataTable control supported TableState data for sizing of columns - this worked relatively well *however* there is/was a bug such that the columns headers above the table did *not* align properly with the data rows of the table below; this could be partially accommodated by specifying a size for the column (in the TableState data) that was wider than the longest string in the column data as he initial / minimum size.
In subsequent release (in 4.x time frame I believe) the control was refactored and the TableState capability as a whole was lost - I saw this in another report on the forum or Jira though not the same but other related issues may be https://issues.jboss.org/browse/RF-4855 + https://issues.jboss.org/browse/RF-13094 and https://issues.jboss.org/browse/RF-13095 ; the report I remember reading, however, is that this TableState functionality was lost during the refactoring and was then said to be restored in a subsequent release.
I am now using Version 5 of RichFaces to include the first milestone and latest (overnight) snapshot and am confirming this TableState table header sizing issue still remains, regardless of prior attempts to include TableState data recognition and, if/as so, the widths of the column headers does not respect the TableState data nor do they conform to the column widths of the data in the rows below.
> ExtendedDataTable Header Column Widths does not conform to Row Data Column Widths specified in TableState
> ----------------------------------------------------------------------------------------------------------
>
> Key: RF-13126
> URL: https://issues.jboss.org/browse/RF-13126
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 5.0.0.Alpha1
> Environment: Windows / Tomcat 7 / JDK 1.7 (Firefox & IE)
> Reporter: Steven W.
> Labels: new_and_noteworthy
>
> In prior 3.x release the ExtendedDataTable control supported TableState data for sizing of columns - this worked relatively well *however* there is/was a bug such that the columns headers above the table did *not* align properly with the data rows of the table below; this could be partially accommodated by specifying a size for the column (in the TableState data) that was wider than the longest string in the column data as he initial / minimum size.
> In subsequent release (in 4.x time frame I believe) the control was refactored and the TableState capability as a whole was lost - I saw this in another report on the forum or Jira though not the same but other related issues may be https://issues.jboss.org/browse/RF-4855 + https://issues.jboss.org/browse/RF-13094 and https://issues.jboss.org/browse/RF-13095 ; the report I remember reading, however, is that this TableState functionality was lost during the refactoring and was then said to be restored in a subsequent release.
> I am now using Version 5 of RichFaces to include the first milestone and latest (overnight) snapshot and am confirming this column header sizing AND/OR TableState table header sizing issue(s) still remain, regardless of prior attempts to include TableState data recognition and, if/as so, the widths of the column headers does not respect the TableState data nor do they conform to the column widths of the data in the rows below.
--
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
11 years, 3 months
[JBoss JIRA] (RF-13126) ExtendedDataTable Header Column Widths does not conform to Row Data Column Widths specified in TableState
by Steven W. (JIRA)
[ https://issues.jboss.org/browse/RF-13126?page=com.atlassian.jira.plugin.s... ]
Steven W. updated RF-13126:
---------------------------
Description:
In prior 3.x release the ExtendedDataTable control supported TableState data for sizing of columns - this worked relatively well *however* there is/was a bug such that the columns headers above the table did *not* align properly with the data rows of the table below; this could be partially accommodated by specifying a size for the column (in the TableState data) that was wider than the longest string in the column data as he initial / minimum size.
In subsequent release (in 4.x time frame I believe) the control was refactored and the TableState capability as a whole was lost - I saw this in another report on the forum or Jira though not the same but other related issues may be https://issues.jboss.org/browse/RF-4855 + https://issues.jboss.org/browse/RF-13094 and https://issues.jboss.org/browse/RF-13095 ; the report I remember reading, however, is that this TableState functionality was lost during the refactoring and was then said to be restored in a subsequent release.
I am now using Version 5 of RichFaces to include the first milestone and latest (overnight) snapshot and am confirming this TableState table header sizing issue still remains, regardless of prior attempts to include TableState data recognition and, if/as so, the widths of the column headers does not respect the TableState data nor do they conform to the column widths of the data in the rows below.
was:
In prior 3.x release the ExtendedDataTable control supported TableState data for sizing of columns - this worked relatively well *however* there is/was a bug such that the columns headers above the table did *not* align properly with the data rows of the table below; this could be partially accommodated by specifying a size for the column (in the TableState data) that was wider than the longest string in the column data as he initial / minimum size.
In subsequent release (in 4.x time frame I believe) the control was refactored and the TableState capability as a whole was lost - I saw this in another report on the forum or Jira though not the same but other related issues may be https://issues.jboss.org/browse/RF-4855 + https://issues.jboss.org/browse/RF-13094 and https://issues.jboss.org/browse/RF-13095 ; the report I remember reading, however, is that this functionality was lost during the refactoring and was then said to be restored in a subsequent release.
I am now using Version 5 of RichFaces to include the first milestone and latest (overnight) snapshot and am confirming this TableState table header sizing issue still remains, regardless of prior attempts to include TableState data recognition and, if/as so, the widths of the column headers does not respect the TableState data nor do they conform to the column widths of the data in the rows below.
> ExtendedDataTable Header Column Widths does not conform to Row Data Column Widths specified in TableState
> ----------------------------------------------------------------------------------------------------------
>
> Key: RF-13126
> URL: https://issues.jboss.org/browse/RF-13126
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 5.0.0.Alpha1
> Environment: Windows / Tomcat 7 / JDK 1.7 (Firefox & IE)
> Reporter: Steven W.
> Labels: new_and_noteworthy
>
> In prior 3.x release the ExtendedDataTable control supported TableState data for sizing of columns - this worked relatively well *however* there is/was a bug such that the columns headers above the table did *not* align properly with the data rows of the table below; this could be partially accommodated by specifying a size for the column (in the TableState data) that was wider than the longest string in the column data as he initial / minimum size.
> In subsequent release (in 4.x time frame I believe) the control was refactored and the TableState capability as a whole was lost - I saw this in another report on the forum or Jira though not the same but other related issues may be https://issues.jboss.org/browse/RF-4855 + https://issues.jboss.org/browse/RF-13094 and https://issues.jboss.org/browse/RF-13095 ; the report I remember reading, however, is that this TableState functionality was lost during the refactoring and was then said to be restored in a subsequent release.
> I am now using Version 5 of RichFaces to include the first milestone and latest (overnight) snapshot and am confirming this TableState table header sizing issue still remains, regardless of prior attempts to include TableState data recognition and, if/as so, the widths of the column headers does not respect the TableState data nor do they conform to the column widths of the data in the rows below.
--
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
11 years, 3 months
[JBoss JIRA] (RF-13126) ExtendedDataTable Header Column Widths does not conform to Row Data Column Widths specified in TableState
by Steven W. (JIRA)
[ https://issues.jboss.org/browse/RF-13126?page=com.atlassian.jira.plugin.s... ]
Steven W. updated RF-13126:
---------------------------
Description:
In prior 3.x release the ExtendedDataTable control supported TableState data for sizing of columns - this worked relatively well *however* there is/was a bug such that the columns headers above the table did *not* align properly with the data rows of the table below; this could be partially accommodated by specifying a size for the column (in the TableState data) that was wider than the longest string in the column data as he initial / minimum size.
In subsequent release (in 4.x time frame I believe) the control was refactored and the TableState capability as a whole was lost - I saw this in another report on the forum or Jira though not the same but other related issues may be https://issues.jboss.org/browse/RF-4855 + https://issues.jboss.org/browse/RF-13094 and https://issues.jboss.org/browse/RF-13095 ; the report I remember reading, however, is that this functionality was lost during the refactoring and was then said to be restored in a subsequent release.
I am now using Version 5 of RichFaces to include the first milestone and latest (overnight) snapshot and am confirming this TableState table header sizing issue still remains, regardless of prior attempts to include TableState data recognition and, if/as so, the widths of the column headers does not respect the TableState data nor do they conform to the column widths of the data in the rows below.
was:
In prior 3.x release the ExtendedDataTable control supported TableState data for sizing of columns - this worked relatively well *however* there is/was a bug such that the columns headers above the table did *not* align properly with the data rows of the table below; this could be partially accommodated by specifying a size for the column (in the TableState data) that was wider than the longest string in the column data as he initial / minimum size.
In subsequent release (in 4.x time frame I believe) the control was refactored and the TableState capability as a whole was lost - I saw this in another report on the forum or Jira though not the same but other related issues may be https://issues.jboss.org/browse/RF-13094 and https://issues.jboss.org/browse/RF-13095 ; the report I remember reading, however, is that this functionality was lost during the refactoring and was then said to be restored in a subsequent release.
I am now using Version 5 of RichFaces to include the first milestone and latest (overnight) snapshot and am confirming this TableState table header sizing issue still remains, regardless of prior attempts to include TableState data recognition and, if/as so, the widths of the column headers does not respect the TableState data nor do they conform to the column widths of the data in the rows below.
> ExtendedDataTable Header Column Widths does not conform to Row Data Column Widths specified in TableState
> ----------------------------------------------------------------------------------------------------------
>
> Key: RF-13126
> URL: https://issues.jboss.org/browse/RF-13126
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 5.0.0.Alpha1
> Environment: Windows / Tomcat 7 / JDK 1.7 (Firefox & IE)
> Reporter: Steven W.
> Labels: new_and_noteworthy
>
> In prior 3.x release the ExtendedDataTable control supported TableState data for sizing of columns - this worked relatively well *however* there is/was a bug such that the columns headers above the table did *not* align properly with the data rows of the table below; this could be partially accommodated by specifying a size for the column (in the TableState data) that was wider than the longest string in the column data as he initial / minimum size.
> In subsequent release (in 4.x time frame I believe) the control was refactored and the TableState capability as a whole was lost - I saw this in another report on the forum or Jira though not the same but other related issues may be https://issues.jboss.org/browse/RF-4855 + https://issues.jboss.org/browse/RF-13094 and https://issues.jboss.org/browse/RF-13095 ; the report I remember reading, however, is that this functionality was lost during the refactoring and was then said to be restored in a subsequent release.
> I am now using Version 5 of RichFaces to include the first milestone and latest (overnight) snapshot and am confirming this TableState table header sizing issue still remains, regardless of prior attempts to include TableState data recognition and, if/as so, the widths of the column headers does not respect the TableState data nor do they conform to the column widths of the data in the rows below.
--
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
11 years, 3 months
[JBoss JIRA] (RF-13126) ExtendedDataTable Header Column Widths does not conform to Row Data Column Widths specified in TableState
by Steven W. (JIRA)
[ https://issues.jboss.org/browse/RF-13126?page=com.atlassian.jira.plugin.s... ]
Steven W. updated RF-13126:
---------------------------
Environment: Windows / Tomcat 7 / JDK 1.7 (Firefox & IE) (was: Windows / Tomcat 7 / JDK 1.7)
> ExtendedDataTable Header Column Widths does not conform to Row Data Column Widths specified in TableState
> ----------------------------------------------------------------------------------------------------------
>
> Key: RF-13126
> URL: https://issues.jboss.org/browse/RF-13126
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 5.0.0.Alpha1
> Environment: Windows / Tomcat 7 / JDK 1.7 (Firefox & IE)
> Reporter: Steven W.
> Labels: new_and_noteworthy
>
> In prior 3.x release the ExtendedDataTable control supported TableState data for sizing of columns - this worked relatively well *however* there is/was a bug such that the columns headers above the table did *not* align properly with the data rows of the table below; this could be partially accommodated by specifying a size for the column (in the TableState data) that was wider than the longest string in the column data as he initial / minimum size.
> In subsequent release (in 4.x time frame I believe) the control was refactored and the TableState capability as a whole was lost - I saw this in another report on the forum or Jira though not the same but other related issues may be https://issues.jboss.org/browse/RF-13094 and https://issues.jboss.org/browse/RF-13095 ; the report I remember reading, however, is that this functionality was lost during the refactoring and was then said to be restored in a subsequent release.
> I am now using Version 5 of RichFaces to include the first milestone and latest (overnight) snapshot and am confirming this TableState table header sizing issue still remains, regardless of prior attempts to include TableState data recognition and, if/as so, the widths of the column headers does not respect the TableState data nor do they conform to the column widths of the data in the rows below.
--
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
11 years, 3 months
[JBoss JIRA] (RF-13126) ExtendedDataTable Header Column Widths does not conform to Row Data Column Widths specified in TableState
by Steven W. (JIRA)
Steven W. created RF-13126:
------------------------------
Summary: ExtendedDataTable Header Column Widths does not conform to Row Data Column Widths specified in TableState
Key: RF-13126
URL: https://issues.jboss.org/browse/RF-13126
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-tables
Affects Versions: 5.0.0.Alpha1
Environment: Windows / Tomcat 7 / JDK 1.7
Reporter: Steven W.
In prior 3.x release the ExtendedDataTable control supported TableState data for sizing of columns - this worked relatively well *however* there is/was a bug such that the columns headers above the table did *not* align properly with the data rows of the table below; this could be partially accommodated by specifying a size for the column (in the TableState data) that was wider than the longest string in the column data as he initial / minimum size.
In subsequent release (in 4.x time frame I believe) the control was refactored and the TableState capability as a whole was lost - I saw this in another report on the forum or Jira though not the same but other related issues may be https://issues.jboss.org/browse/RF-13094 and https://issues.jboss.org/browse/RF-13095 ; the report I remember reading, however, is that this functionality was lost during the refactoring and was then said to be restored in a subsequent release.
I am now using Version 5 of RichFaces to include the first milestone and latest (overnight) snapshot and am confirming this TableState table header sizing issue still remains, regardless of prior attempts to include TableState data recognition and, if/as so, the widths of the column headers does not respect the TableState data nor do they conform to the column widths of the data in the rows below.
--
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
11 years, 3 months
[JBoss JIRA] (RF-13102) rich:calendar with date pattern- input gets cleared on click
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/RF-13102?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on RF-13102:
----------------------------------------------
Juraj Huska <jhuska(a)redhat.com> made a comment on [bug 994012|https://bugzilla.redhat.com/show_bug.cgi?id=994012]
I have done patch testing. It solves the problem and I have not found any other regression.
Could you please proceed with patch uploading ?
> rich:calendar with date pattern- input gets cleared on click
> ------------------------------------------------------------
>
> Key: RF-13102
> URL: https://issues.jboss.org/browse/RF-13102
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.2.3.Final, 4.3.2
> Reporter: Jonáš Trantina
> Assignee: Brian Leathem
> Fix For: 4.3.4
>
>
> When a rich:calendar component has datePattern without a day (e.g. MM/yyyy) then selected date is cleared when opening the calendar (you can see today date instead of the previously selected date).
> However, when the form is sent, the value is correctly assigned to the binded value.
> Example:
> {noformat}
> <rich:calendar value="#{richBean.date}" datePattern="yyyy-MM"/>
> {noformat}
--
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
11 years, 3 months
[JBoss JIRA] (RF-13098) Regression: mediaOutput broken for CDI MediaData beans
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RF-13098?page=com.atlassian.jira.plugin.s... ]
Matej Novotny commented on RF-13098:
------------------------------------
I have verified this issue according to description on this page.
I have manages to reproduce the exception. CDI bean which extends Serializable throws the above mentioned expection. However CDI bean which extends SerializableResource does not throw any exception.
Source code can be found here: [https://github.com/richfaces/richfaces-qa/tree/RF-13098]
Steps to reproduce:
1) Deploy metamer on Jboss AS 7.1.1.Final
2) Load this page: [http://localhost:8080/metamer/faces/components/a4jMediaOutput/rf13098.xhtml]
3) Only one image shows, the other one causes exception. See the exception on the console.
> Regression: mediaOutput broken for CDI MediaData beans
> ------------------------------------------------------
>
> Key: RF-13098
> URL: https://issues.jboss.org/browse/RF-13098
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.3
> Reporter: Marek Schmidt
> Assignee: Matej Novotny
> Labels: regression
>
> https://issues.jboss.org/browse/RF-13089 introduced a regression for a4j:mediaOutput component
> Having a
> {code}
> <a4j:mediaOutput element="img" cacheable="true" session="true" createContent="#{mediaBean.paint}" value="#{mediaData}" mimeType="image/jpeg"/>
> {code}
> with mediaData being a CDI bean, e.g.
> {code}
> @javax.inject.Named("mediaData")
> @javax.enterprise.context.RequestScoped
> public class MediaData implements Serializable
> {code}
> the following exception occurs:
> {code}10:39:27,997 SEVERE [org.richfaces.log.Resource] (http-/127.0.0.1:8080-1) Input error for deserialize data : java.io.InvalidClassException: Unauthorized deserialization attempt; org.jboss.weld.bean.proxy.util.SerializableClientProxy
> at org.richfaces.util.LookAheadObjectInputStream.resolveClass(LookAheadObjectInputStream.java:93) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1610) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1769) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1989) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1913) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1796) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1704) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1342) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) [rt.jar:1.7.0_25]
> at org.richfaces.util.Util.decodeObjectData(Util.java:237) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.resource.DefaultCodecResourceRequestData.getData(DefaultCodecResourceRequestData.java:97) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:337) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:156) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> {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
11 years, 3 months