Replication fails with OWB 1.1.4

[Thomas Andraschko]

Hi,

weeks ago, i created an issue that OWB failover does not work anymore. The
issue was a compatiblity mismatch between MSM (memcached-session-manager)
and Tomcat 7.0.21 or higher.
Currently we stay with Tomcat 7.0.21 and our replication works fine.
Today i upgraded to OWB 1.1.4 and our failover does not work again.

Was anything changed in the failover logic between 1.1.3 and 1.1.4?

Thanks,
Thomas

Re: Replication fails with OWB 1.1.4

[Thomas Andraschko]

Hi Mark!

it seems that this few tiny bits breaks the replication :)

With new behavior, you mean the behavior with Tomcat 7.0.22+?
Why do we need an ServletFilter AND a Valve?

Configuration via context/host etc. or web.xml is ofc ok!

Regards,
Thomas

2012/4/25 Mark Struberg strub...@yahoo.de

 Hi, yes, I changed a bit, but really only a few tiny bits.

 Last week I also talked with Peter Roßbach who is on the Apache Tomcat
 PMC. We went through the Servlet-3.0 spec and it seems that the new
 behaviour is in sync with the spec!

 Which means we need to explore alternative ways to integrate the
 FailoverService. I'd we provide a ServletFilter and a TomcatValve to
 trigger it and completely remove the triggering of the
 SessionContext-Session copying from the ServletListener at all.

 That would allow to integrate it either on server level or at least via
 web.xml.

 wdyt?

 LieGrue,
 strub



 - Original Message -
  From: Thomas Andraschko zoi...@googlemail.com
  To: dev@openwebbeans.apache.org
  Cc:
  Sent: Wednesday, April 25, 2012 10:59 AM
  Subject: Replication fails with OWB 1.1.4
 
  Hi,
 
  weeks ago, i created an issue that OWB failover does not work anymore.
 The
  issue was a compatiblity mismatch between MSM (memcached-session-manager)
  and Tomcat 7.0.21 or higher.
  Currently we stay with Tomcat 7.0.21 and our replication works fine.
  Today i upgraded to OWB 1.1.4 and our failover does not work again.
 
  Was anything changed in the failover logic between 1.1.3 and 1.1.4?
 
  Thanks,
  Thomas
 

Re: Replication fails with OWB 1.1.4

[Thomas Andraschko]

all right :)

 Just to have the choice for other servlet engines. In Tomcat you will
most probably use the Valve. In other environments you can still use the
Filter. But you will probably never use both ;)

Ahh. Do you mean, ServletFilter will be called BEFORE session replication?

2012/4/25 Mark Struberg strub...@yahoo.de

  it seems that this few tiny bits breaks the replication :)

 Well, I take the responsibility - will clean up the mess soon ;)



  With new behavior, you mean the behavior with Tomcat 7.0.22+?

 Yes, seems this is because they 'fixed' the tomcat behaviour to match the
 clarifications in the servlet-3.0 spec.


  Why do we need an ServletFilter AND a Valve?

 Just to have the choice for other servlet engines. In Tomcat you will most
 probably use the Valve. In other environments you can still use the Filter.
 But you will probably never use both ;)

 Got me?

 LieGrue,
 strub


 - Original Message -
  From: Thomas Andraschko zoi...@googlemail.com
  To: dev@openwebbeans.apache.org; Mark Struberg strub...@yahoo.de
  Cc:
  Sent: Wednesday, April 25, 2012 2:50 PM
  Subject: Re: Replication fails with OWB 1.1.4
 
  Hi Mark!
 
  it seems that this few tiny bits breaks the replication :)
 
  With new behavior, you mean the behavior with Tomcat 7.0.22+?
  Why do we need an ServletFilter AND a Valve?
 
  Configuration via context/host etc. or web.xml is ofc ok!
 
  Regards,
  Thomas
 
  2012/4/25 Mark Struberg strub...@yahoo.de
 
   Hi, yes, I changed a bit, but really only a few tiny bits.
 
   Last week I also talked with Peter Roßbach who is on the Apache Tomcat
   PMC. We went through the Servlet-3.0 spec and it seems that the new
   behaviour is in sync with the spec!
 
   Which means we need to explore alternative ways to integrate the
   FailoverService. I'd we provide a ServletFilter and a TomcatValve to
   trigger it and completely remove the triggering of the
   SessionContext-Session copying from the ServletListener at all.
 
   That would allow to integrate it either on server level or at least via
   web.xml.
 
   wdyt?
 
   LieGrue,
   strub
 
 
 
   - Original Message -
From: Thomas Andraschko zoi...@googlemail.com
To: dev@openwebbeans.apache.org
Cc:
Sent: Wednesday, April 25, 2012 10:59 AM
Subject: Replication fails with OWB 1.1.4
   
Hi,
   
weeks ago, i created an issue that OWB failover does not work
 anymore.
   The
issue was a compatiblity mismatch between MSM
  (memcached-session-manager)
and Tomcat 7.0.21 or higher.
Currently we stay with Tomcat 7.0.21 and our replication works fine.
Today i upgraded to OWB 1.1.4 and our failover does not work again.
   
Was anything changed in the failover logic between 1.1.3 and 1.1.4?
   
Thanks,
Thomas
   
 
 

Rework logger API (OWB-674) breaks failover/serialization

[Thomas Andraschko]

Hi,

AFAICS the old WebBeansLogger was serializable and JUL isn't.
This breaks again the failover because OWB has some or many non-static
loggers. It's really annoying because since 1.1.3, every version destroyed
the failover mechanism.
Is there any reason for non-static loggers? The non-static logger in
FailOverBag destroyes the serialization.

I could provide a patch which will change all loggers to static.

Regards,
Thomas

Re: Rework logger API (OWB-674) breaks failover/serialization

[Thomas Andraschko]

This loggers could be static:

PluginLoader
AbstractMetaDataDiscovery
OsgiMetaDataScannerService
FailOverBag
FailOverBagWrapper


There are 2 other classes where it can't be static without changes. Should
we set them as transient?

WebContainerLifecycle
AbstractLifeCycle


2012/8/31 Thomas Andraschko zoi...@gmail.com

 Hi,

 AFAICS the old WebBeansLogger was serializable and JUL isn't.
 This breaks again the failover because OWB has some or many non-static
 loggers. It's really annoying because since 1.1.3, every version destroyed
 the failover mechanism.
 Is there any reason for non-static loggers? The non-static logger in
 FailOverBag destroyes the serialization.

 I could provide a patch which will change all loggers to static.

 Regards,
 Thomas

OWB-702

[Thomas Andraschko]

Hi,

i have already done some refactoring, fixed a bug because passivation
removes the bag from the session and added unit tests for the whole
failover stuff.

I've sent the patch to mark for reviewing first because i didn't dare to
create a issue + patch without reviewing :)

Should i maybe attach my patch to this ticket?

Regards,
Thomas

Re: Fw: [DISCUSS] release OWB-1.1.6 end of this week?

[Thomas Andraschko]

Hi Mark,

it's already fixed but i attached an patch with some refactoring +
unittests to #OWB-702.
I know that i could commit it but it would be great if anyone could review
it :)

Regards,
Thomas

2012/9/12 Mark Struberg strub...@yahoo.de

 2nd try as my previous got eaten by the spam filter :/





 - Forwarded Message -
 From: Mark Struberg strub...@yahoo.de
 To: openwebbeans-dev dev@openwebbeans.apache.org
 Sent: Wednesday, September 12, 2012 7:49 PM
 Subject: [DISCUSS] releaese OWB-1.1.6 end of this week?
 
 
 Hi folks!
 
 I would like to start with a hot-fix release of OWB (version 1.1.6) end
 of this week.
 Thomas, is this an ok timeframe in which you can fix the issues you
 needed for your production?
 
 LIeGrue,
 strub
 
 
 
 
 

Re: Fw: [DISCUSS] release OWB-1.1.6 end of this week?

[Thomas Andraschko]

i know, sorry. Should i deactivate remove trailing spaces in my IDE?

2012/9/12 Joseph Bergmark bergm...@apache.org

 I started to review the patch, and the changes I saw looked good, but
 there is so much whitespace reformatting in that patch that its hard
 to focus on just the implementation changes.

 Sincerely,

 Joe

 On Wed, Sep 12, 2012 at 2:24 PM, Thomas Andraschko zoi...@gmail.com
 wrote:
  Hi Mark,
 
  it's already fixed but i attached an patch with some refactoring +
  unittests to #OWB-702.
  I know that i could commit it but it would be great if anyone could
 review
  it :)
 
  Regards,
  Thomas
 
  2012/9/12 Mark Struberg strub...@yahoo.de
 
  2nd try as my previous got eaten by the spam filter :/
 
 
 
 
 
  - Forwarded Message -
  From: Mark Struberg strub...@yahoo.de
  To: openwebbeans-dev dev@openwebbeans.apache.org
  Sent: Wednesday, September 12, 2012 7:49 PM
  Subject: [DISCUSS] releaese OWB-1.1.6 end of this week?
  
  
  Hi folks!
  
  I would like to start with a hot-fix release of OWB (version 1.1.6) end
  of this week.
  Thomas, is this an ok timeframe in which you can fix the issues you
  needed for your production?
  
  LIeGrue,
  strub
  
  
  
  
  
 

Re: Fw: [DISCUSS] release OWB-1.1.6 end of this week?

[Thomas Andraschko]

@Joe
Yey, i use eclipse :) That would be great!

@Mark
all right, thanks for the infos!

2012/9/12 Joseph Bergmark bergm...@apache.org

 I'm not at all sure whats leading to the whitespace differences.  Do
 you use Eclipse?  If so I can send you the eclipse formatter that
 Gurkan sent me a couple years back.

 Sincerely,

 Joe

 On Wed, Sep 12, 2012 at 2:38 PM, Thomas Andraschko zoi...@gmail.com
 wrote:
  i know, sorry. Should i deactivate remove trailing spaces in my IDE?
 
  2012/9/12 Joseph Bergmark bergm...@apache.org
 
  I started to review the patch, and the changes I saw looked good, but
  there is so much whitespace reformatting in that patch that its hard
  to focus on just the implementation changes.
 
  Sincerely,
 
  Joe
 
  On Wed, Sep 12, 2012 at 2:24 PM, Thomas Andraschko zoi...@gmail.com
  wrote:
   Hi Mark,
  
   it's already fixed but i attached an patch with some refactoring +
   unittests to #OWB-702.
   I know that i could commit it but it would be great if anyone could
  review
   it :)
  
   Regards,
   Thomas
  
   2012/9/12 Mark Struberg strub...@yahoo.de
  
   2nd try as my previous got eaten by the spam filter :/
  
  
  
  
  
   - Forwarded Message -
   From: Mark Struberg strub...@yahoo.de
   To: openwebbeans-dev dev@openwebbeans.apache.org
   Sent: Wednesday, September 12, 2012 7:49 PM
   Subject: [DISCUSS] releaese OWB-1.1.6 end of this week?
   
   
   Hi folks!
   
   I would like to start with a hot-fix release of OWB (version 1.1.6)
 end
   of this week.
   Thomas, is this an ok timeframe in which you can fix the issues you
   needed for your production?
   
   LIeGrue,
   strub
   
   
   
   
   
  
 

Re: [DISCUSS] release OWB-1.1.6 end of this week?

[Thomas Andraschko]

Hi,

i will commit today :)

Regards,
Thomas

2012/9/15 Mark Struberg strub...@yahoo.de

 Hi David!

 I can roll the release tonight or tomorrow morning.
 Udo still likes to get a few things done afaik. UnitTests and stuff...


 Thomas, did you commit all your changes which you have Jiras created for?

 LieGrue,
 strub



 - Original Message -
  From: David Blevins david.blev...@gmail.com
  To: dev@openwebbeans.apache.org; Mark Struberg strub...@yahoo.de
  Cc:
  Sent: Saturday, September 15, 2012 10:56 AM
  Subject: Re: [DISCUSS] release OWB-1.1.6 end of this week?
 
 G ot the ASM support finished.  OWB-701 officially closed.
 
  We still use Javassist by default, but we have the ability to use ASM.
 
  Mark, do you need help with the release?  (I know you have a *very* busy
 week
  coming up :)
 
 
  -David
 
  On Sep 12, 2012, at 11:03 AM, Mark Struberg wrote:
 
   2nd try as my previous got eaten by the spam filter :/
 
 
 
 
 
   - Forwarded Message -
   From: Mark Struberg strub...@yahoo.de
   To: openwebbeans-dev dev@openwebbeans.apache.org
   Sent: Wednesday, September 12, 2012 7:49 PM
   Subject: [DISCUSS] releaese OWB-1.1.6 end of this week?
 
 
   Hi folks!
 
   I would like to start with a hot-fix release of OWB (version 1.1.6)
 end
  of this week.
   Thomas, is this an ok timeframe in which you can fix the issues you
  needed for your production?
 
   LIeGrue,
   strub
 
 
 
 
 
 
 

JIRA permissions

[Thomas Andraschko]

Hi,

how can i change the assignee of a ticket to myself or mark the issue as
fixed? I can't find any button/view for this :)
Do i need special permissions?

Regards,
Thomas

Re: Eclipse/Checkstyle errors

[Thomas Andraschko]

It's only in test-classes because the won't be checked by maven.
For example - AbstractUnitTest#addExtension

2012/9/15 Joseph Bergmark bergm...@apache.org

 Which test classes are you getting check style errors in?  When I
 build on the command line I don't see any check style errors:

 [INFO] --- maven-checkstyle-plugin:2.7:check (verify-style) @
 openwebbeans-web ---
 [INFO]
 [INFO]


 [INFO] --- maven-checkstyle-plugin:2.7:check (verify-style) @
 openwebbeans-impl ---
 [INFO]
 [INFO]

 etc..

 Sincerely,

 Joe

 On Sat, Sep 15, 2012 at 12:26 PM, Thomas Andraschko zoi...@gmail.com
 wrote:
  Hi,
 
  we have many checkstyle errors (not warnings) in the test classes.
  Can i fix them or should i exclude (don't know if possible in Eclipse)
 the
  test classes from checkstyle?
  The most errors are { should be on a new line and naming errors of
  constants and variables.
 
  Also i have many eclipse errors that @PostConstruct, @PreDestory,
  @WebServiceRef etc are not accessible.
  Can we add this APIs with provided scope or is there any better solution?
 
  Regards,
  Thomas

Re: Eclipse/Checkstyle errors

[Thomas Andraschko]

I use the same rules as the maven plugin, you must just import the settings.
The problem is that maven-checkstyle-plugin does not check the test-src but
eclipse does (per default).

So what do you think? should we fix this errors or should the developers
exclude test classes?

2012/9/15 Joseph Bergmark bergm...@apache.org

 I haven't used the checkstyle plugin for Eclipse, so afraid I can't
 provide much advice here.  Its too bad it doesn't appear to follow the
 same rules as the maven plugin.

 Sincerely,

 Joe

 On Sat, Sep 15, 2012 at 1:15 PM, Thomas Andraschko zoi...@gmail.com
 wrote:
  It's only in test-classes because the won't be checked by maven.
  For example - AbstractUnitTest#addExtension
 
  2012/9/15 Joseph Bergmark bergm...@apache.org
 
  Which test classes are you getting check style errors in?  When I
  build on the command line I don't see any check style errors:
 
  [INFO] --- maven-checkstyle-plugin:2.7:check (verify-style) @
  openwebbeans-web ---
  [INFO]
  [INFO]
 
 
  [INFO] --- maven-checkstyle-plugin:2.7:check (verify-style) @
  openwebbeans-impl ---
  [INFO]
  [INFO]
 
  etc..
 
  Sincerely,
 
  Joe
 
  On Sat, Sep 15, 2012 at 12:26 PM, Thomas Andraschko zoi...@gmail.com
  wrote:
   Hi,
  
   we have many checkstyle errors (not warnings) in the test classes.
   Can i fix them or should i exclude (don't know if possible in Eclipse)
  the
   test classes from checkstyle?
   The most errors are { should be on a new line and naming errors of
   constants and variables.
  
   Also i have many eclipse errors that @PostConstruct, @PreDestory,
   @WebServiceRef etc are not accessible.
   Can we add this APIs with provided scope or is there any better
 solution?
  
   Regards,
   Thomas
 

Re: Eclipse/Checkstyle errors

[Thomas Andraschko]

all right! And what about the checkstyle errors?

2012/9/16 Mark Struberg strub...@yahoo.de

 yes, we had requests from _huge_ users running old WAS on mainframes.
 Among those are big stock exchanges, banks and a big western defence pact...





 - Original Message -
  From: Romain Manni-Bucau rmannibu...@gmail.com
  To: dev@openwebbeans.apache.org
  Cc:
  Sent: Sunday, September 16, 2012 12:15 PM
  Subject: Re: Eclipse/Checkstyle errors
 
  for checkstyle fix them if you activate it in mvn build otherwise i fear
  some of us will not check it (i know i'm part of them)
 
  about @Override: do we still target j5?
 
  *Romain Manni-Bucau*
  *Twitter: @rmannibucau*
  *Blog: http://rmannibucau.wordpress.com*
 
 
 
 
  2012/9/16 Thomas Andraschko zoi...@gmail.com
 
   I would fix it, that's no problem.
 
   We also have many compiler warnings because sometimes @Override is
 used for
   implemented methods in test classes, which is not compatible to Java
 1.5.
 
   Could i create tickets for @Override and checkstyle errors in
 test-classes?
   I would fix them for 1.1.7.
 
   2012/9/15 David Jencks david_jen...@yahoo.com
 
My opinion as a pretty much completely inactive contributor to OWB is
   that
it would be better to have the test classes follow the same style
  rules
   as
the main code, but I'm not prepared to help fix it.
   
thanks
david jencks
   
 
 

Re: [VOTE] release Apache OpenWebBeans build tools 1.2

[Thomas Andraschko]

+1

2012/9/16 Mark Struberg strub...@yahoo.de



 Hi!


 I'd like to call a VOTE on releasing Apache OpenWebBeans build-tools-1.2.
 This release is needed for shipping OWB.


 We just relaxed the method length rules a bit.Maven staging repo:

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


 SVN source tag:

 https://svn.apache.org/repos/asf/openwebbeans/build-tools/tags/checkstyle-rules-1.2/

 Source release:


 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-001/org/apache/openwebbeans/build-tools/checkstyle-rules/1.2/checkstyle-rules-1.2-source-release.zip

 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

Re: [VOTE] [take-2] release Apache OpenWebBeans 1.1.6

[Thomas Andraschko]

+1

looks great! :)

2012/9/26 Mark Struberg strub...@yahoo.de



  Hi!

 I'd again like to call a VOTE on releasing Apache OpenWebBeans-1.1.6 . I
 fixed the issues which stopped our first attempt

 This
 is a bugfix release of OpenWebBeans-1.1.x, thus no branch has been
 created. It mainly contains compatibility/portability/performance
 improvements and small bugfixes.

 The ReleaseNotes are available online:

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


 Maven staging repo:


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


 SVN source tag (r 1390181):

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


 Source release:


 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-043/org/apache/openwebbeans/openwebbeans/1.1.6/openwebbeans-1.1.6-source-release.zip


 Binary release:


 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-043/org/apache/openwebbeans/openwebbeans-distribution/1.1.6/openwebbeans-distribution-1.1.6-binary.tar.gz


 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

Re: New Maven Module : Failover Cluster

[Thomas Andraschko]

Hi Gurkan,

what logic do you mean?
The failover logic is in the openwebbeans-web module and it's only used by
the web and resource module (StandaloneResourceInjectionService).

Regards,
Thomas

2012/10/11 Gurkan Erdogdu gurkanerdo...@yahoo.com

 Hello folks

 In coming days I will be thinking about introduce new maven project
 openwebbeans-cluster and remove all of the failover and cluster logic from
 openwebbeans-core. My point is to remove all Java EE related features from
 openwebbeans-core and include them into specific modules.

 WDYT?

 Gurkan

Re: 1.1.8 or 1.2.0 ?

[Thomas Andraschko]

Hi Mark,

+1 for 1.2.0.
Do we completely remove javasisst? If yes, i would like to so some failover
refactoring, too.

Regards,
Thomas

2012/11/10 Mark Struberg strub...@yahoo.de

 Hi folks!

 Removing functionality from webbeans-impl into an own module + changes in
 the API might be too big a change for a bugfix release.

 So I'd rather bump the minor version as well and work towards a 1.2.0.
 This would also allow us to finish the 85% finished move to ASM as well as
 finally committing the HierarchicScannerService and HierarchicBeanManager
 we need for properly supporting EARs.

 wdyt?

 LieGrue,
 strub

Re: December 2012 Board Report

[Thomas Andraschko]

Sorry for off-topic but should i have permissions to open this page? :)

2012/12/10 Jean-Louis MONTEIRO jeano...@gmail.com

 Thanks Mark ;-)


 2012/12/10 Mark Struberg strub...@yahoo.de

  Jean Louis Monteiro got added as committer lately (was long time overdue
  btw ;).
 
 
  LieGrue,
  strub
 
 
 
  - Original Message -
   From: Gurkan Erdogdu gurkanerdo...@yahoo.com
   To: openwebbeans-dev dev@openwebbeans.apache.org
   Cc:
   Sent: Sunday, December 9, 2012 9:54 PM
   Subject: December 2012 Board Report
  
  
  
   Hi
  
   Time to report.  I have written December 2012 at
   https://cwiki.apache.org/confluence/display/OWB/December2012
  
   Please have a look and add/update/delete?
  
   Thanks,
  
   Gurkan
  
 



 --
 Jean-Louis

Re: December 2012 Board Report

[Thomas Andraschko]

thanks gerhard, it's working now :)

2012/12/10 Gerhard Petracek gerhard.petra...@gmail.com

 @thomas:

 please try it again.

 regards,
 gerhard



 2012/12/10 Mark Struberg strub...@yahoo.de

  To be honest, I don't know ;)
 
  In any case, I've added Jean-Louis' committership to the report.
 
  LieGrue,
  strub
 
 
 
 
  - Original Message -
   From: Thomas Andraschko zoi...@gmail.com
   To: dev@openwebbeans.apache.org
   Cc:
   Sent: Monday, December 10, 2012 2:38 PM
   Subject: Re: December 2012 Board Report
  
   Sorry for off-topic but should i have permissions to open this page? :)
  
   2012/12/10 Jean-Louis MONTEIRO jeano...@gmail.com
  
Thanks Mark ;-)
  
  
2012/12/10 Mark Struberg strub...@yahoo.de
  
 Jean Louis Monteiro got added as committer lately (was long time
   overdue
 btw ;).


 LieGrue,
 strub



 - Original Message -
  From: Gurkan Erdogdu gurkanerdo...@yahoo.com
  To: openwebbeans-dev dev@openwebbeans.apache.org
  Cc:
  Sent: Sunday, December 9, 2012 9:54 PM
  Subject: December 2012 Board Report
 
 
 
  Hi
 
  Time to report.  I have written December 2012 at
  https://cwiki.apache.org/confluence/display/OWB/December2012
 
  Please have a look and add/update/delete?
 
  Thanks,
 
  Gurkan
 

  
  
  
--
Jean-Louis
  
  
 

Re: new proxy benches

[Thomas Andraschko]

Great improvement, cool! :)

2013/1/15 Mark Struberg strub...@yahoo.de

 10 million invocations on 6 different methods each time:

 with the new proxies + new interceptors:
 Starting the real bench
 took: 6530479 (6.5 seconds)

 

 with the new proxies + OLD interceptors:
 Starting the real bench
 took: .. I gave up...
 for 1 million invocations it takes: 91909823 (92 seconds for 1/10 of the
 invocations)
 - factor 110...
 There is something bloody broken in this situation...

 

 I was almost worried about the next benchmark:
 OLD proxies + OLD interceptors
 But it seems that the caching of intercepted methods helped a lot.
 For 10 million invocations I got
 took: 37578725 (37.5 seconds)



 The new proxies don't look bad after all. And we didn't even start
 performance tuning...


 See InterceptorProxyChainTest.

 For enabling the new proxies you need to set

 WebBeansContext#TODO_USING_NEW_INTERCEPTORS to true

 LieGrue,
 strub

Re: [VOTE] (take2) Release Apache OpenWebBeans 1.1.8

[Thomas Andraschko]

+1

2013/3/18 Gurkan Erdogdu gurkanerdo...@yahoo.com

 +1

 
  Kimden: Mark Struberg strub...@yahoo.de
 Kime: openwebbeans-dev dev@openwebbeans.apache.org
 Gönderildiği Tarih: 17 Mart 2013 19:01 Pazar
 Konu: [VOTE] (take2) Release Apache OpenWebBeans 1.1.8


 Hi!


 2nd try ;)

 I'd like to call a VOTE on releasing Apache OpenWebBeans-1.1.8 .

 This is a bugfix release of OpenWebBeans-1.1.x, thus it's maintained in a
 maintenance branch.
 This
 release mainly contains small bugfixes. The most prominent new feature
 is the addition of the owb-arquillian-standalone adaptor for the JBoss(tm)
 Arquillian testing framework (which is ALv2 licensed).

 The ReleaseNotes are available online:

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

 Maven staging repo:


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

 SVN source tag:
 https://svn.apache.org/repos/asf/openwebbeans/tags/openwebbeans-1.1.8/

 Source Release:

 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-008/org/apache/openwebbeans/openwebbeans/1.1.8/openwebbeans-1.1.8-source-release.zip

 Binary release:

 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-008/org/apache/openwebbeans/openwebbeans-distribution/1.1.8/openwebbeans-distribution-1.1.8-binary.tar.gz

 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

SVN forbidden

[Thomas Andraschko]

Hi,

is there something wrong with SVN the last 2 days?
I always get following error:

svn: MKACTIVITY of
'/repos/asf/!svn/act/77db735f-3e01-0010-b369-8b3936c519d7': 403 Forbidden (
http://svn.apache.org)

I already tried to delete my eclipse keyring, to enter my user/pw again but
somehow i get this error before the user/pw popup.

Regards,
Thomas

Re: SVN forbidden

[Thomas Andraschko]

same :/


2013/5/1 Romain Manni-Bucau rmannibu...@gmail.com

 Got some issues too, maybe try svn.us.apache.org
 Le 1 mai 2013 11:40, Thomas Andraschko andraschko.tho...@gmail.com a
 écrit :

  Hi,
 
  is there something wrong with SVN the last 2 days?
  I always get following error:
 
  svn: MKACTIVITY of
  '/repos/asf/!svn/act/77db735f-3e01-0010-b369-8b3936c519d7': 403
 Forbidden (
  http://svn.apache.org)
 
  I already tried to delete my eclipse keyring, to enter my user/pw again
 but
  somehow i get this error before the user/pw popup.
 
  Regards,
  Thomas
 

Re: SVN forbidden

[Thomas Andraschko]

Still occurs :/
Who should i contact or should i just wait some days?


2013/5/1 Thomas Andraschko andraschko.tho...@gmail.com

 same :/


 2013/5/1 Romain Manni-Bucau rmannibu...@gmail.com

 Got some issues too, maybe try svn.us.apache.org
 Le 1 mai 2013 11:40, Thomas Andraschko andraschko.tho...@gmail.com a
 écrit :

  Hi,
 
  is there something wrong with SVN the last 2 days?
  I always get following error:
 
  svn: MKACTIVITY of
  '/repos/asf/!svn/act/77db735f-3e01-0010-b369-8b3936c519d7': 403
 Forbidden (
  http://svn.apache.org)
 
  I already tried to delete my eclipse keyring, to enter my user/pw again
 but
  somehow i get this error before the user/pw popup.
 
  Regards,
  Thomas
 

Re: SVN forbidden

[Thomas Andraschko]

How should i contact them?
There is a list of cases and how people should contact them but i didn't
find my case :D


2013/5/2 Mark Struberg strub...@yahoo.de

 +1 for asking infra.

 LieGrue,
 strub



 - Original Message -
  From: Romain Manni-Bucau rmannibu...@gmail.com
  To: dev@openwebbeans.apache.org
  Cc:
  Sent: Thursday, 2 May 2013, 19:36
  Subject: Re: SVN forbidden
 
  Maybe ask infra
  Le 2 mai 2013 19:27, Thomas Andraschko
  andraschko.tho...@gmail.com a
  écrit :
 
   Still occurs :/
   Who should i contact or should i just wait some days?
 
 
   2013/5/1 Thomas Andraschko andraschko.tho...@gmail.com
 
same :/
   
   
2013/5/1 Romain Manni-Bucau rmannibu...@gmail.com
   
Got some issues too, maybe try svn.us.apache.org
Le 1 mai 2013 11:40, Thomas Andraschko
  andraschko.tho...@gmail.com
   a
écrit :
   
 Hi,

 is there something wrong with SVN the last 2 days?
 I always get following error:

 svn: MKACTIVITY of

  '/repos/asf/!svn/act/77db735f-3e01-0010-b369-8b3936c519d7': 403
Forbidden (
 http://svn.apache.org)

 I already tried to delete my eclipse keyring, to enter my
  user/pw
   again
but
 somehow i get this error before the user/pw popup.

 Regards,
 Thomas

   
   
   
 
 

Re: 1.2.0 release end spurt

[Thomas Andraschko]

Hi Mark,

i will try to commit my stuff tomorrow. Hopefully it works, otherwise i
must contant infra team first.

Regards,
Thomas


2013/5/5 Mark Struberg strub...@yahoo.de

 Hi!

 Gonna try to start with the owb-1.2.0 release on tuesday or so.
 Please look over the open issues and close what is already resolved. Or
 even catch a few low hanging fruits ;)

 LieGrue,
 strub

Re: [VOTE] [CANCELLED] release Apache OpenWebBeans-1.2.0

[Thomas Andraschko]

Is there already a new snapshot available somewhere?
I would try it with my current app.


2013/5/10 Mark Struberg strub...@yahoo.de

 Hi folks!

 I'll reroll the release this evening.

 We will _not_ exclude the webbeans-cdi11 module from the source release
 but we don't ship any binaries for it.

 The reason is that we must not ship any CDI-1.1 binaries without passing
 the TCK. But there is no reason not to ship a mechanism to create a compat
 package.


 The reroll will contain Arnes fixes for the AnnotatedType and a few other
 minor things.

 LieGrue,
 strub



 - Original Message -
  From: Arne Limburg arne.limb...@openknowledge.de
  To: u...@openwebbeans.apache.org u...@openwebbeans.apache.org
  Cc:
  Sent: Thursday, 9 May 2013, 18:32
  Subject: Re: [VOTE] release Apache OpenWebBeans-1.2.0
 
 T hanks Harald for catching this one.
 
  That's a serious one. I'll fix it and we re-roll the release.
 
  Cheers,
  Arne
 
  Am 09.05.13 18:15 schrieb Harald Wellmann unter
  hwellmann...@gmail.com:
 
  -1 (non-binding)
 
  Looks like there is a regression regarding
  BeforeBeanDiscovery.addAnnotatedType(), compared to 1.1.8.
 
  Adding more than one type has no effect.
 
  The following method in BeanManagerImpl looks suspicious:
 
   public void addAdditionalAnnotatedType(AnnotatedType?
  annotatedType)
   {
 
 
 webBeansContext.getAnnotatedElementFactory().setAnnotatedType(annotatedTyp
  e);
   additionalAnnotatedTypes.put(null, annotatedType);
   }
 
  All additional types are added with the same null key.
 
  Best regards,
  Harald
 
 
 

Re: [VOTE] Release Apache OpenWebBeans build-tools 1.3

[Thomas Andraschko]

+1


2013/5/14 Romain Manni-Bucau rmannibu...@gmail.com

 +1

 *Romain Manni-Bucau*
 *Twitter: @rmannibucau https://twitter.com/rmannibucau*
 *Blog: **http://rmannibucau.wordpress.com/*
 http://rmannibucau.wordpress.com/
 *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
 *Github: https://github.com/rmannibucau*



 2013/5/14 Mark Struberg strub...@yahoo.de

  Hi!
 
  This is now a split VOTE for owb-build-tools-1.3
 
  The stating repo is up here:
 
 
 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-016/
 
 
  The sources can be found at
 
 
 
 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-016/org/apache/openwebbeans/build-tools/checkstyle-rules/1.3/checkstyle-rules-1.3-source-release.zip
 
  The tag in SVN is here
 
 
 
 https://svn.apache.org/repos/asf/openwebbeans/build-tools/tags/checkstyle-rules-1.3/
  The VOTE will be open for 72 hours.
  [ ] +1 approve
  [ ] +0 no opinion
  [ ] -1 veto (and reason why)
 
  LieGrue,
  strub
 

Re: [VOTE] take 3: Release Apache OpenWebBeans-1.2.0

[Thomas Andraschko]

+1


2013/5/21 Mark Struberg strub...@yahoo.de

 +1

 LieGrue,
 strub



 - Original Message -
  From: Mark Struberg strub...@yahoo.de
  To: openwebbeans-dev dev@openwebbeans.apache.org
  Cc:
  Sent: Sunday, 19 May 2013, 7:49
  Subject: [VOTE] take 3: Release Apache OpenWebBeans-1.2.0
 
  I'd like to call a 3rd take to VOTE on releasing Apache
 OpenWebBeans-1.2.0 .
 
  This is the first release of the OpenWebBeans-1.2.x branch.
  This release changed many internal mechanics but still targets
  the CDI-1.0 specification.
 
  Please note that the source binary contains a few non-enabled modules
 like
  webbeans-cdi11. They do pass RAT though.
 
 
  The ReleaseNotes are available online:
 
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310844version=12315461
 
  Maven staging repo:
 
 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-013/
 
  SVN source tag:
  https://svn.apache.org/repos/asf/openwebbeans/tags/openwebbeans-1.2.0/
 
  Source Release:
 
 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-013/org/apache/openwebbeans/openwebbeans/1.2.0/openwebbeans-1.2.0-source-release.zip
 
  Binary release:
 
 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-013/org/apache/openwebbeans/openwebbeans-distribution/1.2.0/openwebbeans-distribution-1.2.0-binary.zip
 
  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
 

ClassCastException with CODI and OWB 1.2.0

[Thomas Andraschko]

Hi,

today i tried to upgrade OWB from 1.1.5 to 1.2.0 but i get following
exception with CODI (1.0.5):

java.lang.ClassCastException:
org.apache.myfaces.extensions.cdi.jsf2.impl.scope.mapped.Jsf2BeanWrapper
cannot be cast to org.apache.webbeans.portable.AnnotatedTypeImpl
at
org.apache.webbeans.portable.AnnotatedElementFactory.newAnnotatedType(AnnotatedElementFactory.java:142)
at
org.apache.webbeans.config.BeansDeployer.deployFromClassPath(BeansDeployer.java:534)
at
org.apache.webbeans.config.BeansDeployer.deploy(BeansDeployer.java:183)
at
org.apache.webbeans.lifecycle.AbstractLifeCycle.startApplication(AbstractLifeCycle.java:129)
at
org.apache.webbeans.web.lifecycle.WebContainerLifecycle.startApplication(WebContainerLifecycle.java:89)
at
org.apache.webbeans.servlet.WebBeansConfigurationListener.contextInitialized(WebBeansConfigurationListener.java:85)
at
org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:787)
at
org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:434)
at
org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:779)
at
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:284)
at
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1322)
at
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:731)
at
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:490)
at
org.eclipse.jetty.maven.plugin.JettyWebAppContext.doStart(JettyWebAppContext.java:280)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:108)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:90)
at
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:58)
at
org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:108)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:90)
at
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:58)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:108)
at org.eclipse.jetty.server.Server.start(Server.java:342)

I also tried 1.2.1-SNAPSHOT but it's the same exception.
Any idea?

Regards,
Thomas

Re: ClassCastException with CODI and OWB 1.2.0

[Thomas Andraschko]

A trunk build works fine! thanks!


2013/9/20 Thomas Andraschko andraschko.tho...@gmail.com

 Hi Mark,

 i just tried a maven snapshot but i will try to trunk build on monday :)

 Regards,
 Thomas


 2013/9/20 Mark Struberg strub...@yahoo.de

 The latest 1.2.1-SNAPSHOT crashes as well?
 That's weird. I can understand the issue with 1.2.0 as we had a cast in
 there.
 But this cast doesn't exist with 1.2.1 anymore.
 Can you please compile 1.2.1 from trunk and try again?

 LieGrue,
 strub




 - Original Message -
  From: Thomas Andraschko andraschko.tho...@gmail.com
  To: dev@openwebbeans.apache.org
  Cc:
  Sent: Friday, 20 September 2013, 16:12
  Subject: ClassCastException with CODI and OWB  1.2.0
 
  Hi,
 
  today i tried to upgrade OWB from 1.1.5 to 1.2.0 but i get following
  exception with CODI (1.0.5):
 
  java.lang.ClassCastException:
  org.apache.myfaces.extensions.cdi.jsf2.impl.scope.mapped.Jsf2BeanWrapper
  cannot be cast to org.apache.webbeans.portable.AnnotatedTypeImpl
  at
 
 org.apache.webbeans.portable.AnnotatedElementFactory.newAnnotatedType(AnnotatedElementFactory.java:142)
  at
 
 org.apache.webbeans.config.BeansDeployer.deployFromClassPath(BeansDeployer.java:534)
  at
  org.apache.webbeans.config.BeansDeployer.deploy(BeansDeployer.java:183)
  at
 
 org.apache.webbeans.lifecycle.AbstractLifeCycle.startApplication(AbstractLifeCycle.java:129)
  at
 
 org.apache.webbeans.web.lifecycle.WebContainerLifecycle.startApplication(WebContainerLifecycle.java:89)
  at
 
 org.apache.webbeans.servlet.WebBeansConfigurationListener.contextInitialized(WebBeansConfigurationListener.java:85)
  at
 
 org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:787)
  at
 
 org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:434)
  at
 
 org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:779)
  at
 
 org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:284)
  at
 
 org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1322)
  at
 
 org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:731)
  at
  org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:490)
  at
 
 org.eclipse.jetty.maven.plugin.JettyWebAppContext.doStart(JettyWebAppContext.java:280)
  at
 
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
  at
 
 org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:108)
  at
 
 org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:90)
  at
 
 org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:58)
  at
 
 org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
  at
 
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
  at
 
 org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:108)
  at
 
 org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:90)
  at
 
 org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:58)
  at
 
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
  at
 
 org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:108)
  at org.eclipse.jetty.server.Server.start(Server.java:342)
 
  I also tried 1.2.1-SNAPSHOT but it's the same exception.
  Any idea?
 
  Regards,
  Thomas
 

Re: Documentation layout suggestions

[Thomas Andraschko]

I mean this points:
*OpenWebBeans CDI testing framework*

• CDI Test Framework


Isn' it exactly the same? It the second point a subpoint or what does it
mean?


2013/10/1 Karl Kildén karl.kil...@gmail.com

 Thomas, exactly what would you prefer merged and after you reply; can you
 others comment on that as well? Thank you.

 Might as well try to get it kinda right the first time even though we can
 update the layout over time ;-)


 On 1 October 2013 21:14, Thomas Andraschko andraschko.tho...@gmail.com
 wrote:

  +1 for the second
 
  I would only merge the last two points
 
 
  2013/10/1 Gerhard Petracek gerhard.petra...@gmail.com
 
   +1
  
   regards,
   gerhard
  
  
  
   2013/10/1 Arne Limburg arne.limb...@openknowledge.de
  
+1 for the second suggestion
I like the Getting Started part to be promoted bigger
   
   
   
Am 01.10.13 20:54 schrieb Karl Kildén unter karl.kil...@gmail.com
 :
   
First things first. We really need to finish the getting started
  part.
Getting started with OWB is not even that much information to
  condense.
While I start with that, please give your input to the documentation
layout. This is basically what you should see when you click
Documentation. Me and Mark discussed it for 2 minutes and have two
   basic
(and very similar) suggestions. Wdyt?

 Suggestion 1:

Second link *OWB explained* is basically what OWB is, it's
   relationship
to JSR-299 etc. Maybe call it something else. *Further
 configuration*
  is
stuff like failover.

*Using OpenWebBeans*

€ Getting started

€ OWB explained

€ Further configuration

€ OWB Samples

*Modules*

€ Modules Overview Page

*OpenWebBeans CDI testing framework*

€ CDI Test Framework


 Suggestion 2:
Basically here Getting started is promoted to a bigger text to be
 more
recognizable. After all, it's the link most visitors want in the
 first
place.

*About OpenWebBeans*

€ General information / OWB explained

*Getting started with OpenWebBeans*

€ Getting started

€ Further configuration

€ OWB Samples

*Modules*

€ Modules Overview Page

*OpenWebBeans CDI testing framework*

€ CDI Test Framework
cheers
   
   
  
 

Re: Documentation layout suggestions

[Thomas Andraschko]

sorry, i mean subpage - not subpoint


2013/10/1 Thomas Andraschko andraschko.tho...@gmail.com

 I mean this points:

 *OpenWebBeans CDI testing framework*

 • CDI Test Framework


 Isn' it exactly the same? It the second point a subpoint or what does it
 mean?


 2013/10/1 Karl Kildén karl.kil...@gmail.com

 Thomas, exactly what would you prefer merged and after you reply; can you
 others comment on that as well? Thank you.

 Might as well try to get it kinda right the first time even though we can
 update the layout over time ;-)


 On 1 October 2013 21:14, Thomas Andraschko andraschko.tho...@gmail.com
 wrote:

  +1 for the second
 
  I would only merge the last two points
 
 
  2013/10/1 Gerhard Petracek gerhard.petra...@gmail.com
 
   +1
  
   regards,
   gerhard
  
  
  
   2013/10/1 Arne Limburg arne.limb...@openknowledge.de
  
+1 for the second suggestion
I like the Getting Started part to be promoted bigger
   
   
   
Am 01.10.13 20:54 schrieb Karl Kildén unter 
 karl.kil...@gmail.com:
   
First things first. We really need to finish the getting started
  part.
Getting started with OWB is not even that much information to
  condense.
While I start with that, please give your input to the
 documentation
layout. This is basically what you should see when you click
Documentation. Me and Mark discussed it for 2 minutes and have
 two
   basic
(and very similar) suggestions. Wdyt?

 Suggestion 1:

Second link *OWB explained* is basically what OWB is, it's
   relationship
to JSR-299 etc. Maybe call it something else. *Further
 configuration*
  is
stuff like failover.

*Using OpenWebBeans*

€ Getting started

€ OWB explained

€ Further configuration

€ OWB Samples

*Modules*

€ Modules Overview Page

*OpenWebBeans CDI testing framework*

€ CDI Test Framework


 Suggestion 2:
Basically here Getting started is promoted to a bigger text to be
 more
recognizable. After all, it's the link most visitors want in the
 first
place.

*About OpenWebBeans*

€ General information / OWB explained

*Getting started with OpenWebBeans*

€ Getting started

€ Further configuration

€ OWB Samples

*Modules*

€ Modules Overview Page

*OpenWebBeans CDI testing framework*

€ CDI Test Framework
cheers
   
   
  
 

Alternative + Named

[Thomas Andraschko]

Hi,

should it actually be possible to overwrite a bean with a alternative named
bean?

e.g -

@Named public class A

with a activated

@Named(a) @Alternative public class A extends B


This somehow just works randomly. Every X container startup, the right bean
will be used with EL.

Thanks.

Regards,
Thomas

Re: Alternative + Named

[Thomas Andraschko]

Hi Mark,

is there any change to get similar behavior?
It's actually a must-have for product development.
We would like to have multiple implementations in our core and just active
them via alternative.
With @Specialized or @Exclude, i can't do it without code changes :/




2013/10/29 Mark Struberg strub...@yahoo.de

 Gee, I fear this is not really well specified.
 I'd rather not bet for it to work.
 Honestly I would have expected that an AmbiguousResolutionException gets
 thrown.

 I'd use @Exclude or @Specializes in this case.

 LieGrue,
 strub




 - Original Message -
  From: Thomas Andraschko andraschko.tho...@gmail.com
  To: dev@openwebbeans.apache.org
  Cc:
  Sent: Tuesday, 29 October 2013, 21:23
  Subject: Alternative + Named
 
  Hi,
 
  should it actually be possible to overwrite a bean with a alternative
 named
  bean?
 
  e.g -
 
  @Named public class A
 
  with a activated
 
  @Named(a) @Alternative public class A extends B
 
 
  This somehow just works randomly. Every X container startup, the right
 bean
  will be used with EL.
 
  Thanks.
 
  Regards,
  Thomas
 

Re: Alternative + Named

[Thomas Andraschko]

Thanks but IMO this is quite complex for such a normal requirement.
Is there any chance to discuss this with the expert group?
Maybe we could implement in OWB after a successful discussion.


2013/10/29 Mark Struberg strub...@yahoo.de

 you could create a CDI Extension which does the
 ProcessAnnotatedType.veto().

 You could also try to use DeltaSpike globalAlternatives for it. This
 should do pretty much what you like and internally also works with veto().

 LieGrue,
 strub




 
  From: Thomas Andraschko andraschko.tho...@gmail.com
 To: dev@openwebbeans.apache.org; Mark Struberg strub...@yahoo.de
 Sent: Tuesday, 29 October 2013, 21:43
 Subject: Re: Alternative + Named
 
 
 
 Hi Mark,
 
 is there any change to get similar behavior?
 It's actually a must-have for product development.
 We would like to have multiple implementations in our core and just
 active them via alternative.
 With @Specialized or @Exclude, i can't do it without code changes :/
 
 
 
 
 
 
 2013/10/29 Mark Struberg strub...@yahoo.de
 
 Gee, I fear this is not really well specified.
 I'd rather not bet for it to work.
 Honestly I would have expected that an AmbiguousResolutionException gets
 thrown.
 
 I'd use @Exclude or @Specializes in this case.
 
 LieGrue,
 strub
 
 
 
 
 
 - Original Message -
  From: Thomas Andraschko andraschko.tho...@gmail.com
  To: dev@openwebbeans.apache.org
  Cc:
  Sent: Tuesday, 29 October 2013, 21:23
  Subject: Alternative + Named
 
  Hi,
 
  should it actually be possible to overwrite a bean with a alternative
 named
  bean?
 
  e.g -
 
  @Named public class A
 
  with a activated
 
  @Named(a) @Alternative public class A extends B
 
 
  This somehow just works randomly. Every X container startup, the right
 bean
  will be used with EL.
 
  Thanks.
 
  Regards,
  Thomas
 
 
 
 
 

1.2.1 - @Specialized Class : XXX may not explicitly declare a bean name

[Thomas Andraschko]

Hi,

i just upgraded to 1.2.1 and i get this exception.
My @Specialized class does not have a @Named annotation but somehow it's
there in the debugger.

Any idea?

I must still use 1.1.5 :/

Regards,
Thomas

Re: 1.2.1 - @Specialized Class : XXX may not explicitly declare a bean name

[Thomas Andraschko]

Guys, i really need your help!
It was introduced in one of the ~300 commits for #344
The most revisions event don't compile so i can't find the breaking commit!

How is it possible that my Bean does not have a @Named in the source code
but it's really there in the debugger?
Can ASM manipulate this without inheritance? I never looked deeper in that
byte code generation/manipulation stuff.



2013/11/26 Thomas Andraschko andraschko.tho...@gmail.com

 Hi,

 i just upgraded to 1.2.1 and i get this exception.
 My @Specialized class does not have a @Named annotation but somehow it's
 there in the debugger.

 Any idea?

 I must still use 1.1.5 :/

 Regards,
 Thomas

Re: 1.2.1 - @Specialized Class : XXX may not explicitly declare a bean name

[Thomas Andraschko]

Hi Gerhard,

i added a unit test.
It only occurs on multiple specialization - BeanA - @Specialized BeanB -
@Specialized BeanC.
Can i check in and create a issue for it?

It would be great if anyone of you could check it.

Regards,
Thomas



2013/11/28 Gerhard Petracek gerhard.petra...@gmail.com

 hi thomas,

 i did a quick-check and don't see the same effect.
 it would be great, if you provide a small demo which illustrates the issue.

 regards,
 gerhard



 2013/11/28 Thomas Andraschko andraschko.tho...@gmail.com

  Guys, i really need your help!
  It was introduced in one of the ~300 commits for #344
  The most revisions event don't compile so i can't find the breaking
 commit!
 
  How is it possible that my Bean does not have a @Named in the source code
  but it's really there in the debugger?
  Can ASM manipulate this without inheritance? I never looked deeper in
 that
  byte code generation/manipulation stuff.
 
 
 
  2013/11/26 Thomas Andraschko andraschko.tho...@gmail.com
 
   Hi,
  
   i just upgraded to 1.2.1 and i get this exception.
   My @Specialized class does not have a @Named annotation but somehow
 it's
   there in the debugger.
  
   Any idea?
  
   I must still use 1.1.5 :/
  
   Regards,
   Thomas
  
 

Re: 1.2.1 - @Specialized Class : XXX may not explicitly declare a bean name

[Thomas Andraschko]

Hey Mark,

i also posted it in the ticket:
webbeans-impl\src\test\java\org\apache\webbeans\newtests\specalization\multiple

I just commented @Test, to not break the build.

Regards,
Thomas


2013/11/28 Mark Struberg strub...@yahoo.de

 what is the name of the unit test? Or to which JIRA did you attach it?

 LieGrue,
 strub




 
  From: Thomas Andraschko andraschko.tho...@gmail.com
 To: dev@openwebbeans.apache.org
 Sent: Thursday, 28 November 2013, 13:04
 Subject: Re: 1.2.1 - @Specialized Class : XXX may not explicitly declare
 a bean name
 
 
 Hi Gerhard,
 
 i added a unit test.
 It only occurs on multiple specialization - BeanA - @Specialized BeanB
 -
 @Specialized BeanC.
 Can i check in and create a issue for it?
 
 It would be great if anyone of you could check it.
 
 Regards,
 Thomas
 
 
 
 
 2013/11/28 Gerhard Petracek gerhard.petra...@gmail.com
 
  hi thomas,
 
  i did a quick-check and don't see the same effect.
  it would be great, if you provide a small demo which illustrates the
 issue.
 
  regards,
  gerhard
 
 
 
  2013/11/28 Thomas Andraschko andraschko.tho...@gmail.com
 
   Guys, i really need your help!
   It was introduced in one of the ~300 commits for #344
   The most revisions event don't compile so i can't find the breaking
  commit!
  
   How is it possible that my Bean does not have a @Named in the source
 code
   but it's really there in the debugger?
   Can ASM manipulate this without inheritance? I never looked deeper in
  that
   byte code generation/manipulation stuff.
  
  
  
   2013/11/26 Thomas Andraschko andraschko.tho...@gmail.com
  
Hi,
   
i just upgraded to 1.2.1 and i get this exception.
My @Specialized class does not have a @Named annotation but somehow
  it's
there in the debugger.
   
Any idea?
   
I must still use 1.1.5 :/
   
Regards,
Thomas
   
  
 
 
 
 

Re: svn commit: r1552050 - in /openwebbeans/trunk/webbeans-impl/src: main/java/org/apache/webbeans/component/creation/BeanAttributesBuilder.java test/java/org/apache/webbeans/newtests/specalization/mu

[Thomas Andraschko]

Ahh i see!

To be honest, i'm not very experiences in this area too!

I tried it with this code:

AnnotatedType? super C annotatedToSpecialize =

webBeansContext.getAnnotatedElementFactory().newAnnotatedType(getAnnotated().getJavaClass().getSuperclass());

while
(annotatedToSpecialize.isAnnotationPresent(Specializes.class))
{
annotatedToSpecialize =
webBeansContext.getAnnotatedElementFactory().newAnnotatedType(annotatedToSpecialize.getJavaClass().getSuperclass());
}

defineName(annotatedToSpecialize,
WebBeansUtil.getManagedBeanDefaultName(annotatedToSpecialize.getJavaClass().getSimpleName()));

and its working fine too.
All unit tests passing.

Should i commit it?



2013/12/18 Joseph Bergmark bergm...@gmail.com

 Sorry, I'll try to be more clear.  Again, I'm not very experienced in this
 area of OWB, so my interpretation could be wrong or this could be handled
 in a different code path entirely.

 The new code is looking directly at the Class itself for the @Specializes
 annotation.  I'm suggesting that perhaps instead it should be looking at
 the AnnotatedType for the annotation (AnnotatedType.isAnnotatationPresent)
 in case a portable extension has called setAnnotatedType during a
 ProcessAnnotatedType event and has added @Specializes.


 On Wed, Dec 18, 2013 at 4:14 PM, Thomas Andraschko 
 andraschko.tho...@gmail.com wrote:

  Hey,
 
  i'm not exactly sure if understand your question correctly but i will
  explain you my code change.
 
  I think specialization per se was working fine but the old code just
 looked
  for a @Named on the direct parent.
 
  e.g.
 
  @Named BeanA
  @Specializes BeanB extends BeanA
  @Specializes BeanC extends BeanC
 
  It tried to extract the name for BeanC from BeanB but actually it must
 look
  for @Named on BeanA.
 
 
  2013/12/18 Joseph Bergmark bergm...@gmail.com
 
   I'll be the first to admit I'm not very familiar with this code area,
 but
   is it possible that this change could mean that we miss @Specializes
  added
   to the AnnotatedType classes in the super class hierarchy, as you are
   walking up the class objects themselves looking for the annotation?
  
 

Re: [DISCUSS] retire cditest module?

[Thomas Andraschko]

+1


2014-01-26 Romain Manni-Bucau rmannibu...@gmail.com

 +1
 Romain Manni-Bucau
 Twitter: @rmannibucau
 Blog: http://rmannibucau.wordpress.com/
 LinkedIn: http://fr.linkedin.com/in/rmannibucau
 Github: https://github.com/rmannibucau



 2014-01-26 Mark Struberg strub...@yahoo.de:
  Hi!
 
  The CdiTest module is now pretty much obsolete. Users can almost 1:1
 switch to the much superior DeltaSpike CdiCtrl or use Arquillian for their
 tests.
 
  wdyt? Should we ditch it?
 
 
  LieGrue,
  strub

Re: [DISCUSS] drop servlet-2.5 support?

[Thomas Andraschko]

For 2.0/CDI 1.1?
+1 then


2014-01-27 Romain Manni-Bucau rmannibu...@gmail.com

 +1, t8 is almost release so no more need of t6 integration IMO
 Romain Manni-Bucau
 Twitter: @rmannibucau
 Blog: http://rmannibucau.wordpress.com/
 LinkedIn: http://fr.linkedin.com/in/rmannibucau
 Github: https://github.com/rmannibucau



 2014-01-27 Mark Struberg strub...@yahoo.de:
  hi!
 
  Does anyone still like to use a new owb version with servlet-2.5?
  I'd rather ditch that to be finally able to properly support
 asynchronous web requests.
 
  Means we cculd also kill the tomcat6 module, right?
 
  LieGrue,
  strub

Re: time to release owb-1.2.3?

[Thomas Andraschko]

+1


2014-04-21 13:05 GMT+02:00 Gerhard Petracek gerhard.petra...@gmail.com:

 +1

 regards,
 gerhard



 2014-04-21 11:18 GMT+02:00 Jean-Louis MONTEIRO jeano...@gmail.com:

  Awesome.
  +1 of course
 
 
 
  2014-04-21 11:14 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com:
 
   +1 works fine on openejb for 2 weeks at least
  
  
   Romain Manni-Bucau
   Twitter: @rmannibucau
   Blog: http://rmannibucau.wordpress.com/
   LinkedIn: http://fr.linkedin.com/in/rmannibucau
   Github: https://github.com/rmannibucau
  
  
   2014-04-21 10:34 GMT+02:00 Mark Struberg strub...@yahoo.de:
Hi!
   
Romain has added java8 support.
I think we should ship 1.2.3 asap.
Could run the release tasks today if there is no -1.
   
LieGrue,
strub
  
 
 
 
  --
  Jean-Louis
 

Re: rename owb-2.0 to owb-1.5?

[Thomas Andraschko]

+1 for 2.0 for CDI 2.0

don't know about 1.5...


2014-08-30 16:16 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com:

 tomcat does +1 on all major for each spec release (2.5 - 6, 3.0 - 7,
 3.1 - 8...)

 I don't like 1.5 cause it doesn't make any sense but I don't care
 enough about version to fight for it.

 Seems it passed Mark ;)


 Romain Manni-Bucau
 Twitter: @rmannibucau
 Blog: http://rmannibucau.wordpress.com/
 LinkedIn: http://fr.linkedin.com/in/rmannibucau
 Github: https://github.com/rmannibucau


 2014-08-30 14:20 GMT+02:00 Eric Covener cove...@gmail.com:
  On Sat, Aug 30, 2014 at 3:01 AM, Mark Struberg strub...@yahoo.de
 wrote:
  What about renaming our current trunk to 1.5.0-SNAPSHOT?
 
  +1, awfully confusing w/o it.
 
  --
  Eric Covener
  cove...@gmail.com

Re: You shall not pass!

[Thomas Andraschko]

Have some problems...
Already created a issue about WEB-INF/beans.xml lookup with a possible fix
- please have look at it.

I also have a javax.enterprise.inject.UnsatisfiedResolutionException for a
bean without a deviration.
I will try to find the reason later.


2014-10-02 10:37 GMT+02:00 Thomas Andraschko andraschko.tho...@gmail.com:

 Great guys, thanks!
 Will test my apps today!

 2014-10-02 10:28 GMT+02:00 Arne Limburg arne.limb...@openknowledge.de:

 Yes,
 I¹ll use that time to work out these ugly generics issues with the cdi-tck
 team, so we can get rid of these ugly hacks in GenericsUtil, that the tck
 made us implement.

 Cheers,
 Arne


 Am 01.10.14 20:33 schrieb Jens Schumann unter
 jens.schum...@openknowledge.de:

 Congratulation!
 
 .oO(I always assumed, that we have to wait till the end of Arne's
 upcoming parental leave;)
 
  On 01 Oct 2014, at 20:23, Mark Struberg strub...@yahoo.de wrote:
 
  But we do!
 
  Folks, I'm proud to announce that we finally pass the standalone part
 of the CDI-1.2 TCK!
 
  Please, all do checkout our latest OWB 1.5.0-SNAPSHOT (or simply
 compile it yourself [1]) and test YOUR application with it. Any feedback
 is welcome!
 
  I like to kick off the release train for OWB tomorrow.
 
  We will now continue with cleanup and performance improvements. And
 also with working on the EE TCK over in TomEE.
 
 
  txs and LieGrue,
  strub
 

Re: You shall not pass!

[Thomas Andraschko]

Fixed! :)

But i really have a weird problem, i get the follwowing exception on every
startup with another bean:

javax.enterprise.inject.spi.DeploymentException:
org.apache.webbeans.exception.WebBeansConfigurationException: Error while
sending SystemEvent to a CDI Extension!
org.apache.webbeans.portable.events.generics.GProcessAnnotatedType@46573acf
at
org.apache.webbeans.config.BeansDeployer.deploy(BeansDeployer.java:284)
at
org.apache.webbeans.lifecycle.AbstractLifeCycle.bootstrapApplication(AbstractLifeCycle.java:138)
at
org.apache.webbeans.lifecycle.AbstractLifeCycle.startApplication(AbstractLifeCycle.java:104)
at
org.apache.webbeans.web.lifecycle.WebContainerLifecycle.startApplication(WebContainerLifecycle.java:89)
at
org.apache.webbeans.servlet.WebBeansConfigurationListener.contextInitialized(WebBeansConfigurationListener.java:86)
at
org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
... Caused by:
javax.enterprise.inject.UnsatisfiedResolutionException: Api type
[de.test.Anybean] is not found with the qualifiers |Qualifiers:
[@javax.enterprise.inject.Default()]|for injection into Field Injection
Point, field name :  selectItemNone, Bean Owner : [null]
at
org.apache.webbeans.util.InjectionExceptionUtil.throwUnsatisfiedResolutionException(InjectionExceptionUtil.java:65)
at
org.apache.webbeans.container.InjectionResolver.checkInjectionPoint(InjectionResolver.java:221)
at
org.apache.webbeans.container.BeanManagerImpl.validate(BeanManagerImpl.java:1149)
at
org.apache.webbeans.util.WebBeansUtil.validate(WebBeansUtil.java:1683)
at
org.apache.webbeans.container.BeanManagerImpl.createInjectionTarget(BeanManagerImpl.java:1169)
at
org.apache.webbeans.container.InjectableBeanManager.createInjectionTarget(InjectableBeanManager.java:101)
at
org.apache.deltaspike.core.util.bean.BeanBuilder.readFromType(BeanBuilder.java:116)
at
org.apache.deltaspike.jsf.impl.injection.proxy.ConverterAndValidatorProxyExtension.findConverterAndValidatorsWhichNeedProxiesForDependencyInjectionSupport(ConverterAndValidatorProxyExtension.java:73)
at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.apache.webbeans.event.ObserverMethodImpl.invoke(ObserverMethodImpl.java:343)
at
org.apache.webbeans.event.ContainerEventObserverMethodImpl.invoke(ContainerEventObserverMethodImpl.java:82)
at
org.apache.webbeans.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:308)
at
org.apache.webbeans.event.NotificationManager.fireEvent(NotificationManager.java:599)
at
org.apache.webbeans.container.BeanManagerImpl.fireEvent(BeanManagerImpl.java:453)
at
org.apache.webbeans.container.BeanManagerImpl.fireEvent(BeanManagerImpl.java:438)
at
org.apache.webbeans.util.WebBeansUtil.fireProcessAnnotatedTypeEvent(WebBeansUtil.java:1008)
at
org.apache.webbeans.config.BeansDeployer.annotatedTypesFromClassPath(BeansDeployer.java:844)
at
org.apache.webbeans.config.BeansDeployer.deploy(BeansDeployer.java:228)
at
org.apache.webbeans.lifecycle.AbstractLifeCycle.bootstrapApplication(AbstractLifeCycle.java:138)
at
org.apache.webbeans.lifecycle.AbstractLifeCycle.startApplication(AbstractLifeCycle.java:104)
at
org.apache.webbeans.web.lifecycle.WebContainerLifecycle.startApplication(WebContainerLifecycle.java:89)
at
org.apache.webbeans.servlet.WebBeansConfigurationListener.contextInitialized(WebBeansConfigurationListener.java:86)

Works fine with Weld and OWB 1.1.x and OWB 1.2.x.



2014-10-02 12:46 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com:

 @Thomas: +1 WEB-INF/beans.xml is not a valid resource even in tomcat
 and by spec (servlet)

 Also ensure to be very up to date since we added few fixes since the
 announcement


 Romain Manni-Bucau
 Twitter: @rmannibucau
 Blog: http://rmannibucau.wordpress.com/
 LinkedIn: http://fr.linkedin.com/in/rmannibucau
 Github: https://github.com/rmannibucau


 2014-10-02 11:58 GMT+02:00 Thomas Andraschko andraschko.tho...@gmail.com
 :
  Have some problems...
  Already created a issue about WEB-INF/beans.xml lookup with a possible
 fix
  - please have look at it.
 
  I also have a javax.enterprise.inject.UnsatisfiedResolutionException for
 a
  bean without a deviration.
  I will try to find the reason later.
 
 
  2014-10-02 10:37 GMT+02:00 Thomas Andraschko 
 andraschko.tho...@gmail.com:
 
  Great guys, thanks!
  Will test my apps today!
 
  2014-10-02 10:28 GMT+02:00 Arne Limburg arne.limb...@openknowledge.de
 :
 
  Yes,
  I¹ll use that time to work out these ugly generics issues with the
 cdi-tck
  team, so we can get rid of these ugly hacks in GenericsUtil, that the
 tck
  made us implement.
 
  Cheers,
  Arne
 
 
  Am 01.10.14 20:33 schrieb Jens Schumann unter
  jens.schum...@openknowledge.de

Re: You shall not pass!

[Thomas Andraschko]

It worked fine and now, if i start my app, each time another injectionpoint
is invalid.
Therefore i don't think it's usefull to share a single bean.
The most times it's a simple injection - without alternatives/specializes
etc. So nothing special here.

Could it be possible that it's to early and not ALL beans are loaded at
this time?
I have a around 10 jars with beans, maybe it depdends on the order of the
jar loading?

2014-10-02 13:59 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com:

 We validate injection point more drastically now, surely the cause. Can you
 share AnyBean and where it is injected?

 Le jeudi 2 octobre 2014, Thomas Andraschko andraschko.tho...@gmail.com a
 écrit :
  Fixed! :)
 
  But i really have a weird problem, i get the follwowing exception on
 every
  startup with another bean:
 
  javax.enterprise.inject.spi.DeploymentException:
  org.apache.webbeans.exception.WebBeansConfigurationException: Error while
  sending SystemEvent to a CDI Extension!
 
 org.apache.webbeans.portable.events.generics.GProcessAnnotatedType@46573acf
  at
  org.apache.webbeans.config.BeansDeployer.deploy(BeansDeployer.java:284)
  at
 

 org.apache.webbeans.lifecycle.AbstractLifeCycle.bootstrapApplication(AbstractLifeCycle.java:138)
  at
 

 org.apache.webbeans.lifecycle.AbstractLifeCycle.startApplication(AbstractLifeCycle.java:104)
  at
 

 org.apache.webbeans.web.lifecycle.WebContainerLifecycle.startApplication(WebContainerLifecycle.java:89)
  at
 

 org.apache.webbeans.servlet.WebBeansConfigurationListener.contextInitialized(WebBeansConfigurationListener.java:86)
  at
 

 org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
  ... Caused by:
  javax.enterprise.inject.UnsatisfiedResolutionException: Api type
  [de.test.Anybean] is not found with the qualifiers |Qualifiers:
  [@javax.enterprise.inject.Default()]|for injection into Field Injection
  Point, field name :  selectItemNone, Bean Owner : [null]
  at
 

 org.apache.webbeans.util.InjectionExceptionUtil.throwUnsatisfiedResolutionException(InjectionExceptionUtil.java:65)
  at
 

 org.apache.webbeans.container.InjectionResolver.checkInjectionPoint(InjectionResolver.java:221)
  at
 

 org.apache.webbeans.container.BeanManagerImpl.validate(BeanManagerImpl.java:1149)
  at
  org.apache.webbeans.util.WebBeansUtil.validate(WebBeansUtil.java:1683)
  at
 

 org.apache.webbeans.container.BeanManagerImpl.createInjectionTarget(BeanManagerImpl.java:1169)
  at
 

 org.apache.webbeans.container.InjectableBeanManager.createInjectionTarget(InjectableBeanManager.java:101)
  at
 

 org.apache.deltaspike.core.util.bean.BeanBuilder.readFromType(BeanBuilder.java:116)
  at
 

 org.apache.deltaspike.jsf.impl.injection.proxy.ConverterAndValidatorProxyExtension.findConverterAndValidatorsWhichNeedProxiesForDependencyInjectionSupport(ConverterAndValidatorProxyExtension.java:73)
  at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
  at
 

 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(Method.java:606)
  at
 

 org.apache.webbeans.event.ObserverMethodImpl.invoke(ObserverMethodImpl.java:343)
  at
 

 org.apache.webbeans.event.ContainerEventObserverMethodImpl.invoke(ContainerEventObserverMethodImpl.java:82)
  at
 

 org.apache.webbeans.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:308)
  at
 

 org.apache.webbeans.event.NotificationManager.fireEvent(NotificationManager.java:599)
  at
 

 org.apache.webbeans.container.BeanManagerImpl.fireEvent(BeanManagerImpl.java:453)
  at
 

 org.apache.webbeans.container.BeanManagerImpl.fireEvent(BeanManagerImpl.java:438)
  at
 

 org.apache.webbeans.util.WebBeansUtil.fireProcessAnnotatedTypeEvent(WebBeansUtil.java:1008)
  at
 

 org.apache.webbeans.config.BeansDeployer.annotatedTypesFromClassPath(BeansDeployer.java:844)
  at
  org.apache.webbeans.config.BeansDeployer.deploy(BeansDeployer.java:228)
  at
 

 org.apache.webbeans.lifecycle.AbstractLifeCycle.bootstrapApplication(AbstractLifeCycle.java:138)
  at
 

 org.apache.webbeans.lifecycle.AbstractLifeCycle.startApplication(AbstractLifeCycle.java:104)
  at
 

 org.apache.webbeans.web.lifecycle.WebContainerLifecycle.startApplication(WebContainerLifecycle.java:89)
  at
 

 org.apache.webbeans.servlet.WebBeansConfigurationListener.contextInitialized(WebBeansConfigurationListener.java:86)
 
  Works fine with Weld and OWB 1.1.x and OWB 1.2.x.
 
 
 
  2014-10-02 12:46 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com:
 
  @Thomas: +1 WEB-INF/beans.xml is not a valid resource even in tomcat
  and by spec (servlet)
 
  Also ensure to be very up to date since we added few fixes since the
  announcement
 
 
  Romain Manni-Bucau
  Twitter: @rmannibucau
  Blog: http://rmannibucau.wordpress.com/
  LinkedIn: http://fr.linkedin.com/in/rmannibucau

Re: You shall not pass!

[Thomas Andraschko]

Created a small sample here: https://issues.apache.org/jira/browse/OWB-1022
AFAICS the injectoin points are validated to early.

2014-10-02 14:17 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com:

 it is done when we validate injection points so everything should be there


 Romain Manni-Bucau
 Twitter: @rmannibucau
 Blog: http://rmannibucau.wordpress.com/
 LinkedIn: http://fr.linkedin.com/in/rmannibucau
 Github: https://github.com/rmannibucau


 2014-10-02 14:14 GMT+02:00 Thomas Andraschko andraschko.tho...@gmail.com
 :
  It worked fine and now, if i start my app, each time another
 injectionpoint
  is invalid.
  Therefore i don't think it's usefull to share a single bean.
  The most times it's a simple injection - without alternatives/specializes
  etc. So nothing special here.
 
  Could it be possible that it's to early and not ALL beans are loaded at
  this time?
  I have a around 10 jars with beans, maybe it depdends on the order of the
  jar loading?
 
  2014-10-02 13:59 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com:
 
  We validate injection point more drastically now, surely the cause. Can
 you
  share AnyBean and where it is injected?
 
  Le jeudi 2 octobre 2014, Thomas Andraschko andraschko.tho...@gmail.com
 a
  écrit :
   Fixed! :)
  
   But i really have a weird problem, i get the follwowing exception on
  every
   startup with another bean:
  
   javax.enterprise.inject.spi.DeploymentException:
   org.apache.webbeans.exception.WebBeansConfigurationException: Error
 while
   sending SystemEvent to a CDI Extension!
  
 
 org.apache.webbeans.portable.events.generics.GProcessAnnotatedType@46573acf
   at
  
 org.apache.webbeans.config.BeansDeployer.deploy(BeansDeployer.java:284)
   at
  
 
 
 org.apache.webbeans.lifecycle.AbstractLifeCycle.bootstrapApplication(AbstractLifeCycle.java:138)
   at
  
 
 
 org.apache.webbeans.lifecycle.AbstractLifeCycle.startApplication(AbstractLifeCycle.java:104)
   at
  
 
 
 org.apache.webbeans.web.lifecycle.WebContainerLifecycle.startApplication(WebContainerLifecycle.java:89)
   at
  
 
 
 org.apache.webbeans.servlet.WebBeansConfigurationListener.contextInitialized(WebBeansConfigurationListener.java:86)
   at
  
 
 
 org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
   ... Caused by:
   javax.enterprise.inject.UnsatisfiedResolutionException: Api type
   [de.test.Anybean] is not found with the qualifiers |Qualifiers:
   [@javax.enterprise.inject.Default()]|for injection into Field
 Injection
   Point, field name :  selectItemNone, Bean Owner : [null]
   at
  
 
 
 org.apache.webbeans.util.InjectionExceptionUtil.throwUnsatisfiedResolutionException(InjectionExceptionUtil.java:65)
   at
  
 
 
 org.apache.webbeans.container.InjectionResolver.checkInjectionPoint(InjectionResolver.java:221)
   at
  
 
 
 org.apache.webbeans.container.BeanManagerImpl.validate(BeanManagerImpl.java:1149)
   at
   org.apache.webbeans.util.WebBeansUtil.validate(WebBeansUtil.java:1683)
   at
  
 
 
 org.apache.webbeans.container.BeanManagerImpl.createInjectionTarget(BeanManagerImpl.java:1169)
   at
  
 
 
 org.apache.webbeans.container.InjectableBeanManager.createInjectionTarget(InjectableBeanManager.java:101)
   at
  
 
 
 org.apache.deltaspike.core.util.bean.BeanBuilder.readFromType(BeanBuilder.java:116)
   at
  
 
 
 org.apache.deltaspike.jsf.impl.injection.proxy.ConverterAndValidatorProxyExtension.findConverterAndValidatorsWhichNeedProxiesForDependencyInjectionSupport(ConverterAndValidatorProxyExtension.java:73)
   at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
   at
  
 
 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:606)
   at
  
 
 
 org.apache.webbeans.event.ObserverMethodImpl.invoke(ObserverMethodImpl.java:343)
   at
  
 
 
 org.apache.webbeans.event.ContainerEventObserverMethodImpl.invoke(ContainerEventObserverMethodImpl.java:82)
   at
  
 
 
 org.apache.webbeans.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:308)
   at
  
 
 
 org.apache.webbeans.event.NotificationManager.fireEvent(NotificationManager.java:599)
   at
  
 
 
 org.apache.webbeans.container.BeanManagerImpl.fireEvent(BeanManagerImpl.java:453)
   at
  
 
 
 org.apache.webbeans.container.BeanManagerImpl.fireEvent(BeanManagerImpl.java:438)
   at
  
 
 
 org.apache.webbeans.util.WebBeansUtil.fireProcessAnnotatedTypeEvent(WebBeansUtil.java:1008)
   at
  
 
 
 org.apache.webbeans.config.BeansDeployer.annotatedTypesFromClassPath(BeansDeployer.java:844)
   at
  
 org.apache.webbeans.config.BeansDeployer.deploy(BeansDeployer.java:228)
   at
  
 
 
 org.apache.webbeans.lifecycle.AbstractLifeCycle.bootstrapApplication(AbstractLifeCycle.java:138)
   at
  
 
 
 org.apache.webbeans.lifecycle.AbstractLifeCycle.startApplication(AbstractLifeCycle.java:104

Re: You shall not pass!

[Thomas Andraschko]

great! my apps are working fine now!

2014-10-06 9:57 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com:

 should be ok now, issue was cache + maven classpath (jetty)


 Romain Manni-Bucau
 Twitter: @rmannibucau
 Blog: http://rmannibucau.wordpress.com/
 LinkedIn: http://fr.linkedin.com/in/rmannibucau
 Github: https://github.com/rmannibucau


 2014-10-05 21:01 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com:
  surely when we resolve the injection (normally in validate(beans) but
  same method is called by bm.validation(injectionPoint)
 
 
 
 
  Romain Manni-Bucau
  Twitter: @rmannibucau
  Blog: http://rmannibucau.wordpress.com/
  LinkedIn: http://fr.linkedin.com/in/rmannibucau
  Github: https://github.com/rmannibucau
 
 
  2014-10-05 20:39 GMT+02:00 Thomas Andraschko 
 andraschko.tho...@gmail.com:
  Created a small sample here:
 https://issues.apache.org/jira/browse/OWB-1022
  AFAICS the injectoin points are validated to early.
 
  2014-10-02 14:17 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com:
 
  it is done when we validate injection points so everything should be
 there
 
 
  Romain Manni-Bucau
  Twitter: @rmannibucau
  Blog: http://rmannibucau.wordpress.com/
  LinkedIn: http://fr.linkedin.com/in/rmannibucau
  Github: https://github.com/rmannibucau
 
 
  2014-10-02 14:14 GMT+02:00 Thomas Andraschko 
 andraschko.tho...@gmail.com
  :
   It worked fine and now, if i start my app, each time another
  injectionpoint
   is invalid.
   Therefore i don't think it's usefull to share a single bean.
   The most times it's a simple injection - without
 alternatives/specializes
   etc. So nothing special here.
  
   Could it be possible that it's to early and not ALL beans are loaded
 at
   this time?
   I have a around 10 jars with beans, maybe it depdends on the order
 of the
   jar loading?
  
   2014-10-02 13:59 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com
 :
  
   We validate injection point more drastically now, surely the cause.
 Can
  you
   share AnyBean and where it is injected?
  
   Le jeudi 2 octobre 2014, Thomas Andraschko 
 andraschko.tho...@gmail.com
  a
   écrit :
Fixed! :)
   
But i really have a weird problem, i get the follwowing exception
 on
   every
startup with another bean:
   
javax.enterprise.inject.spi.DeploymentException:
org.apache.webbeans.exception.WebBeansConfigurationException:
 Error
  while
sending SystemEvent to a CDI Extension!
   
  
 
 org.apache.webbeans.portable.events.generics.GProcessAnnotatedType@46573acf
at
   
  org.apache.webbeans.config.BeansDeployer.deploy(BeansDeployer.java:284)
at
   
  
  
 
 org.apache.webbeans.lifecycle.AbstractLifeCycle.bootstrapApplication(AbstractLifeCycle.java:138)
at
   
  
  
 
 org.apache.webbeans.lifecycle.AbstractLifeCycle.startApplication(AbstractLifeCycle.java:104)
at
   
  
  
 
 org.apache.webbeans.web.lifecycle.WebContainerLifecycle.startApplication(WebContainerLifecycle.java:89)
at
   
  
  
 
 org.apache.webbeans.servlet.WebBeansConfigurationListener.contextInitialized(WebBeansConfigurationListener.java:86)
at
   
  
  
 
 org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
... Caused by:
javax.enterprise.inject.UnsatisfiedResolutionException: Api type
[de.test.Anybean] is not found with the qualifiers |Qualifiers:
[@javax.enterprise.inject.Default()]|for injection into Field
  Injection
Point, field name :  selectItemNone, Bean Owner : [null]
at
   
  
  
 
 org.apache.webbeans.util.InjectionExceptionUtil.throwUnsatisfiedResolutionException(InjectionExceptionUtil.java:65)
at
   
  
  
 
 org.apache.webbeans.container.InjectionResolver.checkInjectionPoint(InjectionResolver.java:221)
at
   
  
  
 
 org.apache.webbeans.container.BeanManagerImpl.validate(BeanManagerImpl.java:1149)
at
   
 org.apache.webbeans.util.WebBeansUtil.validate(WebBeansUtil.java:1683)
at
   
  
  
 
 org.apache.webbeans.container.BeanManagerImpl.createInjectionTarget(BeanManagerImpl.java:1169)
at
   
  
  
 
 org.apache.webbeans.container.InjectableBeanManager.createInjectionTarget(InjectableBeanManager.java:101)
at
   
  
  
 
 org.apache.deltaspike.core.util.bean.BeanBuilder.readFromType(BeanBuilder.java:116)
at
   
  
  
 
 org.apache.deltaspike.jsf.impl.injection.proxy.ConverterAndValidatorProxyExtension.findConverterAndValidatorsWhichNeedProxiesForDependencyInjectionSupport(ConverterAndValidatorProxyExtension.java:73)
at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown
 Source)
at
   
  
  
 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
   
  
  
 
 org.apache.webbeans.event.ObserverMethodImpl.invoke(ObserverMethodImpl.java:343

Re: do we like to drop servlet-2.5 support?

[Thomas Andraschko]

+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 rmannibu...@gmail.com:

 Le 26 avr. 2015 17:51, Joseph Bergmark bergm...@apache.org 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 strub...@yahoo.de 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: a new OWB-1.2.x release?

[Thomas Andraschko]

+1

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

 Hi folks!

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

 LieGrue,
 strub

Re: upgrade to java7?

[Thomas Andraschko]

+0

2015-04-09 19:28 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com:

 +0
 Le 9 avr. 2015 19:22, Mark Struberg strub...@yahoo.de 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: interceptors and interfaces

[Thomas Andraschko]

+0 but why not? is it a big deal?

2015-06-08 0:39 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com:

 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: WebContextsService errors when servlet session invalidated during request lifecycle

[Thomas Andraschko]

+1
please create a issue

2015-06-11 1:13 GMT+02:00 Adam Cornett adam.corn...@gmail.com:

 If the session is invalidated during the processing of the request an
 exception is thrown when OpenWebBeans is cleaning up.

 The issue is in the WebContextsService.destroyRequestContext method, which
 tries to get the session from the request, however it calls the no-arg
 getSession()
 
 http://tomcat.apache.org/tomcat-7.0-doc/servletapi/javax/servlet/http/HttpServletRequest.html#getSession()
 ,
 which will, per the spec, try to create a new session if one does not
 exist.  However since the response has been committed this is not allowed
 to create a new session and an exception is thrown.
 The solution is to call getSession(false)
 
 http://tomcat.apache.org/tomcat-7.0-doc/servletapi/javax/servlet/http/HttpServletRequest.html#getSession(boolean)
 ,
 which will return null if the session does not exist.  This seems to be the
 desired behavior anyway since the result of the call is null checked a few
 lines later.

 I have tested this change in our application and it produces the desired
 behavior.

 Current code:


 Object payload = null;
 if (context.getServletRequest() != null)
 {
 payload = context.getServletRequest().getSession();
 }

 webBeansContext.getBeanManagerImpl().fireContextLifecyleEvent(
 payload != null ? payload : new Object(),
 DestroyedLiteral.INSTANCE_SESSION_SCOPED);

 Suggested fix:


 Object payload = null;
 if (context.getServletRequest() != null)
 {
 payload = context.getServletRequest().getSession(false);
 }

 webBeansContext.getBeanManagerImpl().fireContextLifecyleEvent(
 payload != null ? payload : new Object(),
 DestroyedLiteral.INSTANCE_SESSION_SCOPED);

 --
 Adam Cornett
 adam.corn...@gmail.com
 (678) 296-1150

Re: [VOTE] for Apache OpenWebBeans 1.6.1

[Thomas Andraschko]

+1 tested my application and everything is working fine

2015-06-16 9:10 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com:

 +1


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

 2015-06-16 8:10 GMT+02:00 Mark Struberg strub...@yahoo.de:

  Hi!
 
  I’d like to call a VOTE on Apache OpenWebBeans-1.6.1.
 
  The staging repository is here
 
 
 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1014/
 
  The source repo is available here
 
 
 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1014/org/apache/openwebbeans/openwebbeans/1.6.1/openwebbeans-1.6.1-source-release.zip
 
 
  The binary distribution can be found at
 
 
 https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1014/org/apache/openwebbeans/openwebbeans-distribution/1.6.1/openwebbeans-distribution-1.6.1-binary.zip
 
  [+1] ship it
  [+0] meh, don’t care
  [-1] stop, because of ${blocker}
 
  The VOTE is open for 72h
 
  txs and LieGrue,
  strub
 
 

Re: Unify project names in poms

[Thomas Andraschko]

Not sure Mark.
If you have much projects openend in your IDE, it's really annoying if they
are not sorted because of a missing prefix...

+1 Romain

2015-10-27 9:33 GMT+01:00 Romain Manni-Bucau <rmannibu...@gmail.com>:

> 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" <strub...@yahoo.de> 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 <
> rmannibu...@gmail.com
> > >:
> > >
> > > 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" <
> andraschko.tho...@gmail.com>
> > 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 <rmannibu...@gmail.com
> >:
> > >>
> > >>> 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 <
> rmannibu...@gmail.com
> > >:
> > >>>>
> > >>>>> 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

[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 <rmannibu...@gmail.com>:

> 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

[Thomas Andraschko]

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 <rmannibu...@gmail.com>:

> 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 <rmannibu...@gmail.com>:
> >
> > > 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

[Thomas Andraschko]

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

Unify project names in poms

[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: Bean scanning exclude list

[Thomas Andraschko]

Hi Romain,

ahhh i see, thats great.
Ok, i will add property and merge the list of tomee/owb/mine.

Regards,
Thomas


2015-09-23 16:09 GMT+02:00 Romain Manni-Bucau <rmannibu...@gmail.com>:

> 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" <andraschko.tho...@gmail.com>
> 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
> >
>

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/

[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  |  Blog
>  | Github <
> https://github.com/rmannibucau> |
> LinkedIn  | Tomitriber
> 
>
> -- 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=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=1704888=1704889=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";
> +
>  

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/

[Thomas Andraschko]

What about scanExclusionPaths?
Otherwise lets go with jarExcludes :)

2015-09-23 19:22 GMT+02:00 Romain Manni-Bucau <rmannibu...@gmail.com>:

> 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 <rmannibu...@gmail.com>:
> >
> > > 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: <tandrasc...@apache.org>
> > > 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=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=1704888=1704889=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 OpenWebBeansConfigurat

Re: [DISCUSS] board report OWB-2015-12

[Thomas Andraschko]

+1

2015-12-11 10:40 GMT+01:00 Romain Manni-Bucau <rmannibu...@gmail.com>:

> 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 <strub...@yahoo.de>:
>
> > 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
>

Re: Object#method and proxies

[Thomas Andraschko]

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  |  Blog
>  | Github <
> https://github.com/rmannibucau> |
> LinkedIn  | Tomitriber
> 
>

Re: release OWB next week?

[Thomas Andraschko]

+1

2016-02-13 12:56 GMT+01:00 Romain Manni-Bucau :

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

Re: moving to owb-1.7.0-SNAPSHOT?

[Thomas Andraschko]

+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: moving to owb-1.7.0-SNAPSHOT?

[Thomas Andraschko]

+1 for 1.7
but as romain said, i'm also very sure this is rarely used by users.

2016-01-31 16:26 GMT+01:00 Mark Struberg <strub...@yahoo.de>:

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

Re: [DISCUSS] moving OpenWebBeans to GIT?

[Thomas Andraschko]

+0 - don't see any big benefit

Am Samstag, 23. Januar 2016 schrieb Romain Manni-Bucau :

> -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: do an OWB release?

[Thomas Andraschko]

+1

2016-07-27 11:37 GMT+02:00 Romain Manni-Bucau :

> +1 to go
>
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Wordpress Blog
>  | Github <
> https://github.com/rmannibucau> |
> LinkedIn  | Tomitriber
>  | JavaEE Factory
> 
>
> 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: CDI 2.0 Spec JAR

[Thomas Andraschko]

cool guys!

+1 daniel, the patch looks good

2016-07-11 21:51 GMT+02:00 Daniel Cunha :

> Cool!
>
> I have a patch to update maven-bundle-plugin and maven-checkstyle-plugin.
> I had work on some changes on branch cdi-2.0 and I get some problems with
> java8.
>
> It's necessary update this plugins to have build working fine, so I'll be
> possible to use java8 features on the code. :)
>
> Let me see what do you think about it:
> https://issues.apache.org/jira/browse/OWB-1134
>
> On Mon, Jul 11, 2016 at 11:50 AM, Mark Struberg  >
> wrote:
>
> > txs will apply.
> >
> > LieGrue,
> > strub
> >
> >
> >
> >
> >
> > > On Monday, 11 July 2016, 2:43, John D. Ament 
> > wrote:
> > > > I've raised a JIRA with the API changes that I noticed.  There might
> > be a
> > > few more pending.  I tested it against Weld, apparently they're behind
> a
> > > little bit as well.
> > >
> > > https://issues.apache.org/jira/browse/GERONIMO-6553
> > >
> > > - John
> > >
> > >
> > > On Wed, Jul 6, 2016 at 2:46 PM Mark Struberg  >
> > > wrote:
> > >
> > >>  >  Only constraint we
> > >>  > have is to not copy official comments/spec AFAIK.
> > >>
> > >>  Except we wrote that stuff ourselves for the spec. In that case the
> > >>  original author is of course free to also contribute it to the ASF
> > under
> > >>  ALv2.
> > >>
> > >>  LieGrue,
> > >>  strub
> > >>
> > >>
> > >>
> > >>  > Am 03.07.2016 um 23:01 schrieb Romain Manni-Bucau
> > >  > >>  >:
> > >>  >
> > >>  > 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 <
> > >>  rmannibu...@gmail.com>
> > >>  >> wrote:
> > >>  >>
> > >>  >>> Hi John,
> > >>  >>>
> > >>  >>> -> geronimo@ ;)
> > >>  >>>
> > >>  >>> Otherwise +1 for jenkins and to replace current 2.0 by an up
> > > to date
> > >>  >>> version
> > >>  >>>
> > >>  >>>
> > >>  >>> Romain Manni-Bucau
> > >>  >>> @rmannibucau  |  Blog
> > >>  >>>  | Old Wordpress
> > > Blog
> > >>  >>>  | Github <
> > >>  >>> https://github.com/rmannibucau> |
> > >>  >>> LinkedIn  |
> > > Tomitriber
> > >>  >>>  | JavaEE Factory
> > >>  >>> 
> > >>  >>>
> > >>  >>> 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
> > >>  
> > >>  >>>
> > >>
> > >>
> > >
> >
>
>
>
> --
> Daniel Cunha
> https://twitter.com/dvlc_
> http://www.tomitribe.com
> http://www.tomitribe.io
>

Re: [VOTE] Release Apache OpenWebBeans-1.7.2

[Thomas Andraschko]

+1

2017-02-19 16:27 GMT+01:00 Romain Manni-Bucau :

> up? we still miss 1 binding vote
>
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github  rmannibucau> |
> LinkedIn  | JavaEE Factory
> 
>
> 2017-02-06 16:31 GMT+01:00 Mark Struberg :
>
> > +1
> >
> >
> > * sig fine
> > * builds fine
> > * rat passes
> > * NOTICE and LICENSE ok
> > * all tests and TCK green
> >
> > let's ship it!
> >
> > txs Romain!
> >
> > LieGrue,
> > strub
> >
> >
> >
> >
> >
> > On Thursday, 2 February 2017, 11:03, Reinhard Sandtner <
> > reinhard.sandt...@gmail.com> wrote:
> > +1 (non-binding), all fine
> >
> > thanks romain!
> >
> > checked the following:
> > - source builds fine
> > - LICENSE
> > - NOTICE
> > - sha1
> > - md5
> > - signature
> >
> > build meecrowave with the new version
> > tested with my apps
> >
> > lg
> > reini
> >
> >
> >
> > > Am 31.01.2017 um 19:31 schrieb Romain Manni-Bucau <
> rmannibu...@gmail.com
> > >:
> > >
> > > Hi all!
> > >
> > > As mentionned on the list I'd like to get 1.7.2 out the door to let all
> > the
> > > apache stack upgrade (meecrowave, tomee etc) cause of that nasty
> > > concurrency issue.
> > >
> > > Here is the staging repo
> > > *https://repository.apache.org/content/repositories/
> > orgapacheopenwebbeans-1022
> > >  > orgapacheopenwebbeans-1022>*
> > >
> > > The source release zip can be found at:
> > > https://repository.apache.org/content/repositories/
> > orgapacheopenwebbeans-1022/org/apache/openwebbeans/openwebbeans/1.7.2/
> > >
> > > The (dev) dist folder is:
> > > https://dist.apache.org/repos/dist/dev/openwebbeans/1.7.2/
> > >
> > > My gpg key can be found at https://svn.apache.org/repos/
> > > asf/openwebbeans/trunk/KEYS
> > >
> > > Please VOTE:
> > > [+1] awesome, was waiting for it
> > > [+0] well, don't care
> > > [-1] stop there is this issue: ${blocker}
> > >
> > > The VOTE is open for 72h as usual.
> > >
> > >
> > > Thks,
> > > Romain Manni-Bucau
> > > @rmannibucau  |  Blog
> > >  | Old Blog
> > >  | Github  > rmannibucau> |
> > > LinkedIn  | JavaEE Factory
> > > 
> >
>

Re: do an OWB release?

[Thomas Andraschko]

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: [VOTE] Release Apache OpenWebBeans-1.7.0 - take 2

[Thomas Andraschko]

+1 - my applications are working fine

2016-09-01 10:50 GMT+02:00 Romain Manni-Bucau :

> dont care much of digits but +1 to just move forward and not reuse failed
> release numbers
>
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Wordpress Blog
>  | Github  rmannibucau> |
> LinkedIn  | Tomitriber
>  | JavaEE Factory
> 
>
> 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  |  Blog
> > >>  >>  >  | Old Wordpress
> > > Blog
> > >>  >>  >  | Github
> > >>  >>  >  |
> > >>  >>  > LinkedIn  |
> > > Tomitriber
> > >>  >>  >  | JavaEE Factory
> > >>  >>  > 
> > >>  >>  >
> > >>  >>  >
> > >>  >>  > 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
> > >>  >>  >>  >
> > > 

Re: do an OWB release?

[Thomas Andraschko]

Already fixed my bug :)

+1 Romain, let's wait for your fix

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

> 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" <strub...@yahoo.de.invalid> 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 <gpetra...@apache.org>:
> > >
> > >>  +1 for a release!
> > >>
> > >>  regards,
> > >>  gerhard
> > >>
> > >>
> > >>
> > >>  2016-07-27 10:47 GMT+02:00 Mark Struberg <strub...@yahoo.de.invalid
> >:
> > >>
> > >>  > Hi!
> > >>  >
> > >>  > Are there anything we need before shipping the next owb release?
> > >>  >
> > >>  >
> > >>  > LieGrue,
> > >>  > strub
> > >>  >
> > >>
> > >
> >
>

Re: [microwave] name selection

[Thomas Andraschko]

both sounds good, too :)

What about something like micro[profile]wave?


2016-10-31 15:25 GMT+01:00 Mark Struberg <strub...@yahoo.de.invalid>:

> microwave is cool but hard to defend.
> Romain also came up with ‚macrowave‘ or ‚meecrowave‘.
>
> I personally really like macrowave!
>
> LieGrue,
> strub
>
> > Am 31.10.2016 um 15:08 schrieb Romain Manni-Bucau <rmannibu...@gmail.com
> >:
> >
> > talked quickly with Mark and seems "microwave" will be hard to handle on
> > legal side, what about "meecrowave"? keeps the same sound (and logo? :D)
> > but writing makes us safer
> >
> >
> > 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>
> >
> > 2016-10-31 13:26 GMT+01:00 Thomas Andraschko <
> andraschko.tho...@gmail.com>:
> >
> >> if possible legally, microwave is a cool name! :)
> >>
> >> 2016-10-31 12:19 GMT+01:00 Romain Manni-Bucau <rmannibu...@gmail.com>:
> >>
> >>> 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>
> >>>
> >>
>
>

Re: [microwave] name selection

[Thomas Andraschko]

if possible legally, microwave is a cool name! :)

2016-10-31 12:19 GMT+01:00 Romain Manni-Bucau :

> 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  |  Blog
>  | Old Blog
>  | Github  rmannibucau> |
> LinkedIn  | JavaEE Factory
> 
>

Re: [VOTE] release Apache OpenWebBeans-1.7.1

[Thomas Andraschko]

+1

2017-01-02 16:52 GMT+01:00 Romain Manni-Bucau :

> +1
>
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github  rmannibucau> |
> LinkedIn  | JavaEE Factory
> 
>
> 2017-01-02 14:02 GMT+01:00 Mark Struberg :
>
> > Hi folks!
> >
> > Please VOTE for the release of Apache OpenWebBeans-1.7.1.
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/
> > orgapacheopenwebbeans-1019/
> >
> > And the source release:
> > https://repository.apache.org/content/repositories/
> > orgapacheopenwebbeans-1019/org/apache/openwebbeans/openwebbeans/1.7.1/
> >
> > My Key is in the OWB KEYS file.
> >
> > Release-Notes:
> > Bug
> >
> > • [OWB-1150] - OSGI bundle version ranges too restrictive
> > • [OWB-1154] - Synchronization on a string literal
> > • [OWB-1157] - when user does a getReference of a
> programmatically
> > registered bean without looking it up it can lead to multiple bean
> handling
> > • [OWB-1158] - Web lifecycle not registering Servlet Context as
> > bean
> > • [OWB-1159] - HttpServletRequest not available
> > • [OWB-1160] - DefaultArchiveService migh mix up BDA urls if the
> > containing folder is also a cp entry
> > • [OWB-1162] - CDI.current().select(X.class).
> select(SomeQualifier.LITERAL)
> > doesn't work
> > • [OWB-1163] - NPE in BeforeBeanDiscovery#addAnnotatedType if id
> > is null
> > • [OWB-1164] - Third Party Beans do not include Any qualifier if
> > not included in bean impl
> > Improvement
> >
> > • [OWB-1151] - extend our default scan-excludes
> > • [OWB-1152] - Improve compatibility and handling with Java9
> > • [OWB-1153] - improve tomcat-plugin performance
> > • [OWB-1156] - implement support for  feature of CDI-2.0
> > Task
> >
> > • [OWB-1090] - remove jsf12 module for owb-2.0
> >
> >
> > Please VOTE:
> > [+1] great, let's ship it
> > [+0] meh, don't care
> > [-1] stop there is a ${blocker}
> >
> > The VOTE is open for 72h.
> >
> >
> > txs and LieGrue,
> > strub
> >
> >
> >
>

Re: [VOTE] Release Apache OpenWebBeans-1.7.3

[Thomas Andraschko]

+1

2017-04-16 12:06 GMT+02:00 Romain Manni-Bucau :

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

Re: [ANNOUNCE] Welcome John D Ament as Apache OpenWebBeans committer

[Thomas Andraschko]

Welcome! :)

2017-10-06 9:47 GMT+02:00 Mark Struberg :

> Good morning ladies and gents!
>
> Due to his contributions in the CDI SE area of OWB, the Apache
> OpenWebBeans PMC has invited John to become a fellow committer to the
> project.
>
>
> Welcome, John!
> Thanks for your contributions and looking forward to improve OWB together!
>
> best regards,
> the Apache OpenWebBeans PMC

Re: [VOTE] Release Apache OpenWebBeans-2.0.3

[Thomas Andraschko]

+1

2017-12-21 11:17 GMT+01:00 Jean-Louis MONTEIRO :

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

Re: org.apache.webbeans.container.InjectionResolver.fastMatching = false?

[Thomas Andraschko]

Then -1 to set it as default :D


Romain Manni-Bucau  schrieb am So., 12. Aug. 2018,
15:36:

> Without. Any generic injection is broken in any project and de are not spec
> compliant without that flag.
>
> Not sure it does worth having our default for most apps but i know for very
> big ones it saves some boot time.
>
> Le dim. 12 août 2018 13:13, Mark Struberg  a
> écrit :
>
> > hmm which test is that?
> >
> > And does deltaspike break with or without the fastMatch flag?
> >
> > LieGrue,
> > strub
> >
> > > Am 10.08.2018 um 14:23 schrieb Romain Manni-Bucau <
> rmannibu...@gmail.com
> > >:
> > >
> > > Up,
> > >
> > > just realized it affects deltaspike-data which can't inject
> > > EntityRepository > > String> cause of that
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau  |  Blog
> > >  | Old Blog
> > >  | Github <
> > https://github.com/rmannibucau> |
> > > LinkedIn  | Book
> > > <
> >
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> > >
> > >
> > >
> > > Le dim. 22 avr. 2018 à 10:14, Romain Manni-Bucau <
> rmannibu...@gmail.com>
> > a
> > > écrit :
> > >
> > >> Oki, let me know if we can do it and I would be happy to do the
> change.
> > >> Alternatively - if we can't, maybe we should introduce that flag per
> jar
> > >> or extension potentially to enable a "mixed" app (to think if previous
> > >> option doesn't become possible).
> > >>
> > >>
> > >> Romain Manni-Bucau
> > >> @rmannibucau  |  Blog
> > >>  | Old Blog
> > >>  | Github
> > >>  | LinkedIn
> > >>  | Book
> > >> <
> >
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> > >
> > >>
> > >> 2018-04-22 10:09 GMT+02:00 Mark Struberg :
> > >>
> > >>> I'd need to do some tests. But think it's fine.
> > >>>
> > >>> LieGrue,
> > >>> strub
> > >>>
> >  Am 21.04.2018 um 18:48 schrieb Romain Manni-Bucau <
> > >>> rmannibu...@gmail.com>:
> > 
> >  Hi guys,
> > 
> >  do we want to switch our fastMatching flag on the 2.x? (think we
> cant
> > on
> >  1.x)
> > 
> >  Rational is we would be spec compliant. I know it has some issue
> with
> > >>> the
> >  old way to create producers without generics (or more exactly with a
> >  wildcard) but it is not spec compliant too.
> > 
> >  I encounter that issue (of having the wrong default) writing an
> > >>> extension
> >  where i register the exact types even for templates (Foo would
> have
> >  registered Foo, Foo, ... as needed)
> > 
> >  wdyt?
> > 
> >  Romain Manni-Bucau
> >  @rmannibucau  |  Blog
> >   | Old Blog
> >   | Github <
> > >>> https://github.com/rmannibucau> |
> >  LinkedIn  | Book
> >  <
> > >>>
> >
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> > 
> > >>>
> > >>>
> > >>
> >
> >
>

[perf] cache observers in NotificationManager#resolveObservers

[Thomas Andraschko]

Hi,

as you already may know from the TomEE/BVal mailing list, i'm not happy
with the startup performance since TomEE8.

TomEE7 OWB startup ~ 4,5seconds
TomEE8 OWB startup ~ 9seconds

i finally managed to improve the performance on 2 places.

1) Filter framework classes in BVal on PAT
Reduces the startup to ~8seconds

2) Cache obervers for systemEvents in NotificationManager#resolveObservers
Reduces the starup to ~7 seconds
Patch:
https://gist.github.com/tandraschko/de4c72c22e65aaefe041af5a15d110e3

Do you think the patch is ok or could it break something?
I would be happy if mark or romain could improve it :D

Best regards,
Thomas

Re: [perf] cache observers in NotificationManager#resolveObservers

[Thomas Andraschko]

ok, will provide a better patch on monday!

Am Fr., 12. Okt. 2018 um 16:44 Uhr schrieb Romain Manni-Bucau <
rmannibu...@gmail.com>:

> We can surely clean it up after startup but looks good
>
> Le ven. 12 oct. 2018 17:16, Thomas Andraschko  >
> a écrit :
>
> > Hi,
> >
> > as you already may know from the TomEE/BVal mailing list, i'm not happy
> > with the startup performance since TomEE8.
> >
> > TomEE7 OWB startup ~ 4,5seconds
> > TomEE8 OWB startup ~ 9seconds
> >
> > i finally managed to improve the performance on 2 places.
> >
> > 1) Filter framework classes in BVal on PAT
> > Reduces the startup to ~8seconds
> >
> > 2) Cache obervers for systemEvents in
> NotificationManager#resolveObservers
> > Reduces the starup to ~7 seconds
> > Patch:
> > https://gist.github.com/tandraschko/de4c72c22e65aaefe041af5a15d110e3
> >
> > Do you think the patch is ok or could it break something?
> > I would be happy if mark or romain could improve it :D
> >
> > Best regards,
> > Thomas
> >
>

Re: [perf] cache observers in NotificationManager#resolveObservers

[Thomas Andraschko]

Not sure. I just searched over the tests yesterday and we didn't had tests
for a generic ProcessManagedBean, so i added the new ones.
I will do some more tests.

Am Di., 16. Okt. 2018 um 08:24 Uhr schrieb Mark Struberg
:

> Didn't we have a test for generic types already?
> E.g. ProcessAnnotatedType vs ProcessAnnotatedType
> And one type layer down
> ProcessAnnotatedType> vs
> ProcessAnnotatedType>
>
> If we don't have this kind of test yet then we should add one.
>
> LieGrue,
> strub
>
> > Am 15.10.2018 um 11:23 schrieb Thomas Andraschko <
> andraschko.tho...@gmail.com>:
> >
> > ok... i totally forgot about generic lifecycle events...
> >
> > I will try to just optimize the current NotificationManager, without
> adding
> > a breaking cache :D
> >
> > Am Fr., 12. Okt. 2018 um 16:48 Uhr schrieb Thomas Andraschko <
> > andraschko.tho...@gmail.com>:
> >
> >> ok, will provide a better patch on monday!
> >>
> >> Am Fr., 12. Okt. 2018 um 16:44 Uhr schrieb Romain Manni-Bucau <
> >> rmannibu...@gmail.com>:
> >>
> >>> We can surely clean it up after startup but looks good
> >>>
> >>> Le ven. 12 oct. 2018 17:16, Thomas Andraschko <
> >>> andraschko.tho...@gmail.com>
> >>> a écrit :
> >>>
> >>>> Hi,
> >>>>
> >>>> as you already may know from the TomEE/BVal mailing list, i'm not
> happy
> >>>> with the startup performance since TomEE8.
> >>>>
> >>>> TomEE7 OWB startup ~ 4,5seconds
> >>>> TomEE8 OWB startup ~ 9seconds
> >>>>
> >>>> i finally managed to improve the performance on 2 places.
> >>>>
> >>>> 1) Filter framework classes in BVal on PAT
> >>>>Reduces the startup to ~8seconds
> >>>>
> >>>> 2) Cache obervers for systemEvents in
> >>> NotificationManager#resolveObservers
> >>>>Reduces the starup to ~7 seconds
> >>>>Patch:
> >>>> https://gist.github.com/tandraschko/de4c72c22e65aaefe041af5a15d110e3
> >>>>
> >>>> Do you think the patch is ok or could it break something?
> >>>> I would be happy if mark or romain could improve it :D
> >>>>
> >>>> Best regards,
> >>>> Thomas
> >>>>
> >>>
> >>
>
>

Re: 2.0.8 release?

[Thomas Andraschko]

Weekend is of course ok :)
Would be really great if you could trigger it, still didn't had the change
to do a apache release :D

Am Mi., 17. Okt. 2018 um 15:40 Uhr schrieb Mark Struberg
:

> sure we can. Just slightly offline due to travelling to GeeCon in Prague
> right now.
> Probably do a release on the weekend?
>
> LieGrue,
> strub
>
> > Am 17.10.2018 um 15:21 schrieb Thomas Andraschko <
> andraschko.tho...@gmail.com>:
> >
> > Hi Mark,
> >
> > WDYT about releasing 2.0.8?
> > We have 2 good performance improvements, ASM7 update and some bug fixes.
> > I think it's not a bad time for a release + we can push the new release
> to
> > TomEE?
> >
> > TomEE-M1 + 2.0.8 improves the startup of TomEE, compared to the TomEE
> > SNAPSHOT last week, up to ~2,5 seconds.
> >
> > Best regards,
> > Thomas
>
>

2.0.8 release?

[Thomas Andraschko]

Hi Mark,

WDYT about releasing 2.0.8?
We have 2 good performance improvements, ASM7 update and some bug fixes.
I think it's not a bad time for a release + we can push the new release to
TomEE?

TomEE-M1 + 2.0.8 improves the startup of TomEE, compared to the TomEE
SNAPSHOT last week, up to ~2,5 seconds.

Best regards,
Thomas

Re: 2.0.8 release?

[Thomas Andraschko]

done - whats next? :D

Am Mi., 17. Okt. 2018 um 18:37 Uhr schrieb Mark Struberg
:

> +1
>
> First step is to walk through our jira issues for the release.
> Check if some are implemented but not yet set to fixed in Jira.
> Then move the rest to the next release version.
> Go to release notes and copy those to our readme.txt
>
>
>
> Sent with autocorrect...
>
> > On 17.10.2018, at 16:24, Romain Manni-Bucau 
> wrote:
> >
> > Sounds like it can be the moment to pass another step? ;)
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://rmannibucau.metawerx.net/> | Old Blog
> > <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> > <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
> >
> >
> > Le mer. 17 oct. 2018 à 15:45, Thomas Andraschko <
> andraschko.tho...@gmail.com>
> > a écrit :
> >
> >> Weekend is of course ok :)
> >> Would be really great if you could trigger it, still didn't had the
> change
> >> to do a apache release :D
> >>
> >> Am Mi., 17. Okt. 2018 um 15:40 Uhr schrieb Mark Struberg
> >> :
> >>
> >>> sure we can. Just slightly offline due to travelling to GeeCon in
> Prague
> >>> right now.
> >>> Probably do a release on the weekend?
> >>>
> >>> LieGrue,
> >>> strub
> >>>
> >>>> Am 17.10.2018 um 15:21 schrieb Thomas Andraschko <
> >>> andraschko.tho...@gmail.com>:
> >>>>
> >>>> Hi Mark,
> >>>>
> >>>> WDYT about releasing 2.0.8?
> >>>> We have 2 good performance improvements, ASM7 update and some bug
> >> fixes.
> >>>> I think it's not a bad time for a release + we can push the new
> release
> >>> to
> >>>> TomEE?
> >>>>
> >>>> TomEE-M1 + 2.0.8 improves the startup of TomEE, compared to the TomEE
> >>>> SNAPSHOT last week, up to ~2,5 seconds.
> >>>>
> >>>> Best regards,
> >>>> Thomas
> >>>
> >>>
> >>
>
>

Re: 2.0.8 release?

[Thomas Andraschko]

my app works with OWB+Jetty and also TomEE8, the tomee tests are working
fine, the geronimo microprofile tests are working fine
how can i test it with DS? All builds are still on OWB 1.7.x

Am Mi., 24. Okt. 2018 um 12:24 Uhr schrieb Romain Manni-Bucau <
rmannibu...@gmail.com>:

> some sanity check son "known" projects (DS, meecrowave, tomee, your app
> etc)
> then jira triage, mvn release:prepare release:perform, dist area creation
> (don't forget the sha512 ;)) and vote thread
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>
>
> Le mer. 24 oct. 2018 à 12:17, Thomas Andraschko <
> andraschko.tho...@gmail.com>
> a écrit :
>
> > done - whats next? :D
> >
> > Am Mi., 17. Okt. 2018 um 18:37 Uhr schrieb Mark Struberg
> > :
> >
> > > +1
> > >
> > > First step is to walk through our jira issues for the release.
> > > Check if some are implemented but not yet set to fixed in Jira.
> > > Then move the rest to the next release version.
> > > Go to release notes and copy those to our readme.txt
> > >
> > >
> > >
> > > Sent with autocorrect...
> > >
> > > > On 17.10.2018, at 16:24, Romain Manni-Bucau 
> > > wrote:
> > > >
> > > > Sounds like it can be the moment to pass another step? ;)
> > > >
> > > > Romain Manni-Bucau
> > > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > > <https://rmannibucau.metawerx.net/> | Old Blog
> > > > <http://rmannibucau.wordpress.com> | Github <
> > > https://github.com/rmannibucau> |
> > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> > > > <
> > >
> >
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> > > >
> > > >
> > > >
> > > > Le mer. 17 oct. 2018 à 15:45, Thomas Andraschko <
> > > andraschko.tho...@gmail.com>
> > > > a écrit :
> > > >
> > > >> Weekend is of course ok :)
> > > >> Would be really great if you could trigger it, still didn't had the
> > > change
> > > >> to do a apache release :D
> > > >>
> > > >> Am Mi., 17. Okt. 2018 um 15:40 Uhr schrieb Mark Struberg
> > > >> :
> > > >>
> > > >>> sure we can. Just slightly offline due to travelling to GeeCon in
> > > Prague
> > > >>> right now.
> > > >>> Probably do a release on the weekend?
> > > >>>
> > > >>> LieGrue,
> > > >>> strub
> > > >>>
> > > >>>> Am 17.10.2018 um 15:21 schrieb Thomas Andraschko <
> > > >>> andraschko.tho...@gmail.com>:
> > > >>>>
> > > >>>> Hi Mark,
> > > >>>>
> > > >>>> WDYT about releasing 2.0.8?
> > > >>>> We have 2 good performance improvements, ASM7 update and some bug
> > > >> fixes.
> > > >>>> I think it's not a bad time for a release + we can push the new
> > > release
> > > >>> to
> > > >>>> TomEE?
> > > >>>>
> > > >>>> TomEE-M1 + 2.0.8 improves the startup of TomEE, compared to the
> > TomEE
> > > >>>> SNAPSHOT last week, up to ~2,5 seconds.
> > > >>>>
> > > >>>> Best regards,
> > > >>>> Thomas
> > > >>>
> > > >>>
> > > >>
> > >
> > >
> >
>

Re: 2.0.8 release?

[Thomas Andraschko]

it's already there, isnt it?
https://search.maven.org/artifact/org.apache.xbean/xbean-asm7-shaded/4.11/bundle
It seems that we already use it

Am Mo., 29. Okt. 2018 um 16:55 Uhr schrieb Mark Struberg
:

> did a few performance tests. Runs perfectly fine.
> DS builds as well.
>
> Let's wait for geronimo-xbean-asm7 and then do a release?
>
> LieGrue,
> strub
>
>
> > Am 24.10.2018 um 14:55 schrieb Romain Manni-Bucau  >:
> >
> > deltaspike$ mvn clean install -POWB2 -Dowb.version=2.0.8-SNAPSHOT
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://rmannibucau.metawerx.net/> | Old Blog
> > <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> > <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
> >
> >
> > Le mer. 24 oct. 2018 à 14:02, Mark Struberg 
> a
> > écrit :
> >
> >> Gimme a day to check with my apps please.
> >>
> >> LieGrue,
> >> strub
> >>
> >>
> >>> Am 24.10.2018 um 13:48 schrieb Thomas Andraschko <
> >> andraschko.tho...@gmail.com>:
> >>>
> >>> my app works with OWB+Jetty and also TomEE8, the tomee tests are
> working
> >>> fine, the geronimo microprofile tests are working fine
> >>> how can i test it with DS? All builds are still on OWB 1.7.x
> >>>
> >>> Am Mi., 24. Okt. 2018 um 12:24 Uhr schrieb Romain Manni-Bucau <
> >>> rmannibu...@gmail.com>:
> >>>
> >>>> some sanity check son "known" projects (DS, meecrowave, tomee, your
> app
> >>>> etc)
> >>>> then jira triage, mvn release:prepare release:perform, dist area
> >> creation
> >>>> (don't forget the sha512 ;)) and vote thread
> >>>>
> >>>> Romain Manni-Bucau
> >>>> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> >>>> <https://rmannibucau.metawerx.net/> | Old Blog
> >>>> <http://rmannibucau.wordpress.com> | Github <
> >>>> https://github.com/rmannibucau> |
> >>>> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> >>>> <
> >>>>
> >>
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >>>>>
> >>>>
> >>>>
> >>>> Le mer. 24 oct. 2018 à 12:17, Thomas Andraschko <
> >>>> andraschko.tho...@gmail.com>
> >>>> a écrit :
> >>>>
> >>>>> done - whats next? :D
> >>>>>
> >>>>> Am Mi., 17. Okt. 2018 um 18:37 Uhr schrieb Mark Struberg
> >>>>> :
> >>>>>
> >>>>>> +1
> >>>>>>
> >>>>>> First step is to walk through our jira issues for the release.
> >>>>>> Check if some are implemented but not yet set to fixed in Jira.
> >>>>>> Then move the rest to the next release version.
> >>>>>> Go to release notes and copy those to our readme.txt
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Sent with autocorrect...
> >>>>>>
> >>>>>>> On 17.10.2018, at 16:24, Romain Manni-Bucau  >
> >>>>>> wrote:
> >>>>>>>
> >>>>>>> Sounds like it can be the moment to pass another step? ;)
> >>>>>>>
> >>>>>>> Romain Manni-Bucau
> >>>>>>> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> >>>>>>> <https://rmannibucau.metawerx.net/> | Old Blog
> >>>>>>> <http://rmannibucau.wordpress.com> | Github <
> >>>>>> https://github.com/rmannibucau> |
> >>>>>>> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> >>>>>>> <
> >>>>>>
> >>>>>
> >>>>
> >>
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> Le mer. 17 oct. 2018 à 15:45, Thomas Andraschko <
> >>>>>> andraschko.tho...@gmail.com>
> >>>>>>> a écrit :
> >>>>>>>
> >>>>>>>> Weekend is of course ok :)
> >>>>>>>> Would be really great if you could trigger it, still didn't had
> the
> >>>>>> change
> >>>>>>>> to do a apache release :D
> >>>>>>>>
> >>>>>>>> Am Mi., 17. Okt. 2018 um 15:40 Uhr schrieb Mark Struberg
> >>>>>>>> :
> >>>>>>>>
> >>>>>>>>> sure we can. Just slightly offline due to travelling to GeeCon in
> >>>>>> Prague
> >>>>>>>>> right now.
> >>>>>>>>> Probably do a release on the weekend?
> >>>>>>>>>
> >>>>>>>>> LieGrue,
> >>>>>>>>> strub
> >>>>>>>>>
> >>>>>>>>>> Am 17.10.2018 um 15:21 schrieb Thomas Andraschko <
> >>>>>>>>> andraschko.tho...@gmail.com>:
> >>>>>>>>>>
> >>>>>>>>>> Hi Mark,
> >>>>>>>>>>
> >>>>>>>>>> WDYT about releasing 2.0.8?
> >>>>>>>>>> We have 2 good performance improvements, ASM7 update and some
> bug
> >>>>>>>> fixes.
> >>>>>>>>>> I think it's not a bad time for a release + we can push the new
> >>>>>> release
> >>>>>>>>> to
> >>>>>>>>>> TomEE?
> >>>>>>>>>>
> >>>>>>>>>> TomEE-M1 + 2.0.8 improves the startup of TomEE, compared to the
> >>>>> TomEE
> >>>>>>>>>> SNAPSHOT last week, up to ~2,5 seconds.
> >>>>>>>>>>
> >>>>>>>>>> Best regards,
> >>>>>>>>>> Thomas
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>
> >>
>
>

Re: 2.0.8 release?

[Thomas Andraschko]

ahh ok, so lets wait :)

Am Mo., 29. Okt. 2018 um 17:29 Uhr schrieb Romain Manni-Bucau <
rmannibu...@gmail.com>:

> it uses asm beta, final is in vote
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>
>
> Le lun. 29 oct. 2018 à 16:57, Thomas Andraschko <
> andraschko.tho...@gmail.com>
> a écrit :
>
> > it's already there, isnt it?
> >
> >
> https://search.maven.org/artifact/org.apache.xbean/xbean-asm7-shaded/4.11/bundle
> > It seems that we already use it
> >
> > Am Mo., 29. Okt. 2018 um 16:55 Uhr schrieb Mark Struberg
> > :
> >
> > > did a few performance tests. Runs perfectly fine.
> > > DS builds as well.
> > >
> > > Let's wait for geronimo-xbean-asm7 and then do a release?
> > >
> > > LieGrue,
> > > strub
> > >
> > >
> > > > Am 24.10.2018 um 14:55 schrieb Romain Manni-Bucau <
> > rmannibu...@gmail.com
> > > >:
> > > >
> > > > deltaspike$ mvn clean install -POWB2 -Dowb.version=2.0.8-SNAPSHOT
> > > >
> > > >
> > > > Romain Manni-Bucau
> > > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > > <https://rmannibucau.metawerx.net/> | Old Blog
> > > > <http://rmannibucau.wordpress.com> | Github <
> > > https://github.com/rmannibucau> |
> > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> > > > <
> > >
> >
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> > > >
> > > >
> > > >
> > > > Le mer. 24 oct. 2018 à 14:02, Mark Struberg
>  > >
> > > a
> > > > écrit :
> > > >
> > > >> Gimme a day to check with my apps please.
> > > >>
> > > >> LieGrue,
> > > >> strub
> > > >>
> > > >>
> > > >>> Am 24.10.2018 um 13:48 schrieb Thomas Andraschko <
> > > >> andraschko.tho...@gmail.com>:
> > > >>>
> > > >>> my app works with OWB+Jetty and also TomEE8, the tomee tests are
> > > working
> > > >>> fine, the geronimo microprofile tests are working fine
> > > >>> how can i test it with DS? All builds are still on OWB 1.7.x
> > > >>>
> > > >>> Am Mi., 24. Okt. 2018 um 12:24 Uhr schrieb Romain Manni-Bucau <
> > > >>> rmannibu...@gmail.com>:
> > > >>>
> > > >>>> some sanity check son "known" projects (DS, meecrowave, tomee,
> your
> > > app
> > > >>>> etc)
> > > >>>> then jira triage, mvn release:prepare release:perform, dist area
> > > >> creation
> > > >>>> (don't forget the sha512 ;)) and vote thread
> > > >>>>
> > > >>>> Romain Manni-Bucau
> > > >>>> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > >>>> <https://rmannibucau.metawerx.net/> | Old Blog
> > > >>>> <http://rmannibucau.wordpress.com> | Github <
> > > >>>> https://github.com/rmannibucau> |
> > > >>>> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> > > >>>> <
> > > >>>>
> > > >>
> > >
> >
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> > > >>>>>
> > > >>>>
> > > >>>>
> > > >>>> Le mer. 24 oct. 2018 à 12:17, Thomas Andraschko <
> > > >>>> andraschko.tho...@gmail.com>
> > > >>>> a écrit :
> > > >>>>
> > > >>>>> done - whats next? :D
> > > >>>>>
> > > >>>>> Am Mi., 17. Okt. 2018 um 18:37 Uhr schrieb Mark Struberg
> > > >>>>> :
> > > >>>>>
> > > >>>>>> +1
> > > >>>>>>
> > > >>>>>> First step is to walk through our jira issues fo

Re: [VOTE] Release Apache OpenWebBeans-2.0.8

[Thomas Andraschko]

and my own +1


The VOTE has passed with the following:

+1: Romain, Mark, Reinhard, Gerhard, Thomas
No -1 nor 0

I'll gonna continue with the release steps.


Am Sa., 10. Nov. 2018 um 18:09 Uhr schrieb Gerhard Petracek <
gpetra...@apache.org>:

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

[ANNOUNCE] Apache OpenWebBeans-2.0.8 CDI container

[Thomas Andraschko]

 It’s a great pleasure to announce the release of Apache OpenWebBeans-2.0.8

Apache OpenWebBeans-2.x is a CDI container (Contexts and Dependency
Injection for Java) and targets the CDI-2.0 specification (JavaEE 8).

This is a maintenance release targeting the new CDI 2.0 specification!
CDI is a JavaEE standard specification (JSR-365) but fully available under
Apache License v2.0.
http://cdi-spec.org/
https://docs.jboss.org/cdi/spec/2.0/cdi-spec.html

OpenWebBeans is modularly built and can be used either in pure Java SE, in
a Servlet Container like e.g. Tomcat or in fully fledged JavaEE containers.
Our core is only 700kByte and thus brings full JavaEE-8 compatibility at a
smaller size of most so called ‚micro solutions‘.

Distribution packages can be downloaded via
https://openwebbeans.apache.org/download.html

The release is also available via maven
http://repo1.maven.org/maven2/org/apache/openwebbeans/


We also include an installer scripts in our binary distribution which can
be used as easy as:

$> unzip openwebbeans-distribution-2.0.8-binary.zip
$> cd openwebbeans-distribution-2.0.8
$> ./install_owb_tomcat7.bat /opt/your/apache-tomcat-9.x.x

(works with Apache Tomcat7 and 8, 8.5 and 9)

OpenWebBeans-2.0.x is included in Apache Meecrowave-1.2.x and the upcoming
Apache TomEE-8.x releases.

Please also visit our homepage http://openwebbeans.apache.org and contact
us on our mailing lists.

have fun,
The Apache OpenWebBeans Team

The following tickets got resolved:

Bug
[OWB-1257] - Conditional exclusion of beans in beans.xml does not honor
system property
[OWB-1263] - Generic observers not called correctly
[OWB-1264] - Observers method throws NoClassDefFoundError for optional
classes
[OWB-1269] - TomcatSecurityService principal is not the contextual one
out of request scope beans

Improvement
[OWB-1261] - Upgrade ASM to version 7
[OWB-1265] - [perf] cache AnnotationManager#getRepeatableMethod
[OWB-1266] - [perf] InjectionResolver cache can be activated earlier

Task
[OWB-1268] - Upgrade to xbean 4.12

[ANNOUNCE] Apache OpenWebBeans-2.0.8 CDI container

[Thomas Andraschko]

It’s a great pleasure to announce the release of Apache OpenWebBeans-2.0.8

Apache OpenWebBeans-2.x is a CDI container (Contexts and Dependency
Injection for Java) and targets the CDI-2.0 specification (JavaEE 8).

This is a maintenance release targeting the new CDI 2.0 specification!
CDI is a JavaEE standard specification (JSR-365) but fully available under
Apache License v2.0.
http://cdi-spec.org/
https://docs.jboss.org/cdi/spec/2.0/cdi-spec.html

OpenWebBeans is modularly built and can be used either in pure Java SE, in
a Servlet Container like e.g. Tomcat or in fully fledged JavaEE containers.
Our core is only 700kByte and thus brings full JavaEE-8 compatibility at a
smaller size of most so called ‚micro solutions‘.

Distribution packages can be downloaded via
https://openwebbeans.apache.org/download.html

The release is also available via maven
http://repo1.maven.org/maven2/org/apache/openwebbeans/


We also include an installer scripts in our binary distribution which can
be used as easy as:

$> unzip openwebbeans-distribution-2.0.8-binary.zip
$> cd openwebbeans-distribution-2.0.8
$> ./install_owb_tomcat7.bat /opt/your/apache-tomcat-9.x.x

(works with Apache Tomcat7 and 8, 8.5 and 9)

OpenWebBeans-2.0.x is included in Apache Meecrowave-1.2.x and the upcoming
Apache TomEE-8.x releases.

Please also visit our homepage http://openwebbeans.apache.org and contact
us on our mailing lists.

have fun,
The Apache OpenWebBeans Team

The following tickets got resolved:

Bug
[OWB-1257] - Conditional exclusion of beans in beans.xml does not honor
system property
[OWB-1263] - Generic observers not called correctly
[OWB-1264] - Observers method throws NoClassDefFoundError for optional
classes
[OWB-1269] - TomcatSecurityService principal is not the contextual one
out of request scope beans

Improvement
[OWB-1261] - Upgrade ASM to version 7
[OWB-1265] - [perf] cache AnnotationManager#getRepeatableMethod
[OWB-1266] - [perf] InjectionResolver cache can be activated earlier

Task
[OWB-1268] - Upgrade to xbean 4.12

Re: 2.0.8 release?

[Thomas Andraschko]

Its released and upgraded now, right!?

Am Mo., 29. Okt. 2018, 17:33 hat Thomas Andraschko <
andraschko.tho...@gmail.com> geschrieben:

> ahh ok, so lets wait :)
>
> Am Mo., 29. Okt. 2018 um 17:29 Uhr schrieb Romain Manni-Bucau <
> rmannibu...@gmail.com>:
>
>> it uses asm beta, final is in vote
>>
>> Romain Manni-Bucau
>> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
>> <https://rmannibucau.metawerx.net/> | Old Blog
>> <http://rmannibucau.wordpress.com> | Github <
>> https://github.com/rmannibucau> |
>> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
>> <
>> https://www.packtpub.com/application-development/java-ee-8-high-performance
>> >
>>
>>
>> Le lun. 29 oct. 2018 à 16:57, Thomas Andraschko <
>> andraschko.tho...@gmail.com>
>> a écrit :
>>
>> > it's already there, isnt it?
>> >
>> >
>> https://search.maven.org/artifact/org.apache.xbean/xbean-asm7-shaded/4.11/bundle
>> > It seems that we already use it
>> >
>> > Am Mo., 29. Okt. 2018 um 16:55 Uhr schrieb Mark Struberg
>> > :
>> >
>> > > did a few performance tests. Runs perfectly fine.
>> > > DS builds as well.
>> > >
>> > > Let's wait for geronimo-xbean-asm7 and then do a release?
>> > >
>> > > LieGrue,
>> > > strub
>> > >
>> > >
>> > > > Am 24.10.2018 um 14:55 schrieb Romain Manni-Bucau <
>> > rmannibu...@gmail.com
>> > > >:
>> > > >
>> > > > deltaspike$ mvn clean install -POWB2 -Dowb.version=2.0.8-SNAPSHOT
>> > > >
>> > > >
>> > > > Romain Manni-Bucau
>> > > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
>> > > > <https://rmannibucau.metawerx.net/> | Old Blog
>> > > > <http://rmannibucau.wordpress.com> | Github <
>> > > https://github.com/rmannibucau> |
>> > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
>> > > > <
>> > >
>> >
>> https://www.packtpub.com/application-development/java-ee-8-high-performance
>> > > >
>> > > >
>> > > >
>> > > > Le mer. 24 oct. 2018 à 14:02, Mark Struberg
>> > > >
>> > > a
>> > > > écrit :
>> > > >
>> > > >> Gimme a day to check with my apps please.
>> > > >>
>> > > >> LieGrue,
>> > > >> strub
>> > > >>
>> > > >>
>> > > >>> Am 24.10.2018 um 13:48 schrieb Thomas Andraschko <
>> > > >> andraschko.tho...@gmail.com>:
>> > > >>>
>> > > >>> my app works with OWB+Jetty and also TomEE8, the tomee tests are
>> > > working
>> > > >>> fine, the geronimo microprofile tests are working fine
>> > > >>> how can i test it with DS? All builds are still on OWB 1.7.x
>> > > >>>
>> > > >>> Am Mi., 24. Okt. 2018 um 12:24 Uhr schrieb Romain Manni-Bucau <
>> > > >>> rmannibu...@gmail.com>:
>> > > >>>
>> > > >>>> some sanity check son "known" projects (DS, meecrowave, tomee,
>> your
>> > > app
>> > > >>>> etc)
>> > > >>>> then jira triage, mvn release:prepare release:perform, dist area
>> > > >> creation
>> > > >>>> (don't forget the sha512 ;)) and vote thread
>> > > >>>>
>> > > >>>> Romain Manni-Bucau
>> > > >>>> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
>> > > >>>> <https://rmannibucau.metawerx.net/> | Old Blog
>> > > >>>> <http://rmannibucau.wordpress.com> | Github <
>> > > >>>> https://github.com/rmannibucau> |
>> > > >>>> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
>> > > >>>> <
>> > > >>>>
>> > > >>
>> > >
>> >
>> https://www.packtpub.com/application-development/java-ee-8-high-performance
>> > > >>>>>
>> > > >>>>
>> > > >>>>
>> > > >>>> Le mer. 24 oct. 2018 à 12:17, Thomas Andraschko <

[VOTE] Release Apache OpenWebBeans-2.0.8

[Thomas Andraschko]

Hi all,

I'd like to call a VOTE on releasing Apache OpenWebBeans-2.0.8

The following tickets got resolved:

Bug

[OWB-1257] - Conditional exclusion of beans in beans.xml does not honor
system property
[OWB-1263] - Generic observers not called correctly
[OWB-1264] - Observers method throws NoClassDefFoundError for optional
classes
[OWB-1269] - TomcatSecurityService principal is not the contextual one
out of request scope beans

Improvement

[OWB-1261] - Upgrade ASM to version 7
[OWB-1265] - [perf] cache AnnotationManager#getRepeatableMethod
[OWB-1266] - [perf] InjectionResolver cache can be activated earlier

Task

[OWB-1268] - Upgrade to xbean 4.12

The staging repo is:
https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1047

The source release is in
https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1047/org/apache/openwebbeans/openwebbeans/2.0.8/

The sha1 of openwebbeans-2.0.8-source-release.zip is
49ddc4060fbce6a83b58666e5db1ae7cd56953c7

The sha512 is
305f03de4690ed9855c3b40a46ca2d47e92efa7bccaf639431ef50c31bd817ed91bb2e7dee1ff3e3a0e65715e868107116fd97980215de37eda2b892973a5812

The tag in SVN is
https://svn.apache.org/repos/asf/openwebbeans/tags/openwebbeans-2.0.8/
-r1846048


Please VOTE:

[+1] go for it!
[+0] meh, don't care
[-1] nah, because there is a ${showstopper}


The VOTE is open for 72h.

Re: [VOTE] Release Apache OpenWebBeans-2.0.8

[Thomas Andraschko]

check-in done in trunk ;)

Am Fr., 9. Nov. 2018 um 09:16 Uhr schrieb Mark Struberg
:

>  Thomas, could you please add your pgp key to our KEYS file?Not sure where
> to take it right now to validate the signature.
> txs and LieGrue,strub
>
> On Thursday, 8 November 2018, 18:47:45 CET, Romain Manni-Bucau <
> rmannibu...@gmail.com> wrote:
>
>  +1, works well
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>
>
> Le mer. 7 nov. 2018 à 17:47, Romain Manni-Bucau  a
> écrit :
>
> > I will review it tomorrow but I want to thank you to have done it and say
> > you congrats for your first release very early! Well done Thomas!
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://rmannibucau.metawerx.net/> | Old Blog
> > <http://rmannibucau.wordpress.com> | Github
> > <https://github.com/rmannibucau> | LinkedIn
> > <https://www.linkedin.com/in/rmannibucau> | Book
> > <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
> >
> >
> > Le mer. 7 nov. 2018 à 17:40, Thomas Andraschko <
> > andraschko.tho...@gmail.com> a écrit :
> >
> >> Hi all,
> >>
> >> I'd like to call a VOTE on releasing Apache OpenWebBeans-2.0.8
> >>
> >> The following tickets got resolved:
> >>
> >> Bug
> >>
> >>[OWB-1257] - Conditional exclusion of beans in beans.xml does not
> >> honor
> >> system property
> >>[OWB-1263] - Generic observers not called correctly
> >>[OWB-1264] - Observers method throws NoClassDefFoundError for
> optional
> >> classes
> >>[OWB-1269] - TomcatSecurityService principal is not the contextual
> one
> >> out of request scope beans
> >>
> >> Improvement
> >>
> >>[OWB-1261] - Upgrade ASM to version 7
> >>[OWB-1265] - [perf] cache AnnotationManager#getRepeatableMethod
> >>[OWB-1266] - [perf] InjectionResolver cache can be activated earlier
> >>
> >> Task
> >>
> >>[OWB-1268] - Upgrade to xbean 4.12
> >>
> >> The staging repo is:
> >>
> >>
> https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1047
> >>
> >> The source release is in
> >>
> >>
> https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1047/org/apache/openwebbeans/openwebbeans/2.0.8/
> >>
> >> The sha1 of openwebbeans-2.0.8-source-release.zip is
> >> 49ddc4060fbce6a83b58666e5db1ae7cd56953c7
> >>
> >> The sha512 is
> >>
> >>
> 305f03de4690ed9855c3b40a46ca2d47e92efa7bccaf639431ef50c31bd817ed91bb2e7dee1ff3e3a0e65715e868107116fd97980215de37eda2b892973a5812
> >>
> >> The tag in SVN is
> >> https://svn.apache.org/repos/asf/openwebbeans/tags/openwebbeans-2.0.8/
> >> -r1846048
> >> <
> https://svn.apache.org/repos/asf/openwebbeans/tags/openwebbeans-2.0.8/-r1846048
> >
> >>
> >>
> >> Please VOTE:
> >>
> >> [+1] go for it!
> >> [+0] meh, don't care
> >> [-1] nah, because there is a ${showstopper}
> >>
> >>
> >> The VOTE is open for 72h.
> >>
> >

Re: OWB release for Java 11?

[Thomas Andraschko]

I released 2.0.8 today with those changes ;)

Am Mo., 12. Nov. 2018, 20:29 hat Jean-Louis MONTEIRO 
geschrieben:

> Hey guys,
>
> As you may have noticed, I am trying to push the Java 11 compatibility
> forward. See TomEE mailing list.
>
> I have noticed Romain upgraded ASM to ASM 7 and XBean to 4.12.
> If everything is ok, any objection if I do a release with OWB?
>
> Thanks
> Jean-Louis
>