[00:09:51] <jbossbot> git [security] push master d4776ea.. Shane Bryzak slight refactor, fix openid-op example, fix open-id-rp login form
[00:09:51] <jbossbot> git [security] push master URL: http://github.com/seam/security/compare/655aba4...d4776ea
[00:20:58] *** gastaldi has joined #seam-dev
[00:21:22] <gastaldi> Hey people !
[00:27:00] *** gastaldi has quit IRC
[00:36:49] <jbossbot> git [security] push master ca557bc.. Shane Bryzak SEAMSECURITY-38
[00:36:50] <jbossbot> jira [SEAMSECURITY-38] Remove / update license headers [Open (Unresolved) Task, Minor, Shane Bryzak] https://issues.jboss.org/browse/SEAMSECURITY-38
[00:36:50] <jbossbot> git [security] push master URL: http://github.com/seam/security/compare/d4776ea...ca557bc
[00:39:13] *** bitshuffler has joined #seam-dev
[00:39:31] <jbossbot> git [security] push master a376110.. Shane Bryzak SEAMSECURITY-38
[00:39:32] <jbossbot> jira [SEAMSECURITY-38] Remove / update license headers [Open (Unresolved) Task, Minor, Shane Bryzak] https://issues.jboss.org/browse/SEAMSECURITY-38
[00:39:32] <jbossbot> git [security] push master URL: http://github.com/seam/security/compare/ca557bc...a376110
[00:40:22] <jbossbot> git [security] push master fa048b9.. Shane Bryzak SEAMSECURITY-38
[00:40:23] <jbossbot> jira [SEAMSECURITY-38] Remove / update license headers [Open (Unresolved) Task, Minor, Shane Bryzak] https://issues.jboss.org/browse/SEAMSECURITY-38
[00:40:23] <jbossbot> git [security] push master URL: http://github.com/seam/security/compare/a376110...fa048b9
[00:49:25] <jbossbot> git [security] push master b2a0fdc.. Shane Bryzak SEAMSECURITY-24
[00:49:26] <jbossbot> jira [SEAMSECURITY-24] Manifest.mf files in jars generated from the module contain unreachable Implementation-URL [Open (Unresolved) Bug, Minor, Shane Bryzak] https://issues.jboss.org/browse/SEAMSECURITY-24
[00:49:26] <jbossbot> git [security] push master URL: http://github.com/seam/security/compare/fa048b9...b2a0fdc
[01:04:42] *** lightguard_jp has quit IRC
[01:38:22] *** gastaldi has joined #seam-dev
[01:39:59] <gastaldi> hello again folks !
[01:42:51] *** johnament has joined #seam-dev
[01:42:51] <bleathem> hello!
[01:43:16] <johnament> You've got mail!
[01:44:55] <gastaldi> me ?
[01:47:49] <johnament> Just making fun of American OnLine
[01:48:48] <gastaldi> oh ! That remembered me that crappy Tom hanks movie
[01:49:02] <gastaldi> :)
[01:49:08] <johnament> gastaldi: I'm merging in your changes now.
[01:49:13] <gastaldi> great
[01:49:17] <gastaldi> have you tested it ?
[01:49:26] <johnament> tests are running now.
[01:49:36] <johnament> i do see one issue, but it's a non-obvious one.
[01:49:52] 
[01:50:16] <gastaldi> in the annotation
[01:50:27] <johnament> I'm told the next arquillian lets us choose which tests to run under what profile
[01:51:14] <johnament> the test case exemplifies the API, if it feels weird/odd/difficult to use, we should consider that in our tests.
[01:51:18] <johnament> errr our developer
[01:51:23] <johnament> errr our development
[01:51:26] <gastaldi> What issue did you saw ?
[01:51:57] <johnament> probably similar to what you're describing.  i can't run your test in -Pmodeshape
[01:52:03] <gastaldi> yeah
[01:52:06] 
[01:52:08] <gastaldi> :)
[01:52:52] <gastaldi> Would be nice if no qualifier were required at all
[01:53:00] 
[01:53:20] <johnament> how would you get the default repository?
[01:53:29] 
[01:53:47] <gastaldi> passing null ?
[01:53:49] <gastaldi> To the map ?
[01:53:57] <gastaldi> What happens if you do that in modeshape ?
[01:54:09] <gastaldi> In Jackrabbit I get a TransientRepository
[01:54:45] *** daniel_hinojosa has quit IRC
[01:54:50] <gastaldi> Hey johnament, check the JavaDoc for RepositoryFactory
[01:55:30] <gastaldi> It says that the map : "@param parameters map of string key/value pairs as repository arguments or <code>null</code> if none are provided and a client wishes to connect to a default repository."
[01:55:45] 
[01:56:38] 
[01:56:57] <gastaldi> Then we can create a @Produces in another class
[01:57:10] <gastaldi> to separate configuration from injection
[01:57:19] <gastaldi> WDYT ?
[01:57:53] <johnament> modeshape returns null if the map is null.
[01:58:10] <gastaldi> hummm I guess that must be a bug in modeshape :)
[01:58:32] <johnament> http://www.day.com/maven/jsr170/javadocs/jcr-2.0/javax/jcr/RepositoryFactory.html#getRepository%28java.util.Map%29
[01:58:42] <johnament> according to the javadocs it's valid.
[01:59:28] <johnament> i'm not sure that the concept of a default repository is known to the spec.
[01:59:54] <gastaldi> Is there a default implementation in modeshape ?
[02:00:08] <gastaldi> Like a Transient Repository or something ?
[02:03:07] <johnament> modeshape works off of user defined repositories.
[02:03:28] <gastaldi> We may throw an exception if it returns null
[02:03:54] <gastaldi> That way, the user must implement a method that @Produces @JcrRepository
[02:04:23] <johnament> why would they... ?
[02:04:25] <gastaldi> thus, avoiding the qualifier when using Jackrabbit or another JCR 2.0 impl
[02:04:49] <johnament> we can treat JcrRepository as not a qualifier.
[02:05:15] <johnament> my concern though is clashes with other things that may want to produce a repository/session
[02:09:49] 
[02:09:49] <gastaldi> If you need to provide properties, just use @JcrRepository in you Repository / Session and it will do
[02:12:44] <gastaldi> also, we could check that on deploy time
[02:14:20] <gastaldi> just imagine that then, the app developer may create two qualifiers (one for using jackrabbit and another for modeshape, for example) and use them when one impl is required
[02:15:00] <johnament> I think you're putting a very large burden on the app developer
[02:15:29] <gastaldi> the annotation could be used  like its  now
[02:16:09] <johnament> why should we have extra code to support this? If we can just make JcrRepository not a qualifier, we can accomplish both cases in a single producer method
[02:16:45] <gastaldi> can you gist an example ?
[02:16:52] 
[02:17:58] <johnament> well, imagine that qualifier is removed from JcrRepository annotation
[02:18:29] <johnament> have a @Produces public Repository produceRepository(InjectionPoint ip) just like we have today
[02:18:55] <gastaldi> ok
[02:18:56] <johnament> in the body, check to see if JcrRepository is present
[02:19:06] <gastaldi> oh, like an ordinary annotation ?
[02:19:12] <johnament> yep
[02:20:15] <gastaldi> but then it would not be possible to separate configuration from injection
[02:20:32] <johnament> from the api perspective it looks the exact same
[02:20:37] <gastaldi> because every time I need an Repository, I need to use that annotation over and over again
[02:21:01] <gastaldi> What if my properties change ?
[02:21:08] <johnament> in the impl?
[02:21:17] <gastaldi> no, in my app
[02:21:39] 
[02:22:01] <gastaldi> If the repository name changes, then we have a problem
[02:22:12] <gastaldi> because the configuration is tied to the injection point
[02:22:26] <gastaldi> right ?
[02:22:30] <johnament> sort of
[02:22:45] <johnament> it's true if you over use the injection point too much refactoring becomes a nightmare
[02:23:01] <gastaldi> yeah
[02:23:18] <gastaldi> That would lead to bloated code also
[02:23:29] <gastaldi> Where people just copy/paste the @JcrConfiguration definition
[02:23:43] <johnament> however, if you annotate a qualifier w/ jcr configuration, it should automatically pick it up
[02:24:21] <johnament> http://docs.jboss.org/weld/reference/latest/en-US/html/stereotypes.html
[02:24:25] <gastaldi> I think that that would be necessary only if you had ANOTHER repository
[02:24:35] <gastaldi> If working on a single repository, why bother ?
[02:24:48] <johnament> the question really is what is more prevalent
[02:25:35] <johnament> i know from the use cases that come in to modeshape, most people are using multiple repositories
[02:26:24] <johnament> in the app i have at work today, we use 3 repos
[02:26:34] <johnament> the staging repo, published repo and audit repo
[02:26:54] <gastaldi> How do you get the Repository ? From JNDI ?
[02:27:00] <gastaldi> or by the Factory ?
[02:27:20] <gastaldi> That would be a maintenance burden if configuration is held in code
[02:27:21] <johnament> lots of ways
[02:27:29] <gastaldi> I think
[02:27:43] <johnament> you're still thinking of it being in multiple places in the code.
[02:27:52] <johnament> did you read through stereotypes?
[02:28:01] <gastaldi> Yes, I read that
[02:28:27] 
[02:28:33] <johnament> right
[02:28:39] *** rruss has quit IRC
[02:28:53] <gastaldi> I think that separating the config from the injection would be a better practice
[02:28:53] <johnament> we also shouldn't hand hold through the idea of not messing up
[02:29:18] <gastaldi> also right
[02:29:21] <johnament> i don't think you got how stereotypes work, since they do exactly that.
[02:30:12] <johnament> you define the config once, at the stereotype, and then the app developer's code only references the stereotype
[02:30:26] <johnament> app developer owns the stereotype
[02:34:15] *** daniel_hinojosa has joined #seam-dev
[02:38:33] <gastaldi> So the app developer creates stereotypes to each repository ?
[02:38:33] <gastaldi> @StagingRepo @ProductionRepo
[02:38:33] <gastaldi> and places @JcrRepository on each of them ?
[02:38:34] <gastaldi> Still not good if your configuration is not placed in code.
[02:38:34] <gastaldi> err IS placed in code
[02:38:34] <gastaldi> well, anyway, the property referenced might be a JNDI place
[02:38:34] <gastaldi> and then the configuration will not be on code anyway
[02:38:48] <jbossbot> git [jcr] push master 7a3de86.. George Gastaldi Improving javadocs
[02:38:49] <jbossbot> git [jcr] push master d919fda.. George Gastaldi SEAMJCR-1
[02:38:50] <jbossbot> jira [SEAMJCR-1] Create testcase and Jackrabbit profile [Resolved (Done) Task, Major, George Gastaldi] https://issues.jboss.org/browse/SEAMJCR-1
[02:38:50] <jbossbot> git [jcr] push master 7e852fc.. George Gastaldi SEAMJCR-1
[02:38:50] <jbossbot> git [jcr] push master 29bee2c.. George Gastaldi SEAMJCR-1
[02:38:50] <jbossbot> git [jcr] push master 0c65904.. John Ament Added first test case, including config file for modeshape.  Modified impl/pom and parent pom to properly run weld 1.0.
[02:38:51] <jbossbot> git [jcr] push master 2c4a36f.. George Gastaldi SEAMJCR-1
[02:38:51] <jbossbot> git [jcr] push master a8db410.. George Gastaldi SEAMJCR-1
[02:38:51] <jbossbot> git [jcr] push master 5be8b08.. John Ament Merge branch 'master' of https://github.com/gastaldi/jcr...
[02:38:51] <jbossbot> git [jcr] push master b849b49.. John Ament Fixed merge.
[02:38:51] <jbossbot> git [jcr] push master URL: http://github.com/seam/jcr/compare/2ef0493...b849b49
[02:40:26] <johnament> gastaldi: i don't know, maybe it's different in jackrabbit, but in modeshape all we can do is point to a config file, or assuming that the engine was started already to look up a repo in the running engine
[02:40:42] <johnament> does jackrabbit have a lot of properties?
[02:41:22] <gastaldi> Some, but usually only one is necessary
[02:41:26] <gastaldi> the home dir
[02:41:34] <gastaldi> or the JNDI name
[02:42:26] <johnament> gastaldi: http://svn.apache.org/repos/asf/jackrabbit/tags/2.2.4/jackrabbit-jcr-commons/src/main/java/org/apache/jackrabbit/commons/JndiRepositoryFactory.java
[02:42:37] <johnament> that looks to be the only implementation that I saw
[02:42:54] <gastaldi> SingletonRepositoryFactory also
[02:43:00] <gastaldi> org.apache.jackrabbit.commons.repository.SingletonRepositoryFactory
[02:44:06] <gastaldi> org.apache.jackrabbit.core.RepositoryFactoryImpl
[02:44:13] <johnament> singleton implements org.apache.jackrabbit.commons.repository.RepositoryFactory , not javax.jcr
[02:44:23] 
[02:44:28] <gastaldi> on the core module
[02:45:37] <gastaldi> that creates a TransientRepository
[02:45:56] <johnament> it looks like repository home points to where config etc are all located, right?
[02:46:01] <gastaldi> yup
[02:46:06] *** bitshuffler has quit IRC
[02:46:17] <gastaldi> normally, you would use in JNDI
[02:46:56] 
[02:49:06] <johnament> right
[02:50:41] <johnament> in modeshape, each repo gets bound to JNDI
[02:50:46] <johnament> or can be
[02:51:09] <gastaldi> nice
[02:51:12] <johnament> the repository factory works off of a JNDI location for the engine or binding initially based on config
[02:51:32] <gastaldi> could be injected with @Resource also when using JNDI
[02:51:57] <johnament> depends.
[02:52:22] <johnament> if they get bound to jndi before app deployment, it can be
[02:52:29] <gastaldi> @Inject @Resource(name="myJNDIName") Repository repo;
[02:52:41] <gastaldi> We may change the producer to watch that
[02:53:00] <johnament> what's @Resource
[02:53:00] <gastaldi> I believe so
[02:53:10] <gastaldi> javax.annotation.Resource
[02:53:17] <johnament> that won't be platform independent
[02:53:38] <gastaldi> you mean because could conflict with JEE ?
[02:53:45] <johnament> yes
[03:03:10] <gastaldi> Also, how about @Observer for JCR events ?
[03:03:29] <johnament> I created an issue for it.
[03:05:33] <gastaldi> too bad the jcr spec do not allow events to be fired before commit
[03:07:31] 
[03:16:32] <gastaldi> johnament: When do you think binding to the ObservationManager should take place ? Before creating a new session ?
[03:40:53] *** tsurdilo has quit IRC
[03:44:16] <johnament> gastaldi: what do you mean?
[03:45:18] <gastaldi> wait a sec
[03:50:58] *** johnament has quit IRC
[04:31:16] *** daniel_hinojosa has quit IRC
[04:39:18] *** daniel_hinojosa has joined #seam-dev
[04:46:10] *** lincolnthree has quit IRC
[05:08:43] *** daniel_hinojosa has quit IRC
[05:20:41] *** jganoff has quit IRC
[05:35:02] 
[05:35:40] *** gastaldi has quit IRC
[05:50:03] *** daniel_hinojosa has joined #seam-dev
[05:51:47] *** gastaldi has joined #seam-dev
[05:56:47] *** gastaldi has quit IRC
[06:49:05] *** lightguard_jp has joined #seam-dev
[07:16:50] *** oskutka has joined #seam-dev
[07:23:43] *** lukaszlenart has joined #seam-dev
[07:24:15] *** clerum has quit IRC
[07:36:26] *** lukaszlenart has left #seam-dev
[07:50:14] <lightguard_jp> sbryzak: Social page created, needs to be added to the left menu
[07:50:37] <sbryzak> lightguard_jp: cool, i'll add it
[07:51:57] <lightguard_jp> http://www.seamframework.org/Seam3/SocialModuleHome
[07:52:11] <sbryzak> done
[07:52:43] <lightguard_jp> Where do you add that? I couldn't find it
[07:53:10] <sbryzak> it's tricky.. you have to edit the Seam3 directory
[07:53:21] <lightguard_jp> Ah
[07:53:45] <lightguard_jp> Time for bed.
[07:54:01] <lightguard_jp> Catch you all at the community meeting
[07:54:23] <sbryzak> g'night :)
[07:54:30] *** lightguard_jp has quit IRC
[08:03:01] *** jharting has joined #seam-dev
[08:18:29] *** bleathem has quit IRC
[08:38:34] *** marekn has joined #seam-dev
[08:40:45] *** marekn has joined #seam-dev
[08:50:23] *** maxandersen has joined #seam-dev
[08:51:26] *** daniel_hinojosa has quit IRC
[08:53:53] *** mgencur has joined #seam-dev
[09:00:48] *** shervin_a has joined #seam-dev
[09:28:56] *** kpiwko has joined #seam-dev
[09:46:29] *** kpiwko has quit IRC
[09:47:33] *** maxandersen has quit IRC
[09:50:03] *** kpiwko has joined #seam-dev
[10:05:01] *** alesj has joined #seam-dev
[10:12:17] *** emmanuel has joined #seam-dev
[10:15:57] <jbossbot> git [persistence] push master eff6ca6.. Shane Bryzak SEAMPERSIST-25
[10:15:58] <jbossbot> jira [SEAMPERSIST-25] Misc documentation issues [Reopened (Unresolved) Bug, Minor, Shane Bryzak] https://issues.jboss.org/browse/SEAMPERSIST-25
[10:15:58] <jbossbot> git [persistence] push master URL: http://github.com/seam/persistence/compare/5832a8c...eff6ca6
[10:21:35] <jbossbot> git [servlet] push master 6ddf3fe.. Shane Bryzak SEAMSERVLET-27
[10:21:36] <jbossbot> jira [SEAMSERVLET-27] Remove jboss-logging dependency [Reopened (Unresolved) Task, Minor, Shane Bryzak] https://issues.jboss.org/browse/SEAMSERVLET-27
[10:21:36] <jbossbot> git [servlet] push master URL: http://github.com/seam/servlet/compare/0050988...6ddf3fe
[10:34:52] *** shervin_a has quit IRC
[10:35:23] *** shervin_a has joined #seam-dev
[10:36:22] *** koentsje has joined #seam-dev
[10:45:47] *** maxandersen has joined #seam-dev
[10:49:47] *** sannegrinovero has joined #seam-dev
[11:28:50] *** adamw1pl has joined #seam-dev
[11:38:23] *** jharting has quit IRC
[12:04:33] *** emmanuel has quit IRC
[12:14:57] *** maxandersen has quit IRC
[12:22:42] *** jose_freitas has joined #seam-dev
[12:26:02] *** epbernard has joined #seam-dev
[12:26:02] *** epbernard is now known as emmanuel
[12:28:27] *** emmanuel has quit IRC
[12:28:30] *** epbernard has joined #seam-dev
[12:28:30] *** epbernard is now known as emmanuel
[12:28:45] *** maschmid has joined #seam-dev
[13:01:16] *** maxandersen has joined #seam-dev
[13:19:33] *** emmanuel has quit IRC
[13:22:04] *** epbernard has joined #seam-dev
[13:22:04] *** epbernard is now known as emmanuel
[13:26:39] *** emmanuel has quit IRC
[13:43:12] *** bitshuffler has joined #seam-dev
[14:01:35] *** epbernard has joined #seam-dev
[14:01:35] *** epbernard is now known as emmanuel
[14:04:53] *** balunasj_away is now known as balunasj_mtg
[14:05:23] *** kpiwko has quit IRC
[14:24:22] <jbossbot> git [jcr] push master c92b7d8.. John Ament SEAMJCR-2 Adding support for ModeShape build profile.
[14:24:23] <jbossbot> jira [SEAMJCR-2] ModeShape test cases & integration [Open (Unresolved) Task, Major, John Ament] https://issues.jboss.org/browse/SEAMJCR-2
[14:24:23] <jbossbot> git [jcr] push master 74f0587.. John Ament SEAMJCR-2 Added session to test case.
[14:24:23] <jbossbot> git [jcr] push master e6db509.. John Ament SEAMJCR-2 Removed file.
[14:24:23] <jbossbot> git [jcr] push master 932cfaf.. John Ament SEAMJCR-2 Fixed path to look for modeshape configuration file.
[14:24:23] <jbossbot> git [jcr] push master d7e4a84.. John Ament SEAMJCR-2 Fixed header on the test case.
[14:24:24] <jbossbot> git [jcr] push master d3a4a48.. John Ament After SEAMJCR-1 and SEAMJCR-2 are complete, but Arquillian has features still to be done, changed the readme's build command to indicate how to run correctly.
[14:24:24] <jbossbot> jira [SEAMJCR-1] Create testcase and Jackrabbit profile [Closed (Done) Task, Major, George Gastaldi] https://issues.jboss.org/browse/SEAMJCR-1
[14:24:24] <jbossbot> git [jcr] push master URL: http://github.com/seam/jcr/compare/b849b49...d3a4a48
[14:35:02] *** rruss has joined #seam-dev
[14:36:35] *** rruss has quit IRC
[15:12:40] *** echelog-2` has joined #seam-dev
[15:26:18] *** lincolnthree has joined #seam-dev
[15:48:59] *** lightguard_jp has joined #seam-dev
[15:49:07] *** shervin_a has quit IRC
[15:50:38] *** tsurdilo has joined #seam-dev
[15:56:35] *** clerum has joined #seam-dev
[16:00:13] *** monkeyden has joined #seam-dev
[16:20:49] *** lincolnthree has left #seam-dev
[16:21:40] *** daniel_hinojosa has joined #seam-dev
[16:42:00] *** marekn has quit IRC
[16:48:08] *** adamw1pl has quit IRC
[16:49:17] *** maxandersen has quit IRC
[17:04:42] *** cbrock has joined #seam-dev
[17:05:33] *** bleathem has joined #seam-dev
[17:12:39] *** oskutka has quit IRC
[17:15:55] *** mgencur has quit IRC
[17:16:31] *** maxandersen has joined #seam-dev
[17:27:35] <lightguard_jp> How long are JUDCon sessions typically?
[17:30:20] <lightguard_jp> maxandersen: ^^ ?
[17:30:49] <alesj> 45min
[17:31:04] <lightguard_jp> Okay
[17:31:08] <lightguard_jp> Thanks alesj
[17:31:53] <alesj> lightguard_jp: http://www.jboss.org/events/JUDCon
[17:31:57] <alesj> actually even more
[17:31:59] <alesj> 60min
[17:32:05] <lightguard_jp> Yeah, that's what I'm looking at.
[17:32:18] <lightguard_jp> They say 45 for the presentation, then ~10 for Q&A
[17:32:22] <alesj> but as it says, 45min for presentation, 10 for qa, ...
[17:37:27] <maxandersen> lightguard_jp: 50-60 mimnutes i believe.
[17:43:02] <alesj> join #infinispan
[17:43:14] <alesj> eh, missing /
[17:43:15] <alesj> :-)
[17:47:25] *** balunasj_mtg is now known as balunasj_busy
[17:50:10] *** tsurdilo has quit IRC
[17:50:19] *** tsurdilo has joined #seam-dev
[17:52:20] <jbossbot> git [catch] push master eb850cf.. LightGuard Fixes SEAMCATCH-45...
[17:52:21] <jbossbot> jira [SEAMCATCH-45] Misc documentation issues [Reopened (Unresolved) Bug, Minor, Jason Porter] https://issues.jboss.org/browse/SEAMCATCH-45
[17:52:21] <jbossbot> git [catch] push master URL: http://github.com/seam/catch/compare/9f795e7...eb850cf
[17:53:27] *** cbrock has quit IRC
[17:56:24] *** maschmid has quit IRC
[17:57:11] *** josefreitas has joined #seam-dev
[17:58:50] *** jose_freitas has quit IRC
[18:13:52] *** daniel_hinojosa has quit IRC
[18:16:44] *** cbrock has joined #seam-dev
[18:16:44] *** cbrock has quit IRC
[18:16:44] *** cbrock has joined #seam-dev
[18:17:25] *** mgencur has joined #seam-dev
[18:17:29] *** mgencur has left #seam-dev
[18:30:56] *** alesj has left #seam-dev
[18:35:07] *** maxandersen has quit IRC
[18:38:09] *** tsurdilo has quit IRC
[18:38:09] *** monkeyden has quit IRC
[18:38:24] *** tsurdilo has joined #seam-dev
[18:38:58] *** monkeyden has joined #seam-dev
[18:47:43] *** daniel_hinojosa has joined #seam-dev
[18:54:39] *** bleathem has quit IRC
[19:05:51] *** clerum1 has joined #seam-dev
[19:07:41] *** tsurdilo1 has joined #seam-dev
[19:08:00] *** tsurdilo has quit IRC
[19:08:00] *** clerum has quit IRC
[19:08:17] *** lincolnthree has joined #seam-dev
[19:10:28] *** oskutka has joined #seam-dev
[19:16:29] *** emmanuel has quit IRC
[19:17:08] *** epbernard has joined #seam-dev
[19:17:19] *** clerum1 has quit IRC
[19:18:54] *** epbernard is now known as emmanuel
[19:19:03] *** clerum has joined #seam-dev
[19:25:55] *** balunasj_busy has quit IRC
[19:44:35] *** oskutka has quit IRC
[19:57:04] *** monkeyden has quit IRC
[19:57:04] *** msmigielski has joined #seam-dev
[19:58:07] *** lincolnthree has quit IRC
[20:09:08] *** oskutka has joined #seam-dev
[20:42:44] *** bitshuffler_ has joined #seam-dev
[20:47:15] *** bitshuffler has quit IRC
[20:57:12] *** daniel_hinojosa has quit IRC
[20:59:29] *** alesj has joined #seam-dev
[21:05:18] *** rruss has joined #seam-dev
[21:09:23] *** bitshuffler__ has joined #seam-dev
[21:10:53] *** bitshuffler_ has quit IRC
[21:21:37] *** tsurdilo1 has quit IRC
[21:23:15] *** emmanuel has quit IRC
[21:26:14] *** sannegrinovero has quit IRC
[21:36:38] <lightguard_jp> sbryzak: https://github.com/seam/build/pull/4
[21:36:41] *** tsurdilo has joined #seam-dev
[21:37:01] <lightguard_jp> Adding a readme to help describe the diffs between standard sun and JBoss Community formatting.
[21:37:51] <clerum> msmigielski: are you going to do another pull req or should I just blow those lines away and commit
[21:38:12] <msmigielski> you can blow them away
[21:38:16] <clerum> k
[21:42:44] <jbossbot> git [build] push master 9037e14.. LightGuard Adding formatting readme to define the differences
[21:42:44] <jbossbot> git [build] push master URL: http://github.com/seam/build/compare/943a860...9037e14
[22:05:34] *** rruss has quit IRC
[22:09:11] *** daniel_hinojosa has joined #seam-dev
[22:14:27] <jbossbot> git [mail] push master bf74ebb.. Cody Lerum remove unnessasary troubleshooting code
[22:14:27] <jbossbot> git [mail] push master URL: http://github.com/seam/mail/compare/a1a1086...bf74ebb
[22:24:19] *** mojavelinux has joined #seam-dev
[22:24:25] <cbrock> http://community.jboss.org/wiki/ErraiCDIIntegration
[22:45:42] *** jharting has joined #seam-dev
[22:52:49] <mojavelinux> community meeting in 10 minutes. go grab your coffee ;)
[22:53:16] <sbryzak> cbrock: here's an example of the assembly.xml we use for examples - https://github.com/seam/catch/blob/master/examples/basic-servlet/src/main/assembly/assembly.xml
[22:53:49] <sbryzak> cbrock: and the plugin is just configured in the example's pom - https://github.com/seam/catch/blob/master/examples/basic-servlet/pom.xml
[22:54:26] <cbrock> sbryzak: ok
[22:54:46] <cbrock> sbryzak: shouldn't be too much trouble...
[22:55:06] <sbryzak> cbrock: great, once it's published could you please let me know and i'll test it with the seam build
[22:56:17] *** maxandersen has joined #seam-dev
[22:56:38] <jbossbot> git [security] push master 6d20c64.. Shane Bryzak changes to idmconsole example, attribute support
[22:56:38] <jbossbot> git [security] push master URL: http://github.com/seam/security/compare/b2a0fdc...6d20c64
[22:57:08] <mojavelinux> shane and mike, we should decide which version of Errai is recommended. is it 1.1 or 1.2? let's make sure we merge the docs from the correct version
[22:57:20] <cbrock> mojavelinux: definitely 1.2.1
[22:57:55] <jbossbot> git [security] push master 2cc659a.. Shane Bryzak Merge branch 'OpenIDProviderExampleTest' of https://github.com/smigielski/security into smig-openidtest
[22:57:55] <jbossbot> git [security] push master URL: http://github.com/seam/security/compare/6d20c64...2cc659a
[22:57:57] <sbryzak> i'm wondering if it's worth bundling the errai libraries also
[22:57:59] <mojavelinux> got it, so then if there is anything in chapter 5 that is not current with 1.2.1, then can you make those updates before shane merges it into the seam 3 stack reference docs?
[22:58:22] *** sannegrinovero has joined #seam-dev
[22:58:38] <mojavelinux> by bundling, we effectively recommend that version of errai as part of Seam 3...that could help users from floating between versions when looking for support
[22:58:46] <mojavelinux> whether it be community or enterprise support
[22:58:54] <sbryzak> the reference docs will also need source artifacts published to nexus
[22:59:03] <sbryzak> as that's where the seam build pulls them from
[22:59:47] <mojavelinux> perhaps we can help mike ensure those builds are setup...use seam pom as reference where needed...since we've worked out most of this maven crap
[23:00:03] <sbryzak> certainly, that's no problem
[23:00:29] <sbryzak> i might have to leave the community meeting early, i've got an asbestos guy coming
[23:00:32] <cbrock> mojavelinux: sbryzak: yeah, right now we don't have the docbook stuff in a maven artifact... just in the sourcecode...
[23:01:18] <lightguard_jp> sbryzak: Eck, I hope you don't have any of that stuff in your house.
[23:01:25] <sbryzak> cbrock: errai is in github right?  we can probably help out with some pull requests
[23:01:35] <cbrock> sbryzak: yes
[23:01:44] <sbryzak> lightguard_jp: i do, i did some demolishing last week and found some
[23:01:55] <sbryzak> need to get the rest of the house inspected and get a quote to remove it
[23:02:27] <lightguard_jp> sbryzak: Family okay?
[23:02:28] <cbrock> sbryzak: http://github.com/errai/
[23:02:31] *** jose_freitas has joined #seam-dev
[23:02:45] *** jose_freitas is now known as jose_home
[23:03:01] <sbryzak> lightguard_jp: they weren't home (and it was kind of outside).. we stopped work immediately and put on breathing masks, then hosed down the whole area
[23:03:07] <sbryzak> cbrock: thanks, i'll take a look today
[23:03:15] <mojavelinux> yep, the key for the GWT integration page will be so that we don't have to search for those links :) that's true today, but it will be more clear once we clean it up
[23:03:35] <jose_home> evening guys
[23:03:51] <mojavelinux> good evening everyone
[23:04:00] <mojavelinux> say hi to the logs
[23:04:14] <cbrock> sbryzak: do you have the latest version of Forge on your system?
[23:04:27] <lightguard_jp> logs: Hi
[23:04:36] <sbryzak> cbrock: i have latest source code as at one week ago
[23:04:38] *** oskutka has quit IRC
[23:04:44] <clerum> here
[23:04:47] <cbrock> sbryzak: if you bootstrap it
[23:04:53] <mojavelinux> the first order of business is that i'd like to revisit the meeting time discussion, which we sort of lost track of
[23:05:01] <cbrock> sbryzak: and type: install-plugin errai
[23:05:04] <mojavelinux> basically, we were talking about moving the meeting back 1 hour and 1 day
[23:05:11] <cbrock> sbryzak: it should install the errai-cdi plugin
[23:05:25] <sbryzak> cbrock: great, thanks
[23:05:29] <cbrock> sbryzak: then just type: gen errai-cdi <example_name> <package_name>
[23:05:59] <sbryzak> cbrock: that will give me my maven-based helloworld example?
[23:06:04] <cbrock> sbryzak:  yes
[23:06:11] <mojavelinux> hopefully that should work so that we can avoid conflicts for most people, though no time will be perfect for all
[23:06:18] <sbryzak> cbrock: perfect, i'll take care of that then.. i'll add it to github.com/seam/examples
[23:06:48] <mojavelinux> i'll e-mail the list and we'll try that next week...Wed @ 21:00 UTC
[23:07:03] <sbryzak> thursday 7am for me...
[23:07:07] <mojavelinux> hehehe
[23:07:18] <mojavelinux> basically, same time as our internal meeting, day before
[23:08:08] <mojavelinux> the plan for CR2 is that shane is going to bundle forge and the booking example (thanks jose!) and release this weekend
[23:08:19] <mojavelinux> everything else stays the same, I believe
[23:08:32] <cbrock> sbryzak:  it also shows off our online plugin installation funness
[23:08:32] <jose_home> :) np
[23:08:34] <sbryzak> that's right
[23:08:43] <sbryzak> too much overhead to release new versions of everything else
[23:08:54] <sbryzak> cbrock: i'm all for funness
[23:09:22] <cbrock> sbryzak: the "gen" stuff in Forge is really a wholesale replacement for Archetype
[23:09:32] <mojavelinux> shane, you should probably see if Martin can run the booking example so that we get a thumbs up from QA
[23:10:04] <sbryzak> mojavelinux: i'll ping him today, although i'll be testing it myself also
[23:10:15] <sbryzak> would be nice to know it runs in other containers though
[23:10:55] <mojavelinux> I think it works in glassfish too, though it may require config changes for persistence. jose, have you run it on glassfish?
[23:12:43] <jose_home> Ive tried yesterday, but it didnt
[23:12:51] 
[23:13:11] <jose_home> the mapping of date is different, I`ll try to fix this tomorrow morning
[23:13:27] <jose_home> eclipse link does not recognize date the way hibernate does
[23:13:36] <lightguard_jp> jose_home: Using EclipseLink or Hibernate?
[23:13:41] <lightguard_jp> Okay
[23:13:56] <mojavelinux> often times Hibernate is more lenient
[23:14:05] <mojavelinux> for the examples we like to take the most strict approach
[23:14:16] <mojavelinux> so it may just need another annotation, like @Temporal
[23:14:59] 
[23:15:09] <jose_home> apparently the problem was solved in 1.2
[23:15:17] 
[23:15:25] <jose_home> bleathem was trying that too
[23:15:29] <mojavelinux> ah. if it doesn't work on glassfish, for the Seam 3 CR2 release, we should just add a note about it in the readme
[23:15:32] *** epbernard has joined #seam-dev
[23:15:32] *** epbernard is now known as emmanuel
[23:15:34] <mojavelinux> so that people are aware of it
[23:15:55] <lightguard_jp> I think it needs an update to weld in glassfish
[23:15:59] <lightguard_jp> which is really easy to do
[23:16:07] <lightguard_jp> Brian blogged about it
[23:16:14] <jose_home> yes, but the snapshot version does not work in glassfish
[23:16:16] <mojavelinux> link for shane?
[23:16:27] <jose_home> yes, he was trying that with me
[23:16:57] <mojavelinux> this is likely what the weld maintenance release thread is about
[23:17:27] <jose_home> here is the bleathem blog link http://blog.bleathem.ca/2011/02/updating-weld-in-glassfish-31.html
[23:17:31] <mojavelinux> excellent
[23:17:49] <sbryzak> it may be worth putting that into the seam reference documentation
[23:18:02] *** bleathem has joined #seam-dev
[23:18:24] <jose_home> bleathem: hey
[23:18:26] <mojavelinux> yes, are there top-level chapters?
[23:18:29] <cbrock> sbryzak: can you afford the weekend to let me try and improve these docs?
[23:18:30] <jose_home> I was talking about you
[23:18:33] <bleathem> jose_home hey
[23:18:33] <mojavelinux> where stuff like that can go?
[23:18:36] <cbrock> sbryzak: I think I can improve them greatly
[23:18:41] <bleathem> that's why my ears were burning
[23:18:52] <jose_home> hehe
[23:18:57] <sbryzak> cbrock: sure, they don't have to be ready until the final release
[23:19:09] <jose_home> did you manage to get weld snapshot to work in glassfish?
[23:19:09] <mojavelinux> no, tell him monday :)
[23:19:17] <mojavelinux> hahaha
[23:19:43] <bleathem> jose_home: only jsut got back to it...
[23:19:55] <bleathem> jose_home you?
[23:19:59] <bleathem> jose_homeany luck?
[23:20:08] <jose_home> nope
[23:20:11] <mojavelinux> a few admin things as we head to Seam 3 final
[23:20:31] <mojavelinux> jason has pushed the jboss community code formatting profiles into the build project
[23:20:35] <mojavelinux> one for eclipse, one for intellij
[23:20:38] *** daniel_hinojosa has quit IRC
[23:20:48] *** gastaldi has joined #seam-dev
[23:21:01] <gastaldi> hey folks !
[23:21:13] <lightguard_jp> If someone wants to export one for Netbeans we can add that too.
[23:21:16] <gastaldi> sbryzak: I created a JIRA for you
[23:21:22] <mojavelinux> please start using that, and if you can apply it to your module
[23:21:27] <lightguard_jp> The readme says what's different between Sun standards and JBoss Community.
[23:21:35] <mojavelinux> also, as shane mentioned, if you are a module lead, please update your docs to use qualified ids
[23:21:49] <mojavelinux> yes, let's print that here for reference:
[23:21:59] <sbryzak> gastaldi: we'll get the page created shortly
[23:22:05] <jose_home> hi gastaldi
[23:22:09] <gastaldi> sbryzak: Thanks !
[23:22:12] <mojavelinux> *  JavaDoc parameter information is on the same line, not indented
[23:22:12] <mojavelinux> *  Line length is 128 characters
[23:22:12] <mojavelinux> *  Spaces are used instead of tabs
[23:22:12] <mojavelinux> *  Switch blocks are indented
[23:22:12] <mojavelinux> *  Indentation size is 4
[23:22:12] <gastaldi> hello !
[23:22:13] <lightguard_jp> *  JavaDoc parameter information is on the same line, not indented
[23:22:13] <lightguard_jp> *  Line length is 128 characters
[23:22:13] <lightguard_jp> *  Spaces are used instead of tabs
[23:22:13] <lightguard_jp> *  Switch blocks are indented
[23:22:13] <lightguard_jp> *  Indentation size is 4
[23:22:16] <mojavelinux> hahhaa
[23:22:17] <lightguard_jp> haha
[23:22:23] <lightguard_jp> Too slow again
[23:22:27] <mojavelinux> well, there you go, now we are all square
[23:22:28] <lightguard_jp> mojavelinux: I just can't keep up with you
[23:22:32] <bleathem> lightguard_jp I'll see if I can do a Netbeans one
[23:22:38] <mojavelinux> oh, great!
[23:22:40] <lightguard_jp> bleathem: Perfect
[23:22:45] 
[23:22:46] <mojavelinux> it's pretty easy rules, which is why we are choosing them
[23:23:01] <cbrock> sbryzak: i can't wait for this guy to get hired
[23:23:09] *** bitshuffler__ has quit IRC
[23:23:11] <cbrock> sbryzak: i want to jump off a building
[23:23:15] <cbrock> sbryzak: =)
[23:23:15] <jose_home> fine, thanks. you?
[23:23:22] <gastaldi> Fine too
[23:23:33] <mojavelinux> don't talk to shane about buidlings, you may give him an idea
[23:23:40] <mojavelinux> though he may throw maven off one before himself
[23:23:41] <jose_home> hehehe
[23:23:52] <sbryzak> don't say the m word
[23:23:56] <lightguard_jp> That way maven will break the fall and we'll still have a leader
[23:23:59] <gastaldi> lol
[23:24:02] <mojavelinux> hahaha
[23:24:06] <jose_home> lol
[23:24:08] <sbryzak> please refer to it as the build system that must not be named
[23:24:13] <lightguard_jp> :)
[23:24:16] <gastaldi> unholy named
[23:24:17] 
[23:24:19] <mojavelinux> the build system that keeps me up at night
[23:24:23] <lightguard_jp> Long live better build systems
[23:25:19] <mojavelinux> gastaldi: we'll be creating a module page for jcr tonight, then turn it over to you for adding a description and goals, etc
[23:25:32] <gastaldi> ok, thanks again
[23:25:52] <lightguard_jp> gastaldi: Ah, yes. I need some info from you, we'll talk after the meeting.
[23:25:59] <mojavelinux> the module page gives your effort an identity, and hopefully attracts users and contributors
[23:26:08] <gastaldi> ok
[23:26:47] <gastaldi> lightguard_jp: Let me know what you need.
[23:26:54] <gastaldi> when possible, of course
[23:26:59] <sbryzak> i had an important point to bring up also
[23:27:03] <mojavelinux> anyone have any questions about the road to the Seam 3 release?
[23:27:06] <sbryzak> we need to get SEAMFACES-33 addressed for the final
[23:27:07] <jbossbot> jira [SEAMFACES-33] Create a solution for consolidated page-flow, transactional control, security constraints and URL-rewriting configuration [Open (Unresolved) Feature Request, Blocker, Stuart Douglas] https://issues.jboss.org/browse/SEAMFACES-33
[23:27:18] <mojavelinux> oh geez
[23:27:24] <stuartdouglas> It really need to be tested
[23:27:27] <stuartdouglas> the code is there
[23:27:31] <lightguard_jp> Yep, Shane said we'd have something.
[23:27:40] <mojavelinux> oh, good
[23:27:40] <sbryzak> if we don't have any way of securing pages, our users will not be happy
[23:27:47] <mojavelinux> yeah, not at all
[23:28:00] <jose_home> indeed
[23:28:01] <mojavelinux> sounds like we should incorporate this into booking, I know jose mentioned that it was on the roadmap
[23:28:02] <stuartdouglas> Ok, so there are two parts to what is there
[23:28:05] <sbryzak> stuartdouglas: in git?
[23:28:06] <stuartdouglas> one is ViewDataStore
[23:28:09] <stuartdouglas> yea
[23:28:20] <sbryzak> is it documented?
[23:28:26] <stuartdouglas> not so much :-)
[23:28:32] <sbryzak> ideally we need a section titled 'How to secure your pages'
[23:28:35] <stuartdouglas> I wrote it ages ago
[23:28:44] <stuartdouglas> It does not have page security stuff yet
[23:28:58] <stuartdouglas> but it does provide a means of configuring it
[23:29:11] <stuartdouglas> and it does provide the seam managed transaction stuff
[23:30:04] <sbryzak> so what needs to be done still?
[23:30:08] <stuartdouglas> give me a sec, and I will walk through how it all fits together
[23:30:08] <sbryzak> can we help with testing?
[23:30:24] <bleathem> I've been meaning to look more closely at SEAMFACEs-33 since we spoke about it last week, but I've been bogged down trying to get JSFUnit tests going for faces
[23:30:46] <jbossbot> git [mail] push master 5e30ec7.. Cody Lerum Merge branch 'master' into freekmarker
[23:30:46] <jbossbot> git [mail] push master 287fdff.. Cody Lerum initial impl of FreeMarker
[23:30:46] <jbossbot> git [mail] push master URL: http://github.com/seam/mail/compare/bf74ebb...287fdff
[23:31:08] <bleathem> I wanted to use JSFUnit to test what stuart had done
[23:31:08] <sbryzak> i'd like to make 33 a top priority for the next week
[23:31:12] *** cbrock has quit IRC
[23:31:14] <bleathem> rather than writing more sample apps
[23:31:25] <stuartdouglas> https://github.com/seam/faces/blob/master/impl/src/main/java/org/jboss/seam/faces/viewdata/ViewDataStoreImpl.java
[23:31:29] <stuartdouglas> So this is the view data store
[23:31:39] <mojavelinux> yes, that is definitely the right direction bleathem we've been cheating with testing in some areas, not good
[23:32:11] <bleathem> just can;t get the JSFUnit going with Weld 1.1 and the containers I've been trying
[23:32:14] <stuartdouglas> actually the impl is not that important https://github.com/seam/faces/blob/master/api/src/main/java/org/jboss/seam/faces/viewdata/ViewDataStore.java
[23:32:35] <stuartdouglas> basically is allows you to associate annotation based config to views
[23:32:47] <stuartdouglas> supporting wildcards and view heirachies
[23:32:57] <stuartdouglas> so you can apply a config annotation to /app/*
[23:33:06] <stuartdouglas> and then override /app/MyPage.xhtml
[23:33:18] <lightguard_jp> bleathem: JSFUnit should work in JBoss AS, maybe not with arquillian though.
[23:33:19] <sbryzak> is that configures with seam-config?
[23:33:24] <sbryzak> *configured
[23:33:44] <stuartdouglas> at the moment it uses an enum based config
[23:33:55] <stuartdouglas> however it can be configured however we like
[23:34:07] <stuartdouglas> so seam-config xml configuration would be fairly easy to do
[23:34:11] <stuartdouglas> if we figure out the syntax
[23:34:27] <stuartdouglas> At the moment it is configured via https://github.com/seam/faces/blob/master/impl/src/main/java/org/jboss/seam/faces/viewdata/ViewDataConfigurationExtension.java
[23:34:38] <bleathem> lightguard_jp yeah, I should try JBoss AS.  I've been using Arquilian though
[23:34:45] <stuartdouglas> Which looks for enums that are annotated @ViewConfig
[23:35:14] <stuartdouglas> and then each enum item is annotated with the view it corresponds to and any configuration enums
[23:35:22] <lightguard_jp> bleathem: I don't think JSFUnit is quite there yet in arquillian Alpha-4
[23:35:47] *** msmigielski has quit IRC
[23:36:37] <mojavelinux> no, JSFUnit works fine (well, assuming you are blessed with good luck), but you'll have better success if you use it with JBoss AS atm
[23:36:52] <bleathem> I'vwe been following https://github.com/arquillian/arquillian-examples
[23:36:59] <mojavelinux> reason being that arquillian alpha4 really needs servlet 3.0 features to work best
[23:37:01] <bleathem> which does Arquillian with Jetty
[23:37:06] <mojavelinux> you can spend many hours trying to get it working with jetty
[23:37:09] <bleathem> but uses Weld 1.1.Beta1
[23:37:10] <mojavelinux> trust me
[23:37:20] <mojavelinux> I can show you the hours I've lost, and it sucks
[23:37:20] <stuartdouglas> so a config example would be: http://pastie.org/1630438
[23:37:23] <gastaldi> lightguard_jp: John d. Ament is also on Seam JCR. He was nominated the leader in JIRA.
[23:37:39] <bleathem> you can add my hours to that pile, but no fruitful results
[23:37:40] <stuartdouglas> I have jetty tests in persistence
[23:37:44] <lightguard_jp> gastaldi: Right. I'll just list both of you as co-leads
[23:37:45] *** tsurdilo has quit IRC
[23:37:51] <mojavelinux> better to use JSFUnit w/ JBoss AS, then go back and get it working w/ jetty :)
[23:37:53] <gastaldi> lightguard_jp: Thanks
[23:38:09] <mojavelinux> right, but bleathem is talking about JSFUnit
[23:38:13] <stuartdouglas> ah
[23:38:19] <sbryzak> stuartdouglas: so that config can go in any bean class?
[23:38:20] <mojavelinux> w/ arquillian, which is like a whole other thing
[23:38:32] <bleathem> will do so with JBoss. Any examples I can follow off of (using JSFUnit?)
[23:38:34] <stuartdouglas> yea, the config can go anywhere
[23:38:38] <mojavelinux> this is all resolved (supposedly) in arquillian.next :)
[23:38:41] <gastaldi> When will Arquillian be upgraded to Weld 1.1 ?
[23:38:52] <mojavelinux> arquillian.next
[23:39:06] <mojavelinux> arquillian.when-aslak-gets-back-from-cuba
[23:39:10] <lightguard_jp> bleathem: Just follow the examples on the JSFUnit page, it's just drop in the jar to your project and run.
[23:39:12] <stuartdouglas> so to do security based stuff you would create a @Restrict annotation
[23:39:12] <gastaldi> :)
[23:39:15] <bleathem> How our new alien overlord torments us!
[23:39:30] <jose_home> lol
[23:39:35] <stuartdouglas> and then create a phase listener that pulls the Restrict annotation info from the ViewDataStore
[23:39:54] <sbryzak> if it's annotation-based, we would use typesafe security annotations
[23:40:24] <stuartdouglas> in a similar manner to https://github.com/seam/faces/blob/master/impl/src/main/java/org/jboss/seam/faces/transaction/TransactionPhaseListener.java
[23:41:22] <mojavelinux> it would be great if you could dump all this info into the JIRA :)
[23:41:45] <mojavelinux> bleathem: I can help you get the tests going at some point tomorrow or the weekend, I'll be writing an arquillian article anyway, so my mind will be on the subject :)
[23:41:53] <mojavelinux> before we wrap up, two important things
[23:42:03] <bleathem> mojavelinux: sounds good!
[23:42:20] 
[23:42:23] <mojavelinux> first, we are looking for volunteers for the Seam 2 bridge module...recruit interested parties :)
[23:42:34] <bleathem> will do
[23:42:42] <mojavelinux> basically, it's going to be an dependency-injection based solution
[23:42:45] <gastaldi> I wish there is a way to annotate a class and generate a instance() method calling from BeanManager, just like in Seam 2.
[23:42:52] <mojavelinux> sort of like the Seam Spring integration
[23:42:55] <bleathem> jose_home I want to get some JSFUnit template tests in Faces, so others can contribute tests more easily
[23:43:19] <bleathem> Facers stands to benefit from a lot of such tests
[23:43:21] <jose_home> nice
[23:43:31] <bleathem> Seam Facers - it's the latest module
[23:43:36] <jose_home> lol
[23:43:38] <bleathem> :P
[23:43:54] <mojavelinux> I'm going to e-mail the list and hit up the forums for volunteers, but we do need to get serious about this because a lot of potential Seam 3 users are stuck until we provide a migration path
[23:44:18] <mojavelinux> I'll be outlining a migration guide fairly soon
[23:44:21] <lightguard_jp> It's two way, right?
[23:44:29] <lightguard_jp> Or just CDI consuming Seam 2 components?
[23:44:38] <sbryzak> lightguard_jp: i think it will have to work both ways
[23:44:43] <mojavelinux> I could say it's two way, but I'm really not sure until we see what is feasible
[23:44:48] <stuartdouglas> sbryzak and I discussed a few ideas about the seam 2 bridge when we met up a few weeks ago
[23:44:48] <gastaldi> Good luck ! :)
[23:44:53] <sbryzak> i.e. injection of cdi beans into seam 2, injection of seam 2 components into cdi beans
[23:45:08] <mojavelinux> yep, okay, good
[23:45:19] <lightguard_jp> Seam 2 into CDI doesn't seem that tough, going the other way I think will take a bit.
[23:45:19] <mojavelinux> I'll put up a module page and perhaps we can get the notes up there
[23:45:25] <mojavelinux> then get them converted to JIRAs
[23:45:32] <stuartdouglas> I think we need a seam 2.5, which has JPA2 and JSF2, and is also CDI aware
[23:45:33] <bleathem> So my Weld-SNAPSHOT on glassfish idea stopped working a few days ago
[23:45:42] *** daniel_hinojosa has joined #seam-dev
[23:45:52] <mojavelinux> that's reasonable, so then we need to involve marek too
[23:46:10] <bleathem> Now I get this message:  Failed to start Bundle Id ...  [org.glassfish.web.weld-integration(Weld integration for glassfish):3.1]
[23:46:13] <lightguard_jp> Isn't part of that the goal for Seam 2.3?
[23:46:17] <bleathem> anyone know what that's about?
[23:46:20] <mojavelinux> okay, last item is that we have outstanding pull requests...module leads please either merge them or let shane or jason know if you need them to be merged
[23:47:09] <gastaldi> I have an old Pull Request on Seam 3 Cron module
[23:47:13] <gastaldi> :)
[23:47:13] <lightguard_jp> I can merge pretty much all modules, and I'll do my best to understand the code around the changes.
[23:47:17] <mojavelinux> isn't there a continuous integration for Weld snapshot into glassfish snapshot?
[23:47:21] <mojavelinux> or do they only do manual integrations?
[23:47:22] <bleathem> maybe I'll try the #glassfish channel
[23:47:28] <mojavelinux> pass on that message
[23:47:29] <mojavelinux> :)
[23:47:39] <lightguard_jp> bleathem: We need to get you the info for Siva
[23:47:56] <clerum> what is the plan for async methods?
[23:47:58] <mojavelinux> seriously, we need to get some continuous integration for this integration
[23:48:07] <mojavelinux> the plan for async methods is Seam Cron
[23:48:08] <bleathem> indeed
[23:48:15] <mojavelinux> at least, it makes the most sense to me putting it there, wdyt?
[23:48:30] <mojavelinux> it should be straightforward given it's not much different than what we did in Seam 2
[23:48:44] <mojavelinux> Seam Cron has managed bean timer support atm
[23:48:45] <clerum> well you could use async for things completely unrelated to scheduling
[23:48:47] <mojavelinux> quartz I think
[23:48:49] <lightguard_jp> Really there are two ways of doing async in Seam 3
[23:48:52] <lightguard_jp> Cron and JMS
[23:49:21] <clerum> sending an email is a very common async request from seam 2
[23:49:22] <gastaldi> A new Seam Async module ?
[23:49:24] <mojavelinux> in a sense, async method call is like Seam At :)
[23:49:27] <gastaldi> or in Solder ?
[23:49:32] <lightguard_jp> Unfortunately neither one of them are quite prime time ready yet.
[23:49:36] <clerum> I was wondering if it belongs in solder
[23:49:42] <mojavelinux> I'd like to make timing-oriented stuff part of Cron
[23:50:18] <mojavelinux> where async is like schedule now :)
[23:51:05] <mojavelinux> at in linux
[23:51:15] <mojavelinux> an async module would be overkill imho
[23:51:33] <clerum> In seam 2 I've done mail with an async event
[23:51:36] <mojavelinux> we can say Seam Cron is "scheduling an asynchronous support for managed beans"
[23:51:44] <clerum> and that worked well
[23:52:04] <mojavelinux> yep, I think at one point I had suggested adding an example like that in seam mail, so we are on the same page
[23:52:33] <mojavelinux> but of course, we need the feature first ;) we could put it in seam jms, but I can see people saying that it's too "heavyweight" to put async in there
[23:52:41] <mojavelinux> and in general solder isn't really supposed to have features
[23:52:53] <mojavelinux> more support, but then again that's sort of a blurry line
[23:53:04] <gastaldi> Solder could have the API
[23:53:11] <gastaldi> and JMS / Cron the impl
[23:53:23] <clerum> do we have an async event in cdi?
[23:53:28] <mojavelinux> nope
[23:53:43] <mojavelinux> only async event is the transaction sync...which is sort of async, but not really
[23:53:55] <mojavelinux> it was there initially, but it got pulled
[23:53:58] <mojavelinux> the async event that is
[23:54:02] <mojavelinux> because it would "compete" with jms
[23:54:22] <mojavelinux> but of course, the jms bridge wasn't included either, so it was a big fat hole
[23:54:42] 
[23:54:49] <mojavelinux> got it, that makes sense
[23:55:10] <mojavelinux> if you have an idea for how to spec that out, feel free to create a JIRA with your ideas and we can move forward on it
[23:55:30] <mojavelinux> it is critical that we get async since we had it in seam 2 and managed beans are basically up a creek if they want aync atm
[23:56:07] <daniel_hinojosa> Hello!
[23:56:17] <gastaldi> daniel_hinojosa: Hello !
[23:56:20] <mojavelinux> yo yo
[23:56:26] <mojavelinux> Mr. Scala
[23:56:35] <daniel_hinojosa> (blush)
[23:56:48] <mojavelinux> thanks for adding those notes to jira stuart
[23:56:57] <stuartdouglas> no problem
[23:56:57] <clerum> yeah async events is a big loss from seam 2
[23:57:00] *** johnament has joined #seam-dev
[23:57:05] <gastaldi> hey john !
[23:57:11] 
[23:57:34] <gastaldi> johnament: have you seen my comments on the pull request ?
[23:57:49] <stuartdouglas> Sorry I am not going to be able to help much with getting it sorted out, but we are meant to do the next release of AS7 in two weeks
[23:58:09] <stuartdouglas> so I don't have much free time
[23:58:41] <johnament> gastaldi: fine, you.  i was about to respond.
[23:59:24] <bleathem> stuartdouglas those darn day jobs!
[23:59:27] <mojavelinux> that's okay, we are excited for AS 7, so we'll make do :)
[23:59:55] <stuartdouglas> hopefully by the end of today I should have a few of the seam demo's running on it





top