[jira] [Created] (GERONIMO-6533) [Geronimo Javamail] InternetAddress should throw exception in strict mode for invalid address
Arnaud MERGEY created GERONIMO-6533:
---
Summary: [Geronimo Javamail] InternetAddress should throw
exception in strict mode for invalid address
Key: GERONIMO-6533
URL: https://issues.apache.org/jira/browse/GERONIMO-6533
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: mail
Reporter: Arnaud MERGEY
Unlike Oracle Javamail to Geronimo Javamail implementation, Geronimo Javamail
accept invalid emails even in strict mode
Executing;
javax.mail.internet.InternetAddress("a",true);
fails throwing AddressException with Oracle Javamail, but succeed with Geronimo
Javamail
validate() succeed as well, it should throw an exception when address is not an
email address
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (GERONIMO-6138) JDBC 4 API is not supported
[ https://issues.apache.org/jira/browse/GERONIMO-6138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13462614#comment-13462614 ] Arnaud MERGEY edited comment on GERONIMO-6138 at 9/25/12 8:54 PM: -- Any news on this ? Geronimo release claim to Support SUN's Java Enterprise Edition 6.0 Full Profile specification But is still not supporting JDBC4, according to this http://www.oracle.com/technetwork/java/javaee/tech/index-jsp-142185.html, I believe it should was (Author: amergey): Any news on this, Geronimo release claim to Support SUN's Java Enterprise Edition 6.0 Full Profile specification But is still not supporting JDBC4, according to this http://www.oracle.com/technetwork/java/javaee/tech/index-jsp-142185.html, I believe it should > JDBC 4 API is not supported > > > Key: GERONIMO-6138 > URL: https://issues.apache.org/jira/browse/GERONIMO-6138 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 3.0-M1, 3.0 >Reporter: Arnaud MERGEY > Fix For: 3.0 > > > I try to deploy an application that uses some JDBC 4 API like > java.sql.ResultSet.isClosed() > This calls fails with following error > java.lang.AbstractMethodError: > org.tranql.connector.jdbc.ResultSetHandle.isClosed()Z > According to JEE 6 specifications, JDBC 4 API should be supported in Geronimo > 3, and it seems not. -- 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
[jira] [Commented] (GERONIMO-6138) JDBC 4 API is not supported
[ https://issues.apache.org/jira/browse/GERONIMO-6138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13462614#comment-13462614 ] Arnaud MERGEY commented on GERONIMO-6138: - Any news on this, Geronimo release claim to Support SUN's Java Enterprise Edition 6.0 Full Profile specification But is still not supporting JDBC4, according to this http://www.oracle.com/technetwork/java/javaee/tech/index-jsp-142185.html, I believe it should > JDBC 4 API is not supported > > > Key: GERONIMO-6138 > URL: https://issues.apache.org/jira/browse/GERONIMO-6138 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 3.0-M1, 3.0 >Reporter: Arnaud MERGEY > Fix For: 3.0 > > > I try to deploy an application that uses some JDBC 4 API like > java.sql.ResultSet.isClosed() > This calls fails with following error > java.lang.AbstractMethodError: > org.tranql.connector.jdbc.ResultSetHandle.isClosed()Z > According to JEE 6 specifications, JDBC 4 API should be supported in Geronimo > 3, and it seems not. -- 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
[jira] [Commented] (GERONIMO-6138) JDBC 4 API is not supported
[ https://issues.apache.org/jira/browse/GERONIMO-6138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095799#comment-13095799 ] Arnaud MERGEY commented on GERONIMO-6138: - I have tried geronimo-tomcat7-javaee6-web-3.0-20110901.085007-314-bin and the issue is still there "java.lang.AbstractMethodError: org.tranql.connector.jdbc.ResultSetHandle.isClosed()Z" by calling java.sql.ResultSet.isClosed() > JDBC 4 API is not supported > > > Key: GERONIMO-6138 > URL: https://issues.apache.org/jira/browse/GERONIMO-6138 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 3.0-M1 >Reporter: Arnaud MERGEY > Fix For: 3.0 > > > I try to deploy an application that uses some JDBC 4 API like > java.sql.ResultSet.isClosed() > This calls fails with following error > java.lang.AbstractMethodError: > org.tranql.connector.jdbc.ResultSetHandle.isClosed()Z > According to JEE 6 specifications, JDBC 4 API should be supported in Geronimo > 3, and it seems not. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6138) JDBC 4 API is not supported
JDBC 4 API is not supported Key: GERONIMO-6138 URL: https://issues.apache.org/jira/browse/GERONIMO-6138 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 3.0-M1 Reporter: Arnaud MERGEY I try to deploy an application that uses some JDBC 4 API like java.sql.ResultSet.isClosed() This calls fails with following error java.lang.AbstractMethodError: org.tranql.connector.jdbc.ResultSetHandle.isClosed()Z According to JEE 6 specifications, JDBC 4 API should be supported in Geronimo 3, and it seems not. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
