[JBoss JIRA] Created: (JBSEAM-4664) [excel] Need ability to choose between Content-Disposition: inline and Content-Disposition: attachment for downloads
by Eric Jung (JIRA)
[excel] Need ability to choose between Content-Disposition: inline and Content-Disposition: attachment for downloads
--------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-4664
URL: https://jira.jboss.org/browse/JBSEAM-4664
Project: Seam
Issue Type: Patch
Components: Excel
Affects Versions: 2.2.1.CR1, 2.2.0.GA, 2.2.0.CR1, 2.1.2.GA, 2.1.2.CR2, 2.1.2.CR1, 2.1.1.GA, 2.1.1.CR2, 2.1.1.CR1, 2.1.0.SP1, 2.1.0.GA, 2.0.3.CR1, 2.0.2.SP1, 2.0.1.GA, 2.0.0.GA, 1.2.1.GA, 1.2.0.GA, 1.1.6.GA, 1.1.5.GA, 1.1.1.GA, 1.1.0.GA, 1.0.1, 1.0, 2.2.1.CR2, 3.0.0.BETA1, The future
Reporter: Eric Jung
Attachments: UIWorkbook.java.diff
When downloading an Excel workbook, org.jboss.seam.excel.ui.UIWorkbook always sends the HTTP response header "Content-Disposition: inline; filename="xxxx.xls" where xxxx is the value of e:workbook's filename attribute.
This header causes problems on some installations of IE 6, 7, and 8 with Excel 2002. Depending on how some settings are configured in the OS, the document may never open after download.
Changing the HTTP response header value to "Content-Disposition: attachment; filename="xxxx.xls" solves the problem. Notice the only difference is the word "attachment" vs. "inline". I would like the capability to choose between these two, just like jboss-seam-pdf.jar provides the same capability with its org.jboss.seam.pdf.ui.UIDocument:
<pdf:document title="Some Title" disposition="attachment"> ... </pdf:document>
Mail attachments in Seam provide the same capability:
<m:attachment value="#{person.photo}" contentType="image/png" disposition="inline"/>
I'm attaching a patch against Seam 2.2 trunk which provides this capability. With this patch, we can now write:
<e:workbook type="jxl" disposition="attachment" ...> ... </e:workbook>
or
<e:workbook type="jxl" disposition="inline" ...> ... </e:workbook>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] Created: (JBSEAM-4813) Data not displayed in log trace message when creating cell
by Derek MacDonald (JIRA)
Data not displayed in log trace message when creating cell
----------------------------------------------------------
Key: JBSEAM-4813
URL: https://issues.jboss.org/browse/JBSEAM-4813
Project: Seam 2
Issue Type: Bug
Components: Excel
Affects Versions: 2.2.2.Final
Reporter: Derek MacDonald
Priority: Minor
Fix For: 2.3.0.ALPHA
#2 is included twice in a log.debug() invocation's String parameter when #3 should be used to display data placed in the created cell.
org/jboss/seam/excel/jxl/JXLHelper.java Line 681:
677 public static WritableCell createCell(int column, int row, CellType type, Object data, WritableCellFormat cellFormat)
678 {
679 if (log.isTraceEnabled())
680 {
681 log.trace("Creating cell at (#0,#1) of type #2 with data #2", column, row, type, data);
682 }
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] Created: (JBSEAM-4821) Typos in documentation
by Jozef Hartinger (JIRA)
Typos in documentation
----------------------
Key: JBSEAM-4821
URL: https://issues.jboss.org/browse/JBSEAM-4821
Project: Seam 2
Issue Type: Bug
Components: Documentation Issues
Affects Versions: 2.2.2.Final
Reporter: Jozef Hartinger
Assignee: Marek Novotny
Priority: Minor
Fix For: 2.3.0.ALPHA
Annotations.xml: spell check failed on 'annotationed'
Annotations.xml: spell check failed on 'precendence'
Annotations.xml: spell check failed on 'signalling'
Cache.xml: spell check failed on 'depoyment'
ClusteringAndEJBPassivation.xml: spell check failed on 'addressses'
ClusteringAndEJBPassivation.xml: spell check failed on 'Ejb' (should be EJB)
ClusteringAndEJBPassivation.xml: spell check failed on 'infrastruture'
ClusteringAndEJBPassivation.xml: spell check failed on 'prematurally'
ClusteringAndEJBPassivation.xml: spell check failed on 'reassociate' (should be re-associate)
ClusteringAndEJBPassivation.xml: spell check failed on 'thise'
ClusteringAndEJBPassivation.xml: spell check failed on 'tranfered'
ClusteringAndEJBPassivation.xml: spell check failed on 'transfered'
ClusteringAndEJBPassivation.xml: spell check failed on 'unserializing' (should be deserializing)
Concepts.xml: spell check failed on 'absense'
Concepts.xml: spell check failed on 'automagically'
Concepts.xml: spell check failed on 'dependecies'
Concepts.xml: spell check failed on 'Javabeans' (should be JavaBeans)
Concepts.xml: spell check failed on 'precedece'
Concepts.xml: spell check failed on 'precendence'
Concepts.xml: spell check failed on 'programatically'
Concepts.xml: spell check failed on 'threadsafeness'
Concepts.xml: spell check failed on 'visable'
Configuration.xml: repeated instance(s) of 'be'.
Configuration.xml: spell check failed on 'aggrevating'
Configuration.xml: spell check failed on 'compoenent'
Configuration.xml: spell check failed on 'thar'
Controls.xml: spell check failed on 'contol'
Controls.xml: spell check failed on 'occured'
Conversations.xml: spell check failed on 'could't'
Conversations.xml: spell check failed on 'overriden'
Conversations.xml: spell check failed on 'thats'
Dependencies.xml: spell check failed on 'libraies'
Drools.xml: spell check failed on 'alse'
Events.xml: spell check failed on 'propreties'
Excel.xml: spell check failed on 'childrens'
Excel.xml: spell check failed on 'ths'
Excel.xml: spell check failed on 'verically'
Getting_Started_With_JBoss_Tools.xml: spell check failed on 'arguements'
Getting_Started_With_JBoss_Tools.xml: spell check failed on 'deloyed'
Getting_Started_With_JBoss_Tools.xml: spell check failed on 'engieneer'
Glassfish.xml: repeated instance(s) of 'the'.
I18n.xml: spell check failed on 'hexidecimal'
Itext.xml: repeated instance(s) of 'to'.
Itext.xml: spell check failed on 'definied'
Jbpm.xml: spell check failed on 'jDPL'
Mail.xml: spell check failed on 'asynchrounously'
Mail.xml: spell check failed on 'musn't'
Persistence.xml: repeated instance(s) of 'be'.
Persistence.xml: spell check failed on 'loosly'
Persistence.xml: spell check failed on 'persisence'
Persistence.xml: spell check failed on 'vaues'
Preface.xml: repeated instance(s) of 'and'.
Remoting.xml: spell check failed on 'containining'
Rss.xml: spell check failed on 'elemenents'
Security.xml: spell check failed on 'chosing'
Security.xml: spell check failed on 'ompletely'
Security.xml: spell check failed on 'omputers'
Security.xml: spell check failed on 'overriden'
Security.xml: spell check failed on 'permisison'
Security.xml: spell check failed on 'precendence'
Security.xml: spell check failed on 'relevent'
Security.xml: spell check failed on 'Thie'
Security.xml: spell check failed on 'trival'
Security.xml: spell check failed on 'ublic'
Security.xml: spell check failed on 'umans'
Security.xml: spell check failed on 'uring'
Security.xml: spell check failed on 'utomated'
Testing.xml: spell check failed on 'Javadoc'
Testing.xml: spell check failed on 'testng' (should be TestNG)
Text.xml: spell check failed on 'Javadoc'
Tools.xml: repeated instance(s) of 'the'.
Tutorial.xml: repeated instance(s) of 'of'.
Tutorial.xml: repeated instance(s) of 'the'.
Tutorial.xml: spell check failed on 'achive'
Tutorial.xml: spell check failed on 'attibute'
Tutorial.xml: spell check failed on 'configration'
Validation.xml: spell check failed on 'Hiberate'
Validation.xml: spell check failed on 'higlighting'
Weblogic.xml: repeated instance(s) of 'the'.
Webservices.xml: spell check failed on 'defauls'
Websphere.xml: spell check failed on 'annd'
Websphere.xml: spell check failed on 'cutomized'
Websphere.xml: spell check failed on 'ejb'
Wicket.xml: spell check failed on 'automagically'
Wicket.xml: spell check failed on 'iinstrumentation'
Xml.xml: repeated instance(s) of 'the'.
Xml.xml: spell check failed on 'namespaced'
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] Created: (JBSEAM-4814) MAX_ROWS reached error message instead displays MAX_COLUMNS
by Derek MacDonald (JIRA)
MAX_ROWS reached error message instead displays MAX_COLUMNS
-----------------------------------------------------------
Key: JBSEAM-4814
URL: https://issues.jboss.org/browse/JBSEAM-4814
Project: Seam 2
Issue Type: Bug
Components: Excel
Affects Versions: 2.2.2.Final
Reporter: Derek MacDonald
Priority: Minor
Fix For: 2.3.0.ALPHA
When the 65535 row limit of a spreadsheet is reached, the generated exception's message mistakenly displays the limit as 255.
org/jboss/seam/excel/jxl/JXLExcelWorkbook.java Line 130:
129 if (currentRowIndex >= MAX_ROWS) {
130 throw new ExcelWorkbookException(Interpolator.instance()
131 .interpolate("Excel only supports {0} rows", MAX_COLUMNS));
132 }
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3355) SeamExpressionEvaluator gobbles up exceptions
by Wolfgang Schwendt (JIRA)
SeamExpressionEvaluator gobbles up exceptions
----------------------------------------------
Key: JBSEAM-3355
URL: https://jira.jboss.org/jira/browse/JBSEAM-3355
Project: Seam
Issue Type: Bug
Affects Versions: 2.1.0.BETA1
Reporter: Wolfgang Schwendt
Priority: Critical
Rev 8710 of org.jboss.seam.bpm.SeamExpressionEvaluator introduced a serious bug. If the invocation of the method expression (me.invoke(...)) throws an exception such as org.jboss.seam.security.AuthorizationException, the SeamExpressionEvaluator afterwards tries to evaluate the EL expression as a value expression. This of course results in a second exception thrown: PropertyNotFoundException. Consequently, the list "exceptions" has size > 2 (rather than just size==1), which results in SeamExpressionEvaluator throwing an ELException that does not wrap the exception which originally caused the method expression invocation to fail.
The bug was introduced because, compared with earlier versions, the try/catch-blocks for the method expression and value expression evaluation were changed and are now wrong. This is serious because it breaks the handling of any application exception thrown while evaluating the EL method expression, such as AuthorizationException.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] Created: (JBSEAM-4833) Erroneous integer divisions in Image.scaleToFit()
by Nicholas Oxhøj (JIRA)
Erroneous integer divisions in Image.scaleToFit()
-------------------------------------------------
Key: JBSEAM-4833
URL: https://issues.jboss.org/browse/JBSEAM-4833
Project: Seam 2
Issue Type: Bug
Components: JSF Controls
Affects Versions: 2.2.0.GA
Reporter: Nicholas Oxhøj
Priority: Minor
org.jboss.seam.ui.graphicImage.Image.scaleToFit(int height, int width) will most of the time just scale to the specified width, because it contains an error. The
ratios are calculated using integer division and will most likely both be 0.
Instead of
float hratio = height/getHeight();
float wratio = width/getWidth();
it should be
float hratio = (float) height/image.getHeight();
float wratio = (float) width/image.getWidth();
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] Created: (SEAMREMOTING-45) Uncaught exception: [Exception... "prompt aborted by user" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: resource:///components/nsPrompter.js :: openTabPrompt :: line 462" data: no]
by Denny Vriesman (JIRA)
Uncaught exception: [Exception... "prompt aborted by user" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: resource:///components/nsPrompter.js :: openTabPrompt :: line 462" data: no]
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: SEAMREMOTING-45
URL: https://issues.jboss.org/browse/SEAMREMOTING-45
Project: Seam Remoting
Issue Type: Bug
Affects Versions: 3.0.0.Final
Environment: Windows 7, JBOSS 4.2.3, Monjara 2.0.3, Weld-Servlet-1.1.1-final, Seam-Remoting 3
Reporter: Denny Vriesman
I was trying to make seam-remoting to work with an existing application that already was using JSF ajax (f:ajax tag).
However, the firefox 6.0 was ever raising the error bellow on javascript console:
Uncaught exception: [Exception... "prompt aborted by user" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: resource:///components/nsPrompter.js :: openTabPrompt :: line 462" data: no]
My code was looking like:
<h:head>
<script type="text/javascript" src="#{facesContext.externalContext.requestContextPath}/seam/resource/remoting/resource/remote.js?compress=false"/>
<script type="text/javascript" src="#{facesContext.externalContext.requestContextPath}/seam/resource/remoting/interface.js?resourceBean"/>
<script>
function getResourceFromDashboardCallback(result) {
$.each(result, iterateResource);
}
</script>
...
...
</h:head>
...
<h:form>
...
...
<h:dataTable border="1" id="dashBoardTable" value="#{dashboardBean.dashboards}" var="dashBoardItem">
<h:column id="column1">
<f:facet name="header">
<h:outputText value="Paineis"></h:outputText>
</f:facet>
<h:commandLink value="#{dashBoardItem.label}" onclick="getResourceFromDashboard(#{dashBoardItem.uri});">
</h:column>
</h:dataTable>
</h:panelGroup>
...
...
</h:form>
When I've been clicked on CommandLink, the error's been throwed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months