[00:00:37] *** lincolnthree has quit IRC
[00:02:24] *** bitshuffler_ has quit IRC
[00:07:03] <jbossbot> git [solder] push master 967e42a.. Jozef Hartinger Test for GLASSFISH-15791
[00:07:04] <jbossbot> git [solder] push master URL: http://github.com/seam/solder/compare/f1b8d8d...967e42a
[00:08:57] *** bitshuffler__ has quit IRC
[00:22:40] *** rruss has joined #seam-dev
[00:46:18] *** aslak has quit IRC
[00:46:41] <jbossbot> git [dist] push master caddb01.. Shane Bryzak added picketlink-idm-spi
[00:46:41] <jbossbot> git [dist] push master URL: http://github.com/seam/dist/compare/ff8dad8...caddb01
[00:47:25] <jbossbot> git [security] push master 67429c6.. Shane Bryzak add structure for simple authentication example
[00:47:25] <jbossbot> git [security] push master 923149a.. Shane Bryzak minor
[00:47:25] <jbossbot> git [security] push master 2f5a5db.. Shane Bryzak added combined jar to build
[00:47:26] <jbossbot> git [security] push master 613c8c0.. Shane Bryzak add combined module to root pom
[00:47:26] <jbossbot> git [security] push master a44acdc.. Shane Bryzak refined api dependencies
[00:47:26] <jbossbot> git [security] push master URL: http://github.com/seam/security/compare/2f5ab29...a44acdc
[00:59:57] *** cbrock has quit IRC
[01:05:34] *** rruss has quit IRC
[01:10:24] <jbossbot> git [dist] push master 6226a60.. Shane Bryzak move exclusions to bom
[01:10:24] <jbossbot> git [dist] push master URL: http://github.com/seam/dist/compare/caddb01...6226a60
[01:22:34] <jbossbot> git [security] push master 34fab3e.. Shane Bryzak updated combined jar dependencies
[01:22:34] <jbossbot> git [security] push master URL: http://github.com/seam/security/compare/a44acdc...34fab3e
[01:39:13] *** balunasj has joined #seam-dev
[01:40:41] *** lightguard_jp has quit IRC
[02:02:41] *** balunasj has quit IRC
[02:45:43] *** johnament has joined #seam-dev
[02:52:24] *** johnament has quit IRC
[02:57:49] *** johnament has joined #seam-dev
[04:14:14] *** tsurdilo has quit IRC
[04:28:51] *** johnament has quit IRC
[04:38:33] <jbossbot> git [security] push master 9377ed5.. Shane Bryzak SEAMSECURITY-29, implemented basic authentication example
[04:38:34] <jbossbot> jira [SEAMSECURITY-29] Create a simple authentication example [Open, Major, Shane Bryzak] https://issues.jboss.org/browse/SEAMSECURITY-29
[04:38:34] <jbossbot> git [security] push master URL: http://github.com/seam/security/compare/34fab3e...9377ed5
[05:26:20] *** clerum has quit IRC
[05:42:47] *** bitshuffler has joined #seam-dev
[05:53:56] *** bitshuffler_ has joined #seam-dev
[05:57:27] *** bitshuffler has quit IRC
[06:38:40] <jbossbot> git [faces] push master 76502f7.. Brian Leathem Updated the Messages package in the messages API chapter of the faces documentation
[06:38:40] <jbossbot> git [faces] push master URL: http://github.com/seam/faces/compare/214bc59...76502f7
[06:56:16] *** allforjava has joined #seam-dev
[07:07:56] *** rpetruescu has joined #seam-dev
[07:13:33] <allforjava> Hi, like 'Seam-Generate Entities' need to develop tool to generate entities based on customized/our templates. Newbie towards seam-gen and eclipse plugin/tool development. From where I need to start.
[07:33:20] *** lukaszlenart has joined #seam-dev
[07:38:24] <stuartdouglas> allforjava: Seam gen actually uses hibernate tools under the covers
[07:38:42] <stuartdouglas> and hibernate tools lets you customise the templates using the volocity templating engine
[07:40:07] <allforjava> i hv heard that seam-gen is using Freemarker for templating
[07:40:33] <stuartdouglas> from memory it is velocity, but I am not 100% sure
[07:41:05] <allforjava> now I need where i need to begin modifications and way to test it
[07:41:17] <allforjava> any documents?
[07:42:00] <stuartdouglas> have a look at the hibernate tools documentation
[07:42:05] <stuartdouglas> on the hibernate site
[07:42:42] <allforjava> and about plugin development i hv found the repo http://anonsvn.jboss.org/repos/jbosstools/branches/3.2.helios/seam/
[07:43:00] <stuartdouglas> that is jboss tools not hibernate tools
[07:43:20] <allforjava> yes agreed.
[07:43:35] <stuartdouglas> actually hibernate tools seems to have moved under jboss tools
[07:43:36] <allforjava> for seam JBoss-Tools provides a suite
[07:44:09] <allforjava> and though that would be possible way to begin
[07:44:12] <stuartdouglas> http://docs.jboss.org/tools/3.2.0.Beta1/en/hibernatetools/html_single/index.html#hbmtemplate
[07:44:13] <allforjava> customizing
[07:44:56] <allforjava> coz even I need to generate the .xhtml and .page.xml files along with security permissions
[07:45:42] <allforjava> with entities or/and copies of same entities with different templates and common properties
[07:46:12] <allforjava> looking @ the hibernate doc...
[07:46:31] <stuartdouglas> have a look at the seam gen source
[07:46:36] <stuartdouglas> at the .ftl files
[07:48:17] <allforjava> thank you very much Stuart Douglas u hv made my day
[07:48:33] *** lukaszlenart has left #seam-dev
[07:48:40] *** lukaszlenart has joined #seam-dev
[07:50:18] <allforjava>  are the .ftl files processed by hibernate tools or anything else
[07:51:20] <allforjava> i hv got the svn checkout of http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_2_Drools5/ with project name seam-gen in eclipse
[08:07:32] *** lukaszlenart has quit IRC
[08:13:55] *** lukaszlenart has joined #seam-dev
[08:24:12] <sbryzak> stuartdouglas: i'm getting a deployment exception when trying to deploy more than one app to JBoss AS that contains seam-persistence.jar
[08:24:22] <stuartdouglas> what is the exception?
[08:24:29] <sbryzak> one sec, i'll pastebin it
[08:24:55] <sbryzak> http://pastebin.com/nMLDQNAF
[08:25:18] <nickarls> known issue, methinks
[08:25:25] * nickarls is digging JBAS jiras
[08:26:00] <stuartdouglas> hmm
[08:26:41] <nickarls> https://issues.jboss.org/browse/EJBTHREE-2197 ?
[08:26:43] <jbossbot> jira [EJBTHREE-2197] Two WARs containing no-local-view EJBs with same name fails to deploy [Open, Major, jaikiran pai] https://issues.jboss.org/browse/EJBTHREE-2197
[08:28:14] <stuartdouglas> yea, I don't really know what we can do about that
[08:28:16] *** oskutka has joined #seam-dev
[08:29:16] <sbryzak> nickarls: it seems to be the same issue
[08:30:20] <stuartdouglas> It may be possible to add a deployment descriptor that changes the EJB name
[08:30:24] <nickarls> mucho annoying. bug jaikiran about it ;-)
[08:31:02] <sbryzak> is what he says about adding the deployment name in the JNDI really such a big deal for users?
[08:31:37] <nickarls> if you have Foo.war and TestFoo.war with 20 EJBs in the same instance, your screwed. unless you use separate explicit names and filter them in the build
[08:31:57] <stuartdouglas> if you would do it with deployment descriptors it would be ok
[08:32:14] <sbryzak> this is potentially going to be a big issue for seam users
[08:32:19] <nickarls> stu: I use annotations only in the normla case
[08:32:27] <sbryzak> many of them will be deploying multiple apps within the same jboss container
[08:32:35] <sbryzak> and persistence is a core module
[08:33:02] <stuartdouglas> hmm, I wonder if there is a way to re-do that without using ejb's
[08:33:16] <stuartdouglas> ...thinks...
[08:33:54] <nickarls> jaikiran is answering questions on the forum so he's awake, I guess he'll appear on #jboss-dev soonish
[08:34:02] <stuartdouglas> I will probably need to write a JTA TransactionManager version of synchronizations
[08:34:18] <nickarls> I think the general problem needs to be solved instead of just worked around for seam...
[08:34:44] <sbryzak> if stu can rewrite it without ejbs then the general problem will be solved ;)
[08:35:04] <stuartdouglas> The problem is that TransactionManager version will require some config
[08:35:19] <nickarls> well, the general problem involves *any* EJB included in two WARs
[08:35:19] <stuartdouglas> and won't work on some containers
[08:36:01] <stuartdouglas> yea, but thats a jboss 6 problem
[08:36:54] *** allforjava1 has joined #seam-dev
[08:36:56] <stuartdouglas> and I don't think they are going to get it fixed in time for our seam 3 release
[08:37:45] <sbryzak> we really need to have this working in jboss 6 final
[08:39:17] *** allforjava has quit IRC
[08:39:33] <stuartdouglas> hmm, actually I need to get rid of the EJB version entirely
[08:40:52] <stuartdouglas> so I will need to make the TransactionManager one the default, and if they are using a retarded container like, like say Websphere for instance, then they will need to use a deployment descriptor to make Syncronizations and ejb again
[08:41:31] <stuartdouglas> or else write a Synchronizations instance that uses UOWManager
[08:41:46] <sbryzak> do you know if glassfish users will have a problem?
[08:42:25] <stuartdouglas> should be fine
[08:42:36] <stuartdouglas> I think the jndi location of the TransactionManager is different
[08:42:42] <stuartdouglas> but I can just make it try both locations
[08:42:45] <sbryzak> cool
[08:42:53] <stuartdouglas> this also opens the door for REQUIRES_NEW support
[08:43:00] <stuartdouglas> as you need the TransactionManager for that
[08:43:35] <stuartdouglas> does any websphere version actually support CDI anyway?
[08:44:21] <sbryzak> not that i've heard
[08:44:31] <sbryzak> we're mainly concerned with jbas and gf
[08:44:51] <stuartdouglas> Actually if it can't find the TransactionManager it can just delegate to SeSyncronizations
[08:45:46] <stuartdouglas> although SeSynchonisation only works when seam controls the transaction
[08:46:10] <stuartdouglas> SEAMPERSIST-26
[08:46:11] <jbossbot> jira [SEAMPERSIST-26] Create a Synchronizations implementation that uses the JTA transaction manager [Open, Major, Stuart Douglas] https://issues.jboss.org/browse/SEAMPERSIST-26
[08:48:04] <sbryzak> do you think it might be fixed by the seam beta 2 release? (11 feb)
[08:48:09] <nickarls> anyone know what GF uses for EJB JNDI names if they don't have the issue?
[08:48:39] <sbryzak> nickarls: no idea, though i'm guessing some deployment-specific qualifier
[08:50:18] <stuartdouglas> I will try and get it done this weekend
[08:50:24] <stuartdouglas> It is not that much work
[08:50:59] <sbryzak> thanks :)
[08:51:17] <sbryzak> do you think we could then release it as CR1?
[08:51:43] <nickarls> stu: those are famous last words before an all-nighter ;-)
[08:51:46] *** marekn has joined #seam-dev
[08:53:37] *** bitshuffler_ has quit IRC
[08:54:34] *** mgencur has joined #seam-dev
[08:56:25] <stuartdouglas> sbryzak: I think so
[08:56:50] <sbryzak> stuartdouglas: ok, i'll add a CR1 version to JIRA, for release on 10th feb.. that ok?
[09:07:32] <jbossbot> git [security] push master 601136b.. Shane Bryzak SEAMSECURITY-25
[09:07:34] <jbossbot> jira [SEAMSECURITY-25] Cannot login into idmconsole application [Open, Major, Shane Bryzak] https://issues.jboss.org/browse/SEAMSECURITY-25
[09:07:34] <jbossbot> git [security] push master 1a0f5a2.. Shane Bryzak added log out button to simple authentication example
[09:07:35] <jbossbot> git [security] push master URL: http://github.com/seam/security/compare/9377ed5...1a0f5a2
[09:21:15] *** aslak has joined #seam-dev
[09:21:15] *** aslak has quit IRC
[09:21:15] *** aslak has joined #seam-dev
[09:26:32] *** jharting has joined #seam-dev
[09:35:33] *** emmanuel has joined #seam-dev
[09:46:29] *** aslak has quit IRC
[09:58:22] *** adamw1pl has joined #seam-dev
[10:34:12] *** shervin_a has joined #seam-dev
[10:43:35] *** aslak has joined #seam-dev
[10:43:35] *** aslak has quit IRC
[10:43:35] *** aslak has joined #seam-dev
[11:15:10] *** alesj has joined #seam-dev
[11:21:44] *** akazakov has joined #seam-dev
[11:23:47] <jbossbot> git [persistence] push master 25fac2e.. mgencur at redhat dot com code-coverage reporting
[11:23:47] <jbossbot> git [persistence] push master URL: http://github.com/seam/persistence/compare/bd58126...25fac2e
[12:03:26] *** allforjava1 has quit IRC
[12:07:58] *** pmuir has joined #seam-dev
[12:07:58] *** pmuir has quit IRC
[12:07:58] *** pmuir has joined #seam-dev
[12:17:42] *** sannegrinovero has joined #seam-dev
[12:17:44] <mgencur> stuartdouglas: ping
[12:17:57] <stuartdouglas> mgencur: pong
[12:18:19] <mgencur> stuartdouglas: hi Stuart, I setup the code-coverage in this job: http://hudson.qa.jboss.com/hudson/view/Seam%203/job/Seam-3.X-persistence-CI/
[12:18:34] <mgencur> you'll be able to see it there in a chart
[12:18:46] <stuartdouglas> hmm, I still can't get to hudson.qa.jboss.com
[12:18:58] <stuartdouglas> I thought once I was on the VPN I would have access?
[12:19:15] <mgencur> stuartdouglas: and what error do you get?
[12:19:30] <stuartdouglas> canot find server
[12:19:47] *** emmanuel has quit IRC
[12:19:55] <mgencur> stuartdouglas: hmm, have you sent a ticket to helpdesk?
[12:20:14] <stuartdouglas> no, I had not actually tried to access it until you sent me the link
[12:20:30] <mgencur> stuartdouglas: ic
[12:21:15] <stuartdouglas> what is the ip address?
[12:21:24] <stuartdouglas> maybe and entry in hosts will let me get to it..
[12:22:01] <mgencur> stuartdouglas: it's 10.16.90.43
[12:23:10] <stuartdouglas> now it works
[12:23:19] <mgencur> stuartdouglas: great!
[12:23:47] <mgencur> stuartdouglas: do you see the chart? there will be an update in a minute
[12:24:08] <stuartdouglas> cool
[12:32:02] <alesj> stuartdouglas: hudson access via link never worked for me as well
[12:32:21] <alesj> hence added direct link to .hosts
[12:44:55] <jbossbot> git [dist] push master 2b75135.. Shane Bryzak [maven-release-plugin] prepare release 3.0.0.b08
[12:44:55] <jbossbot> git [dist] push master URL: http://github.com/seam/dist/compare/6226a60...2b75135
[12:45:09] <jbossbot> git [dist] push master a483e4c.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[12:45:09] <jbossbot> git [dist] push master URL: http://github.com/seam/dist/compare/2b75135...a483e4c
[13:02:28] *** allforjava has joined #seam-dev
[13:04:31] <allforjava> Hi ! made svn checkout for JBoss Tools 'Seam' from http://anonsvn.jboss.org/repos/jbosstools/branches/3.2.helios/seam/
[13:04:53] <allforjava> how I need configure parent-pom.xml
[13:05:14] <jbossbot> git [security] push master 3de6024.. Shane Bryzak updated bom version
[13:05:14] <jbossbot> git [security] push master URL: http://github.com/seam/security/compare/1a0f5a2...3de6024
[13:05:47] <sbryzak> mgencur: i've updated the bom version in security, it should build again now
[13:06:07] <sbryzak> although the external module is failing a test for me, i need to e-mail marcel about it
[13:22:13] <mgencur> sbryzak: ok, I was about to add code-coverage to the external module, so will have to wait...
[13:23:30] <mgencur> sbryzak: what error do you get? compilation error?
[13:23:46] <sbryzak> mgencur: not sure, i think the integration test is failing
[13:23:52] <sbryzak> i'll run it again and see what the exception is
[13:23:58] <mgencur> sbryzak: thanks
[13:25:40] <mgencur> mgencur: hmm, now I'm getting this: Non-resolvable import POM: Could not find artifact org.jboss.seam:seam-bom:pom:3.0.0.b08 in jboss-developer-repository-group (https://repository.jboss.org/nexus/content/groups/developer/) @ line 34, column 22 -> [Help 2]
[13:26:56] <jharting> stuartdouglas: ping
[13:27:04] <sbryzak> mgencur: my bad, i didn't release the staged repository
[13:28:24] <sbryzak> mgencur: done
[13:29:42] <mgencur> sbryzak: great, do I have to add the URL to my settings.xml ?
[13:29:57] <mgencur> sbryzak: or it's public now
[13:29:59] <sbryzak> no, it's in the jboss nexus repository now
[13:30:10] <mgencur> sbryzak: ok, thanks
[13:30:11] <sbryzak> https://repository.jboss.org/nexus/content/groups/public/org/jboss/seam/seam-bom/3.0.0.b08/
[13:33:36] <mgencur> sbryzak: I'm getting a compilation error, is that the same for you? .....[ERROR] /home/mgencur/Java/git/seam3/security/external/src/main/java/org/jboss/seam/security/external/openid/OpenIdUser.java:[5,40] package org.jboss.security.auth.spi.Users does not exist
[13:33:36] <mgencur> [ERROR] /home/mgencur/Java/git/seam3/security/external/src/main/java/org/jboss/seam/security/external/openid/OpenIdUser.java:[12,32] cannot find symbol
[13:33:36] <mgencur> symbol: class User
[13:33:36] <mgencur> public class OpenIdUser extends User
[13:34:28] <mgencur> sbryzak: aha, it seems the problem is on my side
[13:34:41] <sbryzak> mgencur: was just about to suggest that ;)
[13:34:49] <mgencur> :)
[13:43:46] *** epbernard has joined #seam-dev
[13:43:46] *** epbernard is now known as emmanuel
[13:48:43] *** allforjava has left #seam-dev
[13:58:21] *** maschmid has joined #seam-dev
[14:01:12] *** balunasj has joined #seam-dev
[14:02:00] <jose_freitas> the sem 3 forum is getting really active =)
[14:02:03] <jose_freitas> seam*
[14:07:18] *** rruss has joined #seam-dev
[14:19:10] <amitev> cool
[14:20:05] *** adamw1pl has quit IRC
[14:40:21] *** shervin_a has quit IRC
[14:48:42] *** rruss has quit IRC
[14:50:53] <jose_freitas> clerum, do you have any documentantion on the mail module?
[14:51:05] <jose_freitas> ops, clerum is not here
[14:51:13] *** lightguard_jp has joined #seam-dev
[15:04:07] *** balunasj is now known as balunasj_busy
[15:06:31] <jbossbot> git [jms] push master e7a4b42.. mgencur at redhat dot com fix code-coverege to use maven dependency plugin and do proper cleanup
[15:06:31] <jbossbot> git [jms] push master URL: http://github.com/seam/jms/compare/539a589...e7a4b42
[15:20:02] *** balunasj_busy has quit IRC
[15:31:42] <jbossbot> git [rest] push master ee3bd10.. mgencur at redhat dot com fix code-coverage profile to use maven dependency plugin
[15:31:42] <jbossbot> git [rest] push master URL: http://github.com/seam/rest/compare/cdcd018...ee3bd10
[15:32:29] <amitev> has anyone had this issue - http://pastebin.com/s6mrRYJ1b ?
[15:32:57] <lightguard_jp> amitev: Unkown paste id
[15:33:19] <lightguard_jp> http://pastebin.com/s6mrRYJ1 ?
[15:34:02] <lightguard_jp> amitev: I think that's been answered on the forums, if not try updating to the solder beta3
[15:38:24] *** pmuir has quit IRC
[15:45:05] *** pmuir has joined #seam-dev
[15:45:19] *** clerum has joined #seam-dev
[15:46:25] *** lincolnthree has joined #seam-dev
[15:53:30] *** tsurdilo has joined #seam-dev
[15:53:37] *** pmuir has quit IRC
[15:55:28] *** pmuir has joined #seam-dev
[15:55:28] *** pmuir has quit IRC
[15:55:28] *** pmuir has joined #seam-dev
[16:01:52] *** tsurdilo1 has joined #seam-dev
[16:03:41] *** balunasj has joined #seam-dev
[16:04:02] *** tsurdilo has quit IRC
[16:19:20] *** bdlink has joined #seam-dev
[16:21:01] *** marekn has quit IRC
[16:40:58] <amitev> is such thing as foreground and background conversation in CDI?
[16:41:11] <lincolnthree> amitev: not unless ou implement an extension yourself
[16:42:41] <amitev> what will happen if conversation timeout is 5min, session timeout is 30 min and the user idles for 10 min and does something after that?
[16:42:46] <amitev> exception?
[16:42:59] <lincolnthree> Yep, you'll get a NoSuchConversationException or something like that
[16:43:48] <amitev> that would be the most UNwanted behavior :)
[16:44:10] <lincolnthree> Yeah, so you have to handle it
[16:44:16] <lincolnthree> Seam Catch comes to mind :)
[16:46:32] *** lukaszlenart has quit IRC
[16:46:53] *** bdlink has quit IRC
[17:06:20] <lightguard_jp> :) yes, Catch would be very good at handling that
[17:12:21] <amitev> so if i want to have a foreground-like conversation i'll have to set the timeout to be equal to the session timeout
[17:15:24] *** balunasj has quit IRC
[17:17:31] <clerum> well you can also have an ajax poller or something to keep conversations active on pages which are open
[17:17:49] <clerum> otherwise you are going to end up with a lot of stale open conversations
[17:18:46] <amitev> true, but both are workarounds
[17:19:00] <lincolnthree> Our entire jobs are a workaround ;)
[17:19:06] <clerum> in my apps I open a lot of conversations
[17:19:13] <clerum> but 90% are abandoned
[17:19:20] <clerum> and are timedout in 5 minutes
[17:19:34] <clerum> unless the user sits with the page open in their browser
[17:19:39] <lincolnthree> Using a single conversation that lasts the length of the session is? the session ;)
[17:21:33] <amitev> sure but no one clears your beans when the unit of work ends
[17:22:44] *** oskutka has quit IRC
[17:23:02] <clerum> really depends on how your app and navigation works
[17:23:20] <clerum> might work for you, but a convo timeout of 30 minutes would kill my server
[17:32:24] <amitev> clerum: what do you tell the user when his conversation timeouts?
[17:33:34] *** jharting has quit IRC
[17:35:18] *** mgencur has left #seam-dev
[17:46:29] *** jose_freitas has quit IRC
[17:51:09] *** jose_freitas has joined #seam-dev
[17:57:10] <clerum> sorry this conversation has timed out
[17:57:19] <lincolnthree> *OWNED!!!!!!*
[17:57:28] <lincolnthree> that's what i tell them
[17:58:05] <clerum> if I was cool I would do something like this https://github.com/seam/monkey
[17:58:16] <jose_freitas> lol lightguard_jp
[17:58:20] <jose_freitas> ops, lincolnthree
[17:58:43] <lincolnthree> Specifically
[17:58:55] <lincolnthree> "Your conversation got *OWNED!!!!!!*"
[18:00:09] <lightguard_jp> https://github.com/503
[18:02:20] <amitev> lincolnthree: nice. but the user usually has no idea what conversation really means :)
[18:02:45] <lincolnthree> amitev: in the case of uneducated users:
[18:02:46] <lightguard_jp> In some seam2 apps they call them workspaces
[18:03:11] <clerum> "We are sorry but you have been sitting idle for too long"
[18:03:28] <lincolnthree> "Oops! The confidential information we've been tracking on you seems to have been lost. Have you seen it?"
[18:03:49] <amitev> rofl
[18:04:03] <clerum> "Our server got bored with your inactivity and started watching sponge bob. Give it another shot"
[18:04:33] <lincolnthree> "Our server decided to do something more important than service *your* needs. Please give someone else your business."
[18:05:13] *** alesj has quit IRC
[18:05:18] <jose_freitas> "the hr department is waiting you"
[18:07:09] <clerum> you could probably use the international module to localize your witty remark
[18:07:33] *** sannegrinovero has quit IRC
[18:07:34] <clerum> something funny in japan may be offensive in china
[18:07:46] <lincolnthree> Doubtful.
[18:07:56] <lincolnthree> The two languages are like black and white.
[18:08:19] <lincolnthree> However, english and spanish could actually work together quite well.
[18:08:28] <lincolnthree> "Website nova!!!!"
[18:09:22] <clerum> in soviet russia website times you out
[18:09:42] <lincolnthree> Now *that's* offensive in China.
[18:26:58] *** maschmid has quit IRC
[18:27:37] *** sannegrinovero has joined #seam-dev
[18:29:56] *** amitev has quit IRC
[18:31:17] *** sannegrinovero is now known as sanne
[18:38:33] *** pmuir has quit IRC
[18:39:49] *** lightguard_jp has quit IRC
[18:52:16] *** pmuir has joined #seam-dev
[19:03:55] *** emmanuel has quit IRC
[19:03:59] *** stuartdouglas has quit IRC
[19:07:38] *** marekn has joined #seam-dev
[19:13:55] <jose_freitas> clerum, are there any documentation on seam mail?
[19:15:46] *** pmuir has quit IRC
[19:18:45] <clerum> other than the java docs no
[19:18:59] <clerum> I'm waiting on someone to review the whole thing before I start writing the docs
[19:19:12] <clerum> in case there are major fundamental changes coming...
[19:19:20] <jose_freitas> hm
[19:19:41] <jose_freitas> k
[19:20:22] <jose_freitas> it seems that it's been years that you're waiting this code review
[19:20:28] <jose_freitas> hehehe
[19:20:54] <lincolnthree> clerum: remind me in the next few days = I'll go through it
[19:22:30] <clerum> will do
[19:22:43] <jbossbot> git [forge] push master 759a412.. Lincoln Baxter, III Updates to utility plugins
[19:22:43] <jbossbot> git [forge] push master 3d05b48.. Lincoln Baxter, III constrant enforcer should no longer cause NPE when pom.xml is deleted - NPP should now correctly use the requested folder
[19:22:43] <jbossbot> git [forge] push master fec864a.. Lincoln Baxter, III corrected facet name
[19:22:43] <jbossbot> git [forge] push master 60681b0.. Lincoln Baxter, III hackish new project fix
[19:22:43] <jbossbot> git [forge] push master URL: http://github.com/seam/forge/compare/f21695f...60681b0
[19:25:06] *** cbrock has joined #seam-dev
[19:25:06] *** cbrock has quit IRC
[19:25:06] *** cbrock has joined #seam-dev
[19:32:33] <clerum> I'm not too shook about about the delay in review. I'm not at a loss for things to work on :-)
[19:34:34] <jose_freitas> hm
[19:50:38] *** marekn has quit IRC
[19:52:50] *** marekn has joined #seam-dev
[20:06:58] *** marekn has quit IRC
[20:42:01] *** stuartdouglas has joined #seam-dev
[20:45:27] *** bitshuffler has joined #seam-dev
[20:59:04] *** sanne has quit IRC
[21:05:16] *** jose_freitas is now known as jose_freitas_afk
[21:21:22] *** cbrock has quit IRC
[21:43:37] *** rruss has joined #seam-dev
[21:56:32] *** cbrock has joined #seam-dev
[21:56:32] *** cbrock has quit IRC
[21:56:32] *** cbrock has joined #seam-dev
[21:57:41] *** adamw1pl has joined #seam-dev
[22:05:24] *** adamw1pl has quit IRC
[22:11:17] *** rpetruescu has quit IRC
[22:12:44] *** amitev has joined #seam-dev
[22:23:56] *** bitshuffler_ has joined #seam-dev
[22:27:29] *** bitshuffler has quit IRC
[22:33:02] *** rruss has quit IRC
[22:37:50] <jbossbot> git [security] push master 6b61724.. Shane Bryzak removed unrequired src dir
[22:37:50] <jbossbot> git [security] push master URL: http://github.com/seam/security/compare/3de6024...6b61724
[22:40:05] *** amitev has quit IRC
[22:40:22] *** lightguard_jp has joined #seam-dev
[22:51:00] <jbossbot> git [forge] push master cdf647c.. Lincoln Baxter, III Updated and consolidated Forge events, fixed NewProjectPlugin directory target, added TAB-completion for properties/SetPlugin
[22:51:00] <jbossbot> git [forge] push master URL: http://github.com/seam/forge/compare/60681b0...cdf647c
[22:55:09] *** amitev has joined #seam-dev
[22:59:12] *** bitshuffler__ has joined #seam-dev
[23:00:23] *** jose_freitas has joined #seam-dev
[23:02:28] <lightguard_jp> Did we say the meeting was at 2300 or 2200 UTC?
[23:02:41] *** bitshuffler_ has quit IRC
[23:04:57] <jose_freitas> I believe last time were at 22 UTC
[23:05:01] <sbryzak> lightguard_jp: this is the right time i think
[23:05:15] <sbryzak> just waiting for MC Dan
[23:05:45] <jose_freitas> Mc dan olds
[23:05:53] <lightguard_jp> Okay, gotta update my gCal then
[23:06:28] *** lincolnthree has quit IRC
[23:07:32] *** mojavelinux has joined #seam-dev
[23:08:06] <mojavelinux> hey everyone
[23:08:10] <lightguard_jp> Hey Dan
[23:08:12] <sbryzak> hey dan!
[23:08:37] <jose_freitas> hello =)
[23:08:42] <mojavelinux> oh my goodness, I feel like all I've been doing lately is chasing down compliance bugs :/
[23:08:54] <lightguard_jp> GF 3.1?
[23:10:39] <mojavelinux> what else? hehe
[23:10:45] <lightguard_jp> Of course
[23:10:58] <lightguard_jp> Do we have a feel for Siva being able to fix these?
[23:11:06] <mojavelinux> last night I uncovered one that doesn't even have to do with Seam at all
[23:11:22] <lightguard_jp> Sounds like a repeat of jee booking
[23:11:24] <mojavelinux> purely a problem with EJBs and CDI
[23:12:18] <amitev> guys, what do you think about foreground and background conversation functionality in seam3?
[23:13:49] <mojavelinux> you mean like workspaces?
[23:14:08] <amitev> yes
[23:14:29] <amitev> and the most important thing - the background conversation timeouts with the session
[23:14:30] <mojavelinux> I think we need it, the limitation so far has been that the conversation scope in CDI is basically impossible to extend
[23:14:33] <mojavelinux> yep
[23:14:52] <mojavelinux> I believe that an abandoned conversation does timeout with the session already
[23:15:10] <mojavelinux> the problem with workspaces is that there is no way to interact with the conversation store in a portable way
[23:15:25] <lightguard_jp> You could probably create your own impl, but you'd have a lot of work hooking it all up, I think
[23:15:38] <mojavelinux> yep, not too much work if we add the bean store to Solder
[23:16:02] <mojavelinux> what should really happen is that the generic bean store functionality in Weld should be split out into a library
[23:16:05] <mojavelinux> that Solder can use
[23:16:08] <mojavelinux> generic classes
[23:16:17] <mojavelinux> any seam module for that matter
[23:16:47] <mojavelinux> gotta move on to agenda
[23:16:54] <lightguard_jp> Right, is http://www.seamframework.org/Seam3/ProjectMeetings up to date?
[23:16:57] <lightguard_jp> For the agenda?
[23:17:06] <mojavelinux> yep
[23:17:11] <mojavelinux> updated it a short while ago
[23:17:17] <mojavelinux> item #1, asl license
[23:17:26] <mojavelinux> if you module is not yet on the ASL license, please create a JIRA
[23:17:38] <lightguard_jp> We need to update the parent I think
[23:17:42] <lightguard_jp> Or maybe it was solder
[23:17:44] <mojavelinux> and commence with the updated...we'd like to make this by Beta2
[23:17:46] *** cbrock has quit IRC
[23:17:50] <lightguard_jp> One of them says LGPL
[23:17:56] <mojavelinux> it's the parent
[23:18:06] <mojavelinux> I can only update the parent once all modules switch (in other parts)
[23:18:23] <mojavelinux> meaning, source headers and the license.txt file in assembly
[23:18:34] *** cbrock has joined #seam-dev
[23:18:35] *** cbrock has quit IRC
[23:18:35] *** cbrock has joined #seam-dev
[23:18:36] <mojavelinux> then we'll switch the parent over
[23:19:08] <sbryzak> i'll go through the modules today and make a list
[23:19:25] <mojavelinux> modules needing JIRAs are faces, persistence, security, config
[23:19:38] <mojavelinux> rest, international
[23:19:45] <mojavelinux> remoting
[23:19:51] <sbryzak> remoting is done
[23:19:59] <mojavelinux> ah, :)
[23:20:12] <mojavelinux> oh, I forgot to git pull
[23:20:23] <lightguard_jp> Hm, Brian isn't here is he?
[23:21:19] <sbryzak> i'll take care of the asl license switchover
[23:21:23] <mojavelinux> great
[23:21:34] <mojavelinux> okay, #2 solder status
[23:22:02] <mojavelinux> my concern here is that we didn't do any sort of state of the union w/ glassfish announcement
[23:22:29] <mojavelinux> would someone like to volunteer to explain the situation (we've discussed it many times here); the less clear we are in this area, the more time we spend explaining this over and over
[23:22:40] <mojavelinux> ^ as in we need a blog entry
[23:23:01] <mojavelinux> in that blog entry, we can mention that we have compat tests now in the solder test suite
[23:23:05] <mojavelinux> to demonstrate each problem
[23:24:05] <sbryzak> the last i heard was that there was possibly an issue in weld
[23:24:11] <sbryzak> WELD-846
[23:24:15] <jbossbot> jira [WELD-846] Incorrect handling of cyclic dependencies between BeanDeploymentArchives [Open, Major, Ales Justin] https://issues.jboss.org/browse/WELD-846
[23:24:38] *** ssachtleben has joined #seam-dev
[23:24:45] <mojavelinux> funny that the tests still work on jboss as though
[23:24:58] <mojavelinux> perhaps the integration somehow "fixes" the problem :)
[23:25:25] <mojavelinux> and that's not the only issue
[23:25:30] <mojavelinux> afaik
[23:25:36] <mojavelinux> but that compat tests tell the story
[23:25:44] <stuartdouglas> jboss implements the spec wrong :-)
[23:25:52] <mojavelinux> ahhhhhh, now the truth comes out :)
[23:26:06] <stuartdouglas> it treats wars as one big BDA
[23:26:06] <jose_freitas> hehehe
[23:26:14] <stuartdouglas> which is fine for a BDA visibility pov
[23:26:29] <stuartdouglas> but wrong in terms or enabled interceptors/decorators + ordering
[23:26:50] <stuartdouglas> as technically the jars in web-inf/lib can have different interceptors etc
[23:27:22] <lightguard_jp> Is Glassfish actually doing it correctly?
[23:27:37] <mojavelinux> yeah, the compat test should probably show jboss doing it wrong then
[23:27:54] <mojavelinux> basically, the compat tests are the assumptions by which we impl solder
[23:28:06] <mojavelinux> otherwise, we are floating around in quirky land
[23:28:22] <stuartdouglas> yes, BF create a BDA per jar
[23:28:28] <stuartdouglas> GF^
[23:29:31] <mojavelinux> right, I saw that when looking at the extension in non-BDA patch
[23:29:43] <mojavelinux> personally, I think that makes developing a PITA
[23:29:49] *** tsurdilo2 has joined #seam-dev
[23:29:50] <lightguard_jp> No kidding
[23:29:54] <mojavelinux> but, so it is
[23:30:16] <mojavelinux> strange how all of a sudden the non-modularity of EE likes to get all strict on us
[23:30:17] <lightguard_jp> Solder then was created under this false assumption of how the spec should be implemented?
[23:30:47] <jose_freitas> O.O
[23:30:54] <stuartdouglas> no, but there is a bug in weld where the BDA visibilty graph is not created correctly
[23:31:01] <stuartdouglas> if you do implement the spec properly
[23:31:40] <lightguard_jp> Ouch
[23:31:51] <lightguard_jp> Wish we caught that before 1.1.0.Final went out
[23:31:54] <mojavelinux> ah, so I see how this is a problem in Weld
[23:32:03] <mojavelinux> because if you impl the BDA correctly, then Weld gets confused
[23:32:11] <mojavelinux> and so we are sort of in no-mans-land
[23:33:00] <sbryzak> is ales aware of these issues?
[23:33:02] <mojavelinux> this is why it's sooooooooooooooooooooo important to test everything on at least two app servers always
[23:33:10] <mojavelinux> never test on jboss as and assume your work is done
[23:33:15] <mojavelinux> now, 2 isn't a magic number
[23:33:19] <stuartdouglas> We discussed it on wednesday
[23:33:21] <mojavelinux> 4 would be better, but 1 is just not enough
[23:33:32] <lightguard_jp> I'd like to see compat tests done with another CDI impl
[23:33:37] <lightguard_jp> Like OWB or CanDI
[23:33:42] *** tsurdilo1 has quit IRC
[23:33:48] <lightguard_jp> All would be best, but at least one of them
[23:33:49] <mojavelinux> that's why glassfish is so important to us (not just because we like freedom)
[23:33:52] <stuartdouglas> we should be keeping track of these thinks for the next TCK
[23:34:15] <mojavelinux> which is why we want opentck, but of course we aren't "allowed" to do that
[23:34:17] <mojavelinux> grrrrr
[23:34:24] <jose_freitas> why not?
[23:34:29] <mojavelinux> politics
[23:34:43] <lightguard_jp> I can commit :)
[23:34:50] <jose_freitas> who politics?
[23:34:54] <mojavelinux> I suppose you could say that we could encourage people to write tests for the cdi tck, but arquillian is just so much more familiar and flexible
[23:35:01] <stuartdouglas> afaik I we can still add tests to the trunk of the TCK
[23:35:09] <stuartdouglas> they are just not part of the 'official' TCK
[23:35:20] <stuartdouglas> but that way they will make it into the next one
[23:35:24] <mojavelinux> right, but different framework, that's why the compat tests in arquillian
[23:35:26] <mojavelinux> sorry
[23:35:28] <mojavelinux> in solder
[23:35:37] <mojavelinux> are basically proposals for the next tck
[23:35:57] <mojavelinux> I'm just putting them somewhere I am allowed to commit using arquillian
[23:36:01] <mojavelinux> "allowed" to commit
[23:36:39] <mojavelinux> someone could...say, take those tests
[23:36:42] <mojavelinux> and move them to the opentck :)
[23:37:16] <mojavelinux> as for the other point I wanted to make about solder
[23:37:23] <mojavelinux> I think the servicehandler change is very high priority
[23:37:24] <mojavelinux> simply put
[23:37:34] <mojavelinux> make servicehandler like interceptors in how they are configured/wired
[23:37:38] <lightguard_jp> Was that the change that's in Beta3?
[23:37:50] <lightguard_jp> Oh, this is something else then
[23:38:04] <mojavelinux> servicehandler binding annotation
[23:38:56] <mojavelinux> lots of things depend or can happen when servicehandler is completed
[23:39:02] <stuartdouglas> how does that work if you have two bindings to the same service handler annotation
[23:42:04] <mojavelinux> my brain is being slow, can't draw up an example scenario for that
[23:42:35] <stuartdouglas> Well with interceptors both interceptors will run
[23:42:40] <mojavelinux> but regardless, the design doesn't have to mimic interceptors exactly if we need more flexibility, just that we use that concept
[23:42:40] <lightguard_jp> mojavelinux: Purge the cache, reboot needed :P
[23:42:45] <stuartdouglas> but in the order definied in beans.xml
[23:42:51] <mojavelinux> ah, duh
[23:43:07] <mojavelinux> yes, pete said that we need to use beans.xml (or seam config) to define the order
[23:43:09] <mojavelinux> same way
[23:43:19] <stuartdouglas> ah
[23:43:36] <lightguard_jp> Eh
[23:43:38] <stuartdouglas> That reminds me of CDI issue
[23:43:51] <mojavelinux> yeah...btw, having to enable interceptors in beans.xml
[23:43:58] <mojavelinux> made me lose 2 hours last night
[23:43:59] <lightguard_jp> Just for the record, I'm not a fan of having to enable all the stuff in beans.xml
[23:44:00] <mojavelinux> grrrrr
[23:44:45] <mojavelinux> the main reason for that is a weakness of the brain (not just my brain)
[23:44:52] <mojavelinux> that makes us believe in magic tricks
[23:45:05] <mojavelinux> I was changing EJB interceptor annotations into CDI interceptor annotations
[23:45:09] <mojavelinux> interceptor was working
[23:45:12] <mojavelinux> then all of a sudden, it wasn't
[23:45:26] <mojavelinux> I checked my annotations dozens of times...make sure it was all right
[23:45:30] <mojavelinux> forgot about beans.xml
[23:45:32] <stuartdouglas> https://issues.jboss.org/browse/CDI-105
[23:45:34] <jbossbot> jira [CDI-105] Provide a means for portable extensions to access beans.xml files [Open, Major, Unassigned] https://issues.jboss.org/browse/CDI-105
[23:45:39] <mojavelinux> but the reason I forgot was that by default they are enabled in EJB
[23:45:41] <mojavelinux> but not in CDI
[23:45:43] <mojavelinux> same interceptor
[23:45:48] <mojavelinux> same application
[23:45:51] <mojavelinux> different rules
[23:45:53] <mojavelinux> slight of hand
[23:46:08] <mojavelinux> Weld could *at least* tell me I have interceptors which are not enabled
[23:46:20] <mojavelinux> that would be a nice feature to have at the very least
[23:46:28] <stuartdouglas> with CDI-105 you write a portable extensions to do it
[23:46:28] <jbossbot> jira [CDI-105] Provide a means for portable extensions to access beans.xml files [Open, Major, Unassigned] https://issues.jboss.org/browse/CDI-105
[23:46:30] *** bitshuffler has joined #seam-dev
[23:46:59] <mojavelinux> yes, that is a critical improvement...though a little heads up would be nice too
[23:47:24] <mojavelinux> I think I'll add a feature request for that message (we could do it in Solder if rejected from Weld)
[23:47:32] <mojavelinux> though it's really a universal CDI thing
[23:48:04] <mojavelinux> how many heads will bang against a desk over why an interceptor isn't running
[23:48:18] <mojavelinux> moving on
[23:48:21] <lightguard_jp> Many, many.
[23:48:23] <mojavelinux> messages API
[23:48:24] <lightguard_jp> hehe
[23:48:37] <lightguard_jp> That's been a big issue on the forum
[23:48:50] <mojavelinux> this is a critical API in Seam
[23:49:03] <mojavelinux> the reason we aren't fixing the current functionality
[23:49:08] <lightguard_jp> We may want to put a stickie or something out there for it (for beta1, or just wait for beta2 which is in a week?)
[23:49:09] <mojavelinux> is because we want to completed change it anyway
[23:49:24] <mojavelinux> I really don't want to promote what is there currently
[23:49:28] <lightguard_jp> Probably still not a bad idea to let people know it'll change
[23:49:30] <mojavelinux> we want SEAMINTL-7
[23:49:31] <jbossbot> jira [SEAMINTL-7] Rewrite Messages API along the lines of JBoss Logging 3 [Open, Major, Ken Finnigan] https://issues.jboss.org/browse/SEAMINTL-7
[23:50:03] <mojavelinux> of course, that's really not a great title for that issue...who cares about jboss logging 3...it should say "rewrite messages API to leverage type-safety"
[23:50:06] *** bitshuffler__ has quit IRC
[23:50:17] <mojavelinux> adding status messages in JSF is horrible
[23:50:23] <mojavelinux> we want to make that a better experience
[23:50:46] <mojavelinux> w/o tying you to the JSF API (so the same can be used for Wicket, etc)
[23:50:58] <mojavelinux> and which is not a cumbersome API
[23:51:18] *** amitev has quit IRC
[23:51:49] <mojavelinux> I don't want it to make a mountain out of a molehill, but we do want this to be right, so we should be looking at it with a critical eye
[23:52:59] <mojavelinux> ken is driving this, though we need others to review and test
[23:53:00] <sbryzak> mojavelinux: what's the current issue with implementing it?
[23:53:06] <sbryzak> is it that the design isn't final?
[23:53:35] <mojavelinux> I think we are happy with the design in the JIRA
[23:53:54] <mojavelinux> but then the jboss logging thing got dropped in the middle of it
[23:54:06] <mojavelinux> like an atomic bomb
[23:54:28] <jose_freitas> why is it important to use jboss logging?
[23:54:57] <mojavelinux> it's not, really, which is why we've separated from it in part
[23:55:04] <mojavelinux> we are using it for the abstraction over logging frameworks
[23:55:11] <mojavelinux> but that's an impl detail mostly
[23:55:29] <jose_freitas> ok, the weld-logger use jboss logging as well?
[23:55:50] <mojavelinux> part of the hold-up sbryzak is that I've got messages from Ken where he is waiting on a reply
[23:55:56] <mojavelinux> this really needs to be diverted to seam-dev
[23:56:03] <mojavelinux> so that we can get answers from the team
[23:56:17] <sbryzak> ok, can we take a look at this today
[23:56:49] <mojavelinux> I'll collect up what I've got and forward you a summary...this is definitely something where we've got a blocked drain pipe
[23:57:12] <sbryzak> understood, we have to unblock it soon though
[23:57:15] <jose_freitas> mojavelinux, I might get some time to help you with this
[23:57:28] <jose_freitas> if you guys want to
[23:57:35] <mojavelinux> awesome...I really do believe it looks like a bigger issue than it really is
[23:58:15] <jose_freitas> nice
[23:58:27] <mojavelinux> jose_freitas that would be great since this is a core highlight of seam booking
[23:58:35] <mojavelinux> speaking of which, next item, examples
[23:58:43] <mojavelinux> *we* *need* *examples*
[23:58:51] <mojavelinux> the community is like "Seam what?"
[23:59:10] <jose_freitas> well, the booking example is working, it has 3 issues though
[23:59:14] <mojavelinux> yeah!
[23:59:21] <mojavelinux> I bet messages is one of them
[23:59:24] <jose_freitas> yes
[23:59:29] <sbryzak> i'd like to expand on this a bit.. we need *non JSF* examples
[23:59:31] <jose_freitas> I post it on forum today
[23:59:43] <mojavelinux> sbryzak: glad you brought that up...I"ve been studying up on wicket lately





top