[01:42:39] *** michaelschuetz has quit IRC
[02:31:49] *** aslak has quit IRC
[04:35:21] *** bleathem has joined #jbosstesting
[04:43:49] *** bleathem has quit IRC
[04:50:38] *** stuartdouglas has quit IRC
[04:51:12] *** stuartdouglas has joined #jbosstesting
[06:25:44] *** lightguard_jp has joined #jbosstesting
[10:14:54] *** lightguard_jp has quit IRC
[11:30:58] *** jdewinne has joined #jbosstesting
[11:31:07] *** jdewinne has left #jbosstesting
[12:47:19] *** aslak has joined #jbosstesting
[14:07:22] *** jganoff has joined #jbosstesting
[14:26:04] <jganoff> aslak, ping
[15:26:04] <aslak> jganoff, heya
[15:26:17] <jganoff> hiya!
[15:26:20] <jganoff> Happy New Year
[15:26:31] <aslak> happy new year! :)
[15:28:09] <jganoff> So I'm resuming my work trying to test seam-jms and I'm attempting to deploy an ear with some jms destinations and an ejb jar with my tests (CDI enabled)
[15:29:05] <jganoff> Since you said there weren't any known issues deploying ear applications with embedded ejb3.1 jars in JBoss AS 6 and Arq Alpha 4 I took a step back to see if I could deploy a simple test.  That failed.  Maybe I'm doing something wrong but the usecase is pretty simple.
[15:29:46] <jganoff> Check this out: http://pastebin.com/bNfAwtZb
[15:30:08] <jganoff> that works when deployed as an EJB jar but not if I package the jar into an ear.
[15:30:55] <jganoff> When deployed as an ear CDI doesn't properly fulfil the injections
[15:31:57] <aslak> aa, right.. your probably hitting the hierarchy bean manager issue
[15:31:58] <jganoff> Here's the relevant logging: http://pastebin.com/cZ1yJWNF
[15:32:40] <jganoff> Ahhh, ok.  Glad to know this is a known issue, know the JIRA case?
[15:32:47] <aslak> the arq protocol war is not enriched with beans.xml, so a BeanManager is not exposed to the wars Context, even tho your EJB-Jar has one
[15:33:21] <jganoff> Ahh, so what's the actual deployale that's sent over?
[15:33:26] <jganoff> a war that wraps my deployment?
[15:33:42] <aslak> jganoff, in the Jar version yes, in the ear a war is added to the ear
[15:34:24] <aslak> when deploying ejbs in a war, they are all the same module, so a BeanManager is exposed for 'both', but not in a ear
[15:34:52] <jganoff> aslak, Gotcha.
[15:35:13] <jganoff> aslak, Thanks! I'll package this up as a war instead.  Hopefully I can deploy jms descriptors in a war in JBoss AS 6
[15:35:23] <jganoff> if I could just get that to work I'd be in business!
[15:37:23] <jganoff> aslak, so, when creating the deployment, should I place the tests directly in the war or leave them in the jar (added as a library) ?
[15:42:16] <jganoff> Seems like either works - is there a commonly accepted place to put them?
[15:43:56] <aslak> good question
[15:44:19] <aslak> with a war, they will be on the same classpath anyway, so it doesn't really matter i think
[15:57:25] <aslak> jganoff, i though we had one, but.. seems it was only reported for WELD, created ARQ-349
[15:57:27] <jbossbot> jira [ARQ-349] Create a Protocol processor SPI for modifying the Protocol create final deployment [Open, Major, Unassigned] https://issues.jboss.org/browse/ARQ-349
[15:58:01] <jganoff> aslak, awesome, thanks1
[15:58:02] <jganoff> !
[17:27:07] *** pmuir has joined #jbosstesting
[18:06:55] *** pmuir has quit IRC
[19:41:03] *** jganoff has quit IRC
[20:28:03] *** bobmcw has quit IRC
[20:28:21] *** bobmcw has joined #jbosstesting
[20:44:49] *** jc3 has joined #jbosstesting
[20:59:22] *** bobmcw has quit IRC
[21:11:54] *** pmuir has joined #jbosstesting
[21:11:55] *** pmuir has quit IRC
[21:11:55] *** pmuir has joined #jbosstesting
[21:23:05] *** jc3 has quit IRC
[22:22:05] *** michaelschuetz has joined #jbosstesting
[22:27:56] *** pmuir has quit IRC
[23:01:37] *** amitev has quit IRC
[23:01:47] *** amitev has joined #jbosstesting
[23:48:08] *** michaelschuetz has quit IRC
[23:49:15] *** michaelschuetz has joined #jbosstesting





top