[00:00:00] <jose_freitas> 2) is that I cant catch exceptions unless I fire them manually
[00:00:00] <sbryzak> mojavelinux: great, we also need some GWT examples too
[00:00:01] <mojavelinux> and I've gotta say, wicket and cdi are made for each other
[00:00:23] <jose_freitas> 3) the inject of inputField within the validator in seam-faces dont work
[00:00:23] <mojavelinux> gwt and cdi as well...both combos have a similar unity
[00:00:31] <mojavelinux> and one that is decidely absent from jsf
[00:00:32] <jose_freitas> it does find the component on the uitree though
[00:00:53] <mojavelinux> hmm, that is likely a bug in Seam Faces...of course, that is another thing that's supposed to be fixed
[00:00:54] <sbryzak> we really need to start incorporating Errai into some of the examples too
[00:01:07] <mojavelinux> yep
[00:01:29] <sbryzak> cbrock is going to work closely with us to help us improve the CDI/Errai integration
[00:01:36] <mojavelinux> examples are critical to Seam's success at this point because I think people look at CDI and say "okay, everything is perfect now"
[00:01:39] <mojavelinux> and we love CDI
[00:01:44] <mojavelinux> but it isn't the whole story
[00:02:00] <mojavelinux> so we need to "sell" that
[00:02:15] <lightguard_jp> I plan on doing a servlet example for catch
[00:02:31] <lightguard_jp> I'm really considering dropping the JAX-RS example for the servlet one
[00:02:54] <lightguard_jp> The jaxrs catch example was really more of a proof of integration with jaxrs
[00:03:05] <lightguard_jp> Because the rest module has that now, it's not really needed
[00:03:09] <mojavelinux> yep, agreed
[00:03:21] <lightguard_jp> The servlet example would really be an easy example of how it works
[00:03:24] <lightguard_jp> Not the integration
[00:03:28] <mojavelinux> go with servlet only in the example...no circular deps and easier for people to see the simplicity of catch
[00:04:08] <sbryzak> small, concise examples that demonstrate a significant feature in your module are good
[00:04:40] <lightguard_jp> sbryzak: Right, that's what I'm going for.
[00:04:43] <mojavelinux> exactly
[00:06:36] <jose_freitas> sbryzak, what do you by non JSF examples exactly?
[00:07:10] <mojavelinux> wrapping up
[00:07:10] <mojavelinux> shane will address ASL switch for modules
[00:07:10] <mojavelinux> solder needs to track compatibility (may require changes in solder to adopt to correct spec impl)
[00:07:10] <mojavelinux> servicehandler redesign is important
[00:07:10] <mojavelinux> messages API redesign is important; ken is leading, dan will forward info to shane and we need to take it to seam-dev
[00:07:10] <mojavelinux> need examples to get moving, especially non-JSF (wicket, gwt)
[00:07:29] <sbryzak> jose_freitas: examples which don't require JSF
[00:08:15] <mojavelinux> examples can be developed in our own working environment and merged in later...important part is that we are experimenting with/using this stuff...not necessarily where or how
[00:08:36] <mojavelinux> own working == your github if necessarily
[00:08:42] <mojavelinux> s/necessarily/necessary/
[00:08:52] <mojavelinux> in other words, go play
[00:09:46] <mojavelinux> I'll quote shane to conclude
[00:09:56] <mojavelinux> " I just wanted to let everyone know that their efforts are definitely appreciated, and together I'm sure that we can release a top quality project that really makes a big difference to the Java EE landscape."
[00:09:58] <mojavelinux> woot
[00:10:13] <lightguard_jp> :)
[00:10:22] <sbryzak> thanks dan :)
[00:10:55] <mojavelinux> and our work extend beyond features, we are doing a lot to correct the compatibilty/harden java ee just by working on seam and reporting issues
[00:19:35] <jose_freitas> =)
[00:20:34] *** ssachtleben has quit IRC
[00:20:41] <jose_freitas> your moms should be really proud of you
[00:21:16] <jose_freitas> lol
[00:22:12] <clerum> also if anyone has spare time to review mail I can get started on the documenation and test coverage
[00:28:02] <mojavelinux> cody, would you mind if I post the call for review to the mailinglist? I have an idea which may catch people's attention :)
[00:28:34] <jose_freitas> mojavelinux, does ken enters the irc channel?
[00:28:47] <mojavelinux> he does, usually, don't see him now though
[00:28:54] *** aslak has quit IRC
[00:29:13] <mojavelinux> got his e-mail?
[00:29:20] <jose_freitas> I guess I never saw him here.
[00:29:36] <jose_freitas> nope
[00:30:47] <mojavelinux> working through the messages feature with him would be a huge help
[00:31:27] <jose_freitas> ok
[00:31:56] <clerum> that should be fine. first time I have written anything like this
[00:31:58] <jose_freitas> I should thank you all
[00:32:08] <jose_freitas> you guys are really doing a great job
[00:32:23] <clerum> I'm expecting people to have issues with the design
[00:32:45] <jose_freitas> I should get going now.
[00:32:50] <jose_freitas> bye
[00:33:03] *** jose_freitas has quit IRC
[00:38:21] *** akazakov has quit IRC
[00:42:19] <lightguard_jp> Does the faces module have the s:decorate replacement in it?
[00:47:43] *** clerum1 has joined #seam-dev
[00:47:44] *** clerum has quit IRC
[00:52:12] *** clerum1 has quit IRC
[00:52:40] *** clerum has joined #seam-dev
[00:55:23] <mojavelinux> yep
[00:55:27] <mojavelinux> sort of, mostly
[00:55:37] <mojavelinux> it's the UIInputContainer + composite components
[00:55:42] <mojavelinux> you can see example in the booking
[00:56:05] <mojavelinux> https://github.com/seam/examples/blob/master/javaee-booking/src/main/webapp/resources/components/property/input.xhtml
[00:56:27] <lightguard_jp> Yeah, I found it
[00:57:08] <mojavelinux> what we have now is more verbose than before, but also way more powerful
[00:57:18] <mojavelinux> give and take
[00:57:52] <mojavelinux> it's less verbose in the form in which it's used
[00:57:58] <mojavelinux> more verbose in the template
[00:58:07] <mojavelinux> instead of <s:decorate template="..."/>
[00:58:08] <mojavelinux> you just get
[00:58:11] <mojavelinux> <s:input/>
[00:58:46] *** johnament has joined #seam-dev
[01:04:34] <johnament> any thoughts on this stack trace... jboss doesn't like weld i think.. :-) http://pastebin.com/Z3CgkFek
[01:08:32] <mojavelinux> wow, never seen that one before
[01:08:44] <mojavelinux> yep, we have to keep putting JBoss and Weld in timeout for fighting
[01:09:03] <mojavelinux> actually, it would be more true to say that GF and Weld are the adversaries at the moment
[01:09:06] <mojavelinux> disrupting the class
[01:09:24] <mojavelinux> do you have the source of that bean?
[01:09:35] <mojavelinux> as always, I recommend keeping arquillian handy for testing what does/doesn't work
[01:09:51] <mojavelinux> keep a "compat" project around for testing permutations of beans
[01:10:02] <mojavelinux> that's what I do, because otherwise I would lose my mind and all the time I don't have
[01:10:46] *** clerum has quit IRC
[01:12:16] *** lightguard_jp has quit IRC
[01:14:48] <johnament> yeah, it's the bean i wrote to handle ingress JMS messaging.
[01:15:02] <johnament> the exception gets raised on the line where it fires the event via bean manager.
[01:22:37] <johnament> the flow is essentially bean fires event, event publishes to JMS.  sub receives message from queue, sub then throws exception on line with event firing.
[01:37:35] *** clerum has joined #seam-dev
[01:38:36] *** kenfinnigan has joined #seam-dev
[02:01:08] *** tsurdilo2 has quit IRC
[02:03:30] *** cbrock has quit IRC
[02:13:07] <jbossbot> git [international] push master 391a6fe.. Ken Finnigan Update Seam BOM to 3.0.0.b8
[02:13:08] <jbossbot> git [international] push master URL: http://github.com/seam/international/compare/debc820...391a6fe
[02:14:05] *** bitshuffler has quit IRC
[02:18:09] *** jganoff has joined #seam-dev
[02:18:18] <johnament> jganoff:
[02:18:21] <johnament> jganoff: hi
[02:19:48] <jganoff> johnament, howdy!
[02:20:00] <jganoff> johnament, GitHub meet and greet/drink starts here in 1:45
[02:20:24] <jganoff> johnament, I'm replying to your last email now before I head out to that. Just got home from work... busy busy!
[02:20:25] <johnament> jganoff: orly?
[02:20:28] <jganoff> johnament, How's it going?
[02:21:08] <johnament> jganoff: i walked out of work to my car to find a 10" crack in the windshield - that's how it's going
[02:21:43] <jganoff> johnament, :( Ouch.
[02:21:44] <mojavelinux> man, I wish I could join you guys for the github meet and greet
[02:21:54] <jganoff> mojavelinux, you'll get your turn next week, right?
[02:21:55] <mojavelinux> I'll just have to have a beer in the honor of it :)
[02:22:21] <jganoff> mojavelinux, excellent idea! Wish you were in town to join us too. Haven't met up in a while..
[02:22:47] <johnament> with the way the weather's been here, i'm not surprised.
[02:22:47] <jganoff> mojavelinux, and I haven't been able to attend any seam meetings in a while either. The new meeting time is pretty horrible for me.
[02:23:03] <jganoff> johnament, Staying warm at least?
[02:23:14] <mojavelinux> you seem to jump on a bit later...how about this time?
[02:23:23] <mojavelinux> is that better for you guys?
[02:23:31] <mojavelinux> 20:00 EST?
[02:23:44] <jganoff> mojavelinux, yea, just specifically thursdays at 5:30 conflict with another meeting for me
[02:23:49] <jganoff> est
[02:23:51] <mojavelinux> ahhh
[02:24:14] <mojavelinux> we could do Wednesday instead, or do you prefer something around 7:00 - 8:00 in general
[02:24:28] <jganoff> mojavelinux, anyway, on that note - i need to send out an email re: seam-jms beta. The work johnament has been doing is great and we'll be able to push out an alpha2 just to get api feedback.
[02:24:36] <mojavelinux> great!
[02:24:46] <mojavelinux> I had jms on the agenda, but we got stuck on some other things
[02:25:08] <kenfinnigan> for me 5:30 is usually when I'm heading home, so a bit later works for me too
[02:25:15] <jganoff> mojavelinux, and then possibly a quick iteration on that then a beta... would be nice to get some other eyes on it asap. There's not much left to implement to meet the spec. The other extras we've been wanting in (dynamically configurable routes) can be pushed
[02:25:31] <mojavelinux> I'm thrilled to see it picking up again. I was going to ask if you wanted to push out an alpha2 just to upgrade solder, but since you've got new stuff on the way, might as well wait for that
[02:25:48] <johnament> jganoff: i think considering the inexplicable exception i'm still seeing, i'd be a bit cautious....
[02:26:03] <jganoff> mojavelinux, yea, i'm going to ask sbryzak to help with a release - it's been a while since I went through the whole process ;)
[02:26:11] <mojavelinux> don't worry, very fresh in our heads
[02:26:13] <mojavelinux> jason too
[02:26:20] <jganoff> johnament, true, we need to track that down for sure before merging those changes in
[02:26:23] <mojavelinux> we are like release warriors
[02:26:32] <jganoff> mojavelinux, nice!
[02:26:42] <mojavelinux> I Just spent two hours creating a test case for ARquillian to test some strange jndi error
[02:26:45] <jganoff> mojavelinux, I'm all set up to do it but .. yea. It definitely requires a beer at the end
[02:26:51] <mojavelinux> turns out, no bug. not sure if that is good or bad
[02:27:00] <mojavelinux> either way, now I have a killer test case
[02:27:05] <jganoff> mojavelinux, hah, nice!
[02:27:14] <mojavelinux> actually, it found a bug in arquillian too
[02:27:17] <mojavelinux> :)
[02:27:21] <mojavelinux> so I guess it was worth it
[02:27:51] <johnament> i'm sure aslak loves you for those.
[02:27:53] <johnament> :-)
[02:32:13] <mojavelinux> 05:00 is right around the time of travel for the east coast, so I can see how that is bad
[02:32:49] <mojavelinux> I'm proposing somethign on the list
[02:34:53] <jganoff> mojavelinux, great.
[02:35:20] <johnament> jganoff: i'm going to try to get through test cases to figure out what's going on in SEAMJMS-3 & 4.  though i am heavily concerned that if it proves to be a bug in weld or as we may be up the creek, so to speak.
[02:35:21] <jganoff> mojavelinux, To progress a module into beta, what sort of doc is required? The JMS doc has existed since alpha 1 but we don't have any examples yet.
[02:35:21] <jbossbot> jira [SEAMJMS-3] Event Mapping Observer Method Interfaces - Egress [Open, Blocker, John Ament] https://issues.jboss.org/browse/SEAMJMS-3
[02:36:04] *** kenfinnigan has quit IRC
[02:36:22] <jganoff> johnament, that's really great news that we're to that point. Hopefully it's not a bug and something was overlooked. Nevertheless, if it is a bug we'll just have to take that in stride and get it worked out. Not much we can do about that until we know.
[02:36:55] *** kenfinnigan has joined #seam-dev
[02:39:27] <mojavelinux> for docs, it's really your judgement call, but I would say enough docs so that if you were looking at it, you would know what the heck to do with it
[02:39:50] <mojavelinux> and a simple example is ideal so that people can actually see it in action...but keep it simple
[02:39:53] <johnament> jganoff: did you ever figure out what you needed to do for SEAMJMS-2?
[02:39:54] <jbossbot> jira [SEAMJMS-2] Message Destinations may be declared by specifying a @Resource annotation as part of a producer field [Open, Blocker, Unassigned] https://issues.jboss.org/browse/SEAMJMS-2
[02:40:35] <johnament> jganoff: we already know that @Produces @SomeQualifier @Resource(mappedName="xx") Destination d; won't work per the spec.
[02:40:56] *** cbrock has joined #seam-dev
[02:40:56] *** cbrock has quit IRC
[02:40:56] *** cbrock has joined #seam-dev
[02:40:58] <mojavelinux> gotta run, bbl
[02:41:55] <jganoff> johnament, not 100% sure, need to clarify that
[02:42:35] <jganoff> johnament, can you refresh my memory about why it wont work per the spec?
[02:42:42] <jganoff> johnament, I seem to have local amnesia :(
[02:43:17] <johnament> jganoff: i believe it had to do with scoping problems.
[02:44:07] <johnament> jganoff: i think it was part of that first issue i fixed, where you were trying to do it on the application scope
[02:44:46] <jganoff> johnament, oh, with DestinationProducer was it?
[02:45:05] <johnament> jganoff: i think it was the connection.
[02:45:35] <johnament> jganoff: but it was one of those weird fringe issues since putting it in a method makes it work, but still not guaranteed
[02:46:47] <jganoff> johnament, oh right, you were looking at the interface injection when you did your testing with this, correct?
[02:47:30] <johnament> prior to it.
[02:49:33] <jganoff> johnament, I guess I'll just have to dig back into that. My memory is completely lacking on the topic. :/
[02:50:08] <johnament> just dug through it. give me a min
[02:52:24] <johnament> jganoff: it was in connection producer.  the producer for connection factory was field level and application scoped
[02:53:06] <jganoff> johnament, ahh that's right... did you ever identify that as a bug?
[02:53:35] <johnament> yeah, then was rejected due to working as per spec.
[02:55:20] *** cbrock has quit IRC
[02:56:23] <jganoff> johnament, doh! Alright then we may have an inconsistency. I'll post something to the mailing list soon.
[03:01:09] <jganoff> johnament, do you have the link to the jira you created?
[03:02:36] <johnament> jganoff: i'll find it
[03:02:59] <johnament> WELD-814
[03:03:00] <jbossbot> jira [WELD-814] Resources injected to producer fields fail to be produced [Closed, Major, Pete Muir] https://issues.jboss.org/browse/WELD-814
[03:07:21] <jganoff> johnament, Thanks for the clarification. I'll shoot an email to the dev list on that topic now to get some clarification
[03:07:46] <johnament> jganoff: oh well when you look at the spec it makes sense actually
[03:08:36] <jganoff> johnament, sure, I agree with Pete's comment on that case but that then contradicts what JSR-299 says in the JMS section on producing topics
[03:08:45] <jganoff> johnament, or rather destinations in general
[03:10:20] <johnament> jganoff: what page is that on?
[03:10:41] <jganoff> johnament, section 3.7.2 of the spec draft attached to SEAMJMS-2
[03:10:41] <johnament> jganoff: if i had to guess, it's dependent
[03:10:42] <jbossbot> jira [SEAMJMS-2] Message Destinations may be declared by specifying a @Resource annotation as part of a producer field [Open, Blocker, Unassigned] https://issues.jboss.org/browse/SEAMJMS-2
[03:12:00] <johnament> jganoff: yeah both of those are dependent scoped.
[03:14:42] <jganoff> johnament, then it should "just work" as I was originally thinking when I created seamjms-2. I thought there was an environment where @Resource wouldn't properly be injected but I can't for the life of me remember.
[03:32:42] <johnament> i have to say, this container exception makes no sense.
[03:32:54] <jganoff> :/
[03:34:39] <jganoff> ugh, the community disclaimer on jboss.org/jbossas/downloads doesn't work in Chrome.. :( Forcing me to start firefox to get to the actual download link.
[03:56:58] *** kenfinnigan has left #seam-dev
[03:58:04] *** johnament has quit IRC
[04:07:42] *** jganoff has quit IRC
[04:40:00] <jbossbot> git [remoting] push master 97356ae.. Shane Bryzak add web-fragment.xml
[04:40:00] <jbossbot> git [remoting] push master 545cefc.. Shane Bryzak minor
[04:40:00] <jbossbot> git [remoting] push master URL: http://github.com/seam/remoting/compare/55514ba...545cefc
[04:40:17] <jbossbot> git [faces] push master 9d7022d.. Shane Bryzak update to asl
[04:40:17] <jbossbot> git [faces] push master c341b2a.. Shane Bryzak Merge branch 'master' of github.com:seam/faces
[04:40:18] <jbossbot> git [faces] push master URL: http://github.com/seam/faces/compare/76502f7...c341b2a
[04:55:55] <jbossbot> git [persistence] push master a796d1e.. Shane Bryzak convert to asl
[04:55:55] <jbossbot> git [persistence] push master 0222b27.. Shane Bryzak minor
[04:55:56] <jbossbot> git [persistence] push master URL: http://github.com/seam/persistence/compare/25fac2e...0222b27
[04:57:30] <jbossbot> git [remoting] push master db3337d.. Shane Bryzak fix github urls
[04:57:30] <jbossbot> git [remoting] push master URL: http://github.com/seam/remoting/compare/545cefc...db3337d
[05:00:01] <jbossbot> git [security] push master 7f86401.. Shane Bryzak convert to asl
[05:00:01] <jbossbot> git [security] push master URL: http://github.com/seam/security/compare/6b61724...7f86401
[05:00:16] <jbossbot> git [remoting] push master 50f4c53.. Shane Bryzak minor
[05:00:16] <jbossbot> git [remoting] push master URL: http://github.com/seam/remoting/compare/db3337d...50f4c53
[05:02:54] <jbossbot> git [config] push master a6ecb6f.. Shane Bryzak convert to asl
[05:02:54] <jbossbot> git [config] push master URL: http://github.com/seam/config/compare/6303b77...a6ecb6f
[05:05:30] <jbossbot> git [rest] push master 26fb868.. Shane Bryzak convert to asl
[05:05:30] <jbossbot> git [rest] push master 576a044.. Shane Bryzak Merge branch 'master' of github.com:seam/rest
[05:05:30] <jbossbot> git [rest] push master URL: http://github.com/seam/rest/compare/ee3bd10...576a044
[05:08:42] <jbossbot> git [rest] push master f64ee7e.. Shane Bryzak removed lgpl.txt
[05:08:42] <jbossbot> git [rest] push master URL: http://github.com/seam/rest/compare/576a044...f64ee7e
[05:12:48] <jbossbot> git [international] push master 3644bfb.. Shane Bryzak convert to asl
[05:12:48] <jbossbot> git [international] push master URL: http://github.com/seam/international/compare/391a6fe...3644bfb
[05:16:28] <jbossbot> git [parent] push master 57c409b.. Shane Bryzak convert to apache license
[05:16:28] <jbossbot> git [parent] push master 3cf2612.. Shane Bryzak Merge remote branch 'upstream/master'
[05:16:28] <jbossbot> git [parent] push master URL: http://github.com/seam/parent/compare/0e723a3...3cf2612
[05:58:19] *** rruss has joined #seam-dev
[05:58:25] *** rruss has quit IRC
[05:58:25] *** rruss has joined #seam-dev
[06:44:25] *** rruss has quit IRC
[06:47:21] <jbossbot> git [wicket] push master 00cab9d.. Dan Allen SEAMWICKET-21 fix remaining issues...
[06:47:22] <jbossbot> jira [SEAMWICKET-21] Build system breaks profiles and diversified deployments [Resolved, Major, Unassigned] https://issues.jboss.org/browse/SEAMWICKET-21
[06:47:22] <jbossbot> git [wicket] push master URL: http://github.com/seam/wicket/compare/391d81c...00cab9d
[06:49:54] *** rruss has joined #seam-dev
[07:09:14] *** allforjava has joined #seam-dev
[07:09:37] <allforjava> #jbosstools
[07:17:08] *** allforjava has quit IRC
[07:27:59] *** allforjava has joined #seam-dev
[07:30:47] *** lukaszlenart has joined #seam-dev
[07:33:37] <jbossbot> git [persistence] push master 1d0dfb6.. Stuart Douglas Replace EJBSynchronizations with TransactionManagerSynchronizations
[07:33:37] <jbossbot> git [persistence] push master URL: http://github.com/seam/persistence/compare/0222b27...1d0dfb6
[07:43:58] *** rpetruescu has joined #seam-dev
[07:44:00] <jbossbot> git [persistence] push master 2b56511.. Stuart Douglas resin support for TransactionManagerSyncrhonizations
[07:44:01] <jbossbot> git [persistence] push master URL: http://github.com/seam/persistence/compare/1d0dfb6...2b56511
[07:44:08] <stuartdouglas> sbryzak: It should be possible to deploy multiple seam persistence apps now
[07:50:05] <nickarls> stu: and jaikiran is considering a configuration option for prefixing the jndi names for the normal EJB case
[08:02:14] *** clerum has quit IRC
[08:08:56] *** lukaszlenart has quit IRC
[08:12:44] *** amitev has joined #seam-dev
[08:13:38] *** lukaszlenart has joined #seam-dev
[08:15:37] *** aslak has joined #seam-dev
[08:15:37] *** aslak has quit IRC
[08:15:37] *** aslak has joined #seam-dev
[08:25:06] *** marekn has joined #seam-dev
[08:31:43] *** amitev2 has joined #seam-dev
[08:32:55] *** amitev has quit IRC
[08:37:12] *** amitev2 is now known as amitev
[08:37:12] *** aslak has quit IRC
[08:37:48] *** aslak has joined #seam-dev
[08:46:58] *** allforjava1 has joined #seam-dev
[08:48:06] *** allforjava has quit IRC
[08:59:21] *** mgencur has joined #seam-dev
[09:06:22] *** jharting has joined #seam-dev
[09:07:09] *** aslak has quit IRC
[09:07:49] *** aslak has joined #seam-dev
[09:11:24] *** maschmid has joined #seam-dev
[09:17:10] *** oskutka has joined #seam-dev
[09:17:10] *** aslak has quit IRC
[09:17:48] *** aslak has joined #seam-dev
[09:30:15] *** epbernard has joined #seam-dev
[09:30:15] *** epbernard is now known as emmanuel
[09:35:07] *** rpetruescu has quit IRC
[09:36:06] *** rpetruescu has joined #seam-dev
[09:41:07] <jharting> stuartdouglas: ping
[09:41:35] *** akazakov has joined #seam-dev
[10:12:38] *** allforjava has joined #seam-dev
[10:13:16] *** alesj has joined #seam-dev
[10:14:01] *** allforjava1 has quit IRC
[10:37:31] *** allforjava1 has joined #seam-dev
[10:39:01] *** allforjava has quit IRC
[11:03:24] *** rruss has quit IRC
[11:06:50] *** jose_freitas_afk is now known as jose_freitas
[11:35:24] *** shervin_a has joined #seam-dev
[12:08:22] *** allforjava has joined #seam-dev
[12:10:01] *** allforjava1 has quit IRC
[12:13:18] *** allforjava has left #seam-dev
[12:14:54] *** emmanuel has quit IRC
[12:55:18] *** marekn has left #seam-dev
[13:39:25] *** epbernard has joined #seam-dev
[13:39:25] *** epbernard is now known as emmanuel
[13:41:00] <stuartdouglas> jharting: pong
[13:41:49] <jharting> stuartdouglas: Hi Stuart, have a minute?
[13:41:58] <stuartdouglas> ok
[13:43:58] <jharting> stuartdouglas: how is the declarative transaction management within seam persistence implemented wrt the faces module? I haven't found anything about it in the faces documentation and the docs for persistence module say only: "             If you are using seam managed transactions as part of the seam-faces module you do not              need to worry about declarative transaction management. Seam will automatically start              a
[13:44:29] <jharting> stuartdouglas: it is unclear to me whether "Seam will automatically start a transaction ..." means the persistence module or the faces module
[13:44:54] <stuartdouglas> that needs some more work
[13:45:21] <stuartdouglas> I did implement it a while ago, but then there were problems with it and I think it got removed from faces
[13:46:40] <stuartdouglas> I will look at it this weekend
[13:46:54] <jharting> stuartdouglas: ok
[13:47:29] <shervin_a> stuartdouglas: What ever happened to the @Transactional(requires_new) stuff you implemented. It was never taken in?
[13:47:41] <stuartdouglas> That was seam 2
[13:47:47] <stuartdouglas> back ages ago
[13:47:48] <shervin_a> stuartdouglas: yes
[13:47:56] <stuartdouglas> it never got accepted
[13:48:00] <shervin_a> why?
[13:48:05] <stuartdouglas> It did work though
[13:48:32] <shervin_a> hmm too bad. Because it really is handy. Specially in a non ejb enviroment
[13:48:39] <stuartdouglas> Now that I have a bit more time, I will look at making it work in seam 3
[13:49:06] <shervin_a> yes, definitely should
[13:49:21] *** pmuir has joined #seam-dev
[13:49:46] <stuartdouglas> The trickey part is you really need a new smpc when the REQURES_NEW transaction starts
[13:50:29] <stuartdouglas> and also you need access to a JTA TransactionManager,
[13:50:46] <stuartdouglas> so the seam 2 stuff did not work on webshere
[13:52:01] <shervin_a> i c
[13:56:13] <stuartdouglas> I am going to bed
[13:56:15] <stuartdouglas> night
[14:35:18] *** oskutka has quit IRC
[14:41:46] *** lightguard_jp has joined #seam-dev
[15:06:16] *** rruss has joined #seam-dev
[15:07:41] *** marekn has joined #seam-dev
[15:13:05] *** lukaszlenart_ has joined #seam-dev
[15:13:42] *** lukaszlenart has quit IRC
[15:13:42] *** lukaszlenart_ is now known as lukaszlenart
[15:45:47] *** jharting has quit IRC
[15:59:08] *** monkeyden has joined #seam-dev
[16:01:47] *** marekn has quit IRC
[16:03:43] *** clerum has joined #seam-dev
[16:13:58] *** shervin_a has quit IRC
[16:45:14] *** tsurdilo has joined #seam-dev
[16:48:11] *** lightguard_jp has quit IRC
[17:07:53] *** mgencur has quit IRC
[17:11:03] *** maschmid has quit IRC
[17:15:37] *** amitev has quit IRC
[17:27:50] *** pmuir has quit IRC
[17:36:20] *** ssachtleben has joined #seam-dev
[17:57:39] *** rruss has quit IRC
[18:00:29] *** lincolnthree has joined #seam-dev
[18:09:48] *** rpetruescu has quit IRC
[18:15:03] *** rruss has joined #seam-dev
[18:16:53] <ssachtleben> anyone here for two questions? ;)
[18:17:00] <lincolnthree> that depends
[18:17:24] <lincolnthree> what is "here" anyway? isn't it just "there" without the "t" ?
[18:17:34] <ssachtleben> how can I add jsf messages to specific components?
[18:17:48] <lincolnthree> with which framework?
[18:18:00] <ssachtleben> seam 3
[18:18:08] <lincolnthree> Seam 3 Faces?
[18:18:18] <ssachtleben> yep
[18:19:01] <lincolnthree> http://docs.jboss.org/seam/3/faces/reference/snapshot/en-US/html_single/#adding
[18:19:16] <lincolnthree> messages.info("myMessage").targets("componentId")
[18:19:28] <lincolnthree> but keep in mind? this API is going to likely change in the next release
[18:19:37] <lincolnthree> so that *should* work for now, but it might be slightly different soon
[18:20:19] <ssachtleben> but that messages bound global or?
[18:20:33] <lincolnthree> that's what targets() is for
[18:21:37] <ssachtleben> where to set the target?
[18:24:26] <ssachtleben> i cant find any target properties thats my problem ;)
[18:27:56] <ssachtleben> well if it changes it doesnt matter since I wont be finish with my page in the next 2 month
[18:29:24] <ssachtleben> second question is how to use i18n on @Size bean validation since it just takes constants any proper way to implement that?
[18:30:03] <lincolnthree> What properties do you see?
[18:30:20] *** tsurdilo has quit IRC
[18:31:20] *** tsurdilo has joined #seam-dev
[18:31:42] <ssachtleben> info(BundleKey, Object...)
[18:31:55] *** tsurdilo has quit IRC
[18:32:15] *** tsurdilo has joined #seam-dev
[18:33:32] <ssachtleben> ah well maybe its added in the current version i'm still using international version 3.0.0.Alpha3 since deployment problems with the current versions
[18:33:36] <lincolnthree> what does info return?
[18:34:35] <ssachtleben> LOL
[18:34:41] <ssachtleben> TemplateMessage with method targets :D
[18:34:46] <lincolnthree> :)
[18:34:59] <ssachtleben> thanks
[18:42:33] <ssachtleben> any idea about that @Size problem?
[18:43:21] <lincolnthree> No practical solution at this time, sorry. It's a problem with using annotations that are directly tied to a spec that doesn't have an extension point for overriding how messages are handled (as far as I know.. though it's possible it might be if you look in to it.)
[18:44:17] <ssachtleben> ok
[18:44:36] <lincolnthree> If it is possible, then it's something the seam i18n module could tie in to
[18:45:51] <ssachtleben> yeah well I just use one language so its not that big problem for me
[18:46:07] <ssachtleben> just interesting because it just take constants ^^
[18:46:20] <lincolnthree> Ah here's an interesting idea.
[18:46:36] <lincolnthree> It mayyyy be possible to assign a static constant value using seam i18n
[18:46:52] <lincolnthree> then you can use that constant in the annotation
[18:46:54] <lincolnthree> possibly
[18:47:09] <lincolnthree> not sure if that actually works, let me check something
[18:47:39] <ssachtleben> i think I have tried that before
[18:47:56] <ssachtleben> btw the target method works like a charm :)
[18:48:13] <lincolnthree> awesome!
[18:53:22] <ssachtleben> well I cant come arround that "The value for annotation attribute Size.message must be a constant expression"
[18:53:32] <lincolnthree> Yeah i just tried and hit that myself
[18:53:53] <ssachtleben> i really like that bean validation
[18:54:08] <ssachtleben> its so easy and fast done
[18:54:19] <lincolnthree> Yeah, seems like this is an obvious flaw, though
[18:55:17] <ssachtleben> well thanks for your time and gl with the next release :)
[18:55:34] <lincolnthree> Hey thanks! np, let me know how you think it's going
[18:55:49] *** emmanuel has quit IRC
[18:56:51] *** tsurdilo has quit IRC
[18:57:21] *** tsurdilo has joined #seam-dev
[19:04:58] <jose_freitas> lincolnthree, normally dont you have an integration tool between git and eclipsE?
[19:05:31] <lincolnthree> jose_freitas: egit
[19:06:33] <jose_freitas> hmm
[19:06:59] <jose_freitas> I have it too. I can clone the repository with it, but when importing projects I have to import as a maven project cause git does not recognize as a project format
[19:07:05] <jose_freitas> so do you import as a maven project?
[19:07:29] <lincolnthree> usually i use git outside of eclipse to do git stuff
[19:07:36] <jose_freitas> I see
[19:07:38] <lincolnthree> then import as a maven project
[19:09:14] <jose_freitas> yeah... that works, but it'd be more comfortable if I could commit from eclipse
[19:09:26] <jose_freitas> track edited files, and compare with repository
[19:09:32] <jose_freitas> as I usually do with svn
[19:14:14] <jose_freitas> found it
[19:14:15] <jose_freitas> xD
[19:14:43] <jose_freitas> you can import as a maven project and then with "team >> share project" you can choose the project in cloned repository
[19:14:46] <lincolnthree> team -> share project -> git -> select repo -> press enter
[19:14:55] <jose_freitas> thanks
[19:19:39] <jose_freitas> with the booking example I used mvn eclipse:eclipse to create a eclipse structure so I could import with egit
[19:20:20] <jose_freitas> I have to make the eclipse conf disappear
[19:21:42] *** epbernard has joined #seam-dev
[19:21:42] *** epbernard is now known as emmanuel
[19:22:01] <lincolnthree> rm -rf .settings .project .classpath
[19:30:14] <jose_freitas> =)
[19:30:41] <jose_freitas> thanks
[19:33:06] *** emmanuel has quit IRC
[19:42:03] *** msmigielski has joined #seam-dev
[19:42:59] *** ssachtleben has quit IRC
[19:43:48] *** cbrock has joined #seam-dev
[19:45:20] *** rpetruescu has joined #seam-dev
[19:45:33] *** cbrock_ has joined #seam-dev
[19:45:33] *** cbrock_ has quit IRC
[19:45:33] *** cbrock_ has joined #seam-dev
[19:46:50] *** kenfinnigan has joined #seam-dev
[19:48:14] *** cbrock has quit IRC
[19:48:14] *** cbrock_ is now known as cbrock
[19:50:59] <kenfinnigan> jose_freitas: free to chat now if you are?
[19:52:26] <jose_freitas> hey ken
[19:52:48] <kenfinnigan> hey
[19:53:05] <kenfinnigan> what questions did you have?
[19:53:32] <jose_freitas> I was taking a look at what is api and what is impl
[19:53:53] <kenfinnigan> ok
[19:54:47] <jose_freitas> is that defined by a doc or something?
[19:54:57] <jose_freitas> what will be on api and impl?
[19:55:27] <jose_freitas> it sounds stupid
[19:55:43] <jose_freitas> yes, but let me find the class which made me think about it
[19:55:59] <kenfinnigan> no, it mostly depends on whether code will be directly used by app developer
[19:56:19] <kenfinnigan> if yes, then goes in api
[19:56:59] <jose_freitas> hm, but for example the messageFactory
[19:57:23] <kenfinnigan> yep
[19:58:28] <jose_freitas> why not using it on the impl and keeps just the interface?
[19:58:40] <jose_freitas> just a question, not critizing
[19:58:51] *** bitshuffler has joined #seam-dev
[20:00:01] <kenfinnigan> i think it was done like that to provide a concrete way for developers to create messages
[20:00:38] <kenfinnigan> how this works and is structured are all things we can look at changing if it makes sense
[20:01:42] <jose_freitas> ok, now about the structure, when import the repository, it created 6 projects
[20:02:18] <kenfinnigan> that's right
[20:02:23] <jose_freitas> api, dist, impl, parent, reference, and one that has the same pom as the parent
[20:02:42] <jose_freitas> ah,no, its not the same pom
[20:02:43] <kenfinnigan> combined you can ignore
[20:02:48] <jose_freitas> ok
[20:02:58] <kenfinnigan> dist also
[20:03:14] <jose_freitas> so the "seam-international" project I should ignore
[20:03:14] <kenfinnigan> reference is for the moduke
[20:03:33] <jose_freitas> ok
[20:03:35] <kenfinnigan> *module* docs
[20:03:57] <jose_freitas> and one last question, is about the jdocbook
[20:04:24] <jose_freitas> is there a specific pluginrepository for it?
[20:04:43] <kenfinnigan> think it comes from jboss repo
[20:06:50] <jose_freitas> ok, I guess its all
[20:07:12] <jose_freitas> thanks
[20:07:25] <kenfinnigan> no problem
[20:07:43] <kenfinnigan> let me know if you have further questions
[20:07:47] <jose_freitas> thanks
[20:08:01] <jose_freitas> did you think where is the best place I can help you?
[20:08:03] <kenfinnigan> or to discuss changes to the module
[20:08:57] <kenfinnigan> if you were interested, an example app would be cool
[20:09:25] <kenfinnigan> there is plenty of ground work that could be done while messages api is tweaked
[20:10:22] <kenfinnigan> can also come up with suggestions on simplifying current messages api for non type safe usage
[20:10:39] <jose_freitas> ok, it'd be nice to get a timeanddate clone working
[20:11:06] <kenfinnigan> that is the example that dan and i think would work best
[20:11:09] <jose_freitas> but the thing is that I don't know if the best for an example app is to wait till the messages api
[20:11:53] <jose_freitas> we can start with the worldsclock though
[20:12:23] <kenfinnigan> certainly the locale and tz example bits can be done
[20:13:29] <kenfinnigan> take a look at some old seam 2 code for international as there are examples of jsf tz and locale selectors that would be good to update and use
[20:13:42] <jose_freitas> hm
[20:14:54] *** rpetruescu has quit IRC
[20:15:05] *** cbrock has quit IRC
[20:16:05] <jose_freitas> ok, I'll do it
[20:16:26] <kenfinnigan> thanks
[20:16:51] <kenfinnigan> drop me a mail if you have issues, or irc if I'm about
[20:17:10] <kenfinnigan> and thanks for offering to help
[20:17:15] <kenfinnigan> much appreciated
[20:17:53] <jose_freitas> np
[20:18:40] *** kenfinnigan has quit IRC
[20:30:36] *** lightguard_jp has joined #seam-dev
[20:33:41] *** msmigielski has quit IRC
[20:34:25] *** cbrock has joined #seam-dev
[20:34:25] *** cbrock has quit IRC
[20:34:25] *** cbrock has joined #seam-dev
[20:42:28] *** tsurdilo has quit IRC
[20:42:54] *** tsurdilo has joined #seam-dev
[20:45:54] *** lukaszlenart has quit IRC
[20:52:52] <lightguard_jp> I'm looking at SEAMCATCH-43 where does that line go?
[20:52:53] <jbossbot> jira [SEAMCATCH-43] Manifest.mf files in jars generated from  the module contain unreachable Implementation-URL [Open, Minor, Jason Porter] https://issues.jboss.org/browse/SEAMCATCH-43
[21:03:33] <jbossbot> git [catch] push master c05c78e.. LightGuard Fixes https://issues.jboss.org/browse/SEAMCATCH-43...
[21:03:33] <jbossbot> jira [SEAMCATCH-43] Manifest.mf files in jars generated from  the module contain unreachable Implementation-URL [Open, Minor, Jason Porter] https://issues.jboss.org/browse/SEAMCATCH-43
[21:03:33] <jbossbot> git [catch] push master URL: http://github.com/seam/catch/compare/b0e19aa...c05c78e
[21:03:45] *** jose_freitas has quit IRC
[21:10:11] <sbryzak> lightguard_jp: it's defined in the <url/> tag in the parent pom
[21:10:28] <lightguard_jp> sbryzak: Yeah, I found it.
[21:11:10] <lightguard_jp> Gotta love maven
[21:28:16] *** tsurdilo has quit IRC
[21:28:47] *** lightguard_jp has quit IRC
[21:30:18] <jbossbot> git [catch] push master dfac436.. LightGuard Fixes https://issues.jboss.org/browse/SEAMCATCH-45....
[21:30:20] <jbossbot> jira [SEAMCATCH-45] Misc documentation issues [Open, Minor, Jason Porter] https://issues.jboss.org/browse/SEAMCATCH-45
[21:30:20] <jbossbot> git [catch] push master URL: http://github.com/seam/catch/compare/c05c78e...dfac436
[21:30:53] *** lightguard_jp has joined #seam-dev
[21:32:41] <lightguard_jp> Anyone here familiar with how Catch works and traverses the exception stack?  I'd like to discuss SEAMCATCH-26
[21:32:42] <jbossbot> jira [SEAMCATCH-26] Make caught exception available as named bean [Open, Minor, Jason Porter] https://issues.jboss.org/browse/SEAMCATCH-26
[21:34:34] *** tsurdilo has joined #seam-dev
[21:35:04] *** akazakov has quit IRC
[21:36:40] *** akazakov has joined #seam-dev
[21:51:08] <lightguard_jp> For those interested in the discussion, I'm thinking of creating a producer which would create a named bean called "caughtException" which would be of type ExceptionToCatch and one which would produce a bean named "handledException" of type ExceptionStack.  These producers would be dependant scoped and produce conversation scoped beans.
[21:51:14] <lightguard_jp> Thoughts?
[21:51:39] <lincolnthree> What's the point? :-p
[21:53:43] <lightguard_jp> This would be for anyone wanting to create debug pages like the seam debug that exists in Seam2
[21:53:55] <lightguard_jp> Or really any error page
[21:54:17] <lightguard_jp> If you wanted to display to exception message or something.
[21:55:35] <mojavelinux> yeah, it's important that the exception state is exposed to the view
[21:55:42] <lincolnthree> So the bean would need to be sessionscoped most likely
[21:55:47] <lincolnthree> or renderscoped
[21:55:50] <mojavelinux> whether for a casual error page (development) or a more formal debug page
[21:55:52] <lincolnthree> but that only works in JSF
[21:56:21] <mojavelinux> I think request scoped is fine in the core of catch
[21:56:37] <mojavelinux> then JSF can modify that producer
[21:56:48] <lightguard_jp> I think Session is too long
[21:56:51] <mojavelinux> yep
[21:56:56] <lightguard_jp> And Render is probably too short
[21:57:06] <mojavelinux> you could do conversation
[21:57:12] <lightguard_jp> That's my thought
[21:57:19] <lincolnthree> conversation is bad IMO
[21:57:27] <lightguard_jp> That way when we do a seam debug you just start the conversation
[21:57:30] <lincolnthree> they tend to end with errors
[21:57:52] <lightguard_jp> lincolnthree: What do you mean?
[21:57:56] <lightguard_jp> People using them wrong?
[21:58:01] <mojavelinux> well, we aren't propogating the conversation
[21:58:05] <mojavelinux> we are just putting something there
[21:58:12] <mojavelinux> so the errors are in how you are dealing w/ conversation
[21:58:24] <mojavelinux> meaning, catch doesn't affect it one way or another
[21:58:37] <lightguard_jp> mojavelinux: I'm also looking at the servlet docs (http://docs.jboss.org/seam/3/servlet/3.0.0.Beta1/reference/en-US/html/) and you're missing a version number on that first page
[22:01:57] *** akazakov has quit IRC
[22:02:10] <lightguard_jp> I want it scoped right, but to Dan's point if you wanted to promote it to something higher in your application or module then you should be able to do that.
[22:02:56] <lightguard_jp> Conversation just seems to be the right choice because typically it's roughly the same as request but if you want it to hang around longer it will, and it's transparent to the user.
[22:04:53] <mojavelinux> right, because often it's typical to redirect to an error page
[22:04:58] <mojavelinux> so conversation is the right built-in scope
[22:05:12] <mojavelinux> the render scope being ideal only because the conversation scope isn't quite what we needed to solve that problem
[22:05:30] <mojavelinux> but we can make than an option in jsf, where render scope is available (or the end developer can make that change)
[22:06:58] <lightguard_jp> Fair enough, ConversationScoped it is, unless I hear protests :) What about the types?
[22:15:53] <mojavelinux> yep
[22:17:49] <lightguard_jp> mojavelinux: ?? Yep being good choices for the types?
[22:17:51] <lincolnthree> I protest
[22:18:13] <mojavelinux> yes, a +1
[22:18:16] <mojavelinux> :)
[22:18:17] <lightguard_jp> Okay, reasons?
[22:18:22] <lincolnthree> ConversationScope is not going to work in weld-SE
[22:18:32] <lightguard_jp> Hm
[22:18:40] <lightguard_jp> Conversations aren't supported in SE?
[22:19:01] <mojavelinux> I like the types because you get the initial reason that catch was invoked
[22:19:03] <lincolnthree> Neither is RequestScoped or SessionScoped
[22:19:09] <lincolnthree> are*
[22:19:23] <lightguard_jp> That doesn't leave many other options
[22:19:48] <lincolnthree> Fire an event that people can observe to catch the trace
[22:19:52] <mojavelinux> the scope can be changed in weld se
[22:19:54] <lincolnthree> In their own beans
[22:20:14] <mojavelinux> the point is not to observe another event
[22:20:22] <mojavelinux> they could easily do this in a catch handler
[22:20:31] <mojavelinux> the point is that it needs to be exposed and tracked by catch out of the box
[22:20:48] <mojavelinux> you can always reproduce it into the scope you want
[22:21:01] <mojavelinux> besides, only matters if you use it
[22:21:11] <lincolnthree> Fair enough.
[22:21:12] <mojavelinux> meaning, if you don't use it, you don't have a scope problem
[22:21:16] <lincolnthree> That's all I  had.
[22:21:40] *** amitev has joined #seam-dev
[22:21:59] <lightguard_jp> lincolnthree: Okay, sounds like it was resolved then.
[22:22:13] <mojavelinux> the ExceptionStack is the other correct choice because it provides the cleaned up stack ready for display
[22:22:15] <lincolnthree> Yep, no ill effects, proceed :)
[22:22:16] <mojavelinux> the focused picture
[22:22:53] <lightguard_jp> Okay, I'll go ahead with the two producers and types.
[22:23:07] <lightguard_jp> For the name do we want to use the FQN or just the simple name?
[22:23:56] <mojavelinux> a simple name until we have import capabilities for FQN
[22:25:11] <lightguard_jp> Okay, I'm going to proceed with the aforementioned idea.
[22:29:16] *** monkeyden has quit IRC
[22:46:53] *** cbrock has quit IRC
[22:51:30] *** alesj has quit IRC
[22:52:00] *** cbrock has joined #seam-dev
[22:52:00] *** cbrock has quit IRC
[22:52:00] *** cbrock has joined #seam-dev
[22:52:33] <lightguard_jp> If I'm doing a producer from the impl jar of API jars, that's a problem right?  People will have to use the combined jar.
[22:57:38] <mojavelinux> no, that's fine
[22:58:04] <mojavelinux> the problem is when there is an injection point in the impl from a bean that is in the api (I think)
[22:58:18] <lightguard_jp> mojavelinux: Do you remember the GF issue numbers?  Jason Lee is asking in #weld
[22:58:22] <lightguard_jp> I don't recall what they were
[22:58:32] <lightguard_jp> Ah
[22:58:35] <mojavelinux> just gotta look at the cdi component
[22:58:39] <mojavelinux> there aren't too many issues there
[23:04:21] <cbrock> mojavelinux: danping
[23:04:53] <mojavelinux>  /msg NickServ info mojavelinux
[23:04:57] <mojavelinux> oops, that didn't work
[23:06:08] *** mojavelinux is now known as mojavelinux_
[23:06:43] *** mojavelinux_ is now known as mojavelinux
[23:07:14] <lightguard_jp> It's unfortunate that nearly all of the issues are being pushed back to 3.2 :(
[23:10:56] <lightguard_jp> How in maven can you tell it to jar up your web classes instead of putting them in WEB-INF/classes?
[23:11:45] <lincolnthree> web classes?
[23:12:20] <lincolnthree> you mean you want to make a jar of all the classes that would normally just be in the WAR?
[23:12:26] <lincolnthree> and then bundle that JAR in the WAR?
[23:14:48] <lightguard_jp> Yep
[23:14:49] <lightguard_jp> http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html
[23:14:59] <lightguard_jp> That looks like it has the needed options
[23:15:24] <mojavelinux> yep, it's certainly possible, just annoying for instant deployment
[23:15:33] <lightguard_jp> Yeah
[23:15:53] <lightguard_jp> Trying to help Jason Lee with his problems on GF, seeing if putting his classes in a jar work
[23:16:10] <lightguard_jp> deployment in Java EE in general needs an overhaul.
[23:16:26] <lightguard_jp> That's why there's stuff like fakereplace and jRebel out there
[23:16:49] <lightguard_jp> Not that those aren't good solutions, but if you need a third party option to plug a hole in the platform it's time to fix the platform
[23:17:00] <mojavelinux> seriously...I was dev'ing that java ee 6 tutorial the other day
[23:17:07] <mojavelinux> constant crashing of the app server from redeploy
[23:17:10] <mojavelinux> dumb redeploy
[23:17:25] <lightguard_jp> perm gen?
[23:17:25] <mojavelinux> I finally had to turn it off
[23:17:33] <mojavelinux> but then it's like such a big cycle for every change
[23:17:46] <mojavelinux> not perm gen, now it's just that it's constantly registering and deregistering stuff
[23:17:49] <mojavelinux> and it gets confused
[23:17:56] <lightguard_jp> Nice
[23:18:07] <mojavelinux> not to mention, I refactor a class
[23:18:16] <mojavelinux> but don't fix all the usages, it's already off redeploying
[23:18:21] <mojavelinux> I don't like instant redeployment
[23:18:24] <mojavelinux> only web files
[23:18:30] <mojavelinux> why can't IDE vendors get the difference?
[23:18:34] <mojavelinux> maybe IntelliJ does
[23:18:46] <lightguard_jp> Ah Eclipse trying to "help you"
[23:18:54] <mojavelinux> more like f me
[23:19:04] <lightguard_jp> IntelliJ doesn't deploy unless you tell it to.
[23:19:21] <lightguard_jp> Though for me personally I use the command line most of the time
[23:19:29] <lightguard_jp> dev in the IDE build and deploy via CLI
[23:19:50] <lightguard_jp> Maybe slightly slower, but I like it better.
[23:20:01] <mojavelinux> yep
[23:20:14] <mojavelinux> I just like to get away from having to redeploy by just writing arquillian tests
[23:20:31] <mojavelinux> yes, it still redeploys, but it's much more controlled and I get the results and an undeploy right away
[23:20:42] <mojavelinux> rather than having to go check something in a browser, toggling context
[23:27:42] *** tsurdilo1 has joined #seam-dev
[23:30:06] *** tsurdilo has quit IRC
[23:31:39] *** cbrock has quit IRC
[23:43:36] *** cbrock has joined #seam-dev
[23:43:36] *** cbrock has quit IRC
[23:43:36] *** cbrock has joined #seam-dev
[23:45:23] *** tsurdilo2 has joined #seam-dev
[23:47:08] *** tsurdilo1 has quit IRC
[23:47:27] *** rruss has quit IRC
[23:57:10] <jbossbot> git [catch] push master 6bad0a0.. LightGuard Fixes https://issues.jboss.org/browse/SEAMCATCH-26...
[23:57:10] <jbossbot> jira [SEAMCATCH-26] Make caught exception available as named bean [Open, Minor, Jason Porter] https://issues.jboss.org/browse/SEAMCATCH-26
[23:57:10] <jbossbot> git [catch] push master URL: http://github.com/seam/catch/compare/dfac436...6bad0a0





top