[00:01:47] *** lightguard_jp has quit IRC
[00:07:32] *** bleathem has quit IRC
[00:09:57] <jbossbot> git [servlet] push master 5750bf9.. Dan Allen temporary workaround to get typed loggers working on glassfish 3.1
[00:09:58] <jbossbot> git [servlet] push master ed31721.. Dan Allen actually commit the files mentioned in the last commit
[00:09:58] <jbossbot> git [servlet] push master c80b635.. Dan Allen typed logger isn't so broken, reenable
[00:09:58] <jbossbot> git [servlet] push master e870bbe.. Dan Allen only use extension on glassfish (hack)
[00:09:58] <jbossbot> git [servlet] push master 2c1a471.. Dan Allen detect glassfish and Weld version; format
[00:09:58] <jbossbot> git [servlet] push master URL: http://github.com/seam/servlet/compare/2dda4fd...2c1a471
[00:11:51] *** wdrai has joined #seam-dev
[00:22:09] *** daniel_hinojosa has quit IRC
[00:43:26] *** balunasj has quit IRC
[00:43:37] *** tsurdilo has quit IRC
[00:45:07] *** wdrai has left #seam-dev
[00:50:28] *** frgomes__ has joined #seam-dev
[00:53:08] <jbossbot> git [servlet] push master 25eb3d6.. Dan Allen update solder version
[00:53:08] <jbossbot> git [servlet] push master URL: http://github.com/seam/servlet/compare/2c1a471...25eb3d6
[00:53:56] *** daniel_hinojosa has joined #seam-dev
[00:56:11] <jbossbot> git [dist] push master 536b64d.. Dan Allen add solder-tooling
[00:56:11] <jbossbot> git [dist] push master URL: http://github.com/seam/dist/compare/8e601fd...536b64d
[00:56:35] *** daniel_hinojosa has quit IRC
[00:57:06] *** daniel_hinojosa has joined #seam-dev
[01:04:22] <jbossbot> git [examples] push master d5932ae.. Dan Allen switch to CR2 versions
[01:04:22] <jbossbot> git [examples] push master URL: http://github.com/seam/examples/compare/81c6617...d5932ae
[01:04:33] <mojavelinux> okay, booking can now be used without having to compile anything special first
[01:04:49] <mojavelinux> it still has snapshot deps on servlet and faces...those should be resolved as soon as they have CR2 out
[01:04:54] <frgomes__> mojavelinux: Hi Dan
[01:05:16] <mojavelinux> hey frgomes__
[01:05:22] <mojavelinux> saw your e-mail
[01:05:40] <frgomes__> oh.. ok :) I was about to tell you about it :)
[01:06:14] <frgomes__> I've downloaded jbpm from https://github.com/seam/jbpm
[01:06:35] <mojavelinux> basically, we don't know at the moment, but you reminded us to make it an action item to find out. I'll get in touch with shane and see if we can get some concrete plans to communicate
[01:06:38] <frgomes__> I've added some repositories to pom.xml but it still does not build. I'm trying to see some documentation.
[01:06:47] <mojavelinux> but atm, we have no one on the integration, afaik
[01:06:57] <mojavelinux> i think it's an empty module
[01:07:06] <mojavelinux> a placeholder for what awesome things will go there in the future ;)
[01:07:10] <mojavelinux> looking at it on the bright side
[01:07:11] <frgomes__> Could you please send me your settings.xml ... without your passwords, please :)
[01:07:18] <mojavelinux> you shouldn't need that
[01:08:17] <mojavelinux> there's no code to build
[01:08:20] <mojavelinux> in that module
[01:08:23] <frgomes__> well ... if it is empty... I dont have anything to care about atm...
[01:08:37] <mojavelinux> :)
[01:08:53] <frgomes__> ok. thanks a lot for your time, anyway :)
[01:08:54] <mojavelinux> yeah...we've gotten just about every other technology in progress in seam 3, but that is the one hole we currently have
[01:09:01] <mojavelinux> but, we will be in touch with the jbpm team
[01:09:06] <mojavelinux> and make sure things are moving very soon
[01:09:15] <mojavelinux> thanks for reminding me
[01:09:38] <frgomes__> basically, I'm interested on integrating jBPM in a web application. I'm not a web developer, so I'd like to count on code generation tools, etc.
[01:10:51] <frgomes__> Obviously at a certain point I will have to play with GWT or something. Well... there's no other way... isn't it?
[01:11:25] <frgomes__> Thanks a lot :)
[01:11:29] <mojavelinux> you could use seam 2
[01:11:40] <mojavelinux> but that's jbpm 3
[01:12:18] <mojavelinux> to use jbpm 5, well, I can't really give you an answer because I don't know yet...but things definitely will happen very soon, you can count on that much
[01:12:28] <frgomes__> do you know if jBPM3 understands beanshell scripts ?
[01:12:42] <mojavelinux> yep
[01:12:45] <mojavelinux> pretty sure it does
[01:13:02] <mojavelinux> but, better to ask on #jbpm
[01:13:21] <frgomes__> ok, thanks a lot! :)
[01:13:26] <mojavelinux> jbpm is not really my specialty, I know it just enough to be dangerous :)
[01:13:50] <frgomes__> you know a lot better than me, I'm afraid :)
[01:14:47] <frgomes__> I will have a look on it. Thanks a lot. You helped me a lot :)
[01:15:03] <mojavelinux> you bet. hey, at least I prevented you from chasing ghosts :)
[01:16:27] <frgomes__> yes, definitely!
[01:16:42] <frgomes__> I was trying to build a ghost, then... :)
[01:17:50] <mojavelinux> i love commits from stuartdouglas like this: Remove O(n^2) behaviour in BeanManagers
[01:17:56] <mojavelinux> that should be your signature stuartdouglas
[01:18:01] <mojavelinux> you just make shit faster :)
[01:18:07] <stuartdouglas> actually it was O(n!)
[01:18:28] <mojavelinux> ouch!
[01:19:05] <mojavelinux> your signature can be like
[01:19:05] <mojavelinux> + O(n)
[01:21:49] *** bleathem has joined #seam-dev
[01:23:42] <stuartdouglas> with weld 1.1 once you start adding a few archives with beans.xml the deployment time just blows out massivly
[01:23:47] <stuartdouglas> but only on GF
[01:24:06] <stuartdouglas> because AS6 does not implement the spec properly, and this saves it from the same problem :-)
[01:26:46] <mojavelinux> ah, funny how that works out
[01:26:53] <mojavelinux> so then we really, really need a weld 1.1.1 for glassfish
[01:27:05] <mojavelinux> i've patched some parts of seam so that it doesn't fall over
[01:27:12] <mojavelinux> but, that doesn't mean it's really great
[01:27:39] <mojavelinux> I'm going to bump that post on weld-dev to see if we can get some activity :)
[01:28:41] <mojavelinux> actually, I think first I should check to see if I can get weld HEAD to run on glassfish 3.1
[01:28:46] <mojavelinux> maybe then we just need the 1.2 release
[01:29:55] <mojavelinux> i'll give it a go
[01:30:12] <bleathem> +1 for Weld 1.1.1 !!!
[01:32:51] <mojavelinux> bleathem: I came across a post last night that reminded me of something...do we have an api in faces for doing a redirect to another view
[01:33:01] <mojavelinux> something simple...we had something like that in seam 2
[01:33:09] <mojavelinux> some guy just wrote a post that looks quite frankly horrible
[01:33:21] <mojavelinux> and I was like, hmmm sounds like a job for seam faces
[01:34:03] <mojavelinux> http://www.dzone.com/links/r/efficient_way_to_redirect_to_a_page_in_jsf_2.html
[01:34:49] <mojavelinux> surely it must be simpler than that with the JSF 2 API, but atm I can't remember whether we included a simpler api
[01:36:20] <mojavelinux> he's doing specifically an internal forward
[01:36:39] <mojavelinux> but obviously having one that does a regular redirect would be ideal too
[01:37:00] <mojavelinux> btw, this would be from an arbitrary point in an action or action listener
[01:37:06] <mojavelinux> as opposed to using navigation rules
[01:37:14] *** kenfinnigan has joined #seam-dev
[01:38:48] <mojavelinux> this is still happening in the weld osgi bundle
[01:38:50] <mojavelinux> Specification-Version: ${parsedVersion.osgiVersion}
[01:41:53] <mojavelinux> https://issues.jboss.org/browse/WELD-869
[01:47:38] <mojavelinux> cool!
[01:48:15] <mojavelinux> only 2 failures and 4 errors when running solder tests against glassfish with weld SNAPSHOT!
[01:48:20] <mojavelinux> that's a massive improvement!
[01:48:26] <mojavelinux> but, we still aren't out of the woods yet
[01:48:32] <mojavelinux> Failed tests:
[01:48:32] <mojavelinux>   testGenericAlternatives(org.jboss.seam.solder.test.bean.generic.alternative.GenericBeanAlternativeTest)
[01:48:32] <mojavelinux>   testGenericProducerMethodAlternatives(org.jboss.seam.solder.test.bean.generic.alternative.GenericBeanAlternativeTest)
[01:48:32] <mojavelinux> Tests in error:
[01:48:32] <mojavelinux>   org.jboss.seam.solder.test.log.LoggerInjectionTest
[01:48:32] <mojavelinux>   org.jboss.seam.solder.test.log.LoggerInjectionTest
[01:48:32] <mojavelinux>   org.jboss.seam.solder.test.compat.registration.VisibilityOfBeanRegisteredByExtensionFromNonBeanLibraryTest
[01:48:33] <mojavelinux>   org.jboss.seam.solder.test.compat.registration.VisibilityOfBeanRegisteredByExtensionFromNonBeanLibraryTest
[01:48:57] <mojavelinux> generic beans, logging (not sure what that's about) and one visibility test
[01:50:35] <stuartdouglas> I think the generic bean failures are a by product of the visibility stuff
[01:52:44] <mojavelinux> got it
[01:52:50] <mojavelinux> the logger failure is just a bad test
[01:52:53] <mojavelinux> gotta fix that
[01:52:57] <mojavelinux> it's incuding the producer twice
[01:53:04] <mojavelinux> funny it actually worked before
[01:56:57] <mojavelinux> cool!
[01:57:04] <mojavelinux> okay, so just the generic beans, that's all
[01:57:12] <mojavelinux> because of the visibility problem as you mentioned
[02:03:20] *** PeteRoyle has joined #seam-dev
[02:04:19] <mojavelinux> if that visibility is out of compliance, it still needs to be fixed
[02:04:28] <mojavelinux> but if it's to spec, then cut weld 1.1.1!
[02:04:29] <mojavelinux> :)
[02:04:36] <mojavelinux> we are in business
[03:07:11] *** Diablo-D3 has joined #seam-dev
[03:07:24] <Diablo-D3> can seam 3 security use http auth?
[03:08:39] <kenfinnigan> mojavelinux: ping
[03:09:01] <Diablo-D3> also, when is another version of it going to be released that has @LoggedIn
[03:14:40] <kenfinnigan> Diablo-D3: I expect there will be a CR2 of Security in the next day or two
[03:15:05] <kenfinnigan> which should include @LoggedIn
[03:25:44] *** gastaldi has joined #seam-dev
[03:25:55] <gastaldi> hey all !
[03:26:28] <gastaldi> took some beers to celebrate Seam jcr alpha 1 release ! :D
[03:28:45] *** cbrock has joined #seam-dev
[03:28:45] *** cbrock has quit IRC
[03:28:45] *** cbrock has joined #seam-dev
[03:35:32] *** cbrock has quit IRC
[03:35:35] *** gastaldi has quit IRC
[03:45:25] *** kenfinnigan has quit IRC
[03:59:59] *** clerum has quit IRC
[04:32:40] <Diablo-D3> so, no one knows if seam 3 security can use http authb?
[04:45:01] <mojavelinux> to be honest, I haven't had a chance to spend any length of time with seam 3 security yet, so I can't answer the question...however, i would imagine that supporting it would be reasonable...if you can't find it in the code, then perhaps file a jira
[04:55:41] *** gastaldi has joined #seam-dev
[05:04:35] *** clerum has joined #seam-dev
[05:08:59] *** gastaldi has quit IRC
[05:25:56] *** lincolnthree1 has quit IRC
[05:30:14] *** lightguard_jp has joined #seam-dev
[05:39:09] <bleathem> mojavelinux Re: redirecto to another view.  I don't know of anything in Faces that does that, but that doesn't mean it's not there :P
[05:40:03] <bleathem> I'll jira it
[05:42:57] <bleathem> SEAMFACES-103
[05:43:05] <jbossbot> jira [SEAMFACES-103] Create an api for doing a redirect to another view [Open (Unresolved) Feature Request, Major, Unassigned] https://issues.jboss.org/browse/SEAMFACES-103
[05:46:21] <bleathem> Anyone have any input into rename ViewData* to ViewMeta* in Seam Faces?
[05:46:45] <bleathem> ^^ stuartdouglas? mojavelinux?
[05:47:12] <stuartdouglas> I am fine with it
[05:48:36] <bleathem> k, thx
[05:54:42] <bleathem> When will an IDE be good enough that you can trust a refactoring without having to verify with grep.
[05:55:09] <bleathem> I guess once all XML configs are replaced with type safe configurations
[06:12:49] <lightguard_jp> Arquillian Alpha 5 is out!!
[06:12:56] <lightguard_jp> Time to migrate those tests
[06:14:41] <bleathem> Or finally build them (the tests)!
[06:16:40] <mojavelinux> yes, this is the huge breakthrough
[06:16:46] <mojavelinux> because now you can really do JSFUnit tests easily
[06:16:55] <mojavelinux> and also we can do selenium tests
[06:17:05] <mojavelinux> and we can do dependency management
[06:17:10] <mojavelinux> and we can do classpath management
[06:17:37] <bleathem> Any examples with the release?
[06:17:41] <bleathem> :P
[06:18:56] <lightguard_jp> aslak: ^^-2 ?
[06:19:18] <bleathem> So what phase do people think would be the best phase before which to enforce view restrictions?
[06:19:29] <bleathem> I figure the earlier the better
[06:19:30] <aslak> examples?
[06:19:36] <mojavelinux> I think it would be in restore view
[06:19:47] <bleathem> definately don't want invoke application occurring
[06:20:04] <mojavelinux> yep, you can do it during createMetadataView
[06:20:06] <mojavelinux> perhaps
[06:20:07] <bleathem> restore view sounds good :P
[06:20:10] <mojavelinux> which is like a pre-view build
[06:20:28] <mojavelinux> it just builds the metainformation
[06:20:31] <bleathem> Looking forward, I want to be able to parse the metadat
[06:20:40] <bleathem> so maybe after that
[06:20:53] <mojavelinux> yeah, that would be just the right time
[06:20:57] <mojavelinux> me thinks
[06:21:12] <mojavelinux> as andy schwartz likes to say, you don't want to waste time building the view only to throw it away
[06:21:42] <bleathem> efficient!
[06:26:38] <mojavelinux> i need some sleep so I can be ready to play with arquillian alpha5...yeah :)
[06:27:04] <bleathem> if you need help falling asleep, count aliens
[06:28:09] <mojavelinux> I'm blaming aslak if I don't sleep...Ike is calling to me
[06:36:32] <bleathem> @Inject private ViewMetaStore dataStore;
[06:36:38] <bleathem> Restrict annotation = dataStore.getDataForCurrentViewId(Restrict.class);
[06:36:55] <bleathem> stuartdouglas: nice!  this is a really easy to use API!
[06:37:19] <bleathem> suppose I should call it a metaStore though!
[06:37:21] <stuartdouglas> That was what I was going for :-)
[06:37:39] <bleathem> I'd say mission success.
[06:37:49] <bleathem> so far!
[06:38:23] <mojavelinux> heck yeah
[06:38:40] <bleathem> So I've got the EL from my @Restrict annotation
[06:38:46] <bleathem> how should I process it?
[06:38:56] <bleathem> Any other classes I should look to as an example?
[06:39:32] <mojavelinux> Expressions from Solder
[06:39:32] * Diablo-D3 builds seam security trunk for @LoggedIn
[06:39:59] <bleathem> ok, off to chase down the solder source
[06:40:01] <bleathem> thx!
[06:40:41] *** daniel_hinojosa has quit IRC
[06:41:09] <bleathem> oh, already had it cloned.  nice
[06:51:41] <bleathem> testing out a simple @Restrict("false") ViewMeta annotation
[06:59:58] <bleathem> public void enforce (@Observes PostConstructViewMapEvent event)
[07:00:04] <bleathem> ^^ doesn't seem to be getting called
[07:00:22] <sbryzak> we don't want to use EL for view restrictions
[07:00:32] <bleathem> oh
[07:00:35] <sbryzak> they should use the new typesafe security annotations
[07:00:38] <bleathem> what do we want to use?
[07:00:51] <bleathem> From Seam Security?
[07:00:56] <sbryzak> yes
[07:01:16] <bleathem> so Seam security is required?
[07:01:29] <sbryzak> take a look at this example: https://github.com/seam/security/tree/master/examples/authorization
[07:01:46] <sbryzak> it should be an optional requirement
[07:02:36] <lightguard_jp> You get that nasty logging with Mojarra :(
[07:05:19] <bleathem> sbryzak, looking at that example, it seems like one creates custom annotations to apply security constraints
[07:05:22] <bleathem> is that correct?
[07:05:23] *** lukaszlenart has joined #seam-dev
[07:05:32] <sbryzak> bleathem: that's correct
[07:05:36] <bleathem> (sorry, not at all familiar with Seam Security)
[07:05:52] *** lukaszlenart has left #seam-dev
[07:06:04] <sbryzak> there's actually a 'how it works' on this page: https://github.com/seam/security/blob/master/examples/authorization/src/main/webapp/home.xhtml
[07:06:15] <bleathem> Ok, so I don't know ahead of time what are the Security annotations on a enum value will be
[07:06:28] <bleathem> they could be anything that user has decided is appropriate
[07:06:36] <sbryzak> the annotations will be annotated with @SecurityBindingType
[07:06:41] <bleathem> oh, ok
[07:06:45] <sbryzak> so you just check for that, with reflection
[07:08:51] <sbryzak> hmm, one possible way to handle this is to have the faces module raise an event
[07:08:57] <bleathem> and then I have a class, with methods annotated @Secures, and a custom annotation, and those methods are what evaluate whether access is granted?
[07:09:11] <sbryzak> yes, but you don't want to write the code to do all that
[07:09:41] <sbryzak> i think if you raise a ViewSecuredEvent or something like that
[07:09:56] <sbryzak> the security module can observe it, do the security check, and return a boolean
[07:10:09] <bleathem> ok, that sounds good
[07:10:13] <sbryzak> CheckSecuredViewEvent maybe
[07:10:27] <sbryzak> that way you don't have a hard dependency
[07:10:54] <sbryzak> put all the relevent metadata in the event object
[07:11:28] <bleathem> relevant metadata includes what annotations they've put in the @ViewConfig right?
[07:11:28] *** aslak has quit IRC
[07:12:29] <sbryzak> it would require the annotation value/s
[07:12:36] <bleathem> relevant data: annotations, username, user roles
[07:12:37] <sbryzak> (there may be more than one)
[07:12:56] *** kuuyee has joined #seam-dev
[07:12:57] <sbryzak> username is already known if they've logged in
[07:13:15] * nickarls notices sec-talk and reads backlog
[07:13:44] <sbryzak> all this stuff is for nickarls anyway, he's the only one that uses security
[07:14:31] <bleathem> nickarls, feel free to chime in!
[07:15:41] <bleathem> nickarls this is w.r.t. SEAMFACES-33
[07:15:43] <jbossbot> jira [SEAMFACES-33] Create a solution for consolidated page-flow, transactional control, security constraints and URL-rewriting configuration [Open (Unresolved) Feature Request, Blocker, Brian Leathem] https://issues.jboss.org/browse/SEAMFACES-33
[07:17:55] <nickarls> sbryzak: good thing that you're keeping all your sec users happy ;-)
[07:18:10] <sbryzak> i only have one that i know of
[07:18:35] <nickarls> is there anything you could place in f:meta for the view that could serve as sec metadata?
[07:18:53] <bleathem> That's the plan
[07:18:58] <sbryzak> yep, we actually discussed that
[07:19:03] <sbryzak> but it won't be done in time for 3.0 final
[07:19:08] <bleathem> to allow f:metadata tags to allow overriding waht's in the @ViewConfig
[07:19:23] <bleathem> (typed that too fast)
[07:19:32] <nickarls> wouldn't that allow for inheritance through templating?
[07:20:14] <bleathem> I though the f:metadata tag didn't inherit with templating
[07:20:17] <sbryzak> good point, it should
[07:20:19] <bleathem> don't you need on for each page?
[07:20:44] <sbryzak> the template might define some basic security restrictions, e.g. @LoggedIn
[07:20:51] <nickarls> BTW: I'm almost sure I saw there case with two authenticators, A and B, A conffed in beans.xml by classname, then I @Vetoed A but forgot to change the beans.xml and A still got used. Haven't reprodcued/JIRAd yet.
[07:21:19] <nickarls> at least I think I get f:event called from templates
[07:21:26] <sbryzak> nickarls: interesting.. that would suggest that @Veto is broken
[07:22:13] <nickarls> that's so simple so it's hard to think it's  broken. have to reproduce.
[07:22:39] <sbryzak> if you do, please let me know asap
[07:22:52] <sbryzak> can't let something like that get released in the final
[07:23:06] <bleathem> "The page author must ensure that the <f:metadata> element does not appear on a template or included page. It must reside on the root page that corresponds to the viewId."
[07:23:12] <bleathem> http://javaserverfaces.java.net/nonav/docs/2.0/pdldocs/facelets/f/metadata.html
[07:23:51] <lightguard_jp> I'm out for the night.
[07:23:58] <bleathem> g'night!
[07:23:59] *** lukaszlenart has joined #seam-dev
[07:24:05] *** lukaszlenart has left #seam-dev
[07:24:15] <sbryzak> lightguard_jp: night!
[07:24:29] <lightguard_jp> sbryzak: Have a good evening
[07:24:54] <sbryzak> i'll be here :)
[07:24:56] *** lightguard_jp has quit IRC
[07:25:03] *** oskutka has joined #seam-dev
[07:25:47] <bleathem> Ok, it's getting late.  And my PostConstructVierwMapEvent isn't getting observed.
[07:25:59] <bleathem> I'll update the jira with what you said sbryzak
[07:26:12] <sbryzak> bleathem: thanks
[07:26:15] <bleathem> Thanks for the Seam Security crash course!
[07:27:48] <bleathem> nickarls: you may also be interested in SEAMFACES-102
[07:27:49] <jbossbot> jira [SEAMFACES-102] Support ViewMeta configuration via facelet <f:metadata> child tags [Open (Unresolved) Feature Request, Major, Unassigned] https://issues.jboss.org/browse/SEAMFACES-102
[07:31:27] <nickarls> but you could ui:include in all pages inside for the metadata if there is no inheritance?
[07:34:32] <bleathem> Yes, you could ui:include
[07:34:55] <mojavelinux> I'm off to bed, but I saw this blog entry that will just speak to shane
[07:34:56] <mojavelinux> http://hegsti.blogspot.com/2011/03/rethinking-automated-release-management.html
[07:35:05] <nickarls> sbryzak: and you still dislike EL, eh?
[07:35:07] <mojavelinux> rethinking automated release management
[07:35:29] <mojavelinux> with git and gradle
[07:35:52] * nickarls is still a bit sceptic about this gradle-thingie
[07:37:08] <mojavelinux> remember, you could always have a hybrid solution
[07:37:20] <bleathem> how do you do that IRC * thinking thing
[07:37:22] <mojavelinux> where gradle is doing release tasks and maven is building and maintaining the project from a dev standpoint
[07:37:38] <mojavelinux> it doesn't have to be all or nothing
[07:37:50] <mojavelinux> and maven is a whole lot of nothing sometimes when it comes to release management
[07:37:51] <nickarls>  /me without space
[07:38:02] * mojavelinux finally figured out that *** thing
[07:38:06] <mojavelinux> woot
[07:38:24] * mojavelinux thanks nik and says he needs to listen to body
[07:38:25] * bleathem ok
[07:38:47] <bleathem> [Error] mewhat: Unknown command.
[07:38:54] <nickarls> mojave: it says skipping breakfast was a bad idea
[07:39:06] * bleathem trying it out
[07:39:12] <bleathem> oh, got it
[07:39:32] <nickarls> with maven there is method in the madness at least. with gradle you could have obfuscated build script contests
[07:39:35] * bleathem going to probably over use this in the next few days
[07:39:38] <nickarls> guess what this builds and win a price
[07:40:01] <nickarls> I'm sure there is some point at a project size when the balance tips to gradle
[07:40:36] * nickarls slaps bleathem with a trout
[07:41:02] <nickarls> hate that this irc net has registered nicks
[07:41:23] <nickarls> with IRCNet there would be decent nickwars with hostile channel takeovers and all that fun
[07:41:35] * bleathem ouch!
[07:41:41] <nickarls> and you would send PoD:s to get your nick back! Those were the days
[07:41:54] <nickarls> PoD:s are not that effective nowadays ;-)
[07:42:21] <bleathem> sbryzak I updated seamfaces-33 I hope I summarized our conversation correctly :P
[07:42:42] * bleathem is glad he wasn't in IRC in the good ole days!
[07:42:54] <nickarls> sbryzak: correction. If the authenticator is disabled (== not resolved) it tries the next one
[07:43:05] <nickarls> so its probably intended behaviour and not a bug
[07:43:56] <bleathem> way passed my bedtime
[07:44:05] <bleathem> g'night all
[07:44:44] *** jharting has joined #seam-dev
[07:44:55] *** bleathem has quit IRC
[07:46:19] <nickarls> bleathem: nono, you're wrong, it's 9am. keep coding!
[07:47:18] <nickarls> sbryzak: another thing, shouldnt the snapshot seam-bom point to snapshot poms of modules?
[07:50:13] <jbossbot> git [faces] push master 9d1210b.. Dan Allen SEAMFACES-96 don't attempt to propogate PreDestoryApplicationEvent
[07:50:14] <jbossbot> jira [SEAMFACES-96] Disable Abstractlistener when JSF application is shutting down [Pull Request Sent (Unresolved) Bug, Major, Unassigned] https://issues.jboss.org/browse/SEAMFACES-96
[07:50:15] <jbossbot> git [faces] push master URL: http://github.com/seam/faces/compare/c8a0505...9d1210b
[07:56:21] <sbryzak> nickarls: i wasn't aware we were publishing snapshots
[07:57:43] <nickarls> https://repository.jboss.org/nexus/content/groups/public/org/jboss/seam/seam-bom/3.0.0-SNAPSHOT/
[08:02:37] <sbryzak> hmm, how about all the other modules
[08:03:30] <sbryzak> ok it looks like they're getting published also
[08:03:56] <sbryzak> i'm guessing it's hudson
[08:06:38] <nickarls> sbryzak: haven't checked JIRA:s/commits yet but did you fix the Dan-renaming-SeamManaged-breaking-security issue?
[08:07:02] <sbryzak> um, which issue was that?
[08:07:26] <nickarls> no, wait, persistence, but security pulls it in, right?
[08:07:35] <sbryzak> i didn't realise he renamed it.. we just moved it to solder as far as i know
[08:07:44] <nickarls> in solder there was some core/SeamManaged that got renamed
[08:07:53] <nickarls> and it broke an extension in persistence
[08:08:03] <sbryzak> yeah we moved it from persistence to solder
[08:08:16] <sbryzak> because other modules needed a @SeamManaged annotation also
[08:09:06] <sbryzak> is this persistence CR2 you're talking about?
[08:09:24] <nickarls> master, nevermind stu fixed it apparently
[08:09:37] <stuartdouglas> what did I fix?
[08:09:54] <nickarls> https://github.com/seam/persistence/commit/afa73bc6d1150f3fd7b68c0a59a4d31734cc0820
[08:09:55] <jbossbot> git [persistence] afa73bc.. Stuart Douglas Remove @SeamManaged
[08:10:03] <nickarls> Dans SeamManaged rename
[08:10:29] <nickarls> or did you? hold that thought
[08:10:54] <nickarls> https://github.com/seam/solder/commit/acfc7586ad4cef3e1e9c53046ea56ab93708734b
[08:10:54] <jbossbot> git [solder] acfc758.. Dan Allen SOLDER-83 rename SeamManaged to ExtensionManaged
[08:10:55] <jbossbot> jira [SOLDER-83] rename SeamManaged to ExtensionManaged [Resolved (Done) Enhancement, Major, Dan Allen] https://issues.jboss.org/browse/SOLDER-83
[08:11:07] <nickarls> so it was moved *and* renamed?
[08:11:31] <sbryzak> er, this is the first i've heard of it
[08:11:51] <nickarls> I noticed I got breakage yesterday when going all-SNAPSHOT on seam3
[08:12:05] <sbryzak> dammit
[08:12:11] <sbryzak> he did it after i made the release
[08:12:58] <sbryzak> the api was supposed to be stable now, because this is the last CR release
[08:14:47] <sbryzak> i think i'll do another release of solder
[08:15:00] <sbryzak> which means i have to do config and persistence again also
[08:15:23] <nickarls> [22:17:14] <bleathem> #action SeamManaged annotation shall henceforth be referred to as ExtensionManaged
[08:15:24] <nickarls> [22:17:15] <mojavelinux> #agreed rename SeamManaged to ExtensionManaged to reflect it's function over branding, despite pleads by john to name it ModuleManaged
[08:16:14] *** marekn has joined #seam-dev
[08:16:16] <sbryzak> i don't have a problem with the change itself, just the timing of it
[08:19:46] *** Royle has joined #seam-dev
[08:20:02] *** Royle has quit IRC
[08:22:29] *** PeteRoyle has quit IRC
[08:30:30] <nickarls> nfg, any i18n-module wizard around?
[08:35:14] <nickarls> how is it possible that I have @Injected Bundles, which is a @RequestScoped bean
[08:35:29] <nickarls> but the @Inject ApplicationBundles bundles inside that one is null
[08:35:50] <nickarls> how can a (non-produced) value of a managed bean injection be null?
[08:36:25] <nickarls> I can inject the ApplicationBundles myself just fine
[08:41:00] *** mgencur has joined #seam-dev
[08:41:16] <nickarls> even more WTF is that I can call bundles.size() and it works but not the bundles.get
[08:42:39] *** kpiwko has joined #seam-dev
[08:49:13] <nickarls> I don't believe this. I put a breakpoint in Bundles.size() and Bundles.get(Locale, String). For the size(), its injections are fine. For get(), the injections are null. And it's the same proxy!
[08:50:10] *** maschmid has joined #seam-dev
[08:52:46] <sbryzak> nickarls: you need to let ken know
[08:56:50] <nickarls> it must be something weld-proxy-level (or user error related to it)
[09:05:31] * Diablo-D3 hrms.
[09:05:40] <Diablo-D3> I wonder if theres a better solution to handle http auth
[09:21:06] <nickarls> is there any reasonable way to override ResourceBundle so that I can get Bean Validation messages from the database
[09:21:20] <nickarls> other than doing some strange classloader trick that will break everything else?
[09:22:52] <nickarls> ResourceBundle.Control is no good if the implementation doesn't call it
[09:32:59] *** Royle has joined #seam-dev
[09:51:41] *** alesj has joined #seam-dev
[10:02:33] *** emmanuel has joined #seam-dev
[10:12:49] *** Feng has joined #seam-dev
[10:14:33] *** kuuyee has left #seam-dev
[10:15:45] *** Feng has quit IRC
[10:16:15] *** kuuyee has joined #seam-dev
[10:16:31] <kuuyee> hello
[10:18:23] <alesj> kuuyee: hey
[10:18:25] <Diablo-D3> https://issues.jboss.org/browse/SEAMSECURITY-17
[10:18:30] <jbossbot> jira [SEAMSECURITY-17] Servlet Filter to pick up security information for Seam after Java EE web container security [Open (Unresolved) Feature Request, Major, Shane Bryzak] https://issues.jboss.org/browse/SEAMSECURITY-17
[10:18:34] <Diablo-D3> I guess this implies seam security doesnt do http auth yet
[10:18:40] <alesj> kuuyee: got your translation access in order?
[10:23:17] <nickarls> sbryzak: there only difference between wrong password and authenticator throwing exception is the exception in the LoginFailedEvent?
[10:24:31] <sbryzak> nickarls: um.. i don't quite understand
[10:25:23] <nickarls> sbryzak: if the password is wrong there is a LoginFailedEvent fired (with null exception)?
[10:25:36] <kuuyee> alesj:yes thanks
[10:26:39] <kuuyee> alesj: Sean Flanigan have added me to the 'translator' role
[10:26:48] <nickarls> sbryzak: and if the authenticator throws e.g. a NPE, you get an LoginFailedException(npe)
[10:26:55] <sbryzak> nickarls: hmm, yes i think that's right
[10:27:06] <nickarls> judging from the IdentityImpl
[10:27:15] <sbryzak> yep, i'm looking at it now
[10:27:31] <nickarls> could be nice to have a separate event as a feature request
[10:27:46] <sbryzak> if the authentication fails due to incorrect password or something, the LoginFailedEvent won't contain a cause
[10:27:56] <sbryzak> what's the use case?
[10:27:58] <alesj> kuuyee: cool
[10:28:05] <kuuyee> :)
[10:28:34] <nickarls> sbryzak: different observers for bad password and authenticator died. well, you can if() the diff
[10:30:21] <kuuyee> I am Beginner
[10:30:35] <sbryzak> nickarls: i think testing for loginException should be enough
[10:31:02] <sbryzak> the login() method also returns a string, so a navigation rule could use that
[10:31:20] <sbryzak> it returns "failed" for a failure, or "exception" for an exception
[10:32:20] <kuuyee> alesj:May I participate in seam module(face) development?
[10:33:16] <alesj> kuuyee: i don't see any issues ? sbryzak?
[10:33:34] <alesj> kuuyee: with Git, it's super simple to aprticipate
[10:33:43] <sbryzak> kuuyee, you will need to coordinate with bleathem, he's the module lead
[10:33:51] <kuuyee> Ok I see!
[10:34:00] <alesj> kuuyee: simply provide useful patches, pull-requests, etc
[10:34:13] <alesj> then it's up to module lead to decide what to do
[10:34:19] <sbryzak> kuuyee: if you want to provide a patch or something, just send a pull request through github
[10:37:05] <kuuyee> Contribute guideline : http://www.seamframework.org/Seam3/ContributeHome#H-ForkAndContribute
[10:37:59] <kuuyee> I will comply with the Contribute guideline
[10:57:20] *** kenfinnigan has joined #seam-dev
[11:05:34] *** kuuyee has quit IRC
[11:05:47] *** clerum has quit IRC
[11:13:14] *** kenfinnigan has quit IRC
[11:18:04] <alesj> sbryzak: ping?
[11:18:12] <sbryzak> alesj: pong
[11:18:24] <alesj> looking at SEAM-42
[11:18:26] <jbossbot> jira [SEAM-42] @Begin and @End could be moved to the Seam Conversation module [Open (Unresolved) Enhancement, Major, Ales Justin] https://issues.jboss.org/browse/SEAM-42
[11:18:58] <sbryzak> ah, yes
[11:19:03] <sbryzak> i think it belongs in the conversation module
[11:19:11] <sbryzak> it's not a priority right now though
[11:19:37] <alesj> you mean there is already an implmentation
[11:19:44] <alesj> for @Begoni/@End handling
[11:19:50] <alesj> but needs to be moved there
[11:19:54] <sbryzak> i'm not sure
[11:19:54] <alesj> or we need to implment that?
[11:20:06] <sbryzak> bleathem can confirm
[11:20:19] <sbryzak> i was under the impression that it's just an idea at the moment
[11:21:24] <alesj> ok, i'll check Seam Faces
[11:21:28] <alesj> to see what's already done
[11:43:41] *** Royle has quit IRC
[12:03:21] *** emmanuel has quit IRC
[12:26:07] *** epbernard has joined #seam-dev
[12:26:07] *** epbernard is now known as emmanuel
[12:46:21] <jose_freitas> morning
[13:35:22] *** tsurdilo has joined #seam-dev
[13:49:10] *** Diablo-D3 has quit IRC
[13:53:12] *** aslak has joined #seam-dev
[13:53:12] *** aslak has quit IRC
[13:53:12] *** aslak has joined #seam-dev
[13:56:55] *** balunasj has joined #seam-dev
[14:18:08] *** kpiwko has quit IRC
[14:38:18] *** balunasj is now known as balunasj_busy
[14:41:22] <jbossbot> git [rest] push master 7717260.. Jozef Hartinger minor
[14:41:23] <jbossbot> git [rest] push master ec2bf52.. Jozef Hartinger SEAMREST-30 use @DefaultBean again
[14:41:24] <jbossbot> jira [SEAMREST-30] Cannot use @DefaultBean for default ClientExecutor [Open (Unresolved) Bug, Minor, Jozef Hartinger] https://issues.jboss.org/browse/SEAMREST-30
[14:41:24] <jbossbot> git [rest] push master URL: http://github.com/seam/rest/compare/6d9f052...ec2bf52
[14:41:47] *** lincolnthree has joined #seam-dev
[14:41:49] *** rruss has quit IRC
[15:12:46] *** clerum has joined #seam-dev
[15:33:29] *** marekn has quit IRC
[15:34:07] *** rruss has joined #seam-dev
[15:40:53] <jose_freitas> mojavelinux: ping
[15:41:16] <jose_freitas> sbryzak: ping
[15:45:23] *** alesj has quit IRC
[15:51:06] *** alesj has joined #seam-dev
[15:55:31] *** alesj has quit IRC
[16:07:25] *** mgencur has quit IRC
[16:14:38] *** alesj has joined #seam-dev
[16:41:09] <jbossbot> git [forge] push master 560970c.. Lincoln Baxter, III SEAMFORGE-77
[16:41:10] <jbossbot> jira [SEAMFORGE-77] Test harness does not function consistently with actual terminal behavior [Open (Unresolved) Bug, Major, Unassigned] https://issues.jboss.org/browse/SEAMFORGE-77
[16:41:10] <jbossbot> git [forge] push master URL: http://github.com/seam/forge/compare/dc06e89...560970c
[16:42:54] *** jharting has quit IRC
[16:46:34] *** lincolnthree has quit IRC
[16:46:37] <clerum> is there an example somwhere of using the new shrinkwrap maven dep resolver?
[16:56:06] *** kuuyee has joined #seam-dev
[17:00:28] *** kuuyee has quit IRC
[17:07:57] *** oskutka has quit IRC
[17:14:13] *** bitshuffler has joined #seam-dev
[17:21:32] *** daniel_hinojosa has joined #seam-dev
[17:44:16] *** emmanuel has quit IRC
[17:53:07] *** maschmid has quit IRC
[18:05:50] *** daniel_hinojosa has quit IRC
[18:05:52] *** daniel_hinojosa1 has joined #seam-dev
[18:21:25] *** kenfinnigan has joined #seam-dev
[18:22:49] <kenfinnigan> For those playing with arquillian alpha5
[18:23:08] <kenfinnigan> Using the embedded weld ee container
[18:23:52] <kenfinnigan> You will need to modify the pom to use groupId org.jboss.arquillian.container
[18:24:42] <kenfinnigan> Instead of org.jboss.weld.arquillian.container
[18:25:12] <kenfinnigan> Otherwise it will use some alpha4 deps which gives interesting results!
[18:39:15] *** bitshuffler_ has joined #seam-dev
[18:43:08] *** bitshuffler has quit IRC
[18:58:11] *** oskutka has joined #seam-dev
[19:00:06] *** daniel_hinojosa1 has quit IRC
[19:00:12] *** daniel_hinojosa has joined #seam-dev
[19:01:11] *** gastaldi has joined #seam-dev
[19:03:03] <kenfinnigan> Anyone know if arquillian automatically includes content of target/test-classes onto classpath even if not declared in deployment?
[19:03:18] <gastaldi> yes
[19:03:35] <gastaldi> hum.. Wait
[19:03:45] <gastaldi> No, you must include a package
[19:03:48] <kenfinnigan> It does? Is there a way to prevent that?
[19:04:11] <gastaldi> I believe it does not include
[19:04:14] <kenfinnigan> Ok, might be a quirk with weld ee embedded then
[19:06:31] *** cbrock has joined #seam-dev
[19:06:38] *** oskutka has quit IRC
[19:09:55] *** alesj has left #seam-dev
[19:15:24] *** kenfinnigan has quit IRC
[19:38:47] *** balunasj_busy has quit IRC
[19:48:56] *** daniel_hinojosa has quit IRC
[19:49:01] *** wdrai has joined #seam-dev
[19:49:39] *** gastaldi has left #seam-dev
[19:54:46] *** lincolnthree1 has joined #seam-dev
[19:59:48] <jbossbot> git [forge] push master 1182b26.. Lincoln Baxter III SEAMFORGE-78
[19:59:49] <jbossbot> jira [SEAMFORGE-78] Shell color does not function in Windows [Closed (Done) Enhancement, Major, Lincoln Baxter III] https://issues.jboss.org/browse/SEAMFORGE-78
[19:59:50] <jbossbot> git [forge] push master d6ed7d9.. Lincoln Baxter III fixed forge.bat to enable color on windows
[19:59:50] <jbossbot> git [forge] push master URL: http://github.com/seam/forge/compare/560970c...d6ed7d9
[20:39:29] *** balunasj has joined #seam-dev
[20:41:20] *** balunasj has quit IRC
[20:46:43] *** cbrock has quit IRC
[20:53:33] *** daniel_hinojosa has joined #seam-dev
[20:56:53] *** cbrock has joined #seam-dev
[20:56:53] *** cbrock has quit IRC
[20:56:53] *** cbrock has joined #seam-dev
[20:59:12] *** bitshuffler_ has quit IRC
[21:13:44] <jose_freitas> stuartdouglas: ping
[21:13:54] <stuartdouglas> jose_freitas: pong
[21:14:28] <jose_freitas> hello stuart, does seam-persistence transaction management uses JTA?
[21:14:46] <stuartdouglas> yes
[21:15:05] <stuartdouglas> although it can also use EntityTransaction or HibernateTransaction
[21:15:13] <stuartdouglas> but it needs the JTA classes on the CP
[21:15:18] <jose_freitas> ok
[21:15:34] <jose_freitas> how do you manage this? @Requires ?
[21:24:37] *** oskutka has joined #seam-dev
[21:28:06] <stuartdouglas> jose_freitas: no, SeamTransaction extends UserTransaction
[21:28:22] <stuartdouglas> the JTA producer for it is an @DefaultBean
[21:28:33] <stuartdouglas> and then you can install one of the other producers via seam-xml
[21:37:46] <jose_freitas> nice
[21:37:50] <jose_freitas> thanks stuart
[21:42:14] *** alesj has joined #seam-dev
[22:20:42] *** Diablo-D3 has joined #seam-dev
[22:38:55] *** jose_freitas has quit IRC





top