Maybe we should create an OpenSessionInViewInterceptor which does essentially the same exact thing that the OpenSessionInViewFilter does, but around service method calls. Spring has something like that. Maybe we could just "borrow" some logic from it, like I did for my OpenSessionInViewFilter.
-----Original Message----- From: James Carman [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 19, 2006 11:07 AM To: 'Tapestry users' Subject: RE: honeycomb: acquiring session not in a tapestry page We may also need a way to "intercept" the jobs to add in support for other stuff (like opening/closing hibernate sessions). -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 19, 2006 11:00 AM To: 'Tapestry users' Subject: RE: honeycomb: acquiring session not in a tapestry page OK guys, it took me some time to move to the shiny new javaforge. If you want to move back, you do the dirty work ;). Meanwhile, I add you to the team manually ... I've just checked the code. It seems straightforward to do. The scheduler is a service and the Runnable has a wrapper to fire hiveminds thread-events when a task starts/finishes. makes sense. > -----Original Message----- > From: James Carman [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 19, 2006 4:52 PM > To: 'Tapestry users' > Subject: RE: honeycomb: acquiring session not in a tapestry page > > > I don't know if Jesse has told you or not yet, but we plan to move the > Honeycomb over to SourceForge. I was trying to join the > project, but we > couldn't figure out how to do it at JavaForge. It seems to > need some work. > On the projects list page, a whole bunch of projects show up > for me with the > "leave" link next to them (honeycomb was one of them). I > only belong to one > project. So, I clicked on "leave" to leave honeycomb so that > maybe I could > re-join. But, the "leave" link just kept appearing. There > is an existing > Honeycomb project at sourceforge, but it has something to do > with BeOS and > hasn't been maintained for a LONG TIME. I think they approved Jesse's > request to take over the name. They just haven't done what > it takes to give > him control over it yet, I don't think. > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 19, 2006 10:42 AM > To: 'Tapestry users' > Subject: RE: honeycomb: acquiring session not in a tapestry page > > don't really know. I have to admit that I did all my scheduling with > cron/java.util.Timer up to now ... > And I seem to have blown javaforge by trying to browse the repo ??? ;) > > > -----Original Message----- > > From: James Carman [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, April 19, 2006 4:16 PM > > To: 'Tapestry users' > > Subject: RE: honeycomb: acquiring session not in a tapestry page > > > > > > I'm looking at the Quartz API now trying to get ideas of how > > to set it up. > > Would you set up a Scheduler as a service? > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, April 19, 2006 10:00 AM > > To: 'Tapestry users' > > Subject: RE: honeycomb: acquiring session not in a tapestry page > > > > > > > > > -----Original Message----- > > > From: James Carman [mailto:[EMAIL PROTECTED] > > > Sent: Wednesday, April 19, 2006 3:54 PM > > > To: Tapestry users > > > Subject: Re: honeycomb: acquiring session not in a tapestry page > > > > > > > > > How do you run your background process? > > > > > > > good question - actually, I'd like to see some quartz integration in > > honeycomb anyway. There should even be some code by Jesse > in the repo > > waiting to be incorporated. > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
