ProjectStages in EAR scenarios

Hi folks! The ProjectStageProducer currently uses a static field, thus we only have 1 ProjectStage per EAR if DeltaSpike gets shipped in the EARs /lib folder (opposed to each WAR). I personally don't think this is a problem - au contráire, I think it makes sense to have all WARs using the

Re: Updating site docs

@deltaspike.apache.org; Mark Struberg strub...@yahoo.de Sent: Monday, 10 June 2013, 15:39 Subject: Re: Updating site docs Hi Mark, What about permissions? Should we all have permissions to update docs or only VP? John On Mon, Jun 10, 2013 at 2:01 AM, Mark Struberg strub...@yahoo.de wrote

Re: Servlet module prototype

. 2013/6/7 Gerhard Petracek gerhard.petra...@gmail.com the general jira-issue for it is [1]. regards, gerhard [1] https://issues.apache.org/jira/browse/DELTASPIKE-349 2013/6/7 Mark Struberg strub...@yahoo.de

wonky jenkins

Hi! Currently our Jenkins is a bit wonky/wacky. Currently clarifying the issue with infra. LieGrue, strub

Re: [VOTE] Bean Validation Module Name

+1 LieGrue, strub - Original Message - From: John D. Ament john.d.am...@gmail.com To: dev@deltaspike.apache.org Cc: Sent: Monday, 17 June 2013, 2:42 Subject: Re: [VOTE] Bean Validation Module Name [+1] beanval BTW, I'll leave this open for about 72 hours. John On

reminder: use jira numbers in commits

Hi folks! Nothing serious, but if possible, please add the DELTASPIKE-xxx jira numbers to the commit comment in the future. txs and LieGrue, strub

package in core: view.config

Hi! All the ViewConfig stuff has not much to do with 'Configuration', right? It's more related to 'View'. Kind of the configuration for the View, but still only related to the View stuff. As I've understood we only need it in core at all because some Security stuff references it as well,

Re: Time to cut 0.5?

yup, I really like to get 0.5 out of the door. We need some reviews first though. Mainly the new query and beanval modules. Sadly, I'm 180% overloaded at $$dayjob right now. Hope I can find some time on the weekend. Or did anyone else take a deep look at it already? Then I'd be happy to run the

all tests green (almost)

Hi folks! All our CI are now green again. The only Exception being weld-2.0.0 and 2.0.0.SP1. I first guessed it's due to the missing getBean() handling in our InjectionPoints created via BeanBuilder. But it turns our it had no impact. These 2 weld verions fail with an internal proxy failure

Re: General Converter

Hi Florian! Not yet on our list. We are currently working on getting 0.5 out of the door (code reviews and testing against many containers) Please file a feature request in JIRA describing what this Seam2 feature is about and why you like it. txs and LieGrue, strub - Original Message

Re: Checkstyle change

-0 Whether to have them in the same or next line is imo a matter of taste. Both styles work well, so I see no reason to change this now. If there is a majority for another styling then I have no objection as long as a few rules still apply, like e.g. forcing braces even for 1-line blocks, etc

Re: Data module, full replacement for Seam Factories?

I agree, sounds like something useful. LieGrue, strub From: Thomas Hug thomas@gmail.com To: dev@deltaspike.apache.org dev@deltaspike.apache.org Sent: Tuesday, 17 September 2013, 16:02 Subject: Re: Data module, full replacement for Seam Factories? Hi

Re: ConfigSource using ThreadLocal

I think a ThreadLocal ConfigSource is kind of an anti-pattern. Even in your case it looks like this only would work if you start the container inplace. But it will not work with remote containers. But there is nothing which prevents you from registering an own ThreadLocalTestConfigSource which

Re: DS + JSF 2.2

the current draft to your github repository. regards, gerhard 2013/10/1 Mark Struberg strub...@yahoo.de Yes, I intended to fix this since a long time. But I'm atm fully blasted with $$dayjob work. And the current customer does not use JSF but Vaadin (which is nice for rendering

Re: CMS diff: Documentation

applied, txs! LieGrue, strub From: Karl Kildén anonym...@apache.org To: dev@deltaspike.apache.org Sent: Wednesday, 2 October 2013, 11:04 Subject: CMS diff: Documentation Clone URL (Committers only):

Re: git commit: DELTASPIKE-424 taking into account EntityManagerResolver with a normal scope

From: Romain Manni-Bucau rmannibu...@gmail.com To: dev@deltaspike.apache.org dev@deltaspike.apache.org; Mark Struberg strub...@yahoo.de Sent: Thursday, 10 October 2013, 8:33 Subject: Re: git commit: DELTASPIKE-424 taking into account EntityManagerResolver with a normal

Re: CDI ContextControl - only available in SE mode?

Hi John! Yes, the ContextControl is also designed for being used in JavaEE. This is very helpful if you need to manually for new threads which need CDI setup properly in JavaEE6 or a pure Servlet container based environment. In JavaEE7 you should be able to utilize JSR-236 concurrency utils

[DISCUSS] next release version? 0.6 or 1.0?

Hi! In the last 2 months I did a few conference talks and smaller presentations (OpenBlend, W-JAX, ..) and always got the same questions: it's only a 0.x version, so is it already stable? I don't like to use it in production with 0.x And the actual answer is: well, core, cdictrl, etc are

Re: [DISCUSS] next release version? 0.6 or 1.0?

pm...@redhat.com wrote: FWIW, I definitely prefer we do 1, and indicate clearly in docs and on a table on the website what the maturity of each module is. On 12 Nov 2013, at 14:34, Mark Struberg strub...@yahoo.de wrote: Pete, Gerhard The Problem here

Re: Using @ConfigProperty in an EAR File on JBoss 7 fails

Hi Thomas! This sounds like a bug in ConfigResolver. We should walk up the parent ClassLoader chain like we do in BeanManagerProvider. Please create a JIRA issue for it. LieGrue, strub From: Stemmer Thomas thomas.stem...@cellent.at To:

Re: [DISCUSS] unit-test cdi-control

yup +1 TestNG support would also be handy later. LieGrue, strub From: Thomas Andraschko andraschko.tho...@gmail.com To: dev@deltaspike.apache.org Sent: Monday, 2 December 2013, 11:22 Subject: Re: [DISCUSS] unit-test cdi-control +1 simple and nice

Re: [DISCUSS] unit-test cdi-control

I use it ;P Nah, testNG is really cool if you have a bit of a mixture of pure unit tests with a slight touch of integration testing. groups, parallel executions, shuffled executions, etc. _really_ useful stuff! LieGrue, strub - Original Message - From: Romain Manni-Bucau

Re: Renaming @ViewRef config property?

-0 or a tad lower. Actually value= in annotations shall imo only be used if it is really THE value of the annotation and not just because it's handy to not having to write any xxx= But in the end it's a matter of taste. LieGrue, strub - Original Message - From: Thomas Andraschko

Re: Binary distribution

Hi John! binaries would be cool. We should run them in a profiles. We can tweak the maven-release-plugin section to activate that profile during release. cdi-ctrl is an own part because it's basically not based on deltaspike-core, but something really distinct. The modules are kind of EE

Re: Servlet Module - Do we really need @Web?

The question for me is: are there already known producers for it or is there any spec which introduces this? In that case a custom qualifier is always a good idea imo. Otherwise we would face different behaviour on different containers. They most times behave different... I just would like

Re: JSF - default ClientWindowRenderMode?

@deltaspike.apache.org; Mark Struberg strub...@yahoo.de Sent: Friday, 10 January 2014, 13:58 Subject: Re: JSF - default ClientWindowRenderMode? Ok would be fine for me, too! The script for the LAZY mode will just do: - if window.name == undefined - window.name == windowId - if window.name

Re: JSF - default ClientWindowRenderMode?

Struberg strub...@yahoo.de Cc: dev@deltaspike.apache.org dev@deltaspike.apache.org Sent: Friday, 10 January 2014, 14:18 Subject: Re: JSF - default ClientWindowRenderMode? 2014/1/10 Mark Struberg strub...@yahoo.de Otherwise one could just open the same bookmark URL with the windowId=123

Re: Ideas on ClientWindow handling / refactoring

we probably should do both. LieGrue, strub - Original Message - From: Thomas Andraschko andraschko.tho...@gmail.com To: dev@deltaspike.apache.org dev@deltaspike.apache.org Cc: Sent: Friday, 10 January 2014, 16:56 Subject: Re: Ideas on ClientWindow handling / refactoring

Re: ClientWindow compatibility - Rename post param to javax.faces.ClientWindow?

+1 And personally I think the PF partial submit simply contradicts the spec. Does it work with multiple forms in a page already? To be honest, MyFaces does some similar optimisation afaik. But because it is a JSF container, it can do it in a way to _not_ break the spec. We should rather try

Re: [DISCUSS] DeltaSpike Launch Module

Agree, it sounds good but I'd rather focus on (finnally!) shipping DS-1.0 for now. I'll give it a tough test drive in the next weeks to see what we miss before the milestone. John, you could probably do a draft on github? LieGrue, stru On Friday, 7 February 2014, 6:15, Romain Manni-Bucau

Re: Revisit cdiCtrl module name and how it's inconsistent with test-control?

2014-02-10 11:15 GMT+01:00 Mark Struberg strub...@yahoo.de: Well, cdictrl is released already. Thus I would rather not change it's name. test-control is not yet released. So that would be easier to change. LieGrue, strub On Sunday, 9 February 2014, 20:16, Karl Kildén

Re: Revisit cdiCtrl module name and how it's inconsistent with test-control?

, gerhard 2014-02-10 13:17 GMT+01:00 Thomas Andraschko andraschko.tho...@gmail.com: Can't we change the parent? IMHO renaming isn't a problem if we do it BEFORE 1.0. 2014-02-10 13:07 GMT+01:00 Mark Struberg strub...@yahoo.de: We could rename the module, but I'd rather not move it under

Re: [DISCUSS] next release version? 0.6 or 1.0?

back 2 the topic, please! I'd say we should approach 1.0 NOW. DeltaSpike core and a few other modules is really rock solid already since a year or so. It is also used heavily in production already. There will always be some modules which are not so perfectly mature at times. E.g. if we will

Re: Servlet Module - Do we really need @Web?

I do agree on @Managed not being very expressive. Think about the @ManagedBean disaster in JavaEE itself. 'Managed' is in the same ballpark like 'Class' or 'Object'. Managed by whom and what?  In that case I'd rather go with @DeltaSpike or keep @Web... But I do not care that much about

Re: [DISCUSS] move @Initialized and @Destroyed

+1 LieGrue, strub On Tuesday, 18 February 2014, 13:27, Thomas Andraschko andraschko.tho...@gmail.com wrote: +1 I like such minor improvements and finalize such stuff :) Whats the replacements for @After/BeforeJsfRequest then? 2014-02-18 13:23 GMT+01:00 Gerhard Petracek

Re: NPE on DefaultClientWindow.getWindowId after long period of inactivity

Well, from a CDI perspective this is pretty clear. We take whatever the Session is. Regardless if this is an existing one or a new one. Seems to be a WildFly issue. I'm sure the guys over there can fix this. LieGrue, strub On Sunday, 23 February 2014, 19:37, Thomas Frühbeck

Re: [VOTE] #2 Release of Apache DeltaSpike 0.6

+1 sig fine, rat passes, build runs without errors, all tests pass, hash sums fine, LICENSE and NOTICE files in place and content is fine. txs for running the release! LieGrue, strub On Sunday, 16 March 2014, 18:32, Gerhard Petracek gpetra...@apache.org wrote: Hi, I was running

Re: [DISCUSS] releases

+1 LieGrue, strub On Thursday, 3 April 2014, 16:55, Thomas Andraschko andraschko.tho...@gmail.com wrote: +1 2014-04-03 16:14 GMT+02:00 Rafael Benevides benevi...@redhat.com: +1 I like continuous releases to mitigate risk and it also gives the feeling to the early adopters and users

Re: cdictrl build/test structure

Hi Ron! The reason why cdictrl don't inherit from parent is that it is essentially a different beast. It is not an extension FOR containers, but is IS the part who boots the containers. Means it also has totally different dependencies, etc. That is also the reason why it is not part of the

Re: [VOTE] Release of Apache DeltaSpike 0.7

+1 LieGrue, strub On Thursday, 1 May 2014, 17:12, Cody Lerum cody.le...@gmail.com wrote: +1 builds and tests weld and owb fine on win 8.1 x64 7u51 On Wed, Apr 30, 2014 at 2:22 PM, Gerhard Petracek gpetra...@apache.org wrote: Hi, I was running the needed tasks to get the

[DISCUSS] next release as 1.0?

Hi! Is there ANYTHING which holds us back from moving our version to 1.0? We are long overdue and there are SOOO many companies using DeltaSpike in production since years now... LieGrue, strub

Re: Design help for the logo

Hi Jim! I personally have 2 spontaneous thoughts coming to my mind. The first one is a positive 'spike' in productivity. DeltaSpike really helps you to get your work done far faster. The other one is kind of a 'negative' spike. Like a gorge between two mountains. DeltaSpike helps to glue

Re: 0.7/0.8-SNAPSHOT - Error under WAS 8 - NullPointerException at Application Start in ViewConfigResolverProducer.createViewConfigResolver

Hi Heiko! Side note: You need to distinguish between WAS-8.5.5.x and the liberty profile. They both have similar version numbers but are really different. E.g. WAS uses OWB-1.1.0-snapshot whereas liberty uses OWB-1.1.6. LieGrue, strub On Tuesday, 20 May 2014, 12:10, Gerhard Petracek

Re: AW: 0.7/0.8-SNAPSHOT - Error under WAS 8 - NullPointerException at Application Start in ViewConfigResolverProducer.createViewConfigResolver

guess we have to go back developing with this environment too, otherwise we run into things like this incompatiblities. Greetings, Heiko -- Dr.-Ing. Heiko Kopp -Ursprüngliche Nachricht- Von: Mark Struberg [mailto:strub...@yahoo.de] Gesendet: Dienstag, 20. Mai 2014 12:30 An: dev

Re: DeltaSpike Logo Sketches

I really like the 'Geometric' Maybe round the corners of the background, but that's it We could also use the 'delta' sign as a short logo... LieGrue, strub On Tuesday, 20 May 2014, 17:54, James Parenti ja...@visuale.net wrote: Hello, I’m attaching some logo sketches I made for

Re: [VOTE] logo-shape

9, 5, 8 (in this order) LieGrue, strub On Wednesday, 11 June 2014, 18:55, Gerhard Petracek gpetra...@apache.org wrote: hi @ all, this first vote is just about the basic shape/style and not the color. i've uploaded the candidates provided by jim at [1]. please send a +1 for one (or two)

Re: [VOTE] Release of Apache DeltaSpike 1.0.0

+1 as checked from source.zip: builds fine, rat passes, licenses ok, DEPENDENCIES ok, key ok tag matches source.zip go for it! LieGrue and txs to all who helped making 1.0 real! LieGrue, strub On Saturday, 14 June 2014, 18:01, Gerhard Petracek gpetra...@apache.org wrote: Hi,

Re: Promoting and evangelising DeltaSpike

I did held a few DeltaSpike talks in the past but it is barely possible to cover all features of DeltaSpike in one go.  There was a 1h talk I held at jaxcon in early 2013 (and later at openblend where I did _heavily_ run out of time). 

add our latest release JavaDoc to our home page?

Hi! It is _often_ very useful to point people to the JavaDoc of one of our modules. I'm interested mainly in the API and SPI ones. Does anyone have a pointer to how this is done best? LieGrue, strub

Re: first steps for the next release

+1 LieGrue, strub On Sunday, 6 July 2014, 12:01, Thomas Andraschko andraschko.tho...@gmail.com wrote: +1 2014-07-05 15:41 GMT+02:00 Gerhard Petracek gerhard.petra...@gmail.com: hi @ all, if there are no objections, i will start with the first steps for the next release (v1.0.1) by

Re: DeltaSpike docs plan

afaik doing the CMS via svnpubsub is only for convenience. We could theoretically also generate the html pages somewhere else. But at the end of the day we need to push it to svn to publish it. This is our way to make sure we have all in a proper historic context.  LieGrue, strub On Monday,

cdictrl-servlet breaks cdi-1.1 and 1.2

Hi! cdictrl-servlet directly defines cdi-1.0 artifacts. This breaks Weld-1.2 and OWB-2.x. The whole module is actually pretty weird. It is a submodule of cdictrl but I seems to have not much to do with cdictrl. Instead it even has dependencies to deltaspike-core... How do we proceed? Sorry

Re: cdictrl-servlet breaks cdi-1.1 and 1.2

D. Ament john.d.am...@gmail.com wrote: Hi Mark! On Sat, Aug 23, 2014 at 2:51 PM, Mark Struberg strub...@yahoo.de wrote: Hi! cdictrl-servlet directly defines cdi-1.0 artifacts. This breaks Weld-1.2 and OWB-2.x. Yes, I was thinking that as well.  Probably don't need a dependency on CDI

Re: cdictrl-servlet breaks cdi-1.1 and 1.2

: Mark, Seems like the real issue is that OWB2 doesn't run when CDI 1.0 APIs are on the classpath.  Is that the case here? John On Sun, Aug 24, 2014 at 3:36 AM, Mark Struberg strub...@yahoo.de wrote: Hi John! Was partly an error on my side as I mixed up files from cdictrl-servlet

Re: [VOTE] Release of Apache DeltaSpike 1.0.3

+1 LieGrue, strub On Sunday, 21 September 2014, 20:07, Gerhard Petracek gpetra...@apache.org wrote: Hi, I was running the needed tasks to get the 11th release of Apache DeltaSpike out. The artifacts are deployed to Nexus [1] (and [2]). The tag is available at [3] and will get

Re: Commit messages

Well, this is a general rule and is very important for functional changes. However, like with all rules there are certain exceptions. E.g. I will not create a JIRA ticket for fixing a spelling error in a JavaDoc ;) LieGrue, strub On Wednesday, 1 October 2014, 18:24, John D. Ament

Re: Apache DeltaSpike ViewScoped

Hi Alexandr! Do you like to use @ViewScoped in a CDI way or JSF way? Let me explain: Initially javax.faces.bean.ViewScoped was _not_ a native CDI scope but one from the JSF container. (For JSF Managed Beans you would also need the @ManagedBean annotation. For now I assume that's not what

Re: Cross-Site Scripting (XSS) attack possible by manipulating the dswid request parameter, when using ds:windowId/

Txs for the report Heiko! We already discussed this and Gerhard will post a workaround. Of course we will also fix this in trunk for our upcoming release. LieGrue, strub On Saturday, 25 October 2014, 19:07, it-media.k...@extaccount.com it-media.k...@extaccount.com wrote: Hello, we've

AW: JSF module and ICEfaces fileEntry

div id='yahoo__compose_area' style=background-color:white; display:block; font-family:HelveticaNeue-Regular,Helvetica; font-size:15px;Quick guess:divbr/divdivfont face=Times size=3span style=background-color: rgba(255, 255, 255, 0);The emfileEntry/em component requires that a non-AJAX full

Re: JSF module and ICEfaces fileEntry

... On Sun, Oct 26, 2014 at 4:05 AM, Mark Struberg strub...@yahoo.de wrote: div id='yahoo__compose_area' style=background-color:white; display:block; font-family:HelveticaNeue-Regular,Helvetica; font-size:15px;Quick guess:divbr/divdivfont face=Times size=3span style=background

Re: [VOTE] Release of Apache DeltaSpike 1.1.0

+1 LieGrue, strub On Saturday, 1 November 2014, 21:47, Gerhard Petracek gpetra...@apache.org wrote: Hi, I was running the needed tasks to get the 12th release of Apache DeltaSpike out. The artifacts are deployed to Nexus [1] (and [2]). The tag is available at [3] and will get

Re: WebSphere: Error in deltaspike-jsf-module while stopping application under WAS 8.0.0.9

Heiko, how does your deployable look like? Is this an EAR with multiple WARs in there? LieGrue, strub On Monday, 10 November 2014, 10:27, Gerhard Petracek gerhard.petra...@gmail.com wrote: hi heiko, it sounds like an issue in WAS. there is nothing we can do about that, however,

Re: first steps for the next release

-1 for 1.2.0 and +1 for releasing 1.1.1 The fix in BeanManagerProvider was just a minor lookup to the parent ClassLoader. Most of the time you will not even see that it didn't work as it was really just broken for some scenarios. And only since a short time. So I'd really rather go 1.1.1.

Re: first steps for the next release

Oh in that case +1 for 1.2.0 as well. LieGrue, strub From: Gerhard Petracek gerhard.petra...@gmail.com To: dev@deltaspike.apache.org dev@deltaspike.apache.org; Mark Struberg strub...@yahoo.de Sent: Tuesday, 18 November 2014, 9:55 Subject: Re: first steps

Re: [VOTE] Release of Apache DeltaSpike 1.2.0

+1 LieGrue, strub On Sunday, 30 November 2014, 18:25, Gerhard Petracek gpetra...@apache.org wrote: Hi, I was running the needed tasks to get the 13th release of Apache DeltaSpike out. The artifacts are deployed to Nexus [1] (and [2]). The tag is available at [3] and will get

Re: [VOTE] Release of Apache DeltaSpike 1.2.1

+1 LieGrue, strub On Saturday, 20 December 2014, 23:56, Gerhard Petracek gpetra...@apache.org wrote: Hi, I was running the needed tasks to get the 14th release of Apache DeltaSpike out. The artifacts are deployed to Nexus [1] (and [2]). The tag is available at [3] and will get

[ANNOUNCE] Release of DeltaSpike-1.3.0

The Apache DeltaSpike team is pleased to announce the release of DeltaSpike-1.3.0. Apache DeltaSpike is not a CDI-container, but a portable CDI extension. Documentation: http://deltaspike.apache.org/documentation.html Download: http://deltaspike.apache.org/download.html Release Notes:

Re: [VOTE] [RESULT] Release Apache DeltaSpike-1.3.0

Hi folks! Thanks all for voting! The VOTE has passed with the following +1: Rafael, Jason, Romain, Christian, Gerhard, Thomas, John, Antoine, Mark +0 none -1 none I’ll go on and propagate the artifacts, etc. LieGrue, strub Am 04.03.2015 um 10:08 schrieb Mark Struberg strub...@yahoo.de

Re: [VOTE] Release Apache DeltaSpike-1.3.0

+1 LieGrue, strub Am 04.03.2015 um 10:08 schrieb Mark Struberg strub...@yahoo.de: Hi! I’d like to call a VOTE for the release of DeltasSpike-1.3.0 The staging repo is: https://repository.apache.org/content/repositories/orgapachedeltaspike-1020/ The tag is available here: https

[VOTE] Release Apache DeltaSpike-1.3.0

Hi! I’d like to call a VOTE for the release of DeltasSpike-1.3.0 The staging repo is: https://repository.apache.org/content/repositories/orgapachedeltaspike-1020/ The tag is available here: https://github.com/struberg/deltaspike/tree/deltaspike-root-1.3.0 This will get pushed to the ASF repo

Re: Unify internal configuration

Hi! Sorry for brevity. Like to quickly sum up what we discussed on irc: .) DeltaSpikeConfig is merely a marker interface for interfaces/classes which can be used to define the behaviour of certain DeltaSpike features at runtimy. Since this is a class it can return different values for each

Re: Build failed in Jenkins: DeltaSpike_TomEE_1.7.2 #279

Hi folks! I’ve fixed the broken OWB build. The reason was that TomEE changed the groupId for the openejb stuff from org.apache.openejb/openejb-core to org.apache.tomee/openejb-core, etc. Please note that OWB-1.5.0 is not used in any released OpenEJB/TomEE version and thus we cannot really

Re: [VOTE] Release of Apache DeltaSpike 1.4.1

+1 LieGrue, strub Am 12.06.2015 um 23:23 schrieb Gerhard Petracek gpetra...@apache.org: Hi, I was running the needed tasks to get the 17th release of Apache DeltaSpike out. The artifacts are deployed to Nexus [1] (and [2]). The tag is available at [3] and the release-branch at [4].

Re: [VOTE] Release of Apache DeltaSpike 1.4.0

+1 sigs ok, builds fine, rat ok, license, notice ok And also tested with a few customer projects LieGrue, strub Am 18.05.2015 um 10:50 schrieb Gerhard Petracek gpetra...@apache.org: Hi, I was running the needed tasks to get the 16th release of Apache DeltaSpike out. The artifacts are

Re: [VOTE] Release of Apache DeltaSpike 1.5.0

+1 LieGrue, strub Am 10.08.2015 um 04:02 schrieb Gerhard Petracek gpetra...@apache.org: Hi, I was running the needed tasks to get the 19th release of Apache DeltaSpike out. The artifacts are deployed to Nexus [1] (and [2]). The tag is available at [3] and the release-branch at [4].

Re: [VOTE] Release of Apache DeltaSpike 1.4.2

+1 LieGrue, strub Am 19.07.2015 um 19:11 schrieb Gerhard Petracek gpetra...@apache.org: Hi, I was running the needed tasks to get the 18th release of Apache DeltaSpike out. The artifacts are deployed to Nexus [1] (and [2]). The tag is available at [3] and the release-branch at [4].

Re: Start Request scope manually fro a worker thread(asynchronous thread) in WAS8

Am 16.07.2015 um 20:27 schrieb akm ameh...@ford.com: injectJavaEEResources ouch, this indicates that some non-CDI EE stuff is not set up and you use it in this thread. In that case it might be better to use @javax.ejb.Asynchronous to start this new thread. Please note that you might need

Re: Start Request scope manually fro a worker thread(asynchronous thread) in WAS8

The problem I got when I tried this was that the CDI part was perfectly working. But all the com.ibm.ws.* EJB interceptors you get did blow up because those parts were not set up. Sadly this hits you on more CDI beans than you expect :( As DeltaSpike CdiCtrl was originally the openwebbeans

Re: Start Request scope manually fro a worker thread(asynchronous thread) in WAS8

Think you even need to taken an older version https://svn.apache.org/repos/asf/openwebbeans/tags/openwebbeans-1.0.0/webbeans-test/cditest-owb/src/main/java/org/apache/webbeans/cditest/owb/ Am 10.07.2015 um 14:33 schrieb Mark Struberg strub...@yahoo.de: The problem I got when I tried

Re: [VOTE] Release of Apache DeltaSpike 1.5.2

Hi Marvin! As always: we are happy to get any feedback on how to improve those tests. Please note that this is a PERFECT opportunity to get actively involed in the DeltaSpike community as well. I know that there is some sentiment in big companies when it comes to contributing to OSS projects.

Re: [DISCUSS] EJB container as CDI Extension

? sounds it is already there. >>> >>> >>> Romain Manni-Bucau >>> @rmannibucau <https://twitter.com/rmannibucau> | Blog >>> <http://rmannibucau.wordpress.com> | Github < >> https://github.com/rmannibucau> | >>> LinkedIn <htt

Re: [DISCUSS] EJB container as CDI Extension

s4j.pax.exam2/blob/exam-reactor-4.7.0/containers/pax-exam-container-wildfly90/src/main/java/org/ops4j/pax/exam/wildfly90/WildFly90TestContainer.java >> >> Regards, >> Harald >> >> >> >> Am 11.12.2015 um 19:56 schrieb Mark Struberg: >> >>> Oh,

[DISCUSS] EJB container as CDI Extension

Hi folks! Yesterday I gave a presentation about CDI and testing. It’s still pretty hard and costly to test projects which use EJBs in business projects as Arquillian is not a good fit for those most of the times. And once again the idea popped up that it would be easy to just start a CDI

Re: [DISCUSS] EJB container as CDI Extension

Thanks Harald! I also got in touch with Ken Wills from JBoss and Rafael and I will try to make a cdictrl backend real. LieGrue, strub > Am 11.12.2015 um 19:42 schrieb Harald Wellmann <hwellmann...@gmail.com>: > > Am 11.12.2015 um 13:15 schrieb Mark Struberg: >> Probabl

Re: [DISCUSS] EJB container as CDI Extension

? LieGrue, strub > Am 11.12.2015 um 19:47 schrieb Mark Struberg <strub...@yahoo.de>: > > Thanks Harald! > I also got in touch with Ken Wills from JBoss and Rafael and I will try to > make a cdictrl backend real. > > LieGrue, > strub > > >> Am 11.12.2015 u

Re: deltaspike git commit: DELTASPIKE-1034 ActiveEntityManagerHolder needs to be Serializable

Yes and no ;) Yes, the EntityManager is not Serializable (at least almost never). No, it is not a problem. This class gets used and stored in the TransactionStrategy. And this is @Dependent to the TransactionInterceptor. Which is an interceptor and thus @Dependent (per spec) on the

Re: Regression - DeltaSpike 1.4.2 & Weld 2.3.1?

o fail fast if a bean requires an EE resource > and it's not available. > > Martin > > Dne 18.11.2015 v 22:45 Mark Struberg napsal(a): >> Martin, it seems you missed that the whole Resource section in the CDI spec >> ONLY applies if you run in an EE environme

Re: [VOTE] Release of Apache DeltaSpike 1.7.0

Can someone plz check this version with Weld? [ERROR] mvn -rf :deltaspike-scheduler-module-impl Did blow up both with weld1_1_28 and 1_1_10 LieGrue, strub > Am 13.06.2016 um 14:09 schrieb Antoine Sabot-Durand > : > > +1 > > Le lun. 13 juin 2016 à 13:21, John D.

Re: [VOTE] Release of Apache DeltaSpike 1.7.0

> > On Wed, Jun 15, 2016 at 9:26 AM Matej Novotny <manov...@redhat.com> wrote: > >> @struberg, if you are talking about master branch build, than it works for >> me with Weld 1.x (tried 1.1.28 && 1.1.10). >> >> Just tried it with: mvn clean install -PWeld1 -Dwel

Re: [VOTE] Release of Apache DeltaSpike 1.7.0

; repo) (j/k) >>> >>> @Matej could you apply the fixes in master? If not I can probably get to >>> it late tomorrow. >>> >>> John >>> >>> >>> >>> On Wed, Jun 15, 2016 at 4:46 PM Mark Struberg <strub...@yahoo.de.invalid> >>>

Re: [VOTE] Release of Apache DeltaSpike 1.7.0

; I didn't notice as I run these manually > > > So, cancel and fix? or leave it? > > > John > > On Wed, Jun 15, 2016 at 4:02 PM Mark Struberg <strub...@yahoo.de.invalid> > wrote: > >> No, that’s a separate one. It is not in the cdictrl module but in the >> sch

Re: Cutting over to Java 7

Agree, we don't gain much with moving to Java7. Thus I'd say that we keep Java6/CDI-1.0 and have the next major version bump (aka DeltaSpike-2.x) targeting Java8 and CDI-2.0. But of course keep a ds-1.x maintenance branch even after that for a while. LieGrue, strub > On Thursday, 7

Re: [VOTE] Release of Apache DeltaSpike 1.6.0

Reviewed the source package *) builds fine *) 3 of my bigger project run fine and all tests pass *) rat passes (alttough only mvn rat:rat, mvn apache-rat:rat blows up with mvn-3.3.9; not a DS issue though) *) signature fine *) md5 and sha1 ok +1 LieGrue, strub > On Saturday, 2 April

Re: 1.6 to be the last release to support Java 1.6?

+1 LieGrue, strub > Am 28.03.2016 um 17:39 schrieb Jason Porter : > > +1 > > On Sat, Mar 26, 2016 at 11:36 AM, Harald Wellmann > wrote: > >> +1 >> >> 2016-03-26 17:49 GMT+01:00 Christian Kaltepoth : >> >>> +1 >>> >>>

DeltaSpikeProxyFactory questions

a.)DeltaSpikeProxyFactory totally misses docs it sems. Or did I miss something? b.) there are methods which are imo questionable, e.g. public Class getProxyClass(BeanManager beanManager, Class targetClass) { return getProxyClass(beanManager, targetClass, DummyInvocationHandler.class); } what

Re: DeltaSpikeProxyFactory questions

free to align it :) > > > 2016-05-09 13:30 GMT+02:00 John D. Ament <johndam...@apache.org>: > >> On Mon, May 9, 2016 at 7:24 AM Mark Struberg > <strub...@yahoo.de.invalid> >> wrote: >> >> > a.)DeltaSpikeProxyFactory totally misses docs it

Re: DeltaSpikeProxyFactory questions

te >methods". > > >| Maybe we could introduce a new API which just exposes a native java subclass >proxy to retain backward compat? > >What do you mean exactly? > > > > > > > > >2016-05-09 14:55 GMT+02:00 Mark Struberg <strub...@yahoo.de.invalid>

default value for evaluateProperties in ConfigResolver

Hi! I recently committed a feature to evaluate variables in config values. Basically having something like: - document.server.url=http://localhost:8081 myapp.document.lists=${document.server.url}/docapp/list

Re: default value for evaluateProperties in ConfigResolver

ly play a follow up ticket to this to allow you to configure > the prefix/suffix of your variables as well. > > John > > On Fri, Apr 15, 2016 at 6:31 AM Mark Struberg <strub...@yahoo.de.invalid> > wrote: > Hi! > > I recently commit

Re: default value for evaluateProperties in ConfigResolver

wasn't clear, my comment is that this should be the default > behaviour of the other methods. Maybe not now for backwards compatibility, > but at some point. > > John > > > On Fri, Apr 15, 2016 at 7:11 AM Mark Struberg <strub...@yahoo.de> wrote: > >> It’s not dupl

  1   2   3   4   5   6   7   >