15:05:04 #startmeeting 15:05:12 Meeting started Mon May 2 15:05:04 2011 UTC. The chair is sebersole. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:05:12 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:05:57 so the main thing we need to discuss today is the new metamodel and whether we will drive forard with that 15:06:36 tbh i am not feeling confident we will make our dates 15:06:43 for sure not as it is going today 15:07:22 no, I don't think we can 15:07:36 trust me, i understand the new code is "better"; its the reason i have been working on it for nearly 2 years in spare time 15:07:55 but the dates are the dates at this point 15:09:20 hardy: ? 15:09:25 i already mentioned my concerns regarding the deadlines as well 15:10:19 so do we just scrap it and move forward with the "revert"? 15:11:04 what is your revert? 15:11:08 stliu: you have been very productive here, what are your thoughts? 15:11:41 i'm looking gail's task list 15:11:59 well i envision revert as keeping the old mapping stuff 15:12:18 as i said last week, ideally incorporating the new domain model 15:12:33 sorry 15:12:38 the new relational model 15:13:02 if we keep the old mapping stuff (not even taking the relational stuff) what do we have to do then? 15:13:18 we have to change the binding code 15:13:22 but 15:13:31 the "build persister code" is the same 15:13:47 well more-or-less, depending on relational model 15:14:03 then there wouldn't need to be an integration step? 15:14:19 what is "integration step"? 15:14:53 the mapping code is already operational 15:15:04 no its not 15:15:26 you mean the new binding/modeol code? 15:15:58 my point was simply that the code to build persisters from o.h.mapping objects is already in place 15:16:08 yes, that's what I meant 15:16:27 sebersole: so which binding code has to change? 15:16:46 AnnotationBinder and HbmBinder 15:16:50 sebersole, I like the idea of tweaking the mapping code 15:16:55 gbadner: i hate it 15:16:59 but its what we have 15:17:10 i hate it as well 15:17:20 sebersole, at least that way, we can see if it's working as we go 15:17:30 see if what is working? 15:17:43 AnnotationBinder is a very fuggly piece of code to change 15:17:47 anyway 15:17:51 hardy, what if we could get everyone working on this, like emmanuel, sanne? 15:18:00 stliu: not an option really 15:18:05 we can run the full unit test suite and see if our changes break anything 15:18:20 sanne has to get search ready for 4.0 15:18:26 right now, w/ the new code, there's no way to do that 15:18:48 it would be nice to get more on board, but there is also the question on how much we can split the tasks 15:18:57 AND there is of course Search 15:19:05 search 4.0 has been released, hasn't it? 15:19:17 I pretty much are off the list for Search 4.0, so it is Sanne 15:19:22 3.4 is released 15:19:30 oh, yeah, sorry 15:19:38 gbadner: consuing mapping and consuming metamodel are still completely different / parallel tasks 15:19:47 4.0 is the next release where we similar to Core planning to change several APIs 15:19:51 so how does that help test? 15:20:27 btw, emmanuel is the next few weeks on vacation and conferences - I don't think he can help muhc 15:20:44 stliu: how much time can you give to the effort over the next 5 weeks? 15:21:06 3-4 weeks i'd think 15:21:20 what I'm saying is that if we tweak the old code, we can see if it causes unit test failures 15:21:37 there is one eap release i have done before May 11 15:22:25 jpav: how far along are you on the tasks hardy gave you ? 15:22:42 I was close to done until the JIRA was updated today 15:22:55 no idea what that means 15:23:00 But I still had several things I needed to run by hardy 15:23:19 hardy added several additional global configuration components that need to be accounted for 15:23:26 right 15:23:48 see this is my concern. all i see is a lot of uncertainty :) 15:23:53 how do you take care of them? I mean did the new metamodel cater for them already? 15:23:57 HHH-6132? 15:24:02 jira [HHH-6132] Process and bind global configuration annotations [Open (Unresolved) Sub-task, Major, John Verhaeg] http://opensource.atlassian.com/projects/hibernate/browse/HHH-6132 15:24:15 not much we can "hang our hat on" 15:24:37 sebersole, I agree 15:25:23 gbadner: did you finish up that jira i asked you to look at? 15:25:51 oy, which one? 15:26:09 stliu: yes, that's the issue 15:26:47 personally i think we ought to power through this 15:26:56 but i cannot do it on my own 15:27:24 you'd hardly be doing it on your own... 15:27:28 its the last chance we will get to MakeThisRight for quite some time 15:28:17 well i think for sure we need to reorg the worjk quite a bit 15:28:57 if stliu is on board for a good chunk of work i feel better 15:29:29 i will :) 15:29:33 sweet! 15:29:38 right, maybe stliu can continue helping me on the annotation front ;-) 15:29:44 negative 15:29:48 ;) 15:29:52 ahhhhhhhhhhh 15:29:57 nah, actually thats probably best 15:30:17 smarlow_: have we figured out the best way to pass on the jandex stuff yet? 15:30:29 when i looked it did not seem possible tbh 15:30:36 well, if gail want to mock hbm elements to annotation, i'd like continue working on that 15:30:51 stliu: thats not possible 15:30:57 if this is the path we want to go 15:31:03 it makes things more complicated 15:31:41 even though it sounds nice in theory I think it would be faster to continue to have jpa and hbm separately 15:31:58 gbadner: HHH-2049 15:32:02 jira [HHH-2049] LEFT OUTER JOIN subcriteria filters children [In Progress (Unresolved) Bug, Major, Gail Badner] http://opensource.atlassian.com/projects/hibernate/browse/HHH-2049 15:32:06 sebersole: I'm currently, sort of passing it to myself, for the annotation scanner that I pass via "hibernate.ejb.resource_scanner" 15:32:11 if time wouldn't be a factor I would definitely give it a go, but in the current situation ... 15:32:28 hardy: these kinds of things are impl/internal details 15:32:33 we can easily try later 15:32:39 exactly 15:32:43 as it does not effect the apis 15:32:48 sebersole, ok, thanks 15:32:52 +1 15:33:05 we really need to be focused here on stuff that affects apis 15:33:10 of rht next 5 weeks that is 15:33:27 smarlow_: cool 15:33:50 so from there it really comes down to the last big question i see for 4.0 15:34:06 how to manage EJB3Configuration/building-EMF 15:34:41 do we want to support users directly building EMF? 15:34:45 or 15:34:54 do we only support them using the JPA defined mechnisms 15:35:18 hardy: thoguhts? 15:35:45 i have not really been involved in that enough to make an educated decision 15:35:49 not many. I don't have the big picture here 15:35:54 same here 15:36:10 just JPA mechanisms sounds good at the first thought 15:36:22 emmanuel indicated that JPA bootrapping was the preferred mechnism 15:36:33 so maybe we can work on that assumption for the time being 15:36:40 definitely the preferred way 15:36:44 +1 15:37:07 alright, we definitely need that in place for alpha3 15:37:11 not sure what the usecases are for the direct building of the EMF 15:37:16 i think emmanuel is the one to ask here 15:37:33 well it would corelate to whenever EJB3Configuration is used today 15:37:43 used directly i mean 15:38:05 well, the only usage I am aware of is for testing purposes 15:39:06 what I mean is that our EM tests are using the EJB3Configuration under the hood. at least I think so 15:40:08 hardy: yeah i think so 15:40:14 there is for example a BaseEntityManagerFunctionalTestCase which uses it 15:40:28 and a whole bunch of tests derive of it 15:41:08 that does not say much of course about the usage of EJB3Configuration "in the wild" 15:41:51 but the sensible thing to do has always been to use the persistence API 15:41:55 well its not worse than Configuration itself :) 15:42:33 anyway, i cannot find the email discussion anymore about building emf 15:43:50 between emails, and wikis and gists getting hard to track info 15:45:06 so how much metamodel work is not yet pushed? 15:45:20 jpav's "global" stuff i guess 15:45:31 hardy: ? 15:45:35 gbadner: ? 15:45:39 afaik 15:45:44 mine is not pushed yet 15:45:48 i have some work from today 15:45:59 stliu: all of it? 15:46:03 I tend to pull/push pretty miuch daily 15:46:07 maybe Wed or Thu 15:46:18 stliu: thats all of orm.xml ? 15:46:22 sebersole, my stuff is checked in 15:46:30 meaning none of it is pushed? 15:46:40 sebersole, yes, and i have to ask jason to get jandex-2 resolved first 15:46:45 ok 15:46:51 just checking 15:47:06 can you make it in time for release? 15:47:14 alpha3 15:47:24 oh, i guess not 15:48:16 me? 15:48:28 for stliu's work we really need the jandex issue resolved 15:48:41 i think i can, alpha 3 is May 11, right? 15:48:50 i just send a mail to jason 15:48:55 nope, this wed 15:48:59 stliu: no, alpha3 is in 2 days 15:49:08 jason is probably at JBossWorld. 15:49:19 then again, it is such a small change 15:49:36 stliu: have you created a push request for Jason 15:49:44 well, our jira shows alpha 3 is May 11 .. 15:49:59 maybe we gained a week ;-) !? 15:50:04 hardy, no, it is a very simple fix 15:50:13 i know, one method 15:50:18 http://opensource.atlassian.com/projects/hibernate/browse/HHH#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel 15:50:30 and beta 1 is Jun 11 15:51:05 11 is the year ;) 15:51:48 jira shows 4/May/11 15:51:52 he he 15:51:56 damn ...., you know, in china, we use yyyy-mm-dd 15:52:01 yeah i do too 15:52:07 less confusing 15:52:12 and the swedes use mm-dd-yyyy - the worst of all! 15:52:24 thats what most of US uses 15:52:33 i have missed more than one appointment because of it 15:52:38 yup, terrible for sorting 15:52:42 makes no sense to me 15:53:31 so for alpha3... i'll work on finishing up the api work and looking over the metamodel code 15:53:49 ok 15:53:53 after alpha3 i'll start directing the metamodel work a bit more and lending a hand 15:53:59 so we keep battling on 15:54:03 so, my work probably can't go into alpha 3 15:54:12 sebersole, that would be great 15:54:17 hardy: right keep on keeping on for now 15:54:21 ok 15:54:28 gbadner: well only way its gonna get done 15:54:44 you know the most about it 15:54:52 hardy: Are you going to be online for a few more hours today? 15:55:06 most about code i did not write or conceptualize? 15:55:11 ok 15:55:16 yup 15:55:28 I have a meeting now, but can check in later again 15:55:32 k, hardy 15:55:40 k 15:56:30 jpav, fyi, i will mock all jpa global configurations to index 15:56:50 depends which entity be found first 15:57:14 The code I've been working on is starting with the indexes 15:57:40 that's good 15:57:58 gbadner, btw, we need HHH-2049 resolved asap 15:58:03 jira [HHH-2049] LEFT OUTER JOIN subcriteria filters children [In Progress (Unresolved) Bug, Major, Gail Badner] http://opensource.atlassian.com/projects/hibernate/browse/HHH-2049 15:58:28 smarlow_: btw, not sure if you saw but i pushed those changes for jboss jta platform 16:01:35 sebersole: yup, I synced up friday with the changes and pushed updates to the as7 hibernate40_2 branch :) 16:01:52 #endmeeting