[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2534) inline email attachments not showing up properly
by sandy brydon (JIRA)
inline email attachments not showing up properly
------------------------------------------------
Key: JBSEAM-2534
URL: http://jira.jboss.com/jira/browse/JBSEAM-2534
Project: JBoss Seam
Issue Type: Patch
Components: Mail
Affects Versions: 2.0.1.CR2
Environment: JBoss-4.2.1.GA
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-241)
Mozilla Thunderbird version 2.0.0.9 (20071031)
Apple Mail Version 2.1.2 (753)
Gmail
Hotmail
Reporter: sandy brydon
Assigned To: Pete Muir
Priority: Minor
what is being produced:
Header...
Content-Type: multipart/mixed; boundary="outer-boundary"
--outer-boundary
Content-Type: image/gif; charset=ISO-8859-1; name=logo.gif
Content-Transfer-Encoding: base64
Content-ID: <image-content-id>
Content-Disposition: inline; filename=logo.gif
BASE64=ENCODED=IMAGE=DATA==
--outer-boundary
Content-Type: multipart/alternative; boundary="inner-boundary"
Content-Disposition: inline
--inner-boundary
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
my plain text
--inner-boundary
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<html>
<body>
my html text<br />
<img src="cid:image-content-id" />
</body>
</html>
--inner-boundary--
--outer-boundary--
what i think should be there (i'm no email expert)
Header...
Content-Type: multipart/alternative; boundary="outer-boundary"
--outer-boundary
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
my plain text
--outer-boundary
Content-Type: multipart/related;
boundary="inner-boundary"
--inner-boundary
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<body>
my html text<br />
<img src="cid:image-content-id" />
</body>
</html>
--inner-boundary
Content-Type: image/gif; name="logo.gif"
Content-Transfer-Encoding: base64
Content-ID: <image-content-id>
Content-Disposition: inline; filename="logo.gif"
BASE64=ENCODED=IMAGE=DATA==
--inner-boundary--
--outer-boundary--
- it looks like Content-Disposition: inline; is on every content declaration, i don't know if this matters
- in order to have proper inline html image content it looks like both the file and the content it's being included in is required to be part of Content-Type: multipart/related; (http://tools.ietf.org/html/rfc2387)
symptoms as tested:
Mozilla Firefox
- displays the attached files, does not display inline
Apple Mail
- displays the attached files then the content of the email (images show up in both)
gmail
- shows as having attachments, prompts to display images - images display fine
hotmail
- shows as having attachments, prompts to display images - images display fine
... all of this is also described in the forum thread.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 8 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2309) UserTransaction.commit() may throw a RollbackException(), in that case don't try to perform a UserTransaction.rollback()
by Denis Forveille (JIRA)
UserTransaction.commit() may throw a RollbackException(), in that case don't try to perform a UserTransaction.rollback()
------------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-2309
URL: http://jira.jboss.com/jira/browse/JBSEAM-2309
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.0.0.GA, 1.2.1.GA
Reporter: Denis Forveille
In the org.jboss.seam.util.Work class, the call to userTransaction.commit() is surrounded by a try/catch(Exception). In the catch block, if an exception occurs during the commit, a UserTransaction.rollback() is attempted. This may fail as the UserTransaction.commit() may throw a RollbackException, and in that case the UserTransaction ihas already been rollbacked. So an attempt to perform a rollback on the UserTransaction result in an illegalstate exception. This happens to us when something goes wrong in the beforeCommit() methods and hibernate throws a StaleObjectStateException()
We use seam 1.2.1 + POJO + WebSphere v61.0..13
The code could be something like this (Class Work.java):
try {
T result = work();
if (begin) {
log.debug("committing transaction");
userTransaction.commit();
}
return result;
} catch (Exception e) {
if (begin) {
log.debug("rolling back transaction");
if (userTransaction.getStatus() != STATUS_NO_TRANSACTION) {
userTransaction.rollback();
}
}
throw e;
}
Or the code could explicitely catch the RollbackException
This could be applied at any place in the code when a UserTransaction.commit() is called.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 9 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-884) ICEFaces dataPaginator causes duplicate ID exception
by henrik lindberg (JIRA)
ICEFaces dataPaginator causes duplicate ID exception
----------------------------------------------------
Key: JBSEAM-884
URL: http://jira.jboss.com/jira/browse/JBSEAM-884
Project: JBoss Seam
Issue Type: Bug
Components: ICE Faces Integration
Affects Versions: 1.1.6.GA
Environment: Seam 1.1.6.GA, ICEFaces 1.5.3
Reporter: henrik lindberg
Assigned To: Gregory Dick
Priority: Critical
When using a data paginator with a data table duplicate ids are created for all paginator facets except the first added facet.
The attached code illustrates the problem. Use the facelet to add test data, a duplicate id exception is thrown when a new test data is added.
Refresh the page (using browser) to see that data was added, try to add another (refresh again).
Editing out all facets for the paginator except one makes the code work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 9 months