[00:01:18] *** bleathem has quit IRC
[00:06:08] <jbossbot> git [catch] push master 57be36a.. Shane Bryzak SEAMCATCH-45
[00:06:12] <jbossbot> jira [SEAMCATCH-45] Misc documentation issues [Reopened (Unresolved) Bug, Minor, Shane Bryzak] https://issues.jboss.org/browse/SEAMCATCH-45
[00:06:12] <jbossbot> git [catch] push master URL: http://github.com/seam/catch/compare/c5e3625...57be36a
[00:15:43] <sbryzak> SEAMREST-40 can be done after the release
[00:15:45] <jbossbot> jira [SEAMREST-40] Migrate compatibility tests to the seam-compatibility module [Open (Unresolved) Task, Major, Jozef Hartinger] https://issues.jboss.org/browse/SEAMREST-40
[00:20:09] *** johnament has joined #seam-dev
[00:21:32] <mojavelinux> i'm doing that now
[00:21:41] <mojavelinux> almost done
[00:21:44] <mojavelinux> in fact, just testing it
[00:40:38] <Diablo-D3> hey guys
[00:40:43] <Diablo-D3> what does @Model do?
[00:41:11] *** rruss has quit IRC
[00:41:32] *** bitshuffler has joined #seam-dev
[00:41:40] <sbryzak> it's a stereotype
[00:41:52] <sbryzak> means the bean is @Named and @RequestScoped
[00:41:54] <johnament> you mean this one http://download.oracle.com/javaee/6/api/javax/enterprise/inject/Model.html
[00:41:55] <johnament> ?
[00:42:04] <johnament> doh
[00:42:34] <Diablo-D3> Im not viewing it in eclipse
[00:42:40] <Diablo-D3> eclipse I think has ruined me for coding
[00:42:51] <johnament> potentially
[00:42:56] <johnament> IDEs kind of do that
[00:43:06] <Diablo-D3> yeah but I used to hate IDEs :<
[00:44:17] <johnament> so what's the plan for final?
[00:44:32] <johnament> are we just pulling issues assigned to people since all 12 are assigned?
[00:44:36] <sbryzak> johnament: still 12 issues to go
[00:44:50] <sbryzak> well if you'd like to help out, let me know which issue you want ;)
[00:45:01] <sbryzak> some of them are already works in progress
[00:45:02] <johnament> SEAMSERVLET-22
[00:45:04] <jbossbot> jira [SEAMSERVLET-22] Test Seam Servlet in an EAR with multiple web apps [Open (Unresolved) Feature Request, Major, Dan Allen] https://issues.jboss.org/browse/SEAMSERVLET-22
[00:45:13] <sbryzak> ah, i'm sure dan would appreciate you taking that one
[00:45:19] <johnament> i figure
[00:45:32] <sbryzak> mojavelinux: ^^^
[00:45:47] <mojavelinux> dan hinojosa is checking it out
[00:46:05] <sbryzak> johnament: pick another number!
[00:46:21] <johnament> SEAM-31 ?
[00:46:28] 
[00:46:37] <sbryzak> i know that jose has finished most of that
[00:46:46] <johnament> doh
[00:46:52] <sbryzak> how about
[00:46:55] <sbryzak> SEAMREMOTING-30
[00:46:57] <jbossbot> jira [SEAMREMOTING-30] remoting-model example causes ConcurrentModificationException [Open (Unresolved) Bug, Major, Shane Bryzak] https://issues.jboss.org/browse/SEAMREMOTING-30
[00:47:01] <sbryzak> i haven't had a good chance to look at that one
[00:47:05] <johnament> that was the next one
[00:47:09] <johnament> go for it
[00:47:09] <sbryzak> it's easy to reproduce
[00:47:29] <Diablo-D3> okay, what does @Model actually _do_?
[00:47:31] <stuartdouglas> I think SEAMREMOTING-30 is a weld bug
[00:47:36] <jbossbot> jira [SEAMREMOTING-30] remoting-model example causes ConcurrentModificationException [Open (Unresolved) Bug, Major, Shane Bryzak] https://issues.jboss.org/browse/SEAMREMOTING-30
[00:47:37] <johnament> i think remoting is the only module i haven't touched yet
[00:47:41] <jbossbot> git [compatibility] push master b2656b9.. Dan Allen SEAMREST-40 move compatibility tests to compatibility module
[00:47:41] * stuartdouglas looks for jira
[00:47:42] <jbossbot> jira [SEAMREST-40] Migrate compatibility tests to the seam-compatibility module [Open (Unresolved) Task, Major, Jozef Hartinger] https://issues.jboss.org/browse/SEAMREST-40
[00:47:42] <jbossbot> git [compatibility] push master URL: http://github.com/seam/compatibility/compare/2f3aab0...b2656b9
[00:47:56] <sbryzak> i'll add you to the developer list in jira
[00:48:18] <johnament> Diablo-D3: @Named makes it available in EL.  @RequestScoped makes it available within a single HTTP Request.  @Model combines both of these together
[00:48:31] <Diablo-D3> hrrrrrrrrrrm.
[00:48:40] <sbryzak> john: assigned :)
[00:49:07] <stuartdouglas> WELD-833
[00:49:07] <johnament> sbryzak: forked
[00:49:08] <jbossbot> jira [WELD-833] ConcurrentModificationException while deactivating conversations [Coding In Progress (Unresolved) Bug, Major, Ales Justin] https://issues.jboss.org/browse/WELD-833
[00:49:23] <sbryzak> Diablo-D3: you should read the JSR-299 spec, and the weld reference docs for a good overview of cdi
[00:49:23] <stuartdouglas> You can just close it it, it is a weld issue
[00:49:41] <sbryzak> stuartdouglas: cool, thanks
[00:49:43] <Diablo-D3> sbryzak: Im still trying to figure out what parts of the openid rp example I need =P
[00:49:56] <sbryzak> johnament: you're the quickest bug fixer i've ever seen
[00:49:57] <Diablo-D3> it doesnt look like I need Configure.java, but maybe I do
[00:50:01] <johnament> lol
[00:50:07] <sbryzak> assigned one minute, resolved the next
[00:50:17] <johnament> sbryzak: it's probably more applicable to make it a dependency on the weld bug
[00:50:18] <sbryzak> Diablo-D3: for openid?
[00:50:37] <sbryzak> johnament: you can close it, and just put a reference to the weld issue
[00:50:53] <Diablo-D3> sbryzak: yeah, it still gives me null pointer exception when I press login
[00:51:10] <Diablo-D3> only one file seems to reference configure, and thats configure.xhtml
[00:51:25] <mojavelinux> 11 issues
[00:51:27] <sbryzak> Diablo-D3: pastebin the exception and we can take a look
[00:51:33] <johnament> duplicate?
[00:51:34] <mojavelinux> let's get under 10!
[00:52:09] <Diablo-D3> http://pastebin.com/WyKyhpf5
[00:52:12] <sbryzak> mark it as won't fix
[00:52:23] <Diablo-D3> btw https://issues.jboss.org/browse/SEAMSECURITY-48
[00:52:25] <jbossbot> jira [SEAMSECURITY-48] mvn dep scope wrong with seam-security-external + seam-bom [Open (Unresolved) Bug, Major, Unassigned] https://issues.jboss.org/browse/SEAMSECURITY-48
[00:52:32] <Diablo-D3> that should be fixed before 3.0.0 final
[00:53:10] <sbryzak> Diablo-D3: are you using CR3?
[00:53:11] <johnament> 10
[00:53:18] <Diablo-D3> sbryzak: of what?
[00:53:23] <sbryzak> in your app
[00:53:32] <Diablo-D3> no, cr3 of what
[00:53:42] <johnament> mojavelinux: do you know whats going on w/ SEAMREST-39 ?
[00:53:46] <jbossbot> jira [SEAMREST-39] Remove slf4j references [Reopened (Unresolved) Task, Major, Jozef Hartinger] https://issues.jboss.org/browse/SEAMREST-39
[00:53:47] <sbryzak> cr3 of seam-security
[00:53:49] <mojavelinux> checking it out now
[00:54:07] <Diablo-D3> sbryzak: I think so
[00:54:10] <johnament> cuz i didn't see any more slf4j references in solder/catch
[00:54:26] <johnament> SEAMSECURITY-46 ?
[00:54:28] <jbossbot> jira [SEAMSECURITY-46] security examples - provide build profile for GlassFish [Open (Unresolved) Task, Major, Martin Gencur] https://issues.jboss.org/browse/SEAMSECURITY-46
[00:54:29] <mojavelinux> it's okay to have slf4j-simple in a test scope
[00:54:34] <mojavelinux> because some other libraries depend on it
[00:54:39] <Diablo-D3> sbryzak: its whatever cr9 of seam-bom has
[00:54:41] <mojavelinux> what's important is that we not export it in seam
[00:54:46] <sbryzak> damn, i don't have the CR3 bundled release any more
[00:55:22] <sbryzak> Diablo-D3: ah, are you using identity management?
[00:55:34] <johnament> i need coffee. brb
[00:56:09] <Diablo-D3> sbryzak: er... possibly?
[00:56:28] <Diablo-D3> sbryzak: confusing this is.
[00:56:31] <sbryzak> Diablo-D3: ok, i'm guessing not.. in that case, the exception indicates that you don't have an authenticator
[00:56:45] <sbryzak> you need to create a bean that implements the Authenticator interface
[00:56:48] *** balunasj_mtg has quit IRC
[00:57:15] <sbryzak> it needs to look something like this: https://github.com/seam/security/blob/master/examples/simple/src/main/java/org/jboss/seam/security/examples/simple/SimpleAuthenticator.java
[00:57:28] <Diablo-D3> sbryzak: Im trying to add openid
[00:57:34] <sbryzak> oh
[00:57:48] <sbryzak> in that case, you need to configure the Identity bean
[00:57:56] <sbryzak> to let it know you want to use the openid authenticator
[00:58:03] <Diablo-D3> my seam-beans.xml and beans.xml match whats in the openid-rp example
[00:58:27] <sbryzak> that's not good enough, the openid-rp example configures the authenticator from the web page
[00:58:40] <sbryzak> so if you're not doing that, you need to configure it in seam-beans.xml instead
[00:58:57] <Diablo-D3> my login.xhtml looks like the example
[00:59:04] <sbryzak> can you pastebin it?
[00:59:17] <mojavelinux> seam tasks looks cool
[00:59:19] <mojavelinux> I like it :)
[00:59:32] *** aslak has quit IRC
[00:59:33] <sbryzak> mojavelinux: what's that?
[00:59:38] <Diablo-D3> http://pastebin.com/C9mLjZKD
[00:59:41] <mojavelinux> example for the rest example
[00:59:43] <mojavelinux> rest module
[00:59:50] <sbryzak> ah, i haven't had a chance to look yet
[01:00:05] <sbryzak> too busy trying to stop the boat from sinking ;)
[01:00:12] <sbryzak> i look forward to playing with seam though after the release is out
[01:00:18] <Diablo-D3> sbryzak: when I access it, it lists the openid sites I can choose from
[01:00:20] <johnament> i want to pitch another multi-module example.  jitter.  JMS + JCR + Social + Security + REST + Persistence
[01:00:27] <Diablo-D3> sbryzak: it null exceptions when I press login
[01:00:34] <sbryzak> Diablo-D3: your login form doesn't set the authenticator name
[01:00:50] <sbryzak> if you only want to use openid in your app, it's best to configure it in xml
[01:01:01] <sbryzak> one sec and i'll show you what you need to add
[01:01:10] <Diablo-D3>   <security:IdentityImpl>
[01:01:10] <Diablo-D3>     <s:modifies/>
[01:01:10] <Diablo-D3>     <security:authenticatorName>openIdAuthenticator</security:authenticatorName>
[01:01:10] <Diablo-D3>   </security:IdentityImpl>
[01:01:14] <Diablo-D3> thats whats in my seam-beans.xml
[01:01:43] <sbryzak> Diablo-D3: actually, it is configured in xml in the openid-rp example
[01:01:46] <Diablo-D3> and I notice that uses seam config :D :D :D
[01:01:58] <sbryzak> yeah, that's the snippet you need
[01:02:18] <sbryzak> how are you packaging that?
[01:02:27] <Diablo-D3> how?
[01:02:32] <sbryzak> as a war file?
[01:02:35] <Diablo-D3> yeah
[01:02:43] <sbryzak> and where is the seam-beans.xml located?
[01:02:50] <Diablo-D3> in WEB-INF
[01:03:25] <sbryzak> i think it needs to go in WEB-INF/classes/META-INF
[01:03:29] <sbryzak> stuartdouglas: can you pls confirm?
[01:03:34] <Diablo-D3> well, its in the same dir as beans.xml
[01:03:43] <stuartdouglas> yes, it needs to be on the CP
[01:03:53] <stuartdouglas> so W-I/classes/M-I
[01:04:09] <sbryzak> Diablo-D3: so you need to move it, WEB-INF isn't on the classpath
[01:04:09] <Diablo-D3> sbryzak: in mvn's war target, where does it put src/resources/META-INF?
[01:04:23] <sbryzak> into WEB-INF/classes/META-INF
[01:04:26] <Diablo-D3> derp.
[01:04:27] <johnament> src/main/resources/META-INF
[01:04:43] *** bitshuffler_ has joined #seam-dev
[01:04:51] <Diablo-D3> anything else needs to be put there?
[01:05:09] <sbryzak> not for the config to work
[01:05:11] <Diablo-D3> I have beans.xml web.xml pretty-config.xml faces-config.xml in WEB-INF
[01:05:20] <johnament> seam-beans.xml is a bit special
[01:05:25] <sbryzak> you still require the beans.xml in your WEB-INF
[01:05:38] <johnament> should we maybe document that requirement (is it already in seam-config-xml ?)
[01:05:39] <sbryzak> otherwise your deployment won't be recognised as a bean archive
[01:05:53] <sbryzak> johnament: i'm sure it's already documented
[01:06:10] <johnament> i figured, i know it's been a bit of an issue
[01:06:33] <jbossbot> git [rest] push master 418f820.. Dan Allen SEAMREST-39 remove remaining slf4j references
[01:06:37] <jbossbot> jira [SEAMREST-39] Remove slf4j references [Reopened (Unresolved) Task, Major, Jozef Hartinger] https://issues.jboss.org/browse/SEAMREST-39
[01:06:37] <jbossbot> git [rest] push master URL: http://github.com/seam/rest/compare/38dc538...418f820
[01:06:55] <johnament> hmmm. can i decorate interfaces in seam-beans.xml ?
[01:07:37] *** bitshuffler has quit IRC
[01:07:38] * Diablo-D3 force republishes
[01:07:40] <jbossbot> git [rest] push master d9d448b.. Dan Allen SEAMREST-40 move compatibility tests to compatibility module
[01:07:41] <jbossbot> jira [SEAMREST-40] Migrate compatibility tests to the seam-compatibility module [Resolved (Done) Task, Major, Dan Allen] https://issues.jboss.org/browse/SEAMREST-40
[01:07:41] <jbossbot> git [rest] push master URL: http://github.com/seam/rest/compare/418f820...d9d448b
[01:07:44] <sbryzak> johnament: i'd put all standard cdi config in beans.xml, and seam-config stuff in seam-beans.xml, but stuartdouglas can tell you what best practice is
[01:08:07] <johnament> sbryzak: i'm trying to think of an xml based config for JMS
[01:08:13] <mojavelinux> under 10!
[01:08:17] <stuartdouglas> CDI stuff has to go in beans.xml
[01:08:25] <johnament> yay
[01:08:36] <stuartdouglas> seam-beans.xml only exists because when weld starts the servlet context does not exist
[01:08:41] <johnament> sbryzak: so process annotated type ?
[01:08:51] <stuartdouglas> so it is not possible to get stuff from WEB-INF in a portable manner
[01:08:58] <mojavelinux> I'm going to concentrate on two doc issues right now...going dark for a little while
[01:09:07] <johnament> which ones
[01:09:20] <sbryzak> johnament: sorry, i don't understand the question?
[01:09:38] <johnament> errr sorry
[01:09:47] <sbryzak> Diablo-D3: i'm looking at SEAMSECURITY-48 - which pom file does this come from?
[01:09:48] <jbossbot> jira [SEAMSECURITY-48] mvn dep scope wrong with seam-security-external + seam-bom [Open (Unresolved) Bug, Major, Unassigned] https://issues.jboss.org/browse/SEAMSECURITY-48
[01:09:56] <Diablo-D3> sbryzak: mine
[01:10:09] <Diablo-D3> sbryzak: its from the docs... kind of
[01:10:15] <mojavelinux> SOLDER-61, SEAM-54
[01:10:16] <johnament> stuartdouglas: i mean, if i decorate an interface in seam-config-xml, is it available in process annotated type ?
[01:10:20] <jbossbot> jira [SOLDER-61] Write documentation for JBoss Logging [Open (Unresolved) Feature Request, Major, Dan Allen] https://issues.jboss.org/browse/SOLDER-61
[01:10:24] <jbossbot> jira [SEAM-54] Document the purpose of the seam-bom in the seam refguide [Open (Unresolved) Task, Major, Dan Allen] https://issues.jboss.org/browse/SEAM-54
[01:10:34] <sbryzak> Diablo-D3: the seam-security reference docs?
[01:10:35] <johnament> mojavelinux: SOLDER-89 ?
[01:10:37] <jbossbot> jira [SOLDER-89] Document utilities provided by AnnotationInspector [Open (Unresolved) Feature Request, Major, Dan Allen] https://issues.jboss.org/browse/SOLDER-89
[01:10:48] <sbryzak> i'm just trying to understand the issue
[01:10:49] <Diablo-D3> sbryzak: think so. Im not sure which seam docs I pulled the bom code from
[01:10:52] <mojavelinux> nope, I'm not going to do that one yet
[01:10:53] <Diablo-D3> it was one of them
[01:10:59] <mojavelinux> if anyone wants to pick that one up, that would be awesome
[01:11:03] <johnament> mojavelinux: mind if i take a crack?
[01:11:07] <stuartdouglas> what do you mean by availible? decorators should not affect process annotated type
[01:11:08] <mojavelinux> go for it!
[01:11:11] <Diablo-D3> sbryzak: the seam security dep is from the seam security module's front page
[01:11:32] <sbryzak> Diablo-D3: ok.. so what's the actual problem?
[01:11:32] <Diablo-D3> AHAHAH YES
[01:11:34] <mojavelinux> basically, we just want to give developers using solder awareness of the usefulness of these beans, because they aren't seeing it right now
[01:11:43] <johnament> stolen!
[01:11:50] <Diablo-D3> I HAVE PRODUCED A NEW ERRROORRRRR
[01:11:56] <Diablo-D3> PROGRESS ;_;
[01:12:08] <Diablo-D3> sbryzak: but yeah, you take that depMan and that dep, and it doesnt work
[01:12:13] <Diablo-D3> sbryzak: and I cant figure out why
[01:12:34] <sbryzak> Diablo-D3: i think it's already been fixed
[01:12:45] <sbryzak> there previously wasn't a dependency on seam-security from seam-security-external
[01:12:46] <sbryzak> but there is now
[01:12:50] <Diablo-D3> sbryzak: yes BUT
[01:12:54] <johnament> i hate saturday morning maintenance.
[01:13:13] <Diablo-D3> why do I have to do scope compile?
[01:13:45] <sbryzak> you shouldn't need to
[01:13:50] <Diablo-D3> exactly, I shouldnt
[01:14:09] <sbryzak> so remove it
[01:14:17] <Diablo-D3> then my app doesnt build.
[01:14:34] <sbryzak> and what does mvn dependency:tree say?
[01:14:57] <sbryzak> (btw don't paste it here, pastebin it)
[01:15:15] <Diablo-D3> with scope compile it lists seam-security-external
[01:15:20] <johnament> stuartdouglas: process annotated type is where we build the list of possible routes.
[01:15:34] <johnament> stuartdouglas: but basically, is it available in any of the extension callback events?
[01:15:59] <stuartdouglas> what do you mean by 'is it available' ?
[01:16:01] <sbryzak> lincolnthreeeeeeeeeeeeeee: piiiiiiiiiiiiiinnng
[01:16:13] <Diablo-D3> sbryzak: okay, without scope it says [INFO] +- org.jboss.seam.security:seam-security-external:jar:3.0.0.CR3:runtime
[01:16:39] <Diablo-D3> with scope it says [INFO] +- org.jboss.seam.security:seam-security-external:jar:3.0.0.CR3:compile
[01:17:42] <sbryzak> the scope should be compile by default
[01:18:03] <sbryzak> that's what it is in the openid-rp example, your app's pom must be different somehow
[01:18:20] <Diablo-D3> I have the bom though
[01:18:28] <Diablo-D3> the example I dont think does
[01:18:36] <sbryzak> let me check the bom
[01:19:26] <sbryzak> crap, it's the bom
[01:19:39] <Diablo-D3> oh noes is a bom
[01:19:44] <sbryzak> one moment and i'll fix it
[01:19:55] <Diablo-D3> geet to da choppa
[01:20:47] <jbossbot> git [dist] push master a69b585.. Shane Bryzak SEAMSECURITY-48
[01:20:52] <jbossbot> jira [SEAMSECURITY-48] mvn dep scope wrong with seam-security-external + seam-bom [Open (Unresolved) Bug, Major, Unassigned] https://issues.jboss.org/browse/SEAMSECURITY-48
[01:20:52] <jbossbot> git [dist] push master URL: http://github.com/seam/dist/compare/9df421e...a69b585
[01:21:01] <sbryzak> fixed
[01:21:13] <sbryzak> for now, you'll have to continue overriding the scope
[01:21:16] <sbryzak> until we release a new bom
[01:21:45] <jbossbot> git [solder] push master 41e3e7a.. Dan Allen SOLDER-96 update to Arquillian 1.0.0.Alpha5
[01:21:46] <jbossbot> jira [SOLDER-96] Upgrade Arquillian to 1.0.0.Alpha5 [Pull Request Sent (Unresolved) Task, Major, Aslak Knutsen] https://issues.jboss.org/browse/SOLDER-96
[01:21:46] <jbossbot> git [solder] push master URL: http://github.com/seam/solder/compare/db9b97e...41e3e7a
[01:21:53] <Diablo-D3> sbryzak: I am the worst possible thing ever to happen to seam
[01:21:56] <Diablo-D3> I find bugs.
[01:22:08] <Diablo-D3> and not any bugs, but the must fucking annoying ones
[01:22:17] <sbryzak> those are the best ones to get fixed
[01:22:30] <Diablo-D3> infact, I am certain that they dont exist until I start using seam more
[01:22:43] <sbryzak> 9 issues remaining
[01:23:18] <jbossbot> git [solder] push master 49b5f6c.. Aslak Knutsen SOLDER-18 Add OpenWebBeans profile. OpenWebBeans does not support WebArchive deployments(ARQ-403).
[01:23:19] <jbossbot> jira [SOLDER-18] Add test profile for OpenWebBeans [Pull Request Sent (Unresolved) Feature Request, Major, Aslak Knutsen] https://issues.jboss.org/browse/SOLDER-18
[01:23:23] <jbossbot> jira [ARQ-403] OpenWebBeans container should support WebArchive deployments [Open (Unresolved) Feature Request, Minor, Unassigned] https://issues.jboss.org/browse/ARQ-403
[01:23:23] <jbossbot> git [solder] push master URL: http://github.com/seam/solder/compare/41e3e7a...49b5f6c
[01:23:55] <sbryzak> SEAM-38 i already have a valid solution, but i'm trying to find a better one
[01:23:59] <jbossbot> jira [SEAM-38] new-entity command throws java.lang.NoSuchMethodError: org.eclipse.jdt.internal.compiler.impl.CompilerOptions.getSeverity(J)I [Open (Unresolved) Bug, Major, Shane Bryzak] https://issues.jboss.org/browse/SEAM-38
[01:24:12] <sbryzak> SEAM-58 we can bump
[01:24:20] <jbossbot> jira [SEAM-58] seam-booking - functional tests fail although the application works as expected [Open (Unresolved) Bug, Major, Jozef Hartinger] https://issues.jboss.org/browse/SEAM-58
[01:24:27] <sbryzak> same with SEAM-62
[01:24:28] <jbossbot> jira [SEAM-62] Finish functional tests for seam-booking [Open (Unresolved) Task, Major, Jozef Hartinger] https://issues.jboss.org/browse/SEAM-62
[01:25:16] <sbryzak> right, i've got some docs to write also... will be entering stealth mode for a while just like dan
[01:25:28] *** sbryzak is now known as sbryzak_stealth
[01:25:44] <Diablo-D3> nooo
[01:25:50] <Diablo-D3> I produced a new error
[01:25:53] <johnament> he's gone invisible
[01:25:57] <johnament> Diablo-D3: post it!
[01:26:06] <Diablo-D3> javax.servlet.ServletException: viewId:/login.xhtml - View /login.xhtml could not be restored.
[01:26:18] <johnament> close your browser and go back in
[01:26:36] <Diablo-D3> johnament: uh, no.
[01:26:41] <johnament> darn
[01:26:49] <Diablo-D3> this isnt windows
[01:26:53] <Diablo-D3> nothing bluescreened
[01:26:59] <Diablo-D3> I dont have to wave a rubber chicken
[01:27:00] <johnament> Diablo-D3: no, it does happen to me on linux as well.
[01:27:07] <johnament> Diablo-D3: try CTRL + SHIFT + R
[01:27:14] <Diablo-D3> johnament: no, its not that
[01:27:18] <Diablo-D3> I pressed login
[01:27:23] <jbossbot> git [solder] push master 0916c98.. Dan Allen remove compat test references
[01:27:23] <jbossbot> git [solder] push master URL: http://github.com/seam/solder/compare/49b5f6c...0916c98
[01:27:26] <mojavelinux> solder is now on Arquillian Alpha5
[01:27:34] <mojavelinux> it was necessary to enable the glassfish and openwebbeans profiles
[01:27:41] <mojavelinux> and now we are using the weld-ee embedded from arquillian
[01:27:42] <mojavelinux> not weld
[01:27:45] <mojavelinux> so a big plus
[01:27:50] <mojavelinux> aslak took care of that for us
[01:27:53] <Diablo-D3> uh, hurray?
[01:27:56] <mojavelinux> so it was done by the master's hand
[01:28:05] <mojavelinux> compatibility tests, here we come!
[01:30:29] <mojavelinux> john, while you're in there, can you make the few spelling corrections in SOLDER-73
[01:30:31] <jbossbot> jira [SOLDER-73] Misc documentation issues [Open (Unresolved) Bug, Minor, Unassigned] https://issues.jboss.org/browse/SOLDER-73
[01:30:36] <johnament> yes
[01:30:37] <mojavelinux> should be easy, some may be out dated
[01:31:17] <Diablo-D3> ?
[01:31:20] <mojavelinux> thanks!
[01:31:24] <mojavelinux> okay, gotta make dinner
[01:32:04] *** bitshuffler__ has joined #seam-dev
[01:32:31] <Diablo-D3> ANGRY DIABLO IS ANGRY
[01:33:23] *** bleathem has joined #seam-dev
[01:33:30] <Diablo-D3> STOP GIVING ME A NULL POINTER EXCEPTION DAMNIT
[01:33:49] * bleathem offers Diablo-D3 a null pointer exception
[01:34:44] <Diablo-D3> how do I output the current authenticator impl in jsf?
[01:36:01] *** bitshuffler_ has quit IRC
[01:36:44] <Diablo-D3> <h:outputText value="#{security.authenticatorName}" /> doesnt seem to be right
[01:40:14] <johnament> bleathem: you never responded, what'd you sign up for?
[01:46:23] <johnament> hmm should stereotypes be capitalized?
[01:52:39] *** bitshuffler has joined #seam-dev
[01:54:48] *** bitshuffler__ has quit IRC
[02:04:53] <bleathem> johnament going to work on Solder docs - gotta study the API to learn it first!
[02:15:12] *** bitshuffler_ has joined #seam-dev
[02:19:34] *** bitshuffler has quit IRC
[02:35:32] *** bitshuffler__ has joined #seam-dev
[02:38:54] *** bitshuffler_ has quit IRC
[02:39:08] <Diablo-D3> $ ls target/DiabloPool/WEB-INF/classes/META-INF/
[02:39:08] <Diablo-D3> seam-beans.xml
[02:39:12] <Diablo-D3> so it IS in there
[02:39:42] <Diablo-D3> $ ls target/DiabloPool/WEB-INF/lib/seam-security-*
[02:39:42] <Diablo-D3> target/DiabloPool/WEB-INF/lib/seam-security-3.0.0.CR3.jar
[02:39:42] <Diablo-D3> target/DiabloPool/WEB-INF/lib/seam-security-external-3.0.0.CR3.jar
[02:39:45] <Diablo-D3> and those are in there
[02:54:59] *** bitshuffler has joined #seam-dev
[02:56:25] *** bitshuffler has quit IRC
[02:59:05] *** bitshuffler__ has quit IRC
[03:02:43] *** tsurdilo1 has quit IRC
[03:09:28] <bleathem> Do Seam Security support making a Stereotype out of @SecurityBindingType?
[03:10:25] <sbryzak_stealth> bleathem: no
[03:10:29] <sbryzak_stealth> you can raise a feature request though
[03:10:39] <sbryzak_stealth> but it won't be done before the release
[03:10:40] <bleathem> ok, so Faces doesn't have to support it then
[03:10:44] <sbryzak_stealth> nope
[03:13:47] *** daniel_hinojosa has quit IRC
[03:29:10] <jbossbot> git [solder] push master 1095759.. mgencur at redhat dot com fix compilation of tests when running code-coverage
[03:29:10] <jbossbot> git [solder] push master URL: http://github.com/seam/solder/compare/0916c98...1095759
[03:39:00] <jbossbot> git [solder] push master bdf72ae.. Dan Allen Merge branch 'master' of https://github.com/johnament/solder into johnament
[03:39:00] <jbossbot> git [solder] push master URL: http://github.com/seam/solder/compare/1095759...bdf72ae
[03:40:47] <johnament> 8!
[03:52:08] *** johnament has quit IRC
[03:53:44] <bleathem> Just thought of something
[03:54:04] <bleathem> we can put a @FacesRedirect(true) annotation in the viewconfig
[03:54:25] <bleathem> shouldn't be that hard to implement, just listen for the preNavigationEvent
[03:54:54] <bleathem> worth a looking further at anyways. - JIRA !!
[03:58:47] <bleathem> SEAMFACES-121
[03:58:48] <jbossbot> jira [SEAMFACES-121] Support @FacesRedirect(true) in the @ViewConfig [Open (Unresolved) Feature Request, Major, Unassigned] https://issues.jboss.org/browse/SEAMFACES-121
[03:59:10] <bleathem> I think i need to add a View Configuration
[03:59:19] <bleathem> I think i need to add a "View Configuration" component in jira
[03:59:29] <bleathem> I'm linking too man issues to SEAMFACES_33
[03:59:47] <bleathem> Do I have to check with someone before I do that?
[04:00:01] *** sbryzak_stealth is now known as sbryzak
[04:00:17] <sbryzak> bleathem: you should be an admin, you can create whatever jira components you want
[04:00:27] <bleathem> ok, thks
[04:04:17] *** lincolnthree has quit IRC
[04:15:04] *** daniel_hinojosa has joined #seam-dev
[04:52:21] <jbossbot> git [solder] push master 8ceb170.. Dan Allen cleanups...
[04:52:21] <jbossbot> git [solder] push master URL: http://github.com/seam/solder/compare/bdf72ae...8ceb170
[05:10:10] <jbossbot> git [dist] push master d31ad44.. Dan Allen add an intro
[05:10:11] <jbossbot> git [dist] push master URL: http://github.com/seam/dist/compare/a69b585...d31ad44
[05:13:24] <mojavelinux> we have an intro!
[05:13:36] <mojavelinux> i mostly stole it from what I wrote on the Seam 3 home page
[05:13:42] <mojavelinux> but why not, I thought about that plenty
[05:13:48] <mojavelinux> working on the seam-bom section now
[05:27:31] <jbossbot> git [faces] push master 681d92f.. Brian Leathem fixed the short-ly folder directory in the pom.xml
[05:27:31] <jbossbot> git [faces] push master URL: http://github.com/seam/faces/compare/df033fc...681d92f
[05:33:23] <bleathem> Phew - Hudson is back to normal!
[05:33:26] <bleathem> for Faces
[05:42:29] <mojavelinux> seam-bom documentation bit almost done....
[05:42:32] <sbryzak> bleathem: you didn't need to rename the faces examples
[05:42:44] <bleathem> no?
[05:43:09] <sbryzak> not the directory names
[05:43:38] <bleathem> I went with what was in the ticket, want me to change them back?
[05:43:50] <sbryzak> which ticket?
[05:44:03] <bleathem> I was cleaning up the faces-security example, and thouth I'd do the shrt-ly one at the same time
[05:44:12] <bleathem> the one you closed yeaterday
[05:44:16] <bleathem> let me look it up
[05:44:18] <bleathem> 1 sec
[05:44:53] <bleathem> SEAMFACES-120
[05:44:54] <jbossbot> jira [SEAMFACES-120] The short.ly example does not follow the Seam example naming convention [Resolved (Out of Date) Bug, Major, Shane Bryzak] https://issues.jboss.org/browse/SEAMFACES-120
[05:45:06] <bleathem> folder name in the seam distribution - <module name>-<example name>
[05:45:11] <sbryzak> that was more to do with the artifact name
[05:45:24] <bleathem> right, which you'd already fixed
[05:45:26] <sbryzak> that folder name is taken care of by the example assembly
[05:45:37] <bleathem> my bad - sorry!
[05:45:43] <bleathem> want me to change it back?
[05:45:44] <sbryzak> it might be ok, just wait a sec
[05:45:53] <sbryzak> i need to try building the distribution to make sure it hasn't broken
[05:46:38] <bleathem> yeah, I can't build the distribution locally, I haven't had the chance to track down why
[05:46:54] <sbryzak> i'm building it now
[05:47:11] <bleathem> I get an error that I'm missing a class net/socialchange/doctype/DoctypeGenerator
[05:47:11] <sbryzak> as long as it can still locate the faces example, and it puts it in the correct directory, it should be ok
[05:47:20] <bleathem> but I'll follow up on that later
[05:50:04] <sbryzak> bleathem: it looks ok
[05:50:13] <bleathem> ok, cool
[05:50:25] <sbryzak> the princess-rescue example is broken again though, weird
[05:50:39] <bleathem> what module is that in?
[05:50:43] <sbryzak> config
[05:50:56] <sbryzak> it's probably my fault
[05:51:10] <stuartdouglas> if the package names where changed it will change the xml namespaces
[05:53:05] <jbossbot> git [dist] push master 2bd880f.. Dan Allen SEAM-54 document the seam-bom
[05:53:06] <jbossbot> jira [SEAM-54] Document the purpose of the seam-bom in the seam refguide [Open (Unresolved) Task, Major, Dan Allen] https://issues.jboss.org/browse/SEAM-54
[05:53:06] <jbossbot> git [dist] push master URL: http://github.com/seam/dist/compare/d31ad44...2bd880f
[05:53:18] <mojavelinux> yeah, 7 issues
[05:56:07] <sbryzak> mojavelinux: nicely done
[05:56:15] <sbryzak> i'm going to assume the QE guys won't be working this weekend
[05:56:25] <sbryzak> they currently have 3 issues assigned to them
[05:56:35] <sbryzak> i'm tempted to bump both of jozef's
[05:56:52] <sbryzak> and i can take care of SEAMSECURITY-46
[05:56:53] <jbossbot> jira [SEAMSECURITY-46] security examples - provide build profile for GlassFish [Open (Unresolved) Task, Major, Martin Gencur] https://issues.jboss.org/browse/SEAMSECURITY-46
[05:57:35] <sbryzak> for SEAM-31 we can probably close it for now
[05:57:37] 
[05:57:40] <sbryzak> i know that jose has done most of the work
[05:57:48] <sbryzak> anything else he wants to do can be done post-release
[06:01:37] <jbossbot> git [faces] push master fa13fc2.. Brian Leathem Documented the SecurityPhaseListener class
[06:01:38] <jbossbot> git [faces] push master URL: http://github.com/seam/faces/compare/681d92f...fa13fc2
[06:21:26] <mojavelinux> shane, it would be best if you recreated the remaining work with specific action items
[06:21:36] <mojavelinux> the "booking example improvements" was after all a bit generic of a title
[06:21:45] <mojavelinux> which tends to make the issue hard to close :)
[06:22:10] <sbryzak> agreed, i don't know what is remaining though
[06:22:40] <sbryzak> i'll close the issue as-is, and let jose create a more specific one
[06:26:54] <sbryzak> down to 5 issues now
[06:27:41] <mojavelinux> shane, we are going to need to pull this dynamic proxies for JBoss Logging out and also warn a better message if the concrete impl is not found
[06:27:54] <mojavelinux> talked to David Llloyd about this and he said he strongly encourages it
[06:28:08] <mojavelinux> it's not a hard thing, the dynamic proxies are not going to work right now anyway
[06:28:20] <mojavelinux> because of how the check for the system property is done
[06:28:31] <sbryzak> what's involved for that?
[06:28:35] <mojavelinux> but it simplifies things a lot
[06:28:40] <mojavelinux> well, first, pull it from the refguide
[06:28:43] <mojavelinux> which i'm doing now
[06:28:47] <mojavelinux> that way, no one knows about it
[06:28:55] <sbryzak> good idea
[06:29:09] <mojavelinux> and the second is to add a check in the extension to see if the impl can be found eagerly
[06:29:31] <mojavelinux> and provide a clear message that says "use the annotation processor here -> link"
[06:29:45] <mojavelinux> that should save us a lot of trouble...I'm doing the refguide now
[06:29:52] <mojavelinux> I can get ken to add the check perhaps tomorrow
[06:29:59] <mojavelinux> the check isn't critical
[06:30:03] <mojavelinux> but it will save us a lot of headaches
[06:30:13] <mojavelinux> I realized, why wait for jboss logging to fail when it is missing
[06:30:16] <mojavelinux> when we can do it in the extension
[06:30:25] <sbryzak> no problem
[06:30:27] <mojavelinux> just have to try to fetch the bean and see if it's satisified
[06:30:34] <mojavelinux> and then we can be very proactive about it
[06:30:40] <sbryzak> i'll still be writing docs tomorrow, so there's some time left
[06:31:07] <mojavelinux> cool
[06:31:20] <mojavelinux> but yeah, important step is pull it from the docs
[06:31:25] <mojavelinux> and the docs have the annotation processor information now
[06:31:29] <mojavelinux> so it shouldn't be a problem
[06:31:49] <jbossbot> git [security] push master ac6d95e.. Shane Bryzak SEAMSECURITY-46
[06:31:51] <jbossbot> jira [SEAMSECURITY-46] security examples - provide build profile for GlassFish [Open (Unresolved) Task, Major, Martin Gencur] https://issues.jboss.org/browse/SEAMSECURITY-46
[06:31:51] <jbossbot> git [security] push master URL: http://github.com/seam/security/compare/8764ea1...ac6d95e
[06:31:57] <sbryzak> agreed.. if it's not documented, it doesn't exist
[06:33:23] <sbryzak> 4 issues remaining
[06:34:04] <jbossbot> git [forge] push master 8f1d226.. Lincoln Baxter III fixed NewProjectPlugin on windows
[06:34:05] <jbossbot> git [forge] push master 2fb29ac.. Mike Brock fixes
[06:34:05] <jbossbot> git [forge] push master 869653c.. Lincoln Baxter III pathspec issue fixes
[06:34:05] <jbossbot> git [forge] push master URL: http://github.com/seam/forge/compare/44630e7...869653c
[06:39:48] *** jharting has joined #seam-dev
[06:51:14] <sbryzak> jharting: you're either up very late, or very early
[06:51:36] <jharting> sbryzak: not that early
[06:51:48] <sbryzak> ah yeah, it would be about 8am there right?
[06:52:07] <jharting> sbryzak: almost 7am, and it's going to be almost 8am tomorrow same time due to DST change
[06:52:29] <sbryzak> ah, for the summer i guess
[06:52:48] <jharting> sbryzak: yes
[06:53:10] <sbryzak> the good news is we're down to 4 issues
[06:54:41] <jharting> sbryzak: great, the two remaining that are assigned to me are related to functional tests, so we can go without them, however, I can fix them in a few hours
[06:54:59] <sbryzak> jharting: no problem if you don't fix them, you can bump them if you like
[06:57:36] <jharting> sbryzak: ok
[07:01:19] <jbossbot> git [rest] push master ab2f93f.. Jozef Hartinger SEAMREST-40
[07:01:20] <jbossbot> jira [SEAMREST-40] Migrate compatibility tests to the seam-compatibility module [Resolved (Done) Task, Major, Dan Allen] https://issues.jboss.org/browse/SEAMREST-40
[07:01:20] <jbossbot> git [rest] push master URL: http://github.com/seam/rest/compare/d9d448b...ab2f93f
[07:12:51] <daniel_hinojosa> Question: I am working on SERVLET-22 Issue
[07:12:57] <daniel_hinojosa> and creating an ear file
[07:13:16] <daniel_hinojosa> uhm. should solder be in the lib of the ear?
[07:13:19] <mojavelinux> logging is now one of the best damn features documented :)
[07:14:04] <mojavelinux> shane, solder-tooling should be in the parent pom
[07:14:20] <mojavelinux> sorry, seam-bom
[07:14:24] <mojavelinux> we need to make sure that's in there
[07:14:26] <sbryzak> i thought i added it
[07:14:30] <mojavelinux> it should be scope provided
[07:14:32] <mojavelinux> oh, you may have
[07:14:33] <mojavelinux> just saying
[07:14:42] <sbryzak> it's added
[07:14:47] <sbryzak> i can't make it scope provided
[07:14:56] <sbryzak> or else it won't be included in the distribution
[07:15:05] <mojavelinux> ah
[07:15:07] <mojavelinux> got it
[07:15:25] <sbryzak> stupid limitation of the assembly plugin
[07:15:39] <Diablo-D3> okay now I know something is wrong
[07:15:54] <Diablo-D3> I put sysouts at the start of the methods in those three java files
[07:15:59] <sbryzak> daniel_hinojosa: yes it should be in the lib
[07:16:23] <Diablo-D3> only my version of OpenIdRelyingPartyCustomizer gets called
[07:16:26] <jbossbot> git [solder] push master dde2b4f.. Dan Allen SOLDER-61 documentation for JBoss Logging
[07:16:27] <jbossbot> jira [SOLDER-61] Write documentation for JBoss Logging [Open (Unresolved) Feature Request, Major, Dan Allen] https://issues.jboss.org/browse/SOLDER-61
[07:16:27] <jbossbot> git [solder] push master URL: http://github.com/seam/solder/compare/8ceb170...dde2b4f
[07:17:22] <jbossbot> git [solder] push master 555486f.. Dan Allen SOLDER-61 followup
[07:17:23] <jbossbot> jira [SOLDER-61] Write documentation for JBoss Logging [Open (Unresolved) Feature Request, Major, Dan Allen] https://issues.jboss.org/browse/SOLDER-61
[07:17:24] <jbossbot> git [solder] push master URL: http://github.com/seam/solder/compare/dde2b4f...555486f
[07:17:37] <jbossbot> git [solder] push master be2da01.. Dan Allen add instructions for running tests
[07:17:37] <jbossbot> git [solder] push master URL: http://github.com/seam/solder/compare/555486f...be2da01
[07:17:49] <mojavelinux> yeah!
[07:17:55] <mojavelinux> we have docs for JBoss Logging
[07:17:57] <mojavelinux> first in the world
[07:17:58] <mojavelinux> :)
[07:17:59] <daniel_hinojosa> sbryzak:  Just to verify what you said: in ear/lib?
[07:18:13] <sbryzak> daniel_hinojosa: i think so
[07:18:19] <sbryzak> where else would it go?
[07:18:26] <mojavelinux> i'm very glad you are checking this daniel
[07:18:32] <sbryzak> i guess it could be packaged in the war
[07:18:34] <daniel_hinojosa> no problem it helps me
[07:18:50] <mojavelinux> yeah, it's gonna help a lot of people, because we just haven't had time to think about packaging much
[07:18:51] <daniel_hinojosa> plus my business depends on Seam
[07:18:54] <sbryzak> to be honest, i haven't packaged anything in an ear since seam 2/JBAS5
[07:18:57] <mojavelinux> as we have been focused on just getting wars working :)
[07:19:02] <daniel_hinojosa> yeah
[07:19:12] <mojavelinux> sbryzak: I can say I have more recently thanks to arquillian
[07:19:20] <mojavelinux> in fact, I've packaged more ears with arquillian than anything else
[07:19:23] <daniel_hinojosa> oh btw, solder is not a dependency for seam-servlet
[07:19:24] <sbryzak> i don't know why anyone would want to package anything in an ear now
[07:19:33] <sbryzak> i guess we need to test it though ;)
[07:19:36] <Diablo-D3> 02:19:31,695 INFO  [STDOUT] OpenIdRelyingPartyCustomizer servletInitialized
[07:19:46] <daniel_hinojosa> but I can understand why
[07:19:46] <mojavelinux> well, it still makes sense when the app is bigger
[07:19:48] <Diablo-D3> thats all I see
[07:19:51] <daniel_hinojosa> yeah
[07:19:54] <mojavelinux> yeah, it's just that you don't do it first
[07:20:01] <mojavelinux> you start out in war land
[07:20:01] <daniel_hinojosa> it didn't at first but when you do an ear
[07:20:09] <daniel_hinojosa> I still don't have it working
[07:20:15] <daniel_hinojosa> but I have solder in ear/lib
[07:20:21] <daniel_hinojosa> servlet in war/lib
[07:20:25] <mojavelinux> 4 issues! wow
[07:20:38] <mojavelinux> 3 issues
[07:20:49] <Diablo-D3> how the fuck can login fail if it never tried to login
[07:20:58] <sbryzak> jharting will have his issues sorted out today also
[07:21:07] <sbryzak> Diablo-D3: are you getting an error?
[07:21:13] <Diablo-D3> sbryzak: the same damned one
[07:21:17] <sbryzak> pastebin?
[07:21:41] <sbryzak> i seriously need to refactor the openid code, it's way obfuscated
[07:21:45] <Diablo-D3> http://pastebin.com/iYw0VG9a
[07:22:15] <sbryzak> it still looks like your authenticatorName isn't configured
[07:22:21] <Diablo-D3> I copied those three java files verbatim, my login.xhtml is that, my seam-beans.xml is verbatim and in the right spot
[07:22:23] <sbryzak> set a breakpoint in IdentityImpl.authenticate()
[07:22:26] <Diablo-D3> and my beans.xml contains the right shit
[07:22:32] <sbryzak> see what authenticatorName is
[07:23:55] <mojavelinux> what if servlet is in ear too would that work?
[07:24:07] <mojavelinux> or must it be in the war to be scoped to the war?
[07:24:37] <daniel_hinojosa> *ALL* Can I get a set of eyes on this? http://pastebin.com/eWyajS7A
[07:25:11] <daniel_hinojosa> scratch it
[07:25:14] <daniel_hinojosa> don't look at it
[07:25:26] <daniel_hinojosa> for somereason it's holding on to a class that shouldn't be there
[07:26:03] <sbryzak> too late, i looked
[07:26:16] <mojavelinux> hahha
[07:26:40] <mojavelinux> I wouldn't trust jboss as with an undeployment, i've seen funny things...might be faster to restart the server frequently :)
[07:26:51] <mojavelinux> to get a clear picture...if you think something it out of sorts
[07:27:10] <mojavelinux> one thing we've learned a ton in doing this work on Seam 3
[07:27:25] <mojavelinux> we are the first people to ever test half the deployment and extension features of these EE 6 app servers
[07:27:27] <mojavelinux> hehehe
[07:27:38] <mojavelinux> much to the bane of shane's tired existence
[07:27:41] <mojavelinux> mine included
[07:27:57] <sbryzak> i hope to drown my sorrows in beer next week after the release is done
[07:29:23] <Diablo-D3> okay so...
[07:30:06] <Diablo-D3> authenticatorName is null
[07:30:21] <Diablo-D3> I put the breakpoint at activeAuthemticator.authenticate()
[07:30:24] <Diablo-D3> like 305
[07:30:27] <daniel_hinojosa> Alright: *ALL* Can you provide input into this: http://pastebin.com/NAguafJW
[07:30:27] <Diablo-D3> er, line
[07:30:42] <sbryzak> daniel_hinojosa: you sure?
[07:31:13] <daniel_hinojosa> sbryzak: For reals this time
[07:31:14] <daniel_hinojosa> ha
[07:31:22] <sbryzak> ok :)
[07:31:34] <sbryzak> unsatisfied dependency
[07:31:40] <sbryzak> where is seam-faces.jar?
[07:31:51] <daniel_hinojosa> That is in the war
[07:31:58] <daniel_hinojosa> should it be upped to the ear?
[07:32:33] <daniel_hinojosa> the latest I found was seam-faces:3.0.0.CR2
[07:32:38] <mojavelinux> we saw this earlier today
[07:32:42] <sbryzak> one minute while i look at code
[07:32:44] <mojavelinux> at least, it's in the irc logs
[07:33:14] <daniel_hinojosa> I can put this ear project I made on github for everyone if everyone needs it
[07:33:44] <mojavelinux> that's an odd place to have an injection in seam faces
[07:33:48] <mojavelinux> I wonder why it was put there
[07:33:59] <mojavelinux> not what it does, but why it was put there specifically
[07:34:14] <mojavelinux> hmmm, might be grounds for a future jira
[07:34:36] <daniel_hinojosa> NOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
[07:34:38] <daniel_hinojosa> ha
[07:34:52] <sbryzak> you made an important discovery?
[07:35:09] <daniel_hinojosa> the lost civilization of ugh
[07:35:13] <daniel_hinojosa> ha
[07:35:26] <sbryzak> i'm guessing we can stop looking now...
[07:35:42] <daniel_hinojosa> if you do need a JIRA I'll put this ear on github mojavelinux
[07:35:50] <mojavelinux> well, I don't think that's why it breaks
[07:35:52] <mojavelinux> I don't think
[07:35:57] <mojavelinux> just that, well
[07:36:00] <mojavelinux> it's not quite right
[07:36:10] <mojavelinux> an extension should not have a scope annotation on it
[07:36:23] <mojavelinux> first of all, because it's already application scoped as it is
[07:37:28] <Diablo-D3> sbryzak: so any ideas?
[07:37:42] <sbryzak> Diablo-D3: it seems like your configuration isn't being read
[07:37:46] <mojavelinux> you might need a snapshot of faces, i'm not sure...brian fixed a lot of issues in CR2
[07:37:57] <sbryzak> Diablo-D3: you do have seam-config included in your project, right?
[07:38:11] <Diablo-D3> yes
[07:38:20] <mojavelinux> can you try w/o seam faces daniel?
[07:38:20] <Diablo-D3> $ ls target/DiabloPool/WEB-INF/classes/META-INF/seam-beans.xml
[07:38:21] <Diablo-D3> target/DiabloPool/WEB-INF/classes/META-INF/seam-beans.xml
[07:38:25] <Diablo-D3> is it not in the right spot?
[07:38:27] <sbryzak> hmm, there should be a log message while deploying
[07:38:41] <sbryzak> Diablo-D3: that's the right place for seam-beans.xml
[07:38:58] <daniel_hinojosa> mojavelinux: yessir
[07:39:15] <daniel_hinojosa> mojavelinux: BTW, I have no idea where to put beans.xml
[07:39:26] <daniel_hinojosa> I did what the java.sun docs said
[07:39:36] <daniel_hinojosa> and put it in META-INF/ in the ear
[07:39:53] <daniel_hinojosa> but I have one in the ear, the war and the ejb
[07:40:02] <daniel_hinojosa> Jason mentioned in should be in the ejb
[07:40:09] <daniel_hinojosa> so just FYI
[07:40:14] <daniel_hinojosa> ok taking out faces
[07:40:23] <daniel_hinojosa> and taking out catch while I am at it
[07:42:06] <mojavelinux> the beans.xml goes in each jar
[07:42:12] <mojavelinux> if there are beans in the jar
[07:42:23] <mojavelinux> i'm not sure about META-INF/beans.xml
[07:42:29] <mojavelinux> I guess I should read that section :)
[07:42:58] <daniel_hinojosa> mojavelinux: http://pastebin.com/3p3DmVPC
[07:43:31] <mojavelinux> this is interesting, it's the same problem essentially
[07:43:31] <daniel_hinojosa> attn: bleathem,  thoust rocketh
[07:43:38] <mojavelinux> injecting an extension into a bean
[07:43:57] <mojavelinux> makes me wonder if this is broken on jboss as
[07:44:02] <mojavelinux> arquillian would tell me :)
[07:44:05] <mojavelinux> or I should say
[07:44:10] <mojavelinux> we would need to create an ike test
[07:44:14] <mojavelinux> in compat
[07:44:19] <mojavelinux> or should
[07:44:22] <mojavelinux> hmm
[07:44:52] <mojavelinux> so you have seam-servlet.jar in the war?
[07:45:04] <daniel_hinojosa> yes
[07:46:02] <mojavelinux> okay, you don't need beans.xml in /META-INF of ear
[07:46:12] <mojavelinux> it needs to be in the EJB modules specifically
[07:46:21] <mojavelinux> do you have a reference that mentions it in the root of the ear?
[07:46:30] <daniel_hinojosa> yes
[07:46:53] <mojavelinux> i'm trying to think about what that actually means
[07:47:05] <daniel_hinojosa> it was the Oracle tutorial
[07:47:09] <daniel_hinojosa> but I may have read it wrong
[07:47:15] <mojavelinux> yeah, I'm looking at that
[07:47:19] <mojavelinux> I don't think it's needed there
[07:47:24] <mojavelinux> because it's just about scanning
[07:47:30] <mojavelinux> so it needs to be with the classes
[07:47:40] <mojavelinux> similiar to components.xml from seam 2 (or seam.properties)
[07:48:12] <mojavelinux> if you were creating an application
[07:48:15] <mojavelinux> packaging it as an ear
[07:48:19] <mojavelinux> and you wanted to make a servlet listener
[07:48:28] <Diablo-D3> sbryzak: theres something wrong with this code anyhow
[07:48:29] <mojavelinux> would you put that in the war? or in the ear?
[07:48:37] <Diablo-D3>          activeAuthenticator = lookupAuthenticator();
[07:48:37] <Diablo-D3>
[07:48:37] <Diablo-D3>          if (activeAuthenticator == null)
[07:48:42] <Diablo-D3>             throw new AuthenticationException("An Authenticator could not be located");
[07:48:49] <Diablo-D3> shouldnt that have thrown the exception?
[07:49:03] <sbryzak> Diablo-D3: no, because it found an authenticator
[07:49:28] <Diablo-D3> argh
[07:49:35] <Diablo-D3> its trying to use IdmAuthenticator
[07:49:41] <Diablo-D3> I dont think thats what I want
[07:49:56] <sbryzak> it's not, it's using that because authenticatorName is null
[07:50:06] <sbryzak> you need to work out why your bean isn't being configured
[07:50:09] <sbryzak> did you check the log?
[07:50:20] <Diablo-D3> I dont see anything wrong with the log
[07:50:45] <daniel_hinojosa> mojavelinux: http://download.oracle.com/javaee/6/tutorial/doc/gjbnz.html
[07:50:46] <daniel_hinojosa> yeah
[07:50:50] <daniel_hinojosa> you were right
[07:51:03] <daniel_hinojosa> gonna gut beans from the ear/META-ING
[07:51:06] <daniel_hinojosa> INF
[07:51:14] <sbryzak> Diablo-D3: do you have log messages from seam-config?
[07:51:36] <Diablo-D3> http://pastebin.com/4ySZJDUt
[07:51:43] <Diablo-D3> thats the entire log from deployment
[07:52:30] <sbryzak> i don't see any seam-config messages there
[07:52:42] <Diablo-D3> neither do I.
[07:52:42] <sbryzak> are you sure you're including it in your deployment?
[07:52:54] <daniel_hinojosa> mojavelinux: Same message
[07:53:09] <Diablo-D3> sbryzak: hrrrrm
[07:53:12] <mojavelinux> what if you put seam-servlet.jar in the ear
[07:53:15] <Diablo-D3> sbryzak: I think I found another pom bug.
[07:53:24] <sbryzak> Diablo-D3: pastebin your pom.xml
[07:53:34] <Diablo-D3> it has seam-international, persistence, security, security-external, servlet, and solder
[07:53:49] <Diablo-D3> but no seam-config in my war
[07:54:30] <mojavelinux> hehehe, yes
[07:54:34] <Diablo-D3> http://pastebin.com/G4AFeMEE
[07:54:36] <mojavelinux> when seam-config starts, it will be nice and noisy
[07:54:58] <mojavelinux> nice looking pom :)
[07:55:02] <sbryzak> Diablo-D3: you don't have seam config listed as a dependency
[07:55:08] <Diablo-D3> sbryzak: I shouldnt have to
[07:55:17] <mojavelinux> seam-config is optional
[07:55:19] <sbryzak> explain?
[07:55:30] <Diablo-D3> one of those two seam-security jars should drag it in
[07:55:37] <sbryzak> it's not optional if you want to use seam-beans.xml to configure your beans
[07:55:42] <sbryzak> no they won't
[07:55:48] <sbryzak> it's not a dependency
[07:55:50] <mojavelinux> it's optional for seam security I mean
[07:55:52] <Diablo-D3> =|
[07:55:59] <mojavelinux> you don't have to use seam config to configure seam security
[07:56:04] <mojavelinux> so, hence, optional dependency
[07:56:10] * Diablo-D3 beats the example with a bat
[07:56:12] <sbryzak> it's not any sort of dependency for seam-security
[07:56:15] <mojavelinux> right
[07:56:24] <Diablo-D3> so how else can I configure this?
[07:56:32] <sbryzak> the example is correct
[07:56:43] <sbryzak> it has an explicit dependency for it
[07:56:44] <mojavelinux> yeah, if you are using seam-beans.xml, you need to add seam-config
[07:56:46] <mojavelinux> seam-config-xml
[07:56:48] <Diablo-D3> the example is correct for non-standard seam security usage, sure
[07:57:06] <sbryzak> Diablo-D3: just add it to your pom
[07:57:20] <Diablo-D3> what other ways of configuring seam security is there?
[07:57:26] <sbryzak> <dependency><groupId>org.jboss.seam.config</groupId><artifactId>seam-config-xml</artifactId></dependency>
[07:57:29] <Diablo-D3> because I may end up having to se that anyhow
[07:57:43] <Diablo-D3> like if I offer both local and openid auth
[07:57:52] <sbryzak> there are no other ways, unless you write something yourself
[07:58:12] <Diablo-D3> I'd look in the docs but... uh.. *cough* what docs
[07:58:20] <mojavelinux> there needs to be a pastestacktrace.com or something
[07:58:29] <mojavelinux> because stacktraces in pastebin look kind of ugly
[07:58:32] <sbryzak> there are docs for seam-config
[07:58:48] <Diablo-D3> sbryzak: well, can I programmably configure this inside, say, the jsf?
[07:58:55] <mojavelinux> http://docs.jboss.org/seam/3/config/latest/reference/en-US/html/
[07:59:08] <sbryzak> Diablo-D3: you can, but i don't recommend it
[07:59:25] <Diablo-D3> well, how would you suggest offering both kinds of authentication at the same time?
[07:59:38] <sbryzak> Diablo-D3: docs are here: http://docs.jboss.org/seam/3/latest/reference/en-US/html/xml-provider.html
[07:59:56] <sbryzak> you want to provide internal authentication, and openid authentication?
[08:00:08] <Diablo-D3> yes, a lot of sites do that.
[08:00:16] <sbryzak> ok, that's different then
[08:00:30] <sbryzak> you can use the JSF to do that
[08:00:47] <sbryzak> create a radio group or something
[08:01:00] <sbryzak> each value in the radiogroup should be an authenticator name
[08:01:04] <mojavelinux> i'm fading pretty quick. daniel, once you've tried all permutations and reached a stopping point, I would suggest pushing this up as an example into the examples project; that way QE can dig deeper, might even be able to put together tests for it
[08:01:16] <sbryzak> you'll have to put a @Named on your custom authenticator
[08:01:18] <mojavelinux> we need an EAR example anyway, and that would be a huge help to have something to get us started
[08:01:24] <mojavelinux> I'm assuming you've got it based on Maven?
[08:01:35] <sbryzak> and the radio group should bind to #{identity.authenticatorName}
[08:02:49] <daniel_hinojosa> mojavelinux: https://github.com/dhinojosa/seam3_in_your_ear
[08:02:56] <daniel_hinojosa> I'll email it to you
[08:02:59] <mojavelinux> awesome
[08:03:05] <mojavelinux> hey, shane, I think we can kill SEAM-3
[08:03:06] <jbossbot> jira [SEAM-3] Merge "API" javadoc from IMPL to API [Open (Unresolved) Task, Major, Unassigned] https://issues.jboss.org/browse/SEAM-3
[08:03:14] <daniel_hinojosa> ok goodnight
[08:03:16] <daniel_hinojosa> thanks
[08:03:17] <mojavelinux> you've got the docs merging and I don't know what this is about anyway
[08:03:26] <mojavelinux> thanks daniel!
[08:03:50] <mojavelinux> it will be awesome when we get this, because, well, obviously, we need to be able to make this work :)
[08:03:56] <sbryzak> mojavelinux: yeah, i'll close it
[08:04:08] <mojavelinux> have a beer pomodoro on me
[08:04:21] <mojavelinux> and i'll be sure to keep you in the loop about any results we find
[08:05:08] <mojavelinux> shane, we may need to kick this one over to QA (this EAR thing)
[08:05:22] <sbryzak> sure
[08:05:23] <mojavelinux> because you know people are going to ask about this, and they may be able to hammer on it for a while
[08:05:25] <sbryzak> do you think it's a blocker?
[08:05:54] <mojavelinux> I think we need to know if it works or not
[08:06:06] <mojavelinux> if we have bugs, then, we just have to say we can't do ears yet
[08:06:11] <mojavelinux> but if we don't, it would be good to know that
[08:06:15] <daniel_hinojosa> sbryzak + mojavelinux: sent it to seam dev list
[08:06:16] <mojavelinux> if it's just a packaging thing
[08:06:19] <mojavelinux> thanks!
[08:06:23] <sbryzak> thanks daniel
[08:08:01] <mojavelinux> I assigned to jozef for analysis by QA
[08:08:20] <mojavelinux> I think we should put this in the seam examples...we can get it spruced up as we go along, the important part is that we have an ear example at all
[08:09:09] <mojavelinux> SEAM-23 should be done for final, unless it's out of date
[08:09:10] <jbossbot> jira [SEAM-23] Incorrect version Seam Catch docs in the dist bundle [Open (Unresolved) Bug, Major, Shane Bryzak] https://issues.jboss.org/browse/SEAM-23
[08:09:27] <mojavelinux> also SEAM-26
[08:09:28] <jbossbot> jira [SEAM-26] Faces sources contains .class instead of .java files [Open (Unresolved) Bug, Major, Unassigned] https://issues.jboss.org/browse/SEAM-26
[08:09:33] <sbryzak> good idea
[08:09:34] <mojavelinux> seem like minor stuff that you'll do in packaging anyway
[08:10:25] <mojavelinux> is there merit to SEAM-56?
[08:10:27] <jbossbot> jira [SEAM-56] Some jars are missing in the distribution required by the seam-booking sample app [Open (Unresolved) Bug, Major, Unassigned] https://issues.jboss.org/browse/SEAM-56
[08:11:05] <sbryzak> no
[08:11:10] <sbryzak> the examples are built with maven
[08:11:21] <sbryzak> it should pull in any required dependencies
[08:11:40] <Diablo-D3> sbryzak: okay, Ive gotten farther
[08:11:53] <Diablo-D3>   <h:selectOneRadio value="#{identity.authenticatorName}">
[08:11:53] <Diablo-D3>     <f:selectItem itemLabel="OpenID" itemValue="openIdAuthenticator"/>
[08:11:54] <Diablo-D3>   </h:selectOneRadio>
[08:12:00] <sbryzak> mojavelinux: marking it won't fix
[08:12:05] <Diablo-D3> I click login... it keeps loading forever
[08:12:19] <sbryzak> Diablo-D3: looks good
[08:12:26] <sbryzak> Diablo-D3: the debugger is your friend
[08:12:27] <mojavelinux> I tried to get websphere installed the other day
[08:12:33] <mojavelinux> it just timed out on me setting up a domain
[08:12:35] <mojavelinux> 3 times
[08:12:38] <mojavelinux> so I gave up
[08:12:50] <mojavelinux> IBM makes it damn near impossible to install, makes you truly appreciate jboss as and glassfish
[08:12:51] <mojavelinux> unzip
[08:12:51] <mojavelinux> go
[08:13:15] <sbryzak> mojavelinux: i wonder how the weblogic experience is
[08:13:52] <Diablo-D3> sbryzak: how exactly does openid auth work anyhow? how does google or whoever pass auth stuff back to the server backend?
[08:14:24] <mojavelinux> I really want to know...I also want to try the archetype on weblogic
[08:14:27] <mojavelinux> sorry
[08:14:28] <mojavelinux> ye
[08:14:29] <mojavelinux> yes
[08:14:36] <mojavelinux> but I can't get either installed
[08:14:38] <mojavelinux> ugh
[08:14:43] <mojavelinux> I need like a dummy guide for this stuff
[08:14:51] <mojavelinux> my issue might be my 64 bit machine
[08:14:55] <mojavelinux> guess I should try on 32 bit
[08:15:02] <mojavelinux> what would even be nicer!
[08:15:07] <mojavelinux> is a VM image
[08:15:15] <sbryzak> Diablo-D3: http://www.windley.com/archives/2006/04/how_does_openid.shtml
[08:15:16] <mojavelinux> wonder if QA can make that for us
[08:15:24] <mojavelinux> sure would be a better use of our time than installing app servers
[08:15:38] <sbryzak> mojavelinux: are you running fedora?
[08:15:43] <mojavelinux> ubuntu
[08:15:50] <sbryzak> naughty!
[08:16:01] <Diablo-D3> 03:15:53,516 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/DiabloPool].[FacesServlet]] Servlet.service() for servlet FacesServlet threw exception: java.lang.OutOfMemoryError: PermGen space
[08:16:02] <Diablo-D3> 03:15:53,518 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/DiabloPool].[default]] Servlet.service() for servlet default threw exception: java.lang.OutOfMemoryError: PermGen space
[08:16:03] <Diablo-D3> ;_;
[08:16:11] <sbryzak> Diablo-D3: restart your server
[08:16:37] <mojavelinux> i think this is out of date
[08:16:38] <mojavelinux> SEAMINTL-12
[08:16:39] <jbossbot> jira [SEAMINTL-12] Bundle not found in beta1-as [Open (Unresolved) Bug, Major, Unassigned] https://issues.jboss.org/browse/SEAMINTL-12
[08:16:48] <mojavelinux> it refers to pete's AS zip
[08:16:54] <mojavelinux> I doubt that issue still exists
[08:16:59] <mojavelinux> plus, we use the stuff in seam booking
[08:17:27] <sbryzak> want to close it?
[08:17:50] <mojavelinux> SEAMPERSIST-35 should be done
[08:17:51] <jbossbot> jira [SEAMPERSIST-35] Deprecate SeamManaged [Pull Request Sent (Unresolved) Task, Major, Unassigned] https://issues.jboss.org/browse/SEAMPERSIST-35
[08:17:52] <mojavelinux> sure, I'll close that
[08:19:20] <mojavelinux> it will be interesting to see the count of how many issues were closed since the last stack release
[08:19:23] <mojavelinux> I bet it's over 100
[08:20:16] <mojavelinux> I thought we resolved SEAM-14
[08:20:17] <jbossbot> jira [SEAM-14] Figure out how to get ${project.version} replaces in ref guide and readme [Open (Unresolved) Task, Minor, Dan Allen] https://issues.jboss.org/browse/SEAM-14
[08:21:08] <sbryzak> yeah that should be fixed
[08:21:49] <mojavelinux> let's just make sure that QA checks there are no replacements left after the final dist build
[08:21:50] <mojavelinux> closed issue
[08:21:58] <mojavelinux> I saw the code in the module anyway tonight
[08:22:06] <mojavelinux> not all modules use the project version in the docs
[08:22:10] <mojavelinux> that's worth a separate issue later
[08:22:46] <mojavelinux> shane, you can remove this from all modules
[08:22:47] <mojavelinux>    <prerequisites>
[08:22:47] <mojavelinux>       <maven>3.0</maven>
[08:22:47] <mojavelinux>    </prerequisites>
[08:22:51] <mojavelinux> that's enforced by parent
[08:23:12] <sbryzak> sure
[08:24:45] <mojavelinux> i'm adding these small issues to 3.0.0.Final, but they are more of reminders as you are building the dist
[08:25:07] <sbryzak> no problem
[08:38:21] <nickarls> I think you can close SEAMINTL-33, it's probably a Weld issue
[08:38:23] <jbossbot> jira [SEAMINTL-33] Injections null when Bundles.get(String) is called [Reopened (Unresolved) Bug, Major, Ken Finnigan] https://issues.jboss.org/browse/SEAMINTL-33
[08:39:19] <mojavelinux> is it linked to a weld issue?
[08:39:27] <mojavelinux> probably should be linked when it is closed, just for reference
[08:40:12] <nickarls> it's related-tolinked
[08:40:37] *** daniel_hinojosa has quit IRC
[08:40:59] <jbossbot> git [persistence] push master 2688516.. Dan Allen SEAMPERSIST-30 rename test package
[08:41:00] <jbossbot> jira [SEAMPERSIST-30] Rename org.jboss.seam.persistence.transactions test package [Open (Unresolved) Task, Optional, Dan Allen] https://issues.jboss.org/browse/SEAMPERSIST-30
[08:41:00] <jbossbot> git [persistence] push master URL: http://github.com/seam/persistence/compare/f525e5d...2688516
[08:42:50] <mojavelinux> resolved and note added
[08:42:58] <mojavelinux> that would make a good compat test
[08:43:16] <mojavelinux> nik, would you be able to describe how to create a compat test for that scenario?
[08:43:28] <mojavelinux> all custom classes, not using seam intl
[08:43:38] <mojavelinux> if you can describe it, I can note it down to create it
[08:43:42] <mojavelinux> or if you have time to create it
[08:43:51] <mojavelinux> it should be easy in the compatibility module
[08:43:53] <mojavelinux> it's all setup for testing
[08:44:02] <mojavelinux> http://github.com/seam/compatibility
[08:44:09] <mojavelinux> easiest testing environment we've got so far :)
[08:44:31] <Diablo-D3> AAAAAAAAAAHHHHAHAHAHAHHA
[08:44:39] <Diablo-D3> sbryzak: IT WORKEZ
[08:44:49] <mojavelinux> nice!!!!!
[08:44:54] <mojavelinux> I picked off a couple more issues
[08:44:59] <Diablo-D3> well
[08:45:00] <Diablo-D3> kind of
[08:45:07] <mojavelinux> we are looking real good, for both final and in general w/ seam 3 issues
[08:45:17] <Diablo-D3> I go to google's openid auth page, come back, and it goes into a redir frenzy
[08:46:00] <mojavelinux> sbryzak: you may want to scan this https://issues.jboss.org/secure/IssueNavigator.jspa?mode=hide&requestId=12314289
[08:46:21] <mojavelinux> just to see if anything got left behind...not looking for features, but just to make sure we have it all cleaned up for what really did make it
[08:46:26] <mojavelinux> but it looks good to me so far
[08:46:28] <mojavelinux> first pass
[08:47:00] <mojavelinux> I'm toast
[08:47:15] <mojavelinux> later all...again, awesome awesome work
[08:47:19] <mojavelinux> many beers lie ahead
[08:54:16] <nickarls> mojavelinux: test case is in WELD-873
[08:54:18] <jbossbot> jira [WELD-873] Injections not working for certain bean methods [Open (Unresolved) Bug, Major, Unassigned] https://issues.jboss.org/browse/WELD-873
[08:54:29] <nickarls> Pete tried to add it but hudson didn't eat it for some reason
[09:03:01] <sbryzak> mojavelinux: i can't see that filter
[09:05:02] <Diablo-D3> sbryzak: okay so
[09:05:08] <Diablo-D3> I have a problem
[09:05:18] <Diablo-D3> nothing in OpenIdRelyingPartySpiImpl is ever called
[09:06:26] <sbryzak> Diablo-D3: hmm, is it identical to the one in the openid-rp example?
[09:06:37] <Diablo-D3> yes
[09:06:50] <Diablo-D3> except I added sysouts at the top of the two methods
[09:08:29] <Diablo-D3> the sysouts never trigger
[09:08:35] <sbryzak> Diablo-D3: set a breakpoint in OpenIdRpAuthenticationService.handleIncomingMessage()
[09:09:47] <jbossbot> git [rest] push master 0b91c6d.. Shane Bryzak SEAM-49
[09:09:48] <jbossbot> jira [SEAM-49] Seam distribution contains .gitignore files [Open (Unresolved) Bug, Minor, Shane Bryzak] https://issues.jboss.org/browse/SEAM-49
[09:09:48] <jbossbot> git [rest] push master f5370b4.. Shane Bryzak Merge remote branch 'origin/master'
[09:09:49] <jbossbot> git [rest] push master URL: http://github.com/seam/rest/compare/ab2f93f...f5370b4
[09:13:03] <Diablo-D3> goddamnit
[09:13:13] <Diablo-D3> sbryzak: why cant I just tell eclipse to open a goddamned class
[09:13:33] <sbryzak> what do you mean?
[09:13:59] <Diablo-D3> OpenIdRpAuthenticationService is in a jar.
[09:14:03] <Diablo-D3> one of several thousand jars.
[09:14:22] <sbryzak> ctrl-shift-t, start typing class name
[09:14:39] <sbryzak> if eclipse can't find the source, click the add source button
[09:14:48] <sbryzak> then point it to the source directory
[09:14:49] <Diablo-D3> grk
[09:14:55] <Diablo-D3> that shoudl be easier to find
[09:15:47] <sbryzak> Navigate menu -> Open Type
[09:15:56] * Diablo-D3 facepalms
[09:16:26] <Diablo-D3> okay, what am I looking for with this breakpoint
[09:16:35] <sbryzak> first, that it gets hit
[09:17:02] <sbryzak> secondly, you need to step through and see if it hits either of the openIdRelyingPartySpi method calls
[09:17:14] <sbryzak> should be line 107 or line 112
[09:17:45] <Diablo-D3> lets try 107 first
[09:17:57] <sbryzak> just set the breakpoint at the start of the method
[09:18:03] <sbryzak> then step through it with F6
[09:19:23] <Diablo-D3> it never hits the breakpoint
[09:19:32] <sbryzak> ok, we have a problem then
[09:20:09] <sbryzak> i'm wondering if the servlet is registered
[09:20:55] <Diablo-D3> well, I see org.openid4java.* spam in the log
[09:21:11] <sbryzak> try setting a breakpoint in OpenIdServlet.handleMessage
[09:22:34] <Diablo-D3> nope, didnt hit it
[09:22:54] <sbryzak> hmm, ok it's possible the servlet isn't registered
[09:23:28] <Diablo-D3> ... goddamnit.
[09:24:18] <sbryzak> one minute while i try to work out how it's registered
[09:24:37] <Diablo-D3> seriously, seam hates me :<
[09:25:23] <sbryzak> found it
[09:25:30] <sbryzak> it's configured with a web-fragment
[09:25:37] <sbryzak> which app server are you using?
[09:26:05] <Diablo-D3> jboss as 6
[09:26:18] <sbryzak> hmm, it should work then
[09:26:26] <sbryzak> try opening this url in a browser:
[09:27:11] <sbryzak> actually, give me a minute
[09:27:22] * Diablo-D3 gets a soda in the mean time
[09:27:28] <Diablo-D3> need more caffiene to deal with this
[09:28:36] <sbryzak> ok, whatever the url is for your application, add /openid/RP/foo to the end of it
[09:29:02] <sbryzak> so for example, the openid-rp example url would be www.openid-rp.com:8080/security-openid-rp/openid/RP/foo
[09:29:15] <sbryzak> that should give you a 404 error that says 'No service endpoint exists for this URL'
[09:29:24] <sbryzak> if you get that, you know the servlet is working
[09:31:35] * Diablo-D3 equips a +5 pepsi
[09:31:54] <Diablo-D3> capitalized RP?
[09:36:50] <sbryzak> Diablo-D3: yes
[09:37:39] <Diablo-D3> I think I have done something stupid
[09:37:57] <Diablo-D3> aaaaaaaargh
[09:39:59] <Diablo-D3> fuck
[09:40:09] <Diablo-D3> it was my fault
[09:40:16] <Diablo-D3> sbryzak: NOW it works.
[09:40:34] <Diablo-D3> my prettyfaces usage was a little too greedy
[09:47:36] <Diablo-D3> <rewrite trailingSlash="remove" redirect="301"/>
[09:47:36] <Diablo-D3>   <rewrite match="/(.*?)/" toCase="lowercase" redirect="301"/>
[09:47:41] <Diablo-D3> doomed
[09:50:19] <Diablo-D3> 04:50:20,700 INFO  [STDOUT] OpenIdRelyingPartySpiImpl loginSucceeded
[10:03:53] <Diablo-D3> sbryzak: so, after over 9000 seconds of fighting with seam, I have won
[10:10:55] *** bleathem_ has joined #seam-dev
[10:11:22] <jbossbot> git [examples] push master a455226.. Jozef Hartinger SEAM-62
[10:11:24] <jbossbot> jira [SEAM-62] Finish functional tests for seam-booking [Open (Unresolved) Task, Major, Jozef Hartinger] https://issues.jboss.org/browse/SEAM-62
[10:11:24] <jbossbot> git [examples] push master 7151567.. Dan Allen remove inherited blocks, including license
[10:11:24] <jbossbot> git [examples] push master 428b4c8.. Dan Allen update readme, test markdown syntax
[10:11:24] <jbossbot> git [examples] push master 0385306.. Dan Allen fix whitespace and bullets
[10:11:24] <jbossbot> git [examples] push master 4e26680.. Dan Allen minor
[10:11:24] <jbossbot> git [examples] push master 7e7b0d7.. Dan Allen update Seam modules to fix portability issues...
[10:11:25] <jbossbot> git [examples] push master 9b79f29.. Dan Allen add note about eclipselink persistence properties
[10:11:25] <jbossbot> git [examples] push master 78e52aa.. Dan Allen format source
[10:11:26] <jbossbot> git [examples] push master d1c85fa.. Dan Allen switch to CR2 versions
[10:11:26] <jbossbot> git [examples] push master 57fb8a8.. Dan Allen SOLDER-85 update to use repackaged annotations
[10:11:27] <jbossbot> jira [SOLDER-85] Better separation of i18n and logging concerns [Resolved (Done) Enhancement, Major, Dan Allen] https://issues.jboss.org/browse/SOLDER-85
[10:11:27] <jbossbot> git [examples] push master 821cade.. Dan Allen add note about known issue
[10:11:28] <jbossbot> git [examples] push master de098b0.. Dan Allen bugfixes...
[10:11:28] <jbossbot> git [examples] push master f571f51.. Shane Bryzak cleanup
[10:11:40] <jbossbot> git [examples] push master f368ec8.. Jozef Hartinger SEAM-62
[10:11:40] <jbossbot> git [examples] push master 8057fd0.. Jozef Hartinger SEAM-58
[10:11:41] <jbossbot> jira [SEAM-58] seam-booking - functional tests fail although the application works as expected [Open (Unresolved) Bug, Major, Jozef Hartinger] https://issues.jboss.org/browse/SEAM-58
[10:11:41] <jbossbot> git [examples] push master 246f67c.. Shane Bryzak Merge branch 'ftest-new' of https://github.com/jharting/seam-examples into jharting-ftest-new...
[10:11:42] <jbossbot> git [examples] push master URL: http://github.com/seam/examples/compare/4ded4b7...246f67c
[10:13:23] <jharting> sbryzak: shane, I screwed the rebase or something, I'll have to send you another pull request
[10:13:36] <jharting> sbryzak: ideally if we could revert that one
[10:13:43] <jharting> sbryzak: not sure if it's possible
[10:15:14] <sbryzak> oops,i already applied it
[10:15:51] <jharting> sbryzak: is it possible to remove those commits and force a push?
[10:15:57] <jharting> sbryzak: before anyone pulls?
[10:16:22] *** bleathem has quit IRC
[10:16:48] <Diablo-D3> nope you're already screwed
[10:17:05] <jbossbot> git [examples] push master 4e3aa9d.. Shane Bryzak fix conflict
[10:17:05] <jbossbot> git [examples] push master URL: http://github.com/seam/examples/compare/246f67c...4e3aa9d
[10:17:56] <sbryzak> i'm looking now
[10:18:19] <jharting> Diablo-D3: unless github forbids it, you can always push -f IMHO
[10:18:46] <Diablo-D3> its easier to just push a new patch that fixes it
[10:21:29] <sbryzak> jharting: the build seems ok
[10:23:00] <jharting> sbryzak: right, but the patch probably accidentally reverted a lot of things
[10:28:20] <jbossbot> git [examples] push master c1f0bdd.. Shane Bryzak Revert "fix conflict"...
[10:28:20] <jbossbot> git [examples] push master cdb7c73.. Shane Bryzak Revert "Revert "fix conflict""...
[10:28:20] <jbossbot> git [examples] push master URL: http://github.com/seam/examples/compare/4e3aa9d...cdb7c73
[10:28:39] <sbryzak> bah
[10:29:06] <jharting> sbryzak: do you think it would be possible to get us back to 4ded4b760040e5f0e530d0e8f82312c4404cdb88?
[10:29:40] <sbryzak> i can't see that commit
[10:30:19] <sbryzak> ah wait a minute
[10:30:52] <jharting> it's the last commit before the bunch of screwed up commits from the pull request
[10:35:09] <sbryzak> jharting: i need a list of commits you want to keep
[10:35:31] <sbryzak> jharting: http://pastebin.com/erkUNAmm
[10:38:07] <jharting> sbryzak: remove all commits from the pull request, I'll create another one
[10:40:31] <sbryzak> i'm not sure how to do that
[10:42:16] <sbryzak> actually, i don't think i should remove all commits
[10:43:01] <sbryzak> won't that remove the originals?
[10:43:25] <jharting> sbryzak: sec
[10:45:27] <sbryzak> from what i can see, the only affect it's had is to add your name to existing commits
[10:45:35] <sbryzak> i don't think that's a problem
[10:45:53] <sbryzak> e.g. https://github.com/seam/examples/commit/c0385f90a808212475539958b81385d1f6c04080
[10:45:54] <jbossbot> git [examples] c0385f9.. Shane Bryzak skip tests for release build
[10:49:22] <jharting> sbryzak: ok, running a diff it seems that the expected changes are in
[10:49:50] <jharting> sbryzak: it only screwed up the commit history as you said, and the pull request diff looks scary also https://github.com/seam/examples/pull/4/files#diff-34
[10:50:30] <sbryzak> that's a big web page
[10:50:45] <sbryzak> but i agree, HEAD looks fine
[11:02:41] <jharting> sbryzak: one last pull request https://github.com/seam/examples/pull/5 and SEAM-62 should be done
[11:02:43] <jbossbot> jira [SEAM-62] Finish functional tests for seam-booking [Open (Unresolved) Task, Major, Jozef Hartinger] https://issues.jboss.org/browse/SEAM-62
[11:05:01] <sbryzak> no problem, will do it in a minute
[11:06:37] <jharting> sbryzak: I'm going to be AFK till evening. There's one more issue assigned to me for 3.0.0.Final SEAMSERVLET-22 - I am not sure how critical it is to have the test in place - I can either work on it in the evening today (UTC) or actually test the fnctionality during 3.0.0.Final testing and commit the test afterwards
[11:06:38] <jbossbot> jira [SEAMSERVLET-22] Test Seam Servlet in an EAR with multiple web apps [Open (Unresolved) Feature Request, Major, Jozef Hartinger] https://issues.jboss.org/browse/SEAMSERVLET-22
[11:06:59] <sbryzak> jharting: no problem
[11:07:12] <sbryzak> i probably won't do the release until tomorrow evening anyway
[11:07:49] <jharting> sbryzak: ok
[11:07:58] *** jharting has quit IRC
[11:11:37] <jbossbot> git [examples] push master 1a6f441.. Jozef Hartinger SEAM-62
[11:11:38] <jbossbot> jira [SEAM-62] Finish functional tests for seam-booking [Resolved (Done) Task, Major, Jozef Hartinger] https://issues.jboss.org/browse/SEAM-62
[11:11:38] <jbossbot> git [examples] push master URL: http://github.com/seam/examples/compare/cdb7c73...1a6f441
[11:21:03] <Diablo-D3> http://www.mirah.org/
[11:21:05] <Diablo-D3> goddamnit
[11:21:11] <Diablo-D3> we dont need another goddamned jvm language
[11:21:15] <Diablo-D3> we already have like 5
[11:21:30] <Diablo-D3> oh fuck, this is even worse
[11:21:33] <Diablo-D3> its native ruby for jvm
[11:21:41] <Diablo-D3> (as opposed to jruby)
[11:40:19] *** jose_freitas has joined #seam-dev
[11:46:04] <sbryzak> jose_freitas: ping
[11:46:45] <jose_freitas> sbryzak: pong
[11:46:53] <sbryzak> i just got your pull request
[11:47:13] <sbryzak> both pom.xml and booking/pom.xml have windows carriage returns though
[11:47:27] <sbryzak> you'll need to fix that first before i apply it
[11:47:39] <jose_freitas> ok
[11:47:44] 
[11:47:52] <sbryzak> thanks :)
[11:48:08] <Diablo-D3> grrr
[11:48:20] <Diablo-D3> sbryzak: how do I call identity.logout from jsf
[11:48:40] <jose_freitas> this week has been a nightmare
[11:48:47] <Diablo-D3> just doing #{identity.logout} isnt enough
[11:48:57] <sbryzak> it isn't?
[11:48:57] <Diablo-D3> or rather, isnt the right thing
[11:49:05] <sbryzak> Diablo-D3: why, what's happening?
[11:49:17] <sbryzak> jose_freitas: what's happened this week?
[11:49:21] <Diablo-D3> 06:45:17,781 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/DiabloPool].[default]] Servlet.service() for servlet default threw exception: javax.el.ELException: /logout.xhtml: The class 'org.jboss.seam.security.org$jboss$weld$bean-jboss$classloader:id="vfs:$$$home$diablo$Workspace$$metadata$$plugins$org$jboss$ide$eclipse$as$core$JBoss_6$0_Runtime_Server1299437663993$deploy$DiabloPool$war"-ManagedBe
[11:49:22] <Diablo-D3> an-class_org$jboss$seam$security$IdentityImpl_$$_WeldClientProxy' does not have the property 'logout'.
[11:49:49] <sbryzak> show me your jsf
[11:50:08] <sbryzak> it looks like you're trying to access it as a property, not as an action method
[11:50:37] <Diablo-D3> maybe Ive misunderstood, but the internet seems to imply just doing that EL should work
[11:50:46] <Diablo-D3>    <ui:define name="body">
[11:50:46] <Diablo-D3>       Logging out... #{identity.logout}
[11:50:46] <Diablo-D3>    </ui:define>
[11:51:08] <sbryzak> you need to put it in a commandLink or something
[11:51:28] <Diablo-D3> how can I just force it to execute without anyone clicking on anything
[11:51:56] <sbryzak> how should it be invoked then?
[11:52:07] <Diablo-D3> by going to the page called logout
[11:52:18] <sbryzak> hmm, you could do it as a page action
[11:55:03] <Diablo-D3> actually, should I even do it this way?
[11:55:14] <Diablo-D3> a lot of sites have logout pages, but I dunno if thats the right thing to do
[11:55:30] <sbryzak> it's not really conventional
[11:55:44] <sbryzak> usually you would have a logout link
[11:55:46] <jose_freitas> sbryzak: I was giving a 40h training with cdi and seam + 4h normally working each day
[11:56:10] <Diablo-D3> sbryzak: well, the pages usually just say "you've been logged out" or something
[11:56:51] <sbryzak> Diablo-D3: you can still redirect to a page with a logout message, or just generate a FacesMessage that says 'You have logged out' or something to that effect
[12:00:09] *** aslak has joined #seam-dev
[12:02:33] <jose_freitas> sbryzak: ping
[12:02:42] <sbryzak> jose_freitas: pong
[12:02:49] <Diablo-D3> sbryzak: maybe Ill just go with redirecting to the front page
[12:02:54] <Diablo-D3> a lot of sites get away with that fine
[12:03:02] <sbryzak> Diablo-D3: sounds reasonable
[12:03:16] <jose_freitas> how can you see the carriage return through github?
[12:03:54] <sbryzak> i don't, i see it when i open the conflicted file
[12:10:21] <jose_freitas> hmm.
[12:11:01] 
[12:14:27] <jose_freitas> sbryzak: can you try it, please?
[12:14:37] <sbryzak> sure
[12:15:17] <sbryzak> have you created a new pull request?
[12:15:43] <jose_freitas> nope, I thought that it would update it automagically
[12:15:52] <jose_freitas> my pull request with my new push
[12:16:12] <sbryzak> ah, let me try
[12:16:16] <jose_freitas> yes, it updated it
[12:16:37] <jose_freitas> itself*
[12:16:50] <sbryzak> hmm, still has conflicts
[12:19:10] <jose_freitas> changed my workspace now to work with unix new line character
[12:19:46] <Diablo-D3> er, what jsf namespace is s
[12:19:46] <Diablo-D3> ?
[12:20:04] 
[12:20:08] <jose_freitas> anymore
[12:22:45] <sbryzak> jose_freitas: it looks like you made your changes to a really old version of booking/pom.xml
[12:23:04] <sbryzak> it still uses arquillian Alpha3
[12:23:25] <sbryzak> i don't think i can fix this, there's too many conflicts
[12:24:00] <jose_freitas> actually it does not have too many changes on pom.xml
[12:24:11] <jose_freitas> on parent I just changed the bom.version
[12:24:28] <sbryzak> ok, i'm going to overwrite it with the current content in HEAD
[12:25:14] <jose_freitas> and on booking, I just removed the <version>SNAPSHOT thing to get the versions from parent
[12:25:30] <jbossbot> git [examples] push master fc2a239.. joserodolfofreitas changed break line character
[12:25:31] <jbossbot> git [examples] push master d7682b9.. Shane Bryzak Merge branch 'master' of https://github.com/joserodolfofreitas/examples into jose...
[12:25:31] <jbossbot> git [examples] push master URL: http://github.com/seam/examples/compare/1a6f441...d7682b9
[12:25:45] <sbryzak> ok, i think i got it merged cleanly
[12:25:55] <sbryzak> make sure you update your local copy before you do any more work
[12:26:13] <sbryzak> actually, the build is failing now
[12:26:23] <sbryzak> you must have made some changes to the pom
[12:27:30] <sbryzak> fixed it
[12:27:32] <jbossbot> git [examples] push master 3719126.. Shane Bryzak add missing dependencies
[12:27:33] <jbossbot> git [examples] push master URL: http://github.com/seam/examples/compare/d7682b9...3719126
[12:28:39] <jose_freitas> sbryzak: https://github.com/joserodolfofreitas/examples/commit/880fa40566873a48a00625a0d504f542eadea186
[12:28:40] <jbossbot> git [examples] 880fa40.. joserodolfofreitas added cross validation with InputElement to checkInDate and...
[12:28:44] <jose_freitas> that were my real changes
[12:28:51] <jose_freitas> version and added security and config modules
[12:29:00] <jose_freitas> forgot to mention those
[12:29:46] <jose_freitas> normally I get new versions, actually I work with origin version and just commit with force update to my fork
[12:29:54] <sbryzak> the repository is already configured in the parent
[12:30:10] <jose_freitas> ok
[12:30:32] <sbryzak> looks like all the SNAPSHOT versions have been fixed
[12:30:50] <Diablo-D3> oh, its the seam tag library
[12:30:53] <Diablo-D3> does seam 3 have this?
[12:31:12] <sbryzak> jose_freitas: actually i didn't add the seam-config dependency.. i'm assuming it's not being used yet?
[12:31:30] <jose_freitas> sbryzak: I use it to config the authenticator for seam-security
[12:32:02] <sbryzak> np, adding it now
[12:32:12] <jbossbot> git [examples] push master 2a9767a.. Shane Bryzak add seam-config dependency
[12:32:12] <jbossbot> git [examples] push master URL: http://github.com/seam/examples/compare/3719126...2a9767a
[12:32:23] <sbryzak> i think that should be good now
[12:32:50] <sbryzak> Diablo-D3: which tag are you talking about?
[12:33:10] <Diablo-D3> the s namespace
[12:33:27] <jose_freitas> thanks, that were problematic.
[12:33:31] <Diablo-D3> its apparently the seam tag library
[12:33:34] <jose_freitas> gotta get some breakfast now
[12:34:20] <sbryzak> Diablo-D3: which tag are you trying to use though?
[12:34:55] <Diablo-D3> s:link
[12:35:09] <Diablo-D3> but I think Ill just use forms h:forms to do it to get the POST out of it
[12:35:09] <sbryzak> that's a seam 2 tag
[12:35:21] <sbryzak> seam 3 tags are here: http://docs.jboss.org/seam/3/latest/reference/en-US/html/components.html
[12:55:31] *** aslak has quit IRC
[13:00:40] *** gmorling1 has joined #seam-dev
[13:02:47] <gmorling1> sbryzak: ping
[13:05:37] *** bitshuffler has joined #seam-dev
[13:33:07] <sbryzak> gmorling1: pong
[13:33:22] <gmorling1> hi.
[13:33:45] <sbryzak> hey Gunnar
[13:33:59] <gmorling1> There is one issue from Seam Validation which I think would make sense to include in 3.0 Final: SEAMVALIDATE-14
[13:34:01] <jbossbot> jira [SEAMVALIDATE-14] java.lang.NullPointerException at InjectingConstraintValidatorFactory.java:47 [Open (Unresolved) Bug, Major, Gunnar Morling] https://issues.jboss.org/browse/SEAMVALIDATE-14
[13:34:35] <gmorling1> this is about using the injecting factory but not retrieving the javax.validation.Validator via CDI
[13:34:37] <sbryzak> is it an easy fix?
[13:34:51] <gmorling1> in this scenario the BM is not injected
[13:35:25] <jbossbot> git [validation] 4105ada.. Gunnar Morling SEAMVALIDATE-14: Trying to retrieve BM from JNDI, if none was injected.
[13:35:26] <jbossbot> jira [SEAMVALIDATE-14] java.lang.NullPointerException at InjectingConstraintValidatorFactory.java:47 [Open (Unresolved) Bug, Major, Gunnar Morling] https://issues.jboss.org/browse/SEAMVALIDATE-14
[13:35:45] <gmorling1> there is just one question I got:
[13:38:01] <gmorling1> i changed the factory to derive from BeanManagerAware (from Solder). That way the BM is either obtained via DI or as fallback from JNDI, if the BM was not injected (which happens for instance if the validator is retrieved by JSF using the BV API directly). Now one could fall back to the standard factory if also via JNDI was no BM available. But I'd prefer to throw an exception as using the...
[13:38:02] <gmorling1> ...injecting factory and having no BM available at all makes not really sense. WDYT?
[13:40:07] <sbryzak> hmm, trying to get my brain to understand the problem
[13:40:50] <gmorling1> ok, i should give you some background :-)
[13:43:09] <gmorling1> InjectingConstraintValidatorFactory provides DI services to constraint validator implementations. To do so ICVF needs to get hold of a bean manager. So far I had considered the case that javax.validation.Validator (which is what BV users work with at the end) was retrieved via @Inject. In this scenario Seam Validation injected the BM into ICVF and everything is good.
[13:43:50] <sbryzak> with you so far
[13:44:34] <gmorling1> now this issue deals with the case where j.v.Validator is not retrieved using @Inject but by invoking Validation.buildDefaultFactory().getValidator(). In this case no BM will be injected into ICVF which causes the NPE.
[13:45:36] <gmorling1> I therefore changed ICVF to derive from BeanManagerAware. That way as fallback the BM is retrieved from JNDI. Now you can use ICVF also if j.v.Validator is not obtained via CDI.
[13:45:52] <sbryzak> are you using getBeanManager() to get the BeanManager?
[13:45:57] <gmorling1> yes
[13:46:30] <sbryzak> ok, that all sounds good so far
[13:47:20] <gmorling1> now it only could happen that no BM is available at all. then ICVF could call the standard constraint factory as fallback (which of course provides no DI services), but I prefer to throw an exception in that case.
[13:47:31] <sbryzak> i can't think of any other circumstances where BeanManager wouldn't be available
[13:48:25] <gmorling1> because either you have a BM available, then you can use ICVF, or you haven't one (if there is none in JNDI for whatever reasons), then you can't use ICVF. I think failing with a clear exception is the right thing
[13:49:19] <sbryzak> i guess so
[13:49:28] <sbryzak> but there should always be a BeanManager
[13:50:31] <gmorling1> generally yes. the only situation I could think of would be using Seam Validation on Java SE
[13:51:17] <gmorling1> and generally it is preferrable to obtain the validator using @Inject anyways, and in this case JNDI is not needed at all
[13:51:23] <sbryzak> in that environment you can still use Weld
[13:51:31] <sbryzak> and Seam is a set of CDI extensions
[13:51:37] <sbryzak> so the BM should always be there
[13:52:03] <gmorling1> ok, i didn't know that weld provides the BM in JNDI also on plain SE
[13:53:19] <gmorling1> this issue shows that it was better if JSF would retrieve its j.v.Validator via CDI
[13:53:25] <sbryzak> well it will be injectable
[13:53:31] <gmorling1> are at least try to if CDI is around
[13:53:41] <gmorling1> are=or
[13:55:21] <gmorling1> well, thanks for listening to my mumblings :-) for when is the 3.0 Final code freeze planned?
[13:55:54] <sbryzak> we've got a little more documentation to write
[13:55:58] <sbryzak> but tomorrow night i'll start on the release
[13:56:49] <gmorling1> cool, that sounds great :-) Any news on the Weld 1.1.1 release?
[13:57:50] <sbryzak> no, i've been trying to get a hold of ales
[13:59:14] <sbryzak> i really want him to do a release before we do
[13:59:54] <gmorling1> Yes, that would definitely be way better. the other way around makes probably a bad user experience
[14:01:03] <gmorling1> Ok, Shane. I'll push the change for SEAMVALIDATE-14 to master then. Thanks again for your time.
[14:01:05] <jbossbot> jira [SEAMVALIDATE-14] java.lang.NullPointerException at InjectingConstraintValidatorFactory.java:47 [Coding In Progress (Unresolved) Bug, Major, Gunnar Morling] https://issues.jboss.org/browse/SEAMVALIDATE-14
[14:16:23] *** aslak has joined #seam-dev
[14:16:23] *** aslak has quit IRC
[14:16:23] *** aslak has joined #seam-dev
[14:58:59] * Diablo-D3 changes -Xms128m -Xmx512m -XX:MaxPermSize=256m to "-Xms256m -Xmx1024m -XX:MaxPermSize=512m -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled
[14:59:50] <Diablo-D3> hrm, apparently eclipse overrides tose settings
[15:02:11] *** lincolnthree has joined #seam-dev
[15:02:30] <lincolnthree> "boo!"
[15:03:37] <Diablo-D3> lincolnthree: hey you
[15:03:45] <Diablo-D3>    <rewrite match="(!(faces|openid))" trailingSlash="remove" toCase="lowercase" redirect="301"/>
[15:03:54] <Diablo-D3> make that regex work
[15:04:17] <Diablo-D3> Ive been trying to figure out how to do that for the past half hour, and it just doesnt wanna work
[15:04:29] <lincolnthree> try putting .* .* around your pattern
[15:04:42] <Diablo-D3> erm, at which places?
[15:05:03] <lincolnthree> <rewrite match="(.*!(faces|openid)).*" trailingSlash="remove" toCase="lowercase" redirect="301"/>
[15:05:10] <lincolnthree> oh
[15:05:12] <lincolnthree> wait
[15:05:14] <lincolnthree> lol
[15:05:16] <lincolnthree> sorry
[15:05:19] <lincolnthree> you can't use !
[15:05:24] <lincolnthree> it's a regex :)
[15:05:24] <Diablo-D3> why not?
[15:05:27] <lincolnthree> here:
[15:05:54] <lincolnthree> http://ocpsoft.com/opensource/guide-to-regular-expressions-in-java-part-2/
[15:05:56] <lincolnthree> http://ocpsoft.com/opensource/guide-to-regular-expressions-in-java-part-1/
[15:06:16] <Diablo-D3> in perl I think I _can_ actually do it
[15:06:23] <Diablo-D3> lincolnthree: also, putting ? infront of ! doesnt make it work
[15:31:56] <Diablo-D3> going to bed, night all
[15:36:34] *** Diablo-D3 has quit IRC
[16:13:08] *** gmorling1 has quit IRC
[17:13:37] *** gastaldi has joined #seam-dev
[17:13:57] <gastaldi> hey !
[17:14:46] <gastaldi> so we are 3 to go huh ?
[17:22:05] *** gastaldi has quit IRC
[17:46:03] *** hugod_ has quit IRC
[17:50:26] *** lincolnthree has quit IRC
[17:50:44] *** hugod_ has joined #seam-dev
[17:50:49] *** lincolnthree has joined #seam-dev
[17:51:30] *** rruss has joined #seam-dev
[17:56:57] *** wdrai has joined #seam-dev
[18:21:37] <bleathem_> anyone around?
[18:22:02] <bleathem_> I've got a ViewConfig idea I want to bounce around...
[18:22:48] <bleathem_> What if, instead of providing the view pattern in a @ViewPattern annotation, we rather make it a property of the enum itseld via a constructor.
[18:23:16] <bleathem_> that way we can use the enum itself to control Faces navigation
[18:25:14] <bleathem_> ...
[18:25:38] <bleathem_> or maybe we can still do that by using reflection to set the propery of the enum
[18:26:39] <bleathem_> still I'll throw out a couple pasties to chew on:
[18:26:57] <bleathem_> using the @ViewPattern annotation: http://pastie.org/1718661
[18:27:19] <bleathem_> using enum constructor: http://pastie.org/1718670 (constructor not implemented)
[18:27:52] <bleathem_> that will probably be the bit that kills my idea - the application developer would have to implement the constructor
[18:28:47] <bleathem_> whereas if we require the developer to implement an interfaces, that specifies a setViewId method for an enum value
[18:29:29] <bleathem_> then we can programatically set that viewId with what is in the @ViewPattern annotation
[18:29:32] <bleathem_> ...
[18:30:09] <bleathem_> so nevermind
[18:30:22] <bleathem_> thanks for listening jbossbot!
[18:30:26] <bleathem_> ls
[18:38:39] <rruss> bleathem_: I heard as well, but couldn't provide any constructive input ;)
[18:39:37] *** rruss has quit IRC
[18:48:16] *** bitshuffler has quit IRC
[18:51:31] <bleathem_> Here's another thought:
[18:53:30] <bleathem_> @LoginViewId if we did the above enum/@ViewPattern, we could have @LoginViewId refernece another enum value, rather than a string
[18:54:05] <bleathem_> we could also add a @Navigationrule(fromOutcome=..., fromAction=...) and provide a type safe faces-config.xml
[18:54:07] <bleathem_> ...
[18:54:21] <bleathem_> I smell a few jiras coming on!
[18:58:30] <bleathem_> FYI: I'm reading Ed Burns' JSF book, to learn about creating components, so my head is entirely in the JSF space right now
[19:09:03] <jose_freitas> that book is a master piece
[19:09:23] <jose_freitas> i
[19:09:40] <jose_freitas> btw, it would be really nice to control faces navigation through some king of annotation
[19:10:07] 
[19:10:37] <jose_freitas> cause what we call controller in the MVC architecture should be the faces config
[19:12:20] <jose_freitas> ops, faces servlet
[19:12:39] <jose_freitas> would this annotation be located at business beans?
[19:13:51] <bleathem_> This place has life afterall!
[19:13:54] <bleathem_> hey jose_freitas
[19:13:59] <jose_freitas> hey =)
[19:14:11] <bleathem_> I'm talking about annotations in the @ViewConfig interface
[19:14:19] <bleathem_> on the view enums
[19:14:38] <bleathem_> Where we currently specify security and trnsactional behaviour
[19:14:50] <bleathem_> We plan on putting url-rewtiting there too
[19:15:08] <bleathem_> I'm thinking a lot of what is in the faces-config can be included in thsi @ViewConfig
[19:15:31] <bleathem_> to provide a central typesafe configuration for all your view hadnling needs
[19:15:32] <jose_freitas> interesting, and using the elEvaluator of solder we could use even navigation conditions
[19:15:40] <bleathem_> yeah!
[19:15:44] <jose_freitas> the same way navigation rules from faces-config
[19:15:55] <bleathem_> exactly the same
[19:16:05] 
[19:16:06] <bleathem_> we'd have to get the precedence right
[19:16:30] <bleathem_> I imagine the faces-config.xml would override our @ViewConfig stuff
[19:16:40] <bleathem_> but that's an implementation detail
[19:17:23] <bleathem_> And since the ViewConfigStore is meant to be configured by multiple sources
[19:17:41] <bleathem_> we can look at configuring some of this stuff in other places too
[19:17:51] <bleathem_> such as the f:metadata
[19:18:03] <bleathem_> or perhaps a groovy DSL
[19:18:22] <bleathem_> or we could provide an xml config for the sadistic devs :D
[19:19:05] <bleathem_> But the first focus is going to be the @ViewConfig
[19:19:33] <bleathem_> I've created a jira component called "View Configuration" to track all this stuff
[19:24:42] <jose_freitas> nice
[19:24:50] <jose_freitas> I actually was thinking about this
[19:25:04] <jose_freitas> those navigation rules
[19:25:30] <jose_freitas> cause when we close JSF and EJB
[19:25:35] <jose_freitas> someone has to make the control
[19:26:24] <jose_freitas> I believe that if we make controlling (with implicit navigation) over an EJB breaks the feature that EJB provides business services
[19:26:44] <jose_freitas> so the way of doing it should be with navigation rules
[19:27:25] 
[19:27:37] <bleathem_> true
[19:27:53] <bleathem_> sorry, true not to yor ability to express yourself!
[19:27:58] <bleathem_> but to what you said!
[19:28:00] <bleathem_> lol
[19:28:02] <jose_freitas> lol
[19:28:06] <bleathem_> that was bad timing...
[19:28:10] <jose_freitas> I was rewritting it
[19:28:14] <bleathem_> I don't think one needs to relegate EJBs to the business layer
[19:28:18] <bleathem_> it's just a technology
[19:28:30] <bleathem_> rather an application should have a service providing layer
[19:28:40] <bleathem_> and it doesn't all have to be EJBs either
[19:28:50] <bleathem_> Use the tech for the job that is required
[19:29:00] *** rruss has joined #seam-dev
[19:29:01] <bleathem_> and seperate concerns logically, rather than with tech
[19:29:05] *** rruss has quit IRC
[19:29:05] *** rruss has joined #seam-dev
[19:29:38] <bleathem_> hey rruss, thanks for letting me know I was heard by someone earlier!
[19:29:49] <jose_freitas> the thing is that I believe that if the EJB provides services freely from view or controlling issues, it could provide services for different clients, example web and an IPAD
[19:30:23] <bleathem_> right, it makes a lot of sense to provide a service layer
[19:30:31] <bleathem_> but it doesn't have to be coupled to EJB tech
[19:30:33] <jose_freitas> do you think that ejb today are that lightweight so we could use it freely?
[19:30:47] <bleathem_> use the EJB if it helps in the service layer, but also use it if it helps in other layers
[19:30:57] <bleathem_> Yes, I do
[19:31:14] <jose_freitas> but why one should use ejb to control app flow for example?
[19:31:19] <bleathem_> but I've never written "web-scale" applications
[19:31:38] <jose_freitas> normally ejb is used when someone needs transaction or clustering
[19:31:48] <bleathem_> if you need the features that come with the EJB, such as Tx management, etc
[19:31:51] <bleathem_> then use it
[19:31:57] <bleathem_> if you don't then don't use an EJB
[19:32:08] 
[19:32:18] <jose_freitas> perfect
[19:32:29] <jose_freitas> but the thing is, imagine that in a wizard flow
[19:32:34] <bleathem_> but it doesn't have to be confined to the service layer
[19:32:41] <jose_freitas> using conversation
[19:33:04] <jose_freitas> where we really need transaction only on the last phase
[19:33:46] <bleathem_> Have you seen Adam biens solution for using the SFSB's extended persistence context in the view layer?
[19:33:53] <jose_freitas> are you going to use a ConversationScoped with an stateful EJB ? or with a normal webbean and for the last phase use an ejb?
[19:34:03] <bleathem_> it's a good example of using EJBs in a non-service providing fashion
[19:34:14] 
[19:34:24] <bleathem_> it's in is JavaEE 6 patterns book
[19:34:24] <jose_freitas> is it a book? or a web link?
[19:34:33] <jose_freitas> oh, ok
[19:34:50] <bleathem_> It might also be in one of his blog posts
[19:34:54] <bleathem_> he blogs *a lot*
[19:35:45] <bleathem_> TL DR; The tech in EJB's make it a good solution for providing the service layer, but the tech can also be useful elsewhere
[19:36:05] <jose_freitas> what is TL DR?
[19:36:13] <bleathem_> Too Long, Didn't Read
[19:36:19] <bleathem_> a summary
[19:36:21] <jose_freitas> ok
[19:36:43] *** lincolnthree has quit IRC
[19:36:44] <jose_freitas> you meant that the book is too long? or my question?
[19:37:01] <bleathem_> sorry, I just wanted to summarize the conversation
[19:37:39] <jose_freitas> np
[19:37:50] <jose_freitas> I guess that sometimes it could be hard reading what I write
[19:37:56] <jose_freitas> sorry
[19:38:15] <bleathem_> no, you are perfectly clear!
[19:38:29] <bleathem_> Unless you didn't mean what I think you meant...
[19:39:01] <jose_freitas> hahaha
[19:39:20] <bleathem_> anyways, I'm going to get back to Ed's book.
[19:39:30] <jose_freitas> ok
[19:39:31] <bleathem_> I want to write a component by the end of the day
[19:39:37] <jose_freitas> man, adam biens has 860 post!!
[19:39:41] <bleathem_> lol
[19:39:55] <bleathem_> He's a great Java EE 6 advocate
[19:40:06] <bleathem_> really insightful things to say
[19:40:26] *** bleathem_ is now known as bleathem
[19:40:39] <jose_freitas> btw, just got some time today, sorry for not ending the p:input and the SEAMFACES-101
[19:40:42] <jbossbot> jira [SEAMFACES-101] First request in the short.ly example returns weird action URL due to a bug in prettyfaces on JBossAS 6 [Resolved (Done) Bug, Minor, Brian Leathem] https://issues.jboss.org/browse/SEAMFACES-101
[19:40:59] <jose_freitas> this week has been heelish
[19:40:59] <bleathem> no worries, it'll land in Faces when it lands
[19:41:09] <bleathem> I'm sure we'll have a point release pretty quick
[19:41:19] <bleathem> if you want to target that
[19:42:10] <jose_freitas> nice
[20:19:29] *** bitshuffler has joined #seam-dev
[20:25:09] *** jharting has joined #seam-dev
[20:29:59] <jbossbot> git [solder] push master 39cf639.. Dan Allen add book info to refguide
[20:29:59] <jbossbot> git [solder] push master URL: http://github.com/seam/solder/compare/be2da01...39cf639
[20:36:47] *** rruss has quit IRC
[20:38:44] <mojavelinux> setting up the jboss-logging-tools in the project would be an *excellent* forge plugin
[20:38:46] <mojavelinux> like super excellent
[20:38:50] <mojavelinux> and super easy
[20:44:16] *** bitshuffler has quit IRC
[20:48:47] <jbossbot> git [dist] push master f814cac.. Dan Allen add solder preface; rearrange; fix link
[20:48:48] <jbossbot> git [dist] push master URL: http://github.com/seam/dist/compare/2bd880f...f814cac
[20:49:04] <jbossbot> git [solder] push master e4992d7.. Dan Allen fix link
[20:49:04] <jbossbot> git [solder] push master URL: http://github.com/seam/solder/compare/39cf639...e4992d7
[20:54:58] *** lincolnthree has joined #seam-dev
[20:59:21] <mojavelinux> bleathem: I like your idea of using the pattern in the constructor of the enum...that looks much simpler
[20:59:46] <mojavelinux> i'd like to brainstorm this who view config thing a bit more once we get some feedback, just because I know we can do some more fine tuning
[20:59:57] <mojavelinux> also, I think we need to grab the big picture like url rewriting and page actions
[21:00:12] <mojavelinux> basically incorporating that into what we've started with, or what you've started with ;)
[21:00:35] <mojavelinux> we may need a design document with some sample scenarios all together so we can see the bigger picture
[21:00:48] <mojavelinux> but I would like to totally remove the reliance on faces-config.xml for navigation
[21:01:00] <mojavelinux> and even on pretty-config.xml for url rewriting
[21:01:06] <mojavelinux> even though underneath we will use them
[21:01:10] <mojavelinux> we are just consolidating the config
[21:01:38] <mojavelinux> so perhaps the best place to start is with the use cases, so we cover the various needs
[21:01:48] <mojavelinux> then fill in the details with example configs, and see what we are missing
[21:02:02] <mojavelinux> btw, I am okay with saying that the view config is a beta feature, even in Seam 3 final
[21:02:18] <mojavelinux> we needed to include it because the developer needed configuration, couldn't live without it
[21:02:28] <mojavelinux> but we aren't done with it yet and we are certainly looking for peer feedback
[21:03:19] *** lincolnthree has quit IRC
[21:33:02] <bleathem> mojavelinux I'm accumulating a collection of jira issues relating to the view configuration
[21:33:06] <bleathem> you can view them here:
[21:33:08] <bleathem> https://issues.jboss.org/browse/SEAMFACES/component/12313760
[21:33:42] <bleathem> While not a design document per se, it is a seed of such a document
[21:33:48] <mojavelinux> most excellent. definitely is starting to look like a hammer ;)
[21:33:54] <mojavelinux> indeed, it's a good way of doing it
[21:34:15] <bleathem> I'll update the jira issues with use cases, to be more clear
[21:34:16] <mojavelinux> tracking it
[21:34:33] <bleathem> You're right though, we need feedback on the feature
[21:34:42] <mojavelinux> yeah, though I might still hack up something on the whiteboard if I have some use cases to sketch out, then just link into the jiras
[21:35:04] <bleathem> sure - I've still got to get used to the whiteboard concept
[21:35:19] <bleathem> it's not what comes first to mind, but that's a familiarity thing
[21:37:53] <bleathem> The whiteboard has the benefit of exposing the "brainstorm" to the world
[21:38:03] <bleathem> and potentially roping in more feedback
[21:38:33] <bleathem> jira does tend to be a bit more buried that way
[21:38:44] <bleathem> especially with a large number of open issues like Faces has
[21:52:21] *** daniel_hinojosa has joined #seam-dev
[22:05:02] <mojavelinux> another way to go about it is to write brainstorm blogs
[22:05:08] <mojavelinux> that show use case scenarios
[22:05:15] <mojavelinux> that beats the whiteboard because it's temporal
[22:05:23] <mojavelinux> people expect it's a wip, not a final picture
[22:05:36] <mojavelinux> so perhaps use your blog to feel out some scenarios
[22:05:47] <mojavelinux> but what I think is really missing at this point are some concrete scenarios
[22:05:51] <mojavelinux> okay, gotta run
[22:07:00] <bleathem> good call - the start of the week is busy for me, but I'll blog some scenarios nearer the end of the week.
[22:09:13] <bleathem> Well, I'll start with one blog, timed with the Seam 3 release, where I showcase the @ViewConfig as it is so far
[22:42:47] *** jharting has quit IRC
[22:56:03] <jose_freitas> bleathem: Adam bien blog is pure gold
[22:56:24] <jose_freitas> thanks
[23:11:12] *** jose_freitas has quit IRC
[23:13:46] *** Diablo-D3 has joined #seam-dev
[23:14:28] <daniel_hinojosa> good afternoon
[23:14:39] <bleathem> 'tis a good one
[23:14:42] <bleathem> nice and sunny over here
[23:14:56] <bleathem> stuck behind this glow box tho :|
[23:15:43] *** gmorling1 has joined #seam-dev
[23:25:19] *** daniel_hinojosa has quit IRC
[23:25:40] <jbossbot> git [validation] push master 610a9a5.. Gunnar Morling SEAMVALIDATE-14: Upgrading to Arquillian 1.0.0.Alpha5
[23:25:42] <jbossbot> jira [SEAMVALIDATE-14] java.lang.NullPointerException at InjectingConstraintValidatorFactory.java:47 [Pull Request Sent (Unresolved) Bug, Major, Gunnar Morling] https://issues.jboss.org/browse/SEAMVALIDATE-14
[23:25:43] <jbossbot> git [validation] push master 4105ada.. Gunnar Morling SEAMVALIDATE-14: Trying to retrieve BM from JNDI, if none was injected.
[23:25:43] <jbossbot> git [validation] push master URL: http://github.com/seam/validation/compare/702a1bc...4105ada
[23:54:07] <Diablo-D3> hrm
[23:57:28] *** lincolnthree has joined #seam-dev
[23:59:18] <Diablo-D3> hey lincolnthree
[23:59:51] <Diablo-D3> shouldnt .*(?!(faces|openid).* work?





top