[00:03:33] *** koentsje has quit IRC
[00:04:11] *** wdrai has joined #seam-dev
[00:06:37] *** gastaldi has joined #seam-dev
[00:08:31] <gastaldi> heyho
[00:08:56] 
[00:15:01] <Diablo-D3> oh god what
[00:15:14] <gastaldi> ?
[00:16:22] <Diablo-D3> lemme verify this before I say anything
[00:16:53] <daniel_hinojosa> Preventing class org.jboss.seam.servlet.http.HttpServletRequestContext from being installed as bean due to @Veto annotation
[00:17:49] <daniel_hinojosa> anyone seen that?
[00:18:08] <Diablo-D3> that specific one? dunno
[00:18:14] <Diablo-D3> but my jboss log is full of those
[00:18:22] <Diablo-D3> theres a bunch of vetoed classes
[00:18:44] <bleathem> its supposed to be like that as far as I know danno
[00:18:57] <Diablo-D3> http://www.thoughtsabout.net/blog/archives/000033.html
[00:19:00] <daniel_hinojosa> ok thanks
[00:19:06] <Diablo-D3> see the getFacesContext method
[00:19:08] <bleathem> Solder has the @Veto annotation, so one can prevent classes from being installed as beans
[00:19:48] <bleathem> I think it's in the works to be in CDI 1.1 (@Veto)
[00:20:30] <bleathem> danno = daniel_hinojosa  and   dan = mojavelinux
[00:20:35] <bleathem> handy shortcuts
[00:20:47] <bleathem> yet not ambiguous
[00:20:54] *** gastaldi has quit IRC
[00:21:50] <daniel_hinojosa> ha
[00:22:27] <bleathem> I wich my IRC client offered name completion the way twitter clients do
[00:23:36] <stuartdouglas> most do
[00:24:25] <stuartdouglas> XChat does on linux, although it does not have much else going for it
[00:24:38] <bleathem> I'm using Konversation
[00:25:09] <lightguard_jp> Using Irssi here
[00:25:13] <lightguard_jp> It has complete
[00:25:36] <Diablo-D3> irc clients have had tab complete since the dawn of time
[00:25:40] <stuartdouglas> after using Colloquy on the mac, I have not found a linux IRC client I like
[00:27:24] <lincolnthree> sbryzak: working on getting forge out the door for you, having some issues with final testing
[00:28:06] <Diablo-D3> 18:27:53,557 INFO  [org.jboss.seam.solder.core.CoreExtension] Preventing class org.jboss.seam.servlet.http.HttpServletRequestContext from being installed as bean due to @Veto annotation
[00:28:07] <Diablo-D3> btw
[00:28:10] <Diablo-D3> its normal
[00:28:23] <daniel_hinojosa> thx Diablo-D3
[00:30:42] *** Royle has joined #seam-dev
[00:31:14] *** cbrock has joined #seam-dev
[00:31:15] *** cbrock has quit IRC
[00:31:15] *** cbrock has joined #seam-dev
[00:32:40] *** PeteRoyle has quit IRC
[00:32:41] *** Royle is now known as PeteRoyle
[00:34:10] *** gastaldi has joined #seam-dev
[00:34:19] <gastaldi> stuartdouglas: LOL
[00:34:39] <gastaldi> stuartdouglas: I am still laughing on your last tweet
[00:35:03] <stuartdouglas> security at it's finest :-)
[00:35:13] <gastaldi> yeah !!
[00:35:15] <gastaldi> haha
[00:35:22] <Diablo-D3> url
[00:35:23] 
[00:35:31] <gastaldi> http://www.cadw.wales.gov.uk
[00:35:36] <gastaldi> view-source on it
[00:35:55] <Diablo-D3> lol
[00:36:05] <Diablo-D3> I told that one to #perlcafe earlier
[00:36:07] <Diablo-D3> they thought it was a riot
[00:36:10] <Diablo-D3> gastaldi: btw
[00:36:19] <Diablo-D3> it may not be a sql injection protector
[00:36:38] <Diablo-D3> even though theres sql keywords in the filter list
[00:36:54] <gastaldi> Diablo-D3: lol, only if they where teaching SQL somehow
[00:37:06] <Diablo-D3> either way
[00:37:10] <Diablo-D3> this is serious wtfery
[00:37:39] <gastaldi> This makes me laugh out loud: http://2.bp.blogspot.com/_isk1o8_XWYA/R0ML6q6-HYI/AAAAAAAAAtY/_bm0dffd6Gc/s1600-h/exploits_of_a_mom.png
[00:37:40] <stuartdouglas> either way, stuff like that does not belong on the client side
[00:38:06] <Diablo-D3> hn got a laugh out of it though
[00:38:16] <gastaldi> Little bobby tables
[00:38:18] <gastaldi> hahaha
[00:38:25] <Diablo-D3> also, I think EVERYONE made that joke
[00:38:38] <Diablo-D3> and I made that joke on the mysql.com sql exploit the other day
[00:38:46] <gastaldi> yeah, what a mess
[00:39:02] 
[00:39:17] 
[00:40:08] <Diablo-D3> yes, but mysql owned by their own software
[00:40:16] <Diablo-D3> justice has been served
[00:40:50] <gastaldi> haha true
[00:41:08] <gastaldi> mysql really sucks
[00:41:21] <gastaldi> as glassfish.. Ooops, sorry bleathem
[00:41:28] <gastaldi> :)
[00:43:01] <gastaldi> I believe that when JBoss AS 7 be released, all other app servers will crumble to dust
[00:43:24] <bleathem> hopefully!
[00:43:34] <bleathem> and hopfully Glassfish in turn tries to outdo AS 7
[00:43:43] <gastaldi> lol
[00:43:46] <gastaldi> And die
[00:43:47] <bleathem> then we the consumer will really win
[00:43:48] <Diablo-D3> as 7 being released will herald the second coming of jesus
[00:44:55] 
[00:45:13] <gastaldi> It makes my stomach hurt when the work is pronounced
[00:45:16] <Diablo-D3> it doesnt help oracle forcequit half of the glassfish team
[00:45:19] <gastaldi> word
[00:45:49] <gastaldi> It only they could work for Red Hat on JBoss AS 7 ...
[00:46:25] <Diablo-D3> well, google seems to be soaking up all the talent so
[00:46:30] <Diablo-D3> soon as google buys redhat, etc etc
[00:46:41] <gastaldi> haha, in Brazil they are very close
[00:46:59] <gastaldi> Google is a floor beneath Red Hat in the same building
[00:47:52] <gastaldi> I believe Gosling made it to Google in order to fix things up
[00:48:06] <Diablo-D3> I can imagine him showing up
[00:48:07] <bleathem> aack! irssi is curses based!
[00:48:13] <Diablo-D3> barefoot, white robes
[00:48:15] <bleathem> how do I quit it!
[00:48:16] <gastaldi> haha
[00:48:28] <Diablo-D3> and everyone worshiping the floor hes walking on as he comes in the building
[00:48:40] <gastaldi> haha, jesus has come
[00:49:22] <gastaldi> A cup on java instead of the cross marks
[00:49:25] * bleathem hats off to lightguard_jp for using a curses based IRC client.  That's hardcore!
[00:50:04] <bleathem> ahh, found it: /quit
[00:50:32] * bleathem yum remove irssi
[00:50:48] <Diablo-D3> lol
[00:50:51] <Diablo-D3> epic4 or whatever
[00:51:25] <gastaldi> gotta go
[00:51:27] <gastaldi> see ya
[00:51:46] *** gastaldi has quit IRC
[00:51:46] <Diablo-D3> seeya
[01:06:03] *** bleathem has quit IRC
[01:07:26] *** bleathem has joined #seam-dev
[01:07:37] *** aslak has quit IRC
[01:08:21] <bleathem> ooh lala, KVIRC >> Konversation
[01:08:33] <bleathem> gonna take a little getting used to though
[01:15:03] <bleathem> what does an alert look like in kvirc bleathem
[01:18:09] *** clerum1 has quit IRC
[01:18:24] *** clerum has joined #seam-dev
[01:18:48] <Diablo-D3> so
[01:18:58] <Diablo-D3> I dont think the openid rp stuff preserves messages no matter how hard I try
[01:19:18] *** clerum has quit IRC
[01:24:43] *** johnament has joined #seam-dev
[01:24:57] <Diablo-D3> I guess I could just forward to a page that sets the message and then have that page forward to the login page
[01:25:44] <johnament> pipe it to standard out, tell the user to read the server logs to determine what they did wrong.
[01:26:38] <johnament> lightguard_jp: children++ ?
[01:26:41] <Diablo-D3> johnament: hah
[01:26:55] <lightguard_jp> johnament: Not yet
[01:26:59] <johnament> Diablo-D3: i s you not. that's what we do at work.
[01:27:05] <johnament> sigh...
[01:27:19] <Diablo-D3> johnament: how does that help users who wanna know why their login failed?
[01:27:24] *** sannegrinovero has quit IRC
[01:27:26] <johnament> they call the help desk
[01:27:33] <Diablo-D3> a help desk for a website.
[01:27:41] <johnament> help desk tells them they have no idea what they're talking about and hang up.
[01:27:44] <johnament> :-)
[01:27:46] <lightguard_jp> I told my wife she can't have it Fri, Sat or Sun
[01:27:55] <johnament> lightguard_jp: traveling those days?
[01:28:04] <Diablo-D3> lightguard_jp: she'll just tie you to the bed and take it.
[01:28:06] *** clerum has joined #seam-dev
[01:28:08] <lightguard_jp> Between the current job and Red Hat
[01:28:12] <lightguard_jp> No insurance :)
[01:28:17] <johnament> ewww
[01:28:34] <johnament> that's why i don't do employer provided health care.
[01:28:37] <johnament> plus mines cheaper
[01:28:44] <Diablo-D3> it doesnt matter
[01:28:48] <Diablo-D3> health insurance in the US doesnt exist
[01:29:27] <johnament> true
[01:29:38] <Diablo-D3> file a claim? oh we canceled you 3 months ago.
[01:31:00] <jbossbot> git [jms] push master 00512e1.. John Ament Fixed missing title.
[01:31:01] <jbossbot> git [jms] push master URL: http://github.com/seam/jms/compare/0babbc8...00512e1
[01:34:09] *** clerum has quit IRC
[01:34:10] <johnament> lightguard_jp: actually, i was meaning to get a hold of you for the past few days.  i need to rewrite the JMS routing apis to work correctly
[01:34:58] <lightguard_jp> johnament: Doh
[01:35:04] <lightguard_jp> johnament: cleaner?
[01:35:24] <johnament> lightguard_jp: no, the issue where Jordan was trying to make them producer methods. it passed arquillian but failed in a real deployment.
[01:35:35] <johnament> sound familiar?
[01:35:35] <lightguard_jp> That sucks
[01:35:45] <lightguard_jp> Yeah
[01:36:12] <johnament> lightguard_jp: so what I'm thinking is putting back his old code - where the methods were denoted with @EventRouting.  There's an issue though
[01:36:38] <johnament> lightguard_jp: we need to provide some kind of factory class for use that is available during deployment to create instances of RouteImpl
[01:37:19] <johnament> lightguard_jp: since these are never going to be a managed object, I'm thinking that we should require that the class be @Veto
[01:37:31] <lightguard_jp> Makes sense
[01:37:39] <johnament> lightguard_jp: this way the user knows, this isn't a bean I'm working with
[01:37:41] <lightguard_jp> If it's not we could veto it
[01:38:13] <johnament> lightguard_jp: i'd prefer to fail the deployment "Classes with methods denoted @EventRouting must be veto'd"
[01:38:24] <lightguard_jp> That works too
[01:38:46] <johnament> lightguard_jp: because we'll run into issues if they try to access a managed object in their @EventRouting
[01:39:00] <lightguard_jp> Okay, I'm okay with that then.
[01:39:01] <johnament> lightguard_jp: or what we do, and I was sort of avoiding it, is make the methods static
[01:39:09] <lightguard_jp> eck
[01:39:21] <johnament> it's just a thought :-)
[01:40:07] *** clerum has joined #seam-dev
[01:40:08] <johnament> lightguard_jp: another one just popped in my head.  what if we enforced the need for an argument RouteManager, that had a single method .createNewRoute(constructor args)
[01:40:31] <lightguard_jp> Catch kinda set that precedent, could go that route too.
[01:40:35] <johnament> lightguard_jp: this way we give them a psuedo DI feel in the method
[01:41:09] * johnament tries to read catch again
[01:42:13] <lightguard_jp> Catch requires one of the methods to be CaughtException<? extends Throwable>
[01:42:48] <johnament> lightguard_jp: i see
[01:43:22] <johnament> lightguard_jp: i guess the big difference is that mine cannot be managed objects, where catch supports it
[01:43:34] <lightguard_jp> Right
[01:44:01] <lightguard_jp> Just saying the basic idea of requiring sigs of a certain type is already there.
[01:44:16] <lightguard_jp> So it wouldn't be too foreign.
[01:45:39] <jbossbot> git [forge] push master 9993bb7.. Lincoln Baxter, III fixed dependencyresolver once more- had to ensure version range requests looked like version ranges, static versions don't work
[01:45:40] <jbossbot> git [forge] push master URL: http://github.com/seam/forge/compare/d1ef770...9993bb7
[01:48:42] <johnament> lightguard_jp: yeah, i figure it won't be much of an issue
[02:15:20] *** wdrai has left #seam-dev
[02:20:23] <mojavelinux> I played around with AS7 a bit last night
[02:20:30] <mojavelinux> got a project with jsf and cdi working :)
[02:20:34] <lightguard_jp> Wow
[02:20:36] <mojavelinux> built with forge of course
[02:20:37] <lightguard_jp> Snags?
[02:20:40] <mojavelinux> however, jpa, no dice
[02:20:46] <mojavelinux> didn't load up hibernate
[02:20:50] <lightguard_jp> Not quite ready for JPA huh?
[02:20:51] <mojavelinux> not sure if it is supposed to work or not
[02:20:55] <mojavelinux> of course, I could use seam-persistence ;)
[02:21:19] <mojavelinux> it would be interesting to tweak the javaee archetype to use seam persistence, see if we can get that far
[02:21:20] <lightguard_jp> Sounds like a productive night (but maybe not for training)
[02:21:21] <mojavelinux> shouldn't be too hard
[02:21:26] <stuartdouglas> mojavelinux: If you use the AS7 from my master you may get JPA
[02:21:34] <mojavelinux> now there is a gift!
[02:21:48] <mojavelinux> the reason I'm trying this out, is that I'm doing this huge cdi /seam training in two weeks
[02:21:53] <mojavelinux> and it would be glorious to show AS 7
[02:21:57] <mojavelinux> and all I need now is jpa
[02:22:01] <mojavelinux> if I have that, we are golden
[02:22:02] <stuartdouglas> the one in trunk does not support war's yet, I fixed it yesterday but it has not been merged yet
[02:22:12] <mojavelinux> got it
[02:22:16] <mojavelinux> beta1 supported a war
[02:22:20] <mojavelinux> or supports a war
[02:22:34] <mojavelinux> oh, i see what you are saying
[02:22:36] <mojavelinux> persistence in a war
[02:22:37] <mojavelinux> got it
[02:22:40] <mojavelinux> man, I'm excited now!
[02:23:14] <mojavelinux> I have a small nit pick
[02:23:28] <mojavelinux> could we please extra it to jboss-as-7.0.x??
[02:23:43] <mojavelinux> that build script needs to get updated at some point, we inherited the crap from AS 6 in that case
[02:23:48] <mojavelinux> well, not crap, but legacy naming
[02:24:18] <mojavelinux> anyway, perhaps I should just jira it instead of complaining...sorry
[02:24:20] <mojavelinux> hahaha
[02:24:33] <mojavelinux> thanks stuart i'll let you know the results ;)
[02:24:40] <jbossbot> git [forge] push master ea64611.. Lincoln Baxter, III fixed broken tests. apparently arquillian has issues with @ApplicationScoped beans... changed to @Singleton works
[02:24:40] <jbossbot> git [forge] push master URL: http://github.com/seam/forge/compare/9993bb7...ea64611
[02:24:47] <mojavelinux> btw, we really need to start branching out from jboss as and glassfish in our testing
[02:24:56] <mojavelinux> the first step is to actually download something else I suppose
[02:25:08] <lincolnthree> sbryzak: mojavelinux: let me know before you do the Final release and I'll push forge out. just in final verifications now.
[02:25:14] <stuartdouglas> I am not sure when it will be merged, it is part of a much larger commit that will hopefully be merged later this week
[02:25:31] <mojavelinux> k, I can work from git for now...i'm sure we'll be in touch :)
[02:25:42] <lincolnthree> mojavelinux: if you have time. hammer on forge a little, maybe even go through the plugin docs and see what breaks: http://docs.jboss.org/forge/snapshot/reference/en-US/html_single/
[02:25:45] <mojavelinux> just got my virtualbox image with all the java goodness setup
[02:25:55] <mojavelinux> yes, I have a script I"ve been using lincoln
[02:26:02] <mojavelinux> and I know a couple things to test
[02:26:09] <lincolnthree> mojavelinux: do you? awesome, thanks
[02:26:12] <mojavelinux> right now I am desperately trying to close the gap between forge and the archetypes
[02:26:17] <johnament> mojavelinux: there's not many other containers out there yet.
[02:26:18] <lincolnthree> would love to see what you're doing
[02:26:24] <lincolnthree> mojavelinux: talk to mike about FPak
[02:26:26] <lightguard_jp> mojavelinux: We need arq containers for those other containers too
[02:26:28] <lightguard_jp> remote containers
[02:26:32] <mojavelinux> because the goal is to drop the archetypes, but I just haven't be able to yet until I hit all my starting points
[02:26:33] <lincolnthree> cbrock: has an archetype replacement
[02:26:52] <lincolnthree> gotta run though
[02:26:56] <mojavelinux> yeah, but i'm not necessarily needing an archetype
[02:27:02] <lincolnthree> gonna go crazy if i work another 16 hour day
[02:27:03] <mojavelinux> though of course, that is solid too
[02:27:05] <mojavelinux> hahah
[02:27:09] <lightguard_jp> mojavelinux: If you showcase AS 7 in training what's the response when people ask about AS6 and GF?
[02:27:11] <mojavelinux> i'm trying to build from 0
[02:27:21] <mojavelinux> i'm doing all three
[02:27:31] <mojavelinux> the idea is to show that the damn app works in more than one place
[02:27:38] <lightguard_jp> Cool.
[02:27:49] <mojavelinux> so far, that's been like banging our heads against stone :)
[02:27:59] <lightguard_jp> You could try Resin, I found that to be fairly close to AS6 when we were doing Solder testing
[02:28:14] <mojavelinux> yeah, I've installed it and done everything except deploy to it
[02:28:20] <lightguard_jp> Gotta remember it uses eclipselink though
[02:28:22] <mojavelinux> where I always get stuck is jpa
[02:28:43] <mojavelinux> because it's the one non-portable bit atm in java ee
[02:28:52] <mojavelinux> meaning, it requires a couple of tweaks per server to get it working
[02:28:59] <mojavelinux> yep
[02:29:01] <lightguard_jp> Isn't that the impls' fault?
[02:29:17] <mojavelinux> well, part of it is something so basic
[02:29:27] <mojavelinux> app servers should provide a default database with a universal standard name
[02:29:41] <mojavelinux> so that us people writing examples don't have to go through the damn pain of learning how to use 5 admin consoles :)
[02:29:58] <lightguard_jp> I still say use h2 and just tell people to install it.
[02:29:59] <johnament> mojavelinux: can't you deploy the datasource?
[02:30:01] <mojavelinux> jdbc/default or jdbc/sample would be grand
[02:30:05] <mojavelinux> haha
[02:30:13] <mojavelinux> deploying the datasource, see comment above ^
[02:30:22] <mojavelinux> 5 different datasource deployment mechanisms
[02:30:25] <johnament> isn't there a new annotation in EE 6 that can create a datasource?
[02:30:29] <lincolnthree> mojavelinux: lightguard_jp: forge can handle doing that if we write the plugin
[02:30:29] <mojavelinux> and this is hard to document in an example archetype
[02:30:30] <lightguard_jp> Yes
[02:30:42] <lincolnthree> johnament: not a JTA data source IIRC, i could be mistaken
[02:30:44] <lightguard_jp> @Datasource I believe
[02:30:45] <mojavelinux> yeah, that's why it's better in my mind to build up using forge
[02:30:49] <mojavelinux> so you can prompt
[02:30:57] <mojavelinux> yeah, but @Datasource is non JCA
[02:31:07] <mojavelinux> meaning, the connection properties have to be there
[02:31:11] <mojavelinux> and you also need the jar
[02:31:22] <mojavelinux> and GlassFish doesn't have HSQL
[02:31:26] <mojavelinux> and JBoss doesn't have Derby
[02:31:27] <lincolnthree> you need the jar for deployed DS anyway
[02:31:35] <mojavelinux> right, my point is
[02:31:37] <mojavelinux> we need 1 name
[02:31:44] <lightguard_jp> Can you use a jar in the war if you use @Datasource?
[02:31:55] <mojavelinux> yes, but then you are departing from the java ee experience
[02:32:16] <mojavelinux> steven and I have talked about this for quite some time, and always seem to come back to the same conclusion
[02:32:30] <mojavelinux> it would be nice if we could just have a standard default datasource on all servers for example writers
[02:32:34] <mojavelinux> okay, so it's not like a spec thing
[02:32:41] <mojavelinux> but just throw us a bone
[02:32:45] <lightguard_jp> pick your pain point :)
[02:33:13] <mojavelinux> because at the end of the day, the idea is to get a sample app working so that they care to even look how to setup a datasource
[02:33:38] <mojavelinux> but if you have to tell them to setup a datasource, then they aren't interested...this is the tipping point you have to deal with in advocacy
[02:33:46] <mojavelinux> you have them for a minute, so you need it to just work
[02:34:24] <mojavelinux> we've worked around it by having maven deploy default-ds.xml to jboss as
[02:34:31] <mojavelinux> to setup jdbc/__default
[02:34:36] <mojavelinux> and glassfish has jdbc/__default
[02:34:42] <mojavelinux> but there is a catch
[02:34:48] <mojavelinux> the one in glassfish is client-server and has to be started
[02:35:06] <mojavelinux> and as I've discovered, in glassfish 3.1, seems to have an undeployment problem where the schema is not being removed
[02:35:13] <mojavelinux> if the deployment fails part way through
[02:35:22] <mojavelinux> then you are totally borked, so that solution is degrading :)
[02:35:35] <johnament> i think they had that issue in 3.0 as well
[02:35:50] <mojavelinux> ah, so maybe I was just lucky enough not to have seen it yet
[02:36:02] <mojavelinux> anyways, forge is my blessing
[02:36:10] <mojavelinux> because it will let me prompt the developer :)
[02:36:12] <mojavelinux> stupid maven archetypes
[02:36:15] <mojavelinux> grrr
[02:36:28] <mojavelinux> they inherit the pain of their parent
[02:36:29] <mojavelinux> maven
[02:42:14] <lincolnthree> so does forge....
[02:42:16] <lincolnthree> adios. bbl
[02:44:19] <lightguard_jp> I'm out too. Be back later
[02:44:26] *** lightguard_jp has quit IRC
[03:02:22] *** cbrock has quit IRC
[03:04:49] *** jose_freitas has joined #seam-dev
[03:10:33] *** jose_freitas has quit IRC
[03:14:47] <johnament> let's see what this does
[03:20:16] *** jose_freitas has joined #seam-dev
[03:20:26] <jose_freitas> morning sbryzak
[03:33:37] *** jose_freitas has quit IRC
[03:39:58] *** tsurdilo has quit IRC
[03:45:08] <johnament> durrr it would help if i knew the code i just wrote actually is doing before i try to test it.
[03:54:40] *** johnament has quit IRC
[04:11:31] *** bleathem has left #seam-dev
[04:11:31] *** bleathem has joined #seam-dev
[04:12:26] *** bleathem has quit IRC
[04:12:44] *** bleathem has joined #seam-dev
[04:20:16] *** bleathem has quit IRC
[04:25:45] *** bleathem has joined #seam-dev
[04:41:40] *** gastaldi has joined #seam-dev
[04:41:47] <gastaldi> hey
[04:47:41] <gastaldi> hey emmanuel !!
[04:48:00] <gastaldi> the hibernate guy
[04:52:43] *** gastaldi has quit IRC
[05:01:27] *** lincolnthree has quit IRC
[05:11:06] <bleathem> It occurred to me that the work I'm doing to create an IPS package for Hibernate will be useful when we need one for Weld 1.1.1
[05:11:21] <bleathem> that is if the Glassfsih team doesn't do it themselves.
[05:14:13] *** clerum has quit IRC
[05:16:35] <bleathem> sorry, I guess that ^^ comment was a little out of context for anyone other than mojavelinux
[05:50:37] *** kuuyee has joined #seam-dev
[06:15:24] <bleathem> We need some maven archtypes for Seam 3
[06:15:38] <bleathem> For a handful of typical project configrations
[06:15:55] <bleathem> One for Faces only
[06:16:06] <bleathem> One for Faces, Catch, Security
[06:16:31] <bleathem> etc.
[06:16:34] *** lightguard_jp has joined #seam-dev
[06:16:44] <bleathem> hey lightguard_jp
[06:16:59] <bleathem> turns out Lonversation had username completion after all
[06:17:03] <bleathem> ^Konversation
[06:17:47] *** kuuyee has quit IRC
[06:18:20] *** lightguard_jp has quit IRC
[06:34:10] <mojavelinux> hey, we've got some maven archetypes
[06:34:25] <mojavelinux> they just don't have anything but Solder in them at this point
[06:34:32] <mojavelinux> http://tinyurl.com/gojavaee
[06:34:41] <mojavelinux> I'm going to update to Solder 3.0.0.CR4 shortly
[06:34:44] <mojavelinux> damn, bad news
[06:34:53] <mojavelinux> ShrinkWrap broke the location of META-INF in a web archive
[06:34:55] <mojavelinux> so if you do
[06:35:01] *** rruss has quit IRC
[06:35:14] <mojavelinux> .addAsManifestResource("test-persistence.xml", "persistence.xml") it ends up in /META-INF/persistence.xml
[06:35:17] <mojavelinux> ain't gonna work
[06:35:21] <mojavelinux> same for
[06:35:37] <mojavelinux> .addAsServiceProvider(Extension.class, MyExtension.class);
[06:35:39] <mojavelinux> that sux
[06:35:47] <mojavelinux> SHRINKWRAP-266
[06:35:49] <jbossbot> jira [SHRINKWRAP-266] Manifest container for WebArchive should be WEB-INF/classes/META-INF [Open (Unresolved) Bug, Major, Unassigned] https://issues.jboss.org/browse/SHRINKWRAP-266
[06:55:29] <bleathem> mojavelinux: mojarra source svn co https://svn.java.net/svn/mojarra~svn
[06:55:53] <bleathem> without the https, wou get the famous "Repository moved temporarily" message
[06:56:03] *** rruss has joined #seam-dev
[07:07:07] *** mgencur has joined #seam-dev
[07:22:28] *** oskutka has joined #seam-dev
[07:30:20] <oskutka> sbryzak: ping
[07:47:13] *** kuuyee has joined #seam-dev
[08:14:44] *** alesj has joined #seam-dev
[08:17:38] *** kpiwko has joined #seam-dev
[08:34:57] *** koentsje has joined #seam-dev
[08:35:51] *** aslak has joined #seam-dev
[08:35:51] *** aslak has quit IRC
[08:35:51] *** aslak has joined #seam-dev
[08:44:12] *** daniel_hinojosa has quit IRC
[08:45:09] *** mgoldmann has joined #seam-dev
[08:49:36] <nickarls> ...
[08:57:09] *** bleathem has quit IRC
[09:00:13] <sbryzak> oskutka: pong
[09:03:57] *** maschmid has joined #seam-dev
[09:12:56] <nickarls> OT: can you see the actual prices of a JBoss SLA contract or do you have to contact support and they send a marketing drone rushing?
[09:14:07] <sbryzak> nickarls: that's too far on the corporate side of the company for us engineering types to know anything about
[09:14:18] <nickarls> the Dark Side
[09:14:29] <sbryzak> that's the one
[09:15:18] <oskutka> Good afternoon, Shane!
[09:15:18] <oskutka> I know the Seam devs were hunting all the issues that had Fix version set to 3.0.0.Final, but what about the other issues? I thought that you were going to make a triage and set fixed version to all issues, be it 3.0.0.Final or just "Future". But now I see a bunch of jiras with unset fix version and I don't know what has been triaged and what not: https://issues.jboss.org/secure/IssueNavigator.jspa?mode=hide&requestId=12314332
[09:15:18] <oskutka> Another issue -- SOLDER-2 is marked as a blocker, but is still unresolved. I think you cannot (by definition :-) ) release something containing a blocker.
[09:15:19] <jbossbot> jira [SOLDER-2] Rework ServletContextResourceLoader to not rely on static for registration [Open (Unresolved) Bug, Blocker, Stuart Douglas] https://issues.jboss.org/browse/SOLDER-2
[09:15:26] *** rruss has quit IRC
[09:15:58] <sbryzak> oskutka: which version is SOLDER-2 a blocker for?
[09:16:00] <jbossbot> jira [SOLDER-2] Rework ServletContextResourceLoader to not rely on static for registration [Open (Unresolved) Bug, Blocker, Stuart Douglas] https://issues.jboss.org/browse/SOLDER-2
[09:16:24] <stuartdouglas> Future, imho it should never have been a blocker to start with
[09:16:36] <sbryzak> i'll change it to major ?
[09:16:51] <stuartdouglas> done
[09:16:58] <sbryzak> ah, thanks
[09:18:14] <sbryzak> oskutka: any issues without a version should be assigned to a 'future' version
[09:19:35] <sbryzak> oskutka: has your team discovered any new potential blockers?
[09:19:56] <sbryzak> or are we looking good for the release?
[09:22:15] <oskutka> sbryzak: Jozef found a blocker: SEAM-69
[09:22:16] <jbossbot> jira [SEAM-69] lib directory assembled incorrectly [Open (Unresolved) Bug, Blocker, Shane Bryzak] https://issues.jboss.org/browse/SEAM-69
[09:22:29] <sbryzak> i saw that, i don't agree with it
[09:22:50] <sbryzak> the presence of the extra jars isn't really an issue
[09:22:57] <sbryzak> although i can remove them from the distribution
[09:23:12] <sbryzak> as for the forge libs, there's no other choice currently
[09:25:58] <oskutka> sbryzak: ok
[09:26:15] <oskutka> sbryzak: We're still testing
[09:26:54] <oskutka> "(09:18:33) sbryzak: oskutka: any issues without a version should be assigned to a 'future' version"  -- Who should do this?
[09:26:57] <sbryzak> oskutka: no problem, i still need a bit of time to write up announcements, etc
[09:27:19] <sbryzak> oskutka: it's a general rule, though it should really be the module lead
[09:28:27] <oskutka> sbryzak: Do seam conversation have a JIRA project?
[09:28:56] <sbryzak> oskutka: no, issues for it can just go in SEAM and be assigned to alesj
[09:28:57] <oskutka> sbryzak: Not all seam projects have defined "Future" version
[09:29:04] <oskutka> sbryzak: ok
[09:29:39] <sbryzak> oskutka: if there's no future version, ping the module lead and ask them to create one (and also to move all their issues with a fix version there)
[09:29:53] <oskutka> sbryzak: ok, will do
[09:30:43] <oskutka> sbryzak: And do I understand it correctly, that an issue without a fix version filled in is a issue that hasn't been triaged yet?
[09:30:59] <sbryzak> not necessarily
[09:31:18] <sbryzak> most of them will be issues that don't have a determined fix version
[09:31:24] <sbryzak> i.e. they should be 'the future'
[09:31:36] <oskutka> sbryzak: So do you plan to track what has been triaged and what not?
[09:32:36] <sbryzak> i guess i'll take care of it for now, because we have minimal time
[09:32:37] *** marekn has joined #seam-dev
[09:32:54] *** Royle has joined #seam-dev
[09:33:41] <nickarls> OT2: has RedHat already figured out who is representing RH in what EE 7 spec?
[09:33:48] *** Royle has quit IRC
[09:34:46] <alesj> oskutka, sbryzak: what seam conversation issue are you seeing?
[09:34:57] *** PeteRoyle has quit IRC
[09:35:14] <oskutka> alesj: None so far :-)
[09:35:23] <jbossbot> git [dist] push master 9ba17d2.. Shane Bryzak SEAM-68
[09:35:24] <jbossbot> jira [SEAM-68] Incorrect version of seam-booking bundled with the 3.0.0.Final dist [Resolved (Done) Bug, Critical, Shane Bryzak] https://issues.jboss.org/browse/SEAM-68
[09:35:25] <jbossbot> git [dist] push master URL: http://github.com/seam/dist/compare/99c967d...9ba17d2
[09:38:13] <alesj> oskutka: ah, ok, going back to sleep then ? :-)
[09:38:14] <oskutka> sbryzak: Half of the modules have "The future", the other half have just "Future" (and the third half have neither). Should we unify this? I guess it might be good for queries.
[09:38:21] <oskutka> alesj: :-)
[09:38:30] <oskutka> alesj: Good night!
[09:39:07] <sbryzak> oskutka: we can, if we're going to use it for queries we should probably just go with 'Future'
[09:39:33] <oskutka> sbryzak: Ok, I'll ping the leaders.
[09:39:52] <sbryzak> oskutka: nevermind, i'll take care of it
[09:40:24] <mgencur> sbryzak: Shane, we'll probably postpone SEAMREMOTING-32, right? what to do with the fix version?
[09:40:25] <jbossbot> jira [SEAMREMOTING-32] Provide GlassFish build profiles for remoting-model and remoting-validation [Reopened (Unresolved) Task, Critical, Martin Gencur] https://issues.jboss.org/browse/SEAMREMOTING-32
[09:40:55] <sbryzak> mgencur: yes, any exampe issues are non-blockers
[09:41:14] <sbryzak> mgencur: the fix version should really be set to 3.1.0.Beta1
[09:41:17] <oskutka> sbryzak: oh, ok
[09:41:22] <mgencur> sbryzak: ok
[09:41:30] <sbryzak> however we may update it to 3.0.1.Beta1 if we intend to include it in a patch release
[09:41:36] <sbryzak> for now though, everything should be 3.1.0
[09:41:40] <sbryzak> or 'Future'
[09:41:43] <oskutka> sbryzak: for PROJECT in SEAM SEAMCATCH SOLDER SEAMXML SEAMPERSIST SEAMINTL SEAMFACES SEAMREMOTING SEAMSERVLET SEAMREST SEAMVALIDATE SEAMWICKET SEAMSECURITY ; do google-chrome "https://issues.jboss.org/browse/$PROJECT#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel"  ; done
[09:42:05] <oskutka> sbryzak: Just in case you were interested
[09:43:13] <sbryzak> oskutka: thanks
[09:44:32] <nickarls> did viewActions never make into JSF2?
[09:46:41] <sbryzak> nickarls: they made it, in a not-so-obvious way
[09:48:38] <sbryzak> nickarls: http://mkblog.exadel.com/2010/07/learning-jsf2-page-params-and-page-actions/
[09:48:57] <sbryzak> that blog seems to cover all the important stuff
[09:49:53] <nickarls> sbryzak: yeah, that's what I figured. That or s:viewAction...
[09:50:36] *** PeteRoyle has joined #seam-dev
[09:51:26] <nickarls> hmm. not that I can get s:viewAction to work for some reason...
[09:52:28] <sbryzak> nickarls: what's the problem?
[09:52:37] <nickarls> not being called
[09:53:05] <nickarls> I'm almost sure that SEAMFACES-49 was my error I can be closed (OK, ICEfaces error)
[09:53:07] <jbossbot> jira [SEAMFACES-49] faces-redirect not working with non-transient converations and implicit navigation [Open (Unresolved) Bug, Major, Unassigned] https://issues.jboss.org/browse/SEAMFACES-49
[09:54:14] <nickarls> closed it
[09:55:08] <nickarls> I have http://pastebin.com/hLBFuxEh
[09:55:18] <nickarls> I see the setters hit but never the action
[09:55:29] <nickarls> ns is xmlns:s="http://jboss.org/seam/faces"
[09:55:54] <sbryzak> nickarls: hmm, i'm not sure.. maybe one of the jsf guys here can suggest something
[09:57:43] <nickarls> it's used in booking hotel.xhtml so I don't think its completely b0rken
[09:57:49] <nickarls> going for preRenderView for now
[09:57:57] *** PeteRoyle has quit IRC
[10:01:02] <alesj> oskutka: it's 10am here, probably same as your timezone :-)
[10:01:30] <oskutka> alesj: Oh, I thought you were in the us?
[10:01:50] <oskutka> alesj: And you haven't slept yet?
[10:02:14] <alesj> oskutka: nah, just been working till 3am, and woke up at 8am ? hence still half-asleep
[10:02:33] <oskutka> alesj: I see. Good morning, then!
[10:02:38] <alesj> :-0
[10:02:39] <alesj> :-)
[10:02:48] <oskutka> alesj: Slovenia, right?
[10:03:07] <alesj> yup
[10:03:25] <oskutka> alesj: I've been there some three weeks ago. Beautiful country!
[10:04:01] <alesj> you should have pinged me
[10:04:06] <nickarls> one of those languages that think 4-5 consonants in a row is perfectly ok ;-)
[10:04:15] <nickarls> ok polish is worse
[10:04:31] <alesj> oskutka: where did you go?
[10:05:02] <oskutka> nickarls: In Czech, you can even write a sentence using just consonants: Str? prst skrz krk.
[10:05:09] <oskutka> alesj: Osp
[10:05:18] <oskutka> alesj: Or rather ?rni Kal.
[10:05:24] <oskutka> alesj: Rock climbing
[10:05:28] <alesj> ah, climbimg
[10:05:57] <oskutka> alesj: But I've been many times in Slovenia, no only climbing, but also hiking.
[10:06:01] *** PeteRoyle has joined #seam-dev
[10:06:04] <alesj> next time stop at my home town, Vrhnika
[10:06:11] <oskutka> alesj: And white water canoeing.
[10:06:14] <alesj> there are some nice places to climb
[10:06:35] <alesj> and I can hook you up wiht my friend, who was a world class climber
[10:06:43] <alesj> to show you some places
[10:07:06] <nickarls> oskutska: good dark beers in .cz
[10:07:22] <alesj> oskutka: which river did you choose for canoeing? Soca?
[10:07:32] <oskutka> alesj: I'm no good climber. :-(
[10:07:38] <oskutka> alesj: Yup, So?a
[10:08:43] <oskutka> alesj: BTW: Who's that world class climber?
[10:09:36] 
[10:10:16] <oskutka> alesj: I think we should not pollute the seam-dev...
[10:10:49] <alesj> :-)
[10:10:57] <oskutka> nickarls: Dark beers? I thought we were famous for our pils beers...
[10:11:02] <sbryzak> oskutka: i've assigned a fix version to all the issues now
[10:12:24] <oskutka> sbryzak: Great, thanks!
[10:18:19] 
[10:19:48] <oskutka> nickarls: ;-)
[10:19:48] <oskutka> nickarls: Maybe we are more famous for the beer price in the UK :-)
[10:21:00] <oskutka> nickarls: It's said it's cheaper for a Englishman to fly to Prague, drink there and fly back, than to drink in London...
[10:21:44] <Diablo-D3> they'd get better beer too
[10:22:49] <oskutka> Diablo-D3: :-)
[10:24:48] <nickarls> yeah, I also like the way beer is ordered, you get another beer if you don't explicitly stop it, then you get a line drawn on your paper tab :-)
[10:26:57] <marekn> nickarls: that is the usual way of serving, but not everywhere in CZ
[10:27:02] <nickarls> I think it was at the golden tiger pub in prague
[10:29:34] <oskutka> nickarls: Any plans to check other pubs in Prague? ;-)
[10:30:38] <nickarls> so many pubs, so little time.
[10:31:10] <nickarls> it was in the PK-age (pre-kids), would love to go again sometime
[10:31:52] <oskutka> nickarls: I see. Maybe there could be a Seam conference in Prague ;-)
[10:32:18] *** PeteRoyle has quit IRC
[10:32:43] <marekn> oskutka, nickarls: or Seam Face to face meeting in Brno ;-)
[10:32:55] <nickarls> company-sponsored drinking, that would be nice
[10:33:07] <oskutka> :-)
[10:33:20] <nickarls> if nothing else, I could tell my wife I have an important meeting there and go by myself ;-)
[10:33:30] <marekn> :-)
[10:37:30] <Diablo-D3> I love how a backtrace of my servlet not working right does not contain my servlet.
[10:46:35] <sbryzak> oskutka: i have a new distribution
[10:46:47] <sbryzak> oskutka: would you like me to upload it?
[10:49:49] <jbossbot> git [dist] push master e497ebb.. Shane Bryzak SEAM-69
[10:49:50] <jbossbot> jira [SEAM-69] lib directory assembled incorrectly [Open (Unresolved) Bug, Blocker, Shane Bryzak] https://issues.jboss.org/browse/SEAM-69
[10:49:51] <jbossbot> git [dist] push master URL: http://github.com/seam/dist/compare/9ba17d2...e497ebb
[10:55:32] *** PeteRoyle has joined #seam-dev
[11:18:05] <Diablo-D3> java.lang.RuntimeException: javax.servlet.ServletException: Original SevletRequest or wrapped original ServletRequest not passed to RequestDispatcher in violation of SRV.8.2 and SRV.14.2.5.1
[11:32:05] <nickarls> philosophical question of the day, if I have a @Stateful EJB with a @PersistenceContext, am I guaranteed to get the same underlying database connection every time I execute against the PC?
[11:32:39] <nickarls> I would pretty much have to, otherwise database locks etc wouldn't work, right?
[11:33:50] <nickarls> and that is true for within one method on a normal PC and for the entire lifecycle of the EJB for an ext PC.
[11:34:15] *** sannegrinovero has joined #seam-dev
[11:34:15] *** sannegrinovero has quit IRC
[11:34:16] *** sannegrinovero has joined #seam-dev
[11:49:59] <oskutka> sbryzak: Sorry, lunch time. Great! Please do.
[11:51:33] *** PeteRoyle has quit IRC
[11:52:06] <Diablo-D3> nickarls: no?
[11:52:13] <Diablo-D3> nickarls: it could very well be pooled.
[11:52:44] <Diablo-D3> locks can only be held during a transaction, and you cant keep transactions open across requests
[11:52:52] <Diablo-D3> except maybe if somethings held by a session bean
[11:52:57] <Diablo-D3> er, a session scoped bean
[11:53:09] <Diablo-D3> or something
[11:54:44] <Diablo-D3> sbryzak, mojavelinux, etc: so, I think Ive figured it out
[11:55:07] <Diablo-D3> to preserve the messages, I need access to an injectable FacesContext
[11:55:24] <Diablo-D3> which the openid rp code doesnt preserve
[11:58:32] *** alesj has quit IRC
[12:01:49] *** kuuyee has quit IRC
[12:03:17] *** sbryzak has quit IRC
[12:06:18] *** sbryzak has joined #seam-dev
[12:07:33] *** aslak has quit IRC
[12:07:33] *** PeteRoyle has joined #seam-dev
[12:08:19] *** aslak has joined #seam-dev
[12:08:21] *** aslak has quit IRC
[12:09:25] *** emmanuel has quit IRC
[12:17:24] *** alesj has joined #seam-dev
[12:18:55] *** aslak has joined #seam-dev
[12:18:55] *** aslak has quit IRC
[12:18:55] *** aslak has joined #seam-dev
[12:45:11] <nickarls> I have a case where I run native queries against a PC and it uses oracle temporary tables and wonder if there's any way I can guarantee that the next statement can see the previous temp table stuff
[12:46:04] <Diablo-D3> 	at com.ocpsoft.pretty.faces.application.PrettyNavigationHandler.handleNavigation(PrettyNavigationHandler.java:57) [:]
[12:46:05] <Diablo-D3> 	at org.jboss.seam.faces.event.SeamPreNavigationHandler.handleNavigation(SeamPreNavigationHandler.java:55) [:3.0.0.CR2]
[12:46:05] <Diablo-D3> 	at org.diablopool.authentication.OpenIdRedirect.loginFailed(OpenIdRedirect.java:54) [:]
[12:46:08] <Diablo-D3> yearg! so close!
[12:47:40] <nickarls> but anyway since it's all within a single EJB method, it should be in the same transaction (and transaction scoped PC)
[12:48:00] <Diablo-D3> nickarls: if its all in the same ejb, yes, it should be the same transaction
[13:11:40] * Diablo-D3 is so close to fixing this he can TASTE IT
[13:11:52] <Diablo-D3> IT TASTES LIKE VICTORY
[13:12:07] * Diablo-D3 gets the vodka and washes his mouth out
[13:13:32] <Diablo-D3> YEARGH I DIDNT FIX IT
[13:17:06] *** jose_freitas has joined #seam-dev
[13:17:20] <jose_freitas> morning
[13:17:51] * Diablo-D3 stabs java. all of it.
[13:21:26] *** amitev has quit IRC
[13:21:30] *** amitev2 has joined #seam-dev
[13:32:42] *** PeteRoyle has quit IRC
[13:33:55] *** PeteRoyle has joined #seam-dev
[13:40:35] *** epbernard has joined #seam-dev
[13:40:35] *** epbernard is now known as emmanuel
[13:45:30] <nickarls> diablo: easy with the vodka
[13:46:23] * nickarls wishes there was a standard way of getting a Connection from an EntityManager.
[13:47:42] *** tsurdilo has joined #seam-dev
[13:54:06] <Diablo-D3> so I manually build a faces context using over 9000 factories
[13:54:27] <Diablo-D3> then I use facescontext to add a faces message
[13:54:37] <Diablo-D3> then I facescontext.getexternalcontext()
[13:54:55] <Diablo-D3> and then I externalcontext.redirect(the url)
[13:55:03] *** pmuir has joined #seam-dev
[13:55:03] <Diablo-D3> it redirects and I STILL dont get any messages
[14:03:54] *** PeteRoyle has quit IRC
[14:46:57] *** Obsidians has joined #seam-dev
[14:48:03] *** kpiwko1 has joined #seam-dev
[14:48:50] *** kpiwko has quit IRC
[14:49:22] *** kpiwko1 is now known as kpiwko
[14:57:45] *** tsurdilo has quit IRC
[15:14:17] *** tsurdilo has joined #seam-dev
[15:27:47] *** pmuir has quit IRC
[15:32:50] *** jganoff has joined #seam-dev
[15:36:46] *** lightguard_jp has joined #seam-dev
[15:38:17] *** lincolnthree has joined #seam-dev
[15:38:29] <lincolnthree> sbryzak: working on fixing forge for you
[15:38:49] <lincolnthree> the current snapshots are broken
[15:39:02] <lincolnthree> a bug from maven came in without failing the builds or tests
[15:39:08] <lincolnthree> got that resolved
[15:39:17] <lincolnthree> looking at your/marekns issues
[15:39:48] <lightguard_jp> sbryzak: Still around?
[15:40:03] <sbryzak> lightguard_jp: i'm here
[15:40:05] *** wdrai has joined #seam-dev
[15:40:13] <Diablo-D3> okay so
[15:40:14] <sbryzak> lincolnthree: cool, when do you think it will be ready?
[15:40:17] <Diablo-D3> whyat exactly does
[15:40:22] <Diablo-D3> navigationhandler
[15:40:24] <Diablo-D3> actually
[15:40:24] <Diablo-D3> do
[15:40:33] <lightguard_jp> sbryzak: Wow, up late. Anyway, the bugs that are reported and you're moving off, we're not planning on fixing them for Final?
[15:40:49] <sbryzak> none of them are blockers
[15:41:10] <sbryzak> we'll fix them for 3.0.1
[15:41:35] <lightguard_jp> Okay
[15:42:05] <sbryzak> lightguard_jp: so, only about a week until you start? :)
[15:42:18] <lightguard_jp> sbryzak: Monday
[15:42:24] <lightguard_jp> Get my box Tuesday
[15:42:31] <sbryzak> ah, great
[15:42:37] <lightguard_jp> I imagine Wednesday will be setup day
[15:42:41] <lincolnthree> sbryzak: when do you plan on cutting Final?
[15:43:08] <sbryzak> as soon as qa says i can
[15:43:14] <sbryzak> i still need to write up the announcement
[15:43:21] <sbryzak> it needs a little more work than the previous ones
[15:44:12] *** gastaldi has joined #seam-dev
[15:44:17] <gastaldi> hey all !
[15:44:41] <gastaldi> Any news on Seam 3 Final ?
[15:45:06] <sbryzak> gastaldi: not that i've heard
[15:45:15] <gastaldi> :(
[15:45:32] <sbryzak> it will be soon :)
[15:45:38] <gastaldi> lol
[15:45:42] <gastaldi> hope so
[15:46:29] <gastaldi> why, Seam Mail is not on Seam 3 bundle ? :P
[15:47:50] <sbryzak> it wasn't quite ready in time
[15:48:54] <lincolnthree> I think QE just started the forge testing for Seam 3 Final
[15:49:03] <lincolnthree> There are some new issues
[15:49:08] <lincolnthree> in my JIRA
[15:49:14] <gastaldi> sbryzak: When is the next Seam version scheduled ?
[15:49:33] <sbryzak> lincolnthree: any serious ones?
[15:50:04] <gastaldi> Hope Seam JCR can make it until there ! :)
[15:50:11] <sbryzak> gastaldi: in about 6 months for 3.1, earlier for 3.0.1 if we decide to do a patch release
[15:51:05] <gastaldi> Hum, SEAM-61 is reopened
[15:51:06] <jbossbot> jira [SEAM-61] Update the PrettyFaces version to 3.2.0 [Reopened (Unresolved) Library Upgrade, Major, Shane Bryzak] https://issues.jboss.org/browse/SEAM-61
[15:52:44] 
[15:54:22] <sbryzak> i can probably fix that by re-releasing the parent
[15:54:39] <maschmid> gastaldi: that is not really a major issue for Final I think...
[15:55:09] <gastaldi> maschmid: Agreed
[15:55:10] <sbryzak> i don't know why that dependency is in parent anyway
[15:56:15] <lincolnthree> sbryzak: not sure either, but maybe because it could be depended on by both servlet and faces, then, it should probably be in the bom or something else. im losing my sense of the seam 3 build
[15:56:34] <jbossbot> git [parent] push master 3634588.. Shane Bryzak SEAM-61
[15:56:35] <jbossbot> jira [SEAM-61] Update the PrettyFaces version to 3.2.0 [Reopened (Unresolved) Library Upgrade, Major, Shane Bryzak] https://issues.jboss.org/browse/SEAM-61
[15:56:35] <jbossbot> git [parent] push master URL: http://github.com/seam/parent/compare/6ae4102...3634588
[15:56:46] *** mgencur has quit IRC
[15:56:56] <sbryzak> it's already in the bom, maybe its presence in parent is a holdover from earlier
[15:57:00] <lincolnthree> Hm
[15:57:23] <sbryzak> anything non test-related should be in the bom imho
[15:58:29] <maschmid> sbryzak: AFAIK, only examples depend on prettyfaces.
[15:59:21] <gastaldi> humm
[15:59:36] <gastaldi> I believe that Seam should not depend on prettyfaces at all then
[15:59:43] <Diablo-D3> or better yet
[15:59:48] <Diablo-D3> prettyfaces should be a seam 3 module
[16:00:00] 
[16:00:00] <lincolnthree> Diablo-D3: no need :)
[16:00:03] <gastaldi> :)
[16:00:05] <oskutka> sbryzak: ping
[16:00:16] <sbryzak> oskutka: pong
[16:00:21] <gastaldi> merge prettyfaces on seam faces
[16:00:26] <lincolnthree> prettyfaces already has an active developer and user community, no reason to disrupt it
[16:00:31] <lincolnthree> also, prettyfaces is not just for JSF
[16:00:36] <oskutka> sbryzak: You said you have a new zip version. Could you please upload it for the QEs?
[16:00:41] <gastaldi> ah, that justified
[16:00:44] <lincolnthree> it works on plan Java EE and servlet
[16:00:48] <sbryzak> oskutka: sure thing, same place as before?
[16:00:48] <jose_freitas> Diablo-D3: that's nonsense, so for example picketlink and jodaTime should be a module of seam too
[16:00:50] <gastaldi> so no merge at all :)
[16:00:53] <oskutka> sbryzak: yup
[16:01:18] <jose_freitas> Diablo-D3: seam has it dependencies and there's no problem having it
[16:01:53] <gastaldi> jose_freitas: As prettyfaces is only used on examples, I believe it should not be a Seam dependency at all
[16:02:29] <sbryzak> oskutka: 922916567d68199ddaee4c4b5e6785fb
[16:03:07] *** rruss has joined #seam-dev
[16:03:15] <sbryzak> oskutka: 20% now, i'll tell you when it's complete
[16:03:21] <oskutka> sbryzak: Thanks
[16:03:21] <lincolnthree> gastaldi: eventually the Seam Faces viewconfig will depend on PrettyFaces
[16:03:26] <lincolnthree> it just hasn't been integrated yet
[16:03:30] <Diablo-D3> jose_freitas: actually, lets just get rid of this sun shit
[16:03:32] <Diablo-D3> and make it all seam
[16:03:41] <Diablo-D3> seam should just become a whole language.
[16:03:45] <gastaldi> haha
[16:04:04] <jose_freitas> gastaldi: but what's the problem using pf to examples?
[16:04:15] <maschmid> lincolnthree: I have now finished testing Forge, so that should be all from me for now...
[16:04:25] 
[16:04:54] <lincolnthree> thank you maschmid
[16:05:00] <lincolnthree> working on them now
[16:05:04] *** marekn has quit IRC
[16:05:09] <gastaldi> whatever
[16:05:17] <gastaldi> let it be that way :)
[16:05:44] 
[16:06:13] <lincolnthree> but you're correct, right now it doesn't need to be in the bom if it's just used in an example
[16:06:20] <lincolnthree> in the future, the need will be there
[16:07:32] *** alesj has quit IRC
[16:08:19] <jose_freitas> oic, you're not talking about using it, but having it on seam-bom
[16:08:30] <sbryzak> oskutka: upload is complete
[16:08:32] <gastaldi> yes
[16:08:39] <jose_freitas> now I get it :)
[16:08:39] <Diablo-D3> WAAAAAAAAGH
[16:10:05] <gastaldi> RedHat should buy ocpsoft, so that prettyfaces will finally be merged on seam
[16:10:32] <sbryzak> gastaldi: i think it's a generally useful project standalone
[16:10:38] <oskutka> sbryzak: Downloaded. MD5sum matches.
[16:10:50] <gastaldi> Yes, just kidding :)
[16:11:11] <gastaldi> flaming the room a little :)
[16:11:41] <Diablo-D3> WAAAAAAAAAAAAAAAAAGH
[16:13:15] *** clerum has joined #seam-dev
[16:15:23] <jose_freitas> lol gastaldi
[16:15:46] <Diablo-D3> apparently yelling at java isnt fixing this
[16:23:07] <oskutka> sbryzak: We'll have it tested by tomorrow afternoon Australian time, ok?
[16:23:30] <lincolnthree> hey sbryzak or maschmid. Could you explain the name of this issue? It doesn't seem to match the content: SEAMFORGE-103
[16:23:31] <jbossbot> jira [SEAMFORGE-103] Seam Solder from the seam final distribution creates projects that depend on seam-persistence 3.0.0.Beta4, instead of Final. [Open (Unresolved) Bug, Critical, Unassigned] https://issues.jboss.org/browse/SEAMFORGE-103
[16:23:35] <sbryzak> oskutka: that would be great
[16:24:01] *** bleathem has joined #seam-dev
[16:24:02] <maschmid> lincolnthree: I originaly filed it in SEAM, sbryzak moved it...
[16:24:03] <lincolnthree> Was there an issue with Solder as well?
[16:24:11] <lincolnthree> Or did you mean Forge?
[16:24:38] <maschmid> lincolnthree: yes, sorry. that was probably my slip...
[16:24:39] <sbryzak> i think it's because of the version of solder bundled with forge
[16:25:10] *** daniel_hinojosa has joined #seam-dev
[16:25:31] <lincolnthree> Please see my last comment. Any thoughts would be appreciated
[16:25:37] <wdrai> Hi all, I have a small question: I'm working on the Flex module and I need to unproxy entities before serializing them back to Flex (when they are defined as beans). What's the best way to do this ? Currently I'm casting the object to TargetInstanceProxy and use getTargetInstance() but that does not seem right to me.
[16:26:02] <lincolnthree> I can update this to use the .Final package name for the moment, but it will break anyone who tries an earlier version (not a huge concern really. but still an issue that needs to be addressed eventually)
[16:26:14] <sbryzak> how does the user select a version of seam persistence?
[16:26:40] <sbryzak> wdrai: you don't know the bean type?
[16:27:06] <gastaldi> Is there a Flex module ? :P
[16:27:18] <sbryzak> gastaldi: under construction
[16:27:27] <maschmid> lincolnthree: I would say that anybody using Beta should expect the API may change...
[16:27:32] <lincolnthree> |
[16:27:32] 
[16:27:34] <lincolnthree>   1 - [org.jboss.seam.persistence:seam-persistence:3.0.0-SNAPSHOT]
[16:27:34] <lincolnthree>   2 - [org.jboss.seam.persistence:seam-persistence:3.0.0.Beta2]
[16:27:34] <lincolnthree>   3 - [org.jboss.seam.persistence:seam-persistence:3.0.0.Beta3]
[16:27:34] <lincolnthree>   4 - [org.jboss.seam.persistence:seam-persistence:3.0.0.Beta4]
[16:27:34] <lincolnthree>   5 - [org.jboss.seam.persistence:seam-persistence:3.0.0.CR1]
[16:27:35] <lincolnthree>   6 - [org.jboss.seam.persistence:seam-persistence:3.0.0.CR2]
[16:27:35] <lincolnthree>   7 - [org.jboss.seam.persistence:seam-persistence:3.0.0.CR3]
[16:27:36] <lincolnthree>   8 - [org.jboss.seam.persistence:seam-persistence:3.0.0.CR4]
[16:27:37] <lincolnthree> Choose an option by typing the number of the selection:
[16:28:03] <sbryzak> lincolnthree: is it just a list of matching maven artifacts?
[16:28:12] <lincolnthree> Yes.
[16:28:27] <lincolnthree> But if the plugin is updated, i could narrow or expand the list.
[16:28:40] <lincolnthree> Note that I can actually load the jar for any of those artifacts
[16:28:45] *** oskutka has quit IRC
[16:28:49] <sbryzak> i would exclude anything before the final release
[16:29:01] <lincolnthree> Notice the Final release isn't in a repo yet ;)
[16:29:10] <lincolnthree> And doesn't show up.
[16:29:11] <wdrai> sbryzak: yes, I get the object with manager.getReference(...)
[16:29:15] <sbryzak> it's in snapshot repo
[16:29:44] <sbryzak> wdrai: one possibility is to build your metadata from the bean type, then use that to query the proxy
[16:29:50] <sbryzak> wdrai: i do a similar thing with remoting
[16:30:06] <jose_freitas> wdrai: Entities shouldn't be injected
[16:30:31] <jose_freitas> since JPA cannot persist them, it's better to keep them outside the proxies
[16:31:10] <lincolnthree> maschmid: SEAMFORGE-47 - you mean when you use the running app to add rows, the field values do not propagate to the database?
[16:31:11] <jbossbot> jira [SEAMFORGE-47] Default scaffolding does not generate working Update or Delete actions [Open (Unresolved) Bug, Major, Unassigned] https://issues.jboss.org/browse/SEAMFORGE-47
[16:31:30] <maschmid> lincolnthree: yes.
[16:31:32] <lincolnthree> Ok. Not sure I'm going to have that fixed for this release.
[16:31:33] <wdrai> sbryzak: I'm going to have a look at remoting then, but ideally I really would like to get the underlying JPA object
[16:32:14] <sbryzak> wdrai: ah, if it's a jpa object, then jose's statement is relevant
[16:32:52] <wdrai> jose_freitas: sure, but I get proxies from producer methods. I'm building a Flex UI for seam booking and would like to keep the server part exactly the same as the faces one.
[16:32:52] <jose_freitas> wdrai: look at the weld-pdf documentation. at page 13 it has a note about JPA objects
[16:33:50] <wdrai> jose_freitas: for example, when getting the booking and hotel after the call to bookHotel
[16:34:26] <sbryzak> wdrai: with entites you may have to unwrap collections
[16:35:10] <Diablo-D3> cant wait for as7
[16:35:12] <Diablo-D3> really really cant
[16:35:24] <jose_freitas> there we make an instance with new
[16:35:27] <sbryzak> wdrai: see https://github.com/seam/remoting/blob/master/impl/src/main/java/org/jboss/seam/remoting/wrapper/BagWrapper.java
[16:35:56] <wdrai> sbryzak: thanks
[16:37:38] <jose_freitas> Another thing you could do, besides not injecting entities, is to add @Veto to them.
[16:37:44] <wdrai> sbryzak: I think I was not very clear.
[16:38:16] <lincolnthree> sbryzak: perhaps a nice persistence feature would be to automatically @Veto all @Entity classes
[16:38:21] <gastaldi> Diablo-D3: Have you considered helping the developers on AS 7 ?
[16:38:39] <Diablo-D3> dude, I cant even figure out why the hell this goddamned thing wont work
[16:39:02] <Diablo-D3> also, AMAZING, jboss doesnt include the source jars!
[16:39:10] <Diablo-D3> and maven cant find them!
[16:40:03] <gastaldi> lincolnthree: Excellent idea
[16:40:05] <wdrai> The booking object that you get in the seam booking example seems doubly proxied: once by Weld because it's a bean coming from a producer method, and then by Hibernate. I don't have any problem with the Hibernate proxying but I just need to unproxy the Weld/javassist part before serialization.
[16:40:21] <Diablo-D3> jsf-impl-2.0.3-b05
[16:40:34] <sbryzak> lincolnthree: i didn't think that entities were beans anyway
[16:41:01] <lincolnthree> sbryzak: i think they technically qualify unless CDI explicitly excludes them
[16:41:04] <lincolnthree> no?
[16:41:12] <sbryzak> hmm, let me check the spec
[16:41:31] <clerum> because of the no arg constructor?
[16:41:37] <jose_freitas> wdrai: booking is produced to be used in the view
[16:41:38] <jbossbot> git [forge] push master de0509d.. Lincoln Baxter, III SEAMFORGE-106 Fixed plexus class conflict
[16:41:39] <jbossbot> jira [SEAMFORGE-106] Conflict in plexus classes causes new-project to fail [Closed (Done) Bug, Major, Lincoln Baxter III] https://issues.jboss.org/browse/SEAMFORGE-106
[16:41:39] <jbossbot> git [forge] push master e883470.. Lincoln Baxter, III SEAMFORGE-50 (fixed broken mw.xml) SEAMFORGE-105
[16:41:40] <jbossbot> jira [SEAMFORGE-50] Forge default scaffold (metawidget) is not properly configured (id and version fields show up) [Closed (Done) Bug, Major, Lincoln Baxter III] https://issues.jboss.org/browse/SEAMFORGE-50
[16:41:41] <jbossbot> jira [SEAMFORGE-105] Refactory.createGetterAndSetter should create getFirstName method, instead of getFirstname for a field named firstName [Closed (Done) Bug, Minor, Lincoln Baxter III] https://issues.jboss.org/browse/SEAMFORGE-105
[16:41:41] <jbossbot> git [forge] push master URL: http://github.com/seam/forge/compare/ea64611...e883470
[16:41:50] <sbryzak> section 1.2.2: Message-driven and entity beans are by nature non-contextual objects and may not be injected into other objects.
[16:41:57] <jose_freitas> wdrai: but it's not being injected on bookingAgent
[16:42:06] <wdrai> jose_freitas: sure, that's why I want to use it from the Flex view ;)
[16:42:24] <sbryzak> wdrai: might be best to ask pmuir or ales about unproxying the weld object
[16:42:26] <wdrai> jose_freitas: that's why I need to serialize it back to the Flex client
[16:42:28] <lincolnthree> sbryzak: awesome, nm then. thought i had a brilliant moment
[16:43:09] <sbryzak> wdrai: if you have the bean type though, and know how to read its state, can't you just use reflection with the proxy object to extract that state?
[16:43:28] <jose_freitas> wdrai: oic
[16:43:57] <clerum> lincolnthree: I know you have about 1000 better things to do but did the Alpha2 of render make it up to a repo?
[16:44:00] <clerum> not seeing it
[16:44:10] <maschmid> lincolnthree: wow, btw. You do realize you don't have to immediately fix all the minor issues just because I have found them, right? :)
[16:44:13] <lincolnthree> clerum: GDI
[16:44:17] <lincolnthree> ive released it twice now
[16:44:21] <lincolnthree> what is going on
[16:44:24] <jose_freitas> cant you access it through bookingAgent.getBooking ?
[16:44:31] <clerum> ah there it is now
[16:44:59] <clerum> I didn't see it there yesterday or the day before but it's there now
[16:45:20] <lincolnthree> ok phew
[16:46:37] *** pmuir has joined #seam-dev
[16:46:37] *** pmuir has quit IRC
[16:46:37] *** pmuir has joined #seam-dev
[16:46:53] <wdrai> sbryzak: This is an option, but in this case I lose the ability to send the full JPA detached object to Flex as it is possible with GraniteDS
[16:47:32] <Diablo-D3> alright, I give up for today
[16:47:33] <Diablo-D3> night all
[16:47:42] <sbryzak> wdrai: why is that?
[16:48:38] <Diablo-D3> I think tommorow im just going to forward it to a page that sets this, and then have that page forward.
[16:48:40] <Diablo-D3> or something.
[16:49:15] *** adamw1pl has joined #seam-dev
[16:51:11] <wdrai> sbryzak: for example we can send to and restore from Flex the lazy initialization state of collections or associations. Then the modified object coming from Flex can be simply merged in the extended PC. To do this we already introspect the internal state of the Hibernate proxies. Having two layers of proxies makes it more difficult.
[16:51:40] <lincolnthree> sbryzak: when did Transactional change packages?
[16:51:52] <sbryzak> lincolnthree: a little while ago
[16:51:58] <lincolnthree> sbryzak: which release
[16:52:11] <lincolnthree> which release includes the new package
[16:52:17] <lincolnthree> CR4 or Final?
[16:52:17] <sbryzak> checking, one moment
[16:52:26] <gastaldi> CR4 I believe
[16:52:53] <gastaldi> I recall that from the mailing list
[16:53:17] <sbryzak> lincolnthree: it seems we didn't create a JIRA issue for it
[16:53:26] <sbryzak> it wasn't final
[16:53:34] <sbryzak> i think gastaldi is correct
[16:53:45] <sbryzak> wdrai: have you seen the model api in remoting?
[16:55:24] <jbossbot> git [mail] push master b2c6968.. Cody Lerum add logo file to fix test and enable Seam Render tests
[16:55:24] <jbossbot> git [mail] push master 33b6d4c.. Cody Lerum update to render Alpha2
[16:55:24] <jbossbot> git [mail] push master URL: http://github.com/seam/mail/compare/87abf3f...33b6d4c
[16:56:11] *** Diablo-D3 has quit IRC
[16:57:59] <gastaldi> clerum: There is a typo on https://github.com/seam/mail/tree/master/core/api/src/main/java/org/jboss/seam/mail/core/enumurations
[16:58:11] <gastaldi> it should be enumerations, not enumurations :)
[16:58:22] <clerum> grr...no more late night coding
[16:58:39] <clerum> thanks
[16:58:53] 
[16:59:08] <clerum> on the plus side someone is acutally looking at it
[16:59:12] <gastaldi> How about using "Kind" as the suffix for these enums
[16:59:49] <clerum> instead of type
[16:59:53] <gastaldi> ?
[17:00:12] <clerum> ContentKind vs ContentType
[17:00:55] <gastaldi> any thoughts ?
[17:01:39] <clerum> need to mull it over a bit
[17:01:55] <clerum> ContentType really is Content-Type (http://en.wikipedia.org/wiki/MIME#Content-Type)
[17:02:50] <gastaldi> Is there a coding standard for that ?
[17:02:59] <gastaldi> on enum suffixes ?
[17:03:16] <clerum> not that I have seen. I could have missed it though
[17:04:05] <gastaldi> I read somewhere that Kind is the standard suffix for enums on UML notation
[17:04:36] 
[17:04:37] *** maschmid_ has joined #seam-dev
[17:06:41] *** maschmid has quit IRC
[17:06:41] *** monkeyden has joined #seam-dev
[17:08:46] <jbossbot> git [mail] push master 8092559.. Cody Lerum typo
[17:08:47] <jbossbot> git [mail] push master 2da6691.. Cody Lerum license add
[17:08:47] <jbossbot> git [mail] push master URL: http://github.com/seam/mail/compare/33b6d4c...2da6691
[17:11:16] <gastaldi> good job ! :)
[17:12:54] *** mgoldmann has quit IRC
[17:16:26] *** gastaldi has quit IRC
[17:19:04] *** jose_freitas has quit IRC
[17:19:04] *** maschmid_ is now known as maschmid
[17:21:48] <lightguard_jp> I think we now have the most people in this channel I have ever seen!
[17:21:53] <lightguard_jp> Go community!!
[17:22:55] <nickarls> jp: BTW did you ever get to testing your entityConverter?
[17:25:27] <lightguard_jp> No, not yet.
[17:25:44] <lightguard_jp> I spent the weekend with the family, then I've had crap to do at work for my last week
[17:36:19] *** amitev2 has quit IRC
[17:36:24] *** amitev has joined #seam-dev
[17:37:31] <wdrai> sbryzak: I'll have a look at the model api, it seems it's relatively similar to what I'm doing.
[17:45:41] *** jose_freitas has joined #seam-dev
[18:07:20] <bleathem> mojavelinux, lightguard_jp: I won't be able to make the community meeting today. Topics I would bring up are:
[18:07:25] <bleathem> 1) maven archetypes
[18:08:09] <bleathem> well, maybe there is no 2
[18:08:48] *** jbossbot has quit IRC
[18:09:00] <bleathem> add a "w00t" on my part congratulating everyone on the 3.0.0.Final release
[18:09:21] *** jbossbot has joined #seam-dev
[18:12:40] *** bitshuffler has joined #seam-dev
[18:15:09] *** mgencur has joined #seam-dev
[18:15:11] <lincolnthree> bleathem: is it released yet?
[18:15:11] *** mgencur has left #seam-dev
[18:15:35] <bleathem> not yet
[18:15:59] <bleathem> add an imminent to my above statement!
[18:16:27] *** jose_freitas has quit IRC
[18:55:46] *** kpiwko has quit IRC
[19:01:07] *** adamw1pl has quit IRC
[19:01:31] *** maschmid has quit IRC
[19:12:03] *** bitshuffler_ has joined #seam-dev
[19:13:24] *** bitshuffler has quit IRC
[19:28:43] *** bleathem has quit IRC
[19:41:50] <jbossbot> git [forge] push master c2fb62c.. Lincoln Baxter, III SEAMFORGE-103 and Metawidget fixes. ScaffoldPlugin now prompts to overwrite instead of ignoring and mentioning --overwrite.
[19:41:51] <jbossbot> jira [SEAMFORGE-103] Seam Forge from the seam final distribution creates projects that depend on seam-persistence 3.0.0.Beta4, instead of Final. [Open (Unresolved) Bug, Critical, Unassigned] https://issues.jboss.org/browse/SEAMFORGE-103
[19:41:51] <jbossbot> git [forge] push master URL: http://github.com/seam/forge/compare/e883470...c2fb62c
[19:46:55] *** adamw1pl has joined #seam-dev
[19:58:03] *** balunasj has joined #seam-dev
[20:02:06] <nickarls> jp: speaking of the entityConverter, isn't it pretty much the same as an objectConverter where you just map String -> Instance?
[20:07:17] *** emmanuel has quit IRC
[20:16:50] *** maschmid has joined #seam-dev
[20:18:52] *** wdrai has left #seam-dev
[20:19:00] *** sannegrinovero has quit IRC
[20:24:37] *** ALR has joined #seam-dev
[20:24:56] <ALR> Hey boys.
[20:25:03] <ALR> Non-resolvable parent POM: Could not find artifact org.jboss.seam:seam-parent:pom:10 in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/) and 'parent.relativePath' points at wrong local POM @ line 5, column 12 -> [Help 2]
[20:25:04] *** poulpe has joined #seam-dev
[20:25:30] <ALR> Super hot ideas?
[20:26:11] *** poulpe has quit IRC
[20:35:18] <maschmid> ALR: What are you trying to build?  org.jboss.seam:seam-parent:pom:10 has not yet been released...
[20:37:13] <ALR> maschmid: Faces declares it as a dep.
[20:37:21] <ALR> Seam Faces that is
[20:38:26] <ALR> maschmid: https://github.com/seam/faces/blob/master/pom.xml#L8
[20:44:46] *** bitshuffler__ has joined #seam-dev
[20:46:03] <maschmid> ALR: I see... The artifacts are now in the staging repository being tested, they will be released Real Soon Now for the 3.0.0.Final release... until then, if you want to build from source, you may try to change it to 11-SNAPSHOT...
[20:46:04] <oranheim> ALR: It's available on the staging repo: https://repository.jboss.org/nexus/content/groups/staging/org/jboss/seam/seam-bom/
[20:46:47] *** adamw1pl has quit IRC
[20:47:42] *** bleathem has joined #seam-dev
[20:48:07] *** balunasj has joined #seam-dev
[20:48:24] *** bitshuffler_ has quit IRC
[21:03:29] *** jose_freitas has joined #seam-dev
[21:05:38] <jose_freitas> hello, what's the meeting time today?
[21:13:41] *** balunasj has quit IRC
[21:18:37] *** bleathem has quit IRC
[21:28:11] <jbossbot> git [forge] push master 8b58246.. Lincoln Baxter, III Added AS7 container
[21:28:11] <jbossbot> git [forge] push master 96eca65.. Lincoln Baxter, III new-field now uses --named instead of --fieldName
[21:28:11] <jbossbot> git [forge] push master 7649eec.. Lincoln Baxter, III moved 'project build' to a separate plugin 'build' which @RequiresProject
[21:28:11] <jbossbot> git [forge] push master e9d1d1f.. Lincoln Baxter, III docs updates and fixed broken tests
[21:28:11] <jbossbot> git [forge] push master URL: http://github.com/seam/forge/compare/c2fb62c...e9d1d1f
[21:32:30] <jbossbot> git [forge] push master 0376caf.. Lincoln Baxter, III doc update, removed duplicate reference to Maven in installation steps
[21:32:30] <jbossbot> git [forge] push master URL: http://github.com/seam/forge/compare/e9d1d1f...0376caf
[21:34:40] <jbossbot> git [forge] push master acb9d53.. Lincoln Baxter, III reversed order of container and provdier in persistence setup example
[21:34:40] <jbossbot> git [forge] push master URL: http://github.com/seam/forge/compare/0376caf...acb9d53
[21:37:27] <jbossbot> git [forge] push master 8c988aa.. Lincoln Baxter, III spacing update
[21:37:27] <jbossbot> git [forge] push master URL: http://github.com/seam/forge/compare/acb9d53...8c988aa
[21:38:54] <jbossbot> git [forge] push master ade2b1a.. Lincoln Baxter, III fixed build plugin to use @DefaultCommand
[21:38:54] <jbossbot> git [forge] push master URL: http://github.com/seam/forge/compare/8c988aa...ade2b1a
[21:43:17] *** monkeyden has quit IRC
[21:54:32] *** bitshuffler__ has quit IRC
[21:55:25] <jbossbot> git [forge] push master c3ae0a2.. Lincoln Baxter, III Updated generated index scaffolding
[21:55:25] <jbossbot> git [forge] push master URL: http://github.com/seam/forge/compare/ade2b1a...c3ae0a2
[21:55:34] *** gmorling_ has joined #seam-dev
[22:02:33] *** aslak has quit IRC
[22:06:15] <lincolnthree> i wish the build didn't take so long
[22:06:28] <lincolnthree> I want people to see the new docs so they can test accurately
[22:07:09] <clerum> jose_freitas: I think the meeting is rignt now
[22:07:31] *** jganoff has quit IRC
[22:10:00] *** aslak has joined #seam-dev
[22:10:01] *** aslak has quit IRC
[22:10:01] *** aslak has joined #seam-dev
[22:10:07] *** lightguard_jp has quit IRC
[22:17:37] <jose_freitas> clerum: hm
[22:19:14] <clerum> acutally 3PM
[22:19:19] <clerum> err
[22:19:22] <clerum> 40 minutes from now
[22:19:26] <clerum> 3 MDT
[22:19:30] <clerum> 5 EDT
[22:21:08] <clerum> http://www.timeanddate.com/worldclock/fixedtime.html?day=30&month=3&year=2011&hour=22&min=00&sec=0&p1=90
[22:21:21] <clerum> according to http://seamframework.org/Seam3/ProjectMeetings
[22:21:45] *** Obsidians has quit IRC
[22:22:33] <nickarls> midnight meeting
[22:24:30] <jose_freitas> ok
[22:26:10] *** bleathem has joined #seam-dev
[22:31:28] *** bleathem has quit IRC
[22:31:40] *** jbossbot has quit IRC
[22:32:01] *** jbossbot has joined #seam-dev
[22:42:53] <ALR> Thanks guys
[22:45:31] *** wdrai has joined #seam-dev
[23:01:42] *** kenfinnigan has joined #seam-dev
[23:02:14] <kenfinnigan> Hi all
[23:02:49] <jose_freitas> hi ken
[23:03:33] <kenfinnigan> How are you jose_freitas?
[23:03:33] <nickarls> ken: you noticed the mysterious Bundles injection case was solved? ;-)
[23:03:50] <kenfinnigan> Yeah, apparently a fix in weld?
[23:03:53] <mojavelinux> hey everyone
[23:04:02] <kenfinnigan> Haven't tried it recently to confirm
[23:04:19] <kenfinnigan> Evening mojavelinux
[23:04:25] <mojavelinux> #startmeeting
[23:04:33] <jose_freitas> kenfinnigan: I'm good ken, I little bit tired, but nothing that a good night sleep will solve
[23:04:33] <jbott> Meeting started Wed Mar 30 21:04:44 2011 UTC.  The chair is mojavelinux. Information about MeetBot at http://wiki.debian.org/MeetBot.
[23:04:33] <jbott> Useful Commands: #action #agreed #help #info #idea #link #topic.
[23:04:46] <jose_freitas> and you?
[23:04:56] <jose_freitas> ops
[23:05:02] <kenfinnigan> Getting over beong sick since saturday!
[23:05:12] <mojavelinux> I think a good night sleep would help a lot of us at this point ;)
[23:05:15] <mojavelinux> oh no, sick, worse
[23:05:49] <kenfinnigan> I know. Thankfully been working from last few days
[23:06:03] <kenfinnigan> Will respond to ur email from sunday tonight
[23:06:12] <lincolnthree> Hi all
[23:06:16] <kenfinnigan> Summary: very interested
[23:06:36] <mojavelinux> excellent
[23:06:47] <kenfinnigan> Hi lincolnthree
[23:06:51] <jose_freitas> hi lincolnthree
[23:07:26] <mojavelinux> first, before any topic or announcement, I want to start by saying thanks
[23:07:44] <mojavelinux> thanks for all the great work, we annihilated bugs last week
[23:08:49] <mojavelinux> 70 to 0 in 2 days, that's a pretty amazing feat, but it also shows a lot of initiative
[23:09:24] <mojavelinux> i'll be the first to admit that I often look at bugs and assume they will just get fixed
[23:09:39] <kenfinnigan> Haven't we all
[23:09:44] <mojavelinux> so I really appreciate it when I see people scanning through the list and trying to find something to fix
[23:09:48] <kenfinnigan> New features are more fun
[23:10:20] <mojavelinux> yep, it's especially fun to scratch your own itches rather than scratching the back of someone else
[23:10:25] <mojavelinux> yet once we got going
[23:10:52] <mojavelinux> it really inspired everyone to get into the mood of making seam ready for final
[23:11:48] *** ALR has quit IRC
[23:12:51] *** ALR has joined #seam-dev
[23:12:54] <mojavelinux> so good job...and thanks for being a part of the team. my wife wants to kill me by now for talking about you all so much :)
[23:13:12] <jose_freitas> hehehe
[23:14:58] <mojavelinux> with that said, i know that we still have a ways to go with seam, but as larry page says "the work is not done. and there is nothing more fun than doing that work" :)
[23:15:17] <mojavelinux> jose, you did a training last week, are there some thoughts that you want to share from it?
[23:15:57] <jose_freitas> well, people really got confused with the nature of the proxied injection, and I had a bad time explaining to everyone
[23:16:21] <jose_freitas> besides that we discussed a lot about design patterns, use of ejb directly on a view
[23:16:36] <jose_freitas> and they seemed to accept that
[23:16:43] <jose_freitas> about seam, they really loved catch
[23:17:13] <jose_freitas> I presented security, config, faces, persitence, catch and remoting
[23:17:32] <mojavelinux> did you use the booking example, or another example?
[23:17:39] <jose_freitas> yes
[23:17:41] <jose_freitas> booking example
[23:17:55] <jose_freitas> but we builded some things also
[23:17:58] <jose_freitas> in the exercises
[23:18:00] <mojavelinux> cool
[23:18:46] <mojavelinux> yes, the proxied injection is tough, because even though you want the scope to not be the concern of the client, the client does need to know what guarantees it is getting
[23:19:19] <mojavelinux> sounds like perhaps a good point for the opening chapters of seam or even the weld reference guide
[23:19:29] <mojavelinux> btw, has everyone seen the CDISource initiative?
[23:19:37] <kenfinnigan> Not yet
[23:19:41] <mojavelinux> http://java.dzone.com/articles/announcing-cdisource
[23:19:49] <mojavelinux> started by Andy Gibson and Rick Hightower
[23:19:57] <mojavelinux> Andy has been a long-time follower of the Weld and Seam projects
[23:20:00] <jose_freitas> I saw it
[23:20:14] <mojavelinux> and Rick is a well-respected developer in the Spring camp
[23:20:20] 
[23:20:20] <mojavelinux> Spring and JSF that is
[23:20:39] <jose_freitas> I'll start to blog and use twitter
[23:20:46] <jose_freitas> to advocate more about cdi
[23:21:00] <jose_freitas> and seam :)
[23:21:10] <mojavelinux> don't be timid about joining, I think this initiative will help us support each other in training and teaching
[23:21:33] <mojavelinux> in fact, in a way, it's sad to me that Red Hat wasn't the one that launched it, because we should have been on the one hand
[23:21:41] <mojavelinux> but on the other hand, I'm just as happy it was started in the community
[23:21:43] <mojavelinux> even better
[23:21:55] <mojavelinux> because there really isn't a good central source of information for CDI
[23:22:21] <mojavelinux> so hopefully we'll be able to work with them to spread the word about CDI
[23:22:35] <mojavelinux> it breaks my heart everytime I see Maven pulling in Guice as a dependency for another project I'm using
[23:22:41] <mojavelinux> :(
[23:22:45] <jose_freitas> hehehe
[23:24:22] <nickarls> BTW is http://groups.diigo.com/group/cdi-extensions referenced in CDI source?
[23:24:48] <mojavelinux> that's actually something I was going to talk about, thanks for bringing that up
[23:25:12] <mojavelinux> making a diigo as a cdi-extensions directory was, well, not really that successful
[23:25:21] <mojavelinux> i'd like to take a slightly different approach
[23:25:29] <mojavelinux> instead, I'd like to do what we did with arquillian
[23:25:44] <mojavelinux> we have a diigo account for articles, blogs, tutorials, etc about a topic
[23:26:09] <mojavelinux> then anytime you see a decent article, you post it...so it's a catalog of promoted information on the web about the topic
[23:26:17] <mojavelinux> and then people can vote it up or down
[23:26:27] <kenfinnigan> Sounds like a good idea
[23:26:32] <mojavelinux> it's a little different than submitting to dzone and the like because I sort of consider it our catalog
[23:26:37] <jose_freitas> like dzone?
[23:26:40] <jose_freitas> ok
[23:26:49] <mojavelinux> when I need information about arquillian, I always use the diigo group
[23:27:00] <mojavelinux> it's pure and it sort of becomes our recommended resources
[23:27:11] <mojavelinux> and we can prune things that turn out to be not that useful
[23:27:33] <mojavelinux> plus, using tags, we can easy classify the links as advanced, beginner, etc
[23:27:47] <mojavelinux> it's really quite easy to maintain...I usually add about one a week to the arquillian one
[23:28:10] <mojavelinux> and if you just post it in IRC someone will make sure it's up there
[23:28:18] <mojavelinux> then yes, that I hope to have linked from cdisource
[23:28:43] <mojavelinux> anything related to a seam module would just get tagged seam
[23:28:52] <mojavelinux> and the module as well
[23:28:54] <aslak> mojavelinux, #jbosstesting
[23:29:44] <mojavelinux> there is still the issue of a catalog of extensions, I'll have to see what andy and rick have in mind
[23:29:56] <mojavelinux> but we haven't really found the right solution yet to advocate for them properly
[23:31:21] <mojavelinux> remember that when you talk about cdi, seam, etc, the goal is not simply to convert people to "the one true way"; instead, as jose was saying, talk about patterns and best practices
[23:31:31] <mojavelinux> try to figure out what people need, what they struggle with, and what we can improve on
[23:32:05] <mojavelinux> because seam isn't the perfect developer experience yet...but I know we can make it a very excellent one by taking in feedback and listening
[23:32:16] <mojavelinux> I always have to remind myself of that in my talks, gotta do more of that :)
[23:32:47] <mojavelinux> let's turn complaints into jiras :)
[23:32:51] <jose_freitas> mojavelinux: that's definetelly a point worth mention, best practices
[23:32:59] <nickarls> remember to throw in some Spring FUD, too ;-)
[23:33:09] <mojavelinux> hahha
[23:33:17] <jose_freitas> I'll write about some insights I have about that those days
[23:33:37] <jose_freitas> and we have to destroy some myths as well
[23:33:41] <mojavelinux> well, with Rick on board, that should make the Spring camp do a neck bone
[23:33:55] *** daniel_hinojosa has quit IRC
[23:34:07] <maschmid> mojavelinux: Any recommended reading material about pattrerns and best practices?
[23:34:14] <kenfinnigan> Is it worth putting together a CDI patterns page somewhere?
[23:34:32] <kenfinnigan> That become a replacement for j2ee patterns
[23:34:38] *** wdrai has left #seam-dev
[23:34:44] <mojavelinux> #agreed it's worth putting together a CDI patterns page on the wiki; as a replacement for the old j2ee patterns
[23:34:46] <mojavelinux> yep
[23:35:17] <jose_freitas> there's a book by Adam biens called: Real World Patterns:
[23:35:22] <jose_freitas> Rethinking patterns
[23:35:31] <mojavelinux> cdi patterns will no doubt be more agile than the j2ee patterns, because cdi is really more about programming best practices (design by contract and interfaces) than a set of rigid solutions
[23:35:42] 
[23:35:50] <mojavelinux> yeah, to be honest, at this point, I would say some of the best reading material on the subject is Adam Bien's work
[23:36:05] <jose_freitas> yet on his blog he have some great material
[23:36:14] <mojavelinux> I like the way that he thinks
[23:36:19] <jose_freitas> me too
[23:36:29] <jbossbot> git [forge] push master c863bfb.. Lincoln Baxter, III scaffold create indexes example now shows --overwrite
[23:36:29] <jbossbot> git [forge] push master URL: http://github.com/seam/forge/compare/c3ae0a2...c863bfb
[23:36:32] <mojavelinux> so far, the reading material we have for cdi is
[23:37:17] <mojavelinux> ...
[23:37:21] <mojavelinux> hard for dan to find
[23:37:22] <mojavelinux> ...
[23:37:25] <jose_freitas> lol
[23:37:51] <kenfinnigan> If it's hard for you, it would be impossible for the rest of us
[23:38:15] <mojavelinux> http://seamframework.org/Community/LinksToExternalCDIAndWeldDocumentation
[23:38:16] <mojavelinux> hahaha
[23:38:41] <mojavelinux> yeah, I know, that's why we need to see earlier idea of our article catalog
[23:38:48] <mojavelinux> which will be seeded by that list
[23:39:01] <mojavelinux> #agreed need a link to a catalog of articles about cdi and seam
[23:39:14] <mojavelinux> maschmid: hopefully those will cover some best practices
[23:39:21] <mojavelinux> and we'll make sure we label them as such when they do
[23:39:26] *** bleathem has joined #seam-dev
[23:40:03] <mojavelinux> so the answer to your question is, we are in the collection stage ;)
[23:40:08] <maschmid> mojavelinux: cool, thanks! :)
[23:40:25] <mojavelinux> there's also a first attempt here which i'll merge in
[23:40:37] <mojavelinux> http://groups.diigo.com/group/cdi-tech-hub
[23:40:56] <mojavelinux> lincoln has asked to talk to you guys about forge plugins
[23:41:26] <lincolnthree> *takes the mic*
[23:41:36] <jose_freitas> hehehe
[23:41:38] <lincolnthree> Hey everyone
[23:41:50] <bleathem> hey lincoln
[23:42:10] <lincolnthree> As I'm sure some of you are already aware, Forge is starting to take shape in terms of plugin writing.
[23:42:37] <lincolnthree> And with Seam 3.0.0.Final on the horizon.
[23:42:55] <jose_freitas> *clap clap clap*
[23:43:05] <lincolnthree> We think it's a good time to think about starting to write Seam plugins for Forge.
[23:43:36] <lincolnthree> I know issues, enhancements, and bugs will start to roll in soon, but? how to say this.
[23:44:03] <lincolnthree> sbryzak: mojavelinux, and I think now is a good time for module leads to spend some time learning Forge, since it is going to be a crucial part of the Seam vision, to make development more productive.
[23:44:26] <kenfinnigan> Makes sense
[23:44:53] <lincolnthree> The docs are located here: file:///Users/lbaxter/Downloads/forge-1.0.0-SNAPSHOT/doc/reference/html_single/index.html
[23:45:04] <lincolnthree> More specifically:
[23:45:04] <jose_freitas> lincolnthree: what kind of plugins do you have in mind (being imaginative)
[23:45:12] <lincolnthree> file:///Users/lbaxter/Downloads/forge-1.0.0-SNAPSHOT/doc/reference/html_single/index.html#forge.plugin.dev
[23:45:14] <lincolnthree> oops
[23:45:28] <lincolnthree> http://docs.jboss.org/forge/snapshot/reference/en-US/html_single/
[23:45:29] <lincolnthree> sorry about that
[23:45:36] <bleathem> the seam-gen plugin for forge
[23:45:59] <lincolnthree> http://docs.jboss.org/forge/snapshot/reference/en-US/html_single/#forge.plugin.dev
[23:46:20] <lincolnthree> Yes, so at a basic level, taking care of installing the Seam modules
[23:46:26] <lincolnthree> Providing easy configuration for them
[23:46:38] <lincolnthree> Basically attempting to lower the barrier to entry for Seam 3
[23:46:51] <lincolnthree> So if I want to get started with Security, I would run 'forge' and type something like:
[23:46:58] <lincolnthree> $ seam-security setup
[23:47:12] <lincolnthree> which would figure out what I need to do and guide me through installation
[23:47:27] <lincolnthree> Think of it as a maven archetype on steroids.
[23:47:49] <lincolnthree> But it can also be more than that, for example, I want to see a report of which URLs are secured by my current configuration.
[23:47:52] <lincolnthree> So I would type:
[23:47:53] <bleathem> we need jpa reverse engineering, and JSF page creation plugins
[23:47:53] <jose_freitas> oic, and it would create dependencies to seam-security, maybe to seam-config, and maybe we could create a basic authenticator with its configuration
[23:48:10] <lincolnthree> $ seam-security list-secured-urls
[23:48:25] <lincolnthree> jose_freitas: exactly
[23:48:44] <jose_freitas> it sounds good
[23:49:28] <lincolnthree> To wet your appetites...
[23:49:35] <lincolnthree> Developing a plugin is as simple as:
[23:50:02] <lincolnthree> $ new-project ?named myplugin ?topLevelPackage org.mypackage
[23:50:09] <lincolnthree> $ project install-facet forge.api
[23:50:20] <lincolnthree> Then create a class extending "Plugin"
[23:50:23] <lincolnthree> implementing*
[23:50:41] <lincolnthree> Even more enticing is the way plugins are distributed.
[23:51:26] <lincolnthree> All you need to do is push your plugin into a git repo, and tell users where that repository lives. When they install, It will clone the repo, build the project, install the plugin, and hot-load it while forge is running.
[23:51:54] <lincolnthree> here's an example of me installing the PrettyFaces plugin from Git while forge runs: http://pastebin.com/EEGLRHLJ
[23:52:03] <bleathem> should forge plugins line in each respective module? or in the Forge project?
[23:52:13] <lincolnthree> I was talking about sbryzak on that subject
[23:52:15] <bleathem> ^live in, not line in
[23:53:09] <lincolnthree> From my perspective. One repo for each plugin is easier to deal with.
[23:53:15] <gmorling_> how about pulling in forge plug-ins from maven repositories?
[23:53:16] *** jose_freitas is now known as jose_freitas_afk
[23:53:20] <lincolnthree> But for the team's perspective, one repo with all plugins may make more sense.
[23:53:26] * jose_freitas_afk have to go
[23:53:27] <lincolnthree> gmorling_: yep, that works too
[23:53:37] <lincolnthree> http://docs.jboss.org/forge/snapshot/reference/en-US/html_single/#plugin.dev.installing.mvn
[23:53:53] <gmorling_> to me this seems better then building it locally
[23:54:02] <lincolnthree> Yes, definitely.
[23:54:38] <kenfinnigan> Could we have a plugins dir with each module like impl and API?
[23:55:03] <lincolnthree> kenfinnigan: that's one option
[23:55:10] <bleathem> that sounds good
[23:55:29] <lincolnthree> mojavelinux: what do you think? should we take a vote or should this be discussed on seam-dev@jboss ?
[23:55:32] *** maschmid has quit IRC
[23:55:50] <gmorling_> so the current approach strictly requires git to incorporate addtional plug-ins?
[23:56:14] <lincolnthree> No
[23:56:23] <lincolnthree> You can install plugins from:
[23:56:29] <lincolnthree> 1. A local .jar file
[23:56:36] <lincolnthree> 2. A remote (URL) .jar file.
[23:56:49] <lincolnthree> 3. A mvn artifact ID. (Searches most repos, or specify a custom repo)
[23:56:54] <lincolnthree> 4. Local project source files.
[23:56:56] <lincolnthree> 5. Git
[23:57:06] <gmorling_> ah, ok. now i'm happy :-)
[23:57:18] <lincolnthree> There is also a prototype plugin index which will allow for searching and installing plugins by name
[23:57:40] <lincolnthree> $ forge find-plugin {query}
[23:58:23] <mojavelinux> there should be a plugin directory in each module I believe
[23:58:30] <bleathem> +1
[23:58:37] <lincolnthree> +1
[23:59:05] <mojavelinux> also, the key to getting this initiative off the ground
[23:59:18] <mojavelinux> beyond putting together the awesome framework, which was a lot of work and a big part of it
[23:59:23] <mojavelinux> so credit that *cheers*
[23:59:29] <lincolnthree> *cheers*
[23:59:32] <mojavelinux> is that you have to get people to see their itch
[23:59:48] <mojavelinux> and to see an itch, we need a plugin ideas whiteboard
[23:59:54] <mojavelinux> there is the start of one
[23:59:57] <mojavelinux> on the forge page





top