Re: CDI container performance
2014-10-21 11:57 GMT+02:00 Howard W. Smith, Jr. : > Wow, very impressive. I'm glad I'm using TomEE+ 1.7.1 (for now) and looking > forward to TomEE+ 2.x. > > Questions below, > > > >- OWB-1.5.0: 13 ms (no this is NOT a hoax, it's due to our proxy caching >[1]...) > > All with Java8. > > Currently trying to run it on other boxes to rule out some misconfiguration > > [1] For @ApplicationScoped beans our proxies resolve the contextual > instance only once. Thus you get the benefits of a Proxy (serializability, > interceptors, decorators, cycle prevention, shield against scope > differences) for the costs of (almost) native invocation (Creating > 'underTest' via new instead of the CDI bean will run the test in 8ms). > > > OWB-1.5.0 is and/or will be bundled with TomEE+ 2.x 'and' future TomEE+ > 1.7.x releases? > It is in TomEE 2 > @ApplicationScoped? interesting, I can remember you sending a > recommendation (to me via this list) about caching data in my app, and I > did that in my (CDI) @ApplicationScoped bean. Thanks Mark! :) > > > > On Tue, Oct 21, 2014 at 5:37 AM, Mark Struberg wrote: > >> Hi! >> >> Yesterday I wrote a small micro benchmark to test the performance of some >> CDI containers. The outcome was pretty stunning - but best if you run it >> yourself: >> >> https://github.com/struberg/cdi-performance >> >> >> >> $> git clone https://github.com/struberg/cdi-performance.git >> $> cd cdi-performance >> >> Just look for the output:ALL THE STUFF TOOK: xxx ms >> >> >> >> >> The default profile runs with owb-1.2.6 which is currently used in >> TomEE-1.7.1: >> >> $> mvn clean install >> >> If you have OWB trunk installed you can also try the performance of >> OWB-1.5.0-SNAPSHOT: >> $> mvn clean install -POWB15 >> >> >> There is also a profile -POWB11 for testing OpenWebBeans-1.1.x. >> $> mvn clean install -POWB11 -Dowb.version=1.1.8 >> >> >> The numbers of the Reference Implementation (RI: Weld) can be tested via >> $> mvn clean install -PWeld >> >> but take your time and let it run - no it doesn't hang ;) >> >> >> >> The version of OWB can be defined as parameter '-Dowb.version=1.2.0' and >> similar for Weld: '-Dweld.version=2.2.5.Final' if you like to test the >> latest RI version. >> >> >> Feel free to debug into it if you don't believe our sheer crazy >> performance! >> >> As a result of this performance I was able to serve FAT applications with >> BIG pages (huge JSF datatables) within under 150ms where other EE >> containers took 2 seconds++... >> >> >> >> LieGrue, >> strub >>
Re: [cdi-dev] Getting injection point from Bean#create
Do it if you want but I thought it shouldn't be used and @Inject InjectionPoint should be the clean solution. That said nothing more against so feel free to remove this restriction. Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-22 11:58 GMT+01:00 Arne Limburg : > Damn, should have made an svn up, before I started ;-) > > I reviewed your fix and I am not happy with it. Lookup of the InjectionPoint > should be possible from everywhere, where it is available (i.e. In a > Constructor of a @Dependent bean) and not only from ThirdPartyBean#create > > So, I propose that we never throw the exception but assume that it is a > lookup in that case. > > Other opinions? > > Cheers, > Arne > > Von: Romain Manni-Bucau > Datum: Samstag, 22. November 2014 11:40 > An: Arne Limburg > Betreff: Re: [cdi-dev] Getting injection point from Bean#create > > Test is passing ;). Test should be sthg like GetInjectionPoint*Test > > Le 22 nov. 2014 11:30, "Arne Limburg" a > écrit : >> >> Oh, ok, what’s its name? >> Are you already working on a fix? >> >> Von: Romain Manni-Bucau >> Datum: Samstag, 22. November 2014 11:27 >> An: Arne Limburg >> Betreff: Fwd: Re: [cdi-dev] Getting injection point from Bean#create >> >> Hi Arne >> >> I added a test yesterday for it >> >> -- Message transféré -- >> De : "Arne Limburg" >> Date : 22 nov. 2014 11:24 >> Objet : Re: [cdi-dev] Getting injection point from Bean#create >> À : "arjan tijms" >> Cc : "cdi-...@lists.jboss.org" >> >> Hi Arjan, >> >> I¹ve verified, that this is a bug in OpenWebBeans. >> I've created >> https://issues.apache.org/jira/browse/OWB-1030 >> and I¹m going to fix it. >> >> Btw.: You have to use the CreationalContext of the bean (the way OWB >> currently throws the "Inconsistent injection point stack" exception) >> >> Cheers, >> Arne >> >> >> Am 21.11.14 12:58 schrieb "arjan tijms" unter : >> >> >Hi, >> > >> >On Fri, Nov 21, 2014 at 10:31 AM, Jozef Hartinger >> >wrote: >> >> Here is my understanding of Arjan's >> >> setup: >> >> [...] >> >> >> >> This is no different from a producer method injecting InjectionPoint >> >> directly. >> > >> >That's indeed the exact setup. >> > >> >On Fri, Nov 21, 2014 at 11:34 AM, Romain Manni-Bucau >> > wrote: >> >> PS: BTW should work on OWB 1.5.0-SNAPSHOT now >> > >> >Wow, I'll look at the latest SNAPSHOT of OWB then. Thanks Romain! >> > >> >Kind regards, >> >Arjan >> > >> > >> > >> > >> >> >> >> >> >> On 11/21/2014 10:23 AM, Romain Manni-Bucau wrote: >> >>> >> >>> yes but what would mean any of the values? Not bound to any injection >> >>> it doesn't mean anything >> >>> >> >>> >> >>> Romain Manni-Bucau >> >>> @rmannibucau >> >>> http://www.tomitribe.com >> >>> http://rmannibucau.wordpress.com >> >>> https://github.com/rmannibucau >> >>> >> >>> >> >>> 2014-11-21 10:19 GMT+01:00 Jozef Hartinger : >> >>>> >> >>>> It means "give me an instance of type InjectionPoint and @Default >> >>>> qualifier". In default setup this should be served by the built-in >> >>>> Bean". >> >>>> >> >>>> >> >>>> On 11/21/2014 10:12 AM, Romain Manni-Bucau wrote: >> >>>>> >> >>>>> @Jozef: InjectionPoint ip = getBean(InjectionPoint.class); doesn't >> >>>>> mean anything in the absolute. So why should it be allowed? >> >>>>> >> >>>>> >> >>>>> Romain Manni-Bucau >> >>>>> @rmannibucau >> >>>>> http://www.tomitribe.com >> >>>>> http://rmannibucau.wordpress.com >> >>>>> https://github.com/rmannibucau >> >>>>> >> >>>>> >> >>>>> 2014-11-21 9:57 GMT+01:00 Jozef Hartinger : >> >>>>>> >> >>>>>> The workaround is very ugly. Instead of going that path OWB should >> >&g
Re: [VOTE] Release Apache OpenWebBeans-1.2.7
+1 Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-26 22:30 GMT+01:00 Mark Struberg : > Hi! > > I'd like to call a VOTE on releasing Apache OpenWebBeans-1.2.7. > > This is a maintenance release of the owb_1.2.x branch and targets the CDI-1.0 > specification. > > The ReleaseNotes are available online: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310844&version=12327069 > > > Source Release: > http://repository.apache.org/content/repositories/orgapacheopenwebbeans-1007/org/apache/openwebbeans/openwebbeans/1.2.7/openwebbeans-1.2.7-source-release.zipsha1 > is 248fdfef56de3f3de9783b51b81988580fbcdccb > > > SVN source tag (r1641936): > https://svn.apache.org/repos/asf/openwebbeans/tags/openwebbeans-1.2.7/ > > > The staging repo is: > http://repository.apache.org/content/repositories/orgapacheopenwebbeans-1007/ > > > PGP release key 2FDB81B1 > http://svn.apache.org/repos/asf/openwebbeans/trunk/KEYS > > > > The VOTE will be open for 72 hours. > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 veto (and reason why) > > > > > LieGrue, > strub
org.jboss.cdi.tck.tests.implementation.enterprise.newBean.Wizard
Hi
do you think org.jboss.cdi.tck.tests.implementation.enterprise.newBean.Wizard
is valid?
In short:
@RequestScoped
public class Wizard {
@Inject
@Tame
private Dragon dragon;
@Produces
@Tame
public Dragon summon(@New Dragon dragon) {
return dragon;
}
}
so wizard instance is needed to create a dragon (@Produces is not
static) but to call summon to create a dragon we need a wizard...
happen in
but no EE link here
OWB just gives a stackoverflow (which is not shocking) but I wonder if
that's a CDI/TCK issue or it is on our side
wdyt?
Romain Manni-Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com/rmannibucau
Re: org.jboss.cdi.tck.tests.implementation.enterprise.newBean.Wizard
great, exactlt what I thought but was no more sure at all. Thanks Mark
Romain Manni-Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com/rmannibucau
2014-12-14 9:59 GMT+01:00 Mark Struberg :
> I've created
> https://issues.jboss.org/browse/CDITCK-459
> for it.
>
> LieGrue,
> strub
>
>
>
>
>
>> On Sunday, 14 December 2014, 9:51, Mark Struberg wrote:
>> > We've already discussed this and opened a CDITCK issue for a similar class.
>> It is entirely illegal.
>> You might find it in OWBs standalone-suite.xml
>>
>>
>> LieGrue,
>> strub
>>
>>
>>
>>
>>
>>
>>> On Sunday, 14 December 2014, 0:30, Romain Manni-Bucau
>> wrote:
>>> > Hi
>>>
>>> do you think
>> org.jboss.cdi.tck.tests.implementation.enterprise.newBean.Wizard
>>> is valid?
>>>
>>> In short:
>>>
>>> @RequestScoped
>>> public class Wizard {
>>> @Inject
>>> @Tame
>>> private Dragon dragon;
>>>
>>> @Produces
>>> @Tame
>>> public Dragon summon(@New Dragon dragon) {
>>> return dragon;
>>> }
>>> }
>>>
>>> so wizard instance is needed to create a dragon (@Produces is not
>>> static) but to call summon to create a dragon we need a wizard...
>>>
>>> happen in >>
>> name="org.jboss.cdi.tck.tests.implementation.enterprise.newBean.NewEnterpriseBeanTest"/>
>>> but no EE link here
>>>
>>> OWB just gives a stackoverflow (which is not shocking) but I wonder if
>>> that's a CDI/TCK issue or it is on our side
>>>
>>> wdyt?
>>>
>>> Romain Manni-Bucau
>>> @rmannibucau
>>> http://www.tomitribe.com
>>> http://rmannibucau.wordpress.com
>>> https://github.com/rmannibucau
>>>
>>
AfterTypeDiscoveryEvent
Hi guys, is org.apache.webbeans.config.BeansDeployer#fireAfterTypeDiscoveryEvent is not correctly implemented? getXXX() should return "list of enabled XXX" but we return only @Priority ones + user should be allowed to remove items from the list but we don't support it. did I misunderstand it? Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau
Re: AfterTypeDiscoveryEvent
FYI org.jboss.cdi.tck.tests.extensions.lifecycle.atd.AfterTypeDiscoveryTest don't pass with OWB 1.5.0-SNAPSHOT Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-12-19 19:19 GMT+01:00 Romain Manni-Bucau : > Hi guys, > > is org.apache.webbeans.config.BeansDeployer#fireAfterTypeDiscoveryEvent > is not correctly implemented? > > getXXX() should return "list of enabled XXX" but we return only > @Priority ones + user should be allowed to remove items from the list > but we don't support it. > > did I misunderstand it? > > Romain Manni-Bucau > @rmannibucau > http://www.tomitribe.com > http://rmannibucau.wordpress.com > https://github.com/rmannibucau
Re: svn commit: r1646768 - /openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/intercept/InterceptorResolutionService.java
Hmm
What would you have expected as description? This is part of cdi 1.1 impl
one - at least i thought
Le 19 déc. 2014 23:26, "Mark Struberg" a écrit :
> Romain, PLEASE create JIRAs for such tasks. We totally loose oversight
> otherwise.
>
> LieGrue,
> strub
>
>
>
>
>
> > On Friday, 19 December 2014, 16:21, "rmannibu...@apache.org" <
> rmannibu...@apache.org> wrote:
> > > Author: rmannibucau
> > Date: Fri Dec 19 15:21:49 2014
> > New Revision: 1646768
> >
> > URL: http://svn.apache.org/r1646768
> > Log:
> > rewriting @AroundConstruct selection to ensure to use a single
> constructor and
> > avoid to use an aggregated view - including proxy oriented constructors
> >
> > Modified:
> >
> >
> openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/intercept/InterceptorResolutionService.java
> >
> > Modified:
> >
> openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/intercept/InterceptorResolutionService.java
> > URL:
> >
> http://svn.apache.org/viewvc/openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/intercept/InterceptorResolutionService.java?rev=1646768&r1=1646767&r2=1646768&view=diff
> >
> ==
> > ---
> >
> openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/intercept/InterceptorResolutionService.java
> > (original)
> > +++
> >
> openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/intercept/InterceptorResolutionService.java
> > Fri Dec 19 15:21:49 2014
> > @@ -269,67 +269,53 @@ public class InterceptorResolutionServic
> >
> >
> >
> allUsedCdiInterceptors.addAll(beanManagerImpl.resolveInterceptors(InterceptionType.POST_CONSTRUCT,
> > interceptorBindings));
> >
> >
> allUsedCdiInterceptors.addAll(beanManagerImpl.resolveInterceptors(InterceptionType.PRE_DESTROY,
> > interceptorBindings));
> > +}
> >
> > -if (!annotatedType.getConstructors().isEmpty())
> > +AnnotatedConstructor constructorToUse = null;
> > +if (!annotatedType.getConstructors().isEmpty()) // avoid to use
> class
> > annotations for not used constructors
> > +{
> > +for (final AnnotatedConstructor c :
> > annotatedType.getConstructors())
> > {
> > -for (final AnnotatedConstructor c :
> > annotatedType.getConstructors())
> > +if (constructorToUse == null &&
> > c.getParameters().isEmpty())
> > {
> > -final Set constructorAnnot =
> >
> webBeansContext.getAnnotationManager().getInterceptorAnnotations(c.getAnnotations());
> > -if (constructorAnnot.isEmpty())
> > -{
> > -
> >
> allUsedCdiInterceptors.addAll(beanManagerImpl.resolveInterceptors(InterceptionType.AROUND_CONSTRUCT,
> > interceptorBindings));
> > -}
> > -else
> > -{
> > -
> constructorAnnot.addAll(classInterceptorBindings);
> > -
> >
> allUsedCdiInterceptors.addAll(beanManagerImpl.resolveInterceptors(InterceptionType.AROUND_CONSTRUCT,
> > AnnotationUtil.asArray(constructorAnnot)));
> > -}
> > +constructorToUse = c;
> > +}
> > +else if (c.getAnnotation(Inject.class) != null)
> > +{
> > +constructorToUse = c;
> > +break;
> > }
> > -}
> > -else
> > -{
> > -
> >
> allUsedCdiInterceptors.addAll(beanManagerImpl.resolveInterceptors(InterceptionType.AROUND_CONSTRUCT,
> > interceptorBindings));
> > }
> > }
> > -
> > -if (!annotatedType.getConstructors().isEmpty())
> > +if (constructorToUse != null)
> > {
> > -for (final AnnotatedConstructor c :
> > annotatedType.getConstructors())
> > +final Set constructorAnnot =
> >
> webBeansContext.getAnnotationManager().getInterceptorAnnotations(constructorToUse.getAnnotations());
> > +for (final Annotation classA : classInterceptorBindings)
> > {
> > -final Set constructorAnnot =
> >
> webBeansContext.getAnnotationManager().getInterceptorAnnotations(c.getAnnotations());
> > -if (constructorAnnot.isEmpty())
> > +boolean overriden = false;
> > +for (final Annotation consA : constructorAnnot)
> > {
> > -if (interceptorBindings != null)
> > +if (classA.annotationType() ==
> consA.annotationType())
> > {
> > -
> >
> allUsedConstructorCdiInterceptors.addAll(beanManagerImpl.resolveInterceptors(InterceptionType.AROUND_CONSTRUCT,
> > interceptorBindings));
> > +overriden = true;
> > +break;
> > }
> > }
> > -else
> > +if (!overriden)
> > {
> > -
Re: AfterTypeDiscoveryEvent
Ok, not yet sure it is the tck issue. Seems we really have a bug with addAnnotatedType forgetting to trigger some event (called too late to be automatic). I ll try to have a look soon but wanted to understand the "wording". Thks Mark Le 19 déc. 2014 23:19, "Mark Struberg" a écrit : > No this is perfectly fine. We discussed this recently and there was a bug > in Weld. And I guess they just 1:1 moved this bug over to the TCK. > > > "getAlternatives() returns the ordered list of enabled alternatives for > the application. Alternative enabled for a bean archive are not included in > the list." > > Currently only Alternatives with @Priority are 'enabled alternatives _for > the application_'! Whereas "Alternative enabled for a bean archive" (means > via beans.xml) are explicitly NOT enlisted by this method. > > > Similar wording exists for interceptors and decorators. > > > Please file a CDITCK issue for it. > > LieGrue, > strub > > > > > > > On Friday, 19 December 2014, 19:20, Romain Manni-Bucau < > rmannibu...@gmail.com> wrote: > > > Hi guys, > > > > is org.apache.webbeans.config.BeansDeployer#fireAfterTypeDiscoveryEvent > > is not correctly implemented? > > > > getXXX() should return "list of enabled XXX" but we return only > > @Priority ones + user should be allowed to remove items from the list > > but we don't support it. > > > > did I misunderstand it? > > > > Romain Manni-Bucau > > @rmannibucau > > http://www.tomitribe.com > > http://rmannibucau.wordpress.com > > https://github.com/rmannibucau > > >
Re: AfterTypeDiscoveryEvent
I'm on org.jboss.cdi.tck.tests.extensions.lifecycle.atd.AfterTypeDiscoveryTest Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-12-20 9:52 GMT+01:00 Mark Struberg : > which test is this exactly? > > LieGrue, > strub > > > > > >> On Saturday, 20 December 2014, 9:30, Romain Manni-Bucau >> wrote: >> > Ok, not yet sure it is the tck issue. Seems we really have a bug with >> addAnnotatedType forgetting to trigger some event (called too late to be >> automatic). I ll try to have a look soon but wanted to understand the >> "wording". >> >> Thks Mark >> >> Le 19 déc. 2014 23:19, "Mark Struberg" a >> écrit : >> >>> No this is perfectly fine. We discussed this recently and there was a bug >>> in Weld. And I guess they just 1:1 moved this bug over to the TCK. >>> >>> >>> "getAlternatives() returns the ordered list of enabled alternatives >> for >>> the application. Alternative enabled for a bean archive are not included in >>> the list." >>> >>> Currently only Alternatives with @Priority are 'enabled alternatives >> _for >>> the application_'! Whereas "Alternative enabled for a bean >> archive" (means >>> via beans.xml) are explicitly NOT enlisted by this method. >>> >>> >>> Similar wording exists for interceptors and decorators. >>> >>> >>> Please file a CDITCK issue for it. >>> >>> LieGrue, >>> strub >>> >>> >>> >>> >>> >>> > On Friday, 19 December 2014, 19:20, Romain Manni-Bucau < >>> rmannibu...@gmail.com> wrote: >>> > > Hi guys, >>> > >>> > is >> org.apache.webbeans.config.BeansDeployer#fireAfterTypeDiscoveryEvent >>> > is not correctly implemented? >>> > >>> > getXXX() should return "list of enabled XXX" but we return >> only >>> > @Priority ones + user should be allowed to remove items from the list >>> > but we don't support it. >>> > >>> > did I misunderstand it? >>> > >>> > Romain Manni-Bucau >>> > @rmannibucau >>> > http://www.tomitribe.com >>> > http://rmannibucau.wordpress.com >>> > https://github.com/rmannibucau >>> > >>> >>
ConversationManager lookup by key or iterator?
Hi
any reason we iterate over conversations to find the one from cId and
sessionId in
org.apache.webbeans.conversation.ConversationManager#getPropogatedConversation
and we don't use a ConversationId{cId, sessionId} key in a Map?
Romain Manni-Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com/rmannibucau
Re: svn commit: r1658730 - in /openwebbeans/trunk/webbeans-impl/src: main/java/org/apache/webbeans/util/ test/java/org/apache/webbeans/test/interceptors/factory/ test/java/org/apache/webbeans/test/int
sure it should but shouldn't we use annotated type methods instead of
pure reflection?
Romain Manni-Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com/rmannibucau
2015-02-12 14:41 GMT+01:00 Joseph Bergmark :
> I need to write a quick unit test to verify, but I think this may still be
> missing non-public inherited methods.
>
> Previously it only used getDeclaredMethods, which would return all all
> private, protected, default and public methods for the class, but did not
> contain any inherited methods. If I'm reading this change correctly it now
> adds getMethods which will add public inherited methods but still doesn't
> include protected or default methods.
>
> I wonder if we should walk up the class hierarchy and call
> getDeclaredMethods at each step. Might need to discard private methods
> found in superclasses as I'm not sure we need to worry about those being
> called on the proxy.
>
> On Tue, Feb 10, 2015 at 9:57 AM, wrote:
>
>> Author: tandraschko
>> Date: Tue Feb 10 14:57:07 2015
>> New Revision: 1658730
>>
>> URL: http://svn.apache.org/r1658730
>> Log:
>> OWB-1036 NormalScoped ASM proxies broken in some cases for partial beans
>>
>> Added:
>>
>> openwebbeans/trunk/webbeans-impl/src/test/java/org/apache/webbeans/test/interceptors/factory/beans/PartialBeanClass.java
>>
>> openwebbeans/trunk/webbeans-impl/src/test/java/org/apache/webbeans/test/interceptors/factory/beans/PartialBeanClassSuperClass.java
>>
>> openwebbeans/trunk/webbeans-impl/src/test/java/org/apache/webbeans/test/interceptors/factory/beans/PartialBeanClassSuperInterface.java
>> Modified:
>>
>> openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/util/ClassUtil.java
>>
>> openwebbeans/trunk/webbeans-impl/src/test/java/org/apache/webbeans/test/interceptors/factory/NormalScopeProxyFactoryTest.java
>>
>> Modified:
>> openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/util/ClassUtil.java
>> URL:
>> http://svn.apache.org/viewvc/openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/util/ClassUtil.java?rev=1658730&r1=1658729&r2=1658730&view=diff
>>
>> ==
>> ---
>> openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/util/ClassUtil.java
>> (original)
>> +++
>> openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/util/ClassUtil.java
>> Tue Feb 10 14:57:07 2015
>> @@ -305,8 +305,22 @@ public final class ClassUtil
>> Map>
>> methodMap, List allMethods,
>> Class clazz)
>> {
>> +List temp = new
>> ArrayList(Arrays.asList(clazz.getMethods()));
>> for (Method method : clazz.getDeclaredMethods())
>> {
>> +if (!temp.contains(method))
>> +{
>> +temp.add(method);
>> +}
>> +}
>> +
>> +for (Method method : temp)
>> +{
>> + if (allMethods.contains(method))
>> + {
>> + continue;
>> + }
>> +
>> if (method.isBridge())
>> {
>> // we have no interest in generics bridge methods
>>
>> Modified:
>> openwebbeans/trunk/webbeans-impl/src/test/java/org/apache/webbeans/test/interceptors/factory/NormalScopeProxyFactoryTest.java
>> URL:
>> http://svn.apache.org/viewvc/openwebbeans/trunk/webbeans-impl/src/test/java/org/apache/webbeans/test/interceptors/factory/NormalScopeProxyFactoryTest.java?rev=1658730&r1=1658729&r2=1658730&view=diff
>>
>> ==
>> ---
>> openwebbeans/trunk/webbeans-impl/src/test/java/org/apache/webbeans/test/interceptors/factory/NormalScopeProxyFactoryTest.java
>> (original)
>> +++
>> openwebbeans/trunk/webbeans-impl/src/test/java/org/apache/webbeans/test/interceptors/factory/NormalScopeProxyFactoryTest.java
>> Tue Feb 10 14:57:07 2015
>> @@ -38,6 +38,7 @@ import java.lang.reflect.Type;
>> import java.net.URL;
>> import java.net.URLClassLoader;
>> import java.util.Set;
>> +import
>> org.apache.webbeans.test.interceptors.factory.beans.PartialBeanClass;
>>
>> import static org.junit.Assert.assertNotNull;
>>
>> @@ -207,6 +208,40 @@ public class NormalScopeProxyFactoryTest
&
Re: Fwd: sessionscoped rework
Unifying i dont believe it that much but merging half of it sure. That said this switch in sessionid will go in tomcat module to be clean. Le 9 mars 2015 17:23, "Mark Struberg" a écrit : > Whoops should have gone over here. > > LieGrue, > strub > > > > > Anfang der weitergeleiteten Nachricht: > > > > Antwort an: d...@tomee.apache.org > > Von: Mark Struberg > > Betreff: sessionscoped rework > > Datum: 09. März 2015 17:15:26 MEZ > > An: openejb-dev > > > > hi Arne, missed you on IRC > > > > > > 13:20 arne__ > > Hi > > I am looking at the session id stuff from the list > > Any objections to take over the tomee code to our tomcat plugin? > > > > > > I did not take a close look but I think it’s pretty fine. We should > really back our session with a REAL http session IF it is available. It > should be pretty easy to do so in webbeans-web as we can easily override > the context impls via openwebbeans.properties. > > > > Reinhard also said he likes to help, so probably you two can do a > hangout session and hack it together. > > > > txs and LieGrue, > > strub > >
Fwd: svn commit: r1666745 - in /openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception: ./ helper/
Please revert you just broke all arquillian tests relying on a remote
container using OWB (tomee in my case)...and real use cases as well but not
yet hit it.
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>
-- Forwarded message --
From:
Date: 2015-03-14 21:58 GMT+01:00
Subject: svn commit: r1666745 - in
/openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception:
./ helper/
To: comm...@openwebbeans.apache.org
Author: struberg
Date: Sat Mar 14 20:58:32 2015
New Revision: 1666745
URL: http://svn.apache.org/r1666745
Log:
OWB-1039 make revert writeReplace and make ExceptionMessageBuilder
serializable
Modified:
openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception/DuplicateDefinitionException.java
openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception/InconsistentSpecializationException.java
openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception/WebBeansConfigurationException.java
openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception/WebBeansDeploymentException.java
openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception/helper/ExceptionMessageBuilder.java
Modified:
openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception/DuplicateDefinitionException.java
URL:
http://svn.apache.org/viewvc/openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception/DuplicateDefinitionException.java?rev=1666745&r1=1666744&r2=1666745&view=diff
==
---
openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception/DuplicateDefinitionException.java
(original)
+++
openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception/DuplicateDefinitionException.java
Sat Mar 14 20:58:32 2015
@@ -22,8 +22,6 @@ import javax.enterprise.inject.spi.Defin
import org.apache.webbeans.exception.helper.DescriptiveException;
import org.apache.webbeans.exception.helper.ExceptionMessageBuilder;
-import java.io.ObjectStreamException;
-
public class DuplicateDefinitionException extends DefinitionException
implements DescriptiveException
{
private static final long serialVersionUID = 2312285271502063304L;
@@ -64,8 +62,4 @@ public class DuplicateDefinitionExceptio
return msg.getAdditionalInformation(super.getLocalizedMessage());
}
-private Object writeReplace() throws ObjectStreamException
-{
-return new DefinitionException(getMessage(), getCause());
-}
}
Modified:
openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception/InconsistentSpecializationException.java
URL:
http://svn.apache.org/viewvc/openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception/InconsistentSpecializationException.java?rev=1666745&r1=1666744&r2=1666745&view=diff
==
---
openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception/InconsistentSpecializationException.java
(original)
+++
openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception/InconsistentSpecializationException.java
Sat Mar 14 20:58:32 2015
@@ -22,8 +22,6 @@ import javax.enterprise.inject.spi.Defin
import org.apache.webbeans.exception.helper.DescriptiveException;
import org.apache.webbeans.exception.helper.ExceptionMessageBuilder;
-import java.io.ObjectStreamException;
-
public class InconsistentSpecializationException extends
DefinitionException implements DescriptiveException
{
private static final long serialVersionUID = 5398575103682514128L;
@@ -63,8 +61,4 @@ public class InconsistentSpecializationE
return msg.getAdditionalInformation(super.getLocalizedMessage());
}
-private Object writeReplace() throws ObjectStreamException
-{
-return new DefinitionException(getMessage(), getCause());
-}
}
Modified:
openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception/WebBeansConfigurationException.java
URL:
http://svn.apache.org/viewvc/openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception/WebBeansConfigurationException.java?rev=1666745&r1=1666744&r2=1666745&view=diff
==
---
openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception/WebBeansConfigurationException.java
(original)
+++
openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception/WebBeansConfigurationException.java
Sat Mar 14 20:58:32 2015
@@ -22,8 +22,6 @@ import javax.enterprise.inject.spi.Defin
import
Re: Fwd: svn commit: r1666745 - in /openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception: ./ helper/
Yes, point is only to do our best to not let the client with a string, nothing more Le 15 mars 2015 11:23, "Mark Struberg" a écrit : > A summary of what I discussed with Romain on IRC: > > According to the JavaEE spec only checked Exceptions and RuntimeExceptions > which are marked as @ApplicationException must get transfered over @Remote > (regardless if this is a real client or even inside the same JVM). For > others the Exception gets re-packaged into a javax.ejb.EJBException. > > TomEE takes some internal Exceptions and additionally transfers them along > to the client. This is mainly as some TCKs are strictly speaking broken as > they test for DefinitionException, DeploymentException, > OptimisticLockException and other internal exceptions (which are > RuntimeExceptions). But this only works as long as there is a cdi and jpa > spec API jars are available on the client. > > > Since the TomEE server doesn't know what is on the client it usually wraps > Exceptions into a ThrowableArtifact which contains the original Exception > (basically manually serialized as byte[]) plus also the String > representation. If it is not possible to deserialize the original Exception > (because javax.persistence.OptimisticLockException.class is not available > on the client) then it falls back to unwrapping to an EJBException plus > adding the String information of the original Exception. > > TomEE did this wrapping only for custom Exceptions so far. But it also > needs to provide the same for DefinitionException and DeploymentException > as this might contain custom MyVersyOwnOnlyOnServerExtensionException which > got thrown by an Extension on the server. And this will get added as Cause > to the DeploymentException. So even if we don't serialize a > WebBeansDeplyomentException but a spec DeploymentException instead then we > still have the problem with all the containing causes which are not > available on the client side (and thus will make the app fail with a > ClassNotFoundException). > > LieGrue, > strub > > > > > > > On Saturday, 14 March 2015, 22:01, Romain Manni-Bucau < > rmannibu...@gmail.com> wrote: > > > Please revert you just broke all arquillian tests relying on a remote > > container using OWB (tomee in my case)...and real use cases as well but > not > > yet hit it. > > > > 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> > > > > > > -- Forwarded message -- > > From: > > Date: 2015-03-14 21:58 GMT+01:00 > > Subject: svn commit: r1666745 - in > > > /openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception: > > ./ helper/ > > To: comm...@openwebbeans.apache.org > > > > > > Author: struberg > > Date: Sat Mar 14 20:58:32 2015 > > New Revision: 1666745 > > > > URL: http://svn.apache.org/r1666745 > > Log: > > OWB-1039 make revert writeReplace and make ExceptionMessageBuilder > > serializable > > > > Modified: > > > > > openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception/DuplicateDefinitionException.java > > > > > openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception/InconsistentSpecializationException.java > > > > > openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception/WebBeansConfigurationException.java > > > > > openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception/WebBeansDeploymentException.java > > > > > openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception/helper/ExceptionMessageBuilder.java > > > > Modified: > > > openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception/DuplicateDefinitionException.java > > URL: > > > http://svn.apache.org/viewvc/openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception/DuplicateDefinitionException.java?rev=1666745&r1=1666744&r2=1666745&view=diff > > > == > > --- > > > openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception/DuplicateDefinitionException.java > > (original) > > +++ > > > openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/exception/DuplicateDefinitionException.java > > Sat
Re: upgrade to java7?
+0 Le 9 avr. 2015 19:22, "Mark Struberg" a écrit : > Hi! > > Just became aware that we are still targeting java6 in trunk. But CDI-1.2 > is Java7 per spec, so we should imo also upgrade the project to java7. > > Any objections? > > LieGrue, > strub
Re: preparing to release owb-1.5.0
+1 and a big thank you! 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-09 20:36 GMT+02:00 Gerhard Petracek : > +1 > > regards, > gerhard > > > > 2015-04-09 19:40 GMT+02:00 Mark Struberg : > > > 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 >
Re: [VOTE] Release Apache OpenWebBeans-1.5.0
+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 :
> 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=12310844&version=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
@Howard: would have been cool ;). This is not intended to work so easily. TomEE 2 does it. 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 15:17 GMT+02:00 Howard W. Smith, Jr. : > 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 > INFO: openejb.home = C:\apache-tomee-plus-1.7.1 > Apr 13, 2015 9:09:48 AM org.apache.openejb.OpenEJB$Instance > 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.(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 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: >> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310844&version=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.
Re: [DISCUSS] Tasks and Ideas for 1.5.1
2015-04-19 21:25 GMT+02:00 Mark Struberg : > Hi folks! > > First I want to say a BIG thanks to all the people wo made OWB-1.5.0 > possible. It was quite a long walk, but we had tons of fun and the project, > the team and the community around it ist still amazing even after so many > years! > > There is an old saying: „After the release is before the release“ > > I guess we will likely get some bugs and feedback pretty soon, so I target > a 1.5.1 release rather soonish ;) > > What do YOU like to address in the next few weeks? > Here is my personal list of tasks: > > * Update our site to reflect CDI-1.1. ANY HELP IS WELCOME :) > > * Get rid of our Map backed SessionContext impl. Instead we should store > our @SessionScoped beans directly in the HttpSession. And only use a Map if > we really need a ’synthetic session’. We also don’t need to care about > sessionId rewrite anymore in that case. > > +0.7. Basically I think it is a super good feature to not depend on the session impl so we need to keep it even if agree it shouldnt be the default. FYI tomee has it https://github.com/apache/tomee/blob/develop/tomee/tomee-catalina/src/main/java/org/apache/tomee/catalina/cdi/SessionContextBackedByHttpSession.java > * Store our Conversations in a custom Bean in the SessionContext. That > way it doesn’t matter where the session gets stored. > > +1, also wonder if it makes sense to have ConversationBean request scoped. Makes transient conversation hard to manage and dependent of a scope it shouldnt need IMO. > * Probably get rid of the ConversationManager? It uses the nifty sessionId > heavily :( And technically we don’t need that… > > +1 > * Get rid of all the FailOver stuff. This is not needed anymore if we > really persist into a Session. This will really simplify a big area of our > codebase > > +0.7. Makes sense but also far better than session storage depending the session impl used. > * Split WebBeansConfigurationListener in Begin and End Listeners. We did > this in TomEE already. This is important if to guarantee that OWB gets > started as first in the chain, but stopped/cleaning up as last one in the > Listener chain. > > Also makes harder in servlet apps and not very useful. Can makes sense in tomcat integration but I'd keep an aggregated listener for common cases of OWB user usage. > * Improve our Servlet integration. > > I will create JIRA tickets for all thos ideas. > > Wdyt? Any other things to target in the next release? > > > LieGrue, > strub
Re: [DISCUSS] Tasks and Ideas for 1.5.1
well the good point of FO is that you have a flush at the end so potentially a single remote touch. Not sure what's the usage, I know in TomEE it is never used. 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-19 22:08 GMT+02:00 Mark Struberg : > The point is that our default impl will still have a Map backed > SessionContext. But that one also doesn’t need any serialisation! > > The HttpSession will be a part of the webbeans-web module where it fits > with the WebContextsService. > The headache with the whole FailOver stuff is imo in no relation to the > eventual benefits. > > LieGrue, > strub > > > Am 19.04.2015 um 21:51 schrieb Romain Manni-Bucau >: > > > > 2015-04-19 21:25 GMT+02:00 Mark Struberg : > > > >> Hi folks! > >> > >> First I want to say a BIG thanks to all the people wo made OWB-1.5.0 > >> possible. It was quite a long walk, but we had tons of fun and the > project, > >> the team and the community around it ist still amazing even after so > many > >> years! > >> > >> There is an old saying: „After the release is before the release“ > >> > >> I guess we will likely get some bugs and feedback pretty soon, so I > target > >> a 1.5.1 release rather soonish ;) > >> > >> What do YOU like to address in the next few weeks? > >> Here is my personal list of tasks: > >> > >> * Update our site to reflect CDI-1.1. ANY HELP IS WELCOME :) > >> > >> * Get rid of our Map backed SessionContext impl. Instead we should store > >> our @SessionScoped beans directly in the HttpSession. And only use a > Map if > >> we really need a ’synthetic session’. We also don’t need to care about > >> sessionId rewrite anymore in that case. > >> > >> > > +0.7. Basically I think it is a super good feature to not depend on the > > session impl so we need to keep it even if agree it shouldnt be the > > default. FYI tomee has it > > > https://github.com/apache/tomee/blob/develop/tomee/tomee-catalina/src/main/java/org/apache/tomee/catalina/cdi/SessionContextBackedByHttpSession.java > > > > > >> * Store our Conversations in a custom Bean in the SessionContext. > That > >> way it doesn’t matter where the session gets stored. > >> > >> > > +1, also wonder if it makes sense to have ConversationBean request > scoped. > > Makes transient conversation hard to manage and dependent of a scope it > > shouldnt need IMO. > > > > > >> * Probably get rid of the ConversationManager? It uses the nifty > sessionId > >> heavily :( And technically we don’t need that… > >> > >> > > +1 > > > > > >> * Get rid of all the FailOver stuff. This is not needed anymore if we > >> really persist into a Session. This will really simplify a big area of > our > >> codebase > >> > >> > > +0.7. Makes sense but also far better than session storage depending the > > session impl used. > > > > > >> * Split WebBeansConfigurationListener in Begin and End Listeners. We did > >> this in TomEE already. This is important if to guarantee that OWB gets > >> started as first in the chain, but stopped/cleaning up as last one in > the > >> Listener chain. > >> > >> > > Also makes harder in servlet apps and not very useful. Can makes sense in > > tomcat integration but I'd keep an aggregated listener for common cases > of > > OWB user usage. > > > > > >> * Improve our Servlet integration. > >> > >> I will create JIRA tickets for all thos ideas. > >> > >> Wdyt? Any other things to target in the next release? > >> > >> > >> LieGrue, > >> strub > >
Re: a new OWB-1.2.x release?
+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-22 14:03 GMT+02:00 Thomas Andraschko : > +1 > > 2015-04-22 14:01 GMT+02:00 Mark Struberg : > > > 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] Release Apache OpenWebBeans-1.2.8
+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-22 15:37 GMT+02:00 Mark Struberg :
> 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=12310844&version=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: adding a web-fragment.xml to openwebbeans-web?
Le 25 avr. 2015 21:58, "Mark Struberg" a écrit : > > Hi! > > Should we add the WebBeansConfigurationListener (or later the two split ones, see OWB-1055) into a web-fragment.xml inside our openwebbeasns-web module? > > Pro: no need to add any listener manually + we should be neatly able to define the default priorities (outermost listener). > Con: not sure yet, that’s what I’m curious about :) Any input? > Break container usage, not always well supported? That said could be done in another module. Would split lib and app artifacts which is good. Also the conversation filter needs to be handled prog so ServletContextInitializer sounds better. > > LieGrue, > strub
Re: adding a web-fragment.xml to openwebbeans-web?
Le 26 avr. 2015 08:24, "Mark Struberg" a écrit : > > > Break container usage > > As per the servlet spec only web-fragment.xml in jars of WEB-INF/lib must get picked up automatically. > 5 first words are the issue. > See servlet spec 8.2.1 „Modularity of web.xml“: > > „If a framework wants its META-INF/web-fragment.xml honored in such a way that it augments a web application’s web.xml, the framework must be bundled within the web application's WEB-INF/lib directory. > … > In other words, only JAR files bundled in a web application’s WEB-INF/lib directory, but not those higher up in the class loading delegation chain, need to be scanned for web-fragment.xml" > > So that one should not be a blocker. > > > I guess the only loss is some amount of > > ordering control you might have had if you > > included it in the parent web.xml directly. > We can force it "before" which should almost be enough. > I had the exact other problem which brought me to this ;) > In my lightweightee example I use deltaspike-jsf which has a web-fragment for the window handler, ViewConfigPathValidator, etc. > It has > > > > > > but _still_ gets executed before the WebBeansConfigurationListener of our own local web.xml > So I hoped that switching to web-fragment.xml for owb as well (with before-others) should fix that. Still need to test. > Need to check what’s going on. Or if this is a bug in the pretty old tomcat7 I use… > Side note: if done - no issue in tomee btw - should be a 1.6 and not 1.5.1 IMO > LieGrue, > strub > > > > Am 26.04.2015 um 01:12 schrieb Joseph Bergmark : > > > > It should be well supported on any servlet 3.0 compliant container as its > > part of the specification. I suppose it could be inconvenient for > > application servers that already have OWB integration, but in that case I > > wouldn't expect the user to be including OWB in their application at all. > > > > As long as we document that including the openwebbeans-web module into your > > application will cause a ServletContainerInitializer to automatically be > > added, I don't see any harm in it. I guess the only loss is some amount of > > ordering control you might have had if you included it in the parent > > web.xml directly. > > > > On Sat, Apr 25, 2015 at 5:14 PM, Romain Manni-Bucau < rmannibu...@gmail.com> > > wrote: > > > >> Le 25 avr. 2015 21:58, "Mark Struberg" a écrit : > >>> > >>> Hi! > >>> > >>> Should we add the WebBeansConfigurationListener (or later the two split > >> ones, see OWB-1055) into a web-fragment.xml inside our openwebbeasns-web > >> module? > >>> > >>> Pro: no need to add any listener manually + we should be neatly able to > >> define the default priorities (outermost listener). > >>> Con: not sure yet, that’s what I’m curious about :) Any input? > >>> > >> > >> Break container usage, not always well supported? > >> > >> That said could be done in another module. Would split lib and app > >> artifacts which is good. > >> > >> Also the conversation filter needs to be handled prog so > >> ServletContextInitializer sounds better. > >> > >>> > >>> LieGrue, > >>> strub > >> >
Re: adding a web-fragment.xml to openwebbeans-web?
Le 26 avr. 2015 13:38, "Mark Struberg" a écrit : > > > >> As per the servlet spec > > 5 first words are the issue. > > > Well, thats life ;) > We only have to deal with tomcat, jetty and tomee. The rest will 95% work as well. And it’s always possible to do a deeper integration anyway. > Then it is fine. > > > We can force it „before" which should almost be enough. > > If you manually define the order or use the tomcat native integration to define the order or a certain Listener then this will overwrite all the user specified ordering, right? > If you do not then you know it will not work so not sure we have the choice. PS: didnt check - no computer ATM - but wouldnt tomcat integration of owb be broken like tomee would be without hack? > LieGrue, > strub > > > > > Am 26.04.2015 um 09:19 schrieb Romain Manni-Bucau : > > > > Le 26 avr. 2015 08:24, "Mark Struberg" a écrit : > >> > >>> Break container usage > >> > >> As per the servlet spec only web-fragment.xml in jars of WEB-INF/lib must > > get picked up automatically. > >> > > > > 5 first words are the issue. > > > >> See servlet spec 8.2.1 „Modularity of web.xml“: > >> > >> „If a framework wants its META-INF/web-fragment.xml honored in such a way > > that it augments a web application’s web.xml, the framework must be bundled > > within the web application's WEB-INF/lib directory. > >> … > >> In other words, only JAR files bundled in a web application’s WEB-INF/lib > > directory, but not those higher up in the class loading delegation chain, > > need to be scanned for web-fragment.xml" > >> > >> So that one should not be a blocker. > >> > >>> I guess the only loss is some amount of > >>> ordering control you might have had if you > >>> included it in the parent web.xml directly. > >> > > > > We can force it "before" which should almost be enough. > > > >> I had the exact other problem which brought me to this ;) > >> In my lightweightee example I use deltaspike-jsf which has a web-fragment > > for the window handler, ViewConfigPathValidator, etc. > >> It has > >> > >> > >> > >> > >> > >> but _still_ gets executed before the WebBeansConfigurationListener of our > > own local web.xml > >> So I hoped that switching to web-fragment.xml for owb as well (with > > before-others) should fix that. Still need to test. > >> Need to check what’s going on. Or if this is a bug in the pretty old > > tomcat7 I use… > >> > > > > Side note: if done - no issue in tomee btw - should be a 1.6 and not 1.5.1 > > IMO > > > >> LieGrue, > >> strub > >> > >> > >>> Am 26.04.2015 um 01:12 schrieb Joseph Bergmark : > >>> > >>> It should be well supported on any servlet 3.0 compliant container as > > its > >>> part of the specification. I suppose it could be inconvenient for > >>> application servers that already have OWB integration, but in that case > > I > >>> wouldn't expect the user to be including OWB in their application at > > all. > >>> > >>> As long as we document that including the openwebbeans-web module into > > your > >>> application will cause a ServletContainerInitializer to automatically be > >>> added, I don't see any harm in it. I guess the only loss is some > > amount of > >>> ordering control you might have had if you included it in the parent > >>> web.xml directly. > >>> > >>> On Sat, Apr 25, 2015 at 5:14 PM, Romain Manni-Bucau < > > rmannibu...@gmail.com> > >>> wrote: > >>> > >>>> Le 25 avr. 2015 21:58, "Mark Struberg" a écrit : > >>>>> > >>>>> Hi! > >>>>> > >>>>> Should we add the WebBeansConfigurationListener (or later the two > > split > >>>> ones, see OWB-1055) into a web-fragment.xml inside our > > openwebbeasns-web > >>>> module? > >>>>> > >>>>> Pro: no need to add any listener manually + we should be neatly able > > to > >>>> define the default priorities (outermost listener). > >>>>> Con: not sure yet, that’s what I’m curious about :) Any input? > >>>>> > >>>> > >>>> Break container usage, not always well supported? > >>>> > >>>> That said could be done in another module. Would split lib and app > >>>> artifacts which is good. > >>>> > >>>> Also the conversation filter needs to be handled prog so > >>>> ServletContextInitializer sounds better. > >>>> > >>>>> > >>>>> LieGrue, > >>>>> strub >
Re: do we like to drop servlet-2.5 support?
We can/should drop t6 but not servlet 2.5 Not sure i get your comment. Servlet 2 or 3 doesnt change anything for us Le 26 avr. 2015 16:33, "Mark Struberg" a écrit : > > Hi folks! > > I wonder if we still like to support tomcat6 and servlet-2.5. We are talking about technology which got introduced more than 10 years ago and is outdated since 5 years now. > > When switching to servlet-3.0++ we would have a few options: > > Make WebBeansConfigurationListener just implement the contextInitialized and destroy and register the BeginWebBeansListener and EndWebBeansListener dynamically as first respective last listener in the chain. > > Any objections? > > LieGrue, > strub
Re: do we like to drop servlet-2.5 support?
Le 26 avr. 2015 17:51, "Joseph Bergmark" a écrit : > > Perhaps I'm being dense, but tomcat 6 is at spec level servlet 2.5 and > tomcat 7 is at spec level servlet 3.0 right? Requiring Servlet 3.0 lets us > leverage ServletContainerInitializers. > Deploying it in a 2.5 container doesnt hurt > On Sun, Apr 26, 2015 at 10:55 AM, Romain Manni-Bucau < rmannibu...@gmail.com> > wrote: > > > We can/should drop t6 but not servlet 2.5 > > > > Not sure i get your comment. Servlet 2 or 3 doesnt change anything for us > > > > Le 26 avr. 2015 16:33, "Mark Struberg" a écrit : > > > > > > Hi folks! > > > > > > I wonder if we still like to support tomcat6 and servlet-2.5. We are > > talking about technology which got introduced more than 10 years ago and is > > outdated since 5 years now. > > > > > > When switching to servlet-3.0++ we would have a few options: > > > > > > Make WebBeansConfigurationListener just implement the contextInitialized > > and destroy and register the BeginWebBeansListener and EndWebBeansListener > > dynamically as first respective last listener in the chain. > > > > > > Any objections? > > > > > > LieGrue, > > > strub > >
Re: do we like to drop servlet-2.5 support?
what can be done is to "standardize" (=force) listener names. Then user can put them in web.xml and we can check if already there. If there dont do anything for this listener if not then do our magic. That said it still doesnt mean breaking 2.5 compatibility since the initalizer would be 100% ignored by servlet 2.5 containers. We can even support HttpSessionIdListener (servlet 3.1) using a bit of reflection in the initalizer I think. 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-26 22:15 GMT+02:00 Mark Struberg : > I hoped to be able to utilize programmatic configuration of servlet > listeners. But there is only a addListener method. For re-ordering I would > also need a remove. Which doesn’t exist… > So back to thinking what I might probably improve… > > LieGrue, > strub > > > Am 26.04.2015 um 21:27 schrieb Thomas Andraschko < > andraschko.tho...@gmail.com>: > > > > +1 if there is any benefit > > our last customer with servlet 2.5 switched to TC7 this year > > > > 2015-04-26 19:31 GMT+02:00 Romain Manni-Bucau : > > > >> Le 26 avr. 2015 17:51, "Joseph Bergmark" a écrit > : > >>> > >>> Perhaps I'm being dense, but tomcat 6 is at spec level servlet 2.5 and > >>> tomcat 7 is at spec level servlet 3.0 right? Requiring Servlet 3.0 lets > >> us > >>> leverage ServletContainerInitializers. > >>> > >> > >> Deploying it in a 2.5 container doesnt hurt > >> > >>> On Sun, Apr 26, 2015 at 10:55 AM, Romain Manni-Bucau < > >> rmannibu...@gmail.com> > >>> wrote: > >>> > >>>> We can/should drop t6 but not servlet 2.5 > >>>> > >>>> Not sure i get your comment. Servlet 2 or 3 doesnt change anything for > >> us > >>>> > >>>> Le 26 avr. 2015 16:33, "Mark Struberg" a écrit : > >>>>> > >>>>> Hi folks! > >>>>> > >>>>> I wonder if we still like to support tomcat6 and servlet-2.5. We are > >>>> talking about technology which got introduced more than 10 years ago > >> and is > >>>> outdated since 5 years now. > >>>>> > >>>>> When switching to servlet-3.0++ we would have a few options: > >>>>> > >>>>> Make WebBeansConfigurationListener just implement the > >> contextInitialized > >>>> and destroy and register the BeginWebBeansListener and > >> EndWebBeansListener > >>>> dynamically as first respective last listener in the chain. > >>>>> > >>>>> Any objections? > >>>>> > >>>>> LieGrue, > >>>>> strub > >>>> > >> > >
Fwd: svn commit: r1676248 - in /openwebbeans/trunk/webbeans-web/src/main/java: META-INF/ org/apache/webbeans/servlet/
Hi Mark
Did you test on tomcat 8? Blind guess - ie not tested - is it doesnt work
cause init/destroy order is logical
-- Message transféré --
De :
Date : 27 avr. 2015 14:59
Objet : svn commit: r1676248 - in
/openwebbeans/trunk/webbeans-web/src/main/java: META-INF/
org/apache/webbeans/servlet/
À :
Cc :
Author: struberg
Date: Mon Apr 27 12:59:02 2015
New Revision: 1676248
URL: http://svn.apache.org/r1676248
Log:
OWB-1055 Split WebBeansConfigurationListener in Begin and End listeners
We need this as the order is the same for all init and destroy methods.
But CDI should get init as first listener, but destroyed as last.
Added:
openwebbeans/trunk/webbeans-web/src/main/java/org/apache/webbeans/servlet/BeginWebBeansConfigurationListener.java
openwebbeans/trunk/webbeans-web/src/main/java/org/apache/webbeans/servlet/EndWebBeansConfigurationListener.java
Removed:
openwebbeans/trunk/webbeans-web/src/main/java/META-INF/
Modified:
openwebbeans/trunk/webbeans-web/src/main/java/org/apache/webbeans/servlet/WebBeansConfigurationListener.java
Added:
openwebbeans/trunk/webbeans-web/src/main/java/org/apache/webbeans/servlet/BeginWebBeansConfigurationListener.java
URL:
http://svn.apache.org/viewvc/openwebbeans/trunk/webbeans-web/src/main/java/org/apache/webbeans/servlet/BeginWebBeansConfigurationListener.java?rev=1676248&view=auto
==
---
openwebbeans/trunk/webbeans-web/src/main/java/org/apache/webbeans/servlet/BeginWebBeansConfigurationListener.java
(added)
+++
openwebbeans/trunk/webbeans-web/src/main/java/org/apache/webbeans/servlet/BeginWebBeansConfigurationListener.java
Mon Apr 27 12:59:02 2015
@@ -0,0 +1,175 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied. See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+package org.apache.webbeans.servlet;
+
+import javax.enterprise.context.RequestScoped;
+import javax.enterprise.context.SessionScoped;
+import javax.servlet.ServletContextEvent;
+import javax.servlet.ServletContextListener;
+import javax.servlet.ServletRequestEvent;
+import javax.servlet.ServletRequestListener;
+import javax.servlet.http.HttpSessionEvent;
+import javax.servlet.http.HttpSessionListener;
+import java.util.logging.Level;
+import java.util.logging.Logger;
+
+import org.apache.webbeans.config.OWBLogConst;
+import org.apache.webbeans.config.WebBeansContext;
+import org.apache.webbeans.logger.WebBeansLoggerFacade;
+import org.apache.webbeans.spi.ContainerLifecycle;
+import org.apache.webbeans.util.WebBeansUtil;
+import org.apache.webbeans.web.util.ServletCompatibilityUtil;
+
+/**
+ * As the ordering of servlet listener invocations is the same for all
+ * *Initialized events (e.g. contextInitialized, requestInitialized)
+ * and for all *Destroyed events (e.g. contextDestroyed, requestDestroyed)
+ * we need a different listener for start and end events.
+ *
+ * The {@link BeginWebBeansConfigurationListener} needs to be invoked as
+ * very first listener in the chain whereas the
+ * {@link EndWebBeansConfigurationListener} needs to be invoked as last
+ * in the chain.
+ *
+ * The {@link WebBeansConfigurationListener} exists for backward
compatibility
+ * reasons and simply delegates through to the 2 other listeners.
+ *
+ * Note: You only need the separate Begin and End listeners if your
environment
+ * supports injection into ServletListeners and Filters or if you use a
manual
+ * BeanManager lookup in any of these.
+ *
+ * @see EndWebBeansConfigurationListener
+ * @see WebBeansConfigurationListener
+ */
+public class BeginWebBeansConfigurationListener implements
ServletContextListener, ServletRequestListener, HttpSessionListener
+{
+
+/**Logger instance*/
+private static final Logger logger =
WebBeansLoggerFacade.getLogger(WebBeansConfigurationListener.class);
+
+/**Manages the container lifecycle*/
+protected ContainerLifecycle lifeCycle = null;
+
+private WebBeansContext webBeansContext;
+
+/**
+ * Default constructor
+ */
+public BeginWebBeansConfigurationListener()
+{
+webBeansContext = WebBeansContext.getInstance();
+}
+
+/**
+ * Constructor for manual creation
+ */
+public BeginWebBeansConfigurationListener(WebBeansContext
w
Re: svn commit: r1676248 - in /openwebbeans/trunk/webbeans-web/src/main/java: META-INF/ org/apache/webbeans/servlet/
this means this will not work used in tomcat 8 as a normal servlet
container (and potentially jetty, didnt check if spec changed). Said
otherwise - and IIRC - in tomcat 8 begin listener in init phase will be end
listener in destroy phase.
Check org.apache.catalina.core.StandardContext#listenerStop:
for (int i = 0; i < listeners.length; i++) {
int j = (listeners.length - 1) - i
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-27 15:12 GMT+02:00 Mark Struberg :
> This commit does not yet integrate the listeners to our tomcat plugins.
> It just allows the users to configure it separately (Begin+End) or as a
> single one as always (WebBeansConfigurationListener)
>
> But thanks for the tip!
>
> That means we might need to have an own tc8 module?
>
> LieGrue,
> strub
>
> > Am 27.04.2015 um 15:04 schrieb Romain Manni-Bucau >:
> >
> > Hi Mark
> >
> > Did you test on tomcat 8? Blind guess - ie not tested - is it doesnt work
> > cause init/destroy order is logical
> > -- Message transféré --
> > De :
> > Date : 27 avr. 2015 14:59
> > Objet : svn commit: r1676248 - in
> > /openwebbeans/trunk/webbeans-web/src/main/java: META-INF/
> > org/apache/webbeans/servlet/
> > À :
> > Cc :
> >
> > Author: struberg
> > Date: Mon Apr 27 12:59:02 2015
> > New Revision: 1676248
> >
> > URL: http://svn.apache.org/r1676248
> > Log:
> > OWB-1055 Split WebBeansConfigurationListener in Begin and End listeners
> >
> > We need this as the order is the same for all init and destroy methods.
> > But CDI should get init as first listener, but destroyed as last.
> >
> > Added:
> >
> >
> openwebbeans/trunk/webbeans-web/src/main/java/org/apache/webbeans/servlet/BeginWebBeansConfigurationListener.java
> >
> >
> openwebbeans/trunk/webbeans-web/src/main/java/org/apache/webbeans/servlet/EndWebBeansConfigurationListener.java
> > Removed:
> >openwebbeans/trunk/webbeans-web/src/main/java/META-INF/
> > Modified:
> >
> >
> openwebbeans/trunk/webbeans-web/src/main/java/org/apache/webbeans/servlet/WebBeansConfigurationListener.java
> >
> > Added:
> >
> openwebbeans/trunk/webbeans-web/src/main/java/org/apache/webbeans/servlet/BeginWebBeansConfigurationListener.java
> > URL:
> >
> http://svn.apache.org/viewvc/openwebbeans/trunk/webbeans-web/src/main/java/org/apache/webbeans/servlet/BeginWebBeansConfigurationListener.java?rev=1676248&view=auto
> >
> ==
> > ---
> >
> openwebbeans/trunk/webbeans-web/src/main/java/org/apache/webbeans/servlet/BeginWebBeansConfigurationListener.java
> > (added)
> > +++
> >
> openwebbeans/trunk/webbeans-web/src/main/java/org/apache/webbeans/servlet/BeginWebBeansConfigurationListener.java
> > Mon Apr 27 12:59:02 2015
> > @@ -0,0 +1,175 @@
> > +/*
> > + * Licensed to the Apache Software Foundation (ASF) under one
> > + * or more contributor license agreements. See the NOTICE file
> > + * distributed with this work for additional information
> > + * regarding copyright ownership. The ASF licenses this file
> > + * to you under the Apache License, Version 2.0 (the
> > + * "License"); you may not use this file except in compliance
> > + * with the License. You may obtain a copy of the License at
> > + *
> > + * http://www.apache.org/licenses/LICENSE-2.0
> > + *
> > + * Unless required by applicable law or agreed to in writing,
> > + * software distributed under the License is distributed on an
> > + * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
> > + * KIND, either express or implied. See the License for the
> > + * specific language governing permissions and limitations
> > + * under the License.
> > + */
> > +package org.apache.webbeans.servlet;
> > +
> > +import javax.enterprise.context.RequestScoped;
> > +import javax.enterprise.context.SessionScoped;
> > +import javax.servlet.ServletContextEvent;
> > +import javax.servlet.ServletContextListener;
> > +import javax.servlet.ServletRequestEvent;
> > +import javax.servlet.ServletRequestListener;
> > +import javax.servlet.http.HttpSessionEvent;
> > +import javax.servlet.http.HttpSessionListener;
> > +import java.util.logging.Level;
> > +import java.util.logging.Logger;
> > +
> >
next release version
Hi guys, Mark did a lot of rework on conversation scope handling. I would like to go for 1.6.x as base version because of it instead of 1.5.1. Any objection? 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>
Re: next release version
2015-04-30 11:02 GMT+02:00 Mark Struberg : > I’d rather stay with 1.5.1. > > Yes I did lots of changes, but those changes only affect SPI interfaces > which already got marked as deprecated since a long time. Also those > changes do _not_ affect any end users. They just affect integration. And > there is no single released server out there which already uses 1.5.0. So > we are pretty free to change this still as long as we > > 1.5.0 is released even if not integrated in a released server so too late. This is the more nasty changes since they are invisible but impacting (a bit like adding sleep(15000) in a method ;)). > a.) make sure we drop a release soon (which I will) > b.) make sure TomEE still runs. And I will make sure that happens as well. > > For me the 1.5.0 release was kind of ‚pre release‘ to make sure we get > feedback. Again: my changes do _not_ affect any users. > > We should have tagged it pre/alpha/beta/something explicit. That said this is wrong since you use the session (even if you dont want to accept it). To be concrete, suppose the session is clustered with hazelcast using a custom serializer, what happens? can bet in some cases it will not run anymore where before it was fine. > Any further ideas and opinion? > > LieGrue, > strub > > > Am 30.04.2015 um 09:30 schrieb Romain Manni-Bucau >: > > > > Hi guys, > > > > Mark did a lot of rework on conversation scope handling. > > > > I would like to go for 1.6.x as base version because of it instead of > 1.5.1. > > > > Any objection? > > > > 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> > >
BeanAttributesImpl and types
Hi guys, org.apache.webbeans.component.BeanAttributesImpl#BeanAttributesImpl(java.util.Set, java.util.Set, java.lang.Class, java.lang.String, boolean, java.util.Set>, boolean) copies types from bean attributes. It prevents any further changes and https://gist.github.com/antoinesd/3097661ca99fa61900fb becomes not portable (if set is filled before we copy it it works otherwise it is broken) do you think we should just take the input value without any modification? 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>
Re: BeanAttributesImpl and types
PS: alternative is to fix the lifecycle between ProcessBeanAttributes and ProcessInjectionPoint 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-06-01 3:42 GMT+02:00 Romain Manni-Bucau : > Hi guys, > > org.apache.webbeans.component.BeanAttributesImpl#BeanAttributesImpl(java.util.Set, > java.util.Set, java.lang.Class java.lang.annotation.Annotation>, java.lang.String, boolean, > java.util.Set>, > boolean) copies types from bean attributes. It prevents any further changes > and https://gist.github.com/antoinesd/3097661ca99fa61900fb becomes not > portable (if set is filled before we copy it it works otherwise it is > broken) > > do you think we should just take the input value without any modification? > > 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> >
Re: BeanAttributesImpl and types
@Mark: for which of 2 issue? Agree spec is not 100% clean Le 1 juin 2015 00:38, "Mark Struberg" a écrit : > Can you plz create a JIRA issue? > > LieGrue, > strub > > > > Am 01.06.2015 um 03:51 schrieb Romain Manni-Bucau >: > > > > PS: alternative is to fix the lifecycle between ProcessBeanAttributes and > > ProcessInjectionPoint > > > > > > 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-06-01 3:42 GMT+02:00 Romain Manni-Bucau : > > > >> Hi guys, > >> > >> > org.apache.webbeans.component.BeanAttributesImpl#BeanAttributesImpl(java.util.Set, > >> java.util.Set, java.lang.Class extends > >> java.lang.annotation.Annotation>, java.lang.String, boolean, > >> java.util.Set java.lang.annotation.Annotation>>, > >> boolean) copies types from bean attributes. It prevents any further > changes > >> and https://gist.github.com/antoinesd/3097661ca99fa61900fb becomes not > >> portable (if set is filled before we copy it it works otherwise it is > >> broken) > >> > >> do you think we should just take the input value without any > modification? > >> > >> 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> > >> > >
Re: BeanAttributesImpl and types
Le 1 juin 2015 00:58, "Mark Struberg" a écrit : > > No, it’s even explicitly in the spec that it is NOT the case ;) > > Read 12.4.3. Bean discovery > „For every type in the set of discovered types (as defined in Section 12.4.1, “Type discovery”), the container must: > • if the class is a managed bean, session bean, or other Java EE component class supporting injection, fire an event of type ProcessInjectionPoint for each injection point in the class, as defined in Section 11.5.7, “ProcessInjectionPoint event”, and THEN > • if the class is a managed bean, session bean, or other Java EE component class supporting injection, fire an event of type ProcessInjectionTarget, as defined in Section 11.5.8, “ProcessInjectionTarget event”, and then > • determine which alternatives, interceptors and decorators are enabled, according to the rules defined in Section 5.1.2, “Enabled and disabled beans”, Section 9.4, “Interceptor enablement and ordering” and Section 8.2, “Decorator enablement and ordering”, and THEN > • if the class is an enabled bean, interceptor or decorator, fire an event of type ProcessBeanAttributes, as defined in Section 11.5.9, “ProcessBeanAttributes event”, and THEN > … > > „So the CDI spec CLEARLY specifies that the whole loop is ‚for every type in the set of discovered types, THEN THEN THEN“ > That is your interpretation. The bucket one still matches it. > OWB impls it exactly as it is specified. > > So this usecase is rather illegal. > > LieGrue, > strub > > > Am 01.06.2015 um 09:18 schrieb Arne Limburg < arne.limb...@openknowledge.de>: > > > > Hmm, I think we discussed this in the past. > > The problem is, that the spec does not clearly state whether all > > ProcessInjectionPoint-Events have to be fired before the first > > ProcessBeanAttributes-Event. Weld does so, we donąt (we fire them bean by > > bean). > > I donąt think, our way is wrong from the spec point of view. If it is, we > > should fix it. Otherwise I tend to say, that the extension is not portable. > > > > Cheers, > > Arne > > > > > > Am 01.06.15 03:51 schrieb "Romain Manni-Bucau" unter > > : > > > >> PS: alternative is to fix the lifecycle between ProcessBeanAttributes and > >> ProcessInjectionPoint > >> > >> > >> 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-06-01 3:42 GMT+02:00 Romain Manni-Bucau : > >> > >>> Hi guys, > >>> > >>> > >>> org.apache.webbeans.component.BeanAttributesImpl#BeanAttributesImpl(java. > >>> util.Set, > >>> java.util.Set, java.lang.Class >>> extends > >>> java.lang.annotation.Annotation>, java.lang.String, boolean, > >>> java.util.Set >>> java.lang.annotation.Annotation>>, > >>> boolean) copies types from bean attributes. It prevents any further > >>> changes > >>> and https://gist.github.com/antoinesd/3097661ca99fa61900fb becomes not > >>> portable (if set is filled before we copy it it works otherwise it is > >>> broken) > >>> > >>> do you think we should just take the input value without any > >>> modification? > >>> > >>> 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> > >>> > > >
Re: BeanAttributesImpl and types
Ok Originally come with copy one (which is fine) So do we keep it this way finally? Sounds like yes Le 1 juin 2015 01:58, "Mark Struberg" a écrit : > > what is the 2nd issue? > > The one I mean is that the scanned classes are processed one after the other (as specified). But the sample code relies on ProcessInjectionPoint of ALL classes gets scanned before the first ProcessBeanAttributes get fired. > > LieGrue, > strub > > > > Am 01.06.2015 um 09:58 schrieb Romain Manni-Bucau : > > > > @Mark: for which of 2 issue? > > > > Agree spec is not 100% clean > > Le 1 juin 2015 00:38, "Mark Struberg" a écrit : > > > >> Can you plz create a JIRA issue? > >> > >> LieGrue, > >> strub > >> > >> > >>> Am 01.06.2015 um 03:51 schrieb Romain Manni-Bucau < rmannibu...@gmail.com > >>> : > >>> > >>> PS: alternative is to fix the lifecycle between ProcessBeanAttributes and > >>> ProcessInjectionPoint > >>> > >>> > >>> 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-06-01 3:42 GMT+02:00 Romain Manni-Bucau : > >>> > >>>> Hi guys, > >>>> > >>>> > >> org.apache.webbeans.component.BeanAttributesImpl#BeanAttributesImpl(java.util.Set, > >>>> java.util.Set, java.lang.Class >> extends > >>>> java.lang.annotation.Annotation>, java.lang.String, boolean, > >>>> java.util.Set >> java.lang.annotation.Annotation>>, > >>>> boolean) copies types from bean attributes. It prevents any further > >> changes > >>>> and https://gist.github.com/antoinesd/3097661ca99fa61900fb becomes not > >>>> portable (if set is filled before we copy it it works otherwise it is > >>>> broken) > >>>> > >>>> do you think we should just take the input value without any > >> modification? > >>>> > >>>> 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> > >>>> > >> > >> >
Re: Releasing OWB-1.6.0 _now_
hehe when Mark says now it means he is running release:perform ;) 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-06-01 8:25 GMT-07:00 Jean-Louis MONTEIRO : > Nope, go ahead. Thanks > > Le lun. 1 juin 2015 à 16:25, Mark Struberg a écrit : > > > please shout NOW if you are still missing something ;) > > > > LIeGrue, > > strub > > >
Re: [VOTE] Release Apache OpenWebBeans-1.6.0
+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-06-01 17:29 GMT+02:00 Mark Struberg :
> 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…
interceptors and interfaces
Hi guys, in openejb we support EJB without implementation using something like @PartialBean of deltaspike. The issue is then openwebbeans is not able to support interceptors/decorators on them cause the proxies created are not correct (instance var for interface "subclass" etc) Do we want to fix it - the feature is quite not in the spec? 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>
Re: interceptors and interfaces
guess we would need to either generate a faked class to proxy or to use a plain old proxy (ie redefine InvocationHandlers) 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-06-09 12:44 GMT-07:00 Thomas Andraschko : > +0 but why not? is it a big deal? > > 2015-06-08 0:39 GMT+02:00 Romain Manni-Bucau : > > > Hi guys, > > > > in openejb we support EJB without implementation using something like > > @PartialBean of deltaspike. > > > > The issue is then openwebbeans is not able to support > > interceptors/decorators on them cause the proxies created are not correct > > (instance var for interface "subclass" etc) > > > > Do we want to fix it - the feature is quite not in the spec? > > > > 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> > > >
Re: [VOTE] for Apache OpenWebBeans 1.6.1
+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-06-16 8:10 GMT+02:00 Mark Struberg :
> 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
>
>
Re: release owb-1.6.2?
+1 and a big thank you to drive it! 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-07-29 1:44 GMT-07:00 Mark Struberg : > hi! > we've fixed a few issues and tomee needs owb for tomee-7.x. > All fine if I gonna roll a release today? > LieGrue,strub > >
Re: [VOTE] Release OpenWebBeans-1.6.2
+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-08-07 14:22 GMT-07:00 Daniel Cunha :
> +1
>
> On Fri, Aug 7, 2015 at 5:03 PM, Mark Struberg wrote:
>
> > 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
> >
>
>
>
> --
> Best regard,
> Daniel Cunha (soro)
>
Re: starting with CDI-2.0?
Cant guarantee to help a lot now but +1. Would be nice to not identify spec issues too late. Le 11 août 2015 05:31, "Gerhard Petracek" a écrit : > +1 > > regards, > gerhard > > > > 2015-08-11 13:58 GMT+02:00 Mark Struberg : > > > 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: starting with CDI-2.0?
Think we have enough G guys to avoid the cp but no issues bringing it in owb for now. Le 17 août 2015 03:18, "Mark Struberg" a écrit : > The question now is whether we should svn cp the geronimo-jcdi-1.1 package > back to owb and maintain it here until it is reasonably stable (and then > svn mv it back to geronimo)? > Or should we keep it there and just create a new geronimo-jcdi-2.0 package > in geronimo-specs? > > Both is technically the same as we can svn cp back and forth without > loosing any history. > > LieGrue, > strub > > > > Am 17.08.2015 um 11:04 schrieb Jean-Louis MONTEIRO : > > > > +2 lol > > > > Le lun. 17 août 2015 à 10:59, Arne Limburg < > arne.limb...@openknowledge.de> > > a écrit : > > > >> +1 > >> I hope, I¹ll find some time to help > >> > >> > >> Am 11.08.15 15:05 schrieb "Romain Manni-Bucau" unter > >> : > >> > >>> Cant guarantee to help a lot now but +1. Would be nice to not identify > >>> spec > >>> issues too late. > >>> Le 11 août 2015 05:31, "Gerhard Petracek" > a > >>> écrit : > >>> > >>>> +1 > >>>> > >>>> regards, > >>>> gerhard > >>>> > >>>> > >>>> > >>>> 2015-08-11 13:58 GMT+02:00 Mark Struberg : > >>>> > >>>>> 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: Bean scanning exclude list
Hi Thomas Here is the tomee list https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/resources/default.exclusions Slows down a bit when you dont have the jar but makes a diff when you have them. For owb having a prop in owb.properties is the way I d go. A bit like tomcat jarSkip property. Le 23 sept. 2015 02:47, "Thomas Andraschko" a écrit : > Hi, > > i would like to enhance our "known jar" list in AbstractMetaDataDiscovery > with the following items: > > "/bcprov-jdk14-", > "/bcmail-jdk14-", > "/bctsp-jdk14-", > "/bcmail-jdk14-", > "/ss_css2-", > "/itext-", > "/pd4ml-", > "/xmlpull-", > "/log4j-", > "/slf4j-", > "/gson-", > "/xstream-", > "/httpclient-", > "/httpcore-", > "/backport-util-concurrent-", > "/xml-apis", > "/xpp3_min-" > > adding this excludes reduces the OWB startup time in my application about > 500-1000ms. > WDYT? > > I'm not sure if we should also exclude bval and juel? > > Regards, > Thomas >
Fwd: svn commit: r1704889 - in /openwebbeans/trunk/webbeans-impl/src/main: java/org/apache/webbeans/config/ java/org/apache/webbeans/corespi/scanner/ resources/META-INF/openwebbeans/
really a detail but can we name it jarExclusions or something like that? beanScanningExcludes sounds close to what we have in beans.xml for me since CDI 1.1 - ie exclude classes and not jars. Is it only me? is it relevant? 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> -- Forwarded message -- From: Date: 2015-09-23 9:06 GMT-07:00 Subject: svn commit: r1704889 - in /openwebbeans/trunk/webbeans-impl/src/main: java/org/apache/webbeans/config/ java/org/apache/webbeans/corespi/scanner/ resources/META-INF/openwebbeans/ To: comm...@openwebbeans.apache.org Author: tandraschko Date: Wed Sep 23 16:06:29 2015 New Revision: 1704889 URL: http://svn.apache.org/viewvc?rev=1704889&view=rev Log: OWB-1094 Move bean scanning excludes to openwebbeans.properties Modified: openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/config/OpenWebBeansConfiguration.java openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/corespi/scanner/AbstractMetaDataDiscovery.java openwebbeans/trunk/webbeans-impl/src/main/resources/META-INF/openwebbeans/openwebbeans.properties Modified: openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/config/OpenWebBeansConfiguration.java URL: http://svn.apache.org/viewvc/openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/config/OpenWebBeansConfiguration.java?rev=1704889&r1=1704888&r2=1704889&view=diff == --- openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/config/OpenWebBeansConfiguration.java (original) +++ openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/config/OpenWebBeansConfiguration.java Wed Sep 23 16:06:29 2015 @@ -33,7 +33,7 @@ import org.apache.webbeans.logger.WebBea /** * Defines configuration for OpenWebBeans. - * + * * The algorithm is easy: * * Load all properties you can find with the name (META-INF/openwebbeans/openwebbeans.properties), @@ -51,7 +51,7 @@ public class OpenWebBeansConfiguration /**Conversation periodic delay in ms.*/ public static final String CONVERSATION_PERIODIC_DELAY = "org.apache.webbeans.conversation.Conversation.periodicDelay"; - + /**Timeout interval in ms*/ public static final String CONVERSATION_TIMEOUT_INTERVAL = "org.apache.webbeans.conversation.Conversation.timeoutInterval"; @@ -65,34 +65,34 @@ public class OpenWebBeansConfiguration /**Use EJB Discovery or not*/ public static final String USE_EJB_DISCOVERY = "org.apache.webbeans.spi.deployer.useEjbMetaDataDiscoveryService"; - + /**Container lifecycle*/ public static final String CONTAINER_LIFECYCLE = "org.apache.webbeans.spi.ContainerLifecycle"; - + /**JNDI Service SPI*/ -public static final String JNDI_SERVICE = "org.apache.webbeans.spi.JNDIService"; - +public static final String JNDI_SERVICE = "org.apache.webbeans.spi.JNDIService"; + /**Scanner Service*/ public static final String SCANNER_SERVICE = "org.apache.webbeans.spi.ScannerService"; /**Contexts Service*/ public static final String CONTEXTS_SERVICE = "org.apache.webbeans.spi.ContextsService"; - + /**Conversation Service*/ public static final String CONVERSATION_SERVICE = "org.apache.webbeans.spi.ConversationService"; - + /**Resource Injection Service*/ public static final String RESOURCE_INJECTION_SERVICE = "org.apache.webbeans.spi.ResourceInjectionService"; - + /**Security Service*/ public static final String SECURITY_SERVICE = "org.apache.webbeans.spi.SecurityService"; - + /**Validator Service*/ public static final String VALIDATOR_SERVICE = "org.apache.webbeans.spi.ValidatorService"; - + /**Transaction Service*/ public static final String TRANSACTION_SERVICE = "org.apache.webbeans.spi.TransactionService"; - + /**Application is core JSP*/ public static final String APPLICATION_IS_JSP = "org.apache.webbeans.application.jsp"; @@ -117,6 +117,9 @@ public class OpenWebBeansConfiguration **/ public static final String USE_BDA_BEANSXML_SCANNER = "org.apache.webbeans.useBDABeansXMLScanner"; +/** A list of known JARs/pathes which should not be scanned for beans */ +public static final String BEAN_SCANNING_EXCLUDES = "org.apache.webbeans.beanScanningExcludes"; + /** * a comma-separated list of fully qualified class names that should be ignored * when determining if a decorator matches its delegate. These are typically added by @@ -254,7 +257,7 @@ public class OpenWebBeansConfiguration
Re: svn commit: r1704889 - in /openwebbeans/trunk/webbeans-impl/src/main: java/org/apache/webbeans/config/ java/org/apache/webbeans/corespi/scanner/ resources/META-INF/openwebbeans/
dont want to fight on path (even if strictly speaking we just handle names right?) but looks clearly less misleading :) 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-09-23 10:06 GMT-07:00 Thomas Andraschko : > sure, why not. I thought the same but it's actually something like > "pathAndJarExclusion". > WDYT? > > > 2015-09-23 18:15 GMT+02:00 Romain Manni-Bucau : > > > really a detail but can we name it jarExclusions or something like that? > > > > beanScanningExcludes sounds close to what we have in beans.xml for me > since > > CDI 1.1 - ie exclude classes and not jars. Is it only me? is it relevant? > > > > 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> > > > > -- Forwarded message -- > > From: > > Date: 2015-09-23 9:06 GMT-07:00 > > Subject: svn commit: r1704889 - in > > /openwebbeans/trunk/webbeans-impl/src/main: > > java/org/apache/webbeans/config/ > java/org/apache/webbeans/corespi/scanner/ > > resources/META-INF/openwebbeans/ > > To: comm...@openwebbeans.apache.org > > > > > > Author: tandraschko > > Date: Wed Sep 23 16:06:29 2015 > > New Revision: 1704889 > > > > URL: http://svn.apache.org/viewvc?rev=1704889&view=rev > > Log: > > OWB-1094 Move bean scanning excludes to openwebbeans.properties > > > > Modified: > > > > > > > openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/config/OpenWebBeansConfiguration.java > > > > > > > openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/corespi/scanner/AbstractMetaDataDiscovery.java > > > > > > > openwebbeans/trunk/webbeans-impl/src/main/resources/META-INF/openwebbeans/openwebbeans.properties > > > > Modified: > > > > > openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/config/OpenWebBeansConfiguration.java > > URL: > > > > > http://svn.apache.org/viewvc/openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/config/OpenWebBeansConfiguration.java?rev=1704889&r1=1704888&r2=1704889&view=diff > > > > > == > > --- > > > > > openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/config/OpenWebBeansConfiguration.java > > (original) > > +++ > > > > > openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/config/OpenWebBeansConfiguration.java > > Wed Sep 23 16:06:29 2015 > > @@ -33,7 +33,7 @@ import org.apache.webbeans.logger.WebBea > > > > /** > > * Defines configuration for OpenWebBeans. > > - * > > + * > > * The algorithm is easy: > > * > > * Load all properties you can find with the name > > (META-INF/openwebbeans/openwebbeans.properties), > > @@ -51,7 +51,7 @@ public class OpenWebBeansConfiguration > > > > /**Conversation periodic delay in ms.*/ > > public static final String CONVERSATION_PERIODIC_DELAY = > > "org.apache.webbeans.conversation.Conversation.periodicDelay"; > > - > > + > > /**Timeout interval in ms*/ > > public static final String CONVERSATION_TIMEOUT_INTERVAL = > > "org.apache.webbeans.conversation.Conversation.timeoutInterval"; > > > > @@ -65,34 +65,34 @@ public class OpenWebBeansConfiguration > > > > /**Use EJB Discovery or not*/ > > public static final String USE_EJB_DISCOVERY = > > "org.apache.webbeans.spi.deployer.useEjbMetaDataDiscoveryService"; > > - > > + > > /**Container lifecycle*/ > > public static final String CONTAINER_LIFECYCLE = > > "org.apache.webbeans.spi.ContainerLifecycle"; > > - > > + > > /**JNDI Service SPI*/ > > -public static final String JNDI_SERVICE = > > "org.apache.webbeans.spi.JNDIService"; > > - > > +public static final String JNDI_SERVICE = > > "org.apache.webbeans.spi.JNDIService"; > > + > > /**Scanner Service*/ > > public static final String SCANNER_SERVICE = > >
Re: svn commit: r1704889 - in /openwebbeans/trunk/webbeans-impl/src/main: java/org/apache/webbeans/config/ java/org/apache/webbeans/corespi/scanner/ resources/META-INF/openwebbeans/
both work for me, pick the one you prefer :) 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-09-23 10:42 GMT-07:00 Thomas Andraschko : > What about scanExclusionPaths? > Otherwise lets go with jarExcludes :) > > 2015-09-23 19:22 GMT+02:00 Romain Manni-Bucau : > > > dont want to fight on path (even if strictly speaking we just handle > names > > right?) but looks clearly less misleading :) > > > > > > 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-09-23 10:06 GMT-07:00 Thomas Andraschko < > andraschko.tho...@gmail.com > > >: > > > > > sure, why not. I thought the same but it's actually something like > > > "pathAndJarExclusion". > > > WDYT? > > > > > > > > > 2015-09-23 18:15 GMT+02:00 Romain Manni-Bucau : > > > > > > > really a detail but can we name it jarExclusions or something like > > that? > > > > > > > > beanScanningExcludes sounds close to what we have in beans.xml for me > > > since > > > > CDI 1.1 - ie exclude classes and not jars. Is it only me? is it > > relevant? > > > > > > > > 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> > > > > > > > > -- Forwarded message -- > > > > From: > > > > Date: 2015-09-23 9:06 GMT-07:00 > > > > Subject: svn commit: r1704889 - in > > > > /openwebbeans/trunk/webbeans-impl/src/main: > > > > java/org/apache/webbeans/config/ > > > java/org/apache/webbeans/corespi/scanner/ > > > > resources/META-INF/openwebbeans/ > > > > To: comm...@openwebbeans.apache.org > > > > > > > > > > > > Author: tandraschko > > > > Date: Wed Sep 23 16:06:29 2015 > > > > New Revision: 1704889 > > > > > > > > URL: http://svn.apache.org/viewvc?rev=1704889&view=rev > > > > Log: > > > > OWB-1094 Move bean scanning excludes to openwebbeans.properties > > > > > > > > Modified: > > > > > > > > > > > > > > > > > > openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/config/OpenWebBeansConfiguration.java > > > > > > > > > > > > > > > > > > openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/corespi/scanner/AbstractMetaDataDiscovery.java > > > > > > > > > > > > > > > > > > openwebbeans/trunk/webbeans-impl/src/main/resources/META-INF/openwebbeans/openwebbeans.properties > > > > > > > > Modified: > > > > > > > > > > > > > > openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/config/OpenWebBeansConfiguration.java > > > > URL: > > > > > > > > > > > > > > http://svn.apache.org/viewvc/openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/config/OpenWebBeansConfiguration.java?rev=1704889&r1=1704888&r2=1704889&view=diff > > > > > > > > > > > > > > == > > > > --- > > > > > > > > > > > > > > openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/config/OpenWebBeansConfiguration.java > > > > (original) > > > > +++ > > > > > > > > > > > > > > openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/config/OpenWebBeansConfiguration.java > > > > Wed Sep 23 16:06:29 2015 > > > > @@ -33,7 +33,7 @@ import org.apache.webbeans.logger.WebBea > > > > > > > > /** > > > > * Defines configuration for OpenWebBeans. &g
Re: Unify project names in poms
If you speak about mvn +1. BTW I like [:: ]* pattern: Apache OpenWebBeans Apache OpenWebBeans :: Core Apache OpenWebBeans :: Web Apache OpenWebBeans :: JSF 2.2 ... 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-10-26 19:36 GMT+01:00 Thomas Andraschko : > Hi, > > WDYT about unify the project names in the poms? > DeltaSpike and MyFaces always prepends "Apache" and the project name. > e.g. > > Apache MyFaces JSF2.2 Core API > Apache MyFaces JSF2.2 Core Impl > > Apache DeltaSpike Parent > Apache DeltaSpike Modules > ... > > In OWB it's: > OpenWebBeans Core > Tomcat 7 Plugin > EL 2.2 Plugin > > It's just a little bit annoying in the IDE... > > Regards, > Thomas >
Re: Unify project names in poms
TomEE, Sirona, BatchEE, JCS, Johnzon, XBean to cite a few 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-10-26 19:56 GMT+01:00 Thomas Andraschko : > yep, it's about mvn :) > > +0 > Where is this pattern used? > > 2015-10-26 19:41 GMT+01:00 Romain Manni-Bucau : > > > If you speak about mvn +1. > > > > BTW I like [:: ]* pattern: > > > > Apache OpenWebBeans > > Apache OpenWebBeans :: Core > > Apache OpenWebBeans :: Web > > Apache OpenWebBeans :: JSF 2.2 > > ... > > > > > > > > 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-10-26 19:36 GMT+01:00 Thomas Andraschko < > andraschko.tho...@gmail.com > > >: > > > > > Hi, > > > > > > WDYT about unify the project names in the poms? > > > DeltaSpike and MyFaces always prepends "Apache" and the project name. > > > e.g. > > > > > > Apache MyFaces JSF2.2 Core API > > > Apache MyFaces JSF2.2 Core Impl > > > > > > Apache DeltaSpike Parent > > > Apache DeltaSpike Modules > > > ... > > > > > > In OWB it's: > > > OpenWebBeans Core > > > Tomcat 7 Plugin > > > EL 2.2 Plugin > > > > > > It's just a little bit annoying in the IDE... > > > > > > Regards, > > > Thomas > > > > > >
Re: Unify project names in poms
Any separator works but it is nice to not just keep everything inlined without hierarchy marker for multi module projects. 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-10-26 20:20 GMT+01:00 Thomas Andraschko : > oh, i see. > Doesn't matter for me, for me it's usual without "::" :) > > > 2015-10-26 20:11 GMT+01:00 Romain Manni-Bucau : > > > TomEE, Sirona, BatchEE, JCS, Johnzon, XBean to cite a few > > > > > > 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-10-26 19:56 GMT+01:00 Thomas Andraschko < > andraschko.tho...@gmail.com > > >: > > > > > yep, it's about mvn :) > > > > > > +0 > > > Where is this pattern used? > > > > > > 2015-10-26 19:41 GMT+01:00 Romain Manni-Bucau : > > > > > > > If you speak about mvn +1. > > > > > > > > BTW I like [:: ]* pattern: > > > > > > > > Apache OpenWebBeans > > > > Apache OpenWebBeans :: Core > > > > Apache OpenWebBeans :: Web > > > > Apache OpenWebBeans :: JSF 2.2 > > > > ... > > > > > > > > > > > > > > > > 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-10-26 19:36 GMT+01:00 Thomas Andraschko < > > > andraschko.tho...@gmail.com > > > > >: > > > > > > > > > Hi, > > > > > > > > > > WDYT about unify the project names in the poms? > > > > > DeltaSpike and MyFaces always prepends "Apache" and the project > name. > > > > > e.g. > > > > > > > > > > Apache MyFaces JSF2.2 Core API > > > > > Apache MyFaces JSF2.2 Core Impl > > > > > > > > > > Apache DeltaSpike Parent > > > > > Apache DeltaSpike Modules > > > > > ... > > > > > > > > > > In OWB it's: > > > > > OpenWebBeans Core > > > > > Tomcat 7 Plugin > > > > > EL 2.2 Plugin > > > > > > > > > > It's just a little bit annoying in the IDE... > > > > > > > > > > Regards, > > > > > Thomas > > > > > > > > > > > > > > >
Re: Unify project names in poms
Guess it is subjective enough to not do a long thread on this. We just need to avoid to change them each week ;). Le 26 oct. 2015 20:52, "Thomas Andraschko" a écrit : > Yep, you'r right but it still looks good in OWB -> > http://s2.postimg.org/a2b8x7e2x/asd.png > > > 2015-10-26 20:25 GMT+01:00 Romain Manni-Bucau : > > > Any separator works but it is nice to not just keep everything inlined > > without hierarchy marker for multi module projects. > > > > > > 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-10-26 20:20 GMT+01:00 Thomas Andraschko < > andraschko.tho...@gmail.com > > >: > > > > > oh, i see. > > > Doesn't matter for me, for me it's usual without "::" :) > > > > > > > > > 2015-10-26 20:11 GMT+01:00 Romain Manni-Bucau : > > > > > > > TomEE, Sirona, BatchEE, JCS, Johnzon, XBean to cite a few > > > > > > > > > > > > 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-10-26 19:56 GMT+01:00 Thomas Andraschko < > > > andraschko.tho...@gmail.com > > > > >: > > > > > > > > > yep, it's about mvn :) > > > > > > > > > > +0 > > > > > Where is this pattern used? > > > > > > > > > > 2015-10-26 19:41 GMT+01:00 Romain Manni-Bucau < > rmannibu...@gmail.com > > >: > > > > > > > > > > > If you speak about mvn +1. > > > > > > > > > > > > BTW I like [:: ]* pattern: > > > > > > > > > > > > Apache OpenWebBeans > > > > > > Apache OpenWebBeans :: Core > > > > > > Apache OpenWebBeans :: Web > > > > > > Apache OpenWebBeans :: JSF 2.2 > > > > > > ... > > > > > > > > > > > > > > > > > > > > > > > > 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-10-26 19:36 GMT+01:00 Thomas Andraschko < > > > > > andraschko.tho...@gmail.com > > > > > > >: > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > WDYT about unify the project names in the poms? > > > > > > > DeltaSpike and MyFaces always prepends "Apache" and the project > > > name. > > > > > > > e.g. > > > > > > > > > > > > > > Apache MyFaces JSF2.2 Core API > > > > > > > Apache MyFaces JSF2.2 Core Impl > > > > > > > > > > > > > > Apache DeltaSpike Parent > > > > > > > Apache DeltaSpike Modules > > > > > > > ... > > > > > > > > > > > > > > In OWB it's: > > > > > > > OpenWebBeans Core > > > > > > > Tomcat 7 Plugin > > > > > > > EL 2.2 Plugin > > > > > > > > > > > > > > It's just a little bit annoying in the IDE... > > > > > > > > > > > > > > Regards, > > > > > > > Thomas > > > > > > > > > > > > > > > > > > > > > > > > > > > >
Re: Unify project names in poms
IMO it makes the build more readable and human friendly. That said why not just voting. Dont think we need to spend weeks on this topic. Le 27 oct. 2015 09:29, "Mark Struberg" a écrit : > -1 for having in poms at all. In practice it makes finding the > right submodule just too hard if you don’t know the project. And if you do > then you don’t need it anyway. > > LieGrue, > strub > > > > Am 26.10.2015 um 21:16 schrieb Romain Manni-Bucau >: > > > > Guess it is subjective enough to not do a long thread on this. We just > need > > to avoid to change them each week ;). > > Le 26 oct. 2015 20:52, "Thomas Andraschko" > a > > écrit : > > > >> Yep, you'r right but it still looks good in OWB -> > >> http://s2.postimg.org/a2b8x7e2x/asd.png > >> > >> > >> 2015-10-26 20:25 GMT+01:00 Romain Manni-Bucau : > >> > >>> Any separator works but it is nice to not just keep everything inlined > >>> without hierarchy marker for multi module projects. > >>> > >>> > >>> 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-10-26 20:20 GMT+01:00 Thomas Andraschko < > >> andraschko.tho...@gmail.com > >>>> : > >>> > >>>> oh, i see. > >>>> Doesn't matter for me, for me it's usual without "::" :) > >>>> > >>>> > >>>> 2015-10-26 20:11 GMT+01:00 Romain Manni-Bucau >: > >>>> > >>>>> TomEE, Sirona, BatchEE, JCS, Johnzon, XBean to cite a few > >>>>> > >>>>> > >>>>> 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-10-26 19:56 GMT+01:00 Thomas Andraschko < > >>>> andraschko.tho...@gmail.com > >>>>>> : > >>>>> > >>>>>> yep, it's about mvn :) > >>>>>> > >>>>>> +0 > >>>>>> Where is this pattern used? > >>>>>> > >>>>>> 2015-10-26 19:41 GMT+01:00 Romain Manni-Bucau < > >> rmannibu...@gmail.com > >>>> : > >>>>>> > >>>>>>> If you speak about mvn +1. > >>>>>>> > >>>>>>> BTW I like [:: ]* pattern: > >>>>>>> > >>>>>>> Apache OpenWebBeans > >>>>>>> Apache OpenWebBeans :: Core > >>>>>>> Apache OpenWebBeans :: Web > >>>>>>> Apache OpenWebBeans :: JSF 2.2 > >>>>>>> ... > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> 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-10-26 19:36 GMT+01:00 Thomas Andraschko < > >>>>>> andraschko.tho...@gmail.com > >>>>>>>> : > >>>>>>> > >>>>>>>> Hi, > >>>>>>>> > >>>>>>>> WDYT about unify the project names in the poms? > >>>>>>>> DeltaSpike and MyFaces always prepends "Apache" and the project > >>>> name. > >>>>>>>> e.g. > >>>>>>>> > >>>>>>>> Apache MyFaces JSF2.2 Core API > >>>>>>>> Apache MyFaces JSF2.2 Core Impl > >>>>>>>> > >>>>>>>> Apache DeltaSpike Parent > >>>>>>>> Apache DeltaSpike Modules > >>>>>>>> ... > >>>>>>>> > >>>>>>>> In OWB it's: > >>>>>>>> OpenWebBeans Core > >>>>>>>> Tomcat 7 Plugin > >>>>>>>> EL 2.2 Plugin > >>>>>>>> > >>>>>>>> It's just a little bit annoying in the IDE... > >>>>>>>> > >>>>>>>> Regards, > >>>>>>>> Thomas > >>>>>>>> > >>>>>>> > >>>>>> > >>>>> > >>>> > >>> > >> > >
Re: Clean up unused coversations
Hi Emily, conversations are now in the session so when the session is evicted conversations are so no need of our own scheduler. 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-12-04 14:53 GMT+01:00 Emily Jiang : > Hi Mark, > > I noticed this https://issues.apache.org/jira/browse/OWB-1050. Am I > correct > to say that this jira removes the support for > org.apache.webbeans.conversation.Conversation.periodicDelay, which means > from OWB 1.6, this property does not work any more? If yes, can you please > explain why you need to remove this facility? > > -- > Thanks > Emily > = > Emily Jiang > eji...@apache.org >
Re: [DISCUSS] board report OWB-2015-12
looks good 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-12-11 9:47 GMT+01:00 Mark Struberg : > Hi folks! > > Please review the prepared board report. > Would like to ship it this evening > > - > ## Description: > Apache OpenWebBeans is an ALv2-licensed implementations of the > "Contexts and Dependency Injection for the Java EE platform" > specification which is defined as JSR-299 (CDI-1.0) and CDI-1.1 and > CDI-1.2 (MR) > specifications (JSR-346). > > ## Issues: > there are no issues requiring board attention at this time > > ## Activity: > Activity is ok. We did start with CDI-2.0 and fixed a few bugs. > We currently prepare for new maintenance releases. > > ## Health report: > The project is a container library which is stable and actively > used and maintained. Due to the fact that most users are using > OWB as part of another project (e.g. TomEE) we get much feedback > in 'indirect' ways. > > > ## PMC changes: > > - Currently 12 PMC members. > - No new PMC members added in the last 3 months > - Last PMC addition was Thomas Andraschko on Wed May 28 2014 > > ## Committer base changes: > > - Currently 19 committers. > - No new committers added in the last 3 months > - Last committer addition was Reinhard Sandtner at Fri Sep 26 2014 > > ## Releases: > > - Last release was 1.6.2 on Tue Aug 11 2015 > - We are currently preparing releases for 1.6.x and 1.2.x > > ## Mailing list activity: > > - dev@openwebbeans.apache.org: > - 66 subscribers (up 1 in the last 3 months): > - 98 emails sent to list (136 in previous quarter) > > - u...@openwebbeans.apache.org: > - 90 subscribers (up 0 in the last 3 months): > - 8 emails sent to list (17 in previous quarter) > > > ## JIRA activity: > > - 11 JIRA tickets created in the last 3 months > - 6 JIRA tickets closed/resolved in the last 3 months > > > —— > > txs and LieGrue, > strub
Object#method and proxies
Hi guys, ATM we dont proxy methods in Objects (ie normalScope.toString()) will do a toString on the proxy - see org.apache.webbeans.proxy.SubclassProxyFactory#delegateNonInterceptedMethods. This is fine by itself but then how to enforce the eager init of a bean in a reliable manner? Side note: you probably all know the @CdiStartup extension relying on toString() in after validation event callback and the code I used - and which fails - was pretty close to that. FYI I tested only on 1.2.7 but code didnt change much in 1.2.x branch I think. Any input/idea? 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>
Re: Object#method and proxies
It is undefined AFAIK or ambiguous since we pass TCK anyway. Le 19 déc. 2015 13:42, "Thomas Andraschko" a écrit : > Hi, > > shoudln't toString call the original toString method of the contextual > instance? > > 2015-12-18 20:13 GMT+01:00 Romain Manni-Bucau : > > > Hi guys, > > > > ATM we dont proxy methods in Objects (ie normalScope.toString()) will do > a > > toString on the proxy - see > > > > > org.apache.webbeans.proxy.SubclassProxyFactory#delegateNonInterceptedMethods. > > > > This is fine by itself but then how to enforce the eager init of a bean > in > > a reliable manner? > > > > Side note: you probably all know the @CdiStartup extension relying on > > toString() in after validation event callback and the code I used - and > > which fails - was pretty close to that. > > > > FYI I tested only on 1.2.7 but code didnt change much in 1.2.x branch I > > think. > > > > Any input/idea? > > > > 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> > > >
Re: Object#method and proxies
Thought it was cause causing delegate init even in debug dtatement when context was not there. But not sure how to solve the "issue". Le 19 déc. 2015 16:19, "Mark Struberg" a écrit : > We had this in 1.1.x and I remember there was a reason why we removed it. > Think it was either because it was slow or because spec/tck forced us. Not > sure anymore. > You could grab through the changes in svn. > > LieGrue, > strub > > > > Am 19.12.2015 um 13:56 schrieb Romain Manni-Bucau >: > > > > It is undefined AFAIK or ambiguous since we pass TCK anyway. > > Le 19 déc. 2015 13:42, "Thomas Andraschko" > a > > écrit : > > > >> Hi, > >> > >> shoudln't toString call the original toString method of the contextual > >> instance? > >> > >> 2015-12-18 20:13 GMT+01:00 Romain Manni-Bucau : > >> > >>> Hi guys, > >>> > >>> ATM we dont proxy methods in Objects (ie normalScope.toString()) will > do > >> a > >>> toString on the proxy - see > >>> > >>> > >> > org.apache.webbeans.proxy.SubclassProxyFactory#delegateNonInterceptedMethods. > >>> > >>> This is fine by itself but then how to enforce the eager init of a bean > >> in > >>> a reliable manner? > >>> > >>> Side note: you probably all know the @CdiStartup extension relying on > >>> toString() in after validation event callback and the code I used - and > >>> which fails - was pretty close to that. > >>> > >>> FYI I tested only on 1.2.7 but code didnt change much in 1.2.x branch I > >>> think. > >>> > >>> Any input/idea? > >>> > >>> 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> > >>> > >> > >
Re: Object#method and proxies
Le 19 déc. 2015 17:00, "Matt Benson" a écrit : > > On Dec 19, 2015 9:54 AM, "Romain Manni-Bucau" wrote: > > > > Thought it was cause causing delegate init even in debug dtatement when > > context was not there. > > > > But not sure how to solve the "issue". > > I'm not familiar with the code, but it would seem that you could delegate > #toString() any time the proxy already exists. Getting back to the eager > initialization problem, would an additional introduced interface help? > Another API no but we cant really know since the context is user dependent. > Matt > > > Le 19 déc. 2015 16:19, "Mark Struberg" a écrit : > > > > > We had this in 1.1.x and I remember there was a reason why we removed > it. > > > Think it was either because it was slow or because spec/tck forced us. > Not > > > sure anymore. > > > You could grab through the changes in svn. > > > > > > LieGrue, > > > strub > > > > > > > > > > Am 19.12.2015 um 13:56 schrieb Romain Manni-Bucau < > rmannibu...@gmail.com > > > >: > > > > > > > > It is undefined AFAIK or ambiguous since we pass TCK anyway. > > > > Le 19 déc. 2015 13:42, "Thomas Andraschko" < > andraschko.tho...@gmail.com> > > > a > > > > écrit : > > > > > > > >> Hi, > > > >> > > > >> shoudln't toString call the original toString method of the > contextual > > > >> instance? > > > >> > > > >> 2015-12-18 20:13 GMT+01:00 Romain Manni-Bucau < rmannibu...@gmail.com > >: > > > >> > > > >>> Hi guys, > > > >>> > > > >>> ATM we dont proxy methods in Objects (ie normalScope.toString()) > will > > > do > > > >> a > > > >>> toString on the proxy - see > > > >>> > > > >>> > > > >> > > > > org.apache.webbeans.proxy.SubclassProxyFactory#delegateNonInterceptedMethods. > > > >>> > > > >>> This is fine by itself but then how to enforce the eager init of a > bean > > > >> in > > > >>> a reliable manner? > > > >>> > > > >>> Side note: you probably all know the @CdiStartup extension relying > on > > > >>> toString() in after validation event callback and the code I used - > and > > > >>> which fails - was pretty close to that. > > > >>> > > > >>> FYI I tested only on 1.2.7 but code didnt change much in 1.2.x > branch I > > > >>> think. > > > >>> > > > >>> Any input/idea? > > > >>> > > > >>> 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> > > > >>> > > > >> > > > > > >
Re: [DISCUSS] moving OpenWebBeans to GIT?
-0 doesnt bring anything IMO but dont care enough to fight on it Le 23 janv. 2016 11:59, "Mark Struberg" a écrit : > 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 > >
Re: moving to owb-1.7.0-SNAPSHOT?
1.6.3 is good since it is rarely used by *users*. Also not sure we need both SPI since we have bba handling elsewhere and I think scanner service responsability should stay lower level than bda which is a CDI thing to make it useful - keep integration with other filesystems typically. Le 31 janv. 2016 13:06, "Thomas Andraschko" a écrit : > +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: release OWB next week?
+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: [VOTE] Release OpenWebBeans-1.6.3
+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>
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&version=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
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 :
> 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&version=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
To be honest got far worse with cdi/deltaspike+maven in previous releases
and doing a 1.6.4 is not forbidden (:D) if we find it is an actual bug in
OWB.
Let me know if you need me to investigate a bit more the issue.
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 20:12 GMT+01:00 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 :
>
> > 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 >:
> >
> > > 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&version=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: Extending context and bean instance discovery in OpenWebBeans
Le 19 févr. 2016 21:54, "Shahim Essaid" a écrit :
>
> On Fri, Feb 19, 2016 at 12:31 PM, Mark Struberg wrote:
>
> > Hi Shahim!
> >
> > Plz give me a bit to read through the long post. Currently busy with
some
> > other work but hope to get to it tonight or tomorrow morning.
> >
> >
> Hi Mark,
>
> Sure, no problem. I'm just sharing some general thoughts (the long part)
to
> give some background for why I'm asking my questions. There is a specific
> issue that I need some hints about from the experts on this list. I'm
> copying it here:
>
> > I think this can be boiled down to having a method that returns a list
of
> > contexts from BeanManager as in:
> >
> > public List getContext(Class scopeType);
> >
> > and have the various CDI services be able to deal with this by going
> > through the list. The current behavior would be equivalent to only using
> > the first context on this list, if it is available.
>
> There is one additional issue that I didn't think about when I wrote my
> post. I'm assuming that the CDI specification doesn't require (or
> explicitly prohibits) that a contextual reference remember the context it
> was resolved to after the first invocation of that reference. If this is
> the case, I would be interested in understanding how to add this
capability
> to the OWB implementation for my specific use case. In other words, I
think
> that the contextual reference has to be created by the context, not the
> bean so the reference is a reference to "this type, form this context".
> Which OWB classes should I be looking at to give this a try, and is this
> even feasible with the current OWB implementation architecture?
>
Contexts are singleton so they are accessible. CreationalContext instance
depends the scope of the bean and bean instances are not controlled.
> Best,
> Shahim
>
>
> > txs and LieGrue,
> > strub
> >
> >
> > > Am 18.02.2016 um 20:58 schrieb Shahim Essaid :
> > >
> > > Hi all,
> > >
> > > I've been looking at CDI and OpenWebBeans with few usecases in mind.
They
> > > mostly depend on flexible context management, and there are no
concrete
> > > examples of the use cases yet, but I'm trying to understand my
options.
> > > You've seen few JIRA comments that are related to this but the
following
> > > goes beyond those issues.
> > >
> > > An example will help understand why I'm looking into this. I would
like
> > to
> > > take advantage of the CDI programming model but extend how contexts
are
> > > created and managed to be able to deal with certain real world
> > situations.
> > > For example, a @PersonScoped could be a scope for personal objects and
> > > let's assume that there is only one context for for this scope that
holds
> > > all personal related objects. However, @OrgScoped is a scope for
> > > organization beans but organizations are almost always hierarchical
> > > (Company, branch, department, etc.). At runtime this hierarchical
nature
> > > can be represented as a tree or a DAG of @OrgScoped context instances
> > each
> > > with their own instantiation of @OrgScoped beans but with different
> > values
> > > or information in those instances. There are many other examples of
> > > hierarchical contexts in the real world and the available information
in
> > > each context can be augmented with, or defaulted by, information from
a
> > > parent context without having to define custom beans or bean
qualifiers
> > for
> > > the related contexts. The Bean type is exactly the same but there are
> > > additional instances in other contexts that should be considered when
> > > needed. There are also other types of beans in those contexts and when
> > each
> > > bean instance is looked at in a context, it should be considered in
> > > relationship to other instances in that same context.
> > >
> > > With the above example, I would like to possibly do the following in
some
> > > code that is running in the @PersonScoped context for a specific
person
> > > (contexts are identified per person just like sessions, conversations,
> > etc.
> > > are internally identified in the usual case), and all the instantiated
> > > ancestor @OrgSScoped contexts that were previously instantiated at
> > runtime
> > > and assigned as parent contexts for this specific person. If this code
> > has
> > > the following injection point:
> > >
> > > @Inject Instance workInfo;
> > >
> > > and there is a bean:
> > > @OrgScoped
> > > class WorkInfo {}
> > >
> > > and the code iterates over the instances, it should see a list of
> > WorkInfo
> > > instances starting from the direct @OrgScoped context as usual but
then
> > > also be able to get the instances from the parent contexts that were
> > > explicitly managed at runtime. So, the code will see their WorkInfo
> > > instances from their direct work context but then other instances from
> > the
> > > parent contexts.
> > >
> > > I think this can be boiled down to having a method that returns a
list of
> > > contexts from BeanManager as in:
> > >
> > > pub
Re: Extending context and bean instance discovery in OpenWebBeans
There are multiple thibgs then: 1. You will do somthing which has no link with CDI anymore 2. This can be achieved with custom scopes whatever you seem to think 3. Tomee does it having several deployments 4. Adding an id to webbeanscontext is doable and is only relevant to share the same classloader between multiple webbeanscontext. This however needs far more work than just making all internal fields public like changing beans id generation Le 20 févr. 2016 02:02, "Shahim Essaid" a écrit : > Hi Romain, > > Thanks for the tips. I need to look into your comment: "There are some > samples of a method scope. Sounds all you need linked with > some interception to activate the scope." but I'm not sure that it will > address what I'm describing below. > > I'm sorry for another long post but I don't know how to make this much > shorter. :-) Also, none of this is urgent, and I'm not expecting any > significant help but any hints will be much appreciated. > > I'm going to try to describe my situation in a different way and maybe it > will be clearer. To clarify, I'm not asking about how the CDI spec works, > or how exactly it is implemented in OWB. Rather, there are few CDI services > (implemented in OWB) that I would like to continue to use as is but there > are other CDI services or features that are a special case of the more > general case. Below I try to describe the more general case, and how CDI is > a special case of it. What I'm trying to understand is how I might be able > to modify OWB to implement the general case. > > To help with the discussion, I'd like to first introduce the term "World". > A world is modeled with a set of CDI beans (i.e. types and scopes). At > runtime, the world becomes "alive" in contexts and threads, and it could > possibly be persisted to be resumed at a later time. > > The CDI spec assumes a single anonymous world (i.e. there are no persistent > world identifiers). The implementation of this anonymous CDI world in OWB > is in WebBeansContext and it is instantiate by making an instance and > entering it. CDI also assumes that in this world there is a one to one > mapping between scopes and active contexts at any one time. This is a > special case of having multiple active contexts for a scope and each object > proxy/contextual reference being aware of which context it came from. CDI > also doesn't require identifiers for contexts. There is one single, and > anonymous, active context and that is all that matters. The more general > case is that contexts have identifiers to distinguish them from each other > in addition to their scope. In other words, CDI contexts are only indexed > by scope, the more general case is that contexts are indexed by scope and > an additional key, or simply identified with global IRI/URIs, GUIDs, etc. > In this case, when a contextual reference is created, it has to also be > indexed by a specific context. > > Because in CDI there is only one anonymous world at design time, and only > one instance of it at runtime in the form of the singleton active contexts, > there is no need to track where bean instances came from, what context to > use when resolving a contextual reference (when there are multiple active > ones), etc. This is all a special case of many worlds, multiple active > contexts, contexts and worlds with stable identifiers instead of the > singleton and anonymous worlds and contexts (basically null for > world/context ID), etc. > > What I'm trying to understand is how can I use OWB to generalized the CDI > assumptions. It can be done either by multiple active contexts within a > single world, each with their own identity, and any contextual reference is > context aware (through the identity). Or, the better option is multiple > worlds and in each world CDI is implemented as usual but contextual > references are world aware through world identity. Either way, when an > object reference is obtained from one context, or from one world, and this > object is traversed, the other objects that are reached are the correct > ones. This is not a problem in CDI because there is a guarantee that there > is a single instance of the world (in the form of singleton active > contexts) and it is up to the implementation to guarantee this. > > If the above is making things a little clearer, what I would like to > attempt is to do the following (in the same JVM for now): > > 1. Be able to instantiate multiple WebBeanContext instances. > > 2. Have a thread running in one instance be able to getReference(Bean > bean, Type beanType, CreationalContext ctx); on one of the BeanManager > of the other WebBeanContext instance and get an object (which could be > Instance) that is still connected to the other instance (its world) > without the thread having to manage this. > > 3. When this object is traversed, what is accessed is in that world's > contexts, not this world. i.e. the active contexts in that world, not the > ones in this world. Again, without threa
Re: [jira] [Commented] (OWB-1124) Lazy start on SessionContext NPE on no active RequestContext
2016-03-03 21:44 GMT+01:00 Karl Kildén :
> I did not. Sorry I will take notes of this and run it tomorrow and also
> look at your test class, thanks for pushing it! Maybe I can add a few tests
> if you did not cover the whole class.
>
>
> mvn clean install -pl tck/cdi-embedded && cd tck/cdi-embedded
>
> I understand the first part of course the install, then I cd into that
> directory and do what?
>
>
mvn clean install ;)
idea is:
0. upgrade OWB in root pom.xml (there is a property)
1. ensure you have all deps locally:
mvn clean install -pl tck/cdi-embedded -am -DskipTests
2. go in tck module and run it
mvn clean install
Side note: you can do the same with tck/cdi-tomee but it is longer so I
tend to check cdi-embedded and let buildbot (our CI) check cdi-tomee
> Then I can upgrade my local tomee root pom with the new owb version I now
> installed locally and run mvn clean install
>
> Thanks for teaching me these
>
> cheers
>
> On 3 March 2016 at 13:35, Romain Manni-Bucau (JIRA)
> wrote:
>
> >
> > [
> >
> https://issues.apache.org/jira/browse/OWB-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177754#comment-15177754
> > ]
> >
> > Romain Manni-Bucau commented on OWB-1124:
> > -
> >
> > [~karlkilden] pushed a test. Did you test OWB snapshot with tomee cdi
> > tcks? (mvn clean install -pl tck/cdi-embedded && cd tck/cdi-embedded &&
> > mvn clean install from tomee trunk once openwebbeans version property
> > upgraded to the snapshot in root pom).
> >
> > > Lazy start on SessionContext NPE on no active RequestContext
> > >
> > >
> > > Key: OWB-1124
> > > URL: https://issues.apache.org/jira/browse/OWB-1124
> > > Project: OpenWebBeans
> > > Issue Type: Bug
> > > Environment: TomEE 7.0M1
> > >Reporter: Karl Kildén
> > >Assignee: Romain Manni-Bucau
> > > Attachments: changes.diff
> > >
> > >
> > > I upgraded to TomEE 7-M1 and I have a problem with checking for active
> > contexts. Now this behavior:
> > > ServletRequestContext requestContext = getRequestContext(true);
> > > if (requestContext == null)
> > > {
> > > logger.log(Level.WARNING, "Could NOT lazily initialize
> > session context because NO active request context");
> > > }
> > > Only logs it and goes ahead and breaks on NPE on line 815 but before it
> > simply never executed any code if requestContext was null.
> > > This is the code in my application that actually uses Deltaspike now
> for
> > checking:
> > > private boolean isActive(Class scope) {
> > > return ContextUtils.isContextActive(scope);
> > > }
> > > Full stacktrace
> > > at
> >
> org.apache.webbeans.web.context.WebContextsService.lazyStartSessionContext(WebContextsService.java:815)
> > > at
> >
> org.apache.webbeans.web.context.WebContextsService.getSessionContext(WebContextsService.java:739)
> > > at
> >
> org.apache.webbeans.web.context.WebContextsService.getCurrentContext(WebContextsService.java:277)
> > > at
> >
> org.apache.webbeans.container.BeanManagerImpl.getContext(BeanManagerImpl.java:287)
> > > at
> >
> org.apache.webbeans.container.InjectableBeanManager.getContext(InjectableBeanManager.java:129)
> > > at
> >
> org.apache.deltaspike.core.util.ContextUtils.isContextActive(ContextUtils.java:60)
> > > at
> >
> org.apache.deltaspike.core.util.ContextUtils.isContextActive(ContextUtils.java:46)
> > > at
> com.company.ContextLookup.isActive(ContextLookup.java:23)
> > > My actual use case is that I tag all my entities if I can find out who
> > changed it but in this case it was a background thread.
> >
> >
> >
> > --
> > This message was sent by Atlassian JIRA
> > (v6.3.4#6332)
> >
>
seteventfired too early?
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?
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 : > +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: seteventfired too early?
finally pushed a test about it 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-17 14:23 GMT+02:00 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 : > > > 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 : > > > > > +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: CDI 2.0 Spec JAR
Hi John, -> geronimo@ ;) Otherwise +1 for jenkins and to replace current 2.0 by an up to date version Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Wordpress 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-07-03 15:10 GMT+02:00 John D. Ament : > 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 plan to restate them, similar to what i'm seeing in here. > > I'm wondering if we can enable a build in jenkins to build the JAR? > > John >
Re: CDI 2.0 Spec JAR
Le 3 juil. 2016 22:56, "John D. Ament" a écrit : > > geronimo@ who? Dev list > > I emailed the OWB list as the OWB team is maintaining the JAR, there's just > considerable overlap w/ the geronimo PMC that it becomes confusing. > Well you can also see geronimo community is doing so since people overlap a lot there but strictly speaking this jar is not always driven by owb. > What about my comments about the javadocs? > It is usually best effort but im +1 to make it better. Only constraint we have is to not copy official comments/spec AFAIK. > John > > On Sun, Jul 3, 2016 at 3:24 PM Romain Manni-Bucau > wrote: > > > Hi John, > > > > -> geronimo@ ;) > > > > Otherwise +1 for jenkins and to replace current 2.0 by an up to date > > version > > > > > > Romain Manni-Bucau > > @rmannibucau <https://twitter.com/rmannibucau> | Blog > > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress 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-07-03 15:10 GMT+02:00 John D. Ament : > > > > > 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 plan to restate them, similar to what i'm seeing in here. > > > > > > I'm wondering if we can enable a build in jenkins to build the JAR? > > > > > > John > > > > >
WARNING for duplicated interceptors
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 <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Wordpress 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>
Re: Build problem
+1 to upgrade Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Wordpress 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-07-22 19:17 GMT+02:00 Daniel Cunha : > Hi folks, > > last change we got a build error. > Sounds like we need update maven version from 2[1] to version >= 3.0 [2] > on Jenkins for changes on OWB > > [INFO] Internal error in the plugin manager executing goal > 'org.apache.felix:maven-bundle-plugin:3.0.1:manifest': Unable to load the > mojo 'org.apache.felix:maven-bundle-plugin:3.0.1:manifest' in the plugin > 'org.apache.felix:maven-bundle-plugin'. A required class is missing: > org/apache/maven/project/DependencyResolutionException > org.apache.maven.project.DependencyResolutionException > > [1] > > https://maven.apache.org/components/ref/2.2.1/maven-core/apidocs/org/apache/maven/project/DependencyResolutionException.html > [2] > > https://maven.apache.org/ref/3.0/maven-core/apidocs/org/apache/maven/project/DependencyResolutionException.html > > > -- > Daniel Cunha > https://twitter.com/dvlc_ > http://www.tomitribe.com > http://www.tomitribe.io >
Re: do an OWB release?
+1 to go Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Wordpress 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-07-27 11:21 GMT+02:00 Reinhard Sandtner : > hey, > > i think we should go through all open issues before… > maybe i will find some time to help next week > > lg > reini > > > > Am 27.07.2016 um 10:47 schrieb Mark Struberg >: > > > > Hi! > > > > Are there anything we need before shipping the next owb release? > > > > > > LieGrue, > > strub > >
Re: do an OWB release?
Fixed one on tomee we qhould port to owb - didnt get time today - preventing jsp/cdi to work. Tomcat just changed the class setting the jspfactory. Will try to fix it in the week. Le 22 août 2016 19:38, "Mark Struberg" a écrit : > stuck in OpenJPA until I get trunk fixed. > > > Thomas, could you plz go through the open jiras and ping me for the ones > you like to see fixed? > > After that it's just a matter of an hour to make the release. > That's pretty easy. I can do it, but if anybody likes to jump in I'm fine > as well. > > > txs and LieGrue, > strub > > > > > > > On Monday, 22 August 2016, 16:50, Thomas Andraschko < > andraschko.tho...@gmail.com> wrote: > > > any news? :) > > > > > > 2016-07-27 16:38 GMT+02:00 Gerhard Petracek : > > > >> +1 for a release! > >> > >> regards, > >> gerhard > >> > >> > >> > >> 2016-07-27 10:47 GMT+02:00 Mark Struberg : > >> > >> > Hi! > >> > > >> > Are there anything we need before shipping the next owb release? > >> > > >> > > >> > LieGrue, > >> > strub > >> > > >> > > >
Re: do an OWB release?
In tomee i did try new else try old. Will do tmr Le 22 août 2016 20:22, "Mark Struberg" a écrit : > If there are multiple Tomcat versions then we should have an array with > known class + method and call them via java.lang.reflect imo. > > Can you please file a ticket? Or tell me the TomEE ticket so I can create > one that just links over? > > > LieGrue, > strub > > > > > > > On Monday, 22 August 2016, 19:44, Romain Manni-Bucau < > rmannibu...@gmail.com> wrote: > > > Fixed one on tomee we qhould port to owb - didnt get time today - > > preventing jsp/cdi to work. Tomcat just changed the class setting the > > jspfactory. Will try to fix it in the week. > > > > > > Le 22 août 2016 19:38, "Mark Struberg" > > a écrit : > > > >> stuck in OpenJPA until I get trunk fixed. > >> > >> > >> Thomas, could you plz go through the open jiras and ping me for the > ones > >> you like to see fixed? > >> > >> After that it's just a matter of an hour to make the release. > >> That's pretty easy. I can do it, but if anybody likes to jump in > > I'm fine > >> as well. > >> > >> > >> txs and LieGrue, > >> strub > >> > >> > >> > >> > >> > >> > On Monday, 22 August 2016, 16:50, Thomas Andraschko < > >> andraschko.tho...@gmail.com> wrote: > >> > > any news? :) > >> > > >> > > >> > 2016-07-27 16:38 GMT+02:00 Gerhard Petracek > > : > >> > > >> >> +1 for a release! > >> >> > >> >> regards, > >> >> gerhard > >> >> > >> >> > >> >> > >> >> 2016-07-27 10:47 GMT+02:00 Mark Struberg > > : > >> >> > >> >> > Hi! > >> >> > > >> >> > Are there anything we need before shipping the next owb > > release? > >> >> > > >> >> > > >> >> > LieGrue, > >> >> > strub > >> >> > > >> >> > >> > > >> > > >
Re: do an OWB release?
here it is https://issues.apache.org/jira/browse/OWB-1139 Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Wordpress 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-08-22 20:36 GMT+02:00 Romain Manni-Bucau : > In tomee i did try new else try old. Will do tmr > > Le 22 août 2016 20:22, "Mark Struberg" a > écrit : > >> If there are multiple Tomcat versions then we should have an array with >> known class + method and call them via java.lang.reflect imo. >> >> Can you please file a ticket? Or tell me the TomEE ticket so I can create >> one that just links over? >> >> >> LieGrue, >> strub >> >> >> >> >> >> > On Monday, 22 August 2016, 19:44, Romain Manni-Bucau < >> rmannibu...@gmail.com> wrote: >> > > Fixed one on tomee we qhould port to owb - didnt get time today - >> > preventing jsp/cdi to work. Tomcat just changed the class setting the >> > jspfactory. Will try to fix it in the week. >> > >> > >> > Le 22 août 2016 19:38, "Mark Struberg" >> > a écrit : >> > >> >> stuck in OpenJPA until I get trunk fixed. >> >> >> >> >> >> Thomas, could you plz go through the open jiras and ping me for the >> ones >> >> you like to see fixed? >> >> >> >> After that it's just a matter of an hour to make the release. >> >> That's pretty easy. I can do it, but if anybody likes to jump in >> > I'm fine >> >> as well. >> >> >> >> >> >> txs and LieGrue, >> >> strub >> >> >> >> >> >> >> >> >> >> >> >> > On Monday, 22 August 2016, 16:50, Thomas Andraschko < >> >> andraschko.tho...@gmail.com> wrote: >> >> > > any news? :) >> >> > >> >> > >> >> > 2016-07-27 16:38 GMT+02:00 Gerhard Petracek >> > : >> >> > >> >> >> +1 for a release! >> >> >> >> >> >> regards, >> >> >> gerhard >> >> >> >> >> >> >> >> >> >> >> >> 2016-07-27 10:47 GMT+02:00 Mark Struberg >> > : >> >> >> >> >> >> > Hi! >> >> >> > >> >> >> > Are there anything we need before shipping the next owb >> > release? >> >> >> > >> >> >> > >> >> >> > LieGrue, >> >> >> > strub >> >> >> > >> >> >> >> >> > >> >> >> > >> >
Re: set min java level to 1.7 for OWB-1.6.x?
+0 (not sure it changes anything for us mid term but better to upgrade since EOL are way overpassed) Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Wordpress 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-08-29 10:16 GMT+02:00 Mark Struberg : > Hi! > > I'm in the progress to update quite a few plugins in the OWB build. > Most of them now require java7. And CDI-1.2 is also clearly EE7 level. > Which requires Java7. > > So I propose to upgrade trunk to Java7 as minimal requirement. > > Any objections? > > LieGrue, > strub >
Re: set min java level to 1.7 for OWB-1.6.x?
Any way to keep existing released jar compatible without keeping the module there? Saw some users still stucked to that :( Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Wordpress 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-08-29 10:37 GMT+02:00 Mark Struberg : > fine with 1.7.0. > > But then let's also get rid of JSF-1.2 support ;) > > Any objections? > > > LieGrue, > strub > > > > > > > On Monday, 29 August 2016, 10:27, Thomas Andraschko < > andraschko.tho...@gmail.com> wrote: > > > +0 > > It's probably better to do a 1.7 instead 1.6.x release if we do this > > > > > > 2016-08-29 10:18 GMT+02:00 Romain Manni-Bucau : > > > >> +0 (not sure it changes anything for us mid term but better to upgrade > >> since EOL are way overpassed) > >> > >> > >> Romain Manni-Bucau > >> @rmannibucau <https://twitter.com/rmannibucau> | Blog > >> <https://blog-rmannibucau.rhcloud.com> | Old Wordpress 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-08-29 10:16 GMT+02:00 Mark Struberg : > >> > >> > Hi! > >> > > >> > I'm in the progress to update quite a few plugins in the OWB > > build. > >> > Most of them now require java7. And CDI-1.2 is also clearly EE7 > level. > >> > Which requires Java7. > >> > > >> > So I propose to upgrade trunk to Java7 as minimal requirement. > >> > > >> > Any objections? > >> > > >> > LieGrue, > >> > strub > >> > > >> > > >
Re: what do do with the webbeans-doc module
+1 for B Side note: for tomee "ng" website proposal i added to jbake an attribute to generate a pdf from adoc pages (see https://github.com/rmannibucau/site-tomee-ng/blob/master/src/main/java/org/apache/tomee/website/PDFify.java). It allows to add this "download as pdf" on the related pages (ex: http://tomee.apache.org/ng/developer/json/index.html ). Can be nice and suspect it is doable with md too as easily as with adoc if we dont want to migrate everything. Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Wordpress 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-08-29 16:19 GMT+02:00 Mark Struberg : > hi! > > This module started as PDF documentation and is written in DocBook. > It also is a tad outdated ;) > > Means it still addresses CDI-1.0 and other ancient things we do not > support anymore. > > I think we have 2 options: > A.) Either rewrite it from scratch in asciidoc > B.) Remove it completely. We have the home page anyway. > > Is there any information you really like to keep as a separate PDF paper > beside our CMS content? > > LieGrue, > strub >
Re: [VOTE] Release Apache OpenWebBeans-1.7.0
+1
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress 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-08-30 14:55 GMT+02:00 Joseph Bergmark :
> +1
>
> built, mvn apache-rat:check, and ran a couple of the sample applications.
> Looked good to me
>
> On Tue, Aug 30, 2016 at 4:40 AM, Mark Struberg
> wrote:
>
> > Good morning!
> >
> > I'd like to call a VOTE on releasing Apache OpenWebBeans-1.7.0.
> >
> >
> > The staging repo is:
> >
> > https://repository.apache.org/content/repositories/
> > orgapacheopenwebbeans-1017/
> >
> >
> > The source release can be found at
> > https://repository.apache.org/content/repositories/
> > orgapacheopenwebbeans-1017/org/apache/openwebbeans/openwebbeans/1.7.0/
> >
> >
> > My Key can be found in
> > https://svn.apache.org/repos/asf/openwebbeans/trunk/KEYS
> >
> > The tag in SVN is
> >
> > https://svn.apache.org/repos/asf/openwebbeans/tags/openwebbeans-1.7.0/
> > Revision r1758342
> >
> >
> >
> > [+1] let's ship it!
> >
> > [+0] meh, don't care
> >
> > [-1] nope, because ${blocker}
> >
> >
> > The VOTE is open for 72h
> >
> >
> > txs and LieGrue,
> > strub
> >
>
Re: [VOTE] Release Apache OpenWebBeans-1.7.0
FYI CDI TCK are green on tomee project (embedded and standalone)
@Gerhard: if still the same issue related to session/request scopes it is a
bug of CdiCtrl API more than an OWB one so can (should) be fixed in
deltaspike not there (note that OpenWebBeansContextControl doesn't respect
the spec and therefore cdictrl behavior doesn't work and both statements
are very compatible).
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress 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-08-31 22:09 GMT+02:00 Gerhard Petracek :
> -1, because it still breaks
> org.apache.deltaspike.cdise.tck.ContainerCtrlTckTest (as soon as owb is
> used with openejb).
>
> regards,
> gerhard
>
>
>
> 2016-08-30 10:40 GMT+02:00 Mark Struberg :
>
> > Good morning!
> >
> > I'd like to call a VOTE on releasing Apache OpenWebBeans-1.7.0.
> >
> >
> > The staging repo is:
> >
> > https://repository.apache.org/content/repositories/
> > orgapacheopenwebbeans-1017/
> >
> >
> > The source release can be found at
> > https://repository.apache.org/content/repositories/
> > orgapacheopenwebbeans-1017/org/apache/openwebbeans/openwebbeans/1.7.0/
> >
> >
> > My Key can be found in
> > https://svn.apache.org/repos/asf/openwebbeans/trunk/KEYS
> >
> > The tag in SVN is
> >
> > https://svn.apache.org/repos/asf/openwebbeans/tags/openwebbeans-1.7.0/
> > Revision r1758342
> >
> >
> >
> > [+1] let's ship it!
> >
> > [+0] meh, don't care
> >
> > [-1] nope, because ${blocker}
> >
> >
> > The VOTE is open for 72h
> >
> >
> > txs and LieGrue,
> > strub
> >
>
Re: [VOTE] Release Apache OpenWebBeans-1.7.0
2016-08-31 22:18 GMT+02:00 Mark Struberg :
> No, it's really that we ditch the ThreadLocals in a place where we
> shouldn't.
>
> TCK passes even after my fix.
>
>
Shouldn't since the start object is broken in the context control - that
said we can move this over #deltaspike, doesn't affect OWB at all
>
> LieGrue,
> strub
>
>
>
>
>
> > On Wednesday, 31 August 2016, 22:17, Romain Manni-Bucau <
> rmannibu...@gmail.com> wrote:
> > > FYI CDI TCK are green on tomee project (embedded and standalone)
> >
> > @Gerhard: if still the same issue related to session/request scopes it
> is a
> > bug of CdiCtrl API more than an OWB one so can (should) be fixed in
> > deltaspike not there (note that OpenWebBeansContextControl doesn't
> respect
> > the spec and therefore cdictrl behavior doesn't work and both statements
> > are very compatible).
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> | Blog
> > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress 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-08-31 22:09 GMT+02:00 Gerhard Petracek :
> >
> >> -1, because it still breaks
> >> org.apache.deltaspike.cdise.tck.ContainerCtrlTckTest (as soon as owb
> is
> >> used with openejb).
> >>
> >> regards,
> >> gerhard
> >>
> >>
> >>
> >> 2016-08-30 10:40 GMT+02:00 Mark Struberg :
> >>
> >> > Good morning!
> >> >
> >> > I'd like to call a VOTE on releasing Apache OpenWebBeans-1.7.0.
> >> >
> >> >
> >> > The staging repo is:
> >> >
> >> > https://repository.apache.org/content/repositories/
> >> > orgapacheopenwebbeans-1017/
> >> >
> >> >
> >> > The source release can be found at
> >> > https://repository.apache.org/content/repositories/
> >> > orgapacheopenwebbeans-1017/org/apache/openwebbeans/
> openwebbeans/1.7.0/
> >> >
> >> >
> >> > My Key can be found in
> >> > https://svn.apache.org/repos/asf/openwebbeans/trunk/KEYS
> >> >
> >> > The tag in SVN is
> >> >
> >> > https://svn.apache.org/repos/asf/openwebbeans/tags/
> openwebbeans-1.7.0/
> >> > Revision r1758342
> >> >
> >> >
> >> >
> >> > [+1] let's ship it!
> >> >
> >> > [+0] meh, don't care
> >> >
> >> > [-1] nope, because ${blocker}
> >> >
> >> >
> >> > The VOTE is open for 72h
> >> >
> >> >
> >> > txs and LieGrue,
> >> > strub
> >> >
> >>
> >
>
Re: [VOTE] Release Apache OpenWebBeans-1.7.0 - take 2
Any way to not use 1.7.0? Repo(s) is already hosting it so no way to
validate it until we make INFRA evicting the binaries.
Would 1.7.0.1 ok?
Le 31 août 2016 22:51, "Mark Struberg" a écrit :
> New take for OWB-1.7.0
>
> Repo is
> https://repository.apache.org/content/repositories/
> orgapacheopenwebbeans-1018/
>
> Source release is
> https://repository.apache.org/content/repositories/
> orgapacheopenwebbeans-1018/org/apache/openwebbeans/openwebbeans/1.7.0/
>
> You gonna find the rest I'm sure :)
>
>
>
>
> [+1] let's ship it!
> [+0] meh, don't care
> [-1] nope, because ${blocker}
>
>
> The VOTE is open for 72h
>
>
>
> Here is my +1
>
> txs and LieGrue,
> strub
>
>
>
> > On Wednesday, 31 August 2016, 22:23, Romain Manni-Bucau <
> rmannibu...@gmail.com> wrote:
> > > 2016-08-31 22:18 GMT+02:00 Mark Struberg :
> >
> >> No, it's really that we ditch the ThreadLocals in a place where we
> >> shouldn't.
> >>
> >> TCK passes even after my fix.
> >>
> >>
> > Shouldn't since the start object is broken in the context control - that
> > said we can move this over #deltaspike, doesn't affect OWB at all
> >
> >
> >
> >>
> >> LieGrue,
> >> strub
> >>
> >>
> >>
> >>
> >>
> >> > On Wednesday, 31 August 2016, 22:17, Romain Manni-Bucau <
> >> rmannibu...@gmail.com> wrote:
> >> > > FYI CDI TCK are green on tomee project (embedded and standalone)
> >> >
> >> > @Gerhard: if still the same issue related to session/request scopes
> it
> >> is a
> >> > bug of CdiCtrl API more than an OWB one so can (should) be fixed in
> >> > deltaspike not there (note that OpenWebBeansContextControl doesn't
> >> respect
> >> > the spec and therefore cdictrl behavior doesn't work and both
> > statements
> >> > are very compatible).
> >> >
> >> >
> >> > Romain Manni-Bucau
> >> > @rmannibucau <https://twitter.com/rmannibucau> | Blog
> >> > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress 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-08-31 22:09 GMT+02:00 Gerhard Petracek
> > :
> >> >
> >> >> -1, because it still breaks
> >> >> org.apache.deltaspike.cdise.tck.ContainerCtrlTckTest (as soon as
> > owb
> >> is
> >> >> used with openejb).
> >> >>
> >> >> regards,
> >> >> gerhard
> >> >>
> >> >>
> >> >>
> >> >> 2016-08-30 10:40 GMT+02:00 Mark Struberg
> > :
> >> >>
> >> >> > Good morning!
> >> >> >
> >> >> > I'd like to call a VOTE on releasing Apache
> > OpenWebBeans-1.7.0.
> >> >> >
> >> >> >
> >> >> > The staging repo is:
> >> >> >
> >> >> > https://repository.apache.org/content/repositories/
> >> >> > orgapacheopenwebbeans-1017/
> >> >> >
> >> >> >
> >> >> > The source release can be found at
> >> >> > https://repository.apache.org/content/repositories/
> >> >> > orgapacheopenwebbeans-1017/org/apache/openwebbeans/
> >> openwebbeans/1.7.0/
> >> >> >
> >> >> >
> >> >> > My Key can be found in
> >> >> > https://svn.apache.org/repos/asf/openwebbeans/trunk/KEYS
> >> >> >
> >> >> > The tag in SVN is
> >> >> >
> >> >> > https://svn.apache.org/repos/asf/openwebbeans/tags/
> >> openwebbeans-1.7.0/
> >> >> > Revision r1758342
> >> >> >
> >> >> >
> >> >> >
> >> >> > [+1] let's ship it!
> >> >> >
> >> >> > [+0] meh, don't care
> >> >> >
> >> >> > [-1] nope, because ${blocker}
> >> >> >
> >> >> >
> >> >> > The VOTE is open for 72h
> >> >> >
> >> >> >
> >> >> > txs and LieGrue,
> >> >> > strub
> >> >> >
> >> >>
> >> >
> >>
> >
>
Re: [VOTE] Release Apache OpenWebBeans-1.7.0 - take 2
dont care much of digits but +1 to just move forward and not reuse failed
release numbers
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress 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-09-01 10:47 GMT+02:00 Mark Struberg :
> 1.7.1 maybe. But we can easily kill 1.7.0 that from buildjob.
>
>
>
>
>
>
> > On Thursday, 1 September 2016, 8:08, Romain Manni-Bucau <
> rmannibu...@gmail.com> wrote:
> > > Any way to not use 1.7.0? Repo(s) is already hosting it so no way to
> > validate it until we make INFRA evicting the binaries.
> >
> > Would 1.7.0.1 ok?
> >
> >
> > Le 31 août 2016 22:51, "Mark Struberg"
> > a écrit :
> >
> >> New take for OWB-1.7.0
> >>
> >> Repo is
> >> https://repository.apache.org/content/repositories/
> >> orgapacheopenwebbeans-1018/
> >>
> >> Source release is
> >> https://repository.apache.org/content/repositories/
> >> orgapacheopenwebbeans-1018/org/apache/openwebbeans/openwebbeans/1.7.0/
> >>
> >> You gonna find the rest I'm sure :)
> >>
> >>
> >>
> >>
> >> [+1] let's ship it!
> >> [+0] meh, don't care
> >> [-1] nope, because ${blocker}
> >>
> >>
> >> The VOTE is open for 72h
> >>
> >>
> >>
> >> Here is my +1
> >>
> >> txs and LieGrue,
> >> strub
> >>
> >>
> >>
> >> > On Wednesday, 31 August 2016, 22:23, Romain Manni-Bucau <
> >> rmannibu...@gmail.com> wrote:
> >> > > 2016-08-31 22:18 GMT+02:00 Mark Struberg
> > :
> >> >
> >> >> No, it's really that we ditch the ThreadLocals in a place
> > where we
> >> >> shouldn't.
> >> >>
> >> >> TCK passes even after my fix.
> >> >>
> >> >>
> >> > Shouldn't since the start object is broken in the context control
> > - that
> >> > said we can move this over #deltaspike, doesn't affect OWB at all
> >> >
> >> >
> >> >
> >> >>
> >> >> LieGrue,
> >> >> strub
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> > On Wednesday, 31 August 2016, 22:17, Romain Manni-Bucau <
> >> >> rmannibu...@gmail.com> wrote:
> >> >> > > FYI CDI TCK are green on tomee project (embedded and
> > standalone)
> >> >> >
> >> >> > @Gerhard: if still the same issue related to session/request
> > scopes
> >> it
> >> >> is a
> >> >> > bug of CdiCtrl API more than an OWB one so can (should) be
> > fixed in
> >> >> > deltaspike not there (note that OpenWebBeansContextControl
> > doesn't
> >> >> respect
> >> >> > the spec and therefore cdictrl behavior doesn't work and
> > both
> >> > statements
> >> >> > are very compatible).
> >> >> >
> >> >> >
> >> >> > Romain Manni-Bucau
> >> >> > @rmannibucau <https://twitter.com/rmannibucau> | Blog
> >> >> > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress
> > 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-08-31 22:09 GMT+02:00 Gerhard Petracek
> >> > :
> >> >> >
> >> >> >> -1, because it still breaks
> >> >> >> org.apache.deltaspike.cdise.tck.ContainerCtrlTckTest
> > (as soon as
> >> > owb
> >> >> is
> >> >> >> used with openejb).
> >> >> >>
> >> >> >> regards,
> >> >> >> gerhard
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> 2016-08-30 10:40 GMT+02:00 Mark Struberg
> >> > :
> >> >> >>
> >> >> >> > Good morning!
> >> >> >> >
> >> >> >> > I'd like to call a VOTE on releasing Apache
> >> > OpenWebBeans-1.7.0.
> >> >> >> >
> >> >> >> >
> >> >> >> > The staging repo is:
> >> >> >> >
> >> >> >> >
> > https://repository.apache.org/content/repositories/
> >> >> >> > orgapacheopenwebbeans-1017/
> >> >> >> >
> >> >> >> >
> >> >> >> > The source release can be found at
> >> >> >> >
> > https://repository.apache.org/content/repositories/
> >> >> >> >
> > orgapacheopenwebbeans-1017/org/apache/openwebbeans/
> >> >> openwebbeans/1.7.0/
> >> >> >> >
> >> >> >> >
> >> >> >> > My Key can be found in
> >> >> >> >
> > https://svn.apache.org/repos/asf/openwebbeans/trunk/KEYS
> >> >> >> >
> >> >> >> > The tag in SVN is
> >> >> >> >
> >> >> >> >
> > https://svn.apache.org/repos/asf/openwebbeans/tags/
> >> >> openwebbeans-1.7.0/
> >> >> >> > Revision r1758342
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> > [+1] let's ship it!
> >> >> >> >
> >> >> >> > [+0] meh, don't care
> >> >> >> >
> >> >> >> > [-1] nope, because ${blocker}
> >> >> >> >
> >> >> >> >
> >> >> >> > The VOTE is open for 72h
> >> >> >> >
> >> >> >> >
> >> >> >> > txs and LieGrue,
> >> >> >> > strub
> >> >> >> >
> >> >> >>
> >> >> >
> >> >>
> >> >
> >>
> >
>
Re: [VOTE] Release Apache OpenWebBeans-1.7.0 - take 2
+1
Le 3 sept. 2016 20:30, "Reinhard Sandtner" a
écrit :
> +1 (non-binding)
>
> app works fine
> signature ok
> building from src successful
>
> lg
> reini
>
>
>
> > Am 31.08.2016 um 22:50 schrieb Mark Struberg >:
> >
> > New take for OWB-1.7.0
> >
> > Repo is
> > https://repository.apache.org/content/repositories/
> orgapacheopenwebbeans-1018/
> >
> > Source release is
> > https://repository.apache.org/content/repositories/
> orgapacheopenwebbeans-1018/org/apache/openwebbeans/openwebbeans/1.7.0/
> >
> > You gonna find the rest I'm sure :)
> >
> >
> >
> >
> > [+1] let's ship it!
> > [+0] meh, don't care
> > [-1] nope, because ${blocker}
> >
> >
> > The VOTE is open for 72h
> >
> >
> >
> > Here is my +1
> >
> > txs and LieGrue,
> > strub
> >
> >
> >
> >> On Wednesday, 31 August 2016, 22:23, Romain Manni-Bucau <
> rmannibu...@gmail.com> wrote:
> >>> 2016-08-31 22:18 GMT+02:00 Mark Struberg :
> >>
> >>> No, it's really that we ditch the ThreadLocals in a place where we
> >>> shouldn't.
> >>>
> >>> TCK passes even after my fix.
> >>>
> >>>
> >> Shouldn't since the start object is broken in the context control - that
> >> said we can move this over #deltaspike, doesn't affect OWB at all
> >>
> >>
> >>
> >>>
> >>> LieGrue,
> >>> strub
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>> On Wednesday, 31 August 2016, 22:17, Romain Manni-Bucau <
> >>> rmannibu...@gmail.com> wrote:
> >>>>> FYI CDI TCK are green on tomee project (embedded and standalone)
> >>>>
> >>>> @Gerhard: if still the same issue related to session/request scopes it
> >>> is a
> >>>> bug of CdiCtrl API more than an OWB one so can (should) be fixed in
> >>>> deltaspike not there (note that OpenWebBeansContextControl doesn't
> >>> respect
> >>>> the spec and therefore cdictrl behavior doesn't work and both
> >> statements
> >>>> are very compatible).
> >>>>
> >>>>
> >>>> Romain Manni-Bucau
> >>>> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> >>>> <https://blog-rmannibucau.rhcloud.com> | Old Wordpress 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-08-31 22:09 GMT+02:00 Gerhard Petracek
> >> :
> >>>>
> >>>>> -1, because it still breaks
> >>>>> org.apache.deltaspike.cdise.tck.ContainerCtrlTckTest (as soon as
> >> owb
> >>> is
> >>>>> used with openejb).
> >>>>>
> >>>>> regards,
> >>>>> gerhard
> >>>>>
> >>>>>
> >>>>>
> >>>>> 2016-08-30 10:40 GMT+02:00 Mark Struberg
> >> :
> >>>>>
> >>>>>> Good morning!
> >>>>>>
> >>>>>> I'd like to call a VOTE on releasing Apache
> >> OpenWebBeans-1.7.0.
> >>>>>>
> >>>>>>
> >>>>>> The staging repo is:
> >>>>>>
> >>>>>> https://repository.apache.org/content/repositories/
> >>>>>> orgapacheopenwebbeans-1017/
> >>>>>>
> >>>>>>
> >>>>>> The source release can be found at
> >>>>>> https://repository.apache.org/content/repositories/
> >>>>>> orgapacheopenwebbeans-1017/org/apache/openwebbeans/
> >>> openwebbeans/1.7.0/
> >>>>>>
> >>>>>>
> >>>>>> My Key can be found in
> >>>>>> https://svn.apache.org/repos/asf/openwebbeans/trunk/KEYS
> >>>>>>
> >>>>>> The tag in SVN is
> >>>>>>
> >>>>>> https://svn.apache.org/repos/asf/openwebbeans/tags/
> >>> openwebbeans-1.7.0/
> >>>>>> Revision r1758342
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> [+1] let's ship it!
> >>>>>>
> >>>>>> [+0] meh, don't care
> >>>>>>
> >>>>>> [-1] nope, because ${blocker}
> >>>>>>
> >>>>>>
> >>>>>> The VOTE is open for 72h
> >>>>>>
> >>>>>>
> >>>>>> txs and LieGrue,
> >>>>>> strub
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
>
>
Re: weird @WebService handling in webbeans-tomcat7 module
cause the webservice providers handles it (ie CXF cdi integration for instance). Typically for TomEE OWB shouldn't handle it but TomEE does in its CXF integration. Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Wordpress 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-09-08 20:54 GMT+02:00 Mark Struberg : > Hi! > > I will remove the following line from the tomcat7-plugin: > > https://github.com/apache/openwebbeans/blob/trunk/ > webbeans-tomcat7/src/main/java/org/apache/webbeans/web/ > tomcat7/TomcatWebPlugin.java#L109 > > I have no clue why it's there tbh ;) > > But @WebService classes don't belong into the tomcat plugin handling logic. > They will be handled elsewhere. > > @Romain: can you plz cross-check that we handle this properly in TomEE > anyway? > > LieGrue, > strub >
microwave landed
Hi guys, pushed at http://svn.apache.org/repos/asf/openwebbeans/microwave/trunk/ it is a prototype of a microprofile server it is based on tomcat+owb+cxf+johnzon it reuses a lot of tomee code so can need some cleanup but seems functional - didnt tested much maven and main yet but other part has small tests. I think OWB is a good place to host it wdyt? Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Wordpress 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>
Re: microwave landed
TODO I see short term: - make the project a real ASF one (with NOTICE, LICENSE etc) - make a small website (proposal welcomed or I'd use jbake probably) - stabilize the code and main API (we can be still experimental but if we don't break too often that's not bad) - upgrade to cxf 3.1.10 ASAP (not mandatory) - upgrade to OWB 1.7.1 once we'll add the filter config for CdiArchive (check org.apache.microwave.openwebbeans.BundleMetadataDiscovery#initFinder) - probably write a small gradle plugin (will try to do it this week) - enhance tests a lot Once this is done I would be happy to start releasing Then we should think to add extensions (surely through CDI): - tracing (audit trail header) or zipkin/brave integration somehow - monitoring (sirona + enhancement?) - healthchecks maybe - config - ... This part can be very interesting cause it would be best if not owned there but in related projects like deltaspike, tamaya, sirona etc... Sounds like an ASF concentrator but also enhancer ;) Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Wordpress 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-10-19 10:49 GMT+02:00 Reinhard Sandtner : > hey, > > i like the idea ;) really cool > i hope i can take a look this weekend > > ping me if you need help - sounds really interesting > > lg > reini > > > > Am 18.10.2016 um 23:47 schrieb Romain Manni-Bucau >: > > > > Hi guys, > > > > pushed at http://svn.apache.org/repos/asf/openwebbeans/microwave/trunk/ > > > > it is a prototype of a microprofile server > > > > it is based on tomcat+owb+cxf+johnzon > > > > it reuses a lot of tomee code so can need some cleanup but seems > functional > > - didnt tested much maven and main yet but other part has small tests. > > > > I think OWB is a good place to host it > > > > wdyt? > > > > Romain Manni-Bucau > > @rmannibucau <https://twitter.com/rmannibucau> | Blog > > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress 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> > >
Re: microwave landed
Pushed it on svn. Think it is good enough for now and avoids some infra but happy to move it to git later too. Just dont have enough spare time to pay all the costs ATM ;). Le 19 oct. 2016 12:44, "Mark Struberg" a écrit : > great stuff! > > Keep it in GIT and request a new repo? Or commit it to a new root in the > OWB svn ? > > LieGrue, > strub > > > Am 19.10.2016 um 10:55 schrieb Romain Manni-Bucau >: > > > > TODO I see short term: > > > > - make the project a real ASF one (with NOTICE, LICENSE etc) > > - make a small website (proposal welcomed or I'd use jbake probably) > > - stabilize the code and main API (we can be still experimental but if we > > don't break too often that's not bad) > > - upgrade to cxf 3.1.10 ASAP (not mandatory) > > - upgrade to OWB 1.7.1 once we'll add the filter config for CdiArchive > > (check org.apache.microwave.openwebbeans.BundleMetadataDiscovery# > initFinder) > > - probably write a small gradle plugin (will try to do it this week) > > - enhance tests a lot > > > > Once this is done I would be happy to start releasing > > > > Then we should think to add extensions (surely through CDI): > > - tracing (audit trail header) or zipkin/brave integration somehow > > - monitoring (sirona + enhancement?) > > - healthchecks maybe > > - config > > - ... > > > > This part can be very interesting cause it would be best if not owned > there > > but in related projects like deltaspike, tamaya, sirona etc... > > Sounds like an ASF concentrator but also enhancer ;) > > > > > > > > > > > > > > Romain Manni-Bucau > > @rmannibucau <https://twitter.com/rmannibucau> | Blog > > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress 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-10-19 10:49 GMT+02:00 Reinhard Sandtner < > reinhard.sandt...@gmail.com>: > > > >> hey, > >> > >> i like the idea ;) really cool > >> i hope i can take a look this weekend > >> > >> ping me if you need help - sounds really interesting > >> > >> lg > >> reini > >> > >> > >>> Am 18.10.2016 um 23:47 schrieb Romain Manni-Bucau < > rmannibu...@gmail.com > >>> : > >>> > >>> Hi guys, > >>> > >>> pushed at http://svn.apache.org/repos/asf/openwebbeans/microwave/ > trunk/ > >>> > >>> it is a prototype of a microprofile server > >>> > >>> it is based on tomcat+owb+cxf+johnzon > >>> > >>> it reuses a lot of tomee code so can need some cleanup but seems > >> functional > >>> - didnt tested much maven and main yet but other part has small tests. > >>> > >>> I think OWB is a good place to host it > >>> > >>> wdyt? > >>> > >>> Romain Manni-Bucau > >>> @rmannibucau <https://twitter.com/rmannibucau> | Blog > >>> <https://blog-rmannibucau.rhcloud.com> | Old Wordpress 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> > >> > >> > >
[Microwave] Fwd: svn commit: r1766603 [1/8] - in /openwebbeans/microwave/trunk: ./ microwave-arquillian/src/main/java/org/apache/microwave/arquillian/ microwave-core/src/main/java/org/apache/microwave
Hi guys, wonder how we can manage the site. Here is the issue: I don't think we need to get too much grey hairs with licensing of the js/css librairies we use to build the size since we don't care to vote on it or not - doesn't means we'll not respect the license, just we'll not write LICENSE/NOTICE for it. For now I put it in the project cause I think it is a nice way to get it running and maintained but if the license maintenance is too much pain we could split it as well. Happy to get feedback on that since I'm not sure what will be the less painful ATM. wdyt? Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory <https://javaeefactory-rmannibucau.rhcloud.com> -- Forwarded message -- From: Date: 2016-10-25 23:27 GMT+02:00 Subject: svn commit: r1766603 [1/8] - in /openwebbeans/microwave/trunk: ./ microwave-arquillian/src/main/java/org/apache/microwave/arquillian/ microwave-core/src/main/java/org/apache/microwave/ microwave-core/src/main/java/org/apache/microwave/tomcat/ microwave... To: comm...@openwebbeans.apache.org Author: rmannibucau Date: Tue Oct 25 21:27:10 2016 New Revision: 1766603 URL: http://svn.apache.org/viewvc?rev=1766603&view=rev Log: flag to setup tomcat defaults + basic doc module (TODO: exclude it from the src module since that's for the site only) Added: openwebbeans/microwave/trunk/microwave-doc/ openwebbeans/microwave/trunk/microwave-doc/pom.xml openwebbeans/microwave/trunk/microwave-doc/src/ openwebbeans/microwave/trunk/microwave-doc/src/main/ openwebbeans/microwave/trunk/microwave-doc/src/main/java/ openwebbeans/microwave/trunk/microwave-doc/src/main/java/org/ openwebbeans/microwave/trunk/microwave-doc/src/main/java/org/apache/ openwebbeans/microwave/trunk/microwave-doc/src/main/java/ org/apache/microwave/ openwebbeans/microwave/trunk/microwave-doc/src/main/java/ org/apache/microwave/doc/ openwebbeans/microwave/trunk/microwave-doc/src/main/java/ org/apache/microwave/doc/JBake.java (with props) openwebbeans/microwave/trunk/microwave-doc/src/main/java/ org/apache/microwave/doc/PDFify.java (with props) openwebbeans/microwave/trunk/microwave-doc/src/main/java/org/slf4j/ openwebbeans/microwave/trunk/microwave-doc/src/main/java/ org/slf4j/bridge/ openwebbeans/microwave/trunk/microwave-doc/src/main/java/ org/slf4j/bridge/SLF4JBridgeHandler.java (with props) openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/assets/ openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/assets/assets/ openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ assets/assets/css/ openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ assets/assets/css/styles.css openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ assets/assets/images/ openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/assets/assets/images/empty.gif (with props) openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ assets/assets/js/ openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ assets/assets/js/main.js openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ assets/assets/plugins/ openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ assets/assets/plugins/bootstrap/ openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ assets/assets/plugins/bootstrap/css/ openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ assets/assets/plugins/bootstrap/css/bootstrap.min.css (with props) openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ assets/assets/plugins/bootstrap/css/bootstrap.min.css.map (with props) openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ assets/assets/plugins/bootstrap/fonts/ openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ assets/assets/plugins/bootstrap/fonts/glyphicons-halflings-regular.eot (with props) openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ assets/assets/plugins/bootstrap/fonts/glyphicons-halflings-regular.svg (with props) openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ assets/assets/plugins/bootstrap/fonts/glyphicons-halflings-regular.ttf (with props) openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ assets/assets/plugins/bootstrap/fonts/glyphicons-halflings-regular.woff (with props) openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ assets/assets/plugins/bootstrap/fonts/glyphicons-halflings-regular.woff2 (with props) openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ assets/assets/plugins/bootstrap/js/ openwebbeans/microwave/trunk/microwave-doc/
Re: [Microwave] svn commit: r1766603 [1/8] - in /openwebbeans/microwave/trunk: ./ microwave-arquillian/src/main/java/org/apache/microwave/arquillian/ microwave-core/src/main/java/org/apache/microwave/
Le 26 oct. 2016 15:10, "Mark Struberg" a écrit : > > If we make the site part of the release then we must respect the license. Otherwise we don’t. > Here my idea - but really personal for now: part of the source tree but not the release. > LieGrue, > strub > > > > Am 25.10.2016 um 23:32 schrieb Romain Manni-Bucau : > > > > Hi guys, > > > > wonder how we can manage the site. Here is the issue: I don't think we need > > to get too much grey hairs with licensing of the js/css librairies we use > > to build the size since we don't care to vote on it or not - doesn't means > > we'll not respect the license, just we'll not write LICENSE/NOTICE for it. > > For now I put it in the project cause I think it is a nice way to get it > > running and maintained but if the license maintenance is too much pain we > > could split it as well. > > > > Happy to get feedback on that since I'm not sure what will be the less > > painful ATM. > > > > wdyt? > > > > Romain Manni-Bucau > > @rmannibucau <https://twitter.com/rmannibucau> | Blog > > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog > > <http://rmannibucau.wordpress.com> | Github < https://github.com/rmannibucau> | > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory > > <https://javaeefactory-rmannibucau.rhcloud.com> > > > > -- Forwarded message -- > > From: > > Date: 2016-10-25 23:27 GMT+02:00 > > Subject: svn commit: r1766603 [1/8] - in /openwebbeans/microwave/trunk: ./ > > microwave-arquillian/src/main/java/org/apache/microwave/arquillian/ > > microwave-core/src/main/java/org/apache/microwave/ > > microwave-core/src/main/java/org/apache/microwave/tomcat/ microwave... > > To: comm...@openwebbeans.apache.org > > > > > > Author: rmannibucau > > Date: Tue Oct 25 21:27:10 2016 > > New Revision: 1766603 > > > > URL: http://svn.apache.org/viewvc?rev=1766603&view=rev > > Log: > > flag to setup tomcat defaults + basic doc module (TODO: exclude it from the > > src module since that's for the site only) > > > > Added: > >openwebbeans/microwave/trunk/microwave-doc/ > >openwebbeans/microwave/trunk/microwave-doc/pom.xml > >openwebbeans/microwave/trunk/microwave-doc/src/ > >openwebbeans/microwave/trunk/microwave-doc/src/main/ > >openwebbeans/microwave/trunk/microwave-doc/src/main/java/ > >openwebbeans/microwave/trunk/microwave-doc/src/main/java/org/ > >openwebbeans/microwave/trunk/microwave-doc/src/main/java/org/apache/ > >openwebbeans/microwave/trunk/microwave-doc/src/main/java/ > > org/apache/microwave/ > >openwebbeans/microwave/trunk/microwave-doc/src/main/java/ > > org/apache/microwave/doc/ > >openwebbeans/microwave/trunk/microwave-doc/src/main/java/ > > org/apache/microwave/doc/JBake.java (with props) > >openwebbeans/microwave/trunk/microwave-doc/src/main/java/ > > org/apache/microwave/doc/PDFify.java (with props) > >openwebbeans/microwave/trunk/microwave-doc/src/main/java/org/slf4j/ > >openwebbeans/microwave/trunk/microwave-doc/src/main/java/ > > org/slf4j/bridge/ > >openwebbeans/microwave/trunk/microwave-doc/src/main/java/ > > org/slf4j/bridge/SLF4JBridgeHandler.java (with props) > >openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ > >openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/assets/ > > openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/assets/assets/ > >openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ > > assets/assets/css/ > >openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ > > assets/assets/css/styles.css > >openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ > > assets/assets/images/ > > openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/assets/assets/images/empty.gif > > (with props) > >openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ > > assets/assets/js/ > >openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ > > assets/assets/js/main.js > >openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ > > assets/assets/plugins/ > >openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ > > assets/assets/plugins/bootstrap/ > >openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ > > assets/assets/plugins/bootstrap/css/ > >openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ > > assets/
Fwd: svn commit: r1766878 [1/2] - in /openwebbeans/microwave/trunk: ./ microwave-arquillian/src/main/resources/META-INF/ microwave-core/ microwave-core/src/main/resources/META-INF/ microwave-doc/ micr
Hello guys, if someone has few cycle to start reviewing the legal setup of microwave it would be more than appreciated, tried to bootstrap it but not the part I'm the best at ;). For the website I decided to try to set it up as part of the release since dependencies are all legally compliant and it will make our build easier for the beginning at least. Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory <https://javaeefactory-rmannibucau.rhcloud.com> -- Forwarded message -- From: Date: 2016-10-27 22:10 GMT+02:00 Subject: svn commit: r1766878 [1/2] - in /openwebbeans/microwave/trunk: ./ microwave-arquillian/src/main/resources/META-INF/ microwave-core/ microwave-core/src/main/resources/META-INF/ microwave-doc/ microwave-doc/src/main/jbake/templates/ microwave-doc/src/mai... To: comm...@openwebbeans.apache.org Author: rmannibucau Date: Thu Oct 27 20:10:21 2016 New Revision: 1766878 URL: http://svn.apache.org/viewvc?rev=1766878&view=rev Log: first try to get notice/license right Added: openwebbeans/microwave/trunk/LICENSE openwebbeans/microwave/trunk/NOTICE openwebbeans/microwave/trunk/README.adoc openwebbeans/microwave/trunk/microwave-arquillian/src/main/ resources/META-INF/LICENSE openwebbeans/microwave/trunk/microwave-arquillian/src/main/ resources/META-INF/NOTICE openwebbeans/microwave/trunk/microwave-core/src/main/ resources/META-INF/LICENSE openwebbeans/microwave/trunk/microwave-core/src/main/ resources/META-INF/NOTICE openwebbeans/microwave/trunk/microwave-doc/src/main/resources/ openwebbeans/microwave/trunk/microwave-doc/src/main/resources/META-INF/ openwebbeans/microwave/trunk/microwave-doc/src/main/ resources/META-INF/LICENSE openwebbeans/microwave/trunk/microwave-doc/src/main/ resources/META-INF/NOTICE openwebbeans/microwave/trunk/microwave-gradle-plugin/src/ main/resources/META-INF/LICENSE openwebbeans/microwave/trunk/microwave-gradle-plugin/src/ main/resources/META-INF/NOTICE openwebbeans/microwave/trunk/microwave-jpa/src/main/ resources/META-INF/LICENSE openwebbeans/microwave/trunk/microwave-jpa/src/main/ resources/META-INF/NOTICE openwebbeans/microwave/trunk/microwave-junit/src/main/resources/ openwebbeans/microwave/trunk/microwave-junit/src/main/ resources/META-INF/ openwebbeans/microwave/trunk/microwave-junit/src/main/ resources/META-INF/LICENSE openwebbeans/microwave/trunk/microwave-junit/src/main/ resources/META-INF/NOTICE openwebbeans/microwave/trunk/microwave-maven-plugin/src/main/resources/ openwebbeans/microwave/trunk/microwave-maven-plugin/src/ main/resources/META-INF/ openwebbeans/microwave/trunk/microwave-maven-plugin/src/ main/resources/META-INF/LICENSE openwebbeans/microwave/trunk/microwave-maven-plugin/src/ main/resources/META-INF/NOTICE Modified: openwebbeans/microwave/trunk/microwave-core/pom.xml openwebbeans/microwave/trunk/microwave-doc/pom.xml openwebbeans/microwave/trunk/microwave-doc/src/main/jbake/ templates/footer.gsp openwebbeans/microwave/trunk/pom.xml Added: openwebbeans/microwave/trunk/LICENSE URL: http://svn.apache.org/viewvc/openwebbeans/microwave/trunk/ LICENSE?rev=1766878&view=auto == --- openwebbeans/microwave/trunk/LICENSE (added) +++ openwebbeans/microwave/trunk/LICENSE Thu Oct 27 20:10:21 2016 @@ -0,0 +1,201 @@ + Apache License + Version 2.0, January 2004 +http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred fo
[microwave] name selection
Hi guys, I quite like microwave name but have 2 questions on it: 1- is it fine legally speaking? we all think to the kitchen probably but this one would be ok cause not on the same "area" but found some github projects as well. Even if far from what we do I wonder if it is an issue 2- if 1 is ok: do you like it or do we try to get another one? if 1 is ko: any proposal? Side note: this kind of discussion can be "long" so let's try to time box it to this 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>
[microwave] site preview
Hi guys, last week I worked a bit on getting a microwave site. It is based on jbake and still experimental but uploaded it on my home @asf (take care links are broken since not deployed as expected yet but you should be able to manage it ;)): http://home.apache.org/~rmannibucau/microwave-snapshot/ Feedback and help welcomed 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>
