Re: [jta-dev] Converting Specification Documents

[Lance Andersen <lance.andersen@xxxxxxxxxx>]

HI Tom,

I believe we should be using " one-phase optimized” as that change was made prior to the updates I made to the JTA 1.3 spec.

Best

Lance

On Jun 9, 2020, at 5:26 AM, Tom Jenkinson <tom.jenkinson@xxxxxxxxxx> wrote:

One thing I haven't done in pull 97 (the initial import) is that the change made to some hyphenation in JTA 1.3 spec https://github.com/eclipse-ee4j/jta-api/pull/97/commits/a7e6299b32e09eedab81fa798290520c2ef2e234#diff-cf9dc5208e60c322e6fac0bee4a45f72R491 was also reflected in the change log at the bottom of the document but associated with 1.2, so in other words the changelog for JTA 1.2 was altered to change the hyphenation of "onephase-optimized" to "one-phase optimized".

Do people thing that to be closer to JTA 1.3 then we should change the change log in Jakarta Transactions too?

Perhaps we could leave the JTA 1.2 changelog with the old hyphenation (so JTA 1.2 style) and add a new item in changelog 2 to mention what was decided for Jakarta Transactions.

Maybe it's too much though and we would be as well to make the change in the JTA 1.2 changelog as JTA 1.3 did.

So there are three options:

1. Don't change the hyphenation in JTA 1.2 changelog as was updated in JTA 1.3. This has the negative that the cases miss searching the document for when the change was made but doesn't change the changelog for JTA 1.2 (but does change it when comparing to JTA 1.3...).

2. Change the hyphenation in JTA 1.2 changelog as was updated in JTA 1.3.

3. Add a new changelog to Jakarta Transactions 2.0.0 confirming that the wording of onephase-optimized was changed to one-phase optimized in JTA 1.3 and leave the JTA 1.2 changelog as it appeared in JTA 1.2

Does anyone have any preference? Currently it is in the state of "1" above.

On Fri, 5 Jun 2020 at 18:16, Tom Jenkinson <tom.jenkinson@xxxxxxxxxx> wrote:

The initial PR to get the spec into a branch in our repo is: https://github.com/eclipse-ee4j/jta-api/pull/97

On Fri, 17 Jan 2020 at 15:11, Markus Stauffer <markus.stauffer@xxxxxxxxx> wrote:

Thanks for the hint Tom. Now it makes sense. I was not aware of JTS and its status.

I like the wording, I think it is is fine. But as a first time reader of the document the words CORBA and IIOP raised my eyebrows.

Cheers
--
Markus Stauffer

On 17.01.20 15:23, Tom Jenkinson wrote:

On Fri, 17 Jan 2020 at 14:16, Markus Stauffer <markus.stauffer@xxxxxxxxx> wrote:

Looks like everyone is busy with copyrights ;)

In the meantime I have another question about the spec: Will the "Java Transaction Service" described in chapter 2.5 be a "Optional" part for Jakarte EE 9 ? Or will it be pruned?
In the Jakarta EE 9 Release plan it is said that "Support for Distributed Interoperability" is pruned. Does that mean JTS is pruned as well?

JTS won't need to be be pruned in the sense that is is not part of the Jakarta EE platform and is just a draft [1]. If it becomes necessary to alter this wording, perhaps we could consider referencing OTS instead?

[1] https://www.oracle.com/technetwork/java/javaee/jts-spec095-1508547.pdf

Cheers
--
Markus Stauffer

On 16.01.20 11:48, Tom Jenkinson wrote:

Thanks for the heads up but I don't actually think the spec is ready yet. There is some information here: https://docs.google.com/spreadsheets/d/1EN5UEzxFV1Buk7yqdQAweaynWJ3UNn2BjN7blXn9vh4/edit#gid=0 and here: https://github.com/eclipse-ee4j/jakartaee-platform/projects/2

I have raised the topic: https://www.eclipse.org/lists/jakartaee-spec-project-leads/msg00378.html / https://www.eclipse.org/lists/ee4j-pmc/msg02385.html

On Wed, 15 Jan 2020 at 17:03, Markus Stauffer <markus.stauffer@xxxxxxxxx> wrote:

Hello jta-dev

I would like to help converting the specification documents. According to the Jakarta EE Community Update January 2020 they are available and ready to convert.

Question: Is the IPzilla zip file already available? And how can we access it?

Cheers

-- 
Markus Stauffer

_______________________________________________
jta-dev mailing list
jta-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jta-dev

_______________________________________________
jta-dev mailing list
jta-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jta-dev

-- 
Markus Stauffer

_______________________________________________
jta-dev mailing list
jta-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jta-dev

_______________________________________________
jta-dev mailing list
jta-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jta-dev

-- 
Markus Stauffer
Tulpenstrasse 11
CH-2540 Grenchen

E-Mail: Markus.Stauffer@xxxxxxxxx

_______________________________________________
jta-dev mailing list
jta-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jta-dev

_______________________________________________
jta-dev mailing list
jta-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jta-dev

Lance Andersen| Principal Member of Technical Staff | +1.781.442.2037
Oracle Java Engineering 
1 Network Drive 
Burlington, MA 01803
Lance.Andersen@xxxxxxxxxx