[00:02:48] *** rruss1 has quit IRC [00:03:16] *** rruss has joined #seam-dev [00:56:16] *** stuartdouglas has quit IRC [00:56:40] *** stuartdouglas has joined #seam-dev [01:04:43] *** cbrock has quit IRC [01:10:52] *** nickarls has joined #seam-dev [01:12:13] *** bleathem has quit IRC [01:19:58] *** lightguard_jp has quit IRC [01:21:29] *** daniel_hinojosa has quit IRC [01:28:32] *** rruss has quit IRC [01:33:54] *** johnament has joined #seam-dev [01:40:23] *** cbrock has joined #seam-dev [01:40:24] *** cbrock has quit IRC [01:40:24] *** cbrock has joined #seam-dev [02:04:16] *** daniel_hinojosa has joined #seam-dev [02:10:12] *** daniel_hinojosa has quit IRC [02:16:25] *** daniel_hinojosa has joined #seam-dev [02:25:00] *** ssachtleben has quit IRC [02:37:34] *** cbrock has quit IRC [02:38:52] <johnament> DOH! [03:10:44] *** daniel_hinojosa has quit IRC [03:11:26] *** daniel_hinojosa has joined #seam-dev [03:33:37] *** tsurdilo has quit IRC [03:42:08] *** cbrock has joined #seam-dev [03:42:09] *** cbrock has quit IRC [03:42:09] *** cbrock has joined #seam-dev [04:00:50] *** johnament has quit IRC [04:10:51] *** rruss has joined #seam-dev [04:45:59] <jbossbot> git [remoting] push master 0faea2b.. Shane Bryzak update dependencies [04:45:59] <jbossbot> git [remoting] push master URL: http://github.com/seam/remoting/compare/3db44b3...0faea2b [04:47:57] *** bleathem has joined #seam-dev [05:01:42] *** lincolnthree has left #seam-dev [05:34:14] *** cbrock has quit IRC [05:40:02] <jbossbot> git [conversation] push master 923a95b.. Shane Bryzak update dependency scopes [05:40:02] <jbossbot> git [conversation] push master URL: http://github.com/seam/conversation/compare/a3e06f8...923a95b [06:10:31] *** nraf has joined #seam-dev [06:28:03] <nraf> Hey, I was wondering if the following is possible. I have an application that requires all users that are on a certain page to retrieve data as it arrives from the server (atm, using a4j push). I was wondering if there was anyway from the application context to retrieve any natural conversations named 'feeds' for example. [06:28:45] <nraf> I could set up a listener in the JSF and have it update when an event occurs, but my issue is being able to track all relavant conversations. [06:28:59] <jbossbot> git [remoting] push master 35b5220.. Shane Bryzak update distribution structure [06:28:59] <jbossbot> git [remoting] push master URL: http://github.com/seam/remoting/compare/0faea2b...35b5220 [06:29:03] <nraf> Including, for example, a user logged in two different browsers / tabs. [06:29:30] <nraf> Any ideas? [06:30:31] *** bleathem has quit IRC [06:49:16] <jbossbot> git [remoting] push master 0aba7b8.. Shane Bryzak fix model example [06:49:16] <jbossbot> git [remoting] push master URL: http://github.com/seam/remoting/compare/35b5220...0aba7b8 [07:00:38] <jbossbot> git [remoting] push master 495c644.. Shane Bryzak [maven-release-plugin] prepare release 3.0.0.CR1 [07:00:39] <jbossbot> git [remoting] push master URL: http://github.com/seam/remoting/compare/0aba7b8...495c644 [07:00:52] <jbossbot> git [remoting] push master 8b686b1.. Shane Bryzak [maven-release-plugin] prepare for next development iteration [07:00:52] <jbossbot> git [remoting] push master URL: http://github.com/seam/remoting/compare/495c644...8b686b1 [07:02:04] <jbossbot> git [remoting] push master 5e0b6e0.. Shane Bryzak [maven-release-plugin] rollback the release of 3.0.0.CR1 [07:02:04] <jbossbot> git [remoting] push master URL: http://github.com/seam/remoting/compare/8b686b1...5e0b6e0 [07:04:47] *** daniel_hinojosa has quit IRC [07:05:49] <jbossbot> git [remoting] push master f55f7ef.. Shane Bryzak SEAMREMOTING-26 [07:05:51] <jbossbot> jira [SEAMREMOTING-26] Remove / update license headers [Open (Unresolved) Task, Minor, Shane Bryzak] https://issues.jboss.org/browse/SEAMREMOTING-26 [07:05:51] <jbossbot> git [remoting] push master URL: http://github.com/seam/remoting/compare/5e0b6e0...f55f7ef [07:19:24] *** oskutka has joined #seam-dev [07:24:44] *** nraf has quit IRC [07:26:43] *** rruss has quit IRC [07:35:17] *** lukaszlenart has joined #seam-dev [08:00:15] *** koentsje has joined #seam-dev [08:06:02] *** daniel_hinojosa has joined #seam-dev [08:12:00] *** daniel_hinojosa has quit IRC [08:14:55] *** jharting has joined #seam-dev [09:09:42] *** mgencur has joined #seam-dev [10:04:14] *** epbernard has joined #seam-dev [10:06:01] *** epbernard has left #seam-dev [10:07:25] *** marekn has joined #seam-dev [10:19:07] <jbossbot> git [remoting] push master 9d4e8e0.. Shane Bryzak SEAMREMOTING-20 [10:19:09] <jbossbot> jira [SEAMREMOTING-20] The model example does not work as expected [Reopened (Unresolved) Bug, Major, Shane Bryzak] https://issues.jboss.org/browse/SEAMREMOTING-20 [10:19:09] <jbossbot> git [remoting] push master URL: http://github.com/seam/remoting/compare/f55f7ef...9d4e8e0 [10:24:07] *** kpiwko has joined #seam-dev [10:26:13] <jbossbot> git [remoting] push master 01ab252.. Shane Bryzak [maven-release-plugin] prepare release 3.0.0.CR1 [10:26:14] <jbossbot> git [remoting] push master URL: http://github.com/seam/remoting/compare/9d4e8e0...01ab252 [10:29:16] <jbossbot> git [remoting] push master ec1c23f.. Shane Bryzak [maven-release-plugin] rollback the release of 3.0.0.CR1 [10:29:17] <jbossbot> git [remoting] push master URL: http://github.com/seam/remoting/compare/01ab252...ec1c23f [10:31:40] <jbossbot> git [remoting] push master f237744.. Shane Bryzak [maven-release-plugin] prepare release 3.0.0.CR1 [10:31:40] <jbossbot> git [remoting] push master URL: http://github.com/seam/remoting/compare/ec1c23f...f237744 [10:31:56] <jbossbot> git [remoting] push master f56ca43.. Shane Bryzak [maven-release-plugin] prepare for next development iteration [10:31:56] <jbossbot> git [remoting] push master URL: http://github.com/seam/remoting/compare/f237744...f56ca43 [10:34:26] *** jharting has quit IRC [10:39:13] *** sannegrinovero has joined #seam-dev [10:46:57] *** jharting has joined #seam-dev [10:51:49] *** alesj has joined #seam-dev [11:11:33] *** oskutka has quit IRC [11:12:25] *** oskutka has joined #seam-dev [11:14:54] *** jharting is now known as jharting_away [11:37:06] <jbossbot> git [wicket] push master 51bf364.. Shane Bryzak update parent and seam-bom versions [11:37:06] <jbossbot> git [wicket] push master URL: http://github.com/seam/wicket/compare/5128aa4...51bf364 [11:40:17] *** rruss has joined #seam-dev [11:40:36] *** rruss has quit IRC [11:49:24] *** lukaszlenart has quit IRC [12:11:37] *** maschmid has joined #seam-dev [12:36:50] *** stuartdouglas has quit IRC [12:42:53] <jose_freitas> jharting_away: about the name seam-javaee-booking I guess it's because it demonstrates a lot of javaee features, it's a name dan picked I guess. [12:50:23] *** stuartdouglas has joined #seam-dev [13:32:27] *** emmanuel has joined #seam-dev [14:08:46] *** balunasj has joined #seam-dev [14:34:59] *** sannegrinovero has quit IRC [14:53:43] *** marekn has quit IRC [14:54:35] *** jharting_away is now known as jharting [14:55:00] <jharting> jose_freitas: ok, I'll try to bring it up tomorrow on the team meeting [14:56:01] <jharting> jose_freitas: did you get a chance to look at how the registration / password change functionality can be enabled temporarily? [14:58:15] <jose_freitas> I'll pull a request today about that [14:58:31] <jose_freitas> didn't have the time yet [14:59:40] <jharting> jose_freitas: ok, np [15:00:08] *** monkeyden has joined #seam-dev [15:01:38] *** emmanuel has quit IRC [15:07:31] *** sannegrinovero has joined #seam-dev [15:07:43] *** balunasj is now known as balunasj_mtg [15:22:16] *** pmuir has joined #seam-dev [15:23:34] *** clerum has joined #seam-dev [15:42:48] *** jharting is now known as jharting_away [15:59:34] *** bdlink has joined #seam-dev [16:06:38] *** lightguard_jp has joined #seam-dev [16:15:48] *** marekn has joined #seam-dev [16:34:26] *** tsurdilo has joined #seam-dev [16:37:31] *** lincolnthree has joined #seam-dev [16:45:38] *** bdlink has quit IRC [16:54:57] *** oskutka has quit IRC [16:59:07] *** bleathem has joined #seam-dev [17:03:18] *** daniel_hinojosa has joined #seam-dev [17:09:04] *** marekn has left #seam-dev [17:12:05] <jbossbot> git [faces] push master 48f1be6.. Marek Schmidt Fix short-ly example to run on both JBoss6 and Glassfish3.1 [17:12:05] <jbossbot> git [faces] push master URL: http://github.com/seam/faces/compare/7c7c3ac...48f1be6 [17:23:08] *** rruss has joined #seam-dev [17:34:55] *** clerum has quit IRC [17:35:22] *** alesj has quit IRC [17:41:08] *** ssachtleben has joined #seam-dev [17:41:17] <ssachtleben> hi [17:41:40] <ssachtleben> anyone familiar with weld 1.1.0 Final and long running conversation in arquillian? [17:41:49] *** jganoff has joined #seam-dev [17:42:18] <lightguard_jp> ssachtleben: Haven't had to deal with it yet, sorry [17:42:32] <lightguard_jp> ssachtleben: Try asking in #weld [17:47:28] <ssachtleben> k [17:49:39] *** johnament has joined #seam-dev [17:49:46] <jose_freitas> high level heh ssachtleben =) [17:50:17] <johnament> oh, the gang's all here of who i was looking for. [17:50:26] <johnament> jganoff: ping [17:51:33] <jganoff> johnament, pong [17:51:52] <jganoff> johnament, I've been following along with the JIRA activity and figured I'd hop on to see if you needed anything [17:52:15] <johnament> jganoff: funny, i was following it too. and decided to hop in on webchat to see who was around. [17:52:41] <johnament> did you happen to see my tweet of what happens when message firing goes awry :-) [17:53:22] <jganoff> johnament, I did, that was good :P [17:53:46] <johnament> jganoff: no, bad :-( [17:53:54] <jganoff> johnament, well funny and bad. [17:53:59] <johnament> jganoff: yes funny [17:54:04] <jganoff> johnament, So, definitely need @Async [17:54:14] <johnament> jganoff: code base already has it... [17:54:47] <johnament> jganoff: it looks like weld ignores the qualifiers when firing an event. [17:55:02] <johnament> at least against an observer method implementation [17:55:10] <jganoff> johnament, oh, crap. [17:56:06] <johnament> jganoff: i need to do a bit more testing. i tried it this morning using my demo app (since i no longer trust arquillian 100%) using local qualifiers, and the same thing occurred. [17:56:17] <johnament> err not the same thing, but the event fired when it shouldn't have. [17:57:18] <jganoff> johnament, ah alright. I'll check out your latest changes on github and see if I see something [17:57:23] <jganoff> johnament, bbl, lunch time here! [17:57:32] <johnament> e.g. i'm doing @Inject Event<String> sHandler; but the observer method is @Observes @Special Strings [17:57:38] <johnament> jganoff: enjoy [18:01:31] *** mgencur has left #seam-dev [18:04:38] <ssachtleben> johnament: @Inject @Special Event<String> sHandler [18:04:50] <johnament> ssachtleben: that's how it should activate, correct. [18:05:02] <johnament> but it's also activating when i do @Inject Event<String> sHandler; [18:05:14] <ssachtleben> ah ok ^^ [18:05:29] <johnament> which is the part i'm confused about :-) [18:06:09] <lightguard_jp> johnament: That's in 1.1? [18:07:09] <johnament> lightguard_jp: i guess whichever ships with AS 6. I'm not as bleeding edge as bleathem [18:07:12] <johnament> :-) [18:07:42] <ssachtleben> i think its 1.0.1.?? [18:07:55] <johnament> i believe its one of the CR's for 1.1. [18:08:06] <johnament> brb gotta go to the bird cage. [18:08:10] <lightguard_jp> Can you recreate it with just simple observers and events w/o jms? If so, that's amazingly broken. [18:08:13] <ssachtleben> i'm just using custom events for event throwing each works fine [18:09:30] *** balunasj_mtg is now known as balunasj_away [18:09:32] <johnament> lightguard_jp: i believe it's specific to creating custom observer method impls and registering them in ABD. [18:10:07] <lightguard_jp> Ah [18:10:12] <lightguard_jp> That may be. [18:10:44] <lightguard_jp> You may be inadvertently adding @Any to the observer. [18:11:40] <johnament> i doubt it. i put a log message in the getQualifiers method, it's returning empty. [18:11:49] <ssachtleben> [Version] WELD-000900 1.1.0 (CR3) [18:12:00] <ssachtleben> is shipped with jboss 6.0.0 final [18:12:25] <lightguard_jp> Wow, that's really odd then. [18:12:54] <lightguard_jp> johnament: This is using lincolnthree's event bus idea? [18:28:14] *** maschmid has quit IRC [18:29:20] <johnament> lightguard_jp: lincolnthree has an event bus idea? [18:29:49] <lincolnthree> johnament: yep [18:29:51] <lightguard_jp> Yeah, probably very similar to what you're doing [18:30:07] <lincolnthree> 1 sec [18:30:14] <johnament> 1 mississippi [18:30:35] <lightguard_jp> That was 7 seconds [18:30:37] <lincolnthree> https://github.com/seam/forge/tree/master/event-bus [18:30:50] <lincolnthree> https://github.com/seam/forge/blob/master/event-bus/src/test/java/org/jboss/seam/forge/bus/cdi/ObserverCaptureExtensionTest.java [18:30:53] <lightguard_jp> lincolnthree: Hehe, one of these days you need to finish that :P [18:31:02] <lincolnthree> or get johnament to do it for me :) [18:31:08] <lightguard_jp> haha [18:31:24] <lincolnthree> problem is, of all the things forge needs to do, this is on the low end :( [18:33:50] <johnament> i don't think i'm doing the same thing in Seam JMS [18:34:09] <johnament> the goal of Seam JMS right now is to be able to take an event, fire it on JMS, which gets processed down stream as an object message. [18:34:39] <johnament> if an object message comes in that's an event, we refire it with a new qualifier (@Async) to allow it to be processed behind the scenes. [18:35:04] <lightguard_jp> object message? yuck, map or xml payload instead of object? [18:35:22] <bleathem> lightguard_jp Bit of a problem with what we did to the Faces/Catch integration last week [18:35:35] <johnament> i had theorized that CDI events could be done async without using a jMS destination, but we're doing it. [18:35:54] <johnament> lightguard_jp: you don't want to send overly complex data over JMS. in this case, we serialize the event object and send it off. [18:35:55] *** clerum has joined #seam-dev [18:36:27] <lightguard_jp> johnament: Well, they're typically small objects. [18:36:31] <lightguard_jp> bleathem: What's that? [18:36:39] <bleathem> Any exceptions thrown in catch are swallowed, even genuine ones [18:36:40] <johnament> saves on time processing an XML message where the underlying data type may not be XML savy [18:36:48] <bleathem> for instance if my handler throws an NPE [18:36:52] <bleathem> it gets swallowed [18:36:56] <johnament> lightguard_jp: what if i fire an entity over this route? [18:36:57] *** kpiwko has quit IRC [18:37:16] <lightguard_jp> bleathem: Swallowed? Shouldn't JSF run with it? [18:37:38] <bleathem> it runs with the original exception [18:37:50] <bleathem> the one thrown (or rethrown) in catch is swallowed [18:38:03] <lightguard_jp> johnament: Hopefully it's serializable one, but if you're sending a lot of messages it'll bog down. Object Messages are slow. [18:38:08] <lightguard_jp> compared to map or text. [18:38:25] <lightguard_jp> bleathem: Hm [18:38:31] <bleathem> I'll look into whether we can insert that exception into the JSF exception "queue" (or whatever it's called) [18:39:03] <bleathem> but with the conversation creating exception I've been investigating [18:39:09] <lightguard_jp> bleathem: That may work, but because we're already iterating over it, maybe not. [18:39:22] <lightguard_jp> We may have to add it to a temp queue and add them in after the iteration. [18:39:27] <bleathem> All I see in the server log is the original exception that catch wastrying to handle [18:39:43] <bleathem> yeah, or throw it after exception handling is done [18:40:04] <bleathem> anyways, no biggie, just an FYI [18:42:27] <johnament> lightguard_jp: i send 12 object messages an hour from 450 stores (5400 total msgs/hr) across the US, AS 6 has no issue processing them all. [18:42:39] <johnament> server side is a single 2gb instance. [18:42:56] <lightguard_jp> bleathem: Thanks for letting me know, if you want me to look over any code you craft for it, let me know. [18:43:16] <bleathem> sure thing [18:43:34] <bleathem> I'm thinking that what we really want to handle is the rethrow case [18:43:38] <lightguard_jp> johnament: Okay, we're not talking about large quantities of messages. [18:43:42] <bleathem> so any new exception is indeed exceptional [18:43:54] <lightguard_jp> bleathem: Makes sense [18:43:57] <johnament> lightguard_jp: that's not a large quantity? [18:44:02] <bleathem> it should be trivial to compare the exception caught to the exception handled, [18:44:09] <bleathem> and halt if it's a new exception [18:44:19] <bleathem> I'll jira that thought shortly [18:44:30] <lightguard_jp> johnament: If you were sending that many per minute, I'd say yes :) [18:44:36] <bleathem> jira is the best. It's my long-term memory [18:46:13] <lightguard_jp> johnament: http://hornetq.sourceforge.net/docs/hornetq-2.1.2.Final/user-manual/en/html/perf-tuning.html#d0e11462 third bullet [18:46:43] <jose_freitas> offtopic (sorry): does someone knowns a good software for software architecture design? [18:48:06] <johnament> lightguard_jp: i think this describes Seam JMS though: Only use ObjectMessage if you really can't use one of the other message types, i.e. if you really don't know the type of the payload until run-time [18:48:18] <bleathem> jose_freitas: pen & paper ? [18:48:22] <bleathem> :P [18:48:34] <johnament> jose_freitas: for marking up systems? designing software? [18:49:54] <lightguard_jp> johnament: You're probably right [18:50:36] <jose_freitas> bleathem: pen and paper is not enough for my boss. lol [18:51:27] <jose_freitas> johnament: not sure if I understood what you mean by marking up systems [18:53:12] <bleathem> jose_freitas: what tasks are you trying to achieve? software architecture is a broad topic... [18:53:45] <lincolnthree> #Seam-render 1.0.0.Alpha1 released - Fast composite-templating with CDI integration, based on MVEL. ( http://bit.ly/ghr5CX ) [18:53:54] <lincolnthree> And absolutely 0 docs. [18:53:57] <lincolnthree> Good luck everybody! [18:54:31] <johnament> lightguard_jp: in general, you don't want XML in your message http://hornetq.sourceforge.net/docs/hornetq-2.1.2.Final/user-manual/en/html/perf-tuning.html#d0e11711 see bullet 2 [18:54:32] <bleathem> lincolnthree right on! you're a software factory! [18:54:43] <johnament> lincolnthree: did you build that using forge? [18:55:10] <johnament> no angry rooster or hidden panda subtitle? [18:55:10] <lincolnthree> yeah.... [18:55:14] <lincolnthree> lol [18:56:19] <lightguard_jp> johnament: That makes sense too (the link) [18:57:00] <lincolnthree> sbryzak: http://twitter.com/#!/lincolnthree/status/40830240326426624 - this is something we can run with if we have time [18:57:16] <lincolnthree> If not, it can stay as-is. I need it for forge, but it could also be used in seam-mail [18:57:29] <lincolnthree> clerum: you might be interested also [18:57:56] <johnament> probably seam rest would be interested in it too [18:59:13] <lincolnthree> johnament: ah yes, very true [18:59:22] <lincolnthree> eventually I imagine it going into an aggregate seam-mvc [18:59:25] <lincolnthree> which I also have started [18:59:28] <lincolnthree> but needs a LOT of work [18:59:35] <lincolnthree> https://github.com/lincolnthree/seam-mvc [19:02:39] <johnament> lightguard_jp: i do see potential in switching out object message for map message, but the main payload of the data would still be a serialized object, so i'm not sure it would be any better performance wise. [19:03:01] <lightguard_jp> johnament: Probably not [19:03:33] <johnament> lightguard_jp: with the way everything's defined right now, we haven't even begun to look at distributed event processing. if you bring up a hornetq cluster w/ the app on it, it can be processed in a different instance. [19:03:37] <lightguard_jp> johnament: I'd just stick to what you have right now and if someone complains about perf then start looking into other options. [19:03:57] *** rruss has quit IRC [19:04:00] <johnament> lightguard_jp: one of the main things we need to make clear is that all event payload needs to be serializable. [19:04:08] <lightguard_jp> Yep [19:45:45] *** sannegrinovero has quit IRC [19:52:05] *** johnament has quit IRC [19:56:57] *** clerum has quit IRC [19:59:19] *** jharting_away is now known as jharting [20:02:05] *** clerum has joined #seam-dev [20:05:05] *** sannegrinovero has joined #seam-dev [20:13:52] <jose_freitas> bleathem: ping [20:29:24] *** jose_freitas has quit IRC [20:32:45] *** jose_freitas has joined #seam-dev [20:34:26] *** pmuir has quit IRC [20:34:41] *** balunasj_away is now known as balunasj [20:34:45] *** tsurdilo has quit IRC [20:35:12] *** tsurdilo has joined #seam-dev [20:45:47] <jose_freitas> hello guys, what do you think about this discussion? [20:45:50] <jose_freitas> http://www.theserverside.com/news/thread.tss?thread_id=60620 [20:45:58] <jose_freitas> it goes about this article [20:45:59] <jose_freitas> http://manidoraisamy.blogspot.com/2010/07/why-does-elastic-nature-of-cloud-impose.html [20:46:29] <jose_freitas> where the author states that a stateless architecture is the way to go [20:47:05] <jose_freitas> since seam is a framework designed for a stateful system [20:47:37] <jose_freitas> is there something designed to workaround this problem? [20:57:28] *** ssachtleben has quit IRC