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!

Leading An Adopt-A-JSR Effort

Yolande Poirier-OracleOct 13 2015 — edited Jan 20 2016

Introduction

Each Adopt a JSR group works on JSRs in their own way. Some meet Face to Face, some co-ordinate over email, others have Skype sessions, whatever way works with your group is fine.

Every JUG/individual/organisation will want to work differently, we simply suggest is that you put together a wiki similar to LJC's Adopt a JSR Program for your overal program and for each JSR, a wiki similar to LJC's Adoption page for JSR-310 - New Date and Time.

Also see Java EE Adopt-a-JSR page for a list of Java EE JSRs and the Spec Lead requests from Adopt-a-JSR program participants.

Getting started

This section (taken from Somay Nakhal's work) contains some guidance for JUG members who are leading an Adopt a JSR group as used by the LJC. Take as much or as little of it as you need!

Once a group has really gotten going the leader(s) of the Adopt a JSR group might find it useful to:

Create a Collaboration space

Create a collaboration space for your efforts, e.g. LJC JSR-310 page

  1. This space can contain the links to resources such as the JSR project page (typically a java.net projects), mailing lists, conference talks, presentations downloads... etc related to the JSR
  2. Add the link to this on the JSR wiki page on the Global Matrix at Who is Adopting JSRs

Contact the spec lead

  1. Contact the Spec Lead for the JSR, introducing yourself and explaining your intended involvement.

Find volunteers in your JUG or organization

Send an initial email to interested adoptees

  1. Introduce yourself and why you are interested in the JSR
  2. Briefly explain the JCP process (depending on the familiarity of the adoptees)
  3. Talk about the JSR and it's current state
  4. Ask them to introduce themselves and why they are interested in the JSR
  5. Ask interested adoptees to check the details on the Adopt a JSR page and provide their opinion.

Identify areas that need help

Identify areas where the JSR needs help / or areas that your group want to work on. See What to work on for a JSR

  1. Co-ordinate your activities with the spec lead and expert group on the official JSR mailing lists.
  2. Encourage genuine experts within the adoptees to join the Expert Group.
  3. Email the adoptees about updates related to the JSR: eg voting results, availability of drafts...etc.

Organize Talks and Hackdays

Typically you'll:

  1. Give lighting talk(s) or full length presentations about the subject matter and the JSR by yourself/adoptees.
  2. Arrange F2F hackdays/meet-ups to work on the JSR - (How to Run a Hackday).

Give Feedback

It's vital that after a talk or a hackday that all of the feedback is collated and sent back into the Spec Lead and the EG

Forward to What to work on for a JSR
Back to Home

Comments

Alex Keh-Oracle

I tried your C# app with a table using a DATE column and TIMESTAMP column. In both cases with either ODP.NET Core 2.19.80 or 2.19.70, I didn't hit an error. I used DB 19c. Which DB version did you use?

4252326

I found out that there must be at least one record in the table. For example:

Table Design:

Name
Type
Size
IDNumber0
DateDATE7
TimeTIMESTAMP0
Time2INTERVAL DAY TO SECOND0

Table Data:

ID
DateTimeTime2
1(Null)(Null)(Null)

Then replace the [column] in the sql below:

var sql = $"select(CASE WHEN 1 = 0 THEN a.\"[column]\" ELSE NULL END) as C0 from \"YOUR TABLE NAME\" a ";

 

[Date]: reproduced

[Time]: can't reproduce

[Time2]: reproduced

DB version: 11/12/18/19c

Alex Keh-Oracle

I added the interval column and added one row of data, but still can't reproduce the problem with the 2.19.80 version against the data or interval column. Do you want to send us your trace? Just add these two lines and run your app.

OracleConfiguration.TraceFileLocation = @"D:\traces";

OracleConfiguration.TraceLevel = 7;

You can send the trace file to dotnet_us (at) oracle.com.

4252326

Thank you. The email has been sent. I hope it's useful to you.

Alex Keh-Oracle

This bug appears to be the same as Bug 26123054.

4252326

Will this problem be fixed recently?

Alex Keh-Oracle

The bug hasn't been fixed yet. We're still evaluating the root cause.

Alex Keh-Oracle
Answer

The bug has been fixed in our main code line. My expectation is that the fix will be in the ODP.NET Core 19.10 release.

Marked as Answer by 4252326 · Sep 27 2020
1 - 8

Post Details

Added on Oct 13 2015
0 comments
915 views