Re: [VOTE] Release Apache OpenWebBeans-4.0.2

[Gerhard Petracek]

+1

regards,
gerhard



Am Mo., 29. Jan. 2024 um 10:37 Uhr schrieb Mark Struberg
:
>
> Hi lords and ladies!
>
> I'd like to call a VOTE on releasing Apache OpenWebBeans-4.0.2
>
> We fixed the following tickets
>
> Bug
> [OWB-1436] - org.apache.webbeans.el22.WrappedValueExpressionNode'does not 
> have the property 'xxx'
> [OWB-1437] - InstanceImpl#destroy might lead to a NPE
>
> Improvement
> [OWB-1434] - upgrade various dependencies to more recent versions
>
>
> The stating repo is here
>
> https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1085/
>
>
> The source jar is available at
> https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1085/org/apache/openwebbeans/openwebbeans/4.0.2/
>
> sha512 is 
> 28199a1eaff15f3c5b9a6d11467eb595a3c9e78bfde5e9e624ed9e4031d48cb86546c88836f92ac0040f30261a3081a7fa543959ef1489061de31ef5f27fcc5f
>
> Please VOTE
>
> [+1] let's ship it!
> [+0] meh, don't care or not perfect
> [-1] abort, there is a ${showstopper}
>
> The VOTE is open for 72h
>
> txs and LieGrue,
> strub
>

Re: [VOTE] release Apache OpenWebBeans-2.0.14

[Gerhard Petracek]

+1

regards,
gerhard



Am Sa., 11. Jan. 2020 um 16:27 Uhr schrieb Mark Struberg
:
>
> Hi folks!
>
> I've run all the tasks to release OWB 2.0.14
>
> Here is the list of fixed bugs:
>
> Bug
>
> • [OWB-1280] - NPE in filterExcludedJars
> • [OWB-1303] - AbstractOwbBean does not conserve the actual user code 
> exception when creating a bean fails
> • [OWB-1305] - Extensions can be looked up during their bean creation 
> leading to a NPE
> • [OWB-1309] - upgrade to new tomcat7.0.99 introduces a Problem with 
> a new NoSuchMethodException
> Improvement
>
> • [OWB-1306] - Be more tolerant to java version in our unsafe/proxy 
> usage/registration
> Task
>
> • [OWB-1304] - Change OWB to build fine with Java11
> • [OWB-1307] - remove conversation.periodicDelay option from our 
> config
> • [OWB-1308] - dependency upgrades
>
>
> The staging repo is 
> https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1059
>
> The source zip can be found here
> https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1059/org/apache/openwebbeans/openwebbeans/2.0.14/
> sha1 is c0b4fecab7eb17209ff72aa6df4d4ff898433df1
>
>
> Please VOTE:
>
> [+1] go ship it
> [+0] meh, don't care
> [-1] stop, there is a ${showstopper}
>
> The VOTE is open for 72h
>
>
> txs and LieGrue,
> strub
>
>

Re: [DISCUSS] also move the Meecrowave repo to GITbox?

[Gerhard Petracek]

+1

regards,
gerhard



Am Do., 9. Mai 2019 um 08:52 Uhr schrieb Mark Struberg
:
>
> hi folks!
>
> Since we now already moved OWB itself and the meecrowave-examples, should we 
> also move Meecrowave to GIT?
> This is affect the last remaining project sticking with SVN (except the site 
> which will remain SVN).
>
> wdyt?
>
> I'm +1 for moving meecrowave to GIT as well.
>
> LieGrue,
> strub
>

Re: Injection point for qualified points without @inject?

[Gerhard Petracek]

yes a chain or a spi with priority (both should be fine).

regards,
gerhard



Am Do., 9. Mai 2019 um 22:35 Uhr schrieb Romain Manni-Bucau
:
>
> I see, means it is not a spi but a "spi chain" right? (handle vs
> isSupported+handle)
>
> Makes sense this way to me.
>
> Le jeu. 9 mai 2019 à 22:31, Gerhard Petracek  a
> écrit :
>
> > hi romain,
> >
> > i've seen different (special) cases which would have been easier with
> > such a spi - e.g. the integration of custom
> > "module-binding"/qualifier/... concepts (without annotations) - not
> > only but also - for injecting beans of other containers which don't
> > force annotations (and e.g. @Named isn't useful)
> >
> > most parts are possible via std. cdi-producers (that's quite verbose
> > and in many cases hardly ~accepted in projects), std. cdi-extensions
> > (to get the acceptance for it is sometimes also not that easy, because
> > it can get quite ~complex) or the resource-injection spi (it also has
> > its disadvantages, but it's easy/easier to use).
> > most use-cases came up around migrations to ee6 -> the demand might
> > decrease over time... some switched from a step-by-step migration to
> > an immediate migration and some just migrated to something different
> > (in the end topics like that can be a significant part of the decisive
> > factor). -> large/r migration-projects might benefit from such an
> > option (i still know large projects using ee <= v5).
> >
> > @OWB-1287:
> > i'll have a look at it next week
> >
> > regards,
> > gerhard
> >
> > Am Do., 9. Mai 2019 um 18:55 Uhr schrieb Romain Manni-Bucau
> > :
> > >
> > > Hi guys,
> > >
> > > pushed a patch about it - https://issues.apache.org/jira/browse/OWB-1287
> > >
> > > you can see it is very trivial
> > >
> > > I have a few open points about it:
> > >
> > > 1. (For Gerhard) do you want a service for that? How would you generalize
> > > it?
> > > 2. I disabled the feature in impl and tck modules cause a few tests were
> > > failing - I only activated it in the test about that particular feature.
> > In
> > > impl it is a bit of work but we can reverse the setup - ie on by default.
> > > In TCK it is not hard since a single test fails but it requires to setup
> > an
> > > arquillian extension to customize - enrich - the owb configuration for
> > that
> > > test. Not sure how we stand about it and if we care much but this is a
> > > small detail which can be surprising when seen.
> > > 3. (likely for Mark) I pushed it on svn, is git already ready? Didn't see
> > > it.
> > >
> > > Don't hesitate to give some feedback about it.
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > <https://rmannibucau.metawerx.net/> | Old Blog
> > > <http://rmannibucau.wordpress.com> | Github <
> > https://github.com/rmannibucau> |
> > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> > > <
> > https://www.packtpub.com/application-development/java-ee-8-high-performance
> > >
> > >
> > >
> > > Le mer. 8 mai 2019 à 20:52, Romain Manni-Bucau  a
> > > écrit :
> > >
> > > > Well, it is not that I dont like it, I just dont see such a SPI once we
> > > > have qualifier feature or what it would bring. Do you have an example?
> > > >
> > > > That said adding a service and extracting that code is not super costly
> > > > but semantically/design-ly not sure how to defend it yet.
> > > >
> > > > Le mer. 8 mai 2019 à 20:41, Gerhard Petracek  a
> > > > écrit :
> > > >
> > > >> hi romain,
> > > >>
> > > >> it was just a hint - that there would be a chance to make owb even
> > > >> more plugable and maybe to refactor an existing spi to an even more
> > > >> useful spi.
> > > >> i'm fine with it, if you don't like to take such a chance. the overall
> > > >> use-case isn't that important to start a long/er discussion.
> > > >>
> > > >> regards,
> > > >> gerhard
> > > >>
> > > >>
> > > >>
> > > >> Am Mo., 6. Mai 2019 um 23:24 Uhr schrieb Romain Manni-Bucau
> > > >> :
> > > >> >
> > > >> > Le lun. 6 mai 2019 à 22:51, 

Re: Injection point for qualified points without @inject?

[Gerhard Petracek]

+1

regards,
gerhard



Am Do., 9. Mai 2019 um 22:23 Uhr schrieb Romain Manni-Bucau
:
>
> Hi Arne,
>
> No because constructors are just marked with inject, not constructor
> injections (1 vs N).
>
> I can do it tomorrow - will try the spi thing too. Just thought it was not
> impacting as much dev - I rarely use it cause of proxying requirements so
> can be biased.
>
> Just let me know you want it and Ill do it for you with pleasure.
>
> Le jeu. 9 mai 2019 à 21:53, Arne Limburg  a
> écrit :
>
> > Hi Romain,
> >
> > Did not take a look at it for now, just read the JIRA issue and wondered,
> > what about constructors. Did you implement anything regarding constructors
> > such that when a constructor with a parameter with a qualifier exists, that
> > constructor is taken instead of the default constructor?
> >
> > Cheers,
> > Arne
> >
> > --
> > Arne Limburg – Enterprise Architect
> >
> >
> >
> > OPEN KNOWLEDGE GmbH
> > Poststraße 1, 26122 Oldenburg
> > Mobil: +49 151 - 108 22 942
> > Tel: +49 441 - 4082-154
> > Fax: +49 441 - 4082-111
> > arne.limb...@openknowledge.de
> > www.openknowledge.de
> >
> > Registergericht: Amtsgericht Oldenburg, HRB 4670
> > Geschäftsführer: Lars Röwekamp, Jens Schumann
> >
> > Nächste Konferenz:
> >
> > Java Forum Nord | Hannover | 24. September 2019
> >
> > Nächste Akademie:
> >
> > API, Microservices & DDD Summit | München | 17. - 19. Juni 2019
> >
> > Treffen Sie uns auf weiteren Konferenzen,
> > Summits und Events:
> >
> > Zu unseren weiteren Events
> >
> >
> >
> > Am 09.05.19, 18:55 schrieb "Romain Manni-Bucau" :
> >
> > Hi guys,
> >
> > pushed a patch about it -
> > https://issues.apache.org/jira/browse/OWB-1287
> >
> > you can see it is very trivial
> >
> > I have a few open points about it:
> >
> > 1. (For Gerhard) do you want a service for that? How would you
> > generalize
> > it?
> > 2. I disabled the feature in impl and tck modules cause a few tests
> > were
> > failing - I only activated it in the test about that particular
> > feature. In
> > impl it is a bit of work but we can reverse the setup - ie on by
> > default.
> > In TCK it is not hard since a single test fails but it requires to
> > setup an
> > arquillian extension to customize - enrich - the owb configuration for
> > that
> > test. Not sure how we stand about it and if we care much but this is a
> > small detail which can be surprising when seen.
> > 3. (likely for Mark) I pushed it on svn, is git already ready? Didn't
> > see
> > it.
> >
> > Don't hesitate to give some feedback about it.
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://rmannibucau.metawerx.net/> | Old Blog
> > <http://rmannibucau.wordpress.com> | Github <
> > https://github.com/rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> > <
> > https://www.packtpub.com/application-development/java-ee-8-high-performance
> > >
> >
> >
> > Le mer. 8 mai 2019 à 20:52, Romain Manni-Bucau 
> > a
> > écrit :
> >
> > > Well, it is not that I dont like it, I just dont see such a SPI once
> > we
> > > have qualifier feature or what it would bring. Do you have an
> > example?
> > >
> > > That said adding a service and extracting that code is not super
> > costly
> > > but semantically/design-ly not sure how to defend it yet.
> > >
> > > Le mer. 8 mai 2019 à 20:41, Gerhard Petracek 
> > a
> > > écrit :
> > >
> > >> hi romain,
> > >>
> > >> it was just a hint - that there would be a chance to make owb even
> > >> more plugable and maybe to refactor an existing spi to an even more
> > >> useful spi.
> > >> i'm fine with it, if you don't like to take such a chance. the
> > overall
> > >> use-case isn't that important to start a long/er discussion.
> > >>
> > >> regards,
> > >> gerhard
> > >>
> > >>
> > >>
> > >> Am Mo., 6. Mai 2019 um 23:24 Uhr schrieb Romain Manni-Bucau
> > >> :
> >

Re: Injection point for qualified points without @inject?

[Gerhard Petracek]

hi romain,

i've seen different (special) cases which would have been easier with
such a spi - e.g. the integration of custom
"module-binding"/qualifier/... concepts (without annotations) - not
only but also - for injecting beans of other containers which don't
force annotations (and e.g. @Named isn't useful)

most parts are possible via std. cdi-producers (that's quite verbose
and in many cases hardly ~accepted in projects), std. cdi-extensions
(to get the acceptance for it is sometimes also not that easy, because
it can get quite ~complex) or the resource-injection spi (it also has
its disadvantages, but it's easy/easier to use).
most use-cases came up around migrations to ee6 -> the demand might
decrease over time... some switched from a step-by-step migration to
an immediate migration and some just migrated to something different
(in the end topics like that can be a significant part of the decisive
factor). -> large/r migration-projects might benefit from such an
option (i still know large projects using ee <= v5).

@OWB-1287:
i'll have a look at it next week

regards,
gerhard

Am Do., 9. Mai 2019 um 18:55 Uhr schrieb Romain Manni-Bucau
:
>
> Hi guys,
>
> pushed a patch about it - https://issues.apache.org/jira/browse/OWB-1287
>
> you can see it is very trivial
>
> I have a few open points about it:
>
> 1. (For Gerhard) do you want a service for that? How would you generalize
> it?
> 2. I disabled the feature in impl and tck modules cause a few tests were
> failing - I only activated it in the test about that particular feature. In
> impl it is a bit of work but we can reverse the setup - ie on by default.
> In TCK it is not hard since a single test fails but it requires to setup an
> arquillian extension to customize - enrich - the owb configuration for that
> test. Not sure how we stand about it and if we care much but this is a
> small detail which can be surprising when seen.
> 3. (likely for Mark) I pushed it on svn, is git already ready? Didn't see
> it.
>
> Don't hesitate to give some feedback about it.
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>
>
> Le mer. 8 mai 2019 à 20:52, Romain Manni-Bucau  a
> écrit :
>
> > Well, it is not that I dont like it, I just dont see such a SPI once we
> > have qualifier feature or what it would bring. Do you have an example?
> >
> > That said adding a service and extracting that code is not super costly
> > but semantically/design-ly not sure how to defend it yet.
> >
> > Le mer. 8 mai 2019 à 20:41, Gerhard Petracek  a
> > écrit :
> >
> >> hi romain,
> >>
> >> it was just a hint - that there would be a chance to make owb even
> >> more plugable and maybe to refactor an existing spi to an even more
> >> useful spi.
> >> i'm fine with it, if you don't like to take such a chance. the overall
> >> use-case isn't that important to start a long/er discussion.
> >>
> >> regards,
> >> gerhard
> >>
> >>
> >>
> >> Am Mo., 6. Mai 2019 um 23:24 Uhr schrieb Romain Manni-Bucau
> >> :
> >> >
> >> > Le lun. 6 mai 2019 à 22:51, Gerhard Petracek  a
> >> > écrit :
> >> >
> >> > > my point was just to add a spi similar to the resource-injection
> >> spi...
> >> > > or maybe we can even unify the spi for all types of injections.
> >> > >
> >> >
> >> > Using qualifier - even through extensions - it does then so maybe we csn
> >> > drop spi
> >> >
> >> >
> >> > > regards,
> >> > > gerhard
> >> > >
> >> > >
> >> > >
> >> > > Am Mo., 6. Mai 2019 um 20:43 Uhr schrieb Romain Manni-Bucau
> >> > > :
> >> > > >
> >> > > > Well im happy with the spi option but since it would be in impl not
> >> sure
> >> > > we
> >> > > > need to slow down the boot instead of hardcoding it. Or did you
> >> mean in
> >> > > > term of codepath but still bypassing service loader?
> >> > > >
> >> > > > Side note: we should align reflection on xbean which supports meta
> >> > > > annotation and potentially aliasing, this is a bug between s

Re: Injection point for qualified points without @inject?

[Gerhard Petracek]

hi romain,

it was just a hint - that there would be a chance to make owb even
more plugable and maybe to refactor an existing spi to an even more
useful spi.
i'm fine with it, if you don't like to take such a chance. the overall
use-case isn't that important to start a long/er discussion.

regards,
gerhard



Am Mo., 6. Mai 2019 um 23:24 Uhr schrieb Romain Manni-Bucau
:
>
> Le lun. 6 mai 2019 à 22:51, Gerhard Petracek  a
> écrit :
>
> > my point was just to add a spi similar to the resource-injection spi...
> > or maybe we can even unify the spi for all types of injections.
> >
>
> Using qualifier - even through extensions - it does then so maybe we csn
> drop spi
>
>
> > regards,
> > gerhard
> >
> >
> >
> > Am Mo., 6. Mai 2019 um 20:43 Uhr schrieb Romain Manni-Bucau
> > :
> > >
> > > Well im happy with the spi option but since it would be in impl not sure
> > we
> > > need to slow down the boot instead of hardcoding it. Or did you mean in
> > > term of codepath but still bypassing service loader?
> > >
> > > Side note: we should align reflection on xbean which supports meta
> > > annotation and potentially aliasing, this is a bug between scanning and
> > > runtime model we have today - see @Meta or @Metaroot support in xbean.
> > That
> > > said it is another topic ;).
> > >
> > > Le lun. 6 mai 2019 à 15:45, Mark Struberg  a
> > > écrit :
> > >
> > > > Hmm, nah, too memory intense and slower than the other solution I'd
> > say.
> > > >
> > > > LieGrue,
> > > > strub
> > > >
> > > >
> > > > > Am 06.05.2019 um 14:41 schrieb Arne Limburg <
> > > > arne.limb...@openknowledge.de>:
> > > > >
> > > > > Hmm,
> > > > > thinking more of it:
> > > > > Shouldn't it be just an Extension that adds an @Inject Annotation to
> > > > every Field and Method parameter that has a qualifier?
> > > > >
> > > > > Cheers,
> > > > > Arne
> > > > >
> > > > > --
> > > > > Arne Limburg – Enterprise Architect
> > > > >
> > > > >
> > > > >
> > > > > OPEN KNOWLEDGE GmbH
> > > > > Poststraße 1, 26122 Oldenburg
> > > > > Mobil: +49 151 - 108 22 942
> > > > > Tel: +49 441 - 4082-154
> > > > > Fax: +49 441 - 4082-111
> > > > > arne.limb...@openknowledge.de
> > > > > www.openknowledge.de
> > > > >
> > > > > Registergericht: Amtsgericht Oldenburg, HRB 4670
> > > > > Geschäftsführer: Lars Röwekamp, Jens Schumann
> > > > >
> > > > > Nächste Konferenz:
> > > > >
> > > > > Java Forum Nord | Hannover | 24. September 2019
> > > > >
> > > > > Nächste Akademie:
> > > > >
> > > > > API, Microservices & DDD Summit | München | 17. - 19. Juni 2019
> > > > >
> > > > > Treffen Sie uns auf weiteren Konferenzen,
> > > > > Summits und Events:
> > > > >
> > > > > Zu unseren weiteren Events
> > > > >
> > > > >
> > > > >
> > > > > Am 06.05.19, 14:06 schrieb "Gerhard Petracek"  > >:
> > > > >
> > > > >hi romain,
> > > > >
> > > > >some years ago i tried to do something similar (afair with owb
> > 1.0.x)
> > > > >based on our plugin-spi.
> > > > >back then it was just possible via a plugin for resource-injection
> > > > >(and it was a bit "tricky").
> > > > >if nothing changed in the meantime, we should take the chance to
> > add a
> > > > >more powerful injection-spi (to allow multiple plugins which can
> > > > >participate in the "injection-lifecycle").
> > > > >-> your approach would be one of many plugins users can add (e.g.
> > with
> > > > >auto. activation...).
> > > > >
> > > > >regards,
> > > > >gerhard
> > > > >
> > > > >Am So., 5. Mai 2019 um 22:09 Uhr schrieb Romain Manni-Bucau
> > > > >:
> > > > >>
> > > > >> Good catch!
> > > > >>
> > > > >> If no objection i can push a f

Re: Injection point for qualified points without @inject?

[Gerhard Petracek]

my point was just to add a spi similar to the resource-injection spi...
or maybe we can even unify the spi for all types of injections.

regards,
gerhard



Am Mo., 6. Mai 2019 um 20:43 Uhr schrieb Romain Manni-Bucau
:
>
> Well im happy with the spi option but since it would be in impl not sure we
> need to slow down the boot instead of hardcoding it. Or did you mean in
> term of codepath but still bypassing service loader?
>
> Side note: we should align reflection on xbean which supports meta
> annotation and potentially aliasing, this is a bug between scanning and
> runtime model we have today - see @Meta or @Metaroot support in xbean. That
> said it is another topic ;).
>
> Le lun. 6 mai 2019 à 15:45, Mark Struberg  a
> écrit :
>
> > Hmm, nah, too memory intense and slower than the other solution I'd say.
> >
> > LieGrue,
> > strub
> >
> >
> > > Am 06.05.2019 um 14:41 schrieb Arne Limburg <
> > arne.limb...@openknowledge.de>:
> > >
> > > Hmm,
> > > thinking more of it:
> > > Shouldn't it be just an Extension that adds an @Inject Annotation to
> > every Field and Method parameter that has a qualifier?
> > >
> > > Cheers,
> > > Arne
> > >
> > > --
> > > Arne Limburg – Enterprise Architect
> > >
> > >
> > >
> > > OPEN KNOWLEDGE GmbH
> > > Poststraße 1, 26122 Oldenburg
> > > Mobil: +49 151 - 108 22 942
> > > Tel: +49 441 - 4082-154
> > > Fax: +49 441 - 4082-111
> > > arne.limb...@openknowledge.de
> > > www.openknowledge.de
> > >
> > > Registergericht: Amtsgericht Oldenburg, HRB 4670
> > > Geschäftsführer: Lars Röwekamp, Jens Schumann
> > >
> > > Nächste Konferenz:
> > >
> > > Java Forum Nord | Hannover | 24. September 2019
> > >
> > > Nächste Akademie:
> > >
> > > API, Microservices & DDD Summit | München | 17. - 19. Juni 2019
> > >
> > > Treffen Sie uns auf weiteren Konferenzen,
> > > Summits und Events:
> > >
> > > Zu unseren weiteren Events
> > >
> > >
> > >
> > > Am 06.05.19, 14:06 schrieb "Gerhard Petracek" :
> > >
> > >hi romain,
> > >
> > >some years ago i tried to do something similar (afair with owb 1.0.x)
> > >based on our plugin-spi.
> > >back then it was just possible via a plugin for resource-injection
> > >(and it was a bit "tricky").
> > >if nothing changed in the meantime, we should take the chance to add a
> > >more powerful injection-spi (to allow multiple plugins which can
> > >participate in the "injection-lifecycle").
> > >-> your approach would be one of many plugins users can add (e.g. with
> > >auto. activation...).
> > >
> > >regards,
> > >gerhard
> > >
> > >Am So., 5. Mai 2019 um 22:09 Uhr schrieb Romain Manni-Bucau
> > >:
> > >>
> > >> Good catch!
> > >>
> > >> If no objection i can push a first version like on friday I think.
> > >>
> > >> Le dim. 5 mai 2019 à 21:58, Mark Struberg  a
> > >> écrit :
> > >>
> > >>> And NO @Produces
> > >>>
> > >>> LieGrue,
> > >>> Strub
> > >>>
> > >>>> Am 05.05.2019 um 20:07 schrieb Arne Limburg <
> > >>> arne.limb...@openknowledge.de>:
> > >>>>
> > >>>> I
> > >>>> OPEN KNOWLEDGE GmbH
> > >>>> Poststraße 1, 26122 Oldenburg
> > >>>> Mobil: +49 151 - 108 22 942
> > >>>> Tel: +49 441 - 4082-154
> > >>>> Fax: +49 441 - 4082-111
> > >>>> arne.limb...@openknowledge.de
> > >>>> www.openknowledge.de
> > >>>>
> > >>>> Registergericht: Amtsgericht Oldenburg, HRB 4670
> > >>>> Geschäftsführer: Lars Röwekamp, Jens Schumann
> > >>>>
> > >>>> Nächste Konferenz:
> > >>>>
> > >>>> Jax | Mainz | 6. - 10. Mai 2019
> > >>>>
> > >>>> Nächste Akademie:
> > >>>>
> > >>>> API, Microservices & DDD Summit | München | 17. - 19. Juni 2019
> > >>>>
> > >>>> Treffen Sie uns auf weiteren Konferenzen,
> > >>>> Summits und Events:
> > >>>>
> > >>>> Zu unseren weiteren Events
> > >>>>
> > >>>>
> > >>>>
> > >>>> am fine with that. I even thought of that before, when I wanted to add
> > >>> @PersistenceContext as qualifier to implement injection of
> > EntityManager by
> > >>> myself in a pure CDI-Scenario.
> > >>>>
> > >>>> Cheers,
> > >>>> Arne
> > >>>>
> > >>>> --
> > >>>> Arne Limburg – Enterprise Architect
> > >>>>
> > >>>>
> > >>>> Am 05.05.19, 19:39 schrieb "Romain Manni-Bucau" <
> > rmannibu...@gmail.com
> > >>>> :
> > >>>>
> > >>>>   Hi guys,
> > >>>>
> > >>>>   Quarkus makes @Inject optional for MP qualifiers, can we add a flag
> > >>> to get
> > >>>>   it? I.e. injection point is defined if inject is there or there is a
> > >>>>   qualifier (even without inject)?
> > >>>>
> > >>>>   It can probably be extended to delegate too - but less common.
> > >>>>
> > >>>>   Guess it can be on by default but fine if you prefer it off too to
> > >>>>   encourage portability.
> > >>>>
> > >>>>   Wdyt?
> > >>>>
> > >>>>
> > >>>
> > >>>
> > >
> > >
> >
> >

Re: Injection point for qualified points without @inject?

[Gerhard Petracek]

hi arne,

at least with owb 1.x it didn't work.
however, >if< it would work that way (with both implementations), it's
imo more a topic for ds.

regards,
gerhard



Am Mo., 6. Mai 2019 um 14:41 Uhr schrieb Arne Limburg
:
>
> Hmm,
> thinking more of it:
> Shouldn't it be just an Extension that adds an @Inject Annotation to every 
> Field and Method parameter that has a qualifier?
>
> Cheers,
> Arne
>
> --
> Arne Limburg – Enterprise Architect
>
>
>
> OPEN KNOWLEDGE GmbH
> Poststraße 1, 26122 Oldenburg
> Mobil: +49 151 - 108 22 942
> Tel: +49 441 - 4082-154
> Fax: +49 441 - 4082-111
> arne.limb...@openknowledge.de
> www.openknowledge.de
>
> Registergericht: Amtsgericht Oldenburg, HRB 4670
> Geschäftsführer: Lars Röwekamp, Jens Schumann
>
> Nächste Konferenz:
>
> Java Forum Nord | Hannover | 24. September 2019
>
> Nächste Akademie:
>
> API, Microservices & DDD Summit | München | 17. - 19. Juni 2019
>
> Treffen Sie uns auf weiteren Konferenzen,
> Summits und Events:
>
> Zu unseren weiteren Events
>
>
>
> Am 06.05.19, 14:06 schrieb "Gerhard Petracek" :
>
> hi romain,
>
> some years ago i tried to do something similar (afair with owb 1.0.x)
> based on our plugin-spi.
> back then it was just possible via a plugin for resource-injection
> (and it was a bit "tricky").
> if nothing changed in the meantime, we should take the chance to add a
> more powerful injection-spi (to allow multiple plugins which can
> participate in the "injection-lifecycle").
> -> your approach would be one of many plugins users can add (e.g. with
> auto. activation...).
>
> regards,
> gerhard
>
> Am So., 5. Mai 2019 um 22:09 Uhr schrieb Romain Manni-Bucau
> :
> >
> > Good catch!
> >
> > If no objection i can push a first version like on friday I think.
> >
> > Le dim. 5 mai 2019 à 21:58, Mark Struberg  a
> > écrit :
> >
> > > And NO @Produces
> > >
> > > LieGrue,
> > > Strub
> > >
> > > > Am 05.05.2019 um 20:07 schrieb Arne Limburg <
> > > arne.limb...@openknowledge.de>:
> > > >
> > > > I
> > > > OPEN KNOWLEDGE GmbH
> > > > Poststraße 1, 26122 Oldenburg
> > > > Mobil: +49 151 - 108 22 942
> > > > Tel: +49 441 - 4082-154
> > > > Fax: +49 441 - 4082-111
> > > > arne.limb...@openknowledge.de
> > > > www.openknowledge.de
> > > >
> > > > Registergericht: Amtsgericht Oldenburg, HRB 4670
> > > > Geschäftsführer: Lars Röwekamp, Jens Schumann
> > > >
> > > > Nächste Konferenz:
> > > >
> > > > Jax | Mainz | 6. - 10. Mai 2019
> > > >
> > > > Nächste Akademie:
> > > >
> > > > API, Microservices & DDD Summit | München | 17. - 19. Juni 2019
> > > >
> > > > Treffen Sie uns auf weiteren Konferenzen,
> > > > Summits und Events:
> > > >
> > > > Zu unseren weiteren Events
> > > >
> > > >
> > > >
> > > > am fine with that. I even thought of that before, when I wanted to 
> add
> > > @PersistenceContext as qualifier to implement injection of 
> EntityManager by
> > > myself in a pure CDI-Scenario.
> > > >
> > > > Cheers,
> > > > Arne
> > > >
> > > > --
> > > > Arne Limburg – Enterprise Architect
> > > >
> > > >
> > > > Am 05.05.19, 19:39 schrieb "Romain Manni-Bucau" 
>  > > >:
> > > >
> > > >Hi guys,
> > > >
> > > >Quarkus makes @Inject optional for MP qualifiers, can we add a 
> flag
> > > to get
> > > >it? I.e. injection point is defined if inject is there or there 
> is a
> > > >qualifier (even without inject)?
> > > >
> > > >It can probably be extended to delegate too - but less common.
> > > >
> > > >Guess it can be on by default but fine if you prefer it off too 
> to
> > > >encourage portability.
> > > >
> > > >Wdyt?
> > > >
> > > >
> > >
> > >
>
>

Re: Injection point for qualified points without @inject?

[Gerhard Petracek]

hi romain,

some years ago i tried to do something similar (afair with owb 1.0.x)
based on our plugin-spi.
back then it was just possible via a plugin for resource-injection
(and it was a bit "tricky").
if nothing changed in the meantime, we should take the chance to add a
more powerful injection-spi (to allow multiple plugins which can
participate in the "injection-lifecycle").
-> your approach would be one of many plugins users can add (e.g. with
auto. activation...).

regards,
gerhard

Am So., 5. Mai 2019 um 22:09 Uhr schrieb Romain Manni-Bucau
:
>
> Good catch!
>
> If no objection i can push a first version like on friday I think.
>
> Le dim. 5 mai 2019 à 21:58, Mark Struberg  a
> écrit :
>
> > And NO @Produces
> >
> > LieGrue,
> > Strub
> >
> > > Am 05.05.2019 um 20:07 schrieb Arne Limburg <
> > arne.limb...@openknowledge.de>:
> > >
> > > I
> > > OPEN KNOWLEDGE GmbH
> > > Poststraße 1, 26122 Oldenburg
> > > Mobil: +49 151 - 108 22 942
> > > Tel: +49 441 - 4082-154
> > > Fax: +49 441 - 4082-111
> > > arne.limb...@openknowledge.de
> > > www.openknowledge.de
> > >
> > > Registergericht: Amtsgericht Oldenburg, HRB 4670
> > > Geschäftsführer: Lars Röwekamp, Jens Schumann
> > >
> > > Nächste Konferenz:
> > >
> > > Jax | Mainz | 6. - 10. Mai 2019
> > >
> > > Nächste Akademie:
> > >
> > > API, Microservices & DDD Summit | München | 17. - 19. Juni 2019
> > >
> > > Treffen Sie uns auf weiteren Konferenzen,
> > > Summits und Events:
> > >
> > > Zu unseren weiteren Events
> > >
> > >
> > >
> > > am fine with that. I even thought of that before, when I wanted to add
> > @PersistenceContext as qualifier to implement injection of EntityManager by
> > myself in a pure CDI-Scenario.
> > >
> > > Cheers,
> > > Arne
> > >
> > > --
> > > Arne Limburg – Enterprise Architect
> > >
> > >
> > > Am 05.05.19, 19:39 schrieb "Romain Manni-Bucau"  > >:
> > >
> > >Hi guys,
> > >
> > >Quarkus makes @Inject optional for MP qualifiers, can we add a flag
> > to get
> > >it? I.e. injection point is defined if inject is there or there is a
> > >qualifier (even without inject)?
> > >
> > >It can probably be extended to delegate too - but less common.
> > >
> > >Guess it can be on by default but fine if you prefer it off too to
> > >encourage portability.
> > >
> > >Wdyt?
> > >
> > >
> >
> >

Re: [DISCUSS] move OpenWebBeans core repo to GIT?

[Gerhard Petracek]

+1!

regards,
gerhard



Am Fr., 3. Mai 2019 um 13:31 Uhr schrieb Mark Struberg
:
>
> hi folks!
>
> Do we want to move OWB core to GIT?
>
> wdyt?
>
> I'd be +1
>
> LieGrue,
> strub
>

Re: SeContainer & Junit 5

[Gerhard Petracek]

+1

regards,
gerhard



Am Di., 16. Apr. 2019 um 17:49 Uhr schrieb Romain Manni-Bucau
:
>
> Sure
>
> @Cdi
> class MyTest {
>   @Inject Mybean bean;
>
>   @Test
>   void run() {
> //...
>   }
> }
>
> You can also select just a few beans in @Cdi to boost the deployment - by
> default it is a classpath depl.
>
>
> Le mar. 16 avr. 2019 à 17:23, Thomas Andraschko 
> a écrit :
>
> > Can you also post a usage example?
> >
> > Am Di., 16. Apr. 2019 um 09:08 Uhr schrieb Romain Manni-Bucau <
> > rmannibu...@gmail.com>:
> >
> > > Hi guys,
> > >
> > > For a project based on SeContainer I just wrote this JUnit 5 extension:
> > >
> > > https://gist.github.com/rmannibucau/f7f07969225b880c8009b0c0f2f21299
> > >
> > > Do you think it is worth contributing it?
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau  |  Blog
> > >  | Old Blog
> > >  | Github <
> > > https://github.com/rmannibucau> |
> > > LinkedIn  | Book
> > > <
> > >
> > https://www.packtpub.com/application-development/java-ee-8-high-performance
> > > >
> > >
> >

Re: [DISCUSS] move owb to Apache gitbox?

[Gerhard Petracek]

+1

regards,
gerhard



Am Sa., 29. Dez. 2018 um 17:16 Uhr schrieb Mark Struberg
:

> hi folks!
>
> Do we finally want to move to gitbox?
>
> Our Meecrowave-examples are already there:
> https://github.com/apache/openwebbeans-meecrowave-examples
>
> I recommend the following additional 2 repos:
> * openwebbeans-meecrowave
> * openwebbeans or openwebbeans-core
>
> Wdyt?
>
> LieGrue,
> strub
>

Re: [VOTE] Release Apache OpenWebBeans-2.0.8

[Gerhard Petracek]

+1

regards,
gerhard



Am Mi., 7. Nov. 2018 um 17:40 Uhr schrieb Thomas Andraschko <
andraschko.tho...@gmail.com>:

> Hi all,
>
> I'd like to call a VOTE on releasing Apache OpenWebBeans-2.0.8
>
> The following tickets got resolved:
>
> Bug
>
> [OWB-1257] - Conditional exclusion of beans in beans.xml does not honor
> system property
> [OWB-1263] - Generic observers not called correctly
> [OWB-1264] - Observers method throws NoClassDefFoundError for optional
> classes
> [OWB-1269] - TomcatSecurityService principal is not the contextual one
> out of request scope beans
>
> Improvement
>
> [OWB-1261] - Upgrade ASM to version 7
> [OWB-1265] - [perf] cache AnnotationManager#getRepeatableMethod
> [OWB-1266] - [perf] InjectionResolver cache can be activated earlier
>
> Task
>
> [OWB-1268] - Upgrade to xbean 4.12
>
> The staging repo is:
>
> https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1047
>
> The source release is in
>
> https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1047/org/apache/openwebbeans/openwebbeans/2.0.8/
>
> The sha1 of openwebbeans-2.0.8-source-release.zip is
> 49ddc4060fbce6a83b58666e5db1ae7cd56953c7
>
> The sha512 is
>
> 305f03de4690ed9855c3b40a46ca2d47e92efa7bccaf639431ef50c31bd817ed91bb2e7dee1ff3e3a0e65715e868107116fd97980215de37eda2b892973a5812
>
> The tag in SVN is
> https://svn.apache.org/repos/asf/openwebbeans/tags/openwebbeans-2.0.8/
> -r1846048
> 
>
>
> Please VOTE:
>
> [+1] go for it!
> [+0] meh, don't care
> [-1] nah, because there is a ${showstopper}
>
>
> The VOTE is open for 72h.
>

Re: going for a 2.0.7 release this weekend?

[Gerhard Petracek]

+1

regards,
gerhard



Am Fr., 24. Aug. 2018 um 14:32 Uhr schrieb Romain Manni-Bucau <
rmannibu...@gmail.com>:

> +1, all is already here for me :)
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github <
> https://github.com/rmannibucau> |
> LinkedIn  | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>
>
> Le ven. 24 août 2018 à 14:16, Mark Struberg  a
> écrit :
>
> > hi folks!
> >
> > I'd love to run a 2.0.7 release train.
> >
> > Anything missing from OWB core wich you love to get in?
> >
> > LieGrue,
> > strub
> >
>

Re: [VOTE] Release Apache Meecrowave-1.2.3

[Gerhard Petracek]

+1

regards,
gerhard



2018-07-19 12:01 GMT+02:00 Romain Manni-Bucau :

> Hi guys,
>
> Sorry for the fast release start but there are two clear blockers in 1.2.2
> so it would be awesome to get the 1.2.3 out ASAP.
>
> The diff is mainly fixing these two issues:
> 1. Ensure base is not deleted when the container stops if it was not
> created as a temp folder
> 2. Ensure bundle goal creates a runnable container (conflict between se and
> web owb modules)
>
> Staging repository is:
> https://repository.apache.org/content/repositories/
> orgapacheopenwebbeans-1044
> Source zip is at (sha1: 71d7f4d8968faa7f50ed7abeb72f4e9be14f5ac5):
> https://dist.apache.org/repos/dist/dev/openwebbeans/meecrowave/ (rev
> 28217)
>
> Please VOTE:
> [+1] Indeed
> [-1] No, you missed ${showstopper}
>
> The VOTE is open for 72h
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github  rmannibucau> |
> LinkedIn  | Book
>  ee-8-high-performance>
>

Re: [VOTE] Release Apache Meecrowave-1.2.2

[Gerhard Petracek]

+1

regards,
gerhard


2018-07-14 9:33 GMT+02:00 Mark Struberg :

> hi folks!
>
> I'd like to call a VOTE for releaseing Apache Meecrowave-1.2.2
>
> The following bugs and improvements got resolved:
>
> Bug
> • [MEECROWAVE-100] - exclude integration-test modules from
> deployment
> • [MEECROWAVE-105] - provide a bundled spec api jar
> • [MEECROWAVE-108] - NullpointerException when baking with
> Meecrowave.Builder#setDir
> • [MEECROWAVE-109] - Interceptor Spec API missing
> • [MEECROWAVE-111] - meecrowave.sh performas a kill -0 instead of
> -9 for the force quit.
> • [MEECROWAVE-113] - CLONE - MEECROWAVE_TMPDIR does not work
> properly
> • [MEECROWAVE-116] - Meecrowave jpa module can hide some jpa
> exception
> • [MEECROWAVE-121] - duplicate dependency geronimo-atinject vs
> javax.inject
> • [MEECROWAVE-123] - Update OpenJPA to 3.0.0 and JPA-2.1
>
> New Feature
> • [MEECROWAVE-107] - Upgrade to log4j 2.11.0
> • [MEECROWAVE-110] - upgrade to xbean-4.7
> • [MEECROWAVE-115] - Make valves configurable through properties
>
> Improvement
> • [MEECROWAVE-112] - upgrade OWB to 2.0.6
> • [MEECROWAVE-114] - make the tomcat session defaults configurable
> via meecrowave.properties and CLI
> • [MEECROWAVE-127] - update various tool dependencies
>
> Task
> • [MEECROWAVE-101] - Add meecrowave.bat in bundle goal
> • [MEECROWAVE-102] - bundle goal keeps meecrowave as default log
> file instead of ${name}
> • [MEECROWAVE-103] - tomcat 9.0.8
> • [MEECROWAVE-104] - Prevent Johnzon client jsonbjaxrsprovider to
> leak used with cxf client
> • [MEECROWAVE-106] - Upgrade to CXF 3.2.5
> • [MEECROWAVE-117] - upgrade xbean version to 4.9
> • [MEECROWAVE-119] - Support transitive dependencies in meecrowave
> mojo
> • [MEECROWAVE-120] - Add system properties support in run mojo
> • [MEECROWAVE-122] - Update to Johnzon 1.1.8
> • [MEECROWAVE-124] - Let's Encrypt extension
> • [MEECROWAVE-125] - Add Automatic-Module-Name in jars
> • [MEECROWAVE-126] - Upgrade JUnit 5 support to 5.3.0-M1
>
> The staging repository is:
> https://repository.apache.org/content/repositories/
> orgapacheopenwebbeans-1043/
>
> The source zip is at
> https://repository.apache.org/content/repositories/
> orgapacheopenwebbeans-1043/org/apache/meecrowave/meecrowave/1.2.2/
> sha1 is 6e55be6d7bd1dbe7911ad23541ee6c67538e36bc
>
> Please VOTE:
>
> [+1] ship it!
> [+0] meh, don't care
> [-1] nah, becasue ${showstopper}
>
> The VOTE is open for 72h
>
> txs and LieGrue,
> strub
>
>
>
>

Re: [VOTE] Apache OpenWebBeans-2.0.5

[Gerhard Petracek]

+1

regards,
gerhard



2018-04-28 22:52 GMT+02:00 Mark Struberg :

> good evening!
>
> I'd like to call a VOTE to release Apache OpenWebBeans-2.0.5.
>
> The following tickets got resolved
>
> Bug
> • [OWB-1233] - WrappedValueExpression.equals(Object arg0) always
> false if arg0 is an instance of WrappedValueExpression
> • [OWB-1235] - ConversationScope destroyed upon session
> serialization/deserialization
> • [OWB-1241] - Bean cache ignores qualifier model defined through
> an AnnotatedType
>
> New Feature
> • [OWB-1242] - Add a configuration option to not proxy Principal
>
> Improvement
> • [OWB-1232] - replace warning about interceptors
> • [OWB-1238] - Our VersionVisitor shouldn't visit code
> • [OWB-1243] - improve event performance
>
> Task
> • [OWB-1240] - Non-static inner classes should not get picked up
> as CDI Beans
>
> Dependency upgrade
> • [OWB-1236] - Update to XBean Asm 6 Shaded 4.7
> • [OWB-1237] - upgrade to xbean-4.8
>
>
> The staging repo is
> https://repository.apache.org/content/repositories/
> orgapacheopenwebbeans-1041/
>
> The source distribution can be found here:
> https://repository.apache.org/content/repositories/
> orgapacheopenwebbeans-1041/org/apache/openwebbeans/openwebbeans/2.0.5/
>
> The sha1 is 7fed2fe13879270ce17ee711232bdca55b08d83b
>
> The tag is https://svn.apache.org/repos/asf/openwebbeans/tags/
> openwebbeans-2.0.5/
> -r 1830447
>
> Please VOTE
>
> [+1] yeah, let's ship it!
> [+0] meh, don't care
> [-1] stop there's a ${showstopper}
>
> The VOTE is open for 72h
>
> txs and LieGrue,
> strub
>
>
>

Re: [VOTE] Release Apache Meecrowave-1.2.1

[Gerhard Petracek]

i've upgraded [1] to v1.2.1 and all tests look fine.
-> +1

regards,
gerhard

[1] https://github.com/CDIatWork/IdeaForkMicro



2018-02-26 22:40 GMT+01:00 Mark Struberg :

> Hi folks!
>
> This is a vote for Microwave-1.2.1
>
> The following bugs and tasks got resolved:
>
> Bug
>
> • [MEECROWAVE-65] - log isn't visible during shutdown
> • [MEECROWAVE-87] - Enhance meecrowave to get adavnced ssl
> properties from meecrowave.properties
> • [MEECROWAVE-90] - ClassCastException with JUnit 5 integration
> • [MEECROWAVE-93] - bad system property naming in meecrowave.sh
> • [MEECROWAVE-94] - Cli forces a double close of Meecrowave which
> is not supported yet
> • [MEECROWAVE-95] - Maven properties meecrowave.scanning-include
> and exclude are mixed up
> • [MEECROWAVE-96] - add a way to force package scanning without
> excluding every other package
> • [MEECROWAVE-99] - update johnzon to 1.1.7
> Improvement
>
> • [MEECROWAVE-89] - Ensure org.apache.meecrowave.runner.Cli is
> also AutoCloseable
> Task
>
> • [MEECROWAVE-88] - Upgrade to DBCP 2.2.0
> • [MEECROWAVE-92] - Upgrade to tomcat 9.0.5
> • [MEECROWAVE-97] - Upgrade to CXF 3.2.2
> • [MEECROWAVE-98] - upgrade OWB to 2.0.4
>
>
> The staging repo can be found at:
>
> https://repository.apache.org/content/repositories/orgapache
> openwebbeans-1039/
>
> The source release is at
>  https://repository.apache.org/service/local/
> repositories/orgapacheopenwebbeans-1039/content/org/apache/
> meecrowave/meecrowave/1.2.1/meecrowave-1.2.1-source-release.zip
> the sha1 is 4fec229ac405be626947e0a933adde1df3b0fc72
>
>
> Please VOTE:
>
> [+1] yea, ship it!
> [+0] meh, don't care
> [-1] no there is a ${showstopper}
>
> The VOTE is open for 72h.
>
>
> txs and LieGrue,
> strub
>
>
>

Re: [VOTE] Release Apache Meecrowave-1.2.0

[Gerhard Petracek]

+1
(i've tested it with ideafork-micro which is used in the upcoming chapter
of [1]).

regards,
gerhard

[1] http://cdiatwork.irian.at



2017-12-20 17:57 GMT+01:00 Mark Struberg :

> Hi folks!
>
> I've also run the steps to release Meecrowave-1.2.0
>
> The following bugs and tasks got resolved:
>
> Bug
>
> • [MEECROWAVE-64] - OWBTomcatWebScannerService blows up with a NPE
> if used in Unit Tests
> • [MEECROWAVE-68] - JUL/Log4j integration not respected if not set
> on the JVM
> • [MEECROWAVE-71] - MonoMeecrowave.Runner doesn't set up the
> Request Context
> • [MEECROWAVE-74] - exclude log4j-api meta-inf/versions from shade
> • [MEECROWAVE-75] - MeecrowaveBus unwrapping doesn't work for
> interfaces
> • [MEECROWAVE-76] - meecrowave:run ignores meecrowave.properties
> • [MEECROWAVE-78] - Maven plugin activates cdi conversation by
> default
> • [MEECROWAVE-79] - @WebListener/@WebServlet/@WebFilter ignored
> from jar dependencies
> • [MEECROWAVE-81] - upgrade to Johnzon-1.1.5
> • [MEECROWAVE-82] - meecrowave-maven-plugin fails with
> bean-validation
> • [MEECROWAVE-83] - wrong property for tomcatWrapLoader in
> meecrowave mojo
> • [MEECROWAVE-85] - MEECROWAVE_TMPDIR does not work properly
> • [MEECROWAVE-86] - Typo in TomcatAutoInitializer.java causes jsp
> pages not picked up by meecrowave.
> Improvement
>
> • [MEECROWAVE-77] - Wrap MeecrowaveRule runs in a temporary
> URLClassLoader to force a unique BeanManager
> New Feature
>
> • [MEECROWAVE-80] - docBase should be configurable from meecrowave
> rule
> Task
>
> • [MEECROWAVE-63] - upgrade to Johnzon-1.1.4 (actually it was
> 1.1.5)
> • [MEECROWAVE-66] - Upgrade to CXF 3.2.1
> • [MEECROWAVE-67] - Upgrade to tomcat 9.0.2
> • [MEECROWAVE-69] - Update meecrowave-test junit5 integration to
> release version
> • [MEECROWAVE-70] - Upgrade to Johnzon 1.1.4
> • [MEECROWAVE-72] - update log4j to 2.9.1
> • [MEECROWAVE-73] - jcdi_2.0-1.0.1 creates Exception with OWB-2.0.2
> • [MEECROWAVE-84] - upgrade to log4j 2.10
>
>
> The staging repo is
> https://repository.apache.org/content/repositories/
> orgapacheopenwebbeans-1037/
>
>
> The source release zip is in
> https://repository.apache.org/content/repositories/
> orgapacheopenwebbeans-1037/org/apache/meecrowave/meecrowave/1.2.0/
> sha1 is 71e556533510ff30550c4ccd39e5df568344360b
>
> Please VOTE:
>
> [+1] yea, let's ship it!
> [+0] meh, don't care
> [-1] stop, there is a ${showstopper}
>
> The VOTE is open for 72h
>
>
> txs and LieGrue,
> strub
>
>
>
>
>

Re: configureProducerMethodSpecialization looks pretty much overcomplicated

[Gerhard Petracek]

+1

regards,
gerhard



2017-12-19 9:01 GMT+01:00 Mark Struberg :

> Hi folks!
>
> Currently refactoring the WebBeansUtil#configureProducerMethodSpecial
> izations.
>
> This method is not easy to follow and could be seriously simplified.
>
> I already moved all the condition checks to a common place, unifying the
> checks from ProducerMethodBuilder and the ondes in WebBeansUtil.
>
> The next step is to simplify the condition checks itself.
> It looks that the original approach have been a red/black tree like
> algorithm to avoid n^2.
> But by always creating a fresh sorted list of all producer method beans
> inside this loop, we got the issue anyway.
>
> My current try is to sort all the beans just once and then disable all the
> producer methods who got overwritten.
> This means that the sorting has to be reversed, with the subclasses first,
> then the parent classes later.
>
> It's quite some change, but it gladly only affects specialized producer
> methods.
> Still we should critically review the refactoring.
>
> txs and LieGrue,
> strub
>
>

Re: [VOTE] Release Apache OpenWebBeans-2.0.3

[Gerhard Petracek]

+1

regards,
gerhard



2017-12-20 16:01 GMT+01:00 Mark Struberg :

> Hi folks!
>
> I did run all steps to release OWB-2.0.3.
>
> We fixed the following bugs and improvements
>
> Bug
>
> [OWB-1171] - @Priority and @Alternative as sterotype
> [OWB-1219] - Prioritized custom Bean gets ignored if ManagedBean with
> @Priority exists
> [OWB-1220] - URL-encoding issue in AbstractMetaDataDiscovery
> [OWB-1222] - subclass proxy fails with Java9
>
> Improvement
>
> [OWB-1218] - improve toString of producer beans to also log owner class
>
> Task
>
> [OWB-1221] - Upgrade to asm 6
>
> With ASM6 we are now fully able to run on Java9. We do not yet support all
> Java9 features like jmods and jigsaw though.
>
>
> Here is the staging repo
> https://repository.apache.org/content/repositories/
> orgapacheopenwebbeans-1034/
>
> And the source zip
> https://repository.apache.org/content/repositories/
> orgapacheopenwebbeans-1034/org/apache/openwebbeans/openwebbeans/2.0.3/
> The sha1 is c59ed556a30405ca6f6484456fd9b6d264ca7533
>
>
> Please VOTE
>
> [+1] yea, ship it
> [+0] meh, don't care
> [-1] nope stop, because ${showstopper}
>
> The VOTE is open for 72h.
>
> txs and LieGrue,
> strub
>
>

[jira] [Created] (MEECROWAVE-82) meecrowave-maven-plugin fails with bean-validation

[Gerhard Petracek (JIRA)]

Gerhard Petracek created MEECROWAVE-82:
--

 Summary: meecrowave-maven-plugin fails with bean-validation
 Key: MEECROWAVE-82
 URL: https://issues.apache.org/jira/browse/MEECROWAVE-82
 Project: Meecrowave
  Issue Type: Bug
Affects Versions: 1.1.0
Reporter: Gerhard Petracek
Assignee: Romain Manni-Bucau
 Fix For: 1.2.0


if meecrowave gets started via the java-api, there isn't an issue.
once mvn meecrowave:run gets used, the startup fails once bean-validation is on 
the classpath (independent of the version and implementation)

"workaround":
{code}
false
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [meecrowave] disable cdiconversation by default?

[Gerhard Petracek]

+1

regards,
gerhard



2017-11-09 15:36 GMT+01:00 Mark Struberg :

> CDI conversations are hardly usable anyway ;)
>
> LieGrue,
> strub
>
> > Am 09.11.2017 um 09:34 schrieb Romain Manni-Bucau  >:
> >
> > Hi guys,
> >
> > anyone of you uses conversation scope with meecrowave? Having the
> > support of conversation by default creates a session per request tdue
> > to our filter which is pointless in all the apps I did using
> > meecrowave. We can of course switch it off through the CLI/config but
> > wonder if we shouldnt change our default (cdiConversation = false)
> >
> > wdyt?
> >
> > Romain Manni-Bucau
> > @rmannibucau |  Blog | Old Blog | Github | LinkedIn
>
>

Re: Will run the mw 1.2.0 release tonight

[Gerhard Petracek]

+1

regards,
gerhard



2017-10-05 11:38 GMT+02:00 Mark Struberg :

> And also will update to johnzon-1.1.4 before that.
> CXF is already updated to 3.2.0 which will require people to update CXF
> and JAX-RS api, so I'd prefer calling it 1.2.0.
>
> Any objections?
>
> LieGrue,
> strub

Re: [VOTE] Release Apache Meecrowave-1.1.0

[Gerhard Petracek]

+1

regards,
gerhard



2017-09-01 23:35 GMT+02:00 Mark Struberg :

> Hi!
>
> Apache Meecrowave is a very small (9MB) EE based server.
> It can run embeded, as single-jar app, or as a installable zip via
> $> mvn meecrowave:bundle
> Docs are at http://openwebbeans.apache.org/meecrowave/
>
> We improved quite a few things in Meecrowave, so it's definitely time for
> a release!
>
> Bug
>
> • [MEECROWAVE-54] - Upgrade to tomcat 9.0.0.M26
> • [MEECROWAVE-57] - Export MEECROWAVE_BASE in meecrowave.sh
> • [MEECROWAVE-58] - running meecrowave:bundle in a nested maven
> project does not find conf files
> • [MEECROWAVE-60] - do a more graceful shutdown in meecrowave.sh
> • [MEECROWAVE-61] - keystoreFile wrongly set in connector
> configuration when configured in the CLI
> • [MEECROWAVE-62] - shutdown creates a NPE when trying to delete
> the base directory
> Improvement
>
> • [MEECROWAVE-45] - support for owb2
> New Feature
>
> • [MEECROWAVE-53] - basic start/stop listening events
> Task
>
> • [MEECROWAVE-48] - OpenWebBeans 2 upgrade and CDI SE support
> • [MEECROWAVE-55] - Upgrade to Johnzon 1.1.2
> • [MEECROWAVE-56] - Upgrade Commons JCS to 2.2 for Oauth2 module
> • [MEECROWAVE-59] - update log4j2 to 2.9.0
>
> With the update to OWB-2.0.1 we are now all-parts EE8 btw!
>
> The staging repo is
> https://repository.apache.org/content/repositories/
> orgapacheopenwebbeans-1032/
>
> The source dist can be found under
> https://repository.apache.org/content/repositories/
> orgapacheopenwebbeans-1032/org/apache/meecrowave/meecrowave/1.1.0/
>
> The tag is in svn:
> https://svn.apache.org/repos/asf/openwebbeans/meecrowave/
> tags/meecrowave-1.1.0/
>
>
> Please VOTE:
>
> +1: yeah, ship it!
> +0 meh, don't care
> -1 nope because ${reason}
>
> The VOTE is open for 72h.
>
> txs and LieGrue,
> strub
>
>

Re: [VOTE] Release Apache OpenWebBeans-2.0.1

[Gerhard Petracek]

+1

regards,
gerhard



2017-08-29 11:16 GMT+02:00 Mark Struberg :

> Hi folks!
>
> I did run the necessary steps to ship OWB-2.0.1 from trunk, which is our
> CDI-2.0 implementation.
> We improved the SE support (hope to finish it soon and ship all in 2.0.2)
> and a few Instance and Event fixes.
>
> This build passes the standalone CDI TCK and we already fixed a few EE
> integration bugs as well while integrating OWB in the upcoming TomEE8.
>
> The following bugs and enhancements got fixed:
>
> Bug
> • [OWB-1199] - CDISeScannerService.autoScanning should be true by
> default
> • [OWB-1203] - GProcessSyntheticBean not handled correctly for
> extensions leading to incorrect ProcessBean behavior
> • [OWB-1204] - Interceptor and Decorator ignored in annotated mode
> if not decorated with @Dependent
> • [OWB-1205] - We should not fire ProcessInjectionPoint for CDI
> Extension Observers
> • [OWB-1207] - Inconsistent behavior of the instance behind
> CDI.current()
> • [OWB-1209] - Custom bean with isAlternative()=true should not be
> automatically enabled
> • [OWB-1210] - Providing an own alternative implementation of
> Provider might disable some Instance resolving
> • [OWB-1211] - OWB is not firing BeforeDestroyed on contexts
> • [OWB-1213] - producer of URI or other classes with private ct
> blow up with a NPE
> Task
> • [OWB-1086] - initial setup for cdi-2.0
>
>
> The staging repo can be found here:
>
> https://repository.apache.org/content/repositories/
> orgapacheopenwebbeans-1031/
>
> The source release is under
> https://repository.apache.org/content/repositories/
> orgapacheopenwebbeans-1031/org/apache/openwebbeans/openwebbeans/2.0.1/
>
>
> Please VOTE
>
> [+1] go for it!
> [+0] meh, don't care
> [-1] stop because there is a ${showstopper}
>
> The VOTE is open for 72h
>
> txs and LieGrue,
> strub
>
>
>
>

Re: do a 2.0.1 release?

[Gerhard Petracek]

+1

regards,
gerhard



2017-07-30 13:36 GMT+02:00 Mark Struberg :

> Well, I was thinking about a OWB-2.0.1 release.
> And of course then do a MW-2.0.0 or MW-1.1.0 (not sure anymore on what we
> settled and which is better for MW).
>
> LieGrue,
> strub
>
> > Am 30.07.2017 um 12:10 schrieb Romain Manni-Bucau  >:
> >
> > Hi Mark,
> >
> > I would include the coming johnzon release and maybe do a 2.0.0 before
> the
> > 2.0.1 ;)
> >
> > But overall +1 to release
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau  |  Blog
> >  | Old Blog
> >  | Github  rmannibucau> |
> > LinkedIn  | JavaEE Factory
> > 
> >
> > 2017-07-30 10:47 GMT+02:00 Mark Struberg :
> >
> >> Hi folks!
> >>
> >> We've fixed a few important bugs in trunk. Should we do a 2.0.1 release?
> >> Could start it in the afternoon.
> >>
> >> LieGrue,
> >> strub
> >>
>
>

Re: VOTE Release Apache Meecrowave-1.0.0

[Gerhard Petracek]

+1

regards,
gerhard



2017-07-08 0:43 GMT+02:00 Mark Struberg :

> Hi folks!
>
> And finally Meecrowave-1.0.0!
> This is a maintenance version for the EE7 compatible version.
> It's actually the previous 0.3.2 work. We just moved to 1.0.0 to indicate
> that it's production ready.
>
> The following tickets have been resolved since 0.3.1:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12320731=12340988
>
> Bug
>
> • [MEECROWAVE-29] - tomcat 9.0.0.M21 upgrade
> • [MEECROWAVE-34] - meecrowave pidfile option fails with NPE
> • [MEECROWAVE-44] - meecrowave.sh is broken
> • [MEECROWAVE-49] - Returning a binary leads to nullpointers
> • [MEECROWAVE-50] - meecrowave-maven-plugin is not portable
> • [MEECROWAVE-51] - Upgrade dependency versions
> Improvement
>
> • [MEECROWAVE-35] - support application/*+json out of the box
> • [MEECROWAVE-36] - set default max string length to 64x1024
> • [MEECROWAVE-37] - @Context on a field in CDI proxies is broken
> • [MEECROWAVE-38] - drop not needed java 9 workarounds
> • [MEECROWAVE-42] - allow to auto package meecrowave in
> meecrowave:bundle goal
> New Feature
>
> • [MEECROWAVE-30] - Make it easier to reuse Cli
> • [MEECROWAVE-31] - Auto reloading backbone
> • [MEECROWAVE-40] - basic jaxws support if cxf-rt-frontend-jaxws
> is present in meecrowave classloader
> • [MEECROWAVE-41] - make meecrowave:bundle pick up content from
> src/main/meecrowave/conf/*
> • [MEECROWAVE-43] - Introduce @WsMapping annotation to define
> WebService endpoint mapping
> Task
>
> • [MEECROWAVE-32] - upgrade log4j2 to 2.8.2
> • [MEECROWAVE-33] - upgrade johnzon to 1.1.1
> • [MEECROWAVE-46] - Upgrade to Tomcat 9.0.0.M22
> • [MEECROWAVE-47] - CXF 3.1.12 upgrade
> • [MEECROWAVE-52] - Upgrade to OWB-1.7.4
>
>
> Here is the staging repo
> https://repository.apache.org/content/repositories/
> orgapacheopenwebbeans-1029/
>
> And here is the source release:
> https://repository.apache.org/content/repositories/
> orgapacheopenwebbeans-1029/org/apache/meecrowave/meecrowave/1.0.0/
>
>
> Please VOTE:
>
> [+1] yea, let's ship it!
> [+0] meeeh, don't care
> [-1] stop, I found a ${showstopper}
>
> The VOTE is open for 72h
>
> txs and LieGrue,
> strub

Re: [VOTE] Release Apache OpenWebBeans-1.7.4

[Gerhard Petracek]

+1

regards,
gerhard


2017-07-08 0:05 GMT+02:00 Mark Struberg :

> Dear lords and ladies!
>
> It's my pleasure to call a VOTE on releasing Apache OpenWebBeans-1.7.4.
> This is a maintenance release of our CDI-1.2 branch and a drop in
> replacement for OWB-1.7.3
>
> The following bugs got fixed:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12310844=12340364
>
> Bug
>
> • [OWB-1194] - @Interceptors (EJB style) + @AroundConstruct not
> fully supported
> • [OWB-1196] - Signed classes can't be proxied:
> java.lang.SecurityException: class "com.Foo$$OwbNormalScopeProxy0"'s
> signer information does not match signer information of other classes in
> the same package
> Improvement
>
> • [OWB-1180] - Use getDefinedPackage instead of getPackage if
> available (java 9)
> • [OWB-1181] - fallback on unsafe when defineClass is not
> accessible from ClassLoader
>
>
> Here is the staging repo:
>
> https://repository.apache.org/content/repositories/
> orgapacheopenwebbeans-1028/
>
>
> And here is the source release:
> https://repository.apache.org/content/repositories/
> orgapacheopenwebbeans-1028/org/apache/openwebbeans/openwebbeans/1.7.4/
>
> The tag in our repo is http://svn.apache.org/viewvc?rev=1801219=rev
>
> Please VOTE:
>
> [+1] yea, let's ship it!
> [+0] meeeh, don't care
> [-1] stop, I found a ${showstopper}
>
> The VOTE is open for 72h
>
> txs and LieGrue,
> strub

Re: [DISCUSS] time to release Meecrowave-1.0.0 from the maintenance branch?

[Gerhard Petracek]

+1

regards,
gerhard



2017-07-06 12:00 GMT+02:00 Mark Struberg <strub...@yahoo.de.invalid>:

> I think we should release OWB-1.7.4 first (because of the proxy bug with
> handling signed jars) and then ship MW-1.0.0.
>
> Wdyt?
>
> LieGrue,
> strub
>
>
> > Am 04.07.2017 um 15:32 schrieb Gerhard Petracek <gpetra...@apache.org>:
> >
> > fyi @MEECROWAVE-50:
> > it works with the latest snapshot
> >
> > regards,
> > gerhard
> >
> >
> >
> > 2017-07-04 11:34 GMT+02:00 Gerhard Petracek <gpetra...@apache.org>:
> >
> >> hi romain,
> >>
> >> it should be possible to reproduce it with any demo, however, you could
> >> use e.g. [1].
> >> (it uses v0.3.1, but also v0.3.2-SNAPSHOT only works on linux.)
> >> maybe it's something simple (i haven't checked the details so far), but
> >> there shouldn't be a different behavior across platforms...
> >>
> >> regards,
> >> gerhard
> >>
> >> [1] https://github.com/os890/meecrowave_template_jax-rs_cdi_jpa
> >>
> >>
> >>
> >> 2017-07-04 11:09 GMT+02:00 Romain Manni-Bucau <rmannibu...@gmail.com>:
> >>
> >>> @Gerhard: have the simple-demo somewhere on github? will try to
> resetup my
> >>> win box in the week
> >>>
> >>>
> >>> 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>
> >>>
> >>> 2017-07-04 11:08 GMT+02:00 Gerhard Petracek <gpetra...@apache.org>:
> >>>
> >>>> imo MEECROWAVE-50 needs to be part of v1 as well.
> >>>> -> +1 for a release, but not for v1 (without MEECROWAVE-50).
> >>>>
> >>>> regards,
> >>>> gerhard
> >>>>
> >>>>
> >>>>
> >>>> 2017-07-03 16:21 GMT+02:00 Romain Manni-Bucau <rmannibu...@gmail.com
> >:
> >>>>
> >>>>> Yes and no (until you hit it I guess).
> >>>>> https://issues.apache.org/jira/browse/OWB-1194 would be nice to
> >>> include
> >>>> in
> >>>>> since it starts to be used by users and libraries.
> >>>>>
> >>>>>
> >>>>> 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>
> >>>>>
> >>>>> 2017-07-03 16:19 GMT+02:00 Mark Struberg <strub...@yahoo.de.invalid
> >:
> >>>>>
> >>>>>> 1.7.4 is not yet released. Do we need it?
> >>>>>>
> >>>>>> LieGrue,
> >>>>>> strub
> >>>>>>
> >>>>>>
> >>>>>>> Am 03.07.2017 um 15:57 schrieb Romain Manni-Bucau <
> >>>>> rmannibu...@gmail.com
> >>>>>>> :
> >>>>>>>
> >>>>>>> Think we may want to upgrade to owb 1.7.4 before, otherwise +1
> >>>>>>>
> >>>>>>>
> >>>>>>> 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>
> >>>>>>>
> >>>>>>> 2017-07-03 15:56 GMT+02:00 Mark Struberg
> >>> <strub...@yahoo.de.invalid
> >>>>> :
> >>>>>>>
> >>>>>>>> Hi folks!
> >>>>>>>>
> >>>>>>>> As we figured our strategy I think it would be great to ship a
> >>> new
> >>>>>>>> Meecrowave release.
> >>>>>>>> I'll go through the tickets and see what is missing, but afair
> >>> not
> >>>>> much
> >>>>>> is
> >>>>>>>> open.
> >>>>>>>>
> >>>>>>>> LieGrue,
> >>>>>>>> strub
> >>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >>
>
>

Re: [DISCUSS] time to release Meecrowave-1.0.0 from the maintenance branch?

[Gerhard Petracek]

fyi @MEECROWAVE-50:
it works with the latest snapshot

regards,
gerhard



2017-07-04 11:34 GMT+02:00 Gerhard Petracek <gpetra...@apache.org>:

> hi romain,
>
> it should be possible to reproduce it with any demo, however, you could
> use e.g. [1].
> (it uses v0.3.1, but also v0.3.2-SNAPSHOT only works on linux.)
> maybe it's something simple (i haven't checked the details so far), but
> there shouldn't be a different behavior across platforms...
>
> regards,
> gerhard
>
> [1] https://github.com/os890/meecrowave_template_jax-rs_cdi_jpa
>
>
>
> 2017-07-04 11:09 GMT+02:00 Romain Manni-Bucau <rmannibu...@gmail.com>:
>
>> @Gerhard: have the simple-demo somewhere on github? will try to resetup my
>> win box in the week
>>
>>
>> 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>
>>
>> 2017-07-04 11:08 GMT+02:00 Gerhard Petracek <gpetra...@apache.org>:
>>
>> > imo MEECROWAVE-50 needs to be part of v1 as well.
>> > -> +1 for a release, but not for v1 (without MEECROWAVE-50).
>> >
>> > regards,
>> > gerhard
>> >
>> >
>> >
>> > 2017-07-03 16:21 GMT+02:00 Romain Manni-Bucau <rmannibu...@gmail.com>:
>> >
>> > > Yes and no (until you hit it I guess).
>> > > https://issues.apache.org/jira/browse/OWB-1194 would be nice to
>> include
>> > in
>> > > since it starts to be used by users and libraries.
>> > >
>> > >
>> > > 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>
>> > >
>> > > 2017-07-03 16:19 GMT+02:00 Mark Struberg <strub...@yahoo.de.invalid>:
>> > >
>> > > > 1.7.4 is not yet released. Do we need it?
>> > > >
>> > > > LieGrue,
>> > > > strub
>> > > >
>> > > >
>> > > > > Am 03.07.2017 um 15:57 schrieb Romain Manni-Bucau <
>> > > rmannibu...@gmail.com
>> > > > >:
>> > > > >
>> > > > > Think we may want to upgrade to owb 1.7.4 before, otherwise +1
>> > > > >
>> > > > >
>> > > > > 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>
>> > > > >
>> > > > > 2017-07-03 15:56 GMT+02:00 Mark Struberg
>> <strub...@yahoo.de.invalid
>> > >:
>> > > > >
>> > > > >> Hi folks!
>> > > > >>
>> > > > >> As we figured our strategy I think it would be great to ship a
>> new
>> > > > >> Meecrowave release.
>> > > > >> I'll go through the tickets and see what is missing, but afair
>> not
>> > > much
>> > > > is
>> > > > >> open.
>> > > > >>
>> > > > >> LieGrue,
>> > > > >> strub
>> > > > >>
>> > > > >>
>> > > >
>> > > >
>> > >
>> >
>>
>
>

[jira] [Updated] (MEECROWAVE-50) meecrowave-maven-plugin is not portable

[Gerhard Petracek (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MEECROWAVE-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gerhard Petracek updated MEECROWAVE-50:
---
Affects Version/s: (was: 1.0.0)
   0.3.1
Fix Version/s: 1.0.0

> meecrowave-maven-plugin is not portable
> ---
>
> Key: MEECROWAVE-50
> URL: https://issues.apache.org/jira/browse/MEECROWAVE-50
> Project: Meecrowave
>  Issue Type: Bug
>Affects Versions: 0.3.1
>    Reporter: Gerhard Petracek
>Assignee: Mark Struberg
> Fix For: 1.0.0
>
>
> the meecrowave-maven-plugin as well as meecrowave-runner fail on windows with 
> jdk8 (with a simple demo-setup). the same works on linux without issues.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (MEECROWAVE-50) meecrowave-maven-plugin is not portable

[Gerhard Petracek (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MEECROWAVE-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gerhard Petracek resolved MEECROWAVE-50.

Resolution: Fixed

it works with the latest snapshot

> meecrowave-maven-plugin is not portable
> ---
>
> Key: MEECROWAVE-50
> URL: https://issues.apache.org/jira/browse/MEECROWAVE-50
> Project: Meecrowave
>  Issue Type: Bug
>Affects Versions: 0.3.1
>    Reporter: Gerhard Petracek
>Assignee: Mark Struberg
> Fix For: 1.0.0
>
>
> the meecrowave-maven-plugin as well as meecrowave-runner fail on windows with 
> jdk8 (with a simple demo-setup). the same works on linux without issues.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [DISCUSS] time to release Meecrowave-1.0.0 from the maintenance branch?

[Gerhard Petracek]

hi romain,

it should be possible to reproduce it with any demo, however, you could use
e.g. [1].
(it uses v0.3.1, but also v0.3.2-SNAPSHOT only works on linux.)
maybe it's something simple (i haven't checked the details so far), but
there shouldn't be a different behavior across platforms...

regards,
gerhard

[1] https://github.com/os890/meecrowave_template_jax-rs_cdi_jpa



2017-07-04 11:09 GMT+02:00 Romain Manni-Bucau <rmannibu...@gmail.com>:

> @Gerhard: have the simple-demo somewhere on github? will try to resetup my
> win box in the week
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://blog-rmannibucau.rhcloud.com> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibuca
> u> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> <https://javaeefactory-rmannibucau.rhcloud.com>
>
> 2017-07-04 11:08 GMT+02:00 Gerhard Petracek <gpetra...@apache.org>:
>
> > imo MEECROWAVE-50 needs to be part of v1 as well.
> > -> +1 for a release, but not for v1 (without MEECROWAVE-50).
> >
> > regards,
> > gerhard
> >
> >
> >
> > 2017-07-03 16:21 GMT+02:00 Romain Manni-Bucau <rmannibu...@gmail.com>:
> >
> > > Yes and no (until you hit it I guess).
> > > https://issues.apache.org/jira/browse/OWB-1194 would be nice to
> include
> > in
> > > since it starts to be used by users and libraries.
> > >
> > >
> > > 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>
> > >
> > > 2017-07-03 16:19 GMT+02:00 Mark Struberg <strub...@yahoo.de.invalid>:
> > >
> > > > 1.7.4 is not yet released. Do we need it?
> > > >
> > > > LieGrue,
> > > > strub
> > > >
> > > >
> > > > > Am 03.07.2017 um 15:57 schrieb Romain Manni-Bucau <
> > > rmannibu...@gmail.com
> > > > >:
> > > > >
> > > > > Think we may want to upgrade to owb 1.7.4 before, otherwise +1
> > > > >
> > > > >
> > > > > 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>
> > > > >
> > > > > 2017-07-03 15:56 GMT+02:00 Mark Struberg <strub...@yahoo.de.invalid
> > >:
> > > > >
> > > > >> Hi folks!
> > > > >>
> > > > >> As we figured our strategy I think it would be great to ship a new
> > > > >> Meecrowave release.
> > > > >> I'll go through the tickets and see what is missing, but afair not
> > > much
> > > > is
> > > > >> open.
> > > > >>
> > > > >> LieGrue,
> > > > >> strub
> > > > >>
> > > > >>
> > > >
> > > >
> > >
> >
>

Re: [DISCUSS] time to release Meecrowave-1.0.0 from the maintenance branch?

[Gerhard Petracek]

imo MEECROWAVE-50 needs to be part of v1 as well.
-> +1 for a release, but not for v1 (without MEECROWAVE-50).

regards,
gerhard



2017-07-03 16:21 GMT+02:00 Romain Manni-Bucau :

> Yes and no (until you hit it I guess).
> https://issues.apache.org/jira/browse/OWB-1194 would be nice to include in
> since it starts to be used by users and libraries.
>
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github  rmannibucau> |
> LinkedIn  | JavaEE Factory
> 
>
> 2017-07-03 16:19 GMT+02:00 Mark Struberg :
>
> > 1.7.4 is not yet released. Do we need it?
> >
> > LieGrue,
> > strub
> >
> >
> > > Am 03.07.2017 um 15:57 schrieb Romain Manni-Bucau <
> rmannibu...@gmail.com
> > >:
> > >
> > > Think we may want to upgrade to owb 1.7.4 before, otherwise +1
> > >
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau  |  Blog
> > >  | Old Blog
> > >  | Github  > rmannibucau> |
> > > LinkedIn  | JavaEE Factory
> > > 
> > >
> > > 2017-07-03 15:56 GMT+02:00 Mark Struberg :
> > >
> > >> Hi folks!
> > >>
> > >> As we figured our strategy I think it would be great to ship a new
> > >> Meecrowave release.
> > >> I'll go through the tickets and see what is missing, but afair not
> much
> > is
> > >> open.
> > >>
> > >> LieGrue,
> > >> strub
> > >>
> > >>
> >
> >
>

Re: [discuss] meecrowave dev/prod setup

[Gerhard Petracek]

hi romain,

yes - keeping the starter-class in the test-source directory used to be my
workaround for tomee (which works for meecrowave as well).
however, i'm trying to get rid of that workaround. (sorry for skipping that
part in my initial message).

regards,
gerhard



2017-07-02 23:19 GMT+02:00 Romain Manni-Bucau <rmannibu...@gmail.com>:

> Hi Gerhard
>
> What is the proposal? I use it for demos with either maven jar exclude or
> just putting it in test classes instead of main and it work fine. Also
> maven plugin or a plain maven exec shouldnt require any custom main so not
> sure which blocker you hit. Can you detail it please?
>
> Le 2 juil. 2017 22:56, "Gerhard Petracek" <gpetra...@apache.org> a écrit :
>
> > hi @ all,
> >
> > i'm currently using meecrowave for the upcoming chapter of cdi@work.
> > i'm quite happy with it, however, imo we should improve one area.
> > i would like to show a starter similar to [1]. that's a fast alternative
> to
> > the maven-plugin (as well as the runner-jar).
> >
> > however, using this approach to start the application during development
> > results in a web-archive (for prod.) which contains meecrowave as a lib.
> > the current workaround is to use different maven profiles (one defines
> > meecrowave as a provided dependency and the other one as a compile
> > dependency).
> > imo we need something more useful to allow both in parallel (such a
> > starter-class as well as the maven-plugin or runner-jar) without using
> > workarounds like different maven profiles.
> >
> > regards,
> > gerhard
> >
> > [1]
> > https://github.com/os890/meecrowave_template_jax-rs_
> > cdi_jpa/blob/master/src/dev-starter/java/org/os890/
> > meecrowave/dev/DevStarter.java
> >
>

[discuss] meecrowave dev/prod setup

[Gerhard Petracek]

hi @ all,

i'm currently using meecrowave for the upcoming chapter of cdi@work.
i'm quite happy with it, however, imo we should improve one area.
i would like to show a starter similar to [1]. that's a fast alternative to
the maven-plugin (as well as the runner-jar).

however, using this approach to start the application during development
results in a web-archive (for prod.) which contains meecrowave as a lib.
the current workaround is to use different maven profiles (one defines
meecrowave as a provided dependency and the other one as a compile
dependency).
imo we need something more useful to allow both in parallel (such a
starter-class as well as the maven-plugin or runner-jar) without using
workarounds like different maven profiles.

regards,
gerhard

[1]
https://github.com/os890/meecrowave_template_jax-rs_cdi_jpa/blob/master/src/dev-starter/java/org/os890/meecrowave/dev/DevStarter.java

[jira] [Created] (MEECROWAVE-50) meecrowave-maven-plugin is not portable

[Gerhard Petracek (JIRA)]

Gerhard Petracek created MEECROWAVE-50:
--

 Summary: meecrowave-maven-plugin is not portable
 Key: MEECROWAVE-50
 URL: https://issues.apache.org/jira/browse/MEECROWAVE-50
 Project: Meecrowave
  Issue Type: Bug
Affects Versions: 0.3.2
Reporter: Gerhard Petracek
Assignee: Mark Struberg


the meecrowave-maven-plugin as well as meecrowave-runner fail on windows with 
jdk8 (with a simple demo-setup). the same works on linux without issues.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: OWB-2.0.0 to be released soon

[Gerhard Petracek]

sounds great!
i'm going to test the snapshot soon.

regards,
gerhard



2017-06-17 22:43 GMT+02:00 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
>
>
> > Am 17.06.2017 um 22:36 schrieb 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?
> >
> > John
> >
> > On Sat, Jun 17, 2017 at 1:53 PM Mark Struberg 
> wrote:
> > Yes, it is 1:1 backward compatible.
> >
> > The only thing you need to update is the jcdi and common-annotations API:
> >
> > 
> > org.apache.geronimo.specs
> > geronimo-annotation_1.3_spec
> > 1.0-SNAPSHOT
> > 
> >
> > 
> > org.apache.geronimo.specs
> > geronimo-jcdi_2.0_spec
> > 1.0-SNAPSHOT
> > 
> >
> > They will be released this week as well.
> >
> > LieGrue,
> > strub
> >
> >
> > > Am 17.06.2017 um 19:41 schrieb Ludovic Pénet :
> > >
> > > Is it a drop i' remplacement ?
> > > If yes, I would gladky test this works, before test driving the new
> features.
> > >
> > > Ludovic
> > >
> > > Le 17 juin 2017 19:38:01 GMT+02:00, Mark Struberg 
> a écrit :
> > > 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é.
> >
>
>

[jira] [Updated] (OWB-1192) update logic for Instance

[Gerhard Petracek (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OWB-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gerhard Petracek updated OWB-1192:
--
Description: 
new parts:
 * Instance
 ** #stream
 ** #isResolvable
 * BeanManager#createInstance

  was:
new parts:
 * Instance
 ** #stream
 ** #isResolvable
 * BeanManager##createInstance


> update logic for Instance
> -
>
> Key: OWB-1192
> URL: https://issues.apache.org/jira/browse/OWB-1192
> Project: OpenWebBeans
>  Issue Type: Sub-task
>  Components: Core
>    Reporter: Gerhard Petracek
> Fix For: 2.0.0
>
>
> new parts:
>  * Instance
>  ** #stream
>  ** #isResolvable
>  * BeanManager#createInstance



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OWB-1188) implement async events

[Gerhard Petracek (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OWB-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gerhard Petracek updated OWB-1188:
--
Description: 
new parts:
 * Event#fireAsync
 * @ObservesAsync
 * ObserverMethod#isAsync

  was:
new parts:
 * Event#fireAsync
 * ObservesAsync
 * ObserverMethod#isAsync


> implement async events
> --
>
> Key: OWB-1188
> URL: https://issues.apache.org/jira/browse/OWB-1188
> Project: OpenWebBeans
>  Issue Type: Sub-task
>  Components: Events
>    Reporter: Gerhard Petracek
> Fix For: 2.0.0
>
>
> new parts:
>  * Event#fireAsync
>  * @ObservesAsync
>  * ObserverMethod#isAsync



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OWB-1189) add new parts to the event-api

[Gerhard Petracek (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OWB-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gerhard Petracek updated OWB-1189:
--
Description: 
new parts:
 * EventContext
 * NotificationOptions/ImmutableNotificationOptions
 * BeanManager#getEvent
 * ObserverMethod#getPriority()
 * ObserverMethod#notify

new event:
 * BeforeDestroyed

  was:
new parts:
 * EventContext
 * NotificationOptions/ImmutableNotificationOptions
 * BeanManager#getEvent
 * ObserverMethod#getPriority()
 * ObserverMethod#notify


> add new parts to the event-api
> --
>
> Key: OWB-1189
> URL: https://issues.apache.org/jira/browse/OWB-1189
> Project: OpenWebBeans
>  Issue Type: Sub-task
>  Components: Events
>    Reporter: Gerhard Petracek
> Fix For: 2.0.0
>
>
> new parts:
>  * EventContext
>  * NotificationOptions/ImmutableNotificationOptions
>  * BeanManager#getEvent
>  * ObserverMethod#getPriority()
>  * ObserverMethod#notify
> new event:
>  * BeforeDestroyed



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (OWB-1193) implement InterceptionFactory

[Gerhard Petracek (JIRA)]

Gerhard Petracek created OWB-1193:
-

 Summary: implement InterceptionFactory
 Key: OWB-1193
 URL: https://issues.apache.org/jira/browse/OWB-1193
 Project: OpenWebBeans
  Issue Type: Sub-task
  Components: Interceptor and Decorators
Reporter: Gerhard Petracek
 Fix For: 2.0.0


basic logic as well as BeanManager#createInterceptionFactory



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OWB-1189) add new parts to the event-api

[Gerhard Petracek (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OWB-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gerhard Petracek updated OWB-1189:
--
Component/s: (was: Core)
 Events

> add new parts to the event-api
> --
>
> Key: OWB-1189
> URL: https://issues.apache.org/jira/browse/OWB-1189
> Project: OpenWebBeans
>  Issue Type: Sub-task
>  Components: Events
>    Reporter: Gerhard Petracek
> Fix For: 2.0.0
>
>
> new parts:
>  * EventContext
>  * NotificationOptions/ImmutableNotificationOptions
>  * BeanManager#getEvent
>  * ObserverMethod#getPriority()
>  * ObserverMethod#notify



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OWB-1188) implement async events

[Gerhard Petracek (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OWB-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gerhard Petracek updated OWB-1188:
--
Component/s: (was: Core)
 Events

> implement async events
> --
>
> Key: OWB-1188
> URL: https://issues.apache.org/jira/browse/OWB-1188
> Project: OpenWebBeans
>  Issue Type: Sub-task
>  Components: Events
>    Reporter: Gerhard Petracek
> Fix For: 2.0.0
>
>
> new parts:
>  * Event#fireAsync
>  * ObservesAsync
>  * ObserverMethod#isAsync



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (OWB-1192) update logic for Instance

[Gerhard Petracek (JIRA)]

Gerhard Petracek created OWB-1192:
-

 Summary: update logic for Instance
 Key: OWB-1192
 URL: https://issues.apache.org/jira/browse/OWB-1192
 Project: OpenWebBeans
  Issue Type: Sub-task
  Components: Core
Reporter: Gerhard Petracek
 Fix For: 2.0.0


new parts:
 * Instance
 ** #stream
 ** #isResolvable
 * BeanManager##createInstance



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (OWB-1189) add new parts to the event-api

[Gerhard Petracek (JIRA)]

Gerhard Petracek created OWB-1189:
-

 Summary: add new parts to the event-api
 Key: OWB-1189
 URL: https://issues.apache.org/jira/browse/OWB-1189
 Project: OpenWebBeans
  Issue Type: Sub-task
  Components: Core
Reporter: Gerhard Petracek
 Fix For: 2.0.0


new parts:
 * EventContext
 * NotificationOptions/ImmutableNotificationOptions
 * BeanManager#getEvent
 * ObserverMethod#getPriority()
 * ObserverMethod#notify



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OWB-1188) implement async events

[Gerhard Petracek (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OWB-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gerhard Petracek updated OWB-1188:
--
Description: 
new parts:
 * Event#fireAsync
 * ObservesAsync
 * ObserverMethod#isAsync

  was:
new parts:
 * Event#fireAsync
 * ObservesAsync

Component/s: Core

> implement async events
> --
>
> Key: OWB-1188
> URL: https://issues.apache.org/jira/browse/OWB-1188
> Project: OpenWebBeans
>  Issue Type: Sub-task
>  Components: Core
>    Reporter: Gerhard Petracek
> Fix For: 2.0.0
>
>
> new parts:
>  * Event#fireAsync
>  * ObservesAsync
>  * ObserverMethod#isAsync



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (OWB-1187) implement configurators

[Gerhard Petracek (JIRA)]

Gerhard Petracek created OWB-1187:
-

 Summary: implement configurators
 Key: OWB-1187
 URL: https://issues.apache.org/jira/browse/OWB-1187
 Project: OpenWebBeans
  Issue Type: Sub-task
Reporter: Gerhard Petracek
 Fix For: 2.0.0


new configurators:
 * AnnotatedConstructorConfigurator
 * AnnotatedFieldConfigurator
 * AnnotatedMethodConfigurator
 * AnnotatedParameterConfigurator
 * AnnotatedTypeConfigurator
 * BeanAttributesConfigurator
 * BeanConfigurator
 * InjectionPointConfigurator
 * ObserverMethodConfigurator
 * ProducerConfigurator




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OWB-1185) implement Annotated#getAnnotations

[Gerhard Petracek (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OWB-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gerhard Petracek updated OWB-1185:
--
Description: 
+ default implementations in:
 * AnnotatedConstructor
 * AnnotatedField
 * AnnotatedMethod
 * AnnotatedParameter
 * AnnotatedType


> implement Annotated#getAnnotations
> --
>
> Key: OWB-1185
> URL: https://issues.apache.org/jira/browse/OWB-1185
> Project: OpenWebBeans
>  Issue Type: Sub-task
>  Components: Core
>    Reporter: Gerhard Petracek
> Fix For: 2.0.0
>
>
> + default implementations in:
>  * AnnotatedConstructor
>  * AnnotatedField
>  * AnnotatedMethod
>  * AnnotatedParameter
>  * AnnotatedType



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OWB-1186) implement new methods of bootstrapping-events

[Gerhard Petracek (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OWB-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gerhard Petracek updated OWB-1186:
--
Description: 
new methods:
AfterBeanDiscovery
 #addBean()
 #addObserverMethod()
AfterTypeDiscovery
 #addAnnotatedType(Class, String)
BeforeBeanDiscovery
 #addAnnotatedType(Class, String)
 #configureQualifier(Class)
 #configureInterceptorBinding(Class)
ProcessAnnotatedType#configureAnnotatedType
ProcessBeanAttributes
 #configureBeanAttributes
 #ignoreFinalMethods
ProcessInjectionPoint
 #configureInjectionPoint
ProcessObserverMethod
 #setObserverMethod
 #configureObserverMethod
 #veto
ProcessProducer#configureProducer()



  was:
new methods:
AfterBeanDiscovery
 #addBean()
 #addObserverMethod()
AfterTypeDiscovery
 #addAnnotatedType(Class, String)
BeforeBeanDiscovery
 #addAnnotatedType(Class, String)
 #configureQualifier(Class)
 #configureInterceptorBinding(Class)



> implement new methods of bootstrapping-events
> -
>
> Key: OWB-1186
> URL: https://issues.apache.org/jira/browse/OWB-1186
> Project: OpenWebBeans
>  Issue Type: Sub-task
>    Reporter: Gerhard Petracek
> Fix For: 2.0.0
>
>
> new methods:
> AfterBeanDiscovery
>  #addBean()
>  #addObserverMethod()
> AfterTypeDiscovery
>  #addAnnotatedType(Class, String)
> BeforeBeanDiscovery
>  #addAnnotatedType(Class, String)
>  #configureQualifier(Class)
>  #configureInterceptorBinding(Class)
> ProcessAnnotatedType#configureAnnotatedType
> ProcessBeanAttributes
>  #configureBeanAttributes
>  #ignoreFinalMethods
> ProcessInjectionPoint
>  #configureInjectionPoint
> ProcessObserverMethod
>  #setObserverMethod
>  #configureObserverMethod
>  #veto
> ProcessProducer#configureProducer()



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OWB-1186) implement new methods of bootstrapping-events

[Gerhard Petracek (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OWB-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gerhard Petracek updated OWB-1186:
--
Description: 
new methods:
AfterBeanDiscovery
 #addBean()
 #addObserverMethod()
AfterTypeDiscovery
 #addAnnotatedType(Class, String)
BeforeBeanDiscovery
 #addAnnotatedType(Class, String)
 #configureQualifier(Class)
 #configureInterceptorBinding(Class)


  was:
new methods:
 #addBean()
 #addObserverMethod()



> implement new methods of bootstrapping-events
> -
>
> Key: OWB-1186
> URL: https://issues.apache.org/jira/browse/OWB-1186
> Project: OpenWebBeans
>  Issue Type: Sub-task
>    Reporter: Gerhard Petracek
> Fix For: 2.0.0
>
>
> new methods:
> AfterBeanDiscovery
>  #addBean()
>  #addObserverMethod()
> AfterTypeDiscovery
>  #addAnnotatedType(Class, String)
> BeforeBeanDiscovery
>  #addAnnotatedType(Class, String)
>  #configureQualifier(Class)
>  #configureInterceptorBinding(Class)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OWB-1186) implement new methods of bootstrapping-events

[Gerhard Petracek (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OWB-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gerhard Petracek updated OWB-1186:
--
Summary: implement new methods of bootstrapping-events  (was: implement new 
methods of AfterBeanDiscovery)

> implement new methods of bootstrapping-events
> -
>
> Key: OWB-1186
> URL: https://issues.apache.org/jira/browse/OWB-1186
> Project: OpenWebBeans
>  Issue Type: Sub-task
>    Reporter: Gerhard Petracek
> Fix For: 2.0.0
>
>
> new methods:
>  #addBean()
>  #addObserverMethod()



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (OWB-1186) implement new methods of AfterBeanDiscovery

[Gerhard Petracek (JIRA)]

Gerhard Petracek created OWB-1186:
-

 Summary: implement new methods of AfterBeanDiscovery
 Key: OWB-1186
 URL: https://issues.apache.org/jira/browse/OWB-1186
 Project: OpenWebBeans
  Issue Type: Sub-task
Reporter: Gerhard Petracek
 Fix For: 2.0.0


new methods:
 #addBean()
 #addObserverMethod()




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (OWB-1185) implement Annotated#getAnnotations

[Gerhard Petracek (JIRA)]

Gerhard Petracek created OWB-1185:
-

 Summary: implement Annotated#getAnnotations
 Key: OWB-1185
 URL: https://issues.apache.org/jira/browse/OWB-1185
 Project: OpenWebBeans
  Issue Type: Sub-task
  Components: Core
Reporter: Gerhard Petracek
 Fix For: 2.0.0






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [VOTE] Release Apache OpenWebBeans-1.7.3

[Gerhard Petracek]

i've upgraded [1] to v1.7.3 and all tests look fine.
-> +1

regards,
gerhard

[1] https://github.com/CDIatWork/IdeaFork



2017-04-16 0:56 GMT+02:00 Mark Struberg :
>
> Hi folks!
>
> I've run the tasks to ship OWB 1.7.3.
>
> The following bugs got fixed
>
> Bug
>
> • [OWB-1172] - getResources doesn't work in OWB Arquillian
container for WebArchives
> • [OWB-1173] - InjectionPoint with no ownerBean fails on
serialisation
> • [OWB-1175] - Duplicate registration of ServletContextBean
> • [OWB-1177] - producer should check runtime instance for
Serializable constraint and not returned type
> Task
>
> • [OWB-1178] - Upgrade Arquillian to 1.1.13 and ShrinkWrap to
1.2.6
>
>
> The staging repo is:
>
https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1026/
>
> And here is the Source release:
>
https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1026/org/apache/openwebbeans/openwebbeans/1.7.3/
>
> And the SVN tag:
> http://svn.apache.org/viewvc?view=revision=1791551
>
>
>
> Please VOTE:
>
> [+1] Ship it!
> [+0] meh, don't care
> [-1] Stop, because ${showstopper}
>
> The VOTE is open for 72h
>
> txs and LieGrue,
> strub
>
>

Re: [VOTE] Release Apache Meecrowave-0.2.0

[Gerhard Petracek]

the source-zip looks fine -> +1

regards,
gerhard



2017-01-04 13:18 GMT+01:00 Reinhard Sandtner :

> +1
>
> lg
> reini
>
> > Am 04.01.2017 um 09:20 schrieb Mark Struberg  >:
> >
> > checked the following:
> >
> > * sig
> > * sha1
> > * dependencies and their licenses
> > * rat passes
> > * LICENSE and NOTICE in source zip
> > * LICENSE and NOTICE in other artifacts
> > * compiles
> > * tests pass
> > * also tested with a few real world projects
> >
> >
> > +1
> >
> > LieGrue,
> > strub
> >
> >
> >
> >> Am 02.01.2017 um 18:08 schrieb Mark Struberg  >:
> >>
> >> Hi all!
> >>
> >> It's time to do our very first Meecrowave release!
> >> And since we already use it in some production systems we upped the
> version from 0.0.1 to 0.2.0.
> >>
> >> Here is the staging repo
> >> https://repository.apache.org/content/repositories/orgapache
> openwebbeans-1021/
> >>
> >> And here comes the source release zip:
> >> https://repository.apache.org/content/repositories/orgapache
> openwebbeans-1021/org/apache/meecrowave/meecrowave/0.2.0/
> >>
> >> My gpg key can be found at https://svn.apache.org/repos/a
> sf/openwebbeans/trunk/KEYS
> >>
> >> So what is Apache Meecrowave (tm)?
> >>
> >> Meecrowave is a lightweight bundle of
> >>
> >> * Servlet-4.0 (Apache Tomcat 9.0.0.M15)
> >> * CDI-1.2 (Apache OpenWebBeans-1.7.1)
> >> * JAX-RS (Apache CXF-3.1.9)
> >> * JSON-P-1.0 (Apache Johnzon-1.0.0)
> >>
> >> And all that within only 9MB!
> >>
> >> Want to test it?
> >> Just download
> >> https://repository.apache.org/content/repositories/orgapache
> openwebbeans-1021/org/apache/meecrowave/meecrowave-core/0.
> 2.0/meecrowave-core-0.2.0-runner.jar
> >> (sha1: 042a2b4344c494cff378f072423ed8bb4a2ea93a)
> >> and type
> >>
> >> For running an existing.war file:
> >> java -jar meecrowave-core-0.2.0-runner.jar existing.war
> >>
> >> For running an existing-fat.jar file:
> >> java -jar meecrowave-core-0.2.0-runner.jar existing-fat.jar
> >>
> >> Meecrowave can do a lot more.
> >> We will host and imporove the docs at
> >> http://openwebbeans.apache.org/meecrowave/
> >>
> >>
> >> Please VOTE:
> >> [+1] great, let's ship it
> >> [+0] meh, don't care
> >> [-1] stop there is a ${blocker}
> >>
> >> The VOTE is open for 72h.
> >>
> >>
> >> txs and LieGrue,
> >> strub
> >>
> >> PS: thanks to Romain for pushing this!
> >
>
>

[jira] [Reopened] (OWB-1121) IllegalStateException in case of duplicated classes

[Gerhard Petracek (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OWB-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gerhard Petracek reopened OWB-1121:
---

see the voting thread for v1.6.3

> IllegalStateException in case of duplicated classes
> ---
>
> Key: OWB-1121
> URL: https://issues.apache.org/jira/browse/OWB-1121
> Project: OpenWebBeans
>  Issue Type: Bug
>    Reporter: Gerhard Petracek
>Assignee: Mark Struberg
>
> duplicated classes should lead to a warning (with the exact locations of the 
> redundant classes) and not to:
> java.lang.IllegalStateException: It's not allowed to call getBeans(Type, 
> Annotation...) before AfterBeanDiscovery
>  at 
> org.apache.webbeans.container.InjectableBeanManager.checkAfterBeanDiscoveryProcessed(InjectableBeanManager.java:402)
>  at 
> org.apache.webbeans.container.InjectableBeanManager.getBeans(InjectableBeanManager.java:121)
> ...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: WARNING for duplicated interceptors

[Gerhard Petracek]

hi,

i would prefer an info which shows the final order (of interceptors,...)
including skipped configs due to such a (valid) redundancy.
-> with that we get an additional benefit (for users).

regards,
gerhard



2016-07-08 12:27 GMT+02:00 Romain Manni-Bucau :

> Hi guys
>
> today we issue a warning when duplicated interceptors are set up.
>
> Saw it with DS using beans.xml + @Priority on CDI 1.1 runtimes
>
> I wonder if it is ok to put it as an INFO?
>
> I'd like a startup to not have any log > INFO when all is fine and this
> behavior is ok for the spec as said Gerhard.
>
> wdyt?
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Wordpress Blog
>  | Github <
> https://github.com/rmannibucau> |
> LinkedIn  | Tomitriber
>  | JavaEE Factory
> 
>

[jira] [Created] (OWB-1130) ContainerCtrlTckTest fails

[Gerhard Petracek (JIRA)]

Gerhard Petracek created OWB-1130:
-

 Summary: ContainerCtrlTckTest fails
 Key: OWB-1130
 URL: https://issues.apache.org/jira/browse/OWB-1130
 Project: OpenWebBeans
  Issue Type: Bug
Affects Versions: 1.6.3
Reporter: Gerhard Petracek
Assignee: Mark Struberg
Priority: Blocker
 Fix For: 1.6.4


https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;a=blob;f=deltaspike/cdictrl/tck/src/main/java/org/apache/deltaspike/cdise/tck/ContainerCtrlTckTest.java;h=536508b045a84a48acc4cbbbe4b9e3fdfd0fe941;hb=HEAD
 fails with owb 1.6.3



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: seteventfired too early?

[Gerhard Petracek]

since it happened randomly, i tested it multiple times.
so far it looks fine - thx!

regards,
gerhard



2016-04-14 19:57 GMT+02:00 Romain Manni-Bucau <rmannibu...@gmail.com>:

> pushed a change, if anyone has time to validate it. Hope to be able to work
> on a test next week but any help is welcomed
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> <http://www.tomitribe.com> | JavaEE Factory
> <https://javaeefactory-rmannibucau.rhcloud.com>
>
> 2016-04-14 18:10 GMT+02:00 Gerhard Petracek <gpetra...@apache.org>:
>
> > +1 for changing it (otherwise we break ds-partial-beans)
> >
> > regards,
> > gerhard
> >
> >
> >
> > 2016-03-20 15:03 GMT+01:00 Romain Manni-Bucau <rmannibu...@gmail.com>:
> >
> > > Hi guys,
> > >
> > > any reason to consider the event fired before firing it there:
> > >
> > >
> >
> https://github.com/apache/openwebbeans/blob/5197d2ce7f270e7089184b942d4c8e1c8ddc53b6/webbeans-impl/src/main/java/org/apache/webbeans/config/BeansDeployer.java#L670
> > > ?
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau |  Blog | Github | LinkedIn | Tomitriber
> > >
> >
>

Re: seteventfired too early?

[Gerhard Petracek]

+1 for changing it (otherwise we break ds-partial-beans)

regards,
gerhard



2016-03-20 15:03 GMT+01:00 Romain Manni-Bucau :

> Hi guys,
>
> any reason to consider the event fired before firing it there:
>
> https://github.com/apache/openwebbeans/blob/5197d2ce7f270e7089184b942d4c8e1c8ddc53b6/webbeans-impl/src/main/java/org/apache/webbeans/config/BeansDeployer.java#L670
> ?
>
> Romain Manni-Bucau
> @rmannibucau |  Blog | Github | LinkedIn | Tomitriber
>

Re: [VOTE] Release OpenWebBeans-1.6.3

[Gerhard Petracek]

hi romain,

that's correct (as discussed in the irc-channel).
+ mark fixed it already.

however, in such a case you get the message:
"It's not allowed to call getBeans(Type, Annotation...) before
AfterBeanDiscovery"

mark said that it was caused by duplicated classes.
imo owb shouldn't fail that way (in such a case).
-> i won't vote with +1 (but with +0).

regards,
gerhard



2016-02-17 19:44 GMT+01:00 Romain Manni-Bucau <rmannibu...@gmail.com>:

> AFAIK it is due to a setup issue in DS which broke the classpath on some
> module if it is the one you refer too. This is fine to release then.
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> <http://www.tomitribe.com>
>
> 2016-02-17 17:11 GMT+01:00 Gerhard Petracek <gerhard.petra...@gmail.com>:
>
> > we shouldn't release it (as it is), because deltaspike-cdictrl-owb fails
> > with it (v1.6.2 passes).
> >
> > regards,
> > gerhard
> >
> >
> >
> > 2016-02-16 23:17 GMT+01:00 Mark Struberg <strub...@yahoo.de>:
> >
> > > Hi!
> > >
> > > I’ve performed the steps to release Apache OpenWebBeans-1.6.3
> > >
> > > The staging repo can be found here:
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1016/
> > >
> > > The source distribution is
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1016/org/apache/openwebbeans/openwebbeans/1.6.3/
> > >
> > > Here is the binary distribution:
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1016/org/apache/openwebbeans/openwebbeans-distribution/1.6.3/
> > >
> > > To install this owb version with plain Tomcat just unzip the binary
> > > distribution and use the respective scripts (install_owb_*.sh and .bat)
> > >
> > > This OWB version will also be contained in the upcoming TomEE-7.0.x
> > > release.
> > >
> > > The following bugs and improvements got resolved:
> > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310844=12333111
> > >
> > >
> > > Please VOTE on the release:
> > >
> > > [+1] Yea, let’s ship it
> > > [+0] Meh, don’t care
> > > [-1] Stop, there is a ${blocker issue}
> > >
> > > The VOTE is open for 72h
> > >
> > > txs and LieGrue,
> > > strub
> >
>

Re: [VOTE] Release OpenWebBeans-1.6.3

[Gerhard Petracek]

we shouldn't release it (as it is), because deltaspike-cdictrl-owb fails
with it (v1.6.2 passes).

regards,
gerhard



2016-02-16 23:17 GMT+01:00 Mark Struberg :

> Hi!
>
> I’ve performed the steps to release Apache OpenWebBeans-1.6.3
>
> The staging repo can be found here:
>
> https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1016/
>
> The source distribution is
>
> https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1016/org/apache/openwebbeans/openwebbeans/1.6.3/
>
> Here is the binary distribution:
>
> https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1016/org/apache/openwebbeans/openwebbeans-distribution/1.6.3/
>
> To install this owb version with plain Tomcat just unzip the binary
> distribution and use the respective scripts (install_owb_*.sh and .bat)
>
> This OWB version will also be contained in the upcoming TomEE-7.0.x
> release.
>
> The following bugs and improvements got resolved:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310844=12333111
>
>
> Please VOTE on the release:
>
> [+1] Yea, let’s ship it
> [+0] Meh, don’t care
> [-1] Stop, there is a ${blocker issue}
>
> The VOTE is open for 72h
>
> txs and LieGrue,
> strub

Re: release OWB next week?

[Gerhard Petracek]

+1

regards,
gerhard



2016-02-13 13:09 GMT+01:00 Thomas Andraschko :

> +1
>
> 2016-02-13 12:56 GMT+01:00 Romain Manni-Bucau :
>
> > +1 then we release tomee
> > Le 13 févr. 2016 12:29, "Mark Struberg"  a écrit :
> >
> > > hi folks!
> > >
> > > What else is missing for the release?
> > > Any tickets you like to get in before I go on and start the release
> > train?
> > >
> > > LieGrue,
> > > strub
> > >
> >
>

Re: moving to owb-1.7.0-SNAPSHOT?

[Gerhard Petracek]

+1 for 1.7
imo there is no need to stick with 1.6.x

regards,
gerhard



2016-01-31 16:42 GMT+01:00 Thomas Andraschko :

> +1 for 1.7
> but as romain said, i'm also very sure this is rarely used by users.
>
> 2016-01-31 16:26 GMT+01:00 Mark Struberg :
>
> > +1 for what? staying with 1.6.x or moving to 1.7.x?
> >
> > txs and LieGrue,
> > strub
> >
> > > Am 31.01.2016 um 13:06 schrieb Thomas Andraschko <
> > andraschko.tho...@gmail.com>:
> > >
> > > +1
> > >
> > > 2016-01-31 12:59 GMT+01:00 Mark Struberg :
> > >
> > >> hi folks!
> > >>
> > >> While implementing OWB-1107 I had to introduce a subinterface of
> > >> ScannerService called ‚BdaScannerService‘
> > >> While OWB deployer works find with both old ScannerService and new
> > >> BdaScannerService SPI impls it might probably be better to indicate
> the
> > new
> > >> SPI by moving the minor number?
> > >>
> > >> I personally can live with keeping 1.6.3 as next version. But I am
> also
> > >> fine with 1.7.x as we really introduced a few new things which are up
> > for
> > >> CDI-2.0 officially.
> > >>
> > >> Any thoughts?
> > >>
> > >> LieGrue,
> > >> strub
> >
> >
>

Re: [DISCUSS] moving OpenWebBeans to GIT?

[Gerhard Petracek]

+1

regards,
gerhard



2016-01-23 11:59 GMT+01:00 Mark Struberg :

> Hi!
>
> What do you think about moving openwebbeans to GIT.
> Of course hosted at the ASF.
>
> Would probably be helpful when working on the CDI-2.0 branch in the future.
>
> LieGrue,
> strub
>
>

[jira] [Commented] (OWB-1095) Beans not fully initialized in AfterBeanDiscovery or InjectionPoint validation to early?

[Gerhard Petracek (JIRA)]

[ 
https://issues.apache.org/jira/browse/OWB-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14960743#comment-14960743
 ] 

Gerhard Petracek commented on OWB-1095:
---

the issue is in InjectionResolver.
it contains an empty value in resolvedComponents for the key in question.

we just need to change
{code}
Set<Bean> resolvedComponents = resolvedBeansByType.get(cacheKey);
if (resolvedComponents != null)
{
return resolvedComponents;
}
{code}

to

{code}
Set<Bean> resolvedComponents = resolvedBeansByType.get(cacheKey);
if (resolvedComponents != null && !resolvedComponents.isEmpty())
{
return resolvedComponents;
}
{code}

and it will work.

> Beans not fully initialized in AfterBeanDiscovery or InjectionPoint 
> validation to early?
> 
>
> Key: OWB-1095
> URL: https://issues.apache.org/jira/browse/OWB-1095
> Project: OpenWebBeans
>  Issue Type: Bug
>  Components: Core, Injection and Lookup
>Affects Versions: 1.6.2
>Reporter: Thomas Andraschko
>Priority: Critical
> Fix For: 1.6.3
>
> Attachments: owb-ds-test.7z
>
>
> DeltaSpike's ConverterAndValidatorProxyExtension possible adds new beans via 
> afterBeanDiscovery#addBean and DS BeanBuilder if the JSF converter needs to 
> be proxied.
> However, when the converter has a injectionPoint, it will be created during 
> AfterBeanDiscovery via beanManager#createInjectionTarget but OWB always 
> throws "no bean available for class ..."
> This works fine in older OWB versions and other containers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OWB-1095) Beans not fully initialized in AfterBeanDiscovery or InjectionPoint validation to early?

[Gerhard Petracek (JIRA)]

[ 
https://issues.apache.org/jira/browse/OWB-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14960754#comment-14960754
 ] 

Gerhard Petracek commented on OWB-1095:
---

no - the empty value is stored too early in that case, because at some point 
there would be a value.
(just debug it with the provided example and set the result to null to run the 
code after the if-statement and it will work.)

> Beans not fully initialized in AfterBeanDiscovery or InjectionPoint 
> validation to early?
> 
>
> Key: OWB-1095
> URL: https://issues.apache.org/jira/browse/OWB-1095
> Project: OpenWebBeans
>  Issue Type: Bug
>  Components: Core, Injection and Lookup
>Affects Versions: 1.6.2
>Reporter: Thomas Andraschko
>Priority: Critical
> Fix For: 1.6.3
>
> Attachments: owb-ds-test.7z
>
>
> DeltaSpike's ConverterAndValidatorProxyExtension possible adds new beans via 
> afterBeanDiscovery#addBean and DS BeanBuilder if the JSF converter needs to 
> be proxied.
> However, when the converter has a injectionPoint, it will be created during 
> AfterBeanDiscovery via beanManager#createInjectionTarget but OWB always 
> throws "no bean available for class ..."
> This works fine in older OWB versions and other containers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OWB-1095) Beans not fully initialized in AfterBeanDiscovery or InjectionPoint validation to early?

[Gerhard Petracek (JIRA)]

[ 
https://issues.apache.org/jira/browse/OWB-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14960754#comment-14960754
 ] 

Gerhard Petracek edited comment on OWB-1095 at 10/16/15 2:04 PM:
-

no - the empty value is stored too early in that case, because at some point 
there would be a value.
(just debug it with the provided example and set the result to null to run the 
code after the if-statement and it will work.)

@don't cache before the startup finished:
+1
that would be my suggestion as well (at least in case of empty values - if we 
need to keep them)


was (Author: gpetracek):
no - the empty value is stored too early in that case, because at some point 
there would be a value.
(just debug it with the provided example and set the result to null to run the 
code after the if-statement and it will work.)

> Beans not fully initialized in AfterBeanDiscovery or InjectionPoint 
> validation to early?
> 
>
> Key: OWB-1095
> URL: https://issues.apache.org/jira/browse/OWB-1095
> Project: OpenWebBeans
>  Issue Type: Bug
>  Components: Core, Injection and Lookup
>Affects Versions: 1.6.2
>Reporter: Thomas Andraschko
>Priority: Critical
> Fix For: 1.6.3
>
> Attachments: owb-ds-test.7z
>
>
> DeltaSpike's ConverterAndValidatorProxyExtension possible adds new beans via 
> afterBeanDiscovery#addBean and DS BeanBuilder if the JSF converter needs to 
> be proxied.
> However, when the converter has a injectionPoint, it will be created during 
> AfterBeanDiscovery via beanManager#createInjectionTarget but OWB always 
> throws "no bean available for class ..."
> This works fine in older OWB versions and other containers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OWB-1095) Beans not fully initialized in AfterBeanDiscovery or InjectionPoint validation to early?

[Gerhard Petracek (JIRA)]

[ 
https://issues.apache.org/jira/browse/OWB-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14960754#comment-14960754
 ] 

Gerhard Petracek edited comment on OWB-1095 at 10/16/15 2:07 PM:
-

no - the empty value is stored too early in that case, because at some point 
there would be a value.
(just debug it with the provided example and set the result to null to run the 
code after the if-statement and it will work.)

@don't cache before the startup finished:
+1
that would be my suggestion as well (at least in case of empty values - if we 
need to keep them)
the change mentioned before is for sure just useful during the startup.


was (Author: gpetracek):
no - the empty value is stored too early in that case, because at some point 
there would be a value.
(just debug it with the provided example and set the result to null to run the 
code after the if-statement and it will work.)

@don't cache before the startup finished:
+1
that would be my suggestion as well (at least in case of empty values - if we 
need to keep them)

> Beans not fully initialized in AfterBeanDiscovery or InjectionPoint 
> validation to early?
> 
>
> Key: OWB-1095
> URL: https://issues.apache.org/jira/browse/OWB-1095
> Project: OpenWebBeans
>  Issue Type: Bug
>  Components: Core, Injection and Lookup
>Affects Versions: 1.6.2
>Reporter: Thomas Andraschko
>Priority: Critical
> Fix For: 1.6.3
>
> Attachments: owb-ds-test.7z
>
>
> DeltaSpike's ConverterAndValidatorProxyExtension possible adds new beans via 
> afterBeanDiscovery#addBean and DS BeanBuilder if the JSF converter needs to 
> be proxied.
> However, when the converter has a injectionPoint, it will be created during 
> AfterBeanDiscovery via beanManager#createInjectionTarget but OWB always 
> throws "no bean available for class ..."
> This works fine in older OWB versions and other containers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: starting with CDI-2.0?

[Gerhard Petracek]

+1

regards,
gerhard



2015-08-11 13:58 GMT+02:00 Mark Struberg strub...@yahoo.de:

 Hi folks!

 What about starting with implementing CDI-2.0?

 The spec is of course not finished but I’d like to be a bit more bleeding
 edge than last time ;)

 I’ll start with copying over the geronimo-jcdi spec packages and create a
 feature branch in our SVN.
 If you have some changes then feel free to ship some patches!

 LieGrue,
 strub

Re: [VOTE] Release OpenWebBeans-1.6.2

[Gerhard Petracek]

+1

regards,
gerhard



2015-08-07 22:03 GMT+02:00 Mark Struberg strub...@yahoo.de:

 Hi!

 I'd like to call a VOTE for a maintenance release of Apache
 OpenWebBeans-1.6.2.

 We fixed 2 bugs which are needed by TomEE-7.x

 Here is the staging repo:

 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1015/

 And here is the source release:

 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1015/org/apache/openwebbeans/openwebbeans/1.6.2/openwebbeans-1.6.2-source-release.zip


 [+1] let's ship it
 [+0] meh don't care
 [-1] nope, because ${reason}

 The VOTE is open for 72h.


 txs and LieGrue,
 strub

[jira] [Reopened] (OWB-935) wrong result of javax.enterprise.inject.Instance in combination with alternatives

[Gerhard Petracek (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OWB-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gerhard Petracek reopened OWB-935:
--

 wrong result of javax.enterprise.inject.Instance in combination with 
 alternatives
 -

 Key: OWB-935
 URL: https://issues.apache.org/jira/browse/OWB-935
 Project: OpenWebBeans
  Issue Type: Bug
  Components: Injection and Lookup
Affects Versions: 1.2.2
Reporter: Gerhard Petracek
Assignee: Mark Struberg

 if the result of InjectionResolver#findByAlternatives is  1 (for 
 InstanceImpl#iterator) and there is one alternative-bean in the result, beans 
 without alternative implementations aren't part of the result, because 
 alternativeSet only contains alternative beans - see:
 {code}
 if (containsAlternative)
 {
 return alternativeSet;
 }
 return enableSet;
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OWB-935) wrong result of javax.enterprise.inject.Instance in combination with alternatives

[Gerhard Petracek (JIRA)]

[ 
https://issues.apache.org/jira/browse/OWB-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14645953#comment-14645953
 ] 

Gerhard Petracek commented on OWB-935:
--

see the 3 tests - two of them fail

 wrong result of javax.enterprise.inject.Instance in combination with 
 alternatives
 -

 Key: OWB-935
 URL: https://issues.apache.org/jira/browse/OWB-935
 Project: OpenWebBeans
  Issue Type: Bug
  Components: Injection and Lookup
Affects Versions: 1.2.2
Reporter: Gerhard Petracek
Assignee: Mark Struberg
 Attachments: OWB-935.zip


 if the result of InjectionResolver#findByAlternatives is  1 (for 
 InstanceImpl#iterator) and there is one alternative-bean in the result, beans 
 without alternative implementations aren't part of the result, because 
 alternativeSet only contains alternative beans - see:
 {code}
 if (containsAlternative)
 {
 return alternativeSet;
 }
 return enableSet;
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OWB-935) wrong result of javax.enterprise.inject.Instance in combination with alternatives

[Gerhard Petracek (JIRA)]

[ 
https://issues.apache.org/jira/browse/OWB-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14645953#comment-14645953
 ] 

Gerhard Petracek edited comment on OWB-935 at 7/29/15 12:57 PM:


see the 3 tests - two of them fail
(all 3 should result in the same count, however, only the constellation without 
activated default-beans result in the correct count. furthermore the amount of 
enabled alternatives impact the result - see the all- vs. mixed-package...)

the issue is that qualifiers are ignored in #findByAlternatives *once* @Any is 
used.
= if you have at least one active alternative (e.g. for qualifier Q1), that 
alternative impacts the rest of the result (- also beans with a different 
qualifier - in the test e.g. Q2).


was (Author: gpetracek):
see the 3 tests - two of them fail
(all 3 should result in the same count, however, only the constellation without 
activated default-beans result in the correct count. furthermore the amount of 
enabled alternatives impact the result - see the all- vs. mixed-package...)

the issue is that qualifiers are ignored in #findByAlternatives *once* @Any is 
used.
- if you have at least one active alternative (e.g. for qualifier Q1), that 
alternative impacts the rest of the result (- also beans with a different 
qualifier - in the test e.g. Q2).

 wrong result of javax.enterprise.inject.Instance in combination with 
 alternatives
 -

 Key: OWB-935
 URL: https://issues.apache.org/jira/browse/OWB-935
 Project: OpenWebBeans
  Issue Type: Bug
  Components: Injection and Lookup
Affects Versions: 1.2.2
Reporter: Gerhard Petracek
Assignee: Mark Struberg
 Attachments: OWB-935.zip


 if the result of InjectionResolver#findByAlternatives is  1 (for 
 InstanceImpl#iterator) and there is one alternative-bean in the result, beans 
 without alternative implementations aren't part of the result, because 
 alternativeSet only contains alternative beans - see:
 {code}
 if (containsAlternative)
 {
 return alternativeSet;
 }
 return enableSet;
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OWB-935) wrong result of javax.enterprise.inject.Instance in combination with alternatives

[Gerhard Petracek (JIRA)]

[ 
https://issues.apache.org/jira/browse/OWB-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14645953#comment-14645953
 ] 

Gerhard Petracek edited comment on OWB-935 at 7/29/15 12:57 PM:


see the 3 tests - two of them fail
(all 3 should result in the same count, however, only the constellation without 
activated default-beans result in the correct count. furthermore the amount of 
enabled alternatives impact the result - see the all- vs. mixed-package...)

the issue is that qualifiers are ignored in #findByAlternatives *once* @Any is 
used.
- if you have at least one active alternative (e.g. for qualifier Q1), that 
alternative impacts the rest of the result (- also beans with a different 
qualifier - in the test e.g. Q2).


was (Author: gpetracek):
see the 3 tests - two of them fail
(all 3 should result in the same count, however, only the constellation without 
activated default-beans result in the correct count. furthermore the amount of 
enabled alternatives impact the result - see the all- vs. mixed-package...)

 wrong result of javax.enterprise.inject.Instance in combination with 
 alternatives
 -

 Key: OWB-935
 URL: https://issues.apache.org/jira/browse/OWB-935
 Project: OpenWebBeans
  Issue Type: Bug
  Components: Injection and Lookup
Affects Versions: 1.2.2
Reporter: Gerhard Petracek
Assignee: Mark Struberg
 Attachments: OWB-935.zip


 if the result of InjectionResolver#findByAlternatives is  1 (for 
 InstanceImpl#iterator) and there is one alternative-bean in the result, beans 
 without alternative implementations aren't part of the result, because 
 alternativeSet only contains alternative beans - see:
 {code}
 if (containsAlternative)
 {
 return alternativeSet;
 }
 return enableSet;
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OWB-935) wrong result of javax.enterprise.inject.Instance in combination with alternatives

[Gerhard Petracek (JIRA)]

[ 
https://issues.apache.org/jira/browse/OWB-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14645953#comment-14645953
 ] 

Gerhard Petracek edited comment on OWB-935 at 7/29/15 12:20 PM:


see the 3 tests - two of them fail
(all 3 should result in the same count, however, only the constellation without 
activated default-beans result in the correct count. furthermore the amount of 
enabled alternatives impact the result - see the all- vs. mixed-package...)


was (Author: gpetracek):
see the 3 tests - two of them fail

 wrong result of javax.enterprise.inject.Instance in combination with 
 alternatives
 -

 Key: OWB-935
 URL: https://issues.apache.org/jira/browse/OWB-935
 Project: OpenWebBeans
  Issue Type: Bug
  Components: Injection and Lookup
Affects Versions: 1.2.2
Reporter: Gerhard Petracek
Assignee: Mark Struberg
 Attachments: OWB-935.zip


 if the result of InjectionResolver#findByAlternatives is  1 (for 
 InstanceImpl#iterator) and there is one alternative-bean in the result, beans 
 without alternative implementations aren't part of the result, because 
 alternativeSet only contains alternative beans - see:
 {code}
 if (containsAlternative)
 {
 return alternativeSet;
 }
 return enableSet;
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OWB-1085) bootstrapping events observed outside of extension-implementations

[Gerhard Petracek (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OWB-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gerhard Petracek updated OWB-1085:
--
Attachment: OWB-1085.zip

 bootstrapping events observed outside of extension-implementations
 --

 Key: OWB-1085
 URL: https://issues.apache.org/jira/browse/OWB-1085
 Project: OpenWebBeans
  Issue Type: Bug
  Components: Events
Reporter: Gerhard Petracek
Assignee: Mark Struberg
 Attachments: OWB-1085-extension_event.diff, OWB-1085.zip


 an user notified us on irc that @Observes Object observes e.g. 
 ProcessObserverMethod although the observer-method is outside of an 
 javax.enterprise.inject.spi.Extension-implementation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OWB-1085) bootstrapping events observed outside of extension-implementations

[Gerhard Petracek (JIRA)]

Gerhard Petracek created OWB-1085:
-

 Summary: bootstrapping events observed outside of 
extension-implementations
 Key: OWB-1085
 URL: https://issues.apache.org/jira/browse/OWB-1085
 Project: OpenWebBeans
  Issue Type: Bug
  Components: Events
Reporter: Gerhard Petracek
Assignee: Mark Struberg


an user notified us on irc that @Observes Object observes e.g. 
ProcessObserverMethod although the observer-method is outside of an 
javax.enterprise.inject.spi.Extension-implementation.






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] for Apache OpenWebBeans 1.6.1

[Gerhard Petracek]

+1

regards,
gerhard



2015-06-18 8:46 GMT+02:00 Mark Struberg strub...@yahoo.de:
 +1 from me.

 LieGrue,
 strub


 Am 16.06.2015 um 08:10 schrieb Mark Struberg strub...@yahoo.de:

 Hi!

 I’d like to call a VOTE on Apache OpenWebBeans-1.6.1.

 The staging repository is here
 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1014/

 The source repo is available here
 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1014/org/apache/openwebbeans/openwebbeans/1.6.1/openwebbeans-1.6.1-source-release.zip


 The binary distribution can be found at
 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1014/org/apache/openwebbeans/openwebbeans-distribution/1.6.1/openwebbeans-distribution-1.6.1-binary.zip

 [+1] ship it
 [+0] meh, don’t care
 [-1] stop, because of ${blocker}

 The VOTE is open for 72h

 txs and LieGrue,
 strub

[jira] [Updated] (OWB-1078) create Dockerfiles for installing OpenWebBeans as Docker Image based on Tomcat8

[Gerhard Petracek (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OWB-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gerhard Petracek updated OWB-1078:
--
Issue Type: New Feature  (was: Bug)

 create Dockerfiles for installing OpenWebBeans as Docker Image based on 
 Tomcat8
 ---

 Key: OWB-1078
 URL: https://issues.apache.org/jira/browse/OWB-1078
 Project: OpenWebBeans
  Issue Type: New Feature
  Components: Samples  Documentation
Affects Versions: 1.5.0
Reporter: Mark Struberg
Assignee: Mark Struberg
 Fix For: 1.6.1


 create Dockerfiles for installing OpenWebBeans as Docker Image based on 
 Tomcat8



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (OWB-1081) check Reception.IF_EXISTS in case of an inactive context

[Gerhard Petracek (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OWB-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gerhard Petracek resolved OWB-1081.
---
Resolution: Fixed

 check Reception.IF_EXISTS in case of an inactive context
 

 Key: OWB-1081
 URL: https://issues.apache.org/jira/browse/OWB-1081
 Project: OpenWebBeans
  Issue Type: Improvement
  Components: Events
Affects Versions: 1.6.0
Reporter: Gerhard Petracek
Assignee: Mark Struberg
 Fix For: 1.6.1

 Attachments: OWB-1081.patch


 if Reception.IF_EXISTS is used, observers with inactive contexts should be 
 ignored completely. currently info INFO_0010 gets logged.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OWB-1081) check Reception.IF_EXISTS in case of an inactive context

[Gerhard Petracek (JIRA)]

[ 
https://issues.apache.org/jira/browse/OWB-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14571898#comment-14571898
 ] 

Gerhard Petracek edited comment on OWB-1081 at 6/4/15 12:34 AM:


in ObserverMethodImpl#notify
{code}
Context context;
try
{
  context = manager.getContext(component.getScope());
}
catch (ContextNotActiveException cnae)
{
  if (!ifExist) //only this check is new
  {
// this may happen if we try to e.g. send an event to a @ConversationScoped 
bean from a ServletListener
logger.log(Level.INFO, OWBLogConst.INFO_0010, bean);
  }
  return;
}
{code}


was (Author: gpetracek):
in ObserverMethodImpl#notify
{code}
Context context;
try
{
context = manager.getContext(component.getScope());
}
catch (ContextNotActiveException cnae)
{
if (!ifExist) //only this check is new
{
// this may happen if we try to e.g. send an event to a 
@ConversationScoped bean from a ServletListener
logger.log(Level.INFO, OWBLogConst.INFO_0010, bean);
}
return;
}
{code}

 check Reception.IF_EXISTS in case of an inactive context
 

 Key: OWB-1081
 URL: https://issues.apache.org/jira/browse/OWB-1081
 Project: OpenWebBeans
  Issue Type: Improvement
  Components: Events
Affects Versions: 1.6.0
Reporter: Gerhard Petracek
Assignee: Mark Struberg
 Fix For: 1.6.1

 Attachments: OWB-1081.patch


 if Reception.IF_EXISTS is used, observers with inactive contexts should be 
 ignored completely. currently info INFO_0010 gets logged.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OWB-1081) check Reception.IF_EXISTS in case of an inactive context

[Gerhard Petracek (JIRA)]

[ 
https://issues.apache.org/jira/browse/OWB-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14571898#comment-14571898
 ] 

Gerhard Petracek commented on OWB-1081:
---

in ObserverMethodImpl#notify
{code}
Context context;
try
{
context = manager.getContext(component.getScope());
}
catch (ContextNotActiveException cnae)
{
if (!ifExist) //only this check is new
{
// this may happen if we try to e.g. send an event to a 
@ConversationScoped bean from a ServletListener
logger.log(Level.INFO, OWBLogConst.INFO_0010, bean);
}
return;
}
{code}

 check Reception.IF_EXISTS in case of an inactive context
 

 Key: OWB-1081
 URL: https://issues.apache.org/jira/browse/OWB-1081
 Project: OpenWebBeans
  Issue Type: Improvement
  Components: Events
Affects Versions: 1.6.0
Reporter: Gerhard Petracek
Assignee: Mark Struberg
 Fix For: 1.6.1

 Attachments: OWB-1081.patch


 if Reception.IF_EXISTS is used, observers with inactive contexts should be 
 ignored completely. currently info INFO_0010 gets logged.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OWB-1081) check Reception.IF_EXISTS in case of an inactive context

[Gerhard Petracek (JIRA)]

Gerhard Petracek created OWB-1081:
-

 Summary: check Reception.IF_EXISTS in case of an inactive context
 Key: OWB-1081
 URL: https://issues.apache.org/jira/browse/OWB-1081
 Project: OpenWebBeans
  Issue Type: Improvement
  Components: Events
Affects Versions: 1.6.0
Reporter: Gerhard Petracek
Assignee: Mark Struberg
 Fix For: 1.6.1


if Reception.IF_EXISTS is used, observers with inactive contexts should be 
ignored completely. currently info INFO_0010 gets logged.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OWB-1081) check Reception.IF_EXISTS in case of an inactive context

[Gerhard Petracek (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OWB-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gerhard Petracek updated OWB-1081:
--
Attachment: OWB-1081.patch

 check Reception.IF_EXISTS in case of an inactive context
 

 Key: OWB-1081
 URL: https://issues.apache.org/jira/browse/OWB-1081
 Project: OpenWebBeans
  Issue Type: Improvement
  Components: Events
Affects Versions: 1.6.0
Reporter: Gerhard Petracek
Assignee: Mark Struberg
 Fix For: 1.6.1

 Attachments: OWB-1081.patch


 if Reception.IF_EXISTS is used, observers with inactive contexts should be 
 ignored completely. currently info INFO_0010 gets logged.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Release Apache OpenWebBeans-1.6.0

[Gerhard Petracek]

i've upgraded several projects to v1.6.0 (e.g. [1] and [2]) and all tests
look fine.
- +1

regards,
gerhard

[1] https://github.com/CDIatWork/IdeaFork
[2]
https://git-wip-us.apache.org/repos/asf/deltaspike/repo?p=deltaspike.git;a=summary



2015-06-01 17:29 GMT+02:00 Mark Struberg strub...@yahoo.de:

 Hi!

 I’d like to call a VOTE on Apache OpenWebBeans-1.6.0.

 The staging repository is here

 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1013/

 The source repo is available here

 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1013/org/apache/openwebbeans/openwebbeans/1.6.0/openwebbeans-1.6.0-source-release.zip
 sha1 is 0ba823cd2b10501e47f46f01ff76ae487bf29abd


 The binary distribution can be found at

 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1013/org/apache/openwebbeans/openwebbeans-distribution/1.6.0/openwebbeans-distribution-1.6.0-binary.zip

 For testing unzip it and use the provided shell and cmd scripts to install
 it into a tomcat7 or tomcat8.
 I will write elaborated docs for those scripts after the release is done.

 [+1] ship it
 [+0] meh, don’t care
 [-1] stop, because of ${blocker}

 The VOTE is open for 72h

 txs and LieGrue,
 strub


 PS: if you like to build it from source yourself then you also need to add
 the staging repo for xbean-4.3. The xbean release already got enough +1 but
 the 72h are not yet over…

[jira] [Updated] (OWB-654) manual lookups of beans with generics fail

[Gerhard Petracek (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OWB-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gerhard Petracek updated OWB-654:
-
Attachment: OWB-654_test.zip

 manual lookups of beans with generics fail
 --

 Key: OWB-654
 URL: https://issues.apache.org/jira/browse/OWB-654
 Project: OpenWebBeans
  Issue Type: Bug
  Components: Injection and Lookup
Affects Versions: 1.1.3
Reporter: Gerhard Petracek
Assignee: Mark Struberg
 Fix For: 1.6.0

 Attachments: OWB-654_test.zip


 the type-check it too strict right now.
 e.g. for:
 public interface CustomBeanT
 {
   //...
 }
 public class CustomBeanImpl implements CustomBeanString
 {
   //...
 }
 the manual lookup by type with CustomBean.class fails, but it works 
 correctly e.g. in case of:
 public class CustomBeanImpl implements CustomBean
 {
   //...
 }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Reopened] (OWB-654) manual lookups of beans with generics fail

[Gerhard Petracek (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OWB-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gerhard Petracek reopened OWB-654:
--
  Assignee: Mark Struberg  (was: Gerhard Petracek)

 manual lookups of beans with generics fail
 --

 Key: OWB-654
 URL: https://issues.apache.org/jira/browse/OWB-654
 Project: OpenWebBeans
  Issue Type: Bug
  Components: Injection and Lookup
Affects Versions: 1.1.3
Reporter: Gerhard Petracek
Assignee: Mark Struberg
 Fix For: 1.6.0


 the type-check it too strict right now.
 e.g. for:
 public interface CustomBeanT
 {
   //...
 }
 public class CustomBeanImpl implements CustomBeanString
 {
   //...
 }
 the manual lookup by type with CustomBean.class fails, but it works 
 correctly e.g. in case of:
 public class CustomBeanImpl implements CustomBean
 {
   //...
 }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OWB-654) manual lookups of beans with generics fail

[Gerhard Petracek (JIRA)]

[ 
https://issues.apache.org/jira/browse/OWB-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14563477#comment-14563477
 ] 

Gerhard Petracek commented on OWB-654:
--

please have a look at the test and compare it with: mvn clean install -PWeld

 manual lookups of beans with generics fail
 --

 Key: OWB-654
 URL: https://issues.apache.org/jira/browse/OWB-654
 Project: OpenWebBeans
  Issue Type: Bug
  Components: Injection and Lookup
Affects Versions: 1.1.3
Reporter: Gerhard Petracek
Assignee: Mark Struberg
 Fix For: 1.6.0

 Attachments: OWB-654_test.zip


 the type-check it too strict right now.
 e.g. for:
 public interface CustomBeanT
 {
   //...
 }
 public class CustomBeanImpl implements CustomBeanString
 {
   //...
 }
 the manual lookup by type with CustomBean.class fails, but it works 
 correctly e.g. in case of:
 public class CustomBeanImpl implements CustomBean
 {
   //...
 }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Release Apache OpenWebBeans-1.2.8

[Gerhard Petracek]

i've upgraded several projects to v1.2.8 (e.g. [1] and [2]) and all tests
look fine.
- +1

regards,
gerhard

[1] https://github.com/CDIatWork/IdeaFork
[2]
https://git-wip-us.apache.org/repos/asf/deltaspike/repo?p=deltaspike.git;a=summary



2015-04-22 15:37 GMT+02:00 Mark Struberg strub...@yahoo.de:

 I’d like to call a VOTE for releasing Apache OpenWebBeans-1.2.8

 This is a maintenance release of our 1.2.x branch which targsts JSR-299
 (CDI-1.0).

 The release notes:

 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310844version=12327470


 The staging repository:

 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1012/

 The sources release:

 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1012/org/apache/openwebbeans/openwebbeans/1.2.8/openwebbeans-1.2.8-source-release.zip

 The SVN tag (r1675359):
 https://svn.apache.org/repos/asf/openwebbeans/tags/openwebbeans-1.2.8/


 The binary package:

 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1012/org/apache/openwebbeans/openwebbeans-distribution/1.2.8/openwebbeans-distribution-1.2.8-binary.zip


 My Key can be found here
 https://svn.apache.org/repos/asf/openwebbeans/trunk/KEYS


 The VOTE will be open for 72 hours.
 [+1] approve
 [+0] meh, don’t care
 [-1] stop, I’ve found a ${fish} in there


 txs and LieGrue,
 your OpenWebBeans team

Re: a new OWB-1.2.x release?

[Gerhard Petracek]

+1

regards,
gerhard



2015-04-22 14:03 GMT+02:00 Thomas Andraschko andraschko.tho...@gmail.com:

 +1

 2015-04-22 14:01 GMT+02:00 Mark Struberg strub...@yahoo.de:

  Hi folks!
 
  We got a few requests to ship a new 1.2.x release.
  If there is no objection then I gonna start with the release process this
  afternoon.
 
  LieGrue,
  strub

Re: [VOTE] take 2 - Release Apache OpenWebBeans-1.5.0

[Gerhard Petracek]

+1

regards,
gerhard



2015-04-15 21:57 GMT+02:00 Mark Struberg strub...@yahoo.de:

 Hi!

 Another round of release bingo ;)

 It’s a great pleasure - again :) - to call a second VOTE for releasing
 Apache OpenWebBeans-1.5.0.
 OWB-1.5.x is the first version to support CDI-1.2  which is a maintenance
 version of the CDI-1.1 JSR-346 specification.

 The staging repository can be found here:

 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1011/

 The Release Notes can be found in the file readme/README.txt and online
 under:

 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310844version=12328661

 The SVN source TAG is (1673937):
 https://svn.apache.org/repos/asf/openwebbeans/tags/openwebbeans-1.5.0/

 The source release can be found here:

 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1011/org/apache/openwebbeans/openwebbeans/1.5.0/openwebbeans-1.5.0-source-release.zip
 sha1: 3fd0ba83a26cf8e36e8288930950985dfdb95c9a

 The binary release is here:

 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1011/org/apache/openwebbeans/openwebbeans-distribution/1.5.0/openwebbeans-distribution-1.5.0-binary.zip
 sha1: 7dbc18074c6216b3502a485d2cba7c686f455ac8

 My Key can be found here
 https://svn.apache.org/repos/asf/openwebbeans/tags/openwebbeans-1.5.0/KEYS


 The VOTE will be open for 72 hours.
 [+1] approve
 [+0] meh, don’t care
 [-1] stop, I’ve found a ${fish} in there


 txs and LieGrue,
 your OpenWebBeans team

[jira] [Reopened] (OWB-798) expensive check in EventUtil#checkEventBindings

[Gerhard Petracek (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OWB-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gerhard Petracek reopened OWB-798:
--

the check is still in place (and slow)

 expensive check in EventUtil#checkEventBindings
 ---

 Key: OWB-798
 URL: https://issues.apache.org/jira/browse/OWB-798
 Project: OpenWebBeans
  Issue Type: Improvement
  Components: Core, TCK
Affects Versions: 1.1.8
Reporter: Gerhard Petracek
Assignee: Gerhard Petracek
 Fix For: 1.5.0


 #checkEventBindings needs to do a check for the tck.
 however, we can do the same check (once) during bootstrapping before adding 
 an observer.
 reason why we don't need this runtime check here:
 if an invalid event (with an invalid qualifier) is used in a dyn. #fire, we 
 can ignore the invalid literal-instance because there is no corresponding 
 observer (qualifiers of the observers would be checked during bootstrapping 
 - the startup would fail, if there is such an invalid observer).
 - we just need the qualifier-check during bootstrapping and a workaround 
 that this (broken) tck-test still passes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OWB-798) expensive check in EventUtil#checkEventBindings

[Gerhard Petracek (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OWB-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gerhard Petracek updated OWB-798:
-
Fix Version/s: (was: 1.5.0)
   1.5.1

 expensive check in EventUtil#checkEventBindings
 ---

 Key: OWB-798
 URL: https://issues.apache.org/jira/browse/OWB-798
 Project: OpenWebBeans
  Issue Type: Improvement
  Components: Core, TCK
Affects Versions: 1.1.8
Reporter: Gerhard Petracek
Assignee: Gerhard Petracek
 Fix For: 1.5.1


 #checkEventBindings needs to do a check for the tck.
 however, we can do the same check (once) during bootstrapping before adding 
 an observer.
 reason why we don't need this runtime check here:
 if an invalid event (with an invalid qualifier) is used in a dyn. #fire, we 
 can ignore the invalid literal-instance because there is no corresponding 
 observer (qualifiers of the observers would be checked during bootstrapping 
 - the startup would fail, if there is such an invalid observer).
 - we just need the qualifier-check during bootstrapping and a workaround 
 that this (broken) tck-test still passes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Release Apache OpenWebBeans-1.5.0

[Gerhard Petracek]

i did further tests and the issue isn't specific to jetty.
- +1 for fixing the issue before releasing v1.5.0.

regards,
gerhard



2015-04-13 10:16 GMT+02:00 Thomas Andraschko andraschko.tho...@gmail.com:

 I get following error when starting with trunk (i think there are
 currently no changes?) and mvn jetty plugin:

 SCHWERWIEGEND: org.eclipse.jetty.server.Request cannot be cast to
 org.apache.webbeans.context.ConversationContext
 java.lang.ClassCastException: org.eclipse.jetty.server.Request cannot be
 cast to org.apache.webbeans.context.ConversationContext
 at
 org.apache.webbeans.web.context.WebContextsService.startContext(WebContextsService.java:305)
 at
 org.apache.webbeans.context.ContextFactory.initConversationContext(ContextFactory.java:170)
 at
 org.apache.webbeans.jsf.WebBeansPhaseListener.beforePhase(WebBeansPhaseListener.java:122)
 at
 org.apache.myfaces.lifecycle.PhaseListenerManager.informPhaseListenersBefore(PhaseListenerManager.java:77)

 so -1 from my side - it's a blocker for me as our dev env is completely
 based on jetty



 2015-04-13 9:54 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com:

 +1


 Romain Manni-Bucau
 @rmannibucau https://twitter.com/rmannibucau |  Blog
 http://rmannibucau.wordpress.com | Github
 https://github.com/rmannibucau | LinkedIn
 https://www.linkedin.com/in/rmannibucau | Tomitriber
 http://www.tomitribe.com

 2015-04-13 9:28 GMT+02:00 Mark Struberg strub...@yahoo.de:

 Hi!

 It’s a great pleasure to call a VOTE for releasing Apache
 OpenWebBeans-1.5.0.
 OWB-1.5.x is the first version to support CDI-1.2  which is a
 maintenance version of the CDI-1.1 JSR-346 specification.

 The staging repository can be found here:

 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1010/

 The Release Notes can be found in the file readme/README.txt and online
 under:

 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310844version=12328661

 The SVN source TAG is (r1673124):
 https://svn.apache.org/repos/asf/openwebbeans/tags/openwebbeans-1.5.0/

 The source release can be found here:

 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1010/org/apache/openwebbeans/openwebbeans/1.5.0/openwebbeans-1.5.0-source-release.zip
 sha1: a129d7df62d44c0ce5f7cbdc72b000396d91cb01

 The binary release is here:

 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1010/org/apache/openwebbeans/openwebbeans-distribution/1.5.0/openwebbeans-distribution-1.5.0-binary.zip
 sha1: 78d22c788ffcdfa82ca219bf433e37bf7abb3397

 My Key can be found here

 https://svn.apache.org/repos/asf/openwebbeans/tags/openwebbeans-1.5.0/KEYS


 The VOTE will be open for 72 hours.
 [+1] approve
 [+0] meh, don’t care
 [-1] stop, I’ve found a ${fish} in there


 txs and LieGrue,
 your OpenWebBeans team

Re: [VOTE] Release Apache OpenWebBeans-1.5.0

[Gerhard Petracek]

i've upgraded several projects to v1.5.0 (e.g. [1] and [2]) and all tests
look fine.
- +1

regards,
gerhard

[1] https://github.com/CDIatWork/IdeaFork
[2]
https://git-wip-us.apache.org/repos/asf/deltaspike/repo?p=deltaspike.git;a=summary



2015-04-13 23:57 GMT+02:00 Mark Struberg strub...@yahoo.de:

 Txs for testing Harald!

 We will definitly ship a 1.5.1 pretty soon :)

 LieGrue,
 strub



  Am 13.04.2015 um 19:20 schrieb Harald Wellmann hwellmann...@gmail.com:
 
  +1 (non-binding)
 
  This looks  good enough after running some tests with Pax CDI. We've
 been waiting quite some time for a first release supporting CDI 1.1, so I'd
 rather go forward and fix any open issues in 1.5.1.
 
  Regards,
  Harald
 
  2015-04-13 15:25 GMT+02:00 Howard W. Smith, Jr. smithh032...@gmail.com
 :
  Okay, now I know. Thanks Romain! :)
 
  On Mon, Apr 13, 2015 at 9:22 AM, Romain Manni-Bucau 
 rmannibu...@gmail.com wrote:
  @Howard: would have been cool ;). This is not intended to work so
 easily. TomEE 2 does it.
 
 
  Romain Manni-Bucau
  @rmannibucau |  Blog | Github | LinkedIn | Tomitriber
 
  2015-04-13 15:17 GMT+02:00 Howard W. Smith, Jr. smithh032...@gmail.com
 :
  I replaced openwebbeans 1.2.6 JARs with openwebbeans 1.5.0 JARs in
 tomee+ (1.7.1) lib folder, started tomee+ (via NetBeans 8) and tomee+
 failed to start because of the following:
 
  INFO:
 
  Apr 13, 2015 9:09:48 AM org.apache.openejb.OpenEJB$Instance init
  INFO: openejb.home = C:\apache-tomee-plus-1.7.1
  Apr 13, 2015 9:09:48 AM org.apache.openejb.OpenEJB$Instance init
  INFO: openejb.base = C:\apache-tomee-plus-1.7.1
  Apr 13, 2015 9:09:48 AM org.apache.openejb.cdi.CdiBuilder initializeOWB
  INFO: Created new singletonService
 org.apache.openejb.cdi.ThreadSingletonServiceImpl@e50a6f6
  java.lang.NoClassDefFoundError:
 javax/enterprise/inject/spi/DefinitionException
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
at
 java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at
 org.apache.openejb.cdi.CdiBuilder.initializeOWB(CdiBuilder.java:67)
at org.apache.openejb.OpenEJB$Instance.init(OpenEJB.java:120)
at org.apache.openejb.OpenEJB.init(OpenEJB.java:298)
at
 org.apache.tomee.catalina.TomcatLoader.initialize(TomcatLoader.java:253)
at
 org.apache.tomee.catalina.ServerListener.install(ServerListener.java:168)
at
 org.apache.tomee.catalina.ServerListener.lifecycleEvent(ServerListener.java:55)
at
 org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at
 org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
at
 org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402)
at
 org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:110)
at org.apache.catalina.startup.Catalina.load(Catalina.java:638)
at org.apache.catalina.startup.Catalina.load(Catalina.java:663)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:280)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:454)
  Caused by: java.lang.ClassNotFoundException:
 javax.enterprise.inject.spi.DefinitionException
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 29 more
 
 
  On Mon, Apr 13, 2015 at 3:28 AM, Mark Struberg strub...@yahoo.de
 wrote:
  Hi!
 
  It’s a great pleasure to call a VOTE for releasing Apache
 OpenWebBeans-1.5.0.
  OWB-1.5.x is the first version to support CDI-1.2  which is a
 maintenance version of the CDI-1.1 JSR-346 specification.
 
  The staging repository can be found here:
 
 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1010/
 
  The Release Notes can be found in the file readme/README.txt and online
 under:
 
 

Re: preparing to release owb-1.5.0

[Gerhard Petracek]

+1

regards,
gerhard



2015-04-09 19:40 GMT+02:00 Mark Struberg strub...@yahoo.de:

 Hi folks!

 FINALLY I like to get OWB-1.5.0 out of the door. We now pass the TCK for
 JavaSE as well as the web-profile TCK (within TomEE).

 Time to get some real feedback apart from all the people who use their own
 private internal releases already since months  ;)

 LieGrue,
 strub