[00:07:56] *** tsurdilo has quit IRC
[00:21:20] <lightguard_jp> lincolnthree: You there?
[00:21:30] <lightguard_jp> Or anyone else really?
[00:21:39] <lightguard_jp> Can't delpoy my example war to Glassfish
[00:21:42] <lightguard_jp> Unable to load EJB module
[00:28:42] <arbi> show stack trace
[00:28:55] <arbi> how do you communicate stack trace via IRC?
[00:29:07] <arbi> paste somewhere else i guess
[00:29:13] <lightguard_jp> I think it's a class not found
[00:36:28] <arbi> so most likely you're missing a JAR?
[00:36:46] <lightguard_jp> http://pastebin.com/nFASm2hS
[00:36:51] <lightguard_jp> Little better
[00:40:46] <lightguard_jp> If anyone has ideas feel free.  The latest is in my github repo
[01:06:52] *** bleathem has quit IRC
[01:17:14] *** lightguard_jp has quit IRC
[01:21:56] *** tsurdilo has joined #seam-dev
[01:26:57] *** rruss has joined #seam-dev
[01:34:52] *** rruss has quit IRC
[01:59:45] *** aslak has joined #seam-dev
[02:26:54] *** tsurdilo1 has joined #seam-dev
[02:26:55] *** tsurdilo has quit IRC
[02:28:15] *** aslak has quit IRC
[02:36:47] *** tsurdilo has joined #seam-dev
[02:39:23] *** tsurdilo1 has quit IRC
[02:43:29] *** tsurdilo has quit IRC
[02:43:40] *** tsurdilo has joined #seam-dev
[05:04:39] *** tsurdilo has quit IRC
[05:08:44] *** lightguard_jp has joined #seam-dev
[05:36:16] <lightguard_jp> Who's here?
[06:28:54] <stuartdouglas> lightguard_jp: AnnotationInstanceProvider is now in another package
[06:29:17] <lightguard_jp> I had Alpha2 of xml. Switched to Alpha3 and that's fixed
[06:30:05] <lightguard_jp> http://pastebin.com/RWEbXncB
[06:30:11] <lightguard_jp> Is what I'm up against now
[06:31:16] <stuartdouglas> not really sure, looks like a glassfish problem
[06:32:04] <lightguard_jp> I have a producer that creates a request scoped component inside of an ApplicationScoped component, is that a problem?
[06:32:30] <stuartdouglas> shouldn't be
[06:32:35] <stuartdouglas> when do you get the error?
[06:32:45] <lightguard_jp> deploy time
[06:32:49] <stuartdouglas> are you trying to use the request scoped component when there is no active request?
[06:33:17] <stuartdouglas> Are you trying to inject it into a ServletContextListener or similar?
[06:33:20] <lightguard_jp> Ah, I see the problem
[06:35:50] <lightguard_jp> Was injecting the same thing I was producing, but at application startup, there is no request
[06:39:41] <lightguard_jp> Hm, can't inject, may have to go to the BeanManager to get the instance
[06:43:26] <lightguard_jp> Is getReference what I need?
[06:44:42] <lightguard_jp> It's a request scoped bean, but it's inside of a JAX-RS ExceptionMapper (which is @ApplicationScoped, not sure if I can do a different scope, that's what Jozeph has). I'd have to get the creational context for the request, right?
[07:00:53] <stuartdouglas> lightguard_jp: If it is request scoped, and there is no request, you can't get it
[07:01:03] <stuartdouglas> you could get an @New instance though
[07:01:18] <stuartdouglas> but only if there is an injection point that injects the @New bean
[07:01:26] <stuartdouglas> otherwise it does not get created
[07:01:41] <lightguard_jp> When I need it there will be a request
[07:01:55] <lightguard_jp> I think I'm going to get it from the BeanManager within the method that needs it
[07:04:21] <lightguard_jp> Hm, still getting it :(
[07:04:41] <lightguard_jp> Not quite sure what to do here
[07:06:18] *** stan8688 has joined #seam-dev
[07:07:04] <lightguard_jp> stuartdouglas: I'm going to head to bed, it's in my fork: https://github.com/LightGuard/catch the examples/jaxrs stuff if you care to take a look.  If you do, send me an email
[07:07:19] <stan8688> #seam
[07:07:21] <lightguard_jp> I'll take a look tomorrow and see if I can come up with anything
[07:07:41] *** lightguard_jp has quit IRC
[07:09:15] *** stan8688 is now known as stan
[07:10:11] <stan> #channel
[07:29:07] *** stuartdouglas has quit IRC
[07:29:45] <stan> Does anybody When will release seam 3.0?
[07:38:30] *** kpiwko has joined #seam-dev
[07:47:31] *** stan has quit IRC
[08:03:39] *** jharting has joined #seam-dev
[08:08:05] *** stan8688 has joined #seam-dev
[08:08:31] <stan8688> #seam
[08:19:09] <Nik> stan: yup, this is the place
[08:21:59] *** marekn has joined #seam-dev
[08:27:58] *** stan8688 has quit IRC
[08:28:56] *** stan8688 has joined #seam-dev
[08:44:16] *** oskutka has joined #seam-dev
[08:52:48] *** stuartdouglas has joined #seam-dev
[09:18:23] *** kpiwko has quit IRC
[09:28:48] *** plenyi has joined #seam-dev
[09:32:28] *** stan8688 has quit IRC
[09:41:56] *** kpiwko has joined #seam-dev
[09:44:11] *** kpiwko has quit IRC
[09:44:43] *** kpiwko has joined #seam-dev
[10:31:01] *** kpiwko has quit IRC
[10:35:53] *** kpiwko has joined #seam-dev
[10:36:40] <stuartdouglas> is there a meeting tonight?
[10:50:19] <marekn> not sure, pete and Dan are at Devoxx conference
[11:02:55] *** mbg has quit IRC
[11:30:28] *** lincolnthree1 has joined #seam-dev
[11:30:38] *** lincolnthree1 has left #seam-dev
[12:15:25] *** aslak has joined #seam-dev
[12:15:26] *** aslak has quit IRC
[12:15:27] *** aslak has joined #seam-dev
[12:22:30] *** aslak has quit IRC
[12:41:14] *** aslak has joined #seam-dev
[13:36:28] *** plenyi has quit IRC
[13:38:06] *** plenyi has joined #seam-dev
[13:40:24] *** lincolnthree1 has joined #seam-dev
[13:40:28] <jbossbot> git [forge] push master 8c7e554.. Lincoln Baxter, III before max killed my project
[13:40:29] <jbossbot> git [forge] push master f13d581.. Lincoln Baxter, III fixed entity annotation generation
[13:40:29] <jbossbot> git [forge] push master dce6a8c.. Lincoln Baxter, III fixed silly typo
[13:40:29] <jbossbot> git [forge] push master URL: http://github.com/seam/forge/compare/9692e85...dce6a8c
[13:48:09] *** jharting has quit IRC
[13:51:40] *** aslak has quit IRC
[14:10:36] *** aslak has joined #seam-dev
[14:16:47] *** rruss has joined #seam-dev
[14:17:55] *** rruss has left #seam-dev
[14:18:21] *** rruss has joined #seam-dev
[14:30:41] *** aslak has quit IRC
[14:34:47] *** aslak has joined #seam-dev
[14:41:05] *** jharting has joined #seam-dev
[15:02:20] *** lightguard_jp has joined #seam-dev
[15:11:23] *** plenyi has quit IRC
[15:15:47] *** aslak has quit IRC
[15:15:49] *** plenyi has joined #seam-dev
[15:17:28] <jharting> lightguard_jp: ping
[15:17:40] <lightguard_jp> Here
[15:19:45] <lightguard_jp> jharting: What's up?
[15:19:47] *** rruss has quit IRC
[15:19:52] <jharting> lightguard_jp: hi, was looking at the jaxrs example
[15:20:20] <jharting> lightguard_jp: how do you see the exception mapping in seam-rest and seam catch merge happenning?
[15:20:25] <lightguard_jp> Still trying to get it to deploy
[15:21:00] <jharting> I mean we can either : a) move it completely to catch including xml configuration b) modify the exception mapper in rest to use catch infrastructure
[15:22:00] <jharting> lightguard_jp: you and pete suggested one of these a while ago but I don't remember which one
[15:22:21] <lightguard_jp> If you're looking at my example there's a very simple bridge where I create an exception mapper for Throwable which then fires the event to catch.  There's one catch handler for throwable which will find the rest mapping for the exception type.  The ResponseBuilder is injected so it can be built up.  Once catch is done the response is returned with the correct status and messages.
[15:22:47] <jharting> lightguard_jp: yes
[15:22:49] <lightguard_jp> In my example it's kind of a mix of both :)
[15:23:11] <jharting> lightguard_jp: yes, the CatchBridge will definitely go to catch
[15:23:42] <jharting> lightguard_jp: not sure about the exceptionmapping, exceptionmapping configuration, errorMessageWrapper, etc..
[15:24:21] <jharting> lightguard_jp: I guess other modules will use catch as an infrastructure as well, so the latter aproach is possible I guess
[15:24:22] <lightguard_jp> I'm hoping I can just get the mapping configuration injected and pull out the one I need
[15:24:30] <lightguard_jp> Yeah, that's the idea
[15:26:26] <jharting> lightguard_jp: ok, my idea was that either all the configuration is moved to catch or in seam rest, there will be an @HandlesException bean observing events from catch and reacting based on excetion mapping configuration (build by seam rest in this case)
[15:28:18] <jharting> lightguard_jp: I will put it down into an e-mail and let pete and dan react as well.
[15:28:32] <lightguard_jp> New problem on GFv31 :( http://pastebin.com/LSpmygYe
[15:29:36] <lightguard_jp> jharting: We could move the exception mapping configuration stuff into a rest-catch-bridge jar
[15:30:30] <lightguard_jp> jharting: which is probably the more correct way of doing it, that way rest doesn't have to worry at all about any of the exception stuff
[15:30:50] <jharting> lightguard_jp: ok, so the bridge will have its own jar as opposed to being in the main catch jar, right?
[15:30:59] <lightguard_jp> Correct
[15:31:16] <jharting> lightguard_jp: ok, it makes sense
[15:31:25] <lightguard_jp> There will be lots of bridge jars: one for jsf, rest, persistence, etc
[15:31:37] <lightguard_jp> Not sure which project those will live in just yet though
[15:31:51] <jharting> lightguard_jp: is it in already?
[15:31:52] <lightguard_jp> At least that was my (and I think Dan's) thinking.  Pete may have other ideas though.
[15:31:59] <lightguard_jp> No.
[15:32:36] <lightguard_jp> As soon as I can get the example to deploy I'll release and then pull it out into it's own jar (the bridge stuff).
[15:32:48] <lightguard_jp> jharting: Does your example deploy on glassfish?
[15:33:04] <jharting> lightguard_jp: yes it does
[15:33:10] <jharting> lightguard_jp: tested 3.0.1 though
[15:34:08] <lightguard_jp> Crud.
[15:34:13] <lightguard_jp> I was closer in 3.0.1
[15:34:35] <lightguard_jp> I'm trying 3.1 and getting someting different
[15:34:39] <lightguard_jp> :(
[15:34:54] <lightguard_jp> Wait, I don't need jboss-logging if I'm deploying to 3.1 do I?
[15:35:10] <jharting> lightguard_jp: I think you do
[15:35:25] <lightguard_jp> 3.1 has weld 1.1 in it, which I think already has logging
[15:36:06] <lightguard_jp> or not
[15:42:44] <jharting> lightguard_jp: trying your app on GF 3.0.1, seems that the persistence module is causing problems
[15:43:04] <jharting> lightguard_jp: will try to deploy it without the module
[15:43:15] <lightguard_jp> It'll blow up at startup
[15:43:20] <lightguard_jp> I'm currently getting [#|2010-11-18T07:40:33.296-0700|SEVERE|glassfish3.0.1|org.apache.catalina.core.ContainerBase|_ThreadID=24;_ThreadName=Thread-1;|ContainerBase.addChild: start:
[15:43:24] <lightguard_jp> org.apache.catalina.LifecycleException: org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped
[15:46:17] <lightguard_jp> jharting: Ah, yep, I think you are right
[15:46:55] <jharting> lightguard_jp: I'm trying to replace the seam-persistence by EJBs, it should work then
[15:47:02] <jharting> lightguard_jp: temporarily
[15:47:05] <lightguard_jp> :)
[15:47:33] <lightguard_jp> stuartdouglas: Looks like persistence isn't working quite right the way I'm using it (or maybe I'm using it wrong)
[15:55:42] *** balunasj has joined #seam-dev
[15:57:14] <jharting> lightguard_jp: got it deployed
[15:57:39] <lightguard_jp> jharting: Just using ejbs?
[15:58:51] *** plenyi has quit IRC
[15:59:04] <jharting> lightguard_jp: yes, I removed seam-persistence for now, modified em injection points accordingly (switched to @PersistenceContext and made the ejbs), and removed two properties from the persistence.xml file (not sure if they had any effect)
[15:59:09] <jharting> lightguard_jp: can send you a patch
[15:59:33] <lightguard_jp> I think I have the same stuff, w/o the persistence.xml (what did you change)
[15:59:41] <lightguard_jp> Send me the patch for the persistence.xml
[16:00:27] <jharting> I simply removed the following properties:
[16:00:28] <jharting>          <property name="eclipselink.create-ddl-jdbc-file-name" value="seam-catch-jaxrs-create.sql"/>
[16:00:28] <jharting>          <property name="eclipselink.drop-ddl-jdbc-file-name" value="seam-catch-jaxrs-drop.sql"/>
[16:00:34] <jharting> since I havent found the files anywhere
[16:00:38] <lightguard_jp> Ah
[16:00:47] <lightguard_jp> I'm not sure where eclipselink puts those
[16:00:56] <lightguard_jp> Or if it deletes them once it runs them
[16:01:13] <jharting> it works for me even without listing them
[16:01:19] <jharting> tables are created/dropped
[16:01:36] <jharting> lightguard_jp: so IMHO you can ommit that
[16:02:06] <lightguard_jp> Yeah, most likely
[16:02:13] *** lincolnthree1 has quit IRC
[16:02:59] <lightguard_jp> Grr, still issues on my side.  Send me a full patch or a pull request
[16:04:12] <lightguard_jp> Seeding an app within the app isn't as easy as one would think
[16:12:03] *** rruss has joined #seam-dev
[16:14:26] <jharting> lightguard_jp: I'm back, here is the patch http://pastebin.com/gusbQUZp
[16:14:56] <lightguard_jp> jharting: Thanks
[16:15:30] <jharting> lightguard_jp: yw, let me know once you get the bridge package in
[16:16:25] <lightguard_jp> jharting: Probably next week, once this example is done I think I'll release then work on the rest of the stuff like bridges.  Could you please add a jira for the rest bridge?
[16:16:34] <lightguard_jp> jira.jboss.org/browse/seamcatch
[16:20:00] <jharting> https://jira.jboss.org/browse/SEAMCATCH-6
[16:20:02] <jbossbot> jira [SEAMCATCH-6] Create a JAX-RS bridge [Open, Major, Jason Porter] https://jira.jboss.org/browse/SEAMCATCH-6
[16:20:29] <lightguard_jp> Thanks
[16:20:37] <jharting> btw, once you deploy the app, you also need to tune the JAXB configuration a bit as I was getting circular dependencies
[16:20:59] <jharting> @XmlTransient to one of the relation sides
[16:21:14] <lightguard_jp> Ah
[16:21:23] <lightguard_jp> Caused by: java.lang.IllegalArgumentException: Object: org.jboss.seam.exception.control.example.jaxrs.entity.Author@606e685a is not a known entity type. on my box, still more debugging :)
[16:22:02] <jharting> lightguard_jp: seen this as well, restarted GF and redeployed the app and it disapeared
[16:22:18] <lightguard_jp> okay
[16:22:38] <lightguard_jp> Are the circular refs because of the many-to-many?
[16:27:14] <lightguard_jp> jharting: I guess it really doesn't matter which, does it?
[16:28:52] <lightguard_jp> Wow, exceptions left and right :(
[16:29:48] <lightguard_jp> jharting: Seen this one? WELD-001408 Injection point has unsatisfied dependencies.  Injection point:  field org.jboss.weld.extensions.el.ELContextProducer.resolver;  Qualifiers:  [ at org dot jboss.weld.extensions.el.Composite()]
[16:32:46] <jharting> lightguard_jp: nope, that's weird
[16:34:01] <jharting> lightguard_jp: WELDX 1.1.0.Beta1 was deployed in the app in my case
[16:35:07] *** tsurdilo has joined #seam-dev
[16:38:10] <lightguard_jp> jharting: Looks like it may be derby related
[16:38:28] <lightguard_jp> I'm not that familiar with derby, how can I get in and drop the tables manually?
[16:38:46] *** emmanuel has joined #seam-dev
[16:39:24] <jharting> lightguard_jp: you can do it easily from NetBeans
[16:39:46] <jharting> lightguard_jp: do not know other way
[16:39:52] <lightguard_jp> :)
[16:41:51] *** mbg has joined #seam-dev
[16:42:34] *** jharting has quit IRC
[17:01:33] *** oskutka has quit IRC
[17:03:40] *** marekn has left #seam-dev
[17:04:12] *** marekn has joined #seam-dev
[17:07:07] *** emmanuel has quit IRC
[17:07:23] *** rruss has quit IRC
[17:09:08] *** emmanuel has joined #seam-dev
[17:22:24] *** rruss has joined #seam-dev
[17:31:38] *** emmanuel has quit IRC
[17:46:39] *** lightguard_jp has quit IRC
[17:47:36] *** mbg has quit IRC
[17:48:39] *** mbg has joined #seam-dev
[17:48:39] *** mbg has quit IRC
[17:48:39] *** mbg has joined #seam-dev
[18:03:52] *** epbernard has joined #seam-dev
[18:03:52] *** epbernard is now known as emmanuel
[18:03:55] *** emmanuel has quit IRC
[18:07:44] *** balunasj has quit IRC
[18:18:17] *** lincolnthree1 has joined #seam-dev
[18:22:46] *** aslak has joined #seam-dev
[18:31:03] *** mbg has quit IRC
[18:40:28] *** mbg has joined #seam-dev
[18:47:20] <jbossbot> git [forge] push master f84a4c0.. Lincoln Baxter, III fixed bad FSHParser imports
[18:47:20] <jbossbot> git [forge] push master ec7931f.. Lincoln Baxter, III Added properties to Dependency facet
[18:47:20] <jbossbot> git [forge] push master URL: http://github.com/seam/forge/compare/dce6a8c...ec7931f
[18:47:58] *** rruss has quit IRC
[18:54:18] <jbossbot> git [forge] push master d943046.. Lincoln Baxter, III fixed properties not being added to pom, woops
[18:54:18] <jbossbot> git [forge] push master URL: http://github.com/seam/forge/compare/ec7931f...d943046
[19:00:59] *** lightguard_jp has joined #seam-dev
[19:20:38] *** lincolnthree1 has quit IRC
[19:29:40] *** lincolnthree1 has joined #seam-dev
[19:52:23] *** kpiwko has quit IRC
[20:02:12] *** lincolnthree1 has left #seam-dev
[20:21:37] *** rruss has joined #seam-dev
[20:21:45] *** rruss has quit IRC
[20:28:37] *** oskutka has joined #seam-dev
[20:38:49] *** oskutka has quit IRC
[20:47:41] <lightguard_jp> I guess everyone's still heavily involved in devoxx
[21:19:59] *** tsurdilo has quit IRC
[21:20:31] *** tsurdilo has joined #seam-dev
[21:24:38] <arbi> does Spring core team attend devoxx as well?
[21:26:25] <arbi> http://devoxx.com/display/Devoxx2K10/Sponsors so yes
[21:57:59] *** aslak has quit IRC
[22:03:45] *** lincolnthree1 has joined #seam-dev
[22:03:47] *** lincolnthree1 has left #seam-dev
[22:07:31] <lightguard_jp> :( same error on my example with a fresh glassfish install
[23:18:48] *** jharting has joined #seam-dev
[23:18:51] *** jharting has quit IRC





top