[displaytag-devel] [jira] Created: (DISPL-656) Error in Documentation on Pagination Properties
Error in Documentation on Pagination Properties
---
Key: DISPL-656
URL: http://jira.codehaus.org/browse/DISPL-656
Project: DisplayTag
Issue Type: Bug
Components: Documentation
Reporter: Tony Gunter
Priority: Minor
Under the description of the default values for the
paging.banner.{full,first,last}, the href values are listed in quotes.
However, this results in broken linkes ... these values should not be in quotes.
Example:
span class=pagelinks [First/Prev] {0} [ a href={3}Next/a/ a
href={4}Last/a] /span
Should actually be:
span class=pagelinks [First/Prev] {0} [ a href={3}Next/a/ a
href={4}Last/a] /span
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
___
displaytag-devel mailing list
displaytag-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] Commented: (DISPL-655) navigation (next/ previous) not working in displaytag
[
http://jira.codehaus.org/browse/DISPL-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=220388#action_220388
]
Tony Gunter commented on DISPL-655:
---
Are you using custom properties for paging.banner.first / paging.banner.last /
paging.banner.full? If so, you may have followed what was in the
documentation, and put quotes around your href placeholders. However, this
results in broken links. These placeholders should not have quotes around
them. For example:
span class=pagelinks [First/Prev] {0} [ a href={3}Next/a/ a
href={4}Last/a] /span
Should actually be:
span class=pagelinks [First/Prev] {0} [ a href={3}Next/a/ a
href={4}Last/a] /span
I have logged this as a defect against the documentation. If this is *not*
what you have, then I would suggest posting here the actual URLs shown when you
mouse over the link for Next and Previous.
navigation (next/ previous) not working in displaytag
-
Key: DISPL-655
URL: http://jira.codehaus.org/browse/DISPL-655
Project: DisplayTag
Issue Type: Wish
Components: Paging/Sorting
Affects Versions: 1.2
Reporter: Nihar R Mishra
Original Estimate: 1 minute
Remaining Estimate: 1 minute
I have used the code like this...
display:table name=ciLineDTOList pagesize=1 id=row sort=external
tr
display:column title=Select
s:textfield theme=simple name=choosen
value=%{#attr.row.measurement}/
/display:column
ciLineDTOList is having the value in it and it is displaying the first
page. But it is not able to display the other ones when I go next or
previous. That means the values are getting lost and it s showing NO DATA
FOUND at last.
Please help me.. Very Very urgent
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
___
displaytag-devel mailing list
displaytag-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] Commented: (DISPL-672) paging problem
[
https://jira.codehaus.org/browse/DISPL-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=283699#comment-283699
]
Tony Gunter commented on DISPL-672:
---
Maybe it's the double quotes inside your value?
i.e. div class=toolbar id=displayNavigator{0} {1} found, displayed from
{2} to {3} should be =div class='toolbar' id='displayNavigator'{0} {1}
found, displayed from {2} to {3}
You can place these directly into the jsp to test if you want. Also, don't
forget that you probably want to declare display strings for no items found,
one item found, and all items found (for when only one page of results is
returned):
display:setProperty name=paging.banner.no_items_found
value=br/span class='pagebanner'strong No {0} found./strong
br/br//span/
display:setProperty name=paging.banner.one_item_found
value=br/span class='pagebanner'strong One {0} found./strong
br/br//span/
display:setProperty name=paging.banner.all_items_found
value=br/span class='pagebanner'strong {0} {1} found, displaying all
{2}./strongbr/br//span/
display:setProperty name=paging.banner.some_items_found
value=br/span class='pagebanner'strong {0} {1} found, displaying {2} to
{3}./strongbr//span/
paging problem
--
Key: DISPL-672
URL: https://jira.codehaus.org/browse/DISPL-672
Project: DisplayTag
Issue Type: Bug
Components: Paging/Sorting
Affects Versions: 1.1
Reporter: Mauro
Hi everyone,
I'm new in using displaytag.
I'm using 1.1 version and I have the following problem.
I have to fix a problem in code made by an other person.
We have to display a list of element paging it at 100 at 100 if the number of
elements is more than 100.
The problem is that in the page 1 I see 1250 items found, diplayed from 1 to
100, but also in the second page, in the third and go on, I see the same
message, instead I'd like to see ...displayed from 101 to 200, ...201 to
300 and etc.
I have seen that there is a property called paging.banner.some_items_found
in the displaytag.property file and it's used to show that message, but it
does not work correctly.
Can anyone help me to solve the problem? Thanks to all
Here are some parts of my code
in the jsp page
display:table sort=external
requestURI=/abc.do?mth=pagingsensible=${param.sensible}
name=sessionScope.abcList
id=item
pagesize=100
htmlId=abcTable
class=dataGrid
style=border:0px;display:inline
excludedParams=*
decorator=
partialList=true
size=pageScope.pagListConf.totalList
offset=${pagListConf.offSet}
in the properties file
paging.banner.some_items_found=div class=toolbar
id=displayNavigator{0} {1} found, displayed from {2} to {3}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
___
displaytag-devel mailing list
displaytag-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] Commented: (DISPL-672) paging problem
[
https://jira.codehaus.org/browse/DISPL-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=283701#comment-283701
]
Tony Gunter commented on DISPL-672:
---
This is not a bug.
paging problem
--
Key: DISPL-672
URL: https://jira.codehaus.org/browse/DISPL-672
Project: DisplayTag
Issue Type: Bug
Components: Paging/Sorting
Affects Versions: 1.1
Reporter: Mauro
Hi everyone,
I'm new in using displaytag.
I'm using 1.1 version and I have the following problem.
I have to fix a problem in code made by an other person.
We have to display a list of element paging it at 100 at 100 if the number of
elements is more than 100.
The problem is that in the page 1 I see 1250 items found, diplayed from 1 to
100, but also in the second page, in the third and go on, I see the same
message, instead I'd like to see ...displayed from 101 to 200, ...201 to
300 and etc.
I have seen that there is a property called paging.banner.some_items_found
in the displaytag.property file and it's used to show that message, but it
does not work correctly.
Can anyone help me to solve the problem? Thanks to all
Here are some parts of my code
in the jsp page
display:table sort=external
requestURI=/abc.do?mth=pagingsensible=${param.sensible}
name=sessionScope.abcList
id=item
pagesize=100
htmlId=abcTable
class=dataGrid
style=border:0px;display:inline
excludedParams=*
decorator=
partialList=true
size=pageScope.pagListConf.totalList
offset=${pagListConf.offSet}
in the properties file
paging.banner.some_items_found=div class=toolbar
id=displayNavigator{0} {1} found, displayed from {2} to {3}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
___
displaytag-devel mailing list
displaytag-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] Created: (DISPL-673) CLONE - Displaytag breaks rendering in jsp without logging exceptions
CLONE - Displaytag breaks rendering in jsp without logging exceptions
-
Key: DISPL-673
URL: https://jira.codehaus.org/browse/DISPL-673
Project: DisplayTag
Issue Type: Bug
Components: Tag Library
Affects Versions: 1.1
Reporter: Tony Gunter
Fix For: 1.1
I use displaytag library in jsp like:
display:table
core:if test=${printFormat!='true'}
core:choose
.
/core:choose
/core:if
/display:table
And generating HTML fails probably because of errors during accessing beans
in display:table implemention. But nothing is logged by displaytag,
no jsp error is generated but all HTML rendering after display:table tag
is stopped.
Main issue is that it is so hard to find cause of the problem. Displaytag
should log some error at least, I have spent hours finding out where the
problem is. :(
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
___
displaytag-devel mailing list
displaytag-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] Commented: (DISPL-673) CLONE - Displaytag breaks rendering in jsp without logging exceptions
[
https://jira.codehaus.org/browse/DISPL-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=283703#comment-283703
]
Tony Gunter commented on DISPL-673:
---
I thought I could alter this issue once I cloned it. The application server is
not Tomcat. This occurs on OC4J 10.1.3, on paged tables that are tied to
rather large queries, if you click multiple displaytag links rapidly then OC4J
exhausts its displaytag resource pool and displaytag fails to perform cleanup.
There is a very good description of this problem in the comments for the
original issue.
CLONE - Displaytag breaks rendering in jsp without logging exceptions
-
Key: DISPL-673
URL: https://jira.codehaus.org/browse/DISPL-673
Project: DisplayTag
Issue Type: Bug
Components: Tag Library
Affects Versions: 1.1
Reporter: Tony Gunter
Fix For: 1.1
I use displaytag library in jsp like:
display:table
core:if test=${printFormat!='true'}
core:choose
.
/core:choose
/core:if
/display:table
And generating HTML fails probably because of errors during accessing beans
in display:table implemention. But nothing is logged by displaytag,
no jsp error is generated but all HTML rendering after display:table tag
is stopped.
Main issue is that it is so hard to find cause of the problem. Displaytag
should log some error at least, I have spent hours finding out where the
problem is. :(
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
___
displaytag-devel mailing list
displaytag-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] Commented: (DISPL-673) CLONE - Displaytag breaks rendering in jsp without logging exceptions
[
https://jira.codehaus.org/browse/DISPL-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=283704#comment-283704
]
Tony Gunter commented on DISPL-673:
---
http://jira.codehaus.org/browse/DISPL-314
CLONE - Displaytag breaks rendering in jsp without logging exceptions
-
Key: DISPL-673
URL: https://jira.codehaus.org/browse/DISPL-673
Project: DisplayTag
Issue Type: Bug
Components: Tag Library
Affects Versions: 1.1
Reporter: Tony Gunter
Fix For: 1.1
I use displaytag library in jsp like:
display:table
core:if test=${printFormat!='true'}
core:choose
.
/core:choose
/core:if
/display:table
And generating HTML fails probably because of errors during accessing beans
in display:table implemention. But nothing is logged by displaytag,
no jsp error is generated but all HTML rendering after display:table tag
is stopped.
Main issue is that it is so hard to find cause of the problem. Displaytag
should log some error at least, I have spent hours finding out where the
problem is. :(
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
___
displaytag-devel mailing list
displaytag-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/displaytag-devel
