[00:18:21] *** gastaldi has joined #jbosstesting
[00:19:03] *** gastaldi has quit IRC
[00:19:31] *** mhuniewicz has quit IRC
[00:24:11] *** gastaldi has joined #jbosstesting
[00:39:27] *** gastaldi has quit IRC
[01:04:37] *** johnament has joined #jbosstesting
[04:10:05] *** bgeorges has joined #jbosstesting
[04:12:33] *** dblevins has quit IRC
[04:17:40] *** dblevins has joined #jbosstesting
[04:50:09] *** johnament has quit IRC
[06:50:43] *** bgeorges has quit IRC
[07:47:22] *** bgeorges has joined #jbosstesting
[07:58:37] *** bgeorges has quit IRC
[08:06:57] *** jharting has joined #jbosstesting
[08:22:32] *** galderz has joined #jbosstesting
[08:30:23] *** aaronwalker has joined #jbosstesting
[08:31:12] *** ge0ffrey has joined #jbosstesting
[08:42:41] *** tdiesler has joined #jbosstesting
[08:46:42] *** maschmid has joined #jbosstesting
[09:09:34] *** mgoldmann has joined #jbosstesting
[09:13:39] *** oskutka has joined #jbosstesting
[09:14:33] *** pil-gone has quit IRC
[09:38:49] *** jeand has joined #jbosstesting
[09:48:54] *** aslak has joined #jbosstesting
[09:48:54] *** aslak has quit IRC
[09:48:54] *** aslak has joined #jbosstesting
[09:52:29] *** maeste has joined #jbosstesting
[10:10:07] *** aaronwalker has quit IRC
[10:22:28] *** pilhuhn has joined #jbosstesting
[10:22:28] *** pilhuhn has joined #jbosstesting
[10:39:28] *** aslak has quit IRC
[10:39:28] *** jharting has quit IRC
[10:42:17] *** torben has joined #jbosstesting
[10:42:17] *** torben has joined #jbosstesting
[10:45:49] *** aslak has joined #jbosstesting
[10:48:01] *** jharting has joined #jbosstesting
[11:32:37] *** aaronwalker has joined #jbosstesting
[12:13:42] *** galderz has quit IRC
[12:44:26] <jharting> ping aslak
[12:58:01] *** aslak has quit IRC
[13:14:26] *** oskutka has quit IRC
[13:20:40] *** aaronwalker has quit IRC
[13:21:40] *** aaronwalker has joined #jbosstesting
[13:27:38] *** galderz has joined #jbosstesting
[13:43:31] *** jose_freitas_aw has joined #jbosstesting
[13:43:38] *** jose_freitas_aw is now known as jose_freitas
[14:17:49] *** jose_freitas_aw has joined #jbosstesting
[14:19:49] *** jose_freitas has quit IRC
[14:34:49] *** jose_freitas_aw has quit IRC
[14:35:09] *** jose_freitas_aw has joined #jbosstesting
[14:41:48] *** torben has quit IRC
[14:42:31] *** torben has joined #jbosstesting
[14:42:31] *** torben has joined #jbosstesting
[14:47:35] *** jose_freitas has joined #jbosstesting
[14:49:13] *** jose_freitas_aw has quit IRC
[15:48:44] *** mgoldmann has quit IRC
[15:56:46] *** mgoldmann has joined #jbosstesting
[16:06:32] *** htfv has joined #jbosstesting
[16:17:09] *** jharting has quit IRC
[16:44:18] *** mgoldmann has quit IRC
[16:54:40] *** maschmid has quit IRC
[17:22:35] *** mgoldmann has joined #jbosstesting
[17:23:53] *** bgeorges has joined #jbosstesting
[17:30:23] *** mgoldmann has quit IRC
[17:48:51] *** tdiesler has quit IRC
[18:12:23] *** bgeorges has quit IRC
[18:13:33] *** Tashtego has joined #jbosstesting
[18:14:58] *** oskutka has joined #jbosstesting
[18:19:47] *** Tashtego has quit IRC
[18:19:58] *** Tashtego has joined #jbosstesting
[18:19:59] *** Tashtego has left #jbosstesting
[18:20:14] *** Tashtego has joined #jbosstesting
[18:25:06] *** torben has quit IRC
[18:26:17] *** galderz has quit IRC
[18:42:44] *** oskutka has quit IRC
[19:47:06] *** gastaldi has joined #jbosstesting
[19:47:44] *** bobmcw_ has joined #jbosstesting
[19:48:28] *** bobmcw has quit IRC
[19:48:35] <gastaldi> hey
[19:48:45] <gastaldi> Where is the github repo for jBoss Tools ?
[19:57:29] *** danielcmm-BR has joined #jbosstesting
[20:13:04] *** galderz has joined #jbosstesting
[20:35:53] *** OndraZizka has joined #jbosstesting
[20:36:35] <danielcmm-BR> how can i programatically activate the conversation scope in Java EE? ;(
[20:41:42] <gastaldi> @Inject Conversation conversation;
[20:41:50] <gastaldi> conversation.begin() ?
[20:56:55] <danielcmm-BR> Thankssss :)
[21:01:50] *** mhuniewicz has joined #jbosstesting
[21:06:00] <danielcmm-BR> In seam 2, i was able to access the conversation variables with Contexts.getConversationContext().... How can i do it using java 1.6 CDI?
[21:15:58] *** aslak has joined #jbosstesting
[21:20:18] <mhuniewicz> Hi @aslak, got a sec?
[21:20:46] <aslak> mhuniewicz, hey, sure
[21:21:23] <mhuniewicz> I talked to Dan Allen about contributing to Arquillian.
[21:21:32] <mhuniewicz> He told me to ask you.
[21:21:53] <aslak> aa goodie.. :)
[21:22:01] <aslak> mhuniewicz, any specific area?
[21:22:34] <mhuniewicz> CDI I guess. Not sure if my answer makes a lot of sense.
[21:23:13] <mhuniewicz> It all started with my inability to inject @PersstenceContext without having an AS running.
[21:26:15] <aslak> mhuniewicz, mm, your thinking extending on the Weld EE Mock container, where you can configure out own EE integration layer, e.g. PersistenceContextFactory etc ?
[21:26:27] <aslak> out/your
[21:28:14] <mhuniewicz> That's possible - I'm not sure whether this is Weld EE Mock container, never looked into it in such detail, to be honest with you.
[21:31:42] <aslak> aa, well.. Without a AS running, you will have to go down a level, to e.g. the pure Bean CDI Containers, alla Weld.
[21:33:04] <mhuniewicz> That's fine, I like the project and was wondering if I can help. It doesn't have to be that specific thing although it would help me with my project.
[21:33:05] <aslak> there is a Weld container integration for Arquillian called EE Mock, where you can inject PersistenceContext, but it will be a crude Mocked version of it not doing anything useful
[21:33:32] <aslak> mhuniewicz, similar things have been requested before..
[21:34:39] <mhuniewicz> I see.
[21:36:38] <mhuniewicz> Well, anything I can help with, then?
[21:37:51] <aslak> mhuniewicz, we do have another open issue that could be quite interesting, cdi related..
[21:38:33] <mhuniewicz> I'm all ears.
[21:38:40] <aslak> ARQ-337
[21:38:41] <jbossbot> jira [ARQ-337] Create a Context/Scope activation/deactivation abstraction for CDI [Open (Unresolved) Feature Request, Major, Paul Bakker] https://issues.jboss.org/browse/ARQ-337
[21:42:15] *** galderz has quit IRC
[21:43:16] <mhuniewicz> Alright.
[21:43:33] <aslak> mhuniewicz, you get the gist of it?
[21:43:35] <aslak> :)
[21:44:08] <aslak> mhuniewicz, i can find something not so complicated to start you of if you want.. :)
[21:44:08] <mhuniewicz> I think I get it. ;)
[21:44:50] <mhuniewicz> This one is fine, but I might be asking lots of questions to make sure I'm doing the right thing.
[21:54:05] <aslak> mhuniewicz, sure, i'm expecting you to.. :)
[21:54:20] <mhuniewicz> Coolio. :)
[21:54:39] <aslak> mhuniewicz, i'm not sure my self.. but we need it so.. we just need to figure out how :)
[21:55:08] <mhuniewicz> How do I get started?
[21:56:34] <aslak> mhuniewicz, i would start by just drafting some API. how should this look from the Users perspective. then consider the SPI side, how should it look from the Container(Weld, AS etc ) integration side
[21:57:20] <mhuniewicz> So there are no failing unit tests for it or anything?
[21:57:46] <aslak> mhuniewicz, nope, this is from scratch
[21:58:22] <aslak> mhuniewicz, https://github.com/arquillian/arquillian-core
[21:58:41] <mhuniewicz> Cheers.
[21:58:50] <aslak>  /testenrichers/cdi might be where it should be
[22:01:41] *** gastaldi has left #jbosstesting
[22:01:46] *** gastaldi has quit IRC
[22:01:52] <mhuniewicz> Cloned, here it is.
[22:02:12] *** Tashtego has quit IRC
[22:06:54] *** torben has joined #jbosstesting
[22:06:54] *** torben has joined #jbosstesting
[22:07:49] *** ge0ffrey has quit IRC
[22:08:56] <mhuniewicz> aslak, should we keep on talking here? I don't wanna spam everyone. ;)
[22:10:44] <aslak> mhuniewicz, oh, your not spamming.. that's why the chan is here.. :)
[22:11:12] <aslak> mhuniewicz, you might want to put the api / spi proposals up on the dev forum http://community.jboss.org/en/arquillian/dev
[22:11:23] <mhuniewicz> Okay.
[22:11:27] <aslak> makes it a bit easier for async communication acorss time zones etc.. )
[22:11:35] <mhuniewicz> Well, for now Eclipse's giving me countless (96) Maven errors.
[22:11:42] <mhuniewicz> Some libs I need to install manually?
[22:11:54] <aslak> probably 1.5 vs 1.6 target
[22:12:10] <aslak> you can update /pom.xml source/target version and reimport
[22:12:21] <mhuniewicz> Are we on 1.6?
[22:12:35] <aslak> or manually change all the modules
[22:13:08] <aslak> we should be complient with 1.5, so we compile with target 1.5, but we use 1.6 source feature (@Override of interface methods)
[22:13:32] <mhuniewicz> Well I'm getting stuff like this:
[22:13:34] <mhuniewicz> Missing artifact org.jboss.shrinkwrap.descriptors:shrinkwrap-descriptors-api:jar:1.0.0-beta-1:compile
[22:14:14] <aslak> mhuniewicz, they should be in the jboss nexus repo
[22:14:26] <aslak> not currently defined in the poms them self
[22:14:56] <mhuniewicz> settings.xml?
[22:15:02] <aslak> i have them there
[22:16:19] <aslak> mhuniewicz, i have this in my settings.xml https://gist.github.com/1063876
[22:16:41] *** mgoldmann has joined #jbosstesting
[22:20:36] *** pilhuhn is now known as pil-afk
[22:31:14] <mhuniewicz> Why would you want to deactivate a scope?
[22:32:33] *** Tashtego has joined #jbosstesting
[22:32:45] <Tashtego> "Process fork failed." does anyone know about this error?
[22:35:13] <aslak> Tashtego, windows?
[22:36:08] <aslak> mhuniewicz, cuz you want to control when things start and stop basically
[22:37:05] <mhuniewicz> aslak, what would be a real life example?
[22:38:06] <aslak> mhuniewicz, e.g. a Conversation Scoped bean, start and stop the scope to see that it passivates correctly
[22:38:36] <aslak> the need here might be stronger form the CDI impl / extension developers then for the CDI users
[22:39:17] <mhuniewicz> What does this mean: "possible we could do something like @Scopes(Request, Session) @Test as a 'around invoke style, but that is a abstraction over the ContextController that would be step 3/4 or so"?
[22:41:36] <aslak> mhuniewicz, you know CDI scopes right ?
[22:41:41] <mhuniewicz> Yes.
[22:42:04] <aslak> so, we want to control the activation and deactivation of the different scopes via a common api between the different containers
[22:42:16] <aslak> since this is pr now atleast not part of the spec, but vendor specific
[22:42:36] *** mgoldmann has quit IRC
[22:42:44] <aslak> So, ContextController(? to name) could be entry point to control the Contexts.
[22:43:01] <mhuniewicz> So I do
[22:43:02] <aslak> e.g. ContextController.activate(RequestScope.class)
[22:43:04] <mhuniewicz> @Inject
[22:43:11] <mhuniewicz> ContextController contextController;
[22:43:15] <mhuniewicz> and then in my test
[22:43:30] <mhuniewicz> contextController.activate(ConversationScope.class);
[22:43:37] <aslak> exactly
[22:43:41] <mhuniewicz> something
[22:43:46] <Tashtego> yes windows
[22:43:51] <aslak> but in 90% of the usecases, that all becomes a bit cumbersum
[22:43:51] <mhuniewicz> ... .deactivate(ConversationScope.class);
[22:44:06] <Tashtego> i did a clean install and wanted to try several configuration examples with arquillian for documentation reason
[22:44:18] <Tashtego> started again with the docu on the page
[22:44:27] <Tashtego> http://docs.jboss.org/arquillian/reference/latest/en-US/html/gettingstarted.html
[22:44:40] <aslak> mhuniewicz, you don't need that fine grain control. so we can make 'shortcut' hooks to e.g. add a Annotation to the @Test method to say, when this run, i want Request and Session scope to be active
[22:44:41] <Tashtego> but cant get the first example running
[22:45:15] <aslak> e.g. @Test @Scopes(Request.class, Session.class) public void shouldBeAbleTo... () {}
[22:45:47] <mhuniewicz> Does that mean that for this test method scopes Request and Session are active?
[22:45:58] <aslak> yea
[22:46:15] <mhuniewicz> But still, finer grained control is available?
[22:46:32] <aslak> maybe not when you have those, but as a alternative
[22:46:48] <aslak> mhuniewicz, well it doesn
[22:46:58] <aslak> mhuniewicz, well it doesn't do this now.. that's what your working on.. ehe :)
[22:47:06] <mhuniewicz> How does it work now, exactly? Are all scopes available?
[22:47:17] <Tashtego> http://pastebin.com/vUHyPTcS
[22:48:30] <aslak> Tashtego, sounds like your dumping into the 256 char classpath limit, try this one: http://community.jboss.org/en/arquillian/blog/2011/04/05/trim-your-dependencies-when-using-jboss-as-6-remote
[22:49:27] <aslak> mhuniewicz, the Container (weld, openwebbeans etc) provide the EE scopes, request session, conversation, application, then the spec talks about custom scopes which anyone can add, FlashScope, ThreadScope etc are few 'known'
[22:50:32] <mhuniewicz> I mean, if I run a test with Arquillian enabled, all scopes come into play, don't they?
[22:50:44] <aslak> mhuniewicz, in the current weld + ee containers, you have Session Scope from Before til After, and Request inside Test if i remember
[22:51:03] <aslak> Application is Over the whole Class
[22:52:30] <aslak> mhuniewicz, https://github.com/arquillian/arquillian-container-weld/blob/master/weld-ee-embedded-1.1/src/main/java/org/jboss/arquillian/container/weld/ee/embedded_1_1/LifecycleHandler.java
[22:52:58] <aslak> Session around the whole Class and Request from Before -> After
[22:53:35] <Tashtego> arrrrrrrrrrrrr
[22:54:20] <Tashtego> i hate the it business. i hate my life. what a waste of time. i hate computers and i have java arrrrr
[22:54:21] <Tashtego> whatever
[22:54:34] <Tashtego> i want to get some sleep :(
[22:54:56] <aslak> Tashtego, hehe
[22:55:12] <Tashtego> i mean it!
[22:55:13] <Tashtego> arr
[22:55:24] <Tashtego> why the hell is NOTHING ever working out of the box
[22:55:25] <Tashtego> EVER?
[22:55:35] <Tashtego> i am going to buy a playstation
[22:56:10] <Tashtego> your dependency change isnt working anyways
[22:56:39] <aslak> Tashtego, do you have a complete stack trace or error?
[22:56:42] <Tashtego> the docu is wrong. the examples arent running
[22:56:52] <Tashtego> package javax.ejb does not exist
[22:57:05] <Tashtego> i have all dependencies that are mentioned in the docu
[22:57:18] <Tashtego> guess its the javaee6 dep missing or s.th
[22:57:57] <aslak> Tashtego, which doc you on?
[22:58:13] <Tashtego> deleted my example ejbs now. only example left now is temparatureconverter
[22:58:20] <Tashtego> the absolute basic getting started docu
[22:58:32] <Tashtego> Could not read active container configuration: null
[22:58:33] <aslak> Tashtego, it doesn't use @EJB
[22:58:36] <Tashtego> i know
[22:58:40] <Tashtego> i just deleted another bean
[22:58:41] <aslak> Tashtego, just a info log
[22:58:43] <Tashtego> i had in this example
[22:58:48] <Tashtego> so now there is no ejb anymore
[22:59:09] <Tashtego> Could not read active container configuration: null is what i get actually after deleting
[22:59:19] <Tashtego> and before  the next one will come along.
[22:59:33] <Tashtego> i just wanted some embedded ejb examples with the actual arquillian
[22:59:41] <aslak> means it's starting up.. just a bad message.. it's not a error.. basically telling you that you did not specify anything, so arq will default
[22:59:42] <Tashtego> seems i got a bad day
[23:00:14] <Tashtego> Could not connect to container
[23:00:14] <Tashtego> org.jboss.arquillian.spi.client.container.LifecycleException: Could not connect to container
[23:00:23] <aslak> cause ?
[23:00:41] <Tashtego> ah k i think thats becuase its not the embedded variant
[23:00:45] <Tashtego> and jboss is down
[23:00:48] <aslak> yea
[23:00:51] <aslak> most likly
[23:01:16] <Tashtego> man i didnt get sleep for some days now... really need holidays
[23:01:35] <aslak> hot in germany ?
[23:01:56] <Tashtego> the last days it was just raining. and yesterday i was standing all day in the f*** rain
[23:02:01] <Tashtego> had to help my dad out
[23:02:14] <Tashtego> ok got the first test running now
[23:02:23] <Tashtego> will try switching to embedded mode and ejbs
[23:02:59] <Tashtego> aslak we both need to switch brains. well ...mayybe switch our whole lifes ^^...
[23:03:19] <aslak> my wife is American, so we went down town to celebrate 4. july earlier today. but we couldn't find it. then we found out it was yesterday they celebrated 4.july in oslo, due to it being a day off etc.. so, quite lonely.. :)
[23:03:59] <Tashtego> ^^....
[23:04:11] <Tashtego> why the hell should you have more luck than me ;) ...
[23:04:16] <aslak> :)
[23:04:29] <Tashtego> but hey you got a wife... give her some nice greetings from germany ;)
[23:04:30] <Tashtego> ^^
[23:04:48] <aslak> then we figured we'd go to this Thai restaurant on the other side of town for dinner, but when we came there, they had closed down and moved
[23:04:49] <aslak> hehe
[23:05:18] <Tashtego> ;) ... aslak you sure we both arent brothers?? ^^... no relationship ? ;)
[23:05:24] <Tashtego> sounds like my life story
[23:06:23] <aslak> hehe
[23:07:00] <aslak> btw, before we choose Thai, we went Tapas, but it was closed on Mondays.. hehe
[23:07:35] <Tashtego> how did your wife react over all of this? ;)
[23:08:16] <aslak> tired.. :)
[23:10:18] <mhuniewicz> aslak, do we handle anything other than Request, Scope and Conversation now?
[23:16:18] <aslak> mhuniewicz, session
[23:16:26] <aslak> mhuniewicz, application
[23:16:31] <mhuniewicz> Sorry, Session, not Scope.
[23:17:09] *** jeand has quit IRC
[23:17:09] <aslak> mhuniewicz, application is handled internally in the cdi impl
[23:17:43] <mhuniewicz> I'm looking at LifecycleHandler. Where to look for application?
[23:18:09] <aslak> mhuniewicz, i'll check with Pete if there are any plans for a cdi api for context activation/deactivation for CDi 1.1. spec
[23:18:45] <aslak> mhuniewicz, inside WeldManager somewhere if i remember correctly..
[23:19:25] <aslak> or TestContainer
[23:19:50] <mhuniewicz> Is this - so to speak - user story broken into tasks somehow?
[23:20:11] <aslak> this being?
[23:20:23] <mhuniewicz> ARQ-337.
[23:20:25] <jbossbot> jira [ARQ-337] Create a Context/Scope activation/deactivation abstraction for CDI [Open (Unresolved) Feature Request, Major, Paul Bakker] https://issues.jboss.org/browse/ARQ-337
[23:20:48] <aslak> mhuniewicz, nope, be my guest to break it up into sub tasks / user stores if you want
[23:23:58] <mhuniewicz> I think we should decide what we want first.
[23:24:17] <mhuniewicz> Or maybe that's not how it works?
[23:25:58] *** maeste has quit IRC
[23:27:19] <danielcmm-BR> Any1 knows why i keep getting "No org.jboss.shrinkwrap.api.Archive found in context" with weld ee embedded + arquillian?
[23:27:53] <aslak> mhuniewicz, how ever you are comfortable working. there are really no big processes we follow. as long as communication is open and ppl can follow / are included, it's all good
[23:28:44] <aslak> danielcmm-BR, look further up in the exception log. it's probably failing creating the archive for some reason, then later failing cause it can't find it
[23:28:55] <mhuniewicz> aslak, don't you think that since right now all scopes are enabled by default one way or the other, we'd need @DisableScopes rather than @Scopes?
[23:30:14] <aslak> mhuniewicz, hmm.. good point
[23:30:39] <aslak> mhuniewicz, well, that can be a configuration option on a higher level, e.g. container. enableManualScopeControl or similar
[23:31:18] <mhuniewicz> I like the notion of minimal configuration that just works.
[23:32:27] <aslak> mhuniewicz, we could still need @Scopes tho. for Custom scopes that are not handled by default now
[23:32:37] <mhuniewicz> True.
[23:32:38] <aslak> could/would
[23:32:57] <mhuniewicz> I still kinda don't see why I
[23:33:04] <mhuniewicz> 'd disable Request scope or something.
[23:33:33] <mhuniewicz> Unless to prevent stuff from loading?
[23:33:34] <aslak> @PreDestroy
[23:35:44] <aslak> or you want to make sure something work without Session Scope, e.g. EJB don't have that scope
[23:36:28] <mhuniewicz> Okay, that I understand. To annotate test methods with @DisableScopes.
[23:36:42] <mhuniewicz> Or the test class.
[23:36:53] <mhuniewicz> If we have @DisableScopes for test classes,
[23:37:11] <mhuniewicz> then we might provide @EnableScopes for methods to overwrite the class setting.
[23:37:16] <mhuniewicz> (And the other way round)
[23:38:36] <aslak> mhuniewicz, mm, that's a start
[23:38:53] <aslak> mhuniewicz, i would assume the guys in #seam has a few usecases.. :)
[23:39:02] <aslak> sorry, #seam-dev
[23:40:00] <mhuniewicz> Such as
[23:40:01] <mhuniewicz> ?
[23:40:28] <aslak> mhuniewicz, i'm not sure.. talk to them :) they are the biggest CDi consumers
[23:40:52] <mhuniewicz> How about the guy who originally requested this feature?
[23:42:37] <aslak> mhuniewicz, hehe, if i only remembered who that was. i'm pretty sure it came out of the #seam-dev | #weld-dev guys originally
[23:42:58] <mhuniewicz> How about Paul Bakker?
[23:45:42] <aslak> mhuniewicz, Paul started working on it, but i think he dropped it. at lest not heard anything from him on it for a while
[23:46:06] <mhuniewicz> Maybe he died trying to think of a use case. ;)
[23:46:44] <mhuniewicz> So anyhow, the things we've come up so far,
[23:46:49] <mhuniewicz> should I put in on that discussion page?
[23:47:22] <aslak> mhuniewicz, sure
[23:48:34] <mhuniewicz> And in terms of @PersistenceContext, you said there were requests?
[23:49:25] <aslak> mhuniewicz, seems like this might be taken care of by the spec itself in 1.1, ee7..  CDI-29 CDI-30
[23:49:26] <jbossbot> jira [CDI-29] Method of accessing contexts regardless of active state [Open (Unresolved) Feature Request, Major, Unassigned] https://issues.jboss.org/browse/CDI-29
[23:49:27] <jbossbot> jira [CDI-30] An API for managing built in contexts [Open (Unresolved) Feature Request, Major, Unassigned] https://issues.jboss.org/browse/CDI-30
[23:51:34] <mhuniewicz> The thing is,
[23:51:37] *** torben has quit IRC
[23:51:47] <mhuniewicz> with Spring it just works. You provide the annotation and it just works.
[23:52:01] <mhuniewicz> So I checked the vanilla JEE project by Adam Bien.
[23:52:04] <mhuniewicz> I think it's called XRay.
[23:52:35] <mhuniewicz> And what he does is he exposes the @PersistenceContext annotated field by giving in default visibility.
[23:52:56] <mhuniewicz> And then in the test he just assigns this field programatically.
[23:53:27] <mhuniewicz> Like that:
[23:53:33] <mhuniewicz> EntityManagerFactory emf = Persistence.createEntityManagerFactory("integration");
[23:53:37] <mhuniewicz> em = emf.createEntityManager();
[23:53:49] <mhuniewicz> Where em is the @PersistenceContext annotated field.
[23:54:04] <aslak> mhuniewicz, that's possible
[23:54:24] <mhuniewicz> That's all there is to it,
[23:54:29] <mhuniewicz> that's what I was initially looking for,
[23:54:44] <mhuniewicz> but the example by Dan employs an application server and all this full blown thing,
[23:54:55] <mhuniewicz> whereas I thought might be really simple.
[23:55:00] <mhuniewicz> But there could be something I don't know.
[23:55:07] <aslak> mhuniewicz, you can do that
[23:55:33] <danielcmm-BR> aslak, do u know why im getting "org/jboss/weld/bootstrap/spi/BeansXml" now?
[23:55:39] <aslak> nothing stopping you from @Inject MyBean bean; bean.setEM(createem())
[23:56:02] <danielcmm-BR> to be more specific: "java.lang.NoSuchMethodError: org.jboss.weld.bootstrap.api.Bootstrap.parse(Ljava/lang/Iterable;)Lorg/jboss/weld/bootstrap/spi/BeansXml;"
[23:56:15] <aslak> danielcmm-BR, which Weld v. and which weld container you using?
[23:56:16] <mhuniewicz> Well what's stopping me is that I don't want to expose that thing because I think that unnecessary modifications to the code just to make tests work are evil.
[23:56:31] <aslak> mhuniewicz, exactly
[23:56:32] <aslak> :)
[23:56:48] <mhuniewicz> So what do you think about it?
[23:56:49] <aslak> and.. your not really testing the same
[23:57:17] <aslak> cuz it's not managed by the container anymore
[23:57:23] <danielcmm-BR> aslak, weld-ee-embedded-1.1 container and arquillian 1.0.0.Alpha4. Weld v. 1.1.0.Final
[23:57:27] <mhuniewicz> No.
[23:57:57] <aslak> danielcmm-BR, hmm
[23:58:15] <mhuniewicz> So I don't know how much sense I'm making, aslak. :)





top