Discussion:
OWB-2.0.0 to be released soon
Mark Struberg
2017-06-17 17:38:01 UTC
Permalink
Hi folks!

We are finished with implementing all CDI-2.0 features and now successfully pass the standalone TCK!
A recent owb-2.0.0-SNAPSHOT is deployed to the Apache Snapshots repository [1].
This get's deployed via Jenkins each night.

It would be great if you could try it out and give us some feedback!
We gonna release it somewhen next week.

txs and LieGrue,
strub


[1] https://repository.apache.org/content/groups/snapshots/
Ludovic Pénet
2017-06-17 17:41:36 UTC
Permalink
Is it a drop i' remplacement ?
If yes, I would gladky test this works, before test driving the new features.

Ludovic
Post by Mark Struberg
Hi folks!
We are finished with implementing all CDI-2.0 features and now
successfully pass the standalone TCK!
A recent owb-2.0.0-SNAPSHOT is deployed to the Apache Snapshots
repository [1].
This get's deployed via Jenkins each night.
It would be great if you could try it out and give us some feedback!
We gonna release it somewhen next week.
txs and LieGrue,
strub
[1] https://repository.apache.org/content/groups/snapshots/
--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma briÚveté.
Mark Struberg
2017-06-17 17:53:11 UTC
Permalink
Yes, it is 1:1 backward compatible.

The only thing you need to update is the jcdi and common-annotations API:

<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-annotation_1.3_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>

<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-jcdi_2.0_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>

They will be released this week as well.

LieGrue,
strub
Post by Ludovic Pénet
Is it a drop i' remplacement ?
If yes, I would gladky test this works, before test driving the new features.
Ludovic
Hi folks!
We are finished with implementing all CDI-2.0 features and now successfully pass the standalone TCK!
A recent owb-2.0.0-SNAPSHOT is deployed to the Apache Snapshots repository [1].
This get's deployed via Jenkins each night.
It would be great if you could try it out and give us some feedback!
We gonna release it somewhen next week.
txs and LieGrue,
strub
[1] https://repository.apache.org/content/groups/snapshots/
--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.
Romain Manni-Bucau
2017-06-17 18:51:20 UTC
Permalink
Do we want to release meecrowave in the same shot?
Post by Mark Struberg
Yes, it is 1:1 backward compatible.
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-annotation_1.3_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-jcdi_2.0_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
They will be released this week as well.
LieGrue,
strub
Post by Ludovic Pénet
Is it a drop i' remplacement ?
If yes, I would gladky test this works, before test driving the new
features.
Post by Ludovic Pénet
Ludovic
Hi folks!
We are finished with implementing all CDI-2.0 features and now
successfully pass the standalone TCK!
Post by Ludovic Pénet
A recent owb-2.0.0-SNAPSHOT is deployed to the Apache Snapshots
repository [1].
Post by Ludovic Pénet
This get's deployed via Jenkins each night.
It would be great if you could try it out and give us some feedback!
We gonna release it somewhen next week.
txs and LieGrue,
strub
[1] https://repository.apache.org/content/groups/snapshots/
--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma
briÚveté.
John D. Ament
2017-06-17 20:36:04 UTC
Permalink
So... just to confirm. Outside of changing the geronimo specs, taking a
OWB 1.x profile that I may have will just work with OWB 2?

John
Post by Mark Struberg
Yes, it is 1:1 backward compatible.
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-annotation_1.3_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-jcdi_2.0_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
They will be released this week as well.
LieGrue,
strub
Post by Ludovic Pénet
Is it a drop i' remplacement ?
If yes, I would gladky test this works, before test driving the new
features.
Post by Ludovic Pénet
Ludovic
Hi folks!
We are finished with implementing all CDI-2.0 features and now
successfully pass the standalone TCK!
Post by Ludovic Pénet
A recent owb-2.0.0-SNAPSHOT is deployed to the Apache Snapshots
repository [1].
Post by Ludovic Pénet
This get's deployed via Jenkins each night.
It would be great if you could try it out and give us some feedback!
We gonna release it somewhen next week.
txs and LieGrue,
strub
[1] https://repository.apache.org/content/groups/snapshots/
--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma
briÚveté.
Mark Struberg
2017-06-17 20:43:03 UTC
Permalink
Yes, it should 'just work' afaict.
We even kept the SPI the same.
We most likely will add an async event related API for better integration within TomEE in the future.
But this should still be perfectly backward compatible as OWB will provide a default implementation anyway!

If you catch any (unexpected) problems then just ping us.

txs and LieGrue,
strub
So... just to confirm. Outside of changing the geronimo specs, taking a OWB 1.x profile that I may have will just work with OWB 2?
John
Yes, it is 1:1 backward compatible.
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-annotation_1.3_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-jcdi_2.0_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
They will be released this week as well.
LieGrue,
strub
Post by Ludovic Pénet
Is it a drop i' remplacement ?
If yes, I would gladky test this works, before test driving the new features.
Ludovic
Hi folks!
We are finished with implementing all CDI-2.0 features and now successfully pass the standalone TCK!
A recent owb-2.0.0-SNAPSHOT is deployed to the Apache Snapshots repository [1].
This get's deployed via Jenkins each night.
It would be great if you could try it out and give us some feedback!
We gonna release it somewhen next week.
txs and LieGrue,
strub
[1] https://repository.apache.org/content/groups/snapshots/
--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.
Steve Sobol - Lobos Studios
2017-06-17 21:10:23 UTC
Permalink
I have had some good success with OWB and JSF running on Jetty. There are two projects where I'd be happy to use 2.0, but both are still under development and I don't know how much useful feedback I can offer.

--
Lobos Studios | Phone: 877.919.4WEB | LobosStudios.com | Facebook.com/LobosStudios | @LobosStudios
Web Development - Mobile Development - Helpdesk/Tech Support - Computer Sales & Service
Acer Authorized Reseller - Computers, Windows and Android Tablets, Accessories

Steve Sobol - CEO, Senior Developer and Server Jockey
***@LobosStudios.com

-----Original Message-----
From: Mark Struberg [mailto:***@yahoo.de]
Sent: Saturday, June 17, 2017 13:43
To: openwebbeans-user <***@openwebbeans.apache.org>
Cc: openwebbeans-dev <***@openwebbeans.apache.org>
Subject: Re: OWB-2.0.0 to be released soon

Yes, it should 'just work' afaict.
We even kept the SPI the same.
We most likely will add an async event related API for better integration within TomEE in the future.
But this should still be perfectly backward compatible as OWB will provide a default implementation anyway!

If you catch any (unexpected) problems then just ping us.

txs and LieGrue,
strub
So... just to confirm. Outside of changing the geronimo specs, taking a OWB 1.x profile that I may have will just work with OWB 2?
John
Yes, it is 1:1 backward compatible.
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-annotation_1.3_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-jcdi_2.0_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
They will be released this week as well.
LieGrue,
strub
Post by Ludovic Pénet
Is it a drop i' remplacement ?
If yes, I would gladky test this works, before test driving the new features.
Ludovic
Hi folks!
We are finished with implementing all CDI-2.0 features and now successfully pass the standalone TCK!
A recent owb-2.0.0-SNAPSHOT is deployed to the Apache Snapshots repository [1].
This get's deployed via Jenkins each night.
It would be great if you could try it out and give us some feedback!
We gonna release it somewhen next week.
txs and LieGrue,
strub
[1] https://repository.apache.org/content/groups/snapshots/
--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.
Romain Manni-Bucau
2017-06-17 21:43:15 UTC
Permalink
Side note: we already have the async spi ;)
Post by Steve Sobol - Lobos Studios
I have had some good success with OWB and JSF running on Jetty. There are
two projects where I'd be happy to use 2.0, but both are still under
development and I don't know how much useful feedback I can offer.
--
Lobos Studios | Phone: 877.919.4WEB | LobosStudios.com |
Web Development - Mobile Development - Helpdesk/Tech Support - Computer Sales & Service
Acer Authorized Reseller - Computers, Windows and Android Tablets, Accessories
Steve Sobol - CEO, Senior Developer and Server Jockey
-----Original Message-----
Sent: Saturday, June 17, 2017 13:43
Subject: Re: OWB-2.0.0 to be released soon
Yes, it should 'just work' afaict.
We even kept the SPI the same.
We most likely will add an async event related API for better integration
within TomEE in the future.
But this should still be perfectly backward compatible as OWB will provide
a default implementation anyway!
If you catch any (unexpected) problems then just ping us.
txs and LieGrue,
strub
Post by John D. Ament
So... just to confirm. Outside of changing the geronimo specs, taking a
OWB 1.x profile that I may have will just work with OWB 2?
Post by John D. Ament
John
Yes, it is 1:1 backward compatible.
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-annotation_1.3_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-jcdi_2.0_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
They will be released this week as well.
LieGrue,
strub
Post by Ludovic Pénet
Is it a drop i' remplacement ?
If yes, I would gladky test this works, before test driving the new
features.
Post by John D. Ament
Post by Ludovic Pénet
Ludovic
Hi folks!
We are finished with implementing all CDI-2.0 features and now
successfully pass the standalone TCK!
Post by John D. Ament
Post by Ludovic Pénet
A recent owb-2.0.0-SNAPSHOT is deployed to the Apache Snapshots
repository [1].
Post by John D. Ament
Post by Ludovic Pénet
This get's deployed via Jenkins each night.
It would be great if you could try it out and give us some feedback!
We gonna release it somewhen next week.
txs and LieGrue,
strub
[1] https://repository.apache.org/content/groups/snapshots/
--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma
briÚveté.
John D. Ament
2017-06-18 11:45:22 UTC
Permalink
Just wondering, did you change the behavior when a class isn't found to
ignore the bean? Prior versions of OWB would throw an exception.

John
Post by Mark Struberg
Yes, it should 'just work' afaict.
We even kept the SPI the same.
We most likely will add an async event related API for better integration
within TomEE in the future.
But this should still be perfectly backward compatible as OWB will provide
a default implementation anyway!
If you catch any (unexpected) problems then just ping us.
txs and LieGrue,
strub
Post by John D. Ament
So... just to confirm. Outside of changing the geronimo specs, taking a
OWB 1.x profile that I may have will just work with OWB 2?
Post by John D. Ament
John
Yes, it is 1:1 backward compatible.
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-annotation_1.3_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-jcdi_2.0_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
They will be released this week as well.
LieGrue,
strub
Post by Ludovic Pénet
Is it a drop i' remplacement ?
If yes, I would gladky test this works, before test driving the new
features.
Post by John D. Ament
Post by Ludovic Pénet
Ludovic
Hi folks!
We are finished with implementing all CDI-2.0 features and now
successfully pass the standalone TCK!
Post by John D. Ament
Post by Ludovic Pénet
A recent owb-2.0.0-SNAPSHOT is deployed to the Apache Snapshots
repository [1].
Post by John D. Ament
Post by Ludovic Pénet
This get's deployed via Jenkins each night.
It would be great if you could try it out and give us some feedback!
We gonna release it somewhen next week.
txs and LieGrue,
strub
[1] https://repository.apache.org/content/groups/snapshots/
--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma
briÚveté.
Mark Struberg
2017-06-18 13:41:19 UTC
Permalink
OWB itself did always ignore it and log a warning. This code did not get changed for a while.

But we have/had a bug in the arquillian connector which lead to blowing up on NoClassDefFound.
I need to check whether we fixed this already with another commit.

The ticket is https://issues.apache.org/jira/browse/OWB-1179

LieGrue,
strub
Post by John D. Ament
Just wondering, did you change the behavior when a class isn't found to
ignore the bean? Prior versions of OWB would throw an exception.
John
Post by Mark Struberg
Yes, it should 'just work' afaict.
We even kept the SPI the same.
We most likely will add an async event related API for better integration
within TomEE in the future.
But this should still be perfectly backward compatible as OWB will provide
a default implementation anyway!
If you catch any (unexpected) problems then just ping us.
txs and LieGrue,
strub
Post by John D. Ament
So... just to confirm. Outside of changing the geronimo specs, taking a
OWB 1.x profile that I may have will just work with OWB 2?
Post by John D. Ament
John
Yes, it is 1:1 backward compatible.
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-annotation_1.3_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-jcdi_2.0_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
They will be released this week as well.
LieGrue,
strub
Post by Ludovic Pénet
Is it a drop i' remplacement ?
If yes, I would gladky test this works, before test driving the new
features.
Post by John D. Ament
Post by Ludovic Pénet
Ludovic
Hi folks!
We are finished with implementing all CDI-2.0 features and now
successfully pass the standalone TCK!
Post by John D. Ament
Post by Ludovic Pénet
A recent owb-2.0.0-SNAPSHOT is deployed to the Apache Snapshots
repository [1].
Post by John D. Ament
Post by Ludovic Pénet
This get's deployed via Jenkins each night.
It would be great if you could try it out and give us some feedback!
We gonna release it somewhen next week.
txs and LieGrue,
strub
[1] https://repository.apache.org/content/groups/snapshots/
--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma
brièveté.
Romain Manni-Bucau
2017-06-18 14:04:30 UTC
Permalink
2 things to check before the release:

1. se API (not covered by tck and poorly covered by us ATM)
2. the fastMatching flag should get removed if we can (created due to 1 tck)


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>
Post by Mark Struberg
OWB itself did always ignore it and log a warning. This code did not get
changed for a while.
But we have/had a bug in the arquillian connector which lead to blowing up
on NoClassDefFound.
I need to check whether we fixed this already with another commit.
The ticket is https://issues.apache.org/jira/browse/OWB-1179
LieGrue,
strub
Post by John D. Ament
Just wondering, did you change the behavior when a class isn't found to
ignore the bean? Prior versions of OWB would throw an exception.
John
Post by Mark Struberg
Yes, it should 'just work' afaict.
We even kept the SPI the same.
We most likely will add an async event related API for better
integration
Post by John D. Ament
Post by Mark Struberg
within TomEE in the future.
But this should still be perfectly backward compatible as OWB will
provide
Post by John D. Ament
Post by Mark Struberg
a default implementation anyway!
If you catch any (unexpected) problems then just ping us.
txs and LieGrue,
strub
Post by John D. Ament
So... just to confirm. Outside of changing the geronimo specs, taking
a
Post by John D. Ament
Post by Mark Struberg
OWB 1.x profile that I may have will just work with OWB 2?
Post by John D. Ament
John
On Sat, Jun 17, 2017 at 1:53 PM Mark Struberg
Yes, it is 1:1 backward compatible.
The only thing you need to update is the jcdi and common-annotations
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-annotation_1.3_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-jcdi_2.0_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
They will be released this week as well.
LieGrue,
strub
Post by Ludovic Pénet
Is it a drop i' remplacement ?
If yes, I would gladky test this works, before test driving the new
features.
Post by John D. Ament
Post by Ludovic Pénet
Ludovic
Hi folks!
We are finished with implementing all CDI-2.0 features and now
successfully pass the standalone TCK!
Post by John D. Ament
Post by Ludovic Pénet
A recent owb-2.0.0-SNAPSHOT is deployed to the Apache Snapshots
repository [1].
Post by John D. Ament
Post by Ludovic Pénet
This get's deployed via Jenkins each night.
It would be great if you could try it out and give us some feedback!
We gonna release it somewhen next week.
txs and LieGrue,
strub
[1] https://repository.apache.org/content/groups/snapshots/
--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma
briÚveté.
John D. Ament
2017-06-19 02:47:19 UTC
Permalink
Hmm so DeltaSpike is seeing 11 test failures with OWB2.

https://builds.apache.org/view/A-D/view/DeltaSpike/job/DeltaSpike%20OWB%202.0.0/lastCompletedBuild/testReport/

CDI Ctrl Servlet - it looks like a weird error, the impl of this bean
hasn't been changed in 2 years. Not sure if this is a new validation in
place.

ClasspathResourceTest - I'm not sure if the path is getting skewed due to
duplicate resources, or the same resource being added multiple times.

JSF & Scheduler look like changes in the dependency structure. If on
purpose, I'll push up a fix sometime tomorrow.
Post by Romain Manni-Bucau
1. se API (not covered by tck and poorly covered by us ATM)
2. the fastMatching flag should get removed if we can (created due to 1 tck)
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github
<https://github.com/rmannibucau> | LinkedIn
<https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>
Post by Mark Struberg
OWB itself did always ignore it and log a warning. This code did not get
changed for a while.
But we have/had a bug in the arquillian connector which lead to blowing
up on NoClassDefFound.
I need to check whether we fixed this already with another commit.
The ticket is https://issues.apache.org/jira/browse/OWB-1179
LieGrue,
strub
Post by John D. Ament
Just wondering, did you change the behavior when a class isn't found to
ignore the bean? Prior versions of OWB would throw an exception.
John
Post by Mark Struberg
Yes, it should 'just work' afaict.
We even kept the SPI the same.
We most likely will add an async event related API for better
integration
Post by John D. Ament
Post by Mark Struberg
within TomEE in the future.
But this should still be perfectly backward compatible as OWB will
provide
Post by John D. Ament
Post by Mark Struberg
a default implementation anyway!
If you catch any (unexpected) problems then just ping us.
txs and LieGrue,
strub
Post by John D. Ament
So... just to confirm. Outside of changing the geronimo specs,
taking a
Post by John D. Ament
Post by Mark Struberg
OWB 1.x profile that I may have will just work with OWB 2?
Post by John D. Ament
John
On Sat, Jun 17, 2017 at 1:53 PM Mark Struberg
Yes, it is 1:1 backward compatible.
The only thing you need to update is the jcdi and common-annotations
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-annotation_1.3_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-jcdi_2.0_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
They will be released this week as well.
LieGrue,
strub
Post by Ludovic Pénet
Is it a drop i' remplacement ?
If yes, I would gladky test this works, before test driving the new
features.
Post by John D. Ament
Post by Ludovic Pénet
Ludovic
Hi folks!
We are finished with implementing all CDI-2.0 features and now
successfully pass the standalone TCK!
Post by John D. Ament
Post by Ludovic Pénet
A recent owb-2.0.0-SNAPSHOT is deployed to the Apache Snapshots
repository [1].
Post by John D. Ament
Post by Ludovic Pénet
This get's deployed via Jenkins each night.
It would be great if you could try it out and give us some feedback!
We gonna release it somewhen next week.
txs and LieGrue,
strub
[1] https://repository.apache.org/content/groups/snapshots/
--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma
briÚveté.
Mark Struberg
2017-06-19 06:19:33 UTC
Permalink
Oh txs for the catch, will check.

LieGrue,
Strub
Post by John D. Ament
Hmm so DeltaSpike is seeing 11 test failures with OWB2.
https://builds.apache.org/view/A-D/view/DeltaSpike/job/DeltaSpike%20OWB%202.0.0/lastCompletedBuild/testReport/
CDI Ctrl Servlet - it looks like a weird error, the impl of this bean hasn't been changed in 2 years. Not sure if this is a new validation in place.
ClasspathResourceTest - I'm not sure if the path is getting skewed due to duplicate resources, or the same resource being added multiple times.
JSF & Scheduler look like changes in the dependency structure. If on purpose, I'll push up a fix sometime tomorrow.
Post by Romain Manni-Bucau
1. se API (not covered by tck and poorly covered by us ATM)
2. the fastMatching flag should get removed if we can (created due to 1 tck)
Romain Manni-Bucau
@rmannibucau | Blog | Old Blog | Github | LinkedIn | JavaEE Factory
Post by Mark Struberg
OWB itself did always ignore it and log a warning. This code did not get changed for a while.
But we have/had a bug in the arquillian connector which lead to blowing up on NoClassDefFound.
I need to check whether we fixed this already with another commit.
The ticket is https://issues.apache.org/jira/browse/OWB-1179
LieGrue,
strub
Post by John D. Ament
Just wondering, did you change the behavior when a class isn't found to
ignore the bean? Prior versions of OWB would throw an exception.
John
Post by Mark Struberg
Yes, it should 'just work' afaict.
We even kept the SPI the same.
We most likely will add an async event related API for better integration
within TomEE in the future.
But this should still be perfectly backward compatible as OWB will provide
a default implementation anyway!
If you catch any (unexpected) problems then just ping us.
txs and LieGrue,
strub
Post by John D. Ament
So... just to confirm. Outside of changing the geronimo specs, taking a
OWB 1.x profile that I may have will just work with OWB 2?
Post by John D. Ament
John
Yes, it is 1:1 backward compatible.
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-annotation_1.3_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-jcdi_2.0_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
They will be released this week as well.
LieGrue,
strub
Post by Ludovic Pénet
Is it a drop i' remplacement ?
If yes, I would gladky test this works, before test driving the new
features.
Post by John D. Ament
Post by Ludovic Pénet
Ludovic
Hi folks!
We are finished with implementing all CDI-2.0 features and now
successfully pass the standalone TCK!
Post by John D. Ament
Post by Ludovic Pénet
A recent owb-2.0.0-SNAPSHOT is deployed to the Apache Snapshots
repository [1].
Post by John D. Ament
Post by Ludovic Pénet
This get's deployed via Jenkins each night.
It would be great if you could try it out and give us some feedback!
We gonna release it somewhen next week.
txs and LieGrue,
strub
[1] https://repository.apache.org/content/groups/snapshots/
--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma
briÚveté.
Romain Manni-Bucau
2017-06-19 07:21:38 UTC
Permalink
IncompatibleClassChangeError, classpath is probably corrupted with an
owb 1.0 dependency somehow



Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>
Post by Mark Struberg
Oh txs for the catch, will check.
LieGrue,
Strub
Hmm so DeltaSpike is seeing 11 test failures with OWB2.
https://builds.apache.org/view/A-D/view/DeltaSpike/job/
DeltaSpike%20OWB%202.0.0/lastCompletedBuild/testReport/
CDI Ctrl Servlet - it looks like a weird error, the impl of this bean
hasn't been changed in 2 years. Not sure if this is a new validation in
place.
ClasspathResourceTest - I'm not sure if the path is getting skewed due to
duplicate resources, or the same resource being added multiple times.
JSF & Scheduler look like changes in the dependency structure. If on
purpose, I'll push up a fix sometime tomorrow.
Post by Romain Manni-Bucau
1. se API (not covered by tck and poorly covered by us ATM)
2. the fastMatching flag should get removed if we can (created due to 1 tck)
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github
<https://github.com/rmannibucau> | LinkedIn
<https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>
Post by Mark Struberg
OWB itself did always ignore it and log a warning. This code did not get
changed for a while.
But we have/had a bug in the arquillian connector which lead to blowing
up on NoClassDefFound.
I need to check whether we fixed this already with another commit.
The ticket is https://issues.apache.org/jira/browse/OWB-1179
LieGrue,
strub
Post by John D. Ament
Just wondering, did you change the behavior when a class isn't found to
ignore the bean? Prior versions of OWB would throw an exception.
John
On Sat, Jun 17, 2017 at 4:43 PM Mark Struberg <
Post by Mark Struberg
Yes, it should 'just work' afaict.
We even kept the SPI the same.
We most likely will add an async event related API for better
integration
Post by John D. Ament
Post by Mark Struberg
within TomEE in the future.
But this should still be perfectly backward compatible as OWB will
provide
Post by John D. Ament
Post by Mark Struberg
a default implementation anyway!
If you catch any (unexpected) problems then just ping us.
txs and LieGrue,
strub
Post by John D. Ament
So... just to confirm. Outside of changing the geronimo specs,
taking a
Post by John D. Ament
Post by Mark Struberg
OWB 1.x profile that I may have will just work with OWB 2?
Post by John D. Ament
John
On Sat, Jun 17, 2017 at 1:53 PM Mark Struberg <
Yes, it is 1:1 backward compatible.
The only thing you need to update is the jcdi and common-annotations
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-annotation_1.3_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-jcdi_2.0_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
They will be released this week as well.
LieGrue,
strub
Post by Ludovic Pénet
Is it a drop i' remplacement ?
If yes, I would gladky test this works, before test driving the new
features.
Post by John D. Ament
Post by Ludovic Pénet
Ludovic
Le 17 juin 2017 19:38:01 GMT+02:00, Mark Struberg <
Hi folks!
We are finished with implementing all CDI-2.0 features and now
successfully pass the standalone TCK!
Post by John D. Ament
Post by Ludovic Pénet
A recent owb-2.0.0-SNAPSHOT is deployed to the Apache Snapshots
repository [1].
Post by John D. Ament
Post by Ludovic Pénet
This get's deployed via Jenkins each night.
It would be great if you could try it out and give us some feedback!
We gonna release it somewhen next week.
txs and LieGrue,
strub
[1] https://repository.apache.org/content/groups/snapshots/
--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma
briÚveté.
John D. Ament
2017-06-20 00:39:58 UTC
Permalink
I had a hunch it was that, so did a dependency tree - no luck.

https://paste.apache.org/X3c5

John
IncompatibleClassChangeError, classpath is probably corrupted with an owb 1.0 dependency somehow
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github
<https://github.com/rmannibucau> | LinkedIn
<https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>
Post by Mark Struberg
Oh txs for the catch, will check.
LieGrue,
Strub
Hmm so DeltaSpike is seeing 11 test failures with OWB2.
https://builds.apache.org/view/A-D/view/DeltaSpike/job/DeltaSpike%20OWB%202.0.0/lastCompletedBuild/testReport/
CDI Ctrl Servlet - it looks like a weird error, the impl of this bean
hasn't been changed in 2 years. Not sure if this is a new validation in
place.
ClasspathResourceTest - I'm not sure if the path is getting skewed due to
duplicate resources, or the same resource being added multiple times.
JSF & Scheduler look like changes in the dependency structure. If on
purpose, I'll push up a fix sometime tomorrow.
On Sun, Jun 18, 2017 at 10:04 AM Romain Manni-Bucau <
Post by Romain Manni-Bucau
1. se API (not covered by tck and poorly covered by us ATM)
2. the fastMatching flag should get removed if we can (created due to 1 tck)
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github
<https://github.com/rmannibucau> | LinkedIn
<https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>
Post by Mark Struberg
OWB itself did always ignore it and log a warning. This code did not
get changed for a while.
But we have/had a bug in the arquillian connector which lead to blowing
up on NoClassDefFound.
I need to check whether we fixed this already with another commit.
The ticket is https://issues.apache.org/jira/browse/OWB-1179
LieGrue,
strub
Post by John D. Ament
Just wondering, did you change the behavior when a class isn't found
to
Post by John D. Ament
ignore the bean? Prior versions of OWB would throw an exception.
John
On Sat, Jun 17, 2017 at 4:43 PM Mark Struberg <
Post by Mark Struberg
Yes, it should 'just work' afaict.
We even kept the SPI the same.
We most likely will add an async event related API for better
integration
Post by John D. Ament
Post by Mark Struberg
within TomEE in the future.
But this should still be perfectly backward compatible as OWB will
provide
Post by John D. Ament
Post by Mark Struberg
a default implementation anyway!
If you catch any (unexpected) problems then just ping us.
txs and LieGrue,
strub
Post by John D. Ament
So... just to confirm. Outside of changing the geronimo specs,
taking a
Post by John D. Ament
Post by Mark Struberg
OWB 1.x profile that I may have will just work with OWB 2?
Post by John D. Ament
John
On Sat, Jun 17, 2017 at 1:53 PM Mark Struberg <
Yes, it is 1:1 backward compatible.
The only thing you need to update is the jcdi and
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-annotation_1.3_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-jcdi_2.0_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
They will be released this week as well.
LieGrue,
strub
Post by Ludovic Pénet
Is it a drop i' remplacement ?
If yes, I would gladky test this works, before test driving the new
features.
Post by John D. Ament
Post by Ludovic Pénet
Ludovic
Le 17 juin 2017 19:38:01 GMT+02:00, Mark Struberg <
Hi folks!
We are finished with implementing all CDI-2.0 features and now
successfully pass the standalone TCK!
Post by John D. Ament
Post by Ludovic Pénet
A recent owb-2.0.0-SNAPSHOT is deployed to the Apache Snapshots
repository [1].
Post by John D. Ament
Post by Ludovic Pénet
This get's deployed via Jenkins each night.
It would be great if you could try it out and give us some
feedback!
Post by John D. Ament
Post by Mark Struberg
Post by John D. Ament
Post by Ludovic Pénet
We gonna release it somewhen next week.
txs and LieGrue,
strub
[1] https://repository.apache.org/content/groups/snapshots/
--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma
briÚveté.
John D. Ament
2017-06-20 01:23:40 UTC
Permalink
Ok, so I started to add the missing dependencies, that's not going to
work. In scheduler I added log4j then it complained about some terracotta
class. I think there's a regression in the arquillian adapter,
specifically how it handles classes that may not be present.
Post by John D. Ament
I had a hunch it was that, so did a dependency tree - no luck.
https://paste.apache.org/X3c5
John
IncompatibleClassChangeError, classpath is probably corrupted with an owb 1.0 dependency somehow
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github
<https://github.com/rmannibucau> | LinkedIn
<https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>
Post by Mark Struberg
Oh txs for the catch, will check.
LieGrue,
Strub
Hmm so DeltaSpike is seeing 11 test failures with OWB2.
https://builds.apache.org/view/A-D/view/DeltaSpike/job/DeltaSpike%20OWB%202.0.0/lastCompletedBuild/testReport/
CDI Ctrl Servlet - it looks like a weird error, the impl of this bean
hasn't been changed in 2 years. Not sure if this is a new validation in
place.
ClasspathResourceTest - I'm not sure if the path is getting skewed due
to duplicate resources, or the same resource being added multiple times.
JSF & Scheduler look like changes in the dependency structure. If on
purpose, I'll push up a fix sometime tomorrow.
On Sun, Jun 18, 2017 at 10:04 AM Romain Manni-Bucau <
Post by Romain Manni-Bucau
1. se API (not covered by tck and poorly covered by us ATM)
2. the fastMatching flag should get removed if we can (created due to 1 tck)
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github
<https://github.com/rmannibucau> | LinkedIn
<https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>
Post by Mark Struberg
OWB itself did always ignore it and log a warning. This code did not
get changed for a while.
But we have/had a bug in the arquillian connector which lead to
blowing up on NoClassDefFound.
I need to check whether we fixed this already with another commit.
The ticket is https://issues.apache.org/jira/browse/OWB-1179
LieGrue,
strub
Post by John D. Ament
Just wondering, did you change the behavior when a class isn't found
to
Post by John D. Ament
ignore the bean? Prior versions of OWB would throw an exception.
John
On Sat, Jun 17, 2017 at 4:43 PM Mark Struberg <
Post by Mark Struberg
Yes, it should 'just work' afaict.
We even kept the SPI the same.
We most likely will add an async event related API for better
integration
Post by John D. Ament
Post by Mark Struberg
within TomEE in the future.
But this should still be perfectly backward compatible as OWB will
provide
Post by John D. Ament
Post by Mark Struberg
a default implementation anyway!
If you catch any (unexpected) problems then just ping us.
txs and LieGrue,
strub
Am 17.06.2017 um 22:36 schrieb John D. Ament <
So... just to confirm. Outside of changing the geronimo specs,
taking a
Post by John D. Ament
Post by Mark Struberg
OWB 1.x profile that I may have will just work with OWB 2?
John
On Sat, Jun 17, 2017 at 1:53 PM Mark Struberg <
Yes, it is 1:1 backward compatible.
The only thing you need to update is the jcdi and
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-annotation_1.3_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-jcdi_2.0_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
They will be released this week as well.
LieGrue,
strub
Post by Ludovic Pénet
Is it a drop i' remplacement ?
If yes, I would gladky test this works, before test driving the
new
Post by John D. Ament
Post by Mark Struberg
features.
Post by Ludovic Pénet
Ludovic
Le 17 juin 2017 19:38:01 GMT+02:00, Mark Struberg <
Hi folks!
We are finished with implementing all CDI-2.0 features and now
successfully pass the standalone TCK!
Post by Ludovic Pénet
A recent owb-2.0.0-SNAPSHOT is deployed to the Apache Snapshots
repository [1].
Post by Ludovic Pénet
This get's deployed via Jenkins each night.
It would be great if you could try it out and give us some
feedback!
Post by John D. Ament
Post by Mark Struberg
Post by Ludovic Pénet
We gonna release it somewhen next week.
txs and LieGrue,
strub
[1] https://repository.apache.org/content/groups/snapshots/
--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma
briÚveté.
Romain Manni-Bucau
2017-06-20 08:13:06 UTC
Permalink
Oh yes, Mark changed something about it and the default scanning mode of
CDI doesn't help. Maybe we need to just ignore the classes explicitly


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>
Post by John D. Ament
Ok, so I started to add the missing dependencies, that's not going to
work. In scheduler I added log4j then it complained about some terracotta
class. I think there's a regression in the arquillian adapter,
specifically how it handles classes that may not be present.
Post by John D. Ament
I had a hunch it was that, so did a dependency tree - no luck.
https://paste.apache.org/X3c5
John
On Mon, Jun 19, 2017 at 3:22 AM Romain Manni-Bucau <
Post by Romain Manni-Bucau
IncompatibleClassChangeError, classpath is probably corrupted with an
owb 1.0 dependency somehow
Post by John D. Ament
Post by Romain Manni-Bucau
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github
<https://github.com/rmannibucau> | LinkedIn
<https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>
Post by Mark Struberg
Oh txs for the catch, will check.
LieGrue,
Strub
Hmm so DeltaSpike is seeing 11 test failures with OWB2.
https://builds.apache.org/view/A-D/view/DeltaSpike/job/
DeltaSpike%20OWB%202.0.0/lastCompletedBuild/testReport/
Post by John D. Ament
Post by Romain Manni-Bucau
Post by Mark Struberg
CDI Ctrl Servlet - it looks like a weird error, the impl of this bean
hasn't been changed in 2 years. Not sure if this is a new validation
in
Post by John D. Ament
Post by Romain Manni-Bucau
Post by Mark Struberg
place.
ClasspathResourceTest - I'm not sure if the path is getting skewed due
to duplicate resources, or the same resource being added multiple
times.
Post by John D. Ament
Post by Romain Manni-Bucau
Post by Mark Struberg
JSF & Scheduler look like changes in the dependency structure. If on
purpose, I'll push up a fix sometime tomorrow.
On Sun, Jun 18, 2017 at 10:04 AM Romain Manni-Bucau <
Post by Romain Manni-Bucau
1. se API (not covered by tck and poorly covered by us ATM)
2. the fastMatching flag should get removed if we can (created due to
1
Post by John D. Ament
Post by Romain Manni-Bucau
Post by Mark Struberg
Post by Romain Manni-Bucau
tck)
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github
<https://github.com/rmannibucau> | LinkedIn
<https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>
Post by Mark Struberg
OWB itself did always ignore it and log a warning. This code did not
get changed for a while.
But we have/had a bug in the arquillian connector which lead to
blowing up on NoClassDefFound.
I need to check whether we fixed this already with another commit.
The ticket is https://issues.apache.org/jira/browse/OWB-1179
LieGrue,
strub
Am 18.06.2017 um 13:45 schrieb John D. Ament <
Just wondering, did you change the behavior when a class isn't
found
Post by John D. Ament
Post by Romain Manni-Bucau
Post by Mark Struberg
Post by Romain Manni-Bucau
Post by Mark Struberg
to
ignore the bean? Prior versions of OWB would throw an exception.
John
On Sat, Jun 17, 2017 at 4:43 PM Mark Struberg <
Post by Mark Struberg
Yes, it should 'just work' afaict.
We even kept the SPI the same.
We most likely will add an async event related API for better
integration
Post by Mark Struberg
within TomEE in the future.
But this should still be perfectly backward compatible as OWB will
provide
Post by Mark Struberg
a default implementation anyway!
If you catch any (unexpected) problems then just ping us.
txs and LieGrue,
strub
Am 17.06.2017 um 22:36 schrieb John D. Ament <
So... just to confirm. Outside of changing the geronimo specs,
taking a
Post by Mark Struberg
OWB 1.x profile that I may have will just work with OWB 2?
John
On Sat, Jun 17, 2017 at 1:53 PM Mark Struberg <
Yes, it is 1:1 backward compatible.
The only thing you need to update is the jcdi and
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-annotation_1.3_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-jcdi_2.0_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
They will be released this week as well.
LieGrue,
strub
Post by Ludovic Pénet
Is it a drop i' remplacement ?
If yes, I would gladky test this works, before test driving the
new
Post by Mark Struberg
features.
Post by Ludovic Pénet
Ludovic
Le 17 juin 2017 19:38:01 GMT+02:00, Mark Struberg <
Hi folks!
We are finished with implementing all CDI-2.0 features and now
successfully pass the standalone TCK!
Post by Ludovic Pénet
A recent owb-2.0.0-SNAPSHOT is deployed to the Apache Snapshots
repository [1].
Post by Ludovic Pénet
This get's deployed via Jenkins each night.
It would be great if you could try it out and give us some
feedback!
Post by Mark Struberg
Post by Ludovic Pénet
We gonna release it somewhen next week.
txs and LieGrue,
strub
[1] https://repository.apache.org/content/groups/snapshots/
--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser
ma
Post by John D. Ament
Post by Romain Manni-Bucau
Post by Mark Struberg
Post by Romain Manni-Bucau
Post by Mark Struberg
Post by Mark Struberg
briÚveté.
Mark Struberg
2017-07-09 09:33:57 UTC
Permalink
Hi John!

I've now found a bit time to investigate OWB-2 behaviour in DeltaSpike.
I'm now down to just a few tests and they all seems to be caused by different behaviour of arquillian.

There is a test which checks that a resource must only be served a single time from the ClassPath.
In this test we package the resource into the ShrinkWrap war. And since the OWB-Arquillian adapter does it actually correct, we see this resource twice. The first time from the @Deployment of the test, the other time from the test classpath.
If i move the original test resource to e.g. testonly/myresource.properties then the test passes with OWB. But then it fails with older Weld and OWB arquillian versions as they do not properly serve resources from deployment archives :(

To sum it up: Yes, it's something we need to work on, but it's not an OWB core bug but simply an edge case and portability issue with the various Arquillian containers.

Anyway, thanks for catching it and bringing it up!

txs and LieGrue,
strub
Post by John D. Ament
Hmm so DeltaSpike is seeing 11 test failures with OWB2.
https://builds.apache.org/view/A-D/view/DeltaSpike/job/DeltaSpike%20OWB%202.0.0/lastCompletedBuild/testReport/
CDI Ctrl Servlet - it looks like a weird error, the impl of this bean
hasn't been changed in 2 years. Not sure if this is a new validation in
place.
ClasspathResourceTest - I'm not sure if the path is getting skewed due to
duplicate resources, or the same resource being added multiple times.
JSF & Scheduler look like changes in the dependency structure. If on
purpose, I'll push up a fix sometime tomorrow.
Post by Romain Manni-Bucau
1. se API (not covered by tck and poorly covered by us ATM)
2. the fastMatching flag should get removed if we can (created due to 1 tck)
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github
<https://github.com/rmannibucau> | LinkedIn
<https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>
Post by Mark Struberg
OWB itself did always ignore it and log a warning. This code did not get
changed for a while.
But we have/had a bug in the arquillian connector which lead to blowing
up on NoClassDefFound.
I need to check whether we fixed this already with another commit.
The ticket is https://issues.apache.org/jira/browse/OWB-1179
LieGrue,
strub
Post by John D. Ament
Just wondering, did you change the behavior when a class isn't found to
ignore the bean? Prior versions of OWB would throw an exception.
John
Post by Mark Struberg
Yes, it should 'just work' afaict.
We even kept the SPI the same.
We most likely will add an async event related API for better
integration
Post by John D. Ament
Post by Mark Struberg
within TomEE in the future.
But this should still be perfectly backward compatible as OWB will
provide
Post by John D. Ament
Post by Mark Struberg
a default implementation anyway!
If you catch any (unexpected) problems then just ping us.
txs and LieGrue,
strub
Post by John D. Ament
So... just to confirm. Outside of changing the geronimo specs,
taking a
Post by John D. Ament
Post by Mark Struberg
OWB 1.x profile that I may have will just work with OWB 2?
Post by John D. Ament
John
On Sat, Jun 17, 2017 at 1:53 PM Mark Struberg
Yes, it is 1:1 backward compatible.
The only thing you need to update is the jcdi and common-annotations
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-annotation_1.3_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-jcdi_2.0_spec</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
They will be released this week as well.
LieGrue,
strub
Post by Ludovic Pénet
Is it a drop i' remplacement ?
If yes, I would gladky test this works, before test driving the new
features.
Post by John D. Ament
Post by Ludovic Pénet
Ludovic
Hi folks!
We are finished with implementing all CDI-2.0 features and now
successfully pass the standalone TCK!
Post by John D. Ament
Post by Ludovic Pénet
A recent owb-2.0.0-SNAPSHOT is deployed to the Apache Snapshots
repository [1].
Post by John D. Ament
Post by Ludovic Pénet
This get's deployed via Jenkins each night.
It would be great if you could try it out and give us some feedback!
We gonna release it somewhen next week.
txs and LieGrue,
strub
[1] https://repository.apache.org/content/groups/snapshots/
--
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma
brièveté.
Gurkan Erdogdu
2017-06-25 18:43:54 UTC
Permalink
Hi all

As I said earlier , Meecrowave project needs to be seperated from owb, it has own project page, codebase, issues, release cycle etc. There are two options in here either Tomee subproject or new in incubator project. My binding vote will be -1 for such release otherwise. I know that incubator projects needs much more admin work but from my opinion this is the way of introducing such new project in ASF

Regards

Gurkan
Post by Mark Struberg
Hi folks!
We are finished with implementing all CDI-2.0 features and now successfully pass the standalone TCK!
A recent owb-2.0.0-SNAPSHOT is deployed to the Apache Snapshots repository [1].
This get's deployed via Jenkins each night.
It would be great if you could try it out and give us some feedback!
We gonna release it somewhen next week.
txs and LieGrue,
strub
[1] https://repository.apache.org/content/groups/snapshots/
Romain Manni-Bucau
2017-06-25 18:56:19 UTC
Permalink
Hi Gurkan

What is the rational behind such a reasonning since core of meecrowave is
owb and that we agreed to import?

Side note: tomee doesnt fit since we dont impl specs bit just build a
server centered around owb to avoid tomcat integration issues we often see
on the list.
Post by Gurkan Erdogdu
Hi all
As I said earlier , Meecrowave project needs to be seperated from owb, it
has own project page, codebase, issues, release cycle etc. There are two
options in here either Tomee subproject or new in incubator project. My
binding vote will be -1 for such release otherwise. I know that incubator
projects needs much more admin work but from my opinion this is the way of
introducing such new project in ASF
Regards
Gurkan
Post by Mark Struberg
Hi folks!
We are finished with implementing all CDI-2.0 features and now
successfully pass the standalone TCK!
Post by Mark Struberg
A recent owb-2.0.0-SNAPSHOT is deployed to the Apache Snapshots
repository [1].
Post by Mark Struberg
This get's deployed via Jenkins each night.
It would be great if you could try it out and give us some feedback!
We gonna release it somewhen next week.
txs and LieGrue,
strub
[1] https://repository.apache.org/content/groups/snapshots/
Gurkan Erdogdu
2017-06-25 19:03:18 UTC
Permalink
Hi Romain

Because it is a very different mind , it just uses the owb but may also use other cdi implementation in the future

Also, it may implement the microprofile speficiation

Also it has its own project page, codebase, release cycle, issues etc. It just depends on owb as library

So for the future perpective, it is now to route for such action at the beginning, and so it will much more getting attraction from the asf and other communities

I will be gald to help on such effort

Regards

Gurkan
Post by Romain Manni-Bucau
Hi Gurkan
What is the rational behind such a reasonning since core of meecrowave is owb and that we agreed to import?
Side note: tomee doesnt fit since we dont impl specs bit just build a server centered around owb to avoid tomcat integration issues we often see on the list.
Post by Gurkan Erdogdu
Hi all
As I said earlier , Meecrowave project needs to be seperated from owb, it has own project page, codebase, issues, release cycle etc. There are two options in here either Tomee subproject or new in incubator project. My binding vote will be -1 for such release otherwise. I know that incubator projects needs much more admin work but from my opinion this is the way of introducing such new project in ASF
Regards
Gurkan
Post by Mark Struberg
Hi folks!
We are finished with implementing all CDI-2.0 features and now successfully pass the standalone TCK!
A recent owb-2.0.0-SNAPSHOT is deployed to the Apache Snapshots repository [1].
This get's deployed via Jenkins each night.
It would be great if you could try it out and give us some feedback!
We gonna release it somewhen next week.
txs and LieGrue,
strub
[1] https://repository.apache.org/content/groups/snapshots/
Romain Manni-Bucau
2017-06-25 19:08:19 UTC
Permalink
Le 25 juin 2017 21:03, "Gurkan Erdogdu" <***@yahoo.com> a écrit :


Hi Romain

Because it is a very different mind , it just uses the owb but may also use
other cdi implementation in the future



No no. You missed a central point : owb+cxf+tomcat highly integrated vs a
portable stack like hammock is. Here we just want to integrate our
preferred stack.


Also, it may implement the microprofile speficiation



It could but still compat with owb afaik.


Also it has its own project page, codebase, release cycle, issues etc. It
just depends on owb as library


True, it is a subproject



So for the future perpective, it is now to route for such action at the
beginning, and so it will much more getting attraction from the asf and
other communities


We used a subproject cause was proven being wrong on this hypothesis we did
for some other incubator projects



I will be gald to help on such effort


Why not helping here?


Regards

Gurkan

On 25 Jun 2017, at 21:56, Romain Manni-Bucau <***@gmail.com> wrote:

Hi Gurkan

What is the rational behind such a reasonning since core of meecrowave is
owb and that we agreed to import?

Side note: tomee doesnt fit since we dont impl specs bit just build a
server centered around owb to avoid tomcat integration issues we often see
on the list.
Post by Gurkan Erdogdu
Hi all
As I said earlier , Meecrowave project needs to be seperated from owb, it
has own project page, codebase, issues, release cycle etc. There are two
options in here either Tomee subproject or new in incubator project. My
binding vote will be -1 for such release otherwise. I know that incubator
projects needs much more admin work but from my opinion this is the way of
introducing such new project in ASF
Regards
Gurkan
Post by Mark Struberg
Hi folks!
We are finished with implementing all CDI-2.0 features and now
successfully pass the standalone TCK!
Post by Mark Struberg
A recent owb-2.0.0-SNAPSHOT is deployed to the Apache Snapshots
repository [1].
Post by Mark Struberg
This get's deployed via Jenkins each night.
It would be great if you could try it out and give us some feedback!
We gonna release it somewhen next week.
txs and LieGrue,
strub
[1] https://repository.apache.org/content/groups/snapshots/
Gurkan Erdogdu
2017-06-25 19:21:56 UTC
Permalink
Hi Romain
Because this is a new initiative, it must follow the ASF rules even if graduate as a subproject

But imo, this is not a subproject, because it has different aims from owb core, owb aim is just implement the specification

Please have a look http://incubator.apache.org/guides/graduation.html#subproject-or-top-level

So my advice is to write an incubator project , sponsored by the owb, and graduate as sub or top level project ( my vote will be as tlp)

We can also bring this issue in a board report and getting advice from the board

Regards

Gurkan
Post by Gurkan Erdogdu
Hi Romain
Because it is a very different mind , it just uses the owb but may also use other cdi implementation in the future
No no. You missed a central point : owb+cxf+tomcat highly integrated vs a portable stack like hammock is. Here we just want to integrate our preferred stack.
Also, it may implement the microprofile speficiation
It could but still compat with owb afaik.
Also it has its own project page, codebase, release cycle, issues etc. It just depends on owb as library
True, it is a subproject
So for the future perpective, it is now to route for such action at the beginning, and so it will much more getting attraction from the asf and other communities
We used a subproject cause was proven being wrong on this hypothesis we did for some other incubator projects
I will be gald to help on such effort
Why not helping here?
Regards
Gurkan
Post by Romain Manni-Bucau
Hi Gurkan
What is the rational behind such a reasonning since core of meecrowave is owb and that we agreed to import?
Side note: tomee doesnt fit since we dont impl specs bit just build a server centered around owb to avoid tomcat integration issues we often see on the list.
Post by Gurkan Erdogdu
Hi all
As I said earlier , Meecrowave project needs to be seperated from owb, it has own project page, codebase, issues, release cycle etc. There are two options in here either Tomee subproject or new in incubator project. My binding vote will be -1 for such release otherwise. I know that incubator projects needs much more admin work but from my opinion this is the way of introducing such new project in ASF
Regards
Gurkan
Post by Mark Struberg
Hi folks!
We are finished with implementing all CDI-2.0 features and now successfully pass the standalone TCK!
A recent owb-2.0.0-SNAPSHOT is deployed to the Apache Snapshots repository [1].
This get's deployed via Jenkins each night.
It would be great if you could try it out and give us some feedback!
We gonna release it somewhen next week.
txs and LieGrue,
strub
[1] https://repository.apache.org/content/groups/snapshots/
Romain Manni-Bucau
2017-06-25 19:24:44 UTC
Permalink
Le 25 juin 2017 21:22, "Gurkan Erdogdu" <***@yahoo.com.invalid> a
écrit :

Hi Romain
Because this is a new initiative, it must follow the ASF rules even if
graduate as a subproject

But imo, this is not a subproject, because it has different aims from owb
core, owb aim is just implement the specification

Please have a look http://incubator.apache.org/guides/graduation.html#
subproject-or-top-level

So my advice is to write an incubator project , sponsored by the owb, and
graduate as sub or top level project ( my vote will be as tlp)

We can also bring this issue in a board report and getting advice from the
board



Maybe we should ask them yes. What do others think?

Dont sure we need to delay next release cause of it but what about pinging
the board in next report?


Regards

Gurkan
Post by Gurkan Erdogdu
Hi Romain
Because it is a very different mind , it just uses the owb but may also
use other cdi implementation in the future
Post by Gurkan Erdogdu
No no. You missed a central point : owb+cxf+tomcat highly integrated vs a
portable stack like hammock is. Here we just want to integrate our
preferred stack.
Post by Gurkan Erdogdu
Also, it may implement the microprofile speficiation
It could but still compat with owb afaik.
Also it has its own project page, codebase, release cycle, issues etc. It
just depends on owb as library
Post by Gurkan Erdogdu
True, it is a subproject
So for the future perpective, it is now to route for such action at the
beginning, and so it will much more getting attraction from the asf and
other communities
Post by Gurkan Erdogdu
We used a subproject cause was proven being wrong on this hypothesis we
did for some other incubator projects
Post by Gurkan Erdogdu
I will be gald to help on such effort
Why not helping here?
Regards
Gurkan
Post by Romain Manni-Bucau
Hi Gurkan
What is the rational behind such a reasonning since core of meecrowave
is owb and that we agreed to import?
Post by Gurkan Erdogdu
Post by Romain Manni-Bucau
Side note: tomee doesnt fit since we dont impl specs bit just build a
server centered around owb to avoid tomcat integration issues we often see
on the list.
Post by Gurkan Erdogdu
Post by Romain Manni-Bucau
Post by Gurkan Erdogdu
Hi all
As I said earlier , Meecrowave project needs to be seperated from owb,
it has own project page, codebase, issues, release cycle etc. There are two
options in here either Tomee subproject or new in incubator project. My
binding vote will be -1 for such release otherwise. I know that incubator
projects needs much more admin work but from my opinion this is the way of
introducing such new project in ASF
Post by Gurkan Erdogdu
Post by Romain Manni-Bucau
Post by Gurkan Erdogdu
Regards
Gurkan
Post by Mark Struberg
Hi folks!
We are finished with implementing all CDI-2.0 features and now
successfully pass the standalone TCK!
Post by Gurkan Erdogdu
Post by Romain Manni-Bucau
Post by Gurkan Erdogdu
Post by Mark Struberg
A recent owb-2.0.0-SNAPSHOT is deployed to the Apache Snapshots repository [1].
This get's deployed via Jenkins each night.
It would be great if you could try it out and give us some feedback!
We gonna release it somewhen next week.
txs and LieGrue,
strub
[1] https://repository.apache.org/content/groups/snapshots/
Gurkan Erdogdu
2017-06-25 19:39:27 UTC
Permalink
Yup for owb release, no need to delay I am fine with it
Post by Gurkan Erdogdu
Hi Romain
Because this is a new initiative, it must follow the ASF rules even if
graduate as a subproject
But imo, this is not a subproject, because it has different aims from owb
core, owb aim is just implement the specification
Please have a look http://incubator.apache.org/guides/graduation.html#
subproject-or-top-level
So my advice is to write an incubator project , sponsored by the owb, and
graduate as sub or top level project ( my vote will be as tlp)
We can also bring this issue in a board report and getting advice from the board
Maybe we should ask them yes. What do others think?
Dont sure we need to delay next release cause of it but what about pinging
the board in next report?
Regards
Gurkan
Post by Gurkan Erdogdu
Hi Romain
Because it is a very different mind , it just uses the owb but may also
use other cdi implementation in the future
Post by Gurkan Erdogdu
No no. You missed a central point : owb+cxf+tomcat highly integrated vs a
portable stack like hammock is. Here we just want to integrate our
preferred stack.
Post by Gurkan Erdogdu
Also, it may implement the microprofile speficiation
It could but still compat with owb afaik.
Also it has its own project page, codebase, release cycle, issues etc. It
just depends on owb as library
Post by Gurkan Erdogdu
True, it is a subproject
So for the future perpective, it is now to route for such action at the
beginning, and so it will much more getting attraction from the asf and
other communities
Post by Gurkan Erdogdu
We used a subproject cause was proven being wrong on this hypothesis we
did for some other incubator projects
Post by Gurkan Erdogdu
I will be gald to help on such effort
Why not helping here?
Regards
Gurkan
Post by Romain Manni-Bucau
Hi Gurkan
What is the rational behind such a reasonning since core of meecrowave
is owb and that we agreed to import?
Post by Gurkan Erdogdu
Post by Romain Manni-Bucau
Side note: tomee doesnt fit since we dont impl specs bit just build a
server centered around owb to avoid tomcat integration issues we often see
on the list.
Post by Gurkan Erdogdu
Post by Romain Manni-Bucau
Post by Gurkan Erdogdu
Hi all
As I said earlier , Meecrowave project needs to be seperated from owb,
it has own project page, codebase, issues, release cycle etc. There are two
options in here either Tomee subproject or new in incubator project. My
binding vote will be -1 for such release otherwise. I know that incubator
projects needs much more admin work but from my opinion this is the way of
introducing such new project in ASF
Post by Gurkan Erdogdu
Post by Romain Manni-Bucau
Post by Gurkan Erdogdu
Regards
Gurkan
Post by Mark Struberg
Hi folks!
We are finished with implementing all CDI-2.0 features and now
successfully pass the standalone TCK!
Post by Gurkan Erdogdu
Post by Romain Manni-Bucau
Post by Gurkan Erdogdu
Post by Mark Struberg
A recent owb-2.0.0-SNAPSHOT is deployed to the Apache Snapshots
repository [1].
Post by Gurkan Erdogdu
Post by Romain Manni-Bucau
Post by Gurkan Erdogdu
Post by Mark Struberg
This get's deployed via Jenkins each night.
It would be great if you could try it out and give us some feedback!
We gonna release it somewhen next week.
txs and LieGrue,
strub
[1] https://repository.apache.org/content/groups/snapshots/
Loading...