John D. Ament | 18 Dec 14:51 2014
Picon

JMS 2.0 Spec JAR

All,


A few months ago I worked out a spec JAR for JMS 2.0 APIs, the purpose being to include it in apache projects.  You can see the code here:


I'd like to move this into the geronimo specs area and was looking to discuss it further.  I was reached out to this week by some folks claiming to be from the ActiveMQ/HornetQ community, claiming to have spoken to some members of the geronimo community about moving this forward.

Are you in fact interested in this donation?

Thanks,

John
Thomas Neidhart (JIRA | 12 Dec 23:22 2014
Picon

[jira] [Commented] (GERONIMO-6536) MimeBodyPart.setText(String, String, String) ignores subType


    [
https://issues.apache.org/jira/browse/GERONIMO-6536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244894#comment-14244894
] 

Thomas Neidhart commented on GERONIMO-6536:
-------------------------------------------

I have tested it with the latest provider snapshot and the problem is resolved.

Thanks a lot for the quick fix.

> MimeBodyPart.setText(String, String, String)  ignores subType
> -------------------------------------------------------------
>
>                 Key: GERONIMO-6536
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6536
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: mail
>            Reporter: Thomas Neidhart
>
> This has been detected as part of [EMAIL-147].
> When creating the mime message, we call MimeBodyPart.setText(String, String, String) with html as
subtype, but when calling this method, the subType is completely ignored and the resulting contentType
is always "text/plain".

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Hendrik Saly (JIRA | 12 Dec 17:52 2014
Picon

[jira] [Commented] (GERONIMO-6536) MimeBodyPart.setText(String, String, String) ignores subType


    [
https://issues.apache.org/jira/browse/GERONIMO-6536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244439#comment-14244439
] 

Hendrik Saly commented on GERONIMO-6536:
----------------------------------------

pls try again with specs 1.7.2-SNAPSHOT
(https://repository.apache.org/content/repositories/snapshots/org/apache/geronimo/specs/geronimo-javamail_1.4_spec/1.7.2-SNAPSHOT/),
javamail 1.9-SNAPSHOT impl refers to that

> MimeBodyPart.setText(String, String, String)  ignores subType
> -------------------------------------------------------------
>
>                 Key: GERONIMO-6536
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6536
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: mail
>            Reporter: Thomas Neidhart
>
> This has been detected as part of [EMAIL-147].
> When creating the mime message, we call MimeBodyPart.setText(String, String, String) with html as
subtype, but when calling this method, the subType is completely ignored and the resulting contentType
is always "text/plain".

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Hendrik Saly (JIRA | 12 Dec 17:49 2014
Picon

[jira] [Commented] (GERONIMO-6536) MimeBodyPart.setText(String, String, String) ignores subType


    [
https://issues.apache.org/jira/browse/GERONIMO-6536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244435#comment-14244435
] 

Hendrik Saly commented on GERONIMO-6536:
----------------------------------------

Revision 1644976

> MimeBodyPart.setText(String, String, String)  ignores subType
> -------------------------------------------------------------
>
>                 Key: GERONIMO-6536
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6536
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: mail
>            Reporter: Thomas Neidhart
>
> This has been detected as part of [EMAIL-147].
> When creating the mime message, we call MimeBodyPart.setText(String, String, String) with html as
subtype, but when calling this method, the subType is completely ignored and the resulting contentType
is always "text/plain".

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Thomas Neidhart (JIRA | 12 Dec 17:45 2014
Picon

[jira] [Commented] (GERONIMO-6536) MimeBodyPart.setText(String, String, String) ignores subType


    [
https://issues.apache.org/jira/browse/GERONIMO-6536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244427#comment-14244427
] 

Thomas Neidhart commented on GERONIMO-6536:
-------------------------------------------

The problem is in line 437 (http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-javamail_1.4_spec-1.7.1/src/main/java/javax/mail/internet/MimeBodyPart.java?view=markup):

{code}
 public void setText(String text, String charset, String subtype) throws MessagingException {
427 	// we need to sort out the character set if one is not provided.
428 	if (charset == null) {
429 	// if we have non us-ascii characters here, we need to adjust this.
430 	if (!ASCIIUtil.isAscii(text)) {
431 	charset = MimeUtility.getDefaultMIMECharset();
432 	}
433 	else {
434 	charset = "us-ascii";
435 	}
436 	}
437 	setContent(text, "text/plain; charset=" + MimeUtility.quote(charset, HeaderTokenizer.MIME));
438 	} 
{code}

should be "text/" + subtype

> MimeBodyPart.setText(String, String, String)  ignores subType
> -------------------------------------------------------------
>
>                 Key: GERONIMO-6536
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6536
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: mail
>            Reporter: Thomas Neidhart
>
> This has been detected as part of [EMAIL-147].
> When creating the mime message, we call MimeBodyPart.setText(String, String, String) with html as
subtype, but when calling this method, the subType is completely ignored and the resulting contentType
is always "text/plain".

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Thomas Neidhart (JIRA | 12 Dec 17:40 2014
Picon

[jira] [Commented] (GERONIMO-6536) MimeBodyPart.setText(String, String, String) ignores subType


    [
https://issues.apache.org/jira/browse/GERONIMO-6536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244421#comment-14244421
] 

Thomas Neidhart commented on GERONIMO-6536:
-------------------------------------------

No the problem is still present with 1.9.0-SNAPSHOT.
Keep in mind that the problem is actually in the geronimo-javamail_1.4_mail jar as the MimeBodyPart class
is located there.

> MimeBodyPart.setText(String, String, String)  ignores subType
> -------------------------------------------------------------
>
>                 Key: GERONIMO-6536
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6536
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: mail
>            Reporter: Thomas Neidhart
>
> This has been detected as part of [EMAIL-147].
> When creating the mime message, we call MimeBodyPart.setText(String, String, String) with html as
subtype, but when calling this method, the subType is completely ignored and the resulting contentType
is always "text/plain".

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Hendrik Saly (JIRA | 12 Dec 17:13 2014
Picon

[jira] [Commented] (GERONIMO-6536) MimeBodyPart.setText(String, String, String) ignores subType


    [
https://issues.apache.org/jira/browse/GERONIMO-6536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244386#comment-14244386
] 

Hendrik Saly commented on GERONIMO-6536:
----------------------------------------

can you pls. test against current 1.9-SNAPSHOT and report back if this is fixed in 1.9?
https://repository.apache.org/content/repositories/snapshots/org/apache/geronimo/javamail/geronimo-javamail_1.4_provider/1.9.0-SNAPSHOT/

> MimeBodyPart.setText(String, String, String)  ignores subType
> -------------------------------------------------------------
>
>                 Key: GERONIMO-6536
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6536
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: mail
>            Reporter: Thomas Neidhart
>
> This has been detected as part of [EMAIL-147].
> When creating the mime message, we call MimeBodyPart.setText(String, String, String) with html as
subtype, but when calling this method, the subType is completely ignored and the resulting contentType
is always "text/plain".

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Thomas Neidhart (JIRA | 12 Dec 16:26 2014
Picon

[jira] [Commented] (GERONIMO-6536) MimeBodyPart.setText(String, String, String) ignores subType


    [
https://issues.apache.org/jira/browse/GERONIMO-6536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244264#comment-14244264
] 

Thomas Neidhart commented on GERONIMO-6536:
-------------------------------------------

btw. the reason we call setText(...) instead of setContent(...) as before was to add support for the system
property "mail.mime.charset".

> MimeBodyPart.setText(String, String, String)  ignores subType
> -------------------------------------------------------------
>
>                 Key: GERONIMO-6536
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6536
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: mail
>            Reporter: Thomas Neidhart
>
> This has been detected as part of [EMAIL-147].
> When creating the mime message, we call MimeBodyPart.setText(String, String, String) with html as
subtype, but when calling this method, the subType is completely ignored and the resulting contentType
is always "text/plain".

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Thomas Neidhart (JIRA | 12 Dec 16:24 2014
Picon

[jira] [Created] (GERONIMO-6536) MimeBodyPart.setText(String, String, String) ignores subType

Thomas Neidhart created GERONIMO-6536:
-----------------------------------------

             Summary: MimeBodyPart.setText(String, String, String)  ignores subType
                 Key: GERONIMO-6536
                 URL: https://issues.apache.org/jira/browse/GERONIMO-6536
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: mail
            Reporter: Thomas Neidhart

This has been detected as part of [EMAIL-147].

When creating the mime message, we call MimeBodyPart.setText(String, String, String) with html as
subtype, but when calling this method, the subType is completely ignored and the resulting contentType
is always "text/plain".

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Jack Cai | 10 Dec 22:40 2014

What is the equivalence of catalina.policy in Geronimo?

Thanks.

-Jack
Christian Schneider (JIRA | 3 Dec 15:12 2014
Picon

[jira] [Updated] (GERONIMO-4576) Make persistence exceptions more visible to client


     [
https://issues.apache.org/jira/browse/GERONIMO-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Schneider updated GERONIMO-4576:
------------------------------------------
    Attachment: GERONIMO-4576-1.patch

I attached a patch that fixes this issue. The problem was that calling setRollbackOnly() created a quite
uninformative exception and set it using markRollbackCause(e). Then at a later point the real exception
could not be set anymore as markRollbackCause only sets the exception if the current one is not set.

My patch avoids the generic exception and only calls markRollbackCause if a real exception was given.

> Make persistence exceptions more visible to client
> --------------------------------------------------
>
>                 Key: GERONIMO-4576
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4576
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: persistence
>    Affects Versions: 2.2
>         Environment: Linux, Windows
>            Reporter: Joe Bohn
>            Priority: Minor
>             Fix For: Wish List
>
>         Attachments: GERONIMO-4576-1.patch
>
>
> See http://issues.apache.org/jira/browse/GERONIMO-3907  for details of the original problem.   That
core problem was resolved.  However, upon resolution it was mentioned that it would be beneficial to
report more specific failure information back to the client.  From GERONIMO-3907:
> Ralf Baumhof - 06/May/08 06:17 AM
> Today if have tested the new Geronimo release 2.1.1 (published on 28.04.2008). The problem is now fixed.
If the server gets an error on trying a commit, this error is now thrown to the web bean.
> Exception text:
> javax.ejb.EJBTransactionRolledbackException: Transaction was rolled back, presumably because
setRollbackOnly was called during a synchronization: Unable to commit: transaction marked for
rollback Root Cause: javax.transaction.TransactionRolledbackException : Transaction was rolled
back, presumably because setRollbackOnly was called during a synchronization: Unable to commit:
transaction marked for rollback
> Unfortunately there is no proper root cause attached to the exception. So the cause can only be seen in the
server console, but can not be reported to the user. It would be very nice if you could change this in a later release.
> Thanks for your help.
> Vincent MATHON - 06/Nov/08 02:03 AM
> I agree that exceptions on the server side should not be thrown to the client side since such exceptions
types might not be known by the client. However, for unit testing purpose, it is useful to attach the root
cause to the RollBackException. I have modified a few lines in
org.apache.geronimo.transaction.manager.TransactionImpl.java to attach the root cause in case of
RollBackException and it works for my unit testing purpose (I have not enough background on the java
transaction architecture topic to submit a patch for production). It would be great to define a
configuration parameter that permits to provide the root cause to the client and keep the current
behaviour that does not by default.
> Geoff Callender - 22/Dec/08 03:36 AM
> It's useful for more than unit testing - it's essential to be able to inform the client what's wrong with the
request. I've added some examples of this to https://issues.apache.org/jira/browse/OPENEJB-782 .

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Gmane