Re: [DISCUSS] EJB container as CDI Extension

Hi Mark, Although i'm not an expert in the area I'm also interested in this, if I could help some how (e.g write deltaspike example tests using the new integration) just let me know. 2015-12-11 17:25 GMT-02:00 Harald Wellmann : > I'm afraid I won't have a lot of spare

Re: [DISCUSS] EJB container as CDI Extension

Sure, thanks! And thanks Harald, totally understand. Next step will be to check what parts we can reuse from JBoss. Rafael Benevides is working on that. LieGrue, strub > Am 13.12.2015 um 13:42 schrieb Rafael Pestano : > > Hi Mark, > > Although i'm not an expert in the

Re: [DISCUSS] EJB container as CDI Extension

why not using openejb then? sounds it is already there. Romain Manni-Bucau @rmannibucau | Blog | Github | LinkedIn | Tomitriber

Re: [DISCUSS] EJB container as CDI Extension

hi @ all, i agree with romain - with deltaspike-cdictrl-openejb (+ CdiTestRunner) it's easy to do that (see e.g. [1]). regards, gerhard [1] https://github.com/os890/ee6-ds-demo 2015-12-11 10:38 GMT+01:00 Romain Manni-Bucau : > why not using openejb then? sounds it is

Re: [DISCUSS] EJB container as CDI Extension

JBoss should have EJBContainer as well. That said how the initial proposal - reimplementing if I understood - solves the JBoss users need better than using openejb? Romain Manni-Bucau @rmannibucau | Blog | Github

Re: [DISCUSS] EJB container as CDI Extension

hi mark, imo the chance that you create useful tests with openejb is way higher (independent of the server used for the real application). what you suggest is what we used several years ago. (back then there was nothing like deltaspike-cdictrl-openejb + CdiTestRunner -> back then it was way

Re: [DISCUSS] EJB container as CDI Extension

I agree and had the same arguments. Especially as Weld-embedded behaves totally different than Wildfly when it comes to BDAs. And this is actually the main functional difference between Weld and OWB used in OpenEJB. In that regard it btw also doesn’t help to test with Arquillian in my

[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

I'm afraid I won't have a lot of spare time for coding before Christmas, and I'm not much of an authority on WildFly Embedded either, I'm just using it a lot (via Pax Exam) for most integration tests of my daytime projects. Have a look at [1] for the Pax Exam WildFly Container - if there are

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 : > > Am 11.12.2015 um 13:15 schrieb Mark Struberg: >> Probably because JBoss STILL

Re: [DISCUSS] EJB container as CDI Extension

Oh, when I think about it… Would you have an hour to hack this? We could also do a hangout session and kind of pair programming with you Rafael and I (and whoever likes to join). The problem we face at the moment is that the code we got pointed to by the wildfly team is obviously LGPL. So we

Re: [DISCUSS] EJB container as CDI Extension

Am 11.12.2015 um 13:15 schrieb Mark Struberg: Probably because JBoss STILL don’t support an embedded version of wildfly? There *is* an embedded version of WildFly: org.wildfly.core.embedded.EmbeddedServerFactory. This is used e.g. by the Pax Exam WildFly test container, another method to