Skip to Main Content

Java EE (Java Enterprise Edition) General Discussion

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

JavaMail 1.6.0 Release Candidate 2

A second "release candidate" version of JavaMail 1.6.0 is now available.

There's a few bug fixes relative to the rc1 release related to the UTF-8

support.

At this point, I expect NO changes for the final release.

The 1.6.0 release contains API improvements, bug fixes, and enhancements,

including the following significant changes:

  • Use of Java generics in most APIs
  • Support for internationalized email addresses (RFC 6530/6531/6532)
  • Support for SMTP CHUNKING (RFC 3030)
  • Support for connecting through web proxy servers

The full list of changes is in the file CHANGES.txt, viewable in the

source code repository here:

https://raw.githubusercontent.com/javaee/javamail/master/doc/release/CHANGES.txt

The API changes in JavaMail 1.6 are described here:

https://raw.githubusercontent.com/javaee/javamail/master/doc/spec/JavaMail-1.6-changes.txt

The JavaMail 1.6 specification Maintenance Review is now underway at the JCP:

https://jcp.org/en/jsr/detail?id=919

The ballot will finish on July 10.  Assuming it passes, I expect to produce

the final JavaMail 1.6.0 release shortly thereafter.

The JavaMail javax.mail-1.6.0-rc2.jar file is available in the java.net

Maven Repository starting here:

https://maven.java.net/content/repositories/public/com/sun/mail/javax.mail/

It is also available from the Maven Central repository.

You'll find the source code for this version in the repository

of the JavaMail project on GitHub:

https://javaee.github.io/javamail

Please send feedback to javamail_ww@oracle.com.

Enjoy!

        The JavaMail Team

Comments

Centinul
Answer
You can try:
SELECT * FROM V$VERSION
or
SELECT version FROM V$INSTANCE
or
BEGIN DBMS_OUTPUT.PUT_LINE(DBMS_DB_VERSION.VERSION || '.' || DBMS_DB_VERSION.RELEASE); END;
Marked as Answer by 858277 · Sep 27 2020
onkar.nath
I am not sure what exactly you mean by "what type of database am using " but you can try this:

select from v$version;*

This will give you detailed version number of the database components. You can also use

select from PRODUCT_COMPONENT_VERSION;*

to get various components of the DB with their version.

Onkar
858277
Thanks
1 - 3
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Jun 22 2017
Added on May 25 2017
0 comments
963 views