[Lift] Re: Db4o Integration
On Mon, Oct 6, 2008 at 7:53 AM, David Pollak <[EMAIL PROTECTED]> wrote: > Unfortunately, DB4O's choice of license and business model drives them away > from JVM-land and toward CLR-land. > > I've had pretty extensive chats with the DB4O people and would really like > to do something with them related to Lift, but it's a huge challenge. > > DB4O is dual-licensed under a GPL variant and commercial. In order to do > any commercial development at all (according to the DB4O sales people), one > must buy a commercial license. But buying a commercial license is hard. I > spent more than a week in round-and-round discussions with DB4O sales just > to get a price list. Basically, it was going to cost about $10K for my > development licenses. This was a development license just to explore and > see if DB4O was right for the project that I was working on. Yes, I know... > I could have just downloaded the code and tested it out, but I believe in > abiding by license terms. > > What this means is that people can't just play with DB4O in a commercial > setting... they have to plunk down cash. This is normal in Microsoft/CLR > land, but most JVM-based projects, even in corporate settings, are > prototyped with open source code. When things get closer to production, the > companies buy support and indemnification from the open source vendors. > > So, I'd like to do something with DB4O. They'd like to do something with > Lift. But nobody's found the right ground or the right business model to > make things work. Sigh. > > David Forgive my ignorance, but if all you're talking about is prototyping, wouldn't using the GPL'ed code okay? As I understand it, the GPL doesn't kick in until you actually go to distribute the software. Also, since Lift is server-side, doesn't that let it off the hook for most uses? Kris --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Db4o Integration
efleming969 wrote: > David, I've browsed your past discussions on this topic and didn't > quite get this point from them. So, according to their interpretation > of the GPL, I cannot develop an application using Lift+Db4o, as a > consultant, for my customer's internal use? > There are two issues at work here. The first is that one cannot mix Apache 2.0 licensed code with GPL 2.0 code. This is *not* an issue with DB4O. They are happy to allow Lift and DB4O code to be mixed in projects that are otherwise free. So, my past discussions (rants) about the GPL and Apache 2.0 licenses are not material to this discussion. The way that the DB4O sales person interpreted the license is far more restrictive in terms of what "distribution" means than any other interpretation I'm familiar with. However, the DB4O execs that I spoke with subsequent to the sales person did not disclaim her interpretation, so I've got to take it that as a corporate policy, DB4O is trying to get revenue from *any* non-free use of DB4O. > I guess my existing app using wicket+db4o is also in violation. > bummer :-( > > On Oct 6, 11:40 am, David Pollak <[EMAIL PROTECTED]> wrote: > >> Kris Nuttycombe wrote: >> >>> On Mon, Oct 6, 2008 at 7:53 AM, David Pollak <[EMAIL PROTECTED]> wrote: >>> Unfortunately, DB4O's choice of license and business model drives them away from JVM-land and toward CLR-land. I've had pretty extensive chats with the DB4O people and would really like to do something with them related to Lift, but it's a huge challenge. DB4O is dual-licensed under a GPL variant and commercial. In order to do any commercial development at all (according to the DB4O sales people), one must buy a commercial license. But buying a commercial license is hard. I spent more than a week in round-and-round discussions with DB4O sales just to get a price list. Basically, it was going to cost about $10K for my development licenses. This was a development license just to explore and see if DB4O was right for the project that I was working on. Yes, I know... I could have just downloaded the code and tested it out, but I believe in abiding by license terms. What this means is that people can't just play with DB4O in a commercial setting... they have to plunk down cash. This is normal in Microsoft/CLR land, but most JVM-based projects, even in corporate settings, are prototyped with open source code. When things get closer to production, the companies buy support and indemnification from the open source vendors. So, I'd like to do something with DB4O. They'd like to do something with Lift. But nobody's found the right ground or the right business model to make things work. Sigh. David >>> Forgive my ignorance, but if all you're talking about is prototyping, >>> wouldn't using the GPL'ed code okay? As I understand it, the GPL >>> doesn't kick in until you actually go to distribute the software. >>> Also, since Lift is server-side, doesn't that let it off the hook for >>> most uses? >>> >> According to the DB4O sales person, they interpret "distribution" to >> include putting in a source repository that is not hosted on the >> company's servers or having non-employee consultants access the code. >> It's an extremely aggressive interpretation. It makes exploration >> difficult. Plus, many companies have an absolute bar against any GPL >> code entering any project. >> >> >>> Kris >>> > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Db4o Integration
David, I've browsed your past discussions on this topic and didn't quite get this point from them. So, according to their interpretation of the GPL, I cannot develop an application using Lift+Db4o, as a consultant, for my customer's internal use? I guess my existing app using wicket+db4o is also in violation. bummer :-( On Oct 6, 11:40 am, David Pollak <[EMAIL PROTECTED]> wrote: > Kris Nuttycombe wrote: > > On Mon, Oct 6, 2008 at 7:53 AM, David Pollak <[EMAIL PROTECTED]> wrote: > > >> Unfortunately, DB4O's choice of license and business model drives them away > >> from JVM-land and toward CLR-land. > > >> I've had pretty extensive chats with the DB4O people and would really like > >> to do something with them related to Lift, but it's a huge challenge. > > >> DB4O is dual-licensed under a GPL variant and commercial. In order to do > >> any commercial development at all (according to the DB4O sales people), one > >> must buy a commercial license. But buying a commercial license is hard. I > >> spent more than a week in round-and-round discussions with DB4O sales just > >> to get a price list. Basically, it was going to cost about $10K for my > >> development licenses. This was a development license just to explore and > >> see if DB4O was right for the project that I was working on. Yes, I > >> know... > >> I could have just downloaded the code and tested it out, but I believe in > >> abiding by license terms. > > >> What this means is that people can't just play with DB4O in a commercial > >> setting... they have to plunk down cash. This is normal in Microsoft/CLR > >> land, but most JVM-based projects, even in corporate settings, are > >> prototyped with open source code. When things get closer to production, > >> the > >> companies buy support and indemnification from the open source vendors. > > >> So, I'd like to do something with DB4O. They'd like to do something with > >> Lift. But nobody's found the right ground or the right business model to > >> make things work. Sigh. > > >> David > > > Forgive my ignorance, but if all you're talking about is prototyping, > > wouldn't using the GPL'ed code okay? As I understand it, the GPL > > doesn't kick in until you actually go to distribute the software. > > Also, since Lift is server-side, doesn't that let it off the hook for > > most uses? > > According to the DB4O sales person, they interpret "distribution" to > include putting in a source repository that is not hosted on the > company's servers or having non-employee consultants access the code. > It's an extremely aggressive interpretation. It makes exploration > difficult. Plus, many companies have an absolute bar against any GPL > code entering any project. > > > Kris --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Db4o Integration
Kris Nuttycombe wrote: > On Mon, Oct 6, 2008 at 7:53 AM, David Pollak <[EMAIL PROTECTED]> wrote: > > >> Unfortunately, DB4O's choice of license and business model drives them away >> from JVM-land and toward CLR-land. >> >> I've had pretty extensive chats with the DB4O people and would really like >> to do something with them related to Lift, but it's a huge challenge. >> >> DB4O is dual-licensed under a GPL variant and commercial. In order to do >> any commercial development at all (according to the DB4O sales people), one >> must buy a commercial license. But buying a commercial license is hard. I >> spent more than a week in round-and-round discussions with DB4O sales just >> to get a price list. Basically, it was going to cost about $10K for my >> development licenses. This was a development license just to explore and >> see if DB4O was right for the project that I was working on. Yes, I know... >> I could have just downloaded the code and tested it out, but I believe in >> abiding by license terms. >> >> What this means is that people can't just play with DB4O in a commercial >> setting... they have to plunk down cash. This is normal in Microsoft/CLR >> land, but most JVM-based projects, even in corporate settings, are >> prototyped with open source code. When things get closer to production, the >> companies buy support and indemnification from the open source vendors. >> >> So, I'd like to do something with DB4O. They'd like to do something with >> Lift. But nobody's found the right ground or the right business model to >> make things work. Sigh. >> >> David >> > > Forgive my ignorance, but if all you're talking about is prototyping, > wouldn't using the GPL'ed code okay? As I understand it, the GPL > doesn't kick in until you actually go to distribute the software. > Also, since Lift is server-side, doesn't that let it off the hook for > most uses? > According to the DB4O sales person, they interpret "distribution" to include putting in a source repository that is not hosted on the company's servers or having non-employee consultants access the code. It's an extremely aggressive interpretation. It makes exploration difficult. Plus, many companies have an absolute bar against any GPL code entering any project. > Kris > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Db4o Integration
efleming969 wrote:
> I saw that syntax on a blog a few days ago, but I did not try it with
> version 7.6.
>
> The db4o team has been really dedicated to C# and LINQ in the past few
> versions, to I would image the library will become more friendly to
> languageas like Scala.
>
Unfortunately, DB4O's choice of license and business model drives them
away from JVM-land and toward CLR-land.
I've had pretty extensive chats with the DB4O people and would really
like to do something with them related to Lift, but it's a huge challenge.
DB4O is dual-licensed under a GPL variant and commercial. In order to
do any commercial development at all (according to the DB4O sales
people), one must buy a commercial license. But buying a commercial
license is hard. I spent more than a week in round-and-round
discussions with DB4O sales just to get a price list. Basically, it was
going to cost about $10K for my development licenses. This was a
development license just to explore and see if DB4O was right for the
project that I was working on. Yes, I know... I could have just
downloaded the code and tested it out, but I believe in abiding by
license terms.
What this means is that people can't just play with DB4O in a commercial
setting... they have to plunk down cash. This is normal in
Microsoft/CLR land, but most JVM-based projects, even in corporate
settings, are prototyped with open source code. When things get closer
to production, the companies buy support and indemnification from the
open source vendors.
So, I'd like to do something with DB4O. They'd like to do something
with Lift. But nobody's found the right ground or the right business
model to make things work. Sigh.
David
> On Oct 6, 12:08 am, "Bjarte S. Karlsen"
> <[EMAIL PROTECTED]> wrote:
>
>> efleming969:
>>
>>
>>
>>
>>> I've added a project to github under the name of liftyourdb4o.
>>>
>> I looked at db4o in the #scala channel and got this nice query method to
>> work. It needs db4o 7.6 though (I tried with 7.4 and it fails since the
>> match method retuns an Object and not a T), since it has a fix that allows
>> match to get an Object.
>>
>> def query[T](filter:T => boolean) = {
>> db.query(new Predicate[T]() {
>> def `match`(entry: T): boolean = {
>> filter(entry)
>> }
>> });
>> }
>>
>> So basically you could do
>>
>> val result = query[Course](_.name.equals("Scala"))
>>
>> --
>> With kind regards / Med vennlig hilsen,
>> Bjarte Stien Karlsen (GPG: 0x626B2F3A)
>> To find out the limits of the possible you have to go beyond them into the
>> impossible.
>>
> >
>
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: Db4o Integration
I saw that syntax on a blog a few days ago, but I did not try it with
version 7.6.
The db4o team has been really dedicated to C# and LINQ in the past few
versions, to I would image the library will become more friendly to
languageas like Scala.
On Oct 6, 12:08 am, "Bjarte S. Karlsen"
<[EMAIL PROTECTED]> wrote:
> efleming969:
>
>
>
> > I've added a project to github under the name of liftyourdb4o.
>
> I looked at db4o in the #scala channel and got this nice query method to
> work. It needs db4o 7.6 though (I tried with 7.4 and it fails since the match
> method retuns an Object and not a T), since it has a fix that allows match to
> get an Object.
>
> def query[T](filter:T => boolean) = {
> db.query(new Predicate[T]() {
> def `match`(entry: T): boolean = {
> filter(entry)
> }
> });
> }
>
> So basically you could do
>
> val result = query[Course](_.name.equals("Scala"))
>
> --
> With kind regards / Med vennlig hilsen,
> Bjarte Stien Karlsen (GPG: 0x626B2F3A)
> To find out the limits of the possible you have to go beyond them into the
> impossible.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: Db4o Integration
Funny, I was just fixing the link to the lift's google groups on the
front page of the wiki and did not even think of add your tip. Doing
it right now.
On Oct 5, 3:35 pm, "David Pollak" <[EMAIL PROTECTED]>
wrote:
> On Sun, Oct 5, 2008 at 8:16 AM, efleming969 <[EMAIL PROTECTED]> wrote:
>
> > @david
>
> > thanks, that did the trick.
>
> Great... did you add this to the Lift wiki? :-)
>
>
>
>
>
> > On Oct 3, 12:51 pm, "David Pollak" <[EMAIL PROTECTED]>
> > wrote:
> > > def myUnloader(): Unit = {
> > > ... run when Lift is being unloaded
>
> > > }
>
> > > LiftRules.unloadHooks += myUnloader _
>
> > > On Fri, Oct 3, 2008 at 8:56 AM, efleming969 <[EMAIL PROTECTED]>
> > wrote:
>
> > > > I'm trying to convert a scala + wicket + db4o application to Lift +
> > > > db4o. I'm using a standard ServletContextListener to shutdown my
> > > > database file.
>
> > > > What is the recommended method for ContextListener type code in Lift.
> > > > Should I just configure my ContextListener as normal or is there a
> > > > special place for this type of code?
>
> > > > Thanks
>
> > > --
> > > Lift, the simply functional web frameworkhttp://liftweb.net
> > > Collaborative Task Managementhttp://much4.us
> > > Follow me:http://twitter.com/dpp
> > > Git some:http://github.com/dpp
>
> --
> Lift, the simply functional web frameworkhttp://liftweb.net
> Collaborative Task Managementhttp://much4.us
> Follow me:http://twitter.com/dpp
> Git some:http://github.com/dpp
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: Db4o Integration
efleming969:
>
> I've added a project to github under the name of liftyourdb4o.
>
I looked at db4o in the #scala channel and got this nice query method to work.
It needs db4o 7.6 though (I tried with 7.4 and it fails since the match method
retuns an Object and not a T), since it has a fix that allows match to get an
Object.
def query[T](filter:T => boolean) = {
db.query(new Predicate[T]() {
def `match`(entry: T): boolean = {
filter(entry)
}
});
}
So basically you could do
val result = query[Course](_.name.equals("Scala"))
--
With kind regards / Med vennlig hilsen,
Bjarte Stien Karlsen (GPG: 0x626B2F3A)
To find out the limits of the possible you have to go beyond them into the
impossible.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: Db4o Integration
On Sun, Oct 5, 2008 at 8:49 PM, efleming969 <[EMAIL PROTECTED]> wrote:
>
> I've added a project to github under the name of liftyourdb4o.
>
> I'm not sure where or if it would be appropriate to add a link to my
> project on the wiki, so maybe I'll wait on that for a bit.
It would be appropriate.
>
>
> On Oct 5, 3:44 pm, efleming969 <[EMAIL PROTECTED]> wrote:
> > Funny, I was just fixing the link to the lift's google groups on the
> > front page of the wiki and did not even think of add your tip. Doing
> > it right now.
> >
> > On Oct 5, 3:35 pm, "David Pollak" <[EMAIL PROTECTED]>
> > wrote:
> >
> > > On Sun, Oct 5, 2008 at 8:16 AM, efleming969 <[EMAIL PROTECTED]>
> wrote:
> >
> > > > @david
> >
> > > > thanks, that did the trick.
> >
> > > Great... did you add this to the Lift wiki? :-)
> >
> > > > On Oct 3, 12:51 pm, "David Pollak" <[EMAIL PROTECTED]>
> > > > wrote:
> > > > > def myUnloader(): Unit = {
> > > > > ... run when Lift is being unloaded
> >
> > > > > }
> >
> > > > > LiftRules.unloadHooks += myUnloader _
> >
> > > > > On Fri, Oct 3, 2008 at 8:56 AM, efleming969 <[EMAIL PROTECTED]
> >
> > > > wrote:
> >
> > > > > > I'm trying to convert a scala + wicket + db4o application to Lift
> +
> > > > > > db4o. I'm using a standard ServletContextListener to shutdown my
> > > > > > database file.
> >
> > > > > > What is the recommended method for ContextListener type code in
> Lift.
> > > > > > Should I just configure my ContextListener as normal or is there
> a
> > > > > > special place for this type of code?
> >
> > > > > > Thanks
> >
> > > > > --
> > > > > Lift, the simply functional web frameworkhttp://liftweb.net
> > > > > Collaborative Task Managementhttp://much4.us
> > > > > Follow me:http://twitter.com/dpp
> > > > > Git some:http://github.com/dpp
> >
> > > --
> > > Lift, the simply functional web frameworkhttp://liftweb.net
> > > Collaborative Task Managementhttp://much4.us
> > > Follow me:http://twitter.com/dpp
> > > Git some:http://github.com/dpp
> >
>
--
Lift, the simply functional web framework http://liftweb.net
Collaborative Task Management http://much4.us
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: Db4o Integration
I've added a project to github under the name of liftyourdb4o.
I'm not sure where or if it would be appropriate to add a link to my
project on the wiki, so maybe I'll wait on that for a bit.
On Oct 5, 3:44 pm, efleming969 <[EMAIL PROTECTED]> wrote:
> Funny, I was just fixing the link to the lift's google groups on the
> front page of the wiki and did not even think of add your tip. Doing
> it right now.
>
> On Oct 5, 3:35 pm, "David Pollak" <[EMAIL PROTECTED]>
> wrote:
>
> > On Sun, Oct 5, 2008 at 8:16 AM, efleming969 <[EMAIL PROTECTED]> wrote:
>
> > > @david
>
> > > thanks, that did the trick.
>
> > Great... did you add this to the Lift wiki? :-)
>
> > > On Oct 3, 12:51 pm, "David Pollak" <[EMAIL PROTECTED]>
> > > wrote:
> > > > def myUnloader(): Unit = {
> > > > ... run when Lift is being unloaded
>
> > > > }
>
> > > > LiftRules.unloadHooks += myUnloader _
>
> > > > On Fri, Oct 3, 2008 at 8:56 AM, efleming969 <[EMAIL PROTECTED]>
> > > wrote:
>
> > > > > I'm trying to convert a scala + wicket + db4o application to Lift +
> > > > > db4o. I'm using a standard ServletContextListener to shutdown my
> > > > > database file.
>
> > > > > What is the recommended method for ContextListener type code in Lift.
> > > > > Should I just configure my ContextListener as normal or is there a
> > > > > special place for this type of code?
>
> > > > > Thanks
>
> > > > --
> > > > Lift, the simply functional web frameworkhttp://liftweb.net
> > > > Collaborative Task Managementhttp://much4.us
> > > > Follow me:http://twitter.com/dpp
> > > > Git some:http://github.com/dpp
>
> > --
> > Lift, the simply functional web frameworkhttp://liftweb.net
> > Collaborative Task Managementhttp://much4.us
> > Follow me:http://twitter.com/dpp
> > Git some:http://github.com/dpp
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: Db4o Integration
On Sun, Oct 5, 2008 at 8:16 AM, efleming969 <[EMAIL PROTECTED]> wrote:
>
> @david
>
> thanks, that did the trick.
Great... did you add this to the Lift wiki? :-)
>
>
> On Oct 3, 12:51 pm, "David Pollak" <[EMAIL PROTECTED]>
> wrote:
> > def myUnloader(): Unit = {
> > ... run when Lift is being unloaded
> >
> > }
> >
> > LiftRules.unloadHooks += myUnloader _
> >
> > On Fri, Oct 3, 2008 at 8:56 AM, efleming969 <[EMAIL PROTECTED]>
> wrote:
> >
> > > I'm trying to convert a scala + wicket + db4o application to Lift +
> > > db4o. I'm using a standard ServletContextListener to shutdown my
> > > database file.
> >
> > > What is the recommended method for ContextListener type code in Lift.
> > > Should I just configure my ContextListener as normal or is there a
> > > special place for this type of code?
> >
> > > Thanks
> >
> > --
> > Lift, the simply functional web frameworkhttp://liftweb.net
> > Collaborative Task Managementhttp://much4.us
> > Follow me:http://twitter.com/dpp
> > Git some:http://github.com/dpp
> >
>
--
Lift, the simply functional web framework http://liftweb.net
Collaborative Task Management http://much4.us
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: Db4o Integration
On Sun, Oct 5, 2008 at 8:27 AM, efleming969 <[EMAIL PROTECTED]> wrote:
>
> @bjarte and @charles
>
> Sure, I've been learning Scala for a few months now and was trying to
> create a wicket application with db4o and kept running into problems
> that I did not know how to solve in Scala. Since Lift is witten in
> Scala, I thought my learning curve could be about the same, so here I
> am. I will definitely post any experiences I come accross and I'll
> start a sample project in github, for anyone interested. Keep in mind
> that I don't know Scala or Lift very well and therefore cannot be
> trusted with correct implementations.
Looking at how newbies approach Lift will help us make Lift more
approachable.
>
>
> On Oct 5, 10:16 am, efleming969 <[EMAIL PROTECTED]> wrote:
> > @david
> >
> > thanks, that did the trick.
> >
> > On Oct 3, 12:51 pm, "David Pollak" <[EMAIL PROTECTED]>
> > wrote:
> >
> > > def myUnloader(): Unit = {
> > > ... run when Lift is being unloaded
> >
> > > }
> >
> > > LiftRules.unloadHooks += myUnloader _
> >
> > > On Fri, Oct 3, 2008 at 8:56 AM, efleming969 <[EMAIL PROTECTED]>
> wrote:
> >
> > > > I'm trying to convert a scala + wicket + db4o application to Lift +
> > > > db4o. I'm using a standard ServletContextListener to shutdown my
> > > > database file.
> >
> > > > What is the recommended method for ContextListener type code in Lift.
> > > > Should I just configure my ContextListener as normal or is there a
> > > > special place for this type of code?
> >
> > > > Thanks
> >
> > > --
> > > Lift, the simply functional web frameworkhttp://liftweb.net
> > > Collaborative Task Managementhttp://much4.us
> > > Follow me:http://twitter.com/dpp
> > > Git some:http://github.com/dpp
> >
>
--
Lift, the simply functional web framework http://liftweb.net
Collaborative Task Management http://much4.us
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: Db4o Integration
@david
thanks, that did the trick.
On Oct 3, 12:51 pm, "David Pollak" <[EMAIL PROTECTED]>
wrote:
> def myUnloader(): Unit = {
> ... run when Lift is being unloaded
>
> }
>
> LiftRules.unloadHooks += myUnloader _
>
> On Fri, Oct 3, 2008 at 8:56 AM, efleming969 <[EMAIL PROTECTED]> wrote:
>
> > I'm trying to convert a scala + wicket + db4o application to Lift +
> > db4o. I'm using a standard ServletContextListener to shutdown my
> > database file.
>
> > What is the recommended method for ContextListener type code in Lift.
> > Should I just configure my ContextListener as normal or is there a
> > special place for this type of code?
>
> > Thanks
>
> --
> Lift, the simply functional web frameworkhttp://liftweb.net
> Collaborative Task Managementhttp://much4.us
> Follow me:http://twitter.com/dpp
> Git some:http://github.com/dpp
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: Db4o Integration
That sounds great. It would be difficult for your understanding of Lift
and Scala to be any worse than mine. :-)
Chas.
efleming969 wrote:
> @bjarte and @charles
>
> Sure, I've been learning Scala for a few months now and was trying to
> create a wicket application with db4o and kept running into problems
> that I did not know how to solve in Scala. Since Lift is witten in
> Scala, I thought my learning curve could be about the same, so here I
> am. I will definitely post any experiences I come accross and I'll
> start a sample project in github, for anyone interested. Keep in mind
> that I don't know Scala or Lift very well and therefore cannot be
> trusted with correct implementations.
>
> On Oct 5, 10:16 am, efleming969 <[EMAIL PROTECTED]> wrote:
>> @david
>>
>> thanks, that did the trick.
>>
>> On Oct 3, 12:51 pm, "David Pollak" <[EMAIL PROTECTED]>
>> wrote:
>>
>>> def myUnloader(): Unit = {
>>> ... run when Lift is being unloaded
>>> }
>>> LiftRules.unloadHooks += myUnloader _
>>> On Fri, Oct 3, 2008 at 8:56 AM, efleming969 <[EMAIL PROTECTED]> wrote:
I'm trying to convert a scala + wicket + db4o application to Lift +
db4o. I'm using a standard ServletContextListener to shutdown my
database file.
What is the recommended method for ContextListener type code in Lift.
Should I just configure my ContextListener as normal or is there a
special place for this type of code?
Thanks
>>> --
>>> Lift, the simply functional web frameworkhttp://liftweb.net
>>> Collaborative Task Managementhttp://much4.us
>>> Follow me:http://twitter.com/dpp
>>> Git some:http://github.com/dpp
> >
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: Db4o Integration
@bjarte and @charles
Sure, I've been learning Scala for a few months now and was trying to
create a wicket application with db4o and kept running into problems
that I did not know how to solve in Scala. Since Lift is witten in
Scala, I thought my learning curve could be about the same, so here I
am. I will definitely post any experiences I come accross and I'll
start a sample project in github, for anyone interested. Keep in mind
that I don't know Scala or Lift very well and therefore cannot be
trusted with correct implementations.
On Oct 5, 10:16 am, efleming969 <[EMAIL PROTECTED]> wrote:
> @david
>
> thanks, that did the trick.
>
> On Oct 3, 12:51 pm, "David Pollak" <[EMAIL PROTECTED]>
> wrote:
>
> > def myUnloader(): Unit = {
> > ... run when Lift is being unloaded
>
> > }
>
> > LiftRules.unloadHooks += myUnloader _
>
> > On Fri, Oct 3, 2008 at 8:56 AM, efleming969 <[EMAIL PROTECTED]> wrote:
>
> > > I'm trying to convert a scala + wicket + db4o application to Lift +
> > > db4o. I'm using a standard ServletContextListener to shutdown my
> > > database file.
>
> > > What is the recommended method for ContextListener type code in Lift.
> > > Should I just configure my ContextListener as normal or is there a
> > > special place for this type of code?
>
> > > Thanks
>
> > --
> > Lift, the simply functional web frameworkhttp://liftweb.net
> > Collaborative Task Managementhttp://much4.us
> > Follow me:http://twitter.com/dpp
> > Git some:http://github.com/dpp
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: Db4o Integration
This is something I've been very interested in, but have been too swamped to get very far with. Please keep us posted. Chas. efleming969 wrote: > I'm trying to convert a scala + wicket + db4o application to Lift + > db4o. I'm using a standard ServletContextListener to shutdown my > database file. > > What is the recommended method for ContextListener type code in Lift. > Should I just configure my ContextListener as normal or is there a > special place for this type of code? > > Thanks > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Db4o Integration
efleming969: > > I'm trying to convert a scala + wicket + db4o application to Lift + > db4o. I'm using a standard ServletContextListener to shutdown my > database file. This sounds really cool. Are you able to share this when you are done? Or blog a tutorial about it? -- With kind regards / Med vennlig hilsen, Bjarte Stien Karlsen (GPG: 0x626B2F3A) To find out the limits of the possible you have to go beyond them into the impossible. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Db4o Integration
def myUnloader(): Unit = {
... run when Lift is being unloaded
}
LiftRules.unloadHooks += myUnloader _
On Fri, Oct 3, 2008 at 8:56 AM, efleming969 <[EMAIL PROTECTED]> wrote:
>
> I'm trying to convert a scala + wicket + db4o application to Lift +
> db4o. I'm using a standard ServletContextListener to shutdown my
> database file.
>
> What is the recommended method for ContextListener type code in Lift.
> Should I just configure my ContextListener as normal or is there a
> special place for this type of code?
>
> Thanks
> >
>
--
Lift, the simply functional web framework http://liftweb.net
Collaborative Task Management http://much4.us
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
