[displaytag-devel] [jira] (DISPL-688) CSV export fixes (patch included)
Title: Message Title
Michael Osipov commented on an issue
Re: CSV export fixes (patch included)
Here is the Excel-compatible version: {code:java} /** * Excelkompatibler CSV-Export: * ol * liFeldtrenner muss ein Semikolon sein./li * liBei UTF-8 Kodierung stronga * href="" href="http://wiki.sdn.sap.com/wiki/display/ABAP/Excel+files+-+CSV+format" style="color: #3b73af; text-decoration: none">http://wiki.sdn.sap.com/wiki/display/ABAP/Excel+files+-+CSV+format * muss/a/strong der BOM vorhanden sein, sonst ist die Datei fr Excel * nicht sauber lesbar. Obwohl der BOM a * href="" href="http://unicode.org/faq/utf_bom.html#bom5" style="color: #3b73af; text-decoration: none">http://unicode.org/faq/utf_bom.html#bom5nicht empfohlen/a wird bei * UTF-8/li. * /ol */ public class ExcelCompatibleCsvView extends CsvView { @Override protected String getDocumentStart() { // Write Byte Order Mark return \ufeff; } @Override protected String getCellEnd() { return ;; } @Override protected String escapeColumnValue(Object value) { String stringValue = StringUtils.trim(value.toString()); if (!StringUtils.containsNone(stringValue, new char[] { '\n', ';' })) { return \ + //$NON-NLS-1$ StringUtils.replace(stringValue, \, \\\) + \; //$NON-NLS-1$ //$NON-NLS-2$ //$NON-NLS-3$ } return stringValue; } } {code}
Add Comment
DisplayTag / DISPL-688
CSV export fixes (patch included)
* UTF8 header needs to be captured before we reset the headers. * Line feeds caused spreadsheet applications to render columns incorrectly. * Added BOM to csv export file so spreadsheet applications know what to display text as.
[displaytag-devel] [jira] (DISPL-688) CSV export fixes (patch included)
Title: Message Title
Michael Osipov edited a comment on an issue
Re: CSV export fixes (patch included)
Notreally,becauseyoudonotknowwhoaregoingtobetheconsumersofthosefiles.TheycodechokeontheBOM.Noadditinalpropertynecessary.Itisenoughtoprovidean{ { ExcelCompatibleCsvView} } andleavingtheoriginalonealone.ThisiswhatIdidanditworksflawlessly.Asmentionedbefore,Icansharethatcode.
Add Comment
DisplayTag / DISPL-688
CSV export fixes (patch included)
* UTF8 header needs to be captured before we reset the headers. * Line feeds caused spreadsheet applications to render columns incorrectly. * Added BOM to csv export file so spreadsheet applications know what to display text as.
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
--
___
displaytag-devel mailing list
displaytag-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] (DISPL-688) CSV export fixes (patch included)
Title: Message Title
Michael Osipov edited a comment on an issue
Re: CSV export fixes (patch included)
Notreally,becauseyoudonotknowwhoaregoingtobetheconsumersofthosefiles.TheycodechokeontheBOM. JustbecauseMicrosoftistoostupidtowritedecentsoftware,weshouldn'tfollow. Noadditinalpropertynecessary.Itisenoughtoprovidean{ExcelCompatibleCsvView}andleavingtheoriginalonealone.ThisiswhatIdidanditworksflawlessly.Asmentionedbefore,Icansharethatcode.
Add Comment
DisplayTag / DISPL-688
CSV export fixes (patch included)
* UTF8 header needs to be captured before we reset the headers. * Line feeds caused spreadsheet applications to render columns incorrectly. * Added BOM to csv export file so spreadsheet applications know what to display text as.
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
--
___
displaytag-devel mailing list
displaytag-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] (DISPL-688) CSV export fixes (patch included)
Title: Message Title Michael Osipov commented on an issue Re: CSV export fixes (patch included) Not a good idea to add a BOM for two reasons: 1. If you read Unicode specs, it clearly says that a BOM is redundant 2. This is solely a Excel problem The give CSV exporter should a neutral, though you can provide a subclass for Excel. I have a valid one for our projects. Excel is then able to ready any Unicode char. Add Comment DisplayTag / DISPL-688 CSV export fixes (patch included) * UTF8 header needs to be captured before we reset the headers. * Line feeds caused spreadsheet applications to render columns incorrectly. * Added BOM to csv export file so spreadsheet applications know what to display text as. This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) -- ___ displaytag-devel mailing list displaytag-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] (DISPL-687) I18nJstlAdapter ignores locale from other scopes than session
Michael Osipov commented on DISPL-687 I18nJstlAdapter ignores locale from other scopes than session Have you tried to contact Fabrizio? I have planned this for a long time but stalled due to time problems. I have filed and patched many issued here. 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 -- LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151iu=/4140/ostg.clktrk___ displaytag-devel mailing list displaytag-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] (DISPL-687) I18nJstlAdapter ignores locale from other scopes than session
Michael Osipov
created DISPL-687
I18nJstlAdapter ignores locale from other scopes than session
Issue Type:
Bug
Affects Versions:
1.2
Assignee:
Unassigned
Components:
I18N
Created:
09/Aug/13 9:02 AM
Description:
Say you have called fmt:setlocale ... scope=page|request
Display is not able to determine anymore because it thinks that the locale is always in the session. Sometimes one want to change the locale just for the page or request.
Unfortunately, the LocaleResolver accepts a request only. Thus, {{Config.find}} cannot be used. The interface has to be changed, and depending classes too.
I will provide a patch for soon.
Project:
DisplayTag
Priority:
Critical
Reporter:
Michael Osipov
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
--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with 2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031iu=/4140/ostg.clktrk___
displaytag-devel mailing list
displaytag-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] (DISPL-606) Page numbers localized using wrong locale
[ https://jira.codehaus.org/browse/DISPL-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=288006#comment-288006 ] Michael Osipov commented on DISPL-606: -- I have ran into the same issue. Very annoying. Have this patch applied and everything is fine again in DisplayTag. Page numbers localized using wrong locale - Key: DISPL-606 URL: https://jira.codehaus.org/browse/DISPL-606 Project: DisplayTag Issue Type: Bug Components: I18N, Paging/Sorting Affects Versions: 1.2 Reporter: Hilde Meuris Fix For: 1.3 Attachments: DISPL-606.patch, mixed formatting.jpg As stated in DISPL-564, localization of page numbers is not correct. DISPL-564 has been set to fixed, but in fact the problem has only been fixed partially, which results in a mixture of European and American formatting. The changed from DISPL-564 should also be performed to PaginatedListSmartListHelper.java (line 206) and SmartListHelper.java (line 289). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ displaytag-devel mailing list displaytag-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] (DISPL-471) Patch to allow displaytag users to specify the target encoding of export files
[
https://jira.codehaus.org/browse/DISPL-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=287814#comment-287814
]
Michael Osipov commented on DISPL-471:
--
I have found the error which is responsible for the incorrect encoding and
patched it: DISPL-674.
My CSV export works as desired now.
Patch to allow displaytag users to specify the target encoding of export files
--
Key: DISPL-471
URL: https://jira.codehaus.org/browse/DISPL-471
Project: DisplayTag
Issue Type: New Feature
Components: Export
Reporter: Frantz DEGRIGNY
Original Estimate: 30 minutes
Remaining Estimate: 30 minutes
It will be very useful to permit to the displaytag users to choose for the
export files a different encoding than the JSP page.
This will solve many national characters problems (as MS Excel cannot read
UTF-8 encoded files, for example).
This can be simply done with an ExportDelegate little patch which permits the
user to specify the traget encoding in the getMimeType() method of a custom
ExportView implementation. :
example :
public class ExcelCsvView extends CsvView {
public String getMimeType() {
return text/csv; charset=cp1252; //uses the Windows Latin-1
superset encoding
}
}
ExportDelegate patch :
--- ExportDelegate.java
+++ ExportDelegate.java
@@ -112,124 +112,131 @@
String characterEncoding = wrapper.getCharacterEncoding();
String wrappedContentType = wrapper.getContentType();
if (wrappedContentType != null
wrappedContentType.indexOf(charset) -1)
{
// charset is already specified (see #921811)
characterEncoding =
StringUtils.substringAfter(wrappedContentType, charset=);
}
+//the target encoding is already specified in contentType :
+if( contentType.indexOf(charset) -1)
+{
+ characterEncoding=StringUtils.substringAfter(contentType,
charset=);
+ contentType = contentType.substring(0,
contentType.indexOf(';')).trim();
+}
+
if (characterEncoding != null contentType.indexOf(charset) ==
-1) //$NON-NLS-1$
{
contentType += ; charset= + characterEncoding; //$NON-NLS-1$
}
A better solution (but a little more complicated) is to allow the encoding
specification with a taglib table property like this :
display:setProperty name=export.csv.encoding value=cp1252/ (But I
haven't found how to do this).
Frantz D.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
___
displaytag-devel mailing list
displaytag-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] (DISPL-675) Response character encoding is set on export even if the export type is a binary file
Michael Osipov created DISPL-675: Summary: Response character encoding is set on export even if the export type is a binary file Key: DISPL-675 URL: https://jira.codehaus.org/browse/DISPL-675 Project: DisplayTag Issue Type: Bug Components: Export Affects Versions: 1.2 Reporter: Michael Osipov Attachments: DISPL-675.patch The char encoding of the JSP is always appended to the repsonse.setContentType(String) even if the type is binary. This happens with and without the ResponseOverrideFilter. Patch is included. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ displaytag-devel mailing list displaytag-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] (DISPL-676) Some JUnit tests fail if VM locale language is not English
Michael Osipov created DISPL-676: Summary: Some JUnit tests fail if VM locale language is not English Key: DISPL-676 URL: https://jira.codehaus.org/browse/DISPL-676 Project: DisplayTag Issue Type: Bug Components: I18N Affects Versions: 1.2 Reporter: Michael Osipov Attachments: DISPL-676.patch In several methods a SimpleDateFormat with is used. I do have a German locale and therefore these tests fail. Patch is included. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ displaytag-devel mailing list displaytag-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] Created: (DISPL-669) I18nJstlAdapter creates a new session
I18nJstlAdapter creates a new session
-
Key: DISPL-669
URL: https://jira.codehaus.org/browse/DISPL-669
Project: DisplayTag
Issue Type: Bug
Reporter: Michael Osipov
Attachments: DISPL-669.patch
In line 83 this is executed
{code}
Locale locale = (Locale) Config.get(request.getSession(), Config.FMT_LOCALE);
{code}
This unwanted because I want to be in control of the session creation.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
uberSVN's rich system and user administration capabilities and model
configuration take the hassle out of deploying and managing Subversion and
the tools developers use with it. Learn more about uberSVN and get a free
download at: http://p.sf.net/sfu/wandisco-dev2dev
___
displaytag-devel mailing list
displaytag-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] Created: (DISPL-663) Export label und separation char have missing space char
Export label und separation char have missing space char
Key: DISPL-663
URL: http://jira.codehaus.org/browse/DISPL-663
Project: DisplayTag
Issue Type: Improvement
Components: Export
Affects Versions: 1.2
Reporter: Michael Osipov
Right now every export label looks like:
{noformat}
export.pdf.label=span class=export pdfPDF /span
{noformat}
It will include a superfluous space char in the link. I would be more
reasonable to remove the space in all export labels and modify the sepchar to:
{noformat}
export.banner.sepchar=\u0020|
{noformat}
--
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
--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
___
displaytag-devel mailing list
displaytag-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] Commented: (DISPL-646) POM config exposes unneeded dependencies to client apps
[ http://jira.codehaus.org/browse/DISPL-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=204816#action_204816 ] Michael Osipov commented on DISPL-646: -- DisplayTag would work without SFL4J, that's correct but you would need JCL anyway. What's the point. The bridge binding has been chosen as a mild migration path to native SLF4J logging. I mailed Fabrizio since I want to have the project leadership. I use this lib almost daily at work and patched some stuff already. Hopefully I will be able to fix those nasty bugs like this one. Mike POM config exposes unneeded dependencies to client apps --- Key: DISPL-646 URL: http://jira.codehaus.org/browse/DISPL-646 Project: DisplayTag Issue Type: Bug Components: Build/distribution Affects Versions: 1.2 Reporter: Jeff Jensen DisplayTag transitive dependencies cause erroneous configuration on client projects. Specifically, DisplayTag should depend on only slf4j-api in the compile scope, resulting in exposing only that required dependency to client apps, and the slf4j-log4j12 and jcl104-over-slf4j dependencies should be removed (or changed to test scope if wanted for local testing). slf4j-api would be a new direct dependency to DisplayTag. It currently is transitively brought in through the slf4j-log4j12 direct dependency. I noticed this because, after just adding DisplayTag to my web app, SLF4J gave error messages on multiple SLF4J bindings on app startup - one binding is correctly from my POM/app config (found in logback-classic) and the other is erroneously exposed transitively from DisplayTag's dependency slf4j-log4j12. See http://www.slf4j.org/codes.html#multiple_bindings for the SLF4J error. The root cause is the DisplayTag POM exposing slf4j-log4j12 and jcl104-over-slf4j dependencies. Client apps do not need those specifically, e.g. slf4j-log4j12 is not needed with Logback. This dependency configuration approach also forces client apps to have log4j on the classpath transitively from slf4j-log4j12. We do not use Log4J. -- 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 -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ displaytag-devel mailing list displaytag-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] Commented: (DISPL-218) Need the ability to search.
[ http://jira.codehaus.org/browse/DISPL-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=204838#action_204838 ] Michael Osipov commented on DISPL-218: -- Actually, I solution can easily be done w/o modifying displaytag at all. Put a form in your jsp. Read params, pass them to a filter iterator from Commons Collections and your search is done on the fly. This is it. Need the ability to search. --- Key: DISPL-218 URL: http://jira.codehaus.org/browse/DISPL-218 Project: DisplayTag Issue Type: New Feature Components: HTML Generation Reporter: Prathit Bondre Fix For: TBD Currently the grid taglib has the ability to sort, page , export etc. However it lacks tha aiblity to search a column for a piece of data. If the grid has 5000 rows with paging of 20 items per page, it is hard for the users to search a column for a value. This can be achived by writing custom code to do this but it would be nice if it was a part of the taglib where you could search on certain columns or all columns for a particular value. -- 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 -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ displaytag-devel mailing list displaytag-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] Commented: (DISPL-646) POM config exposes unneeded dependencies to client apps
[ http://jira.codehaus.org/browse/DISPL-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=204537#action_204537 ] Michael Osipov commented on DISPL-646: -- Jeff, I must admit, yes the POM is misconfigured. slf4j-log4j binding is absolutely useless. But I still do disagree, slf4j itself is not unnecessary. It completely replaces JCL because it's old, not performant as SFL4J and most people moved to SFL4J anyway. At least in my projects I use SFL4J exclusively. I excluded the false transitive deps. POM config exposes unneeded dependencies to client apps --- Key: DISPL-646 URL: http://jira.codehaus.org/browse/DISPL-646 Project: DisplayTag Issue Type: Bug Components: Build/distribution Affects Versions: 1.2 Reporter: Jeff Jensen DisplayTag transitive dependencies cause erroneous configuration on client projects. Specifically, DisplayTag should depend on only slf4j-api in the compile scope, resulting in exposing only that required dependency to client apps, and the slf4j-log4j12 and jcl104-over-slf4j dependencies should be removed (or changed to test scope if wanted for local testing). slf4j-api would be a new direct dependency to DisplayTag. It currently is transitively brought in through the slf4j-log4j12 direct dependency. I noticed this because, after just adding DisplayTag to my web app, SLF4J gave error messages on multiple SLF4J bindings on app startup - one binding is correctly from my POM/app config (found in logback-classic) and the other is erroneously exposed transitively from DisplayTag's dependency slf4j-log4j12. See http://www.slf4j.org/codes.html#multiple_bindings for the SLF4J error. The root cause is the DisplayTag POM exposing slf4j-log4j12 and jcl104-over-slf4j dependencies. Client apps do not need those specifically, e.g. slf4j-log4j12 is not needed with Logback. This dependency configuration approach also forces client apps to have log4j on the classpath transitively from slf4j-log4j12. We do not use Log4J. -- 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 -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ displaytag-devel mailing list displaytag-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] Commented: (DISPL-646) POM config exposes unneeded dependencies to client apps
[ http://jira.codehaus.org/browse/DISPL-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=20#action_20 ] Michael Osipov commented on DISPL-646: -- Hopefully you have noticed that DisplayTag uses JCL natively and thus it requires jcl over sfl4j and its transitive deps. Turing DisplayTag to slf4j native would require code changes. Using jcl over slf4j requires none and makes use of slf4j by default. POM config exposes unneeded dependencies to client apps --- Key: DISPL-646 URL: http://jira.codehaus.org/browse/DISPL-646 Project: DisplayTag Issue Type: Bug Components: Build/distribution Affects Versions: 1.2 Reporter: Jeff Jensen DisplayTag transitive dependencies cause erroneous configuration on client projects. Specifically, DisplayTag should depend on only slf4j-api in the compile scope, resulting in exposing only that required dependency to client apps, and the slf4j-log4j12 and jcl104-over-slf4j dependencies should be removed (or changed to test scope if wanted for local testing). slf4j-api would be a new direct dependency to DisplayTag. It currently is transitively brought in through the slf4j-log4j12 direct dependency. I noticed this because, after just adding DisplayTag to my web app, SLF4J gave error messages on multiple SLF4J bindings on app startup - one binding is correctly from my POM/app config (found in logback-classic) and the other is erroneously exposed transitively from DisplayTag's dependency slf4j-log4j12. See http://www.slf4j.org/codes.html#multiple_bindings for the SLF4J error. The root cause is the DisplayTag POM exposing slf4j-log4j12 and jcl104-over-slf4j dependencies. Client apps do not need those specifically, e.g. slf4j-log4j12 is not needed with Logback. This dependency configuration approach also forces client apps to have log4j on the classpath transitively from slf4j-log4j12. We do not use Log4J. -- 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 -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ displaytag-devel mailing list displaytag-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] Commented: (DISPL-203) Date Sorting with Table Decorator
[ http://jira.codehaus.org/browse/DISPL-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=204445#action_204445 ] Michael Osipov commented on DISPL-203: -- Guys, there is a format attribute on the column tag. You're done. Date Sorting with Table Decorator - Key: DISPL-203 URL: http://jira.codehaus.org/browse/DISPL-203 Project: DisplayTag Issue Type: Bug Components: Decorators Affects Versions: 1.0 Reporter: Narayanan A Fix For: TBD Attachments: Decorator.txt, work-around.txt Original Estimate: 1 minute Remaining Estimate: 1 minute Hello, I have been using display tag with column decorators in my project, recently there was case where we have to use the value in session to decide on the decoration of a column, As column decorator isn't supporting PageContext as of v1.0, i switched to Table decorator,everything works fine except sorting of Date Object Columns. The same column sorting is working fine with Column Decorator. Date based sorting is very important in the existing functionality and i would request you to kindly help me with this issue. Please find the code snippet attached. -- 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 -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ displaytag-devel mailing list displaytag-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] Commented: (DISPL-644) Problem with DisplayTag export option
[ http://jira.codehaus.org/browse/DISPL-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=204446#action_204446 ] Michael Osipov commented on DISPL-644: -- Attach the case as-is without wrapping proprietary crap. Problem with DisplayTag export option - Key: DISPL-644 URL: http://jira.codehaus.org/browse/DISPL-644 Project: DisplayTag Issue Type: Bug Components: Export Affects Versions: 1.1 Reporter: Rajesh Swain Priority: Critical Attachments: Error.doc On opening the file using the Export option (CSV, XL), i am getting the following error: The file is not in a recognizable format I am attaching the file, that shows the error. -- 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 -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ displaytag-devel mailing list displaytag-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] Commented: (DISPL-621) getOutputStream() has already been called for this response
[ http://jira.codehaus.org/browse/DISPL-621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=180486#action_180486 ] Michael Osipov commented on DISPL-621: -- It could have 2 reasons: 1. The buffer of the JSP has already been flushed. 64 KiB are not enough for 3000 records. 2. You did not use the ResponseOverrideFilter. Evaluate them. getOutputStream() has already been called for this response --- Key: DISPL-621 URL: http://jira.codehaus.org/browse/DISPL-621 Project: DisplayTag Issue Type: Bug Components: Export Affects Versions: 1.1.1 Reporter: Ranjit H. Dhongade Fix For: 1.1.1 Attachments: ShowReport.zip Original Estimate: 1 day Remaining Estimate: 1 day Hi All, Even if I new to display-tag , I have successfully explored all its features. Thanks for every thing u have given in it. But one of the features of exporting PDF is not working when something round 3000 plus records contains in a jsp showing reports. I am getting following exception when trying to export to PDF (For CSV, Excel and XML I m not getting any error):- HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception org.apache.jasper.JasperException: java.lang.IllegalStateException: getOutputStream() has already been called for this response org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:522) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:410) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:696) org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:667) org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:808) org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:781) org.apache.jsp.ShowReport_jsp._jspService(ShowReport_jsp.java:354) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:374) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) root cause java.lang.IllegalStateException: getOutputStream() has already been called for this response org.apache.catalina.connector.Response.getWriter(Response.java:610) org.apache.catalina.connector.ResponseFacade.getWriter(ResponseFacade.java:198) org.apache.jasper.runtime.JspWriterImpl.initOut(JspWriterImpl.java:125) org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:118) org.apache.jasper.runtime.PageContextImpl.release(PageContextImpl.java:188) org.apache.jasper.runtime.JspFactoryImpl.internalReleasePageContext(JspFactoryImpl.java:118) org.apache.jasper.runtime.JspFactoryImpl.releasePageContext(JspFactoryImpl.java:77) org.apache.jsp.error_jsp._jspService(error_jsp.java:146) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:374) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:696) org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:667) org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:808) org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:781) org.apache.jsp.ShowReport_jsp._jspService(ShowReport_jsp.java:354) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:374) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342)
[displaytag-devel] [jira] Commented: (DISPL-592) Excel export shows only sublists
[ http://jira.codehaus.org/browse/DISPL-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=180018#action_180018 ] Michael Osipov commented on DISPL-592: -- I misunderstood the concept of the TableWriteTemplate and Default and non-Default views. Using ExcelHssfView.java instread of DefaultHssfExportView.java resolves the issue! Excel export shows only sublists Key: DISPL-592 URL: http://jira.codehaus.org/browse/DISPL-592 Project: DisplayTag Issue Type: Bug Components: Export Affects Versions: 1.1.1 Reporter: Michael Osipov Priority: Critical Attachments: DISPL-592.patch I do export my tables with the org.displaytag.export.excel.DefaultHssfExportView class. My export.amount is set to list and not page. Doing HTML, PDF, XML the export contains the entire list. Doing an Excel export reveals the same page as HTML. I tracked down the bug I reaized that HTML Export and Excel Export subclass TableWriterTemplate which always says in #writeTableBody rowIterator = model.getRowIterator(false); Setting to rowIterator = model.getRowIterator(model.getProperties().getExportFullList()); does not completely resolve it because HTML shows everything. I have attached a patch with resolves the issue but I do think that this can be done better and cleaner for both (html, xls) types. -- 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 -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ displaytag-devel mailing list displaytag-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] Commented: (DISPL-487) escapeXml attribute doesn't escape spaces to nbsp;
[ http://jira.codehaus.org/browse/DISPL-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=165450#action_165450 ] Michael Osipov commented on DISPL-487: -- From my point of view, this bug is invalid. a space (0x20) does not equal a non-breaking space. Thus it cannot be replaced with it. escapeXml attribute doesn't escape spaces to nbsp; --- Key: DISPL-487 URL: http://jira.codehaus.org/browse/DISPL-487 Project: DisplayTag Issue Type: Bug Affects Versions: 1.1 Reporter: daniel weijers Within our project data is read from a database and displayed via the displaytag table. The escapeXml=true is set for the column tag. We expected to have dataName to be escaped into nbsp;nbsp;Name. Is it possible to have the escapeXml working for space? This doesn't happen. Note: It looks like only the en ' are transformed to there respective amp quot en apos; No other characters are escaped. The possibility of having a global (configuration) setting for the escapXml (like the defaultHtmlEscape of Spring) would be great! -- 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 -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ displaytag-devel mailing list displaytag-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] Commented: (DISPL-425) Case Insensitive Sorting
[ http://jira.codehaus.org/browse/DISPL-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=165451#action_165451 ] Michael Osipov commented on DISPL-425: -- This but is rather invalid. Declare a case-insensitive decorator and that's it! Case Insensitive Sorting Key: DISPL-425 URL: http://jira.codehaus.org/browse/DISPL-425 Project: DisplayTag Issue Type: Bug Components: Paging/Sorting Affects Versions: 1.1 Reporter: Barry Gerdsen Priority: Minor Regarding the use of DisplayTag 1.1, I noticed that Fabrizio posted on the codehaus site the following note: fabrizio giustina [31/Dec/05 08:21 AM] The DefaultComparator used in displaytag 1.1 is configured with a low strength so it will ignore case and accents by default (only if objects are already Strings). We have recently updated to Displaytag version 1.1 (we used to use version 1.0) and have found this not to be the case. Is there perhaps a new property that I should be adding in order for a column sort to be case insensitive ? Any assistance you could provide would be greatly appreciated. Sincerely, Barry Gerdsen -- 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 -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ displaytag-devel mailing list displaytag-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] Created: (DISPL-594) HTML export and Excel Hssf export share too much code
HTML export and Excel Hssf export share too much code - Key: DISPL-594 URL: http://jira.codehaus.org/browse/DISPL-594 Project: DisplayTag Issue Type: Bug Components: Export, HTML Generation Affects Versions: 1.1.1 Reporter: Michael Osipov Priority: Critical I recently ran into some problems with the Excel ASCII export and had to switch to the POI (binary) export which resolved my problems. Another issued popped up: When declaring maxWords or maxColumns on a column they are handled correctly in HTML. Using an export function would imply that this feature is ignored since this feature is only necessary in HTML. Doing an Excel export results in the same bevahior as in HTML which is incorrect. I checked the code and noticed that HTML and Excel share the same base. HTML: HTMLTableWriter = ... = TableWriterTemplate Excel: HssfTableWriter = ... = TableWriterTemplate This means that they share the implemented methods in the abstract class and share too much code, Excel output resebles the HTML one. The codes needs to be more separated! This bug is related to my other issue: DISPL-592 -- 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 -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ displaytag-devel mailing list displaytag-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] Created: (DISPL-592) Excel export shows only sublists
Excel export shows only sublists Key: DISPL-592 URL: http://jira.codehaus.org/browse/DISPL-592 Project: DisplayTag Issue Type: Bug Components: Export Affects Versions: 1.1.1 Reporter: Michael Osipov Priority: Critical Attachments: DISPL-592 I do export my tables with the org.displaytag.export.excel.DefaultHssfExportView class. My export.amount is set to list and not page. Doing HTML, PDF, XML the export contains the entire list. Doing an Excel export reveals the same page as HTML. I tracked down the bug I reaized that HTML Export and Excel Export subclass TableWriterTemplate which always says in #writeTableBody rowIterator = model.getRowIterator(false); Setting to rowIterator = model.getRowIterator(model.getProperties().getExportFullList()); does not completely resolve it because HTML shows everything. I have attached a patch with resolves the issue but I do think that this can be done better and cleaner for both (html, xls) types. -- 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 -- Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com ___ displaytag-devel mailing list displaytag-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] Commented: (DISPL-379) Grouping is performned by default if you don't define any columns
[ http://jira.codehaus.org/browse/DISPL-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=155995#action_155995 ] Michael Osipov commented on DISPL-379: -- I ran into this problem last week too. Well, the problem ist extremely easy to fix. Don't unterstand why no one of you took it on. Grouping is performned by default if you don't define any columns - Key: DISPL-379 URL: http://jira.codehaus.org/browse/DISPL-379 Project: DisplayTag Issue Type: Bug Components: Tag Library Affects Versions: 1.1 Reporter: Anthony Gerrard Fix For: TBD Attachments: ColumnGroup.jsp, DISPL-379.patch Steps: * Define a table but don't define any columns * The columns are grouped as if you've specified group=1 etc on each of the columns This did not happen in version 1.0 and is contrary to the documentation for display:column If this attribute is not included, then no grouping is performed. See attached for jsp to reproduce the error. I'm using no columns for a page that runs user defined sql reports. I could specify the columns by iterating over the first row but don't want to as its more code and this used to work fine. -- 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 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ displaytag-devel mailing list displaytag-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] Created: (DISPL-575) Dynamic table/no title or titleKey capitalizes the propertyName
Dynamic table/no title or titleKey capitalizes the propertyName --- Key: DISPL-575 URL: http://jira.codehaus.org/browse/DISPL-575 Project: DisplayTag Issue Type: Improvement Components: HTML Generation Affects Versions: 1.1.1 Reporter: Michael Osipov Priority: Minor I think that it is really annoying that my keys are capitalized. The headerCell should pass them as-is. If I really want to capitalize them, I should do it explicitly in some manner. I have fixes this. -- 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 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ displaytag-devel mailing list displaytag-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] Commented: (DISPL-481) Loading properties from different package
[ http://jira.codehaus.org/browse/DISPL-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=129758#action_129758 ] Michael Osipov commented on DISPL-481: -- 1. you can patch displaytag yourself for your request within 60 seconds 2. how is displaytag able to know which is your package without have a config file at a default place telling it?? this is a paradoxon! Loading properties from different package - Key: DISPL-481 URL: http://jira.codehaus.org/browse/DISPL-481 Project: DisplayTag Issue Type: Improvement Components: Configuration Affects Versions: 1.0, 1.1, 1.1.1 Reporter: Igal Corcos Priority: Minor It is currently not possible to have displaytag load its resource bundles from a location other than the root package of a web app. Many developers package resource files in a sub-package such as com.acme.resources. It would be extremely useful to be able to package displaytag.properties files in the same location as other resources. -- 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 - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ displaytag-devel mailing list displaytag-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] Commented: (DISPL-516) Missing jsp-api dependency in maven's pom.xml
[
http://jira.codehaus.org/browse/DISPL-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124448
]
Michael Osipov commented on DISPL-516:
--
scope provided is sufficient.
Missing jsp-api dependency in maven's pom.xml
-
Key: DISPL-516
URL: http://jira.codehaus.org/browse/DISPL-516
Project: DisplayTag
Issue Type: Bug
Components: Build/distribution
Affects Versions: 1.1.1
Reporter: Tomas Kramar
Priority: Trivial
When the decorator is used, compilation fails with message:
RowIdDecorator.java:[5,7] cannot access javax.servlet.jsp.PageContext
class file for javax.servlet.jsp.PageContext not found
public class RowIdDecorator extends TableDecorator {
This can be fixed by adding the following code into pom.xml:
dependency
groupIdjspapi/groupId
artifactIdjsp-api/artifactId
version2.0/version
scopecompile/scope
/dependency
This should be added to displaytag's pom.xml so it can be included
transitively.
--
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
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
displaytag-devel mailing list
displaytag-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/displaytag-devel
[displaytag-devel] [jira] Commented: (DISPL-509) Add property to set request header Content-Disposition
[ http://jira.codehaus.org/browse/DISPL-509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124311 ] Michael Osipov commented on DISPL-509: -- I have tested with properties and setProperty, all worked fine. I hope this can be incorporated into 1.1.2 Add property to set request header Content-Disposition -- Key: DISPL-509 URL: http://jira.codehaus.org/browse/DISPL-509 Project: DisplayTag Issue Type: New Feature Components: Export Affects Versions: 1.1.1 Reporter: Michael Osipov Attachments: DISPL-509.patch I'd like to be able to do the following: either in properties or by setProperty tag export.export name.content_disposition = (inline|attachment) default should be attachment results in response.setHeader(Content-Disposition, inline; filename=name.pdf); or results in response.setHeader(Content-Disposition, attachment; filename=name.pdf); The filename can be set, the serve type not. It is extremely annoying if my browser window turns into my an exported xml or inline pdf or else. -- 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 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ displaytag-devel mailing list displaytag-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/displaytag-devel
