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

+1 it makes life easier for all On Fri, May 3, 2019, 07:31 Mark Struberg wrote: > hi folks! > > Do we want to move OWB core to GIT? > > wdyt? > > I'd be +1 > > LieGrue, > strub > >

Re: Consistent results for CDI.current().getBeanManager()

the TCCL accordingly? > >> > >> That way you will get perfect isolation. > >> > >> LieGrue, > >> strub > >> > >> > >> > Am 09.04.2018 um 14:10 schrieb Romain Manni-Bucau < > rmannibu...@gmail.com > >> >

Re: Consistent results for CDI.current().getBeanManager()

m > >: > > > > 2018-04-09 14:07 GMT+02:00 John D. Ament <johndam...@apache.org>: > > > >> On Mon, Apr 9, 2018 at 7:55 AM Romain Manni-Bucau < > rmannibu...@gmail.com> > >> wrote: > >> > >>> 2018-04-09 13:3

Re: Consistent results for CDI.current().getBeanManager()

ain Manni-Bucau <rmannibu...@gmail.com > >: > > > > Le 9 avr. 2018 02:33, "John D. Ament" <johndam...@apache.org> a écrit : > > > > On Wed, Mar 7, 2018 at 1:33 AM Romain Manni-Bucau <rmannibu...@gmail.com > > > > wrote: > >

Re: Consistent results for CDI.current().getBeanManager()

ld be to create an additional constructor in WebBeansConfigurationListener that took the proper WebBeansContext to look up, instead of relying on the singleton service to look one up. > > Le 7 mars 2018 03:27, "John D. Ament" <johndam...@apache.org> a écrit : >

Re: Consistent results for CDI.current().getBeanManager()

gt; > you dont have the right tccl in different places - which has impacts as > > well. > > > > The wrapper instance is not that important here, only the delegate one > > > > > > Le 5 mars 2018 02:19, "John D. Ament" <johndam...@apache.org&

Consistent results for CDI.current().getBeanManager()

Hi So I'm noticing when CDI.current().getBeanManager() is called, it returns a new InjectableBeanManager instance. I have a custom OWBListener ( https://github.com/hammock-project/hammock/blob/master/bootstrap-owb2/src/main/java/ws/ament/hammock/bootstrap/owb/OWBListener.java) which handles the

Re: Meecrowave java 9 support

If you explicitly add the dependencies that Ravi's mentioning, you'll get the correct output without --add-modules. However, it is a hard dependency for CXF to include these dependencies. Some of their core feature work is based on JAX-WS features, so there's no way to avoid the dependency. On

Re: Injecting Array types as fields

dIn <https://www.linkedin.com/in/rmannibucau> > > 2017-12-18 13:01 GMT+01:00 John D. Ament <johndam...@apache.org>: > > > That's good that this works. However, I wonder if my issue is specific to > > 3rd Party Bean creation? Same problem seems to be on both OWB a

Re: Injecting Array types as fields

t; https://github.com/rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> > > 2017-12-18 9:15 GMT+01:00 Mark Struberg <strub...@yahoo.de.invalid>: > > > I think it should work. > > > > Could you please create a ticket? > > > > txs and LieG

Injecting Array types as fields

MP Config is adding arrays as a valid type for config properties. In doing so, without making any changes to Geronimo Config I get this failure (not what I'm expecting, I'm expecting no valid beans at this point): arquillianBeforeClass(org.eclipse.microprofile.config.tck.ClassConverterTest) Time

Re: Different BeanManagers in use

nibucau <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> > >

Different BeanManagers in use

Hi, I'm troubleshooting an issue in Hammock where when using OWB 2.0.1 + Tomcat 9 M26, the results of CDI.current().getBeanManager() give back different BeanManager instances. In fact, calling WebBeansContext.currentInstance() is returning a different instance on each invocation in separate

Re: Odd behavior in InjectionPointProducer

>> > >>>>>> > >>>>>> Von: Mark Struberg <strub...@yahoo.de.INVALID> > >>>>>> Gesendet: Montag, 11. September 2017 09:04:41 > >>>>>> An: openwebbeans-dev > >>>>>&

[jira] [Created] (OWB-1216) InjectionPoint.getType() returns wrong type for produced beans

John D. Ament created OWB-1216: -- Summary: InjectionPoint.getType() returns wrong type for produced beans Key: OWB-1216 URL: https://issues.apache.org/jira/browse/OWB-1216 Project: OpenWebBeans

Re: Odd behavior in InjectionPointProducer

OWB we introduced an own method getReturnType() in OwbBean. > > This get's evaluated and cached based on a few criteria. > > Most of the time it simply uses the getBeanClass() type. > > > > I'll have to dig deeper into your sample to understand what you wanted to > > do with it. &g

Re: Odd behavior in InjectionPointProducer

not be used for type safe resolution (we actually > had a > >>>>> discussion about this on the EG list as I had the opposite belief). > >>>> > >>>> Yes, there was a discussion which never got finished... > >>>> > >>>> We

Re: Odd behavior in InjectionPointProducer

est and then use: > startcontainer(ClassX.class, ClassY.class, ...); > > > txs and LieGrue, > strub > > > > > LieGrue, > strub > > > Am 10.09.2017 um 22:54 schrieb John D. Ament <johndam...@apache.org>: > > > > Hi, > > > > I'm

Re: [VOTE] Release Apache OpenWebBeans-2.0.1

Looks good to me, ship it +1 Tested with Hammock + Geronimo Config, both passing fine at this point. On Tue, Aug 29, 2017 at 5:17 AM Mark Struberg wrote: > Hi folks! > > I did run the necessary steps to ship OWB-2.0.1 from trunk, which is our > CDI-2.0 implementation. > We

Re: [DISCUSS] Release OWB-2.0.1 ?

Ok, both tickets are in. On Wed, Aug 16, 2017 at 12:17 AM Mark Struberg <strub...@yahoo.de.invalid> wrote: > That would be really great if you could create Tickets and attach patches, > txs John > > LieGrue, > strub > > > > Am 16.08.2017 um 01:25 schrieb Joh

[jira] [Created] (OWB-1212) OWB not honoring implicit scanning flag

John D. Ament created OWB-1212: -- Summary: OWB not honoring implicit scanning flag Key: OWB-1212 URL: https://issues.apache.org/jira/browse/OWB-1212 Project: OpenWebBeans Issue Type: Bug

[jira] [Created] (OWB-1211) OWB is not firing BeforeDestroyed on contexts

John D. Ament created OWB-1211: -- Summary: OWB is not firing BeforeDestroyed on contexts Key: OWB-1211 URL: https://issues.apache.org/jira/browse/OWB-1211 Project: OpenWebBeans Issue Type: Bug

Re: [DISCUSS] Release OWB-2.0.1 ?

be a bit more work to be left still. > > > > I'd then suggest to go on with the immanent features and release > OWB-2.0.1 > > pretty soon while targetting 2.0.2 for the SE work. > > > > txs and LieGrue, > > strub > > > > > > > Am 15.08.2

Re: [DISCUSS] Release OWB-2.0.1 ?

Mark, SE support is still a long ways from being done. Most of the issues are resolved, all of the remaining problems are related to OWB not honoring when the container's been shutdown. The good news, by removing the automatic starting of request context and properly shutting down app context

Re: Update on SE support

On Mon, Aug 14, 2017 at 8:19 AM Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > 2017-08-14 13:50 GMT+02:00 John D. Ament <johndam...@apache.org>: > > > On Mon, Aug 14, 2017 at 1:03 AM Romain Manni-Bucau < > rmannibu...@gmail.com> > > wrote: > >

Re: Update on SE support

On Mon, Aug 14, 2017 at 1:03 AM Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > Le 14 août 2017 04:31, "John D. Ament" <john.d.am...@gmail.com> a écrit : > > Hey guys > > Good news on the SE support front. Looks like there were two features just >

Re: Bean Validation for Meecrowave JSON-B/JAX-RS

JAX-RS Defines Bean Val integration, if you add @Valid to resource methods (params and return value) they should get validated on the way in or the way out. On Mon, Aug 7, 2017 at 8:16 AM Mark Struberg wrote: > Hi! > > Not sure whether I should post this in Johnzon,

[jira] [Commented] (OWB-1208) Unable to use Unmanaged with mixed CDI 2.0/1.1 bean archives

[ https://issues.apache.org/jira/browse/OWB-1208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116393#comment-16116393 ] John D. Ament commented on OWB-1208: The CXFCdiServlet is just an example. I actually had been using

[jira] [Created] (OWB-1208) Unable to use Unmanaged with mixed CDI 2.0/1.1 bean archives

John D. Ament created OWB-1208: -- Summary: Unable to use Unmanaged with mixed CDI 2.0/1.1 bean archives Key: OWB-1208 URL: https://issues.apache.org/jira/browse/OWB-1208 Project: OpenWebBeans

[jira] [Created] (OWB-1207) Inconsistent behavior of the instance behind CDI.current()

John D. Ament created OWB-1207: -- Summary: Inconsistent behavior of the instance behind CDI.current() Key: OWB-1207 URL: https://issues.apache.org/jira/browse/OWB-1207 Project: OpenWebBeans

Re: Why does CDI.current() include a Default Qualifier?

90% sure spec is not that closed on that > point but if you dont have an implicit default, direct type lookup doesnt > work but if another qualifier is set the *implicit* one (not default, only > default when implicit) should be stripped IMHO. > > Le 6 août 2017 14:46, "John D.

Re: Why does CDI.current() include a Default Qualifier?

bean, not a third party bean. On Sun, Aug 6, 2017 at 8:07 AM John D. Ament <johndam...@apache.org> wrote: > Hey guys > > Before I create a ticket, I wanted to understand from your POV. I'm not > sure if it's a spec issue. > > I noticed in OWB when I do CDI.cu

How to handle javax.enterprise.inject.scan.implicit

There's an open CDI spec ticket https://issues.jboss.org/browse/CDI-632 But it seems that this property isn't handled presently in OWB. Its basically whether to turn on whether JARs without any beans.xml should be CDI archives. It probably makes sense to handle this property in

[jira] [Updated] (OWB-1206) Enable CDI 2.0 TCK SE Tests

[ https://issues.apache.org/jira/browse/OWB-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated OWB-1206: --- Attachment: OWB_1206_v2.patch Here's a better patch, created an owb-se-tck package to run. It's a bit

Re: XBean & ShrinkWrap archives

:29 PM John D. Ament <johndam...@apache.org> wrote: > I have a local test working. > > It's not going to work too cleanly, but its doable. > > If you look at this test for instance: > https://github.com/cdi-spec/cdi-tck/blob/2.0.0.Final/impl/src/main/java/org/jboss/cdi/tck/te

Re: XBean & ShrinkWrap archives

from the tomcat7-m-p to cargo-maven2-plugin. > I can help and take a look into those SE parts affter all that is running > again. > > LieGrue, > strub > > > > Am 31.07.2017 um 00:11 schrieb John D. Ament <johndam...@apache.org>: > > > > Agreed, when I first lo

Re: XBean & ShrinkWrap archives

webbeans-se normal tests. > > This is good enough and doesnt require arquillian hacks. > > > > Le 30 juil. 2017 23:56, "John D. Ament" <johndam...@apache.org> a écrit > : > > > > On Sun, Jul 30, 2017 at 4:36 PM Romain Manni-Bucau < > rmannibu.

Re: XBean & ShrinkWrap archives

re. > > Le 30 juil. 2017 22:29, "John D. Ament" <johndam...@apache.org> a écrit : > > > Mark, > > > > Sure, its this TCK test in particular: > > https://github.com/cdi-spec/cdi-tck/blob/2.0.0.Final/impl/ > > src/main/java/org/jboss/cdi/tck/

Re: XBean & ShrinkWrap archives

t; Can you share your setup? Probably might help a bit later. > > LieGrue, > strub > > > Am 30.07.2017 um 20:23 schrieb John D. Ament <johndam...@apache.org>: > > > > Hi All, > > > > So I've been trying to dig into why OWB's CDI TCK tests are failing. I &g

XBean & ShrinkWrap archives

Hi All, So I've been trying to dig into why OWB's CDI TCK tests are failing. I have it down to 22 failures that should mostly be passing (or are failing in the wrong spot). The most common failure is because of this: Caused by: java.lang.UnsupportedOperationException: unsupported archive type:

[jira] [Commented] (OWB-1206) Enable CDI 2.0 TCK SE Tests

[ https://issues.apache.org/jira/browse/OWB-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16106520#comment-16106520 ] John D. Ament commented on OWB-1206: Well, the reason being that SE and Arquillian should work together

[jira] [Commented] (OWB-1206) Enable CDI 2.0 TCK SE Tests

[ https://issues.apache.org/jira/browse/OWB-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16106516#comment-16106516 ] John D. Ament commented on OWB-1206: Many of the errors seem to originate from xbean, and it's odd

[jira] [Updated] (OWB-1206) Enable CDI 2.0 TCK SE Tests

[ https://issues.apache.org/jira/browse/OWB-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated OWB-1206: --- Attachment: OWB_1206.patch The following tests fail after making the attached changes {code

[jira] [Created] (OWB-1206) Enable CDI 2.0 TCK SE Tests

John D. Ament created OWB-1206: -- Summary: Enable CDI 2.0 TCK SE Tests Key: OWB-1206 URL: https://issues.apache.org/jira/browse/OWB-1206 Project: OpenWebBeans Issue Type: Improvement

[jira] [Commented] (OWB-1191) implement api for manual request-context handling

[ https://issues.apache.org/jira/browse/OWB-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16106496#comment-16106496 ] John D. Ament commented on OWB-1191: Oh , I see. OWB's ignoring the SE tests.. {code

[jira] [Updated] (OWB-1191) implement api for manual request-context handling

[ https://issues.apache.org/jira/browse/OWB-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated OWB-1191: --- Attachment: OWB_1191.patch Here's a patch, untested, but looks logically right. I'm not sure yet how

Re: do a 2.0.1 release?

Hi, Looks like there's still a couple of issues open in 2.0.1 [1]. I'm surprised there's no testing for [2], I'm guessing it's ignored in the TCK? If you can wait until tomorrow I should be able to get a patch together for it, if not go for it. [1]:

Re: OWB 2 not firing ProcessAnnotatedType for all bean classes

@gmail.com > >: > > > > Cause the scanning by itself is undefined, you can not scan skip not bean > > types and be spec compliant. > > > > > > Le 21 juil. 2017 21:26, "John D. Ament" <johndam...@apache.org> a écrit > : > > > >>

Re: Interceptor discovery

ibu...@gmail.com> wrote: > Misses @Dependent yes. > > Le 21 juil. 2017 19:35, "John D. Ament" <johndam...@apache.org> a écrit : > > I have an interceptor defined as: > > @Interceptor > @LoggedIn > @Priority(Interceptor.Priority.APPLICATION + 100) > pu

Re: OWB 2 not firing ProcessAnnotatedType for all bean classes

teresting edge case. For me it should be ignored until you make it > scanned using @Dependent or so. But fear it is quite undefined or > "interpretable" > > Le 21 juil. 2017 21:10, "John D. Ament" <johndam...@apache.org> a écrit : > > > I

OWB 2 not firing ProcessAnnotatedType for all bean classes

I do something really lazy, I have an extension that has this method on it: public void findEntities(@Observes @WithAnnotations(Entity.class) ProcessAnnotatedType pat) which just looks for entity classes. They're not going to be CDI beans, but they are annotated types. Per the spec,

Re: ProcessBean being called regardless of type

> >> <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 > >>

Interceptor discovery

I have an interceptor defined as: @Interceptor @LoggedIn @Priority(Interceptor.Priority.APPLICATION + 100) public class LoggedInInterceptor { and a beans.xml with This interceptor isn't being discovered. It is discovered when beans.xml is an empty file. This same interceptor is discovered

ProcessBean being called regardless of type

Hi, I have a portable extension that registers an observer method like so: public void findSpecialBeans(@Observes ProcessBean processBean) In Weld, this gets invoked once in my test application, only for beans of type SpecialBean. In OWB 2, this is getting invoked once for that same bean, but

[jira] [Resolved] (OWB-1200) OWB 2 skips producer methods defined in annotated bean archives in SE

[ https://issues.apache.org/jira/browse/OWB-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament resolved OWB-1200. Resolution: Invalid Non issue, see OWB-1201 for more details. > OWB 2 skips producer methods defi

[jira] [Commented] (OWB-1199) CDISeScannerService.autoScanning should be true by default

[ https://issues.apache.org/jira/browse/OWB-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088926#comment-16088926 ] John D. Ament commented on OWB-1199: LGTM thanks. Just want to make sure we don't end up

[jira] [Comment Edited] (OWB-1201) OWB Not discovering JARs in a Capsule packaged JAR

[ https://issues.apache.org/jira/browse/OWB-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088925#comment-16088925 ] John D. Ament edited comment on OWB-1201 at 7/16/17 1:09 PM: - I did just give

[jira] [Commented] (OWB-1201) OWB Not discovering JARs in a Capsule packaged JAR

[ https://issues.apache.org/jira/browse/OWB-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088925#comment-16088925 ] John D. Ament commented on OWB-1201: I did just give it a shot, if I use the old style bootstrap, e.g

[jira] [Commented] (OWB-1200) OWB 2 skips producer methods defined in annotated bean archives in SE

[ https://issues.apache.org/jira/browse/OWB-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1603#comment-1603 ] John D. Ament commented on OWB-1200: Agreed, this wouldn't work in an implicit bean archive. However

[jira] [Commented] (OWB-1201) OWB Not discovering JARs in a Capsule packaged JAR

[ https://issues.apache.org/jira/browse/OWB-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1602#comment-1602 ] John D. Ament commented on OWB-1201: Hi, The exact same sample works correctly w/ OWB 1.7.3. I

[jira] [Created] (OWB-1201) OWB Not discovering JARs in a Capsule packaged JAR

John D. Ament created OWB-1201: -- Summary: OWB Not discovering JARs in a Capsule packaged JAR Key: OWB-1201 URL: https://issues.apache.org/jira/browse/OWB-1201 Project: OpenWebBeans Issue Type

[jira] [Created] (OWB-1200) OWB 2 skips producer methods defined in annotated bean archives in SE

John D. Ament created OWB-1200: -- Summary: OWB 2 skips producer methods defined in annotated bean archives in SE Key: OWB-1200 URL: https://issues.apache.org/jira/browse/OWB-1200 Project: OpenWebBeans

[jira] [Commented] (OWB-1199) CDISeScannerService.autoScanning should be true by default

[ https://issues.apache.org/jira/browse/OWB-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088624#comment-16088624 ] John D. Ament commented on OWB-1199: Any reason you skipped the test change

[jira] [Updated] (OWB-1199) CDISeScannerService.autoScanning should be true by default

[ https://issues.apache.org/jira/browse/OWB-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated OWB-1199: --- Attachment: OWB_1199.patch Attached is a more complete patch with tests

[jira] [Created] (OWB-1199) CDISeScannerService.autoScanning should be true by default

John D. Ament created OWB-1199: -- Summary: CDISeScannerService.autoScanning should be true by default Key: OWB-1199 URL: https://issues.apache.org/jira/browse/OWB-1199 Project: OpenWebBeans

Re: AutoScanning off by default in SE?

itter.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://javaeefa

AutoScanning off by default in SE?

Hi, I was trying to wire in Hammock w/ OWB 2. I noticed that in CDISeScannerService autoScanning isn't set. I can't find a way to set it to true. The behavior in Weld is that this is on by default, hence why in SeContainerInitializer there's only a disableDiscovery method. John

Re: [VOTE] Release Apache OpenWebBeans-2.0.0

10, 2017 at 7:36 AM John D. Ament <johndam...@apache.org> wrote: > Hi Mark, > > I just pulled trunk and get this compilation error > > [ERROR] COMPILATION ERROR : > [INFO] - > [ERROR] > /Users/johnament/src/

Re: [VOTE] Release Apache OpenWebBeans-2.0.0

Hi Mark, I just pulled trunk and get this compilation error [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /Users/johnament/src/openwebbeans/webbeans-impl/src/main/java/org/apache/webbeans/boot/OwbSeContainerInitializer.java:[57,14]

Re: behaviour of URLClassLoader#findResources

If the same URL comes back from multiple classloaders, you may want to use a Set instead of a List to ensure uniqueness. URLs delegate uniqueness checks to the URLStreamHandler, which by default looks at the ref attribute of the URL. I do think you need to delegate up to the parent classloader

Re: OWB-2.0.0 to be released soon

:39 PM John D. Ament <johndam...@apache.org> wrote: > I had a hunch it was that, so did a dependency tree - no luck. > > https://paste.apache.org/X3c5 > > John > > > On Mon, Jun 19, 2017 at 3:22 AM Romain Manni-Bucau <rmannibu...@gmail.com> > wrote: >

Re: OWB-2.0.0 to be released soon

have/had a bug in the arquillian connector which lead to blowing >> up on NoClassDefFound. >> I need to check whether we fixed this already with another commit. >> >> The ticket is https://issues.apache.org/jira/browse/OWB-1179 >> >> LieGrue, >>

Re: OWB-2.0.0 to be released soon

t ping us. > > txs and LieGrue, > strub > > > > Am 17.06.2017 um 22:36 schrieb John D. Ament <johndam...@apache.org>: > > > > 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? &

Re: OWB-2.0.0 to be released soon

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

[jira] [Commented] (OWB-1190) implement java-se support

[ https://issues.apache.org/jira/browse/OWB-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16029241#comment-16029241 ] John D. Ament commented on OWB-1190: I started playing around with this. It seems like the right course

Re: Build failed in Jenkins: OpenWebBeans-trunk #1204

I updated the build to point to 1.8. John On Mon, May 29, 2017 at 6:53 PM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < > https://builds.apache.org/job/OpenWebBeans-trunk/1204/display/redirect?page=changes > > > > Changes: > > [struberg] OWB-1186 implement

Re: [VOTE] Release Apache Meecrowave-0.2.0

we can verify the license of the file. Romain wrote those files and > there is a proper NOTICE and LICENSE file in the jars. > > It's not perfect that we have those files in the source zip, but it is > legally perfectly fine. > > LieGrue, > strub > > > > Am 02.0

Re: [VOTE] Release Apache Meecrowave-0.2.0

um 23:00 schrieb Romain Manni-Bucau <rmannibu...@gmail.com > >: > > > > This is part of the way a few (1 or 2) tests are written. This is > intended > > for now. > > > > Le 2 janv. 2017 22:11, "John D. Ament" <johndam...@apache.org> a écrit : > &g

Re: [VOTE] Release Apache Meecrowave-0.2.0

You have two binaries in the source release: ./meecrowave-core/src/test/resources/org/superbiz/app-res/OtherEndpoint.class ./meecrowave-core/src/test/resources/org/superbiz/app-res/OtherFilter.class The allowable ASF binaries are usually graphics, not class files (which are usually compiled java

[jira] [Commented] (OWB-1164) Third Party Beans do not include Any qualifier if not included in bean impl

[ https://issues.apache.org/jira/browse/OWB-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15785470#comment-15785470 ] John D. Ament commented on OWB-1164: [~rmannibucau] I see you made some changes on top of my patch

[jira] [Updated] (OWB-1164) Third Party Beans do not include Any qualifier if not included in bean impl

[ https://issues.apache.org/jira/browse/OWB-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated OWB-1164: --- Affects Version/s: 1.7.0 > Third Party Beans do not include Any qualifier if not included in bean i

Re: Programmatic instance look up

://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-rmann

[jira] [Created] (OWB-1164) Third Party Beans do not include Any qualifier if not included in bean impl

John D. Ament created OWB-1164: -- Summary: Third Party Beans do not include Any qualifier if not included in bean impl Key: OWB-1164 URL: https://issues.apache.org/jira/browse/OWB-1164 Project

Re: Programmatic instance look up

https://github.com/rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory > <https://javaeefactory-rmannibucau.rhcloud.com> > > 2016-12-28 14:29 GMT+01:00 John D. Ament <johndam...@apache.org>: > > > Looks like you already applied a f

Re: Programmatic instance look up

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

Re: Programmatic instance look up

; > > Le 27 déc. 2016 23:29, "John D. Ament" <johndam...@apache.org> a écrit : > > > Hi, > > > > So I'm starting to run into my old friend, where instance doesn't work > the > > same in OWB and Weld. Basically anytime I use C

Programmatic instance look up

Hi, So I'm starting to run into my old friend, where instance doesn't work the same in OWB and Weld. Basically anytime I use CDI.current() to resolve a bean, it fails. The same lookup works when using BeanManager.getReference, or even the DeltaSpike utilities. My understanding is that I should

Re: Handling bootstrap for mixed SE/Servlet scenario

to work well. Let me know, I can provide a patch. John On Tue, Dec 27, 2016 at 12:27 AM John D. Ament <johndam...@apache.org> wrote: > Nevermind, I forgot about openwebbeans.properties. Mix and match for the > win. > > John > > > On Mon, Dec 26, 2016 at 11:5

Re: Handling bootstrap for mixed SE/Servlet scenario

Nevermind, I forgot about openwebbeans.properties. Mix and match for the win. John On Mon, Dec 26, 2016 at 11:55 PM John D. Ament <johndam...@apache.org> wrote: > Hi, > > So let's say I'm using Tomcat embedded and OWB. I bootstrap OWB using its > normal function, an

Handling bootstrap for mixed SE/Servlet scenario

Hi, So let's say I'm using Tomcat embedded and OWB. I bootstrap OWB using its normal function, and I have impl, web and resource on my classpath. When I ask for the ContainerLifecycle service, I get back a WebContainerLifecycle since I have web on the classpath. So I'm wondering, does it make

Re: CDI 2.0 Spec JAR

erg > <strub...@yahoo.de.invalid > > > > > wrote: > > > > > txs will apply. > > > > > > LieGrue, > > > strub > > > > > > > > > > > > > > > > > > > On Monday, 11 July 2016, 2:43, John D. Ament <johndam...

Re: CDI 2.0 Spec JAR

strub > > > > > Am 03.07.2016 um 23:01 schrieb Romain Manni-Bucau <rmannibu...@gmail.com > >: > > > > Le 3 juil. 2016 22:56, "John D. Ament" <johndam...@apache.org> a écrit : > >> > >> geronimo@ who? > > > > Dev list

Re: CDI 2.0 Spec JAR

ess 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&g

CDI 2.0 Spec JAR

Hey guys I'm looking at the current state of the Geronimo CDI 2 spec jar. I'm wondering, what version of CDI 2 is it based on currently? In addition, I'm planning to apply patches to it based on the changes in CDI 2. I notice that unlike most geronimo specs, its pretty heavy on javadocs. I

[jira] [Created] (OWB-719) @Named qualifier is not adhering to CDI spec default naming conventions

John D. Ament created OWB-719: - Summary: @Named qualifier is not adhering to CDI spec default naming conventions Key: OWB-719 URL: https://issues.apache.org/jira/browse/OWB-719 Project: OpenWebBeans