[Lift] Re: OSGi support for Lift

[Heiko Seeberger]

If you pack everything into one bundle, this approach will work.

But then there is no real benefit from running on OSGi. What we really need
is Lift apps made up from several bundles. And that will be still some work
...

Heiko

2009/7/23 Kjetil Valstadsve 

>
> The paxers (in the link above) seem to suggest that a compliant war
> will work with their WAR watchdog extender bundle, combined with
> (preferrably) the Pax Web HTTP Service. Has anyone tried this with a
> Lift app and succeeded?
>
> I don't feel like it's quite Spring-time on my projects yet, but if
> anyone has succeeded with that approach, please give a holler.
>
> Kjetil
>
> On Jun 10, 4:19 pm, Alex Boisvert  wrote:
> > Quick follow-up I've since discovered you can use the
> 'Webapp-Context:'
> > manifest entry with PAX Web Extender and Spring dm Server to achieve
> this.
> >
> >
> http://wiki.ops4j.org/display/paxweb/WAR+Extenderhttp://jira.springframework.org/browse/OSGI-468
> >
> > alex
> >
> > On Tue, May 12, 2009 at 12:48 PM, Alex Boisvert  >wrote:
> >
> >
> >
> > > Alright, thanks for your help!   I was mostly kicking the tires to get
> a
> > > taste for the upcoming OSGi integration.  I guess my main feedback at
> this
> > > point is that it would be nice to map the app into a non-root context
> of
> > > Jetty.   e.g.http://localhost:8080/examples-osgiinstead of directly
> > > underhttp://localhost:8080.This would make it possible to deploy
> > > several Lift apps onto the same OSGi container.
> >
> > > alex
> >
> > > On Tue, May 12, 2009 at 12:19 PM, Heiko Seeberger <
> > > heiko.seeber...@googlemail.com> wrote:
> >
> > >> Hm, does not look good :-(Thanx for trying and please keep on!
> > >> I have to deal with some build issues, and will take a look at that
> > >> tomorrow.
> >
> > >> Heiko
> >
> > >> 2009/5/12 Alex Boisvert 
> >
> > >>> That was it.  I pulled again from git and now I can start the
> > >>> examples-osgi app.
> >
> > >>> However, one more nitpick...  I can load index.htm but the snippet
> isn't
> > >>> rendered correctly because some resources can't be found.
> >
> > >>> e.g.
> > >>> [5285...@qtp-20735553-0 - /] INFO
> > >>> org.ops4j.pax.web.service.internal.HttpServiceContext - getting
> resource:
> > >>> [/templates-hidden/default.htm]
> > >>> [5285...@qtp-20735553-0 - /] INFO
> > >>> org.ops4j.pax.web.service.internal.HttpServiceContext - found
> resource: null
> >
> > >>> Is that normal?  I can see the following displayed:
> >
> > >>>   From a snippet: Hi, I am a snippet from a Lift-powered
> OSGi
> > >>> bundle!
> >
> > >>> but there's no surrounding   ...   so the
> > >>> browser complains.
> >
> > >>> alex
> >
> > >>> On Tue, May 12, 2009 at 11:24 AM, Heiko Seeberger <
> > >>> heiko.seeber...@googlemail.com> wrote:
> >
> >  When did you check out? I pushed again about one or two hours
> ago.From
> >  the log I can see that you use an old version of hello.composite.
> The new
> >  one should look like:
> >
> >  scan-bundle:wrap:mvn:javax.mail/mail/1.4
> >
> >  scan-bundle:wrap:mvn:javax.activation/activation/1.1
> >  ...
> >
> >  The "wrap:" is important. Pax Runner will wrap vanilla JARs into
> OSGi
> >  bundles.
> >
> >  Please pull again, that should help.
> >  Heiko
> >
> >  2009/5/12 Alex Boisvert 
> >
> > > Ok, I tried again based on your suggestion but I'm getting an error
> > > related to javax.mail:1.4 not being a valid bundle...
> >
> > >  -> Preparing framework [Felix 1.6.0]
> > >  -> Downloading bundles...
> > >  -> mvn:javax.mail/mail/1.4 : 388864 bytes @ [ 471kBps ]
> > > s @ [ 498kBps ]
> >
> > >  ___
> > > /  /
> > >/  / Oops, there has been a problem!
> > >   /  /
> > >  /__/   org.ops4j.pax.runner.platform.PlatformException:
> > > [mvn:javax.mail/mail/1.4] is not a valid bundle
> > > ___
> > >/__/ Use --log=debug to see details.
> >
> > > To be sure, I wiped my M2 repo under javax/mail and retried but I'm
> > > getting the same error.  Any idea?
> >
> > > I'm attaching the full log in case it's helpful.
> >
> > > alex
> >
> > > On Tue, May 12, 2009 at 10:08 AM, Heiko Seeberger <
> > > heiko.seeber...@googlemail.com> wrote:
> >
> > >> Hi Alex,
> > >> 2009/5/12 Alex Boisvert 
> >
> > >> I downloaded and ran PAX runner,
> >
> > >>> ./pax-run.sh --profiles=log,scala,felix.webconsole,web
> >
> > >>> then installed the examples-osgi bundle,
> >
> > >>> -> install
> > >>>
> file:///home/boisvert/git/liftweb/sites/examples-osgi/hello/target/examples
> -osgi-hello-1.1-SNAPSHOT.jar
> > >>> Bundle ID: 9
> > >>> -> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello -
> > >>> BundleEvent INSTALLED
> > >>> start 9
> > >>> -> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello -
> > >>> BundleEvent RESOLVED
> > >>> [FelixDispatchQueue] DEBUG net.liftweb.examples-os

[Lift] Re: OSGi support for Lift

[Kjetil Valstadsve]

The paxers (in the link above) seem to suggest that a compliant war
will work with their WAR watchdog extender bundle, combined with
(preferrably) the Pax Web HTTP Service. Has anyone tried this with a
Lift app and succeeded?

I don't feel like it's quite Spring-time on my projects yet, but if
anyone has succeeded with that approach, please give a holler.

Kjetil

On Jun 10, 4:19 pm, Alex Boisvert  wrote:
> Quick follow-up I've since discovered you can use the 'Webapp-Context:'
> manifest entry with PAX Web Extender and Spring dm Server to achieve this.
>
> http://wiki.ops4j.org/display/paxweb/WAR+Extenderhttp://jira.springframework.org/browse/OSGI-468
>
> alex
>
> On Tue, May 12, 2009 at 12:48 PM, Alex Boisvert wrote:
>
>
>
> > Alright, thanks for your help!   I was mostly kicking the tires to get a
> > taste for the upcoming OSGi integration.  I guess my main feedback at this
> > point is that it would be nice to map the app into a non-root context of
> > Jetty.   e.g.http://localhost:8080/examples-osgiinstead of directly
> > underhttp://localhost:8080.    This would make it possible to deploy
> > several Lift apps onto the same OSGi container.
>
> > alex
>
> > On Tue, May 12, 2009 at 12:19 PM, Heiko Seeberger <
> > heiko.seeber...@googlemail.com> wrote:
>
> >> Hm, does not look good :-(Thanx for trying and please keep on!
> >> I have to deal with some build issues, and will take a look at that
> >> tomorrow.
>
> >> Heiko
>
> >> 2009/5/12 Alex Boisvert 
>
> >>> That was it.  I pulled again from git and now I can start the
> >>> examples-osgi app.
>
> >>> However, one more nitpick...  I can load index.htm but the snippet isn't
> >>> rendered correctly because some resources can't be found.
>
> >>> e.g.
> >>> [5285...@qtp-20735553-0 - /] INFO
> >>> org.ops4j.pax.web.service.internal.HttpServiceContext - getting resource:
> >>> [/templates-hidden/default.htm]
> >>> [5285...@qtp-20735553-0 - /] INFO
> >>> org.ops4j.pax.web.service.internal.HttpServiceContext - found resource: 
> >>> null
>
> >>> Is that normal?  I can see the following displayed:
>
> >>>   From a snippet: Hi, I am a snippet from a Lift-powered OSGi
> >>> bundle!
>
> >>> but there's no surrounding   ...   so the
> >>> browser complains.
>
> >>> alex
>
> >>> On Tue, May 12, 2009 at 11:24 AM, Heiko Seeberger <
> >>> heiko.seeber...@googlemail.com> wrote:
>
>  When did you check out? I pushed again about one or two hours ago.From
>  the log I can see that you use an old version of hello.composite. The new
>  one should look like:
>
>  scan-bundle:wrap:mvn:javax.mail/mail/1.4
>
>  scan-bundle:wrap:mvn:javax.activation/activation/1.1
>  ...
>
>  The "wrap:" is important. Pax Runner will wrap vanilla JARs into OSGi
>  bundles.
>
>  Please pull again, that should help.
>  Heiko
>
>  2009/5/12 Alex Boisvert 
>
> > Ok, I tried again based on your suggestion but I'm getting an error
> > related to javax.mail:1.4 not being a valid bundle...
>
> >  -> Preparing framework [Felix 1.6.0]
> >  -> Downloading bundles...
> >  -> mvn:javax.mail/mail/1.4 : 388864 bytes @ [ 471kBps ]
> > s @ [ 498kBps ]
>
> >          ___
> >         /  /
> >        /  / Oops, there has been a problem!
> >       /  /
> >      /__/   org.ops4j.pax.runner.platform.PlatformException:
> > [mvn:javax.mail/mail/1.4] is not a valid bundle
> >     ___
> >    /__/     Use --log=debug to see details.
>
> > To be sure, I wiped my M2 repo under javax/mail and retried but I'm
> > getting the same error.  Any idea?
>
> > I'm attaching the full log in case it's helpful.
>
> > alex
>
> > On Tue, May 12, 2009 at 10:08 AM, Heiko Seeberger <
> > heiko.seeber...@googlemail.com> wrote:
>
> >> Hi Alex,
> >> 2009/5/12 Alex Boisvert 
>
> >> I downloaded and ran PAX runner,
>
> >>> ./pax-run.sh --profiles=log,scala,felix.webconsole,web
>
> >>> then installed the examples-osgi bundle,
>
> >>> -> install
> >>> file:///home/boisvert/git/liftweb/sites/examples-osgi/hello/target/examples
> >>>  -osgi-hello-1.1-SNAPSHOT.jar
> >>> Bundle ID: 9
> >>> -> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello -
> >>> BundleEvent INSTALLED
> >>> start 9
> >>> -> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello -
> >>> BundleEvent RESOLVED
> >>> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello -
> >>> BundleEvent STARTED
>
> >> OSGi support for Lift is implemented as "extender" in order to keep
> >> Lift "core" OSGi-agnostic. This means that there is a special add-on 
> >> bundle
> >> (lift-osgi) which must be installed and started. It will watch all 
> >> bundles
> >> if they are Lift-powered which means they have got a Lift-Config 
> >> manifest
> >> entry. If so, these bundles will be delegated to for resource look-ups
> >> (templates) and also (latest checkin) boo

[Lift] Re: OSGi support for Lift

[Alex Boisvert]

Quick follow-up I've since discovered you can use the 'Webapp-Context:'
manifest entry with PAX Web Extender and Spring dm Server to achieve this.

http://wiki.ops4j.org/display/paxweb/WAR+Extender
http://jira.springframework.org/browse/OSGI-468

alex

On Tue, May 12, 2009 at 12:48 PM, Alex Boisvert wrote:

> Alright, thanks for your help!   I was mostly kicking the tires to get a
> taste for the upcoming OSGi integration.  I guess my main feedback at this
> point is that it would be nice to map the app into a non-root context of
> Jetty.   e.g. http://localhost:8080/examples-osgi instead of directly
> under http://localhost:8080.This would make it possible to deploy
> several Lift apps onto the same OSGi container.
>
> alex
>
>
>
> On Tue, May 12, 2009 at 12:19 PM, Heiko Seeberger <
> heiko.seeber...@googlemail.com> wrote:
>
>> Hm, does not look good :-(Thanx for trying and please keep on!
>> I have to deal with some build issues, and will take a look at that
>> tomorrow.
>>
>> Heiko
>>
>> 2009/5/12 Alex Boisvert 
>>
>>> That was it.  I pulled again from git and now I can start the
>>> examples-osgi app.
>>>
>>> However, one more nitpick...  I can load index.htm but the snippet isn't
>>> rendered correctly because some resources can't be found.
>>>
>>> e.g.
>>> [5285...@qtp-20735553-0 - /] INFO
>>> org.ops4j.pax.web.service.internal.HttpServiceContext - getting resource:
>>> [/templates-hidden/default.htm]
>>> [5285...@qtp-20735553-0 - /] INFO
>>> org.ops4j.pax.web.service.internal.HttpServiceContext - found resource: null
>>>
>>> Is that normal?  I can see the following displayed:
>>>
>>>   From a snippet: Hi, I am a snippet from a Lift-powered OSGi
>>> bundle!
>>>
>>> but there's no surrounding   ...   so the
>>> browser complains.
>>>
>>> alex
>>>
>>> On Tue, May 12, 2009 at 11:24 AM, Heiko Seeberger <
>>> heiko.seeber...@googlemail.com> wrote:
>>>
 When did you check out? I pushed again about one or two hours ago.From
 the log I can see that you use an old version of hello.composite. The new
 one should look like:

 scan-bundle:wrap:mvn:javax.mail/mail/1.4

 scan-bundle:wrap:mvn:javax.activation/activation/1.1
 ...

 The "wrap:" is important. Pax Runner will wrap vanilla JARs into OSGi
 bundles.

 Please pull again, that should help.
 Heiko

 2009/5/12 Alex Boisvert 

> Ok, I tried again based on your suggestion but I'm getting an error
> related to javax.mail:1.4 not being a valid bundle...
>
>  -> Preparing framework [Felix 1.6.0]
>  -> Downloading bundles...
>  -> mvn:javax.mail/mail/1.4 : 388864 bytes @ [ 471kBps ]
> s @ [ 498kBps ]
>
>  ___
> /  /
>/  / Oops, there has been a problem!
>   /  /
>  /__/   org.ops4j.pax.runner.platform.PlatformException:
> [mvn:javax.mail/mail/1.4] is not a valid bundle
> ___
>/__/ Use --log=debug to see details.
>
>
> To be sure, I wiped my M2 repo under javax/mail and retried but I'm
> getting the same error.  Any idea?
>
> I'm attaching the full log in case it's helpful.
>
> alex
>
>
>
>
> On Tue, May 12, 2009 at 10:08 AM, Heiko Seeberger <
> heiko.seeber...@googlemail.com> wrote:
>
>> Hi Alex,
>> 2009/5/12 Alex Boisvert 
>>
>> I downloaded and ran PAX runner,
>>>
>>> ./pax-run.sh --profiles=log,scala,felix.webconsole,web
>>
>>
>>>
>>> then installed the examples-osgi bundle,
>>>
>>> -> install
>>> file:///home/boisvert/git/liftweb/sites/examples-osgi/hello/target/examples-osgi-hello-1.1-SNAPSHOT.jar
>>> Bundle ID: 9
>>> -> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello -
>>> BundleEvent INSTALLED
>>> start 9
>>> -> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello -
>>> BundleEvent RESOLVED
>>> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello -
>>> BundleEvent STARTED
>>>
>>
>> OSGi support for Lift is implemented as "extender" in order to keep
>> Lift "core" OSGi-agnostic. This means that there is a special add-on 
>> bundle
>> (lift-osgi) which must be installed and started. It will watch all 
>> bundles
>> if they are Lift-powered which means they have got a Lift-Config manifest
>> entry. If so, these bundles will be delegated to for resource look-ups
>> (templates) and also (latest checkin) bootstrap.liftweb.Boot classes 
>> will be
>> called.
>>
>> OK, you have got to install lift-osgi and all its prerequesites, i.e.
>> lift-webkit, lift-util, etc. You could install the example PLUS all the
>> required other bundles manually. But better go for Pax Runner like that
>>
>> pax-run.sh --profiles=web,scala,
>> scan-composite:file:
>>
>> with  the path to hello.composite which is part of
>> sites/examples-osgi/hello
>>
>

[Lift] Re: OSGi support for Lift

[Heiko Seeberger]

Hi Alex,


> Yes, I do get that and these are exactly the things I'm looking for in
> moving to OSGi.  However, as applications grow I think it's eventually
> necessary to modularize and isolate them so that changing something in one
> app doesn't affect another one.
>

Yes, you are right. But so far OSGi does not support the concept of an
application.


> Let's say I have 2 apps and I'd like one of them to run on Lift 1.0 and the
> other one on Lift 1.1-SNAPSHOT, how do you see this working?  In a typical
> J2EE webapp, these would be deployed as separate wars, each having a
> separate web context and isolated Lift core instances.
>

Two separate WARs means two separate applications which is not possible in
OSGi so far. We could try to tweak this, e.g. by using non-overlapping
version ranges on package imports. But currently Lift needs (evil)
DynamicImport-Package to properly resolve classes (e.g. Snippets) which
breaks version-based resolving. And there would be other issues, too.

This whole application and isolation stuff is currently investigated by the
OSGi EEG (enterprise experts group): Hopefully we will soon see a solution!

Heiko

--~--~-~--~~~---~--~~
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 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: OSGi support for Lift

[Alex Boisvert]

Hi Heiko,

On Tue, May 12, 2009 at 11:21 PM, Heiko Seeberger <
heiko.seeber...@googlemail.com> wrote:

> This is an interesting requirement and could be feasible but not trivial.
> Please keep in mind, that in OSGi *each* application is (potentially) made
> up from several bundles that can be installed, updated and removed at any
> point of (run)time => Whar really leverages the power of OSGi is to have one
> *composite* web application (under one context). Because then you can do
> things like adding functionality or hot deployment which have not been
> possible before.
>

Yes, I do get that and these are exactly the things I'm looking for in
moving to OSGi.  However, as applications grow I think it's eventually
necessary to modularize and isolate them so that changing something in one
app doesn't affect another one.

Let's say I have 2 apps and I'd like one of them to run on Lift 1.0 and the
other one on Lift 1.1-SNAPSHOT, how do you see this working?  In a typical
J2EE webapp, these would be deployed as separate wars, each having a
separate web context and isolated Lift core instances.   Ideally, these
would run in the same OSGi container so the overhead of the OSGi platform
remains fixed.

(Yes, I can imagine cases where you'd want to run multiple containers for
additional isolation but I'm personally not expecting this anytime soon)

alex

--~--~-~--~~~---~--~~
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 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: OSGi support for Lift

[Heiko Seeberger]

Alex,
This is an interesting requirement and could be feasible but not trivial.

Please keep in mind, that in OSGi *each* application is (potentially) made
up from several bundles that can be installed, updated and removed at any
point of (run)time => Whar really leverages the power of OSGi is to have one
*composite* web application (under one context). Because then you can do
things like adding functionality or hot deployment which have not been
possible before.

Also notice that in OSGi space you will not have a Jetty as the "leading"
server, but an OSGi framework like Felix or Equinox where Jetty or another
servlet container is just one bundle. Currently there are ongoing efforts on
how to nest OSGi frameworks => This will provide a very mature way to have
several isolated composite applications. Maybe we should wait for that ...

Cheers
Heiko

2009/5/12 Alex Boisvert 

> Alright, thanks for your help!   I was mostly kicking the tires to get a
> taste for the upcoming OSGi integration.  I guess my main feedback at this
> point is that it would be nice to map the app into a non-root context of
> Jetty.   e.g. http://localhost:8080/examples-osgi instead of directly
> under http://localhost:8080.This would make it possible to deploy
> several Lift apps onto the same OSGi container.
>
> alex
>
>
>
> On Tue, May 12, 2009 at 12:19 PM, Heiko Seeberger <
> heiko.seeber...@googlemail.com> wrote:
>
>> Hm, does not look good :-(Thanx for trying and please keep on!
>> I have to deal with some build issues, and will take a look at that
>> tomorrow.
>>
>> Heiko
>>
>> 2009/5/12 Alex Boisvert 
>>
>>> That was it.  I pulled again from git and now I can start the
>>> examples-osgi app.
>>>
>>> However, one more nitpick...  I can load index.htm but the snippet isn't
>>> rendered correctly because some resources can't be found.
>>>
>>> e.g.
>>> [5285...@qtp-20735553-0 - /] INFO
>>> org.ops4j.pax.web.service.internal.HttpServiceContext - getting resource:
>>> [/templates-hidden/default.htm]
>>> [5285...@qtp-20735553-0 - /] INFO
>>> org.ops4j.pax.web.service.internal.HttpServiceContext - found resource: null
>>>
>>> Is that normal?  I can see the following displayed:
>>>
>>>   From a snippet: Hi, I am a snippet from a Lift-powered OSGi
>>> bundle!
>>>
>>> but there's no surrounding   ...   so the
>>> browser complains.
>>>
>>> alex
>>>
>>> On Tue, May 12, 2009 at 11:24 AM, Heiko Seeberger <
>>> heiko.seeber...@googlemail.com> wrote:
>>>
 When did you check out? I pushed again about one or two hours ago.From
 the log I can see that you use an old version of hello.composite. The new
 one should look like:

 scan-bundle:wrap:mvn:javax.mail/mail/1.4

 scan-bundle:wrap:mvn:javax.activation/activation/1.1
 ...

 The "wrap:" is important. Pax Runner will wrap vanilla JARs into OSGi
 bundles.

 Please pull again, that should help.
 Heiko

 2009/5/12 Alex Boisvert 

> Ok, I tried again based on your suggestion but I'm getting an error
> related to javax.mail:1.4 not being a valid bundle...
>
>  -> Preparing framework [Felix 1.6.0]
>  -> Downloading bundles...
>  -> mvn:javax.mail/mail/1.4 : 388864 bytes @ [ 471kBps ]
> s @ [ 498kBps ]
>
>  ___
> /  /
>/  / Oops, there has been a problem!
>   /  /
>  /__/   org.ops4j.pax.runner.platform.PlatformException:
> [mvn:javax.mail/mail/1.4] is not a valid bundle
> ___
>/__/ Use --log=debug to see details.
>
>
> To be sure, I wiped my M2 repo under javax/mail and retried but I'm
> getting the same error.  Any idea?
>
> I'm attaching the full log in case it's helpful.
>
> alex
>
>
>
>
> On Tue, May 12, 2009 at 10:08 AM, Heiko Seeberger <
> heiko.seeber...@googlemail.com> wrote:
>
>> Hi Alex,
>> 2009/5/12 Alex Boisvert 
>>
>> I downloaded and ran PAX runner,
>>>
>>> ./pax-run.sh --profiles=log,scala,felix.webconsole,web
>>
>>
>>>
>>> then installed the examples-osgi bundle,
>>>
>>> -> install
>>> file:///home/boisvert/git/liftweb/sites/examples-osgi/hello/target/examples-osgi-hello-1.1-SNAPSHOT.jar
>>> Bundle ID: 9
>>> -> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello -
>>> BundleEvent INSTALLED
>>> start 9
>>> -> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello -
>>> BundleEvent RESOLVED
>>> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello -
>>> BundleEvent STARTED
>>>
>>
>> OSGi support for Lift is implemented as "extender" in order to keep
>> Lift "core" OSGi-agnostic. This means that there is a special add-on 
>> bundle
>> (lift-osgi) which must be installed and started. It will watch all 
>> bundles
>> if they are Lift-powered which means they have got a Lift-Config manifest
>> entry. If so, these bundles 

[Lift] Re: OSGi support for Lift

[Heiko Seeberger]

Alex,

[5285...@qtp-20735553-0 - /] INFO
> org.ops4j.pax.web.service.internal.HttpServiceContext - getting resource:
> [/templates-hidden/default.htm]
> [5285...@qtp-20735553-0 - /] INFO
> org.ops4j.pax.web.service.internal.HttpServiceContext - found resource: null
>
> Is that normal?  I can see the following displayed:


As far as I know Lift that *is* normal, because Lift tries different locales
and suffixes to match "index". Browse little further down and you should see
that it finally finds index.html (not .htm):

INFO org.ops4j.pax.web.service.internal.HttpServiceContext - getting
resource: [/index_en_US]
INFO org.ops4j.pax.web.service.internal.HttpServiceContext - found resource:
null
INFO org.ops4j.pax.web.service.internal.HttpServiceContext - getting
resource: [/index_en]
INFO org.ops4j.pax.web.service.internal.HttpServiceContext - found resource:
null
INFO org.ops4j.pax.web.service.internal.HttpServiceContext - getting
resource: [/index]
INFO org.ops4j.pax.web.service.internal.HttpServiceContext - found resource:
null
INFO org.ops4j.pax.web.service.internal.HttpServiceContext - getting
resource: [/index_en_US.html]
INFO org.ops4j.pax.web.service.internal.HttpServiceContext - found resource:
null
INFO org.ops4j.pax.web.service.internal.HttpServiceContext - getting
resource: [/index_en.html]
INFO org.ops4j.pax.web.service.internal.HttpServiceContext - found resource:
null
INFO org.ops4j.pax.web.service.internal.HttpServiceContext - getting
resource: [/index.html]
INFO org.ops4j.pax.web.service.internal.HttpServiceContext - found resource:
bundle://16.0:1/webapp/index.html

  From a snippet: Hi, I am a snippet from a Lift-powered OSGi
> bundle!
>
> but there's no surrounding   ...   so the browser
> complains.
>

Puh, I cannot reproduce this. My browser gets


http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
http://liftweb.net/";
xmlns="http://www.w3.org/1999/xhtml";>
  Lift-OSGi



  Welcome to Lift on OSGi!
  From a snippet: Hi, I am a snippet from a Lift-powered OSGi
bundle!


// 




My fix for the build issues broke the example. I just pushed a new version
that works again (for me). Could you please give it another try?

Thanx
Heiko

--~--~-~--~~~---~--~~
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 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: OSGi support for Lift

[Alex Boisvert]

Alright, thanks for your help!   I was mostly kicking the tires to get a
taste for the upcoming OSGi integration.  I guess my main feedback at this
point is that it would be nice to map the app into a non-root context of
Jetty.   e.g. http://localhost:8080/examples-osgi instead of directly under
http://localhost:8080.This would make it possible to deploy several Lift
apps onto the same OSGi container.

alex


On Tue, May 12, 2009 at 12:19 PM, Heiko Seeberger <
heiko.seeber...@googlemail.com> wrote:

> Hm, does not look good :-(Thanx for trying and please keep on!
> I have to deal with some build issues, and will take a look at that
> tomorrow.
>
> Heiko
>
> 2009/5/12 Alex Boisvert 
>
>> That was it.  I pulled again from git and now I can start the
>> examples-osgi app.
>>
>> However, one more nitpick...  I can load index.htm but the snippet isn't
>> rendered correctly because some resources can't be found.
>>
>> e.g.
>> [5285...@qtp-20735553-0 - /] INFO
>> org.ops4j.pax.web.service.internal.HttpServiceContext - getting resource:
>> [/templates-hidden/default.htm]
>> [5285...@qtp-20735553-0 - /] INFO
>> org.ops4j.pax.web.service.internal.HttpServiceContext - found resource: null
>>
>> Is that normal?  I can see the following displayed:
>>
>>   From a snippet: Hi, I am a snippet from a Lift-powered OSGi
>> bundle!
>>
>> but there's no surrounding   ...   so the
>> browser complains.
>>
>> alex
>>
>> On Tue, May 12, 2009 at 11:24 AM, Heiko Seeberger <
>> heiko.seeber...@googlemail.com> wrote:
>>
>>> When did you check out? I pushed again about one or two hours ago.From
>>> the log I can see that you use an old version of hello.composite. The new
>>> one should look like:
>>>
>>> scan-bundle:wrap:mvn:javax.mail/mail/1.4
>>>
>>> scan-bundle:wrap:mvn:javax.activation/activation/1.1
>>> ...
>>>
>>> The "wrap:" is important. Pax Runner will wrap vanilla JARs into OSGi
>>> bundles.
>>>
>>> Please pull again, that should help.
>>> Heiko
>>>
>>> 2009/5/12 Alex Boisvert 
>>>
 Ok, I tried again based on your suggestion but I'm getting an error
 related to javax.mail:1.4 not being a valid bundle...

  -> Preparing framework [Felix 1.6.0]
  -> Downloading bundles...
  -> mvn:javax.mail/mail/1.4 : 388864 bytes @ [ 471kBps ]
 s @ [ 498kBps ]

  ___
 /  /
/  / Oops, there has been a problem!
   /  /
  /__/   org.ops4j.pax.runner.platform.PlatformException:
 [mvn:javax.mail/mail/1.4] is not a valid bundle
 ___
/__/ Use --log=debug to see details.


 To be sure, I wiped my M2 repo under javax/mail and retried but I'm
 getting the same error.  Any idea?

 I'm attaching the full log in case it's helpful.

 alex




 On Tue, May 12, 2009 at 10:08 AM, Heiko Seeberger <
 heiko.seeber...@googlemail.com> wrote:

> Hi Alex,
> 2009/5/12 Alex Boisvert 
>
> I downloaded and ran PAX runner,
>>
>> ./pax-run.sh --profiles=log,scala,felix.webconsole,web
>
>
>>
>> then installed the examples-osgi bundle,
>>
>> -> install
>> file:///home/boisvert/git/liftweb/sites/examples-osgi/hello/target/examples-osgi-hello-1.1-SNAPSHOT.jar
>> Bundle ID: 9
>> -> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello -
>> BundleEvent INSTALLED
>> start 9
>> -> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello -
>> BundleEvent RESOLVED
>> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello -
>> BundleEvent STARTED
>>
>
> OSGi support for Lift is implemented as "extender" in order to keep
> Lift "core" OSGi-agnostic. This means that there is a special add-on 
> bundle
> (lift-osgi) which must be installed and started. It will watch all bundles
> if they are Lift-powered which means they have got a Lift-Config manifest
> entry. If so, these bundles will be delegated to for resource look-ups
> (templates) and also (latest checkin) bootstrap.liftweb.Boot classes will 
> be
> called.
>
> OK, you have got to install lift-osgi and all its prerequesites, i.e.
> lift-webkit, lift-util, etc. You could install the example PLUS all the
> required other bundles manually. But better go for Pax Runner like that
>
> pax-run.sh --profiles=web,scala,
> scan-composite:file:
>
> with  the path to hello.composite which is part of
> sites/examples-osgi/hello
>
> Cheers
> Heiko
>
>
>



>>>
>>>
>>> --
>>> My blog: heikoseeberger.name
>>> Follow me: twitter.com/hseeberger
>>> OSGi on Scala: www.scalamodules.org
>>> Lift, the simply functional web framework: liftweb.net
>>>
>>>
>>>
>>
>>
>>
>
>
> --
> My blog: heikoseeberger.name
> Follow me: twitter.com/hseeberger
> OSGi on Scala: www.scalamodules.org
> Lift, the simply functional web framework: liftweb.net
>
> >
>

--~--~-~--~~---

[Lift] Re: OSGi support for Lift

[Viktor Klang]

I', down with that! :)

On Tue, May 12, 2009 at 7:01 PM, Timothy Perrett wrote:

>
>
> If you like that Viktor, you should hang out in some of the finest (read:
> most local) drinking establishments the west-country of England has to
> offer!
>
> Who's in EMEA? Me, Viktor, Heiko? Anyone else? Until the EPFL meetup next
> fall (rumoured to be happening) cant help but feel EMEA is a little left
> out
> of the scala + beer drinking times!
>
> Cheers, Tim
>
> On 12/05/2009 17:43, "Viktor Klang"  wrote:
>
> > I'm a big fan of smoked German beer like Schlenkerla Rauchbier :)
>
>
>
> >
>


-- 
Viktor Klang
Senior Systems Analyst

--~--~-~--~~~---~--~~
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 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: OSGi support for Lift

[Heiko Seeberger]

Hm, does not look good :-(Thanx for trying and please keep on!
I have to deal with some build issues, and will take a look at that
tomorrow.

Heiko

2009/5/12 Alex Boisvert 

> That was it.  I pulled again from git and now I can start the examples-osgi
> app.
>
> However, one more nitpick...  I can load index.htm but the snippet isn't
> rendered correctly because some resources can't be found.
>
> e.g.
> [5285...@qtp-20735553-0 - /] INFO
> org.ops4j.pax.web.service.internal.HttpServiceContext - getting resource:
> [/templates-hidden/default.htm]
> [5285...@qtp-20735553-0 - /] INFO
> org.ops4j.pax.web.service.internal.HttpServiceContext - found resource: null
>
> Is that normal?  I can see the following displayed:
>
>   From a snippet: Hi, I am a snippet from a Lift-powered OSGi
> bundle!
>
> but there's no surrounding   ...   so the browser
> complains.
>
> alex
>
> On Tue, May 12, 2009 at 11:24 AM, Heiko Seeberger <
> heiko.seeber...@googlemail.com> wrote:
>
>> When did you check out? I pushed again about one or two hours ago.From
>> the log I can see that you use an old version of hello.composite. The new
>> one should look like:
>>
>> scan-bundle:wrap:mvn:javax.mail/mail/1.4
>>
>> scan-bundle:wrap:mvn:javax.activation/activation/1.1
>> ...
>>
>> The "wrap:" is important. Pax Runner will wrap vanilla JARs into OSGi
>> bundles.
>>
>> Please pull again, that should help.
>> Heiko
>>
>> 2009/5/12 Alex Boisvert 
>>
>>> Ok, I tried again based on your suggestion but I'm getting an error
>>> related to javax.mail:1.4 not being a valid bundle...
>>>
>>>  -> Preparing framework [Felix 1.6.0]
>>>  -> Downloading bundles...
>>>  -> mvn:javax.mail/mail/1.4 : 388864 bytes @ [ 471kBps ]
>>> s @ [ 498kBps ]
>>>
>>>  ___
>>> /  /
>>>/  / Oops, there has been a problem!
>>>   /  /
>>>  /__/   org.ops4j.pax.runner.platform.PlatformException:
>>> [mvn:javax.mail/mail/1.4] is not a valid bundle
>>> ___
>>>/__/ Use --log=debug to see details.
>>>
>>>
>>> To be sure, I wiped my M2 repo under javax/mail and retried but I'm
>>> getting the same error.  Any idea?
>>>
>>> I'm attaching the full log in case it's helpful.
>>>
>>> alex
>>>
>>>
>>>
>>>
>>> On Tue, May 12, 2009 at 10:08 AM, Heiko Seeberger <
>>> heiko.seeber...@googlemail.com> wrote:
>>>
 Hi Alex,
 2009/5/12 Alex Boisvert 

 I downloaded and ran PAX runner,
>
> ./pax-run.sh --profiles=log,scala,felix.webconsole,web


>
> then installed the examples-osgi bundle,
>
> -> install
> file:///home/boisvert/git/liftweb/sites/examples-osgi/hello/target/examples-osgi-hello-1.1-SNAPSHOT.jar
> Bundle ID: 9
> -> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello -
> BundleEvent INSTALLED
> start 9
> -> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello -
> BundleEvent RESOLVED
> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello -
> BundleEvent STARTED
>

 OSGi support for Lift is implemented as "extender" in order to keep Lift
 "core" OSGi-agnostic. This means that there is a special add-on bundle
 (lift-osgi) which must be installed and started. It will watch all bundles
 if they are Lift-powered which means they have got a Lift-Config manifest
 entry. If so, these bundles will be delegated to for resource look-ups
 (templates) and also (latest checkin) bootstrap.liftweb.Boot classes will 
 be
 called.

 OK, you have got to install lift-osgi and all its prerequesites, i.e.
 lift-webkit, lift-util, etc. You could install the example PLUS all the
 required other bundles manually. But better go for Pax Runner like that

 pax-run.sh --profiles=web,scala,
 scan-composite:file:

 with  the path to hello.composite which is part of
 sites/examples-osgi/hello

 Cheers
 Heiko



>>>
>>>
>>>
>>
>>
>> --
>> My blog: heikoseeberger.name
>> Follow me: twitter.com/hseeberger
>> OSGi on Scala: www.scalamodules.org
>> Lift, the simply functional web framework: liftweb.net
>>
>>
>>
>
> >
>


-- 
My blog: heikoseeberger.name
Follow me: twitter.com/hseeberger
OSGi on Scala: www.scalamodules.org
Lift, the simply functional web framework: liftweb.net

--~--~-~--~~~---~--~~
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 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: OSGi support for Lift

[Alex Boisvert]

That was it.  I pulled again from git and now I can start the examples-osgi
app.

However, one more nitpick...  I can load index.htm but the snippet isn't
rendered correctly because some resources can't be found.

e.g.
[5285...@qtp-20735553-0 - /] INFO
org.ops4j.pax.web.service.internal.HttpServiceContext - getting resource:
[/templates-hidden/default.htm]
[5285...@qtp-20735553-0 - /] INFO
org.ops4j.pax.web.service.internal.HttpServiceContext - found resource: null

Is that normal?  I can see the following displayed:

  From a snippet: Hi, I am a snippet from a Lift-powered OSGi
bundle!

but there's no surrounding   ...   so the browser
complains.

alex

On Tue, May 12, 2009 at 11:24 AM, Heiko Seeberger <
heiko.seeber...@googlemail.com> wrote:

> When did you check out? I pushed again about one or two hours ago.From the
> log I can see that you use an old version of hello.composite. The new one
> should look like:
>
> scan-bundle:wrap:mvn:javax.mail/mail/1.4
>
> scan-bundle:wrap:mvn:javax.activation/activation/1.1
> ...
>
> The "wrap:" is important. Pax Runner will wrap vanilla JARs into OSGi
> bundles.
>
> Please pull again, that should help.
> Heiko
>
> 2009/5/12 Alex Boisvert 
>
>> Ok, I tried again based on your suggestion but I'm getting an error
>> related to javax.mail:1.4 not being a valid bundle...
>>
>>  -> Preparing framework [Felix 1.6.0]
>>  -> Downloading bundles...
>>  -> mvn:javax.mail/mail/1.4 : 388864 bytes @ [ 471kBps ]
>> s @ [ 498kBps ]
>>
>>  ___
>> /  /
>>/  / Oops, there has been a problem!
>>   /  /
>>  /__/   org.ops4j.pax.runner.platform.PlatformException:
>> [mvn:javax.mail/mail/1.4] is not a valid bundle
>> ___
>>/__/ Use --log=debug to see details.
>>
>>
>> To be sure, I wiped my M2 repo under javax/mail and retried but I'm
>> getting the same error.  Any idea?
>>
>> I'm attaching the full log in case it's helpful.
>>
>> alex
>>
>>
>>
>>
>> On Tue, May 12, 2009 at 10:08 AM, Heiko Seeberger <
>> heiko.seeber...@googlemail.com> wrote:
>>
>>> Hi Alex,
>>> 2009/5/12 Alex Boisvert 
>>>
>>> I downloaded and ran PAX runner,

 ./pax-run.sh --profiles=log,scala,felix.webconsole,web
>>>
>>>

 then installed the examples-osgi bundle,

 -> install
 file:///home/boisvert/git/liftweb/sites/examples-osgi/hello/target/examples-osgi-hello-1.1-SNAPSHOT.jar
 Bundle ID: 9
 -> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello -
 BundleEvent INSTALLED
 start 9
 -> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello -
 BundleEvent RESOLVED
 [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello - BundleEvent
 STARTED

>>>
>>> OSGi support for Lift is implemented as "extender" in order to keep Lift
>>> "core" OSGi-agnostic. This means that there is a special add-on bundle
>>> (lift-osgi) which must be installed and started. It will watch all bundles
>>> if they are Lift-powered which means they have got a Lift-Config manifest
>>> entry. If so, these bundles will be delegated to for resource look-ups
>>> (templates) and also (latest checkin) bootstrap.liftweb.Boot classes will be
>>> called.
>>>
>>> OK, you have got to install lift-osgi and all its prerequesites, i.e.
>>> lift-webkit, lift-util, etc. You could install the example PLUS all the
>>> required other bundles manually. But better go for Pax Runner like that
>>>
>>> pax-run.sh --profiles=web,scala, scan-composite:file:
>>>
>>> with  the path to hello.composite which is part of
>>> sites/examples-osgi/hello
>>>
>>> Cheers
>>> Heiko
>>>
>>>
>>>
>>
>>
>>
>
>
> --
> My blog: heikoseeberger.name
> Follow me: twitter.com/hseeberger
> OSGi on Scala: www.scalamodules.org
> Lift, the simply functional web framework: liftweb.net
>
> >
>

--~--~-~--~~~---~--~~
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 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: OSGi support for Lift

[Timothy Perrett]

EMEA == Europe, Middle East and Africa :-)

On 12/05/2009 18:58, "Charles F. Munat"  wrote:

> 
> What is EMEA?
> 
> (Personally, I'm a fan of Belgian ales, including the wonderful Flemish
> sour ales. Duchesse du Bourgogne is a favorite. And the amazing aged
> alembic ales coming out of the Russian River brewery in Santa Rosa,
> California are legendary!)
> 
> Chas.
> 
> Timothy Perrett wrote:
>> 
>> If you like that Viktor, you should hang out in some of the finest (read:
>> most local) drinking establishments the west-country of England has to
>> offer!
>> 
>> Who's in EMEA? Me, Viktor, Heiko? Anyone else? Until the EPFL meetup next
>> fall (rumoured to be happening) cant help but feel EMEA is a little left out
>> of the scala + beer drinking times!
>> 
>> Cheers, Tim
>> 
>> On 12/05/2009 17:43, "Viktor Klang"  wrote:
>> 
>>> I'm a big fan of smoked German beer like Schlenkerla Rauchbier :)
>> 
>> 
>> 
>>> 
> 
> > 
> 



--~--~-~--~~~---~--~~
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 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: OSGi support for Lift

[Heiko Seeberger]

Sure, Pax Exam rules!

2009/5/12 James Strachan 

>
> BTW speaking of PAX - I've found a nice easy way to test OSGI jars (as
> its so easy to mess up the metadata) is to use Pax Exam to create
> an OSGi integration test of your bundles against one or more OSGi
> containers (e.g. Felix and Equinox), using the maven poms and the
> Apache ServiceMix/Karaf plugin to deduce the versions of the
> dependencies you're using to avoid hard coding them in your
> integration test.
>
> More details here:
>
> http://macstrac.blogspot.com/2009/04/if-you-are-using-osgi-then-give-pax.html
>
> 2009/5/12 Alex Boisvert :
> > Hi Heiko,
> >
> > Just a few basic questions
> >
> > I downloaded and ran PAX runner,
> >
> > ./pax-run.sh --profiles=log,scala,felix.webconsole,web
> >
> > then installed the examples-osgi bundle,
> >
> > -> install
> >
> file:///home/boisvert/git/liftweb/sites/examples-osgi/hello/target/examples-osgi-hello-1.1-SNAPSHOT.jar
> > Bundle ID: 9
> > -> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello -
> BundleEvent
> > INSTALLED
> > start 9
> > -> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello -
> BundleEvent
> > RESOLVED
> > [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello - BundleEvent
> > STARTED
> >
> > Now how to I access the Lift app?   How does the servlet context get
> mapped
> > onto Jetty?  It is normal there's no web.xml in this project?   (I can
> > access the Felix admin console at http://localhost:8080/system/console)
> >
> > alex
> >
> > >
> >
>
>
>
> --
> James
> ---
> http://macstrac.blogspot.com/
>
> Open Source Integration
> http://fusesource.com/
>
> >
>


-- 
My blog: heikoseeberger.name
Follow me: twitter.com/hseeberger
OSGi on Scala: www.scalamodules.org
Lift, the simply functional web framework: liftweb.net

--~--~-~--~~~---~--~~
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 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: OSGi support for Lift

[James Strachan]

BTW speaking of PAX - I've found a nice easy way to test OSGI jars (as
its so easy to mess up the metadata) is to use Pax Exam to create
an OSGi integration test of your bundles against one or more OSGi
containers (e.g. Felix and Equinox), using the maven poms and the
Apache ServiceMix/Karaf plugin to deduce the versions of the
dependencies you're using to avoid hard coding them in your
integration test.

More details here:
http://macstrac.blogspot.com/2009/04/if-you-are-using-osgi-then-give-pax.html

2009/5/12 Alex Boisvert :
> Hi Heiko,
>
> Just a few basic questions
>
> I downloaded and ran PAX runner,
>
> ./pax-run.sh --profiles=log,scala,felix.webconsole,web
>
> then installed the examples-osgi bundle,
>
> -> install
> file:///home/boisvert/git/liftweb/sites/examples-osgi/hello/target/examples-osgi-hello-1.1-SNAPSHOT.jar
> Bundle ID: 9
> -> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello - BundleEvent
> INSTALLED
> start 9
> -> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello - BundleEvent
> RESOLVED
> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello - BundleEvent
> STARTED
>
> Now how to I access the Lift app?   How does the servlet context get mapped
> onto Jetty?  It is normal there's no web.xml in this project?   (I can
> access the Felix admin console at http://localhost:8080/system/console)
>
> alex
>
> >
>



-- 
James
---
http://macstrac.blogspot.com/

Open Source Integration
http://fusesource.com/

--~--~-~--~~~---~--~~
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 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: OSGi support for Lift

[Heiko Seeberger]

When did you check out? I pushed again about one or two hours ago.From the
log I can see that you use an old version of hello.composite. The new one
should look like:

scan-bundle:wrap:mvn:javax.mail/mail/1.4

scan-bundle:wrap:mvn:javax.activation/activation/1.1
...

The "wrap:" is important. Pax Runner will wrap vanilla JARs into OSGi
bundles.

Please pull again, that should help.
Heiko

2009/5/12 Alex Boisvert 

> Ok, I tried again based on your suggestion but I'm getting an error related
> to javax.mail:1.4 not being a valid bundle...
>
>  -> Preparing framework [Felix 1.6.0]
>  -> Downloading bundles...
>  -> mvn:javax.mail/mail/1.4 : 388864 bytes @ [ 471kBps ]
> s @ [ 498kBps ]
>
>  ___
> /  /
>/  / Oops, there has been a problem!
>   /  /
>  /__/   org.ops4j.pax.runner.platform.PlatformException:
> [mvn:javax.mail/mail/1.4] is not a valid bundle
> ___
>/__/ Use --log=debug to see details.
>
>
> To be sure, I wiped my M2 repo under javax/mail and retried but I'm getting
> the same error.  Any idea?
>
> I'm attaching the full log in case it's helpful.
>
> alex
>
>
>
>
> On Tue, May 12, 2009 at 10:08 AM, Heiko Seeberger <
> heiko.seeber...@googlemail.com> wrote:
>
>> Hi Alex,
>> 2009/5/12 Alex Boisvert 
>>
>> I downloaded and ran PAX runner,
>>>
>>> ./pax-run.sh --profiles=log,scala,felix.webconsole,web
>>
>>
>>>
>>> then installed the examples-osgi bundle,
>>>
>>> -> install
>>> file:///home/boisvert/git/liftweb/sites/examples-osgi/hello/target/examples-osgi-hello-1.1-SNAPSHOT.jar
>>> Bundle ID: 9
>>> -> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello -
>>> BundleEvent INSTALLED
>>> start 9
>>> -> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello -
>>> BundleEvent RESOLVED
>>> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello - BundleEvent
>>> STARTED
>>>
>>
>> OSGi support for Lift is implemented as "extender" in order to keep Lift
>> "core" OSGi-agnostic. This means that there is a special add-on bundle
>> (lift-osgi) which must be installed and started. It will watch all bundles
>> if they are Lift-powered which means they have got a Lift-Config manifest
>> entry. If so, these bundles will be delegated to for resource look-ups
>> (templates) and also (latest checkin) bootstrap.liftweb.Boot classes will be
>> called.
>>
>> OK, you have got to install lift-osgi and all its prerequesites, i.e.
>> lift-webkit, lift-util, etc. You could install the example PLUS all the
>> required other bundles manually. But better go for Pax Runner like that
>>
>> pax-run.sh --profiles=web,scala, scan-composite:file:
>>
>> with  the path to hello.composite which is part of
>> sites/examples-osgi/hello
>>
>> Cheers
>> Heiko
>>
>>
>>
>
> >
>


-- 
My blog: heikoseeberger.name
Follow me: twitter.com/hseeberger
OSGi on Scala: www.scalamodules.org
Lift, the simply functional web framework: liftweb.net

--~--~-~--~~~---~--~~
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 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: OSGi support for Lift

[Alex Boisvert]

Ok, I tried again based on your suggestion but I'm getting an error related
to javax.mail:1.4 not being a valid bundle...

 -> Preparing framework [Felix 1.6.0]
 -> Downloading bundles...
 -> mvn:javax.mail/mail/1.4 : 388864 bytes @ [ 471kBps ]
s @ [ 498kBps ]

 ___
/  /
   /  / Oops, there has been a problem!
  /  /
 /__/   org.ops4j.pax.runner.platform.PlatformException:
[mvn:javax.mail/mail/1.4] is not a valid bundle
___
   /__/ Use --log=debug to see details.


To be sure, I wiped my M2 repo under javax/mail and retried but I'm getting
the same error.  Any idea?

I'm attaching the full log in case it's helpful.

alex



On Tue, May 12, 2009 at 10:08 AM, Heiko Seeberger <
heiko.seeber...@googlemail.com> wrote:

> Hi Alex,
> 2009/5/12 Alex Boisvert 
>
> I downloaded and ran PAX runner,
>>
>> ./pax-run.sh --profiles=log,scala,felix.webconsole,web
>
>
>>
>> then installed the examples-osgi bundle,
>>
>> -> install
>> file:///home/boisvert/git/liftweb/sites/examples-osgi/hello/target/examples-osgi-hello-1.1-SNAPSHOT.jar
>> Bundle ID: 9
>> -> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello -
>> BundleEvent INSTALLED
>> start 9
>> -> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello -
>> BundleEvent RESOLVED
>> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello - BundleEvent
>> STARTED
>>
>
> OSGi support for Lift is implemented as "extender" in order to keep Lift
> "core" OSGi-agnostic. This means that there is a special add-on bundle
> (lift-osgi) which must be installed and started. It will watch all bundles
> if they are Lift-powered which means they have got a Lift-Config manifest
> entry. If so, these bundles will be delegated to for resource look-ups
> (templates) and also (latest checkin) bootstrap.liftweb.Boot classes will be
> called.
>
> OK, you have got to install lift-osgi and all its prerequesites, i.e.
> lift-webkit, lift-util, etc. You could install the example PLUS all the
> required other bundles manually. But better go for Pax Runner like that
>
> pax-run.sh --profiles=web,scala, scan-composite:file:
>
> with  the path to hello.composite which is part of
> sites/examples-osgi/hello
>
> Cheers
> Heiko
>
> >
>

--~--~-~--~~~---~--~~
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 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

__    __  __
   / __  / /  __   / / / / /
  /  ___/ /  __   / _\ \ _/
 /  //  / /  / / _\ \
/__//__/ /__/ /_/ /_/

Pax Runner (0.19.0) from OPS4J - http://www.ops4j.org
-

 -> Using config [classpath:META-INF/runner.properties]
 -> Using only arguments from command line
 -> Scan bundles from [scan-composite:file:/home/boisvert/git/liftweb/sites/examples-osgi/hello/hello.composite]
 -> Scan bundles from [scan-bundle:mvn:javax.mail/mail/1.4]
 -> Scan bundles from [scan-bundle:mvn:javax.activation/activation/1.1]
 -> Scan bundles from [scan-bundle:mvn:commons-httpclient/commons-httpclient/3.1]
 -> Scan bundles from [scan-bundle:mvn:commons-fileupload/commons-fileupload/1.2.1]
 -> Scan bundles from [scan-bundle:mvn:commons-collections/commons-collections/3.2.1]
 -> Scan bundles from [scan-bundle:mvn:commons-codec/commons-codec/1.3]
 -> Scan bundles from [scan-bundle:mvn:commons-io/commons-io/1.3.2]
 -> Scan bundles from [scan-bundle:mvn:org.scalamodules/scalamodules-core/1.1-SNAPSHOT]
 -> Scan bundles from [scan-bundle:mvn:org.scalamodules/scalamodules-util/1.1-SNAPSHOT]
 -> Scan bundles from [scan-bundle:mvn:net.liftweb/lift-util/1.1-snaps...@update]
 -> Scan bundles from [scan-bundle:mvn:net.liftweb/lift-webkit/1.1-snaps...@update]
 -> Scan bundles from [scan-bundle:mvn:net.liftweb/lift-osgi/1.1-snaps...@update]
 -> Scan bundles from [scan-bundle:mvn:org.ops4j.pax.swissbox/pax-swissbox-extender/0.2.0]
 -> Scan bundles from [scan-bundle:mvn:org.ops4j.pax.swissbox/pax-swissbox-lifecycle/0.2.0]
 -> Scan bundles from [scan-bundle:mvn:org.ops4j.base/ops4j-base-lang/0.5.0]
 -> Scan bundles from [scan-bundle:mvn:net.liftweb/examples-osgi-hello/1.1-snaps...@update]
 -> Scan bundles from [scan-composite:mvn:org.ops4j.pax.runner.profiles/web//composite]
 -> Scan bundles from [scan-composite:mvn:org.ops4j.pax.runner.profiles/log//composite]
 -> Scan bundles from [scan-bundle:mvn:org.ops4j.pax.logging/pax-logging-api/1.3.0]
 -> Scan bundles from [scan-bundle:mvn:org.ops4j.pax.logging/pax-logging-service/1.3.0]
 -> Scan bundles from [scan-bundle:mvn:org.ops4j.pax.web/pax-web-service/0.6.0]
 -> Scan bundles from [scan-composite:mvn:org.ops4j.pax.runner.profiles/scala//composite]
 -> Scan bundles from [scan-bundle:mvn:http://scala-tools.org/repo

[Lift] Re: OSGi support for Lift

[Heiko Seeberger]

Alex,

> Now how to I access the Lift app?   How does the servlet context get mapped
> onto Jetty?  It is normal there's no web.xml in this project?
>

Sorry, I missed your last questions.

You can access the demo the usual way via http://localhost:8080/index ;-)
In OSGi everything is a bundle and so is the servlet container. I am using
Pax Web which comes with a bundled Jetty.
And yes: It is normal not to have web.xml in OSGi. The servlet filter is
registered via API in the lift-osgi bundle.

Heiko

--~--~-~--~~~---~--~~
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 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: OSGi support for Lift

[Charles F. Munat]

What is EMEA?

(Personally, I'm a fan of Belgian ales, including the wonderful Flemish 
sour ales. Duchesse du Bourgogne is a favorite. And the amazing aged 
alembic ales coming out of the Russian River brewery in Santa Rosa, 
California are legendary!)

Chas.

Timothy Perrett wrote:
> 
> If you like that Viktor, you should hang out in some of the finest (read:
> most local) drinking establishments the west-country of England has to
> offer!
> 
> Who's in EMEA? Me, Viktor, Heiko? Anyone else? Until the EPFL meetup next
> fall (rumoured to be happening) cant help but feel EMEA is a little left out
> of the scala + beer drinking times!
> 
> Cheers, Tim
> 
> On 12/05/2009 17:43, "Viktor Klang"  wrote:
> 
>> I'm a big fan of smoked German beer like Schlenkerla Rauchbier :)
> 
> 
> 
> > 

--~--~-~--~~~---~--~~
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 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: OSGi support for Lift

[Heiko Seeberger]

Hi Alex,
2009/5/12 Alex Boisvert 

I downloaded and ran PAX runner,
>
> ./pax-run.sh --profiles=log,scala,felix.webconsole,web


>
> then installed the examples-osgi bundle,
>
> -> install
> file:///home/boisvert/git/liftweb/sites/examples-osgi/hello/target/examples-osgi-hello-1.1-SNAPSHOT.jar
> Bundle ID: 9
> -> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello - BundleEvent
> INSTALLED
> start 9
> -> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello - BundleEvent
> RESOLVED
> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello - BundleEvent
> STARTED
>

OSGi support for Lift is implemented as "extender" in order to keep Lift
"core" OSGi-agnostic. This means that there is a special add-on bundle
(lift-osgi) which must be installed and started. It will watch all bundles
if they are Lift-powered which means they have got a Lift-Config manifest
entry. If so, these bundles will be delegated to for resource look-ups
(templates) and also (latest checkin) bootstrap.liftweb.Boot classes will be
called.

OK, you have got to install lift-osgi and all its prerequesites, i.e.
lift-webkit, lift-util, etc. You could install the example PLUS all the
required other bundles manually. But better go for Pax Runner like that

pax-run.sh --profiles=web,scala, scan-composite:file:

with  the path to hello.composite which is part of
sites/examples-osgi/hello

Cheers
Heiko

--~--~-~--~~~---~--~~
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 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: OSGi support for Lift

[Timothy Perrett]

If you like that Viktor, you should hang out in some of the finest (read:
most local) drinking establishments the west-country of England has to
offer!

Who's in EMEA? Me, Viktor, Heiko? Anyone else? Until the EPFL meetup next
fall (rumoured to be happening) cant help but feel EMEA is a little left out
of the scala + beer drinking times!

Cheers, Tim

On 12/05/2009 17:43, "Viktor Klang"  wrote:

> I'm a big fan of smoked German beer like Schlenkerla Rauchbier :)



--~--~-~--~~~---~--~~
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 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: OSGi support for Lift

[Alex Boisvert]

Hi Heiko,

Just a few basic questions

I downloaded and ran PAX runner,

./pax-run.sh --profiles=log,scala,felix.webconsole,web

then installed the examples-osgi bundle,

-> install
file:///home/boisvert/git/liftweb/sites/examples-osgi/hello/target/examples-osgi-hello-1.1-SNAPSHOT.jar
Bundle ID: 9
-> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello - BundleEvent
INSTALLED
start 9
-> [FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello - BundleEvent
RESOLVED
[FelixDispatchQueue] DEBUG net.liftweb.examples-osgi-hello - BundleEvent
STARTED

Now how to I access the Lift app?   How does the servlet context get mapped
onto Jetty?  It is normal there's no web.xml in this project?   (I can
access the Felix admin console at http://localhost:8080/system/console)

alex

--~--~-~--~~~---~--~~
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 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: OSGi support for Lift

[Viktor Klang]

Hi Heiko,

I'm a big fan of smoked German beer like Schlenkerla Rauchbier :)

On Tue, May 12, 2009 at 4:21 PM, Heiko Seeberger <
heiko.seeber...@googlemail.com> wrote:

> Beer sounds great (I am form Bavaria) and team beer night also ;-)How does
> this work? Everybody chatting how much she has drunk?
>
> Cheers
> Heiko
>
> 2009/5/12 Viktor Klang 
>
>>
>>
>> On Tue, May 12, 2009 at 3:59 PM, Timothy Perrett > > wrote:
>>
>>>
>>> If your buying Viktor ;-)
>>>
>>> Say, when we having a lift team beer night? Feels like were long overdue
>>> for something like that!
>>>
>>
>> We really should!
>>
>>
>>>
>>> Cheers, Tim
>>>
>>> On 12/05/2009 14:50, "Viktor Klang"  wrote:
>>>
>>> I feel I owe Heiko a beer.
>>>
>>> On Tue, May 12, 2009 at 3:36 PM, David Pollak <
>>> feeder.of.the.be...@gmail.com> wrote:
>>>
>>> Very good stuff!
>>>
>>> Looking forward to playing with it today.
>>>
>>> Thanks for the hard work!
>>>
>>>
>>> On Tue, May 12, 2009 at 12:03 AM, Heiko Seeberger <
>>> heiko.seeber...@googlemail.com> wrote:
>>>
>>> Hi Lift folks,
>>>
>>> Today I checked in the first little step towards OSGi support:
>>>
>>>- Modules lift-util and lift-webkit are no longer plain vanilla JARs,
>>>but built as OSGi bundles (OSGi metadata in META-INF/MANIFEST.MF)
>>>- New module lift-osgi which offers (yet very limited) support for
>>>Lift application bundles (to ones you write)
>>>- New example module (under sites) examples-osgi with one (yet very
>>>limited) examples-osgi-hello bundle
>>>
>>> The first thing I would like to ask you is to verify that the changes to
>>> the existing modules are free of side effects: Lift should work without OSGi
>>> just like before. As the changes to lift-util and lift-webkit are merely in
>>> the manifest, I am very confident, but just to be sure ...
>>>
>>> And for those of you interested in OSGi:
>>> Currently there is only support for resources (templates) contributed
>>> from Lift-powered bundles to a composite Lift application. Yet no snippets,
>>> no custom dispatch, etc. Please take a look at sites/examples-osgi/hello.
>>> Note the new manifest header Lift-Config in the POM (the value is yet
>>> without any meaning). This bundle contributes its resources under webapp to
>>> a composite Lift application. The actual work is done by lift-osgi which is
>>> an implementation of the extender pattern. In order to run the example, I
>>> suggest you use Pax Runner 
>>>  with the scala and web profiles and the provided component configuration
>>> file at sites/examples-osgi/hello/hello.component. Else you will have to
>>> provision OSGi bundles for Scala, ScalaModules, Lift and all required
>>> dependencies (take a look into hello.component) by hand.
>>>
>>> Of course I would be very glad to get some reviews on my Scala code,
>>> because I guess there is still a long way of learning ahead ...
>>>
>>> Cheers
>>> Heiko
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Viktor Klang
>> Senior Systems Analyst
>>
>>
>>
>
>
> --
> My blog: heikoseeberger.name
> Follow me: twitter.com/hseeberger
> OSGi on Scala: www.scalamodules.org
> Lift, the simply functional web framework: liftweb.net
>
> >
>


-- 
Viktor Klang
Senior Systems Analyst

--~--~-~--~~~---~--~~
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 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: OSGi support for Lift

[Heiko Seeberger]

Hi again,
I just checked in the next little step: Now it is possible to have a Boot
class and provide packages => Snippets are also working (and maybe other
LiftRules stuff, too).
I also improved and fixed some stuff in the osgi-hello example.

Cheers
Heiko

2009/5/12 Heiko Seeberger 

> Beer sounds great (I am form Bavaria) and team beer night also ;-)How does
> this work? Everybody chatting how much she has drunk?
>
> Cheers
> Heiko
>
> 2009/5/12 Viktor Klang 
>
>
>>
>> On Tue, May 12, 2009 at 3:59 PM, Timothy Perrett > > wrote:
>>
>>>
>>> If your buying Viktor ;-)
>>>
>>> Say, when we having a lift team beer night? Feels like were long overdue
>>> for something like that!
>>>
>>
>> We really should!
>>
>>
>>>
>>> Cheers, Tim
>>>
>>> On 12/05/2009 14:50, "Viktor Klang"  wrote:
>>>
>>> I feel I owe Heiko a beer.
>>>
>>> On Tue, May 12, 2009 at 3:36 PM, David Pollak <
>>> feeder.of.the.be...@gmail.com> wrote:
>>>
>>> Very good stuff!
>>>
>>> Looking forward to playing with it today.
>>>
>>> Thanks for the hard work!
>>>
>>>
>>> On Tue, May 12, 2009 at 12:03 AM, Heiko Seeberger <
>>> heiko.seeber...@googlemail.com> wrote:
>>>
>>> Hi Lift folks,
>>>
>>> Today I checked in the first little step towards OSGi support:
>>>
>>>- Modules lift-util and lift-webkit are no longer plain vanilla JARs,
>>>but built as OSGi bundles (OSGi metadata in META-INF/MANIFEST.MF)
>>>- New module lift-osgi which offers (yet very limited) support for
>>>Lift application bundles (to ones you write)
>>>- New example module (under sites) examples-osgi with one (yet very
>>>limited) examples-osgi-hello bundle
>>>
>>> The first thing I would like to ask you is to verify that the changes to
>>> the existing modules are free of side effects: Lift should work without OSGi
>>> just like before. As the changes to lift-util and lift-webkit are merely in
>>> the manifest, I am very confident, but just to be sure ...
>>>
>>> And for those of you interested in OSGi:
>>> Currently there is only support for resources (templates) contributed
>>> from Lift-powered bundles to a composite Lift application. Yet no snippets,
>>> no custom dispatch, etc. Please take a look at sites/examples-osgi/hello.
>>> Note the new manifest header Lift-Config in the POM (the value is yet
>>> without any meaning). This bundle contributes its resources under webapp to
>>> a composite Lift application. The actual work is done by lift-osgi which is
>>> an implementation of the extender pattern. In order to run the example, I
>>> suggest you use Pax Runner 
>>>  with the scala and web profiles and the provided component configuration
>>> file at sites/examples-osgi/hello/hello.component. Else you will have to
>>> provision OSGi bundles for Scala, ScalaModules, Lift and all required
>>> dependencies (take a look into hello.component) by hand.
>>>
>>> Of course I would be very glad to get some reviews on my Scala code,
>>> because I guess there is still a long way of learning ahead ...
>>>
>>> Cheers
>>> Heiko
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Viktor Klang
>> Senior Systems Analyst
>>
>> >>
>>
>
>
> --
> My blog: heikoseeberger.name
> Follow me: twitter.com/hseeberger
> OSGi on Scala: www.scalamodules.org
> Lift, the simply functional web framework: liftweb.net
>



-- 
My blog: heikoseeberger.name
Follow me: twitter.com/hseeberger
OSGi on Scala: www.scalamodules.org
Lift, the simply functional web framework: liftweb.net

--~--~-~--~~~---~--~~
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 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: OSGi support for Lift

[Heiko Seeberger]

Beer sounds great (I am form Bavaria) and team beer night also ;-)How does
this work? Everybody chatting how much she has drunk?

Cheers
Heiko

2009/5/12 Viktor Klang 

>
>
> On Tue, May 12, 2009 at 3:59 PM, Timothy Perrett 
> wrote:
>
>>
>> If your buying Viktor ;-)
>>
>> Say, when we having a lift team beer night? Feels like were long overdue
>> for something like that!
>>
>
> We really should!
>
>
>>
>> Cheers, Tim
>>
>> On 12/05/2009 14:50, "Viktor Klang"  wrote:
>>
>> I feel I owe Heiko a beer.
>>
>> On Tue, May 12, 2009 at 3:36 PM, David Pollak <
>> feeder.of.the.be...@gmail.com> wrote:
>>
>> Very good stuff!
>>
>> Looking forward to playing with it today.
>>
>> Thanks for the hard work!
>>
>>
>> On Tue, May 12, 2009 at 12:03 AM, Heiko Seeberger <
>> heiko.seeber...@googlemail.com> wrote:
>>
>> Hi Lift folks,
>>
>> Today I checked in the first little step towards OSGi support:
>>
>>- Modules lift-util and lift-webkit are no longer plain vanilla JARs,
>>but built as OSGi bundles (OSGi metadata in META-INF/MANIFEST.MF)
>>- New module lift-osgi which offers (yet very limited) support for
>>Lift application bundles (to ones you write)
>>- New example module (under sites) examples-osgi with one (yet very
>>limited) examples-osgi-hello bundle
>>
>> The first thing I would like to ask you is to verify that the changes to
>> the existing modules are free of side effects: Lift should work without OSGi
>> just like before. As the changes to lift-util and lift-webkit are merely in
>> the manifest, I am very confident, but just to be sure ...
>>
>> And for those of you interested in OSGi:
>> Currently there is only support for resources (templates) contributed from
>> Lift-powered bundles to a composite Lift application. Yet no snippets, no
>> custom dispatch, etc. Please take a look at sites/examples-osgi/hello. Note
>> the new manifest header Lift-Config in the POM (the value is yet without any
>> meaning). This bundle contributes its resources under webapp to a composite
>> Lift application. The actual work is done by lift-osgi which is an
>> implementation of the extender pattern. In order to run the example, I
>> suggest you use Pax Runner 
>>  with the scala and web profiles and the provided component configuration
>> file at sites/examples-osgi/hello/hello.component. Else you will have to
>> provision OSGi bundles for Scala, ScalaModules, Lift and all required
>> dependencies (take a look into hello.component) by hand.
>>
>> Of course I would be very glad to get some reviews on my Scala code,
>> because I guess there is still a long way of learning ahead ...
>>
>> Cheers
>> Heiko
>>
>>
>>
>>
>
>
> --
> Viktor Klang
> Senior Systems Analyst
>
> >
>


-- 
My blog: heikoseeberger.name
Follow me: twitter.com/hseeberger
OSGi on Scala: www.scalamodules.org
Lift, the simply functional web framework: liftweb.net

--~--~-~--~~~---~--~~
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 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: OSGi support for Lift

[Viktor Klang]

On Tue, May 12, 2009 at 3:59 PM, Timothy Perrett wrote:

>
> If your buying Viktor ;-)
>
> Say, when we having a lift team beer night? Feels like were long overdue
> for something like that!
>

We really should!


>
> Cheers, Tim
>
> On 12/05/2009 14:50, "Viktor Klang"  wrote:
>
> I feel I owe Heiko a beer.
>
> On Tue, May 12, 2009 at 3:36 PM, David Pollak <
> feeder.of.the.be...@gmail.com> wrote:
>
> Very good stuff!
>
> Looking forward to playing with it today.
>
> Thanks for the hard work!
>
>
> On Tue, May 12, 2009 at 12:03 AM, Heiko Seeberger <
> heiko.seeber...@googlemail.com> wrote:
>
> Hi Lift folks,
>
> Today I checked in the first little step towards OSGi support:
>
>- Modules lift-util and lift-webkit are no longer plain vanilla JARs,
>but built as OSGi bundles (OSGi metadata in META-INF/MANIFEST.MF)
>- New module lift-osgi which offers (yet very limited) support for Lift
>application bundles (to ones you write)
>- New example module (under sites) examples-osgi with one (yet very
>limited) examples-osgi-hello bundle
>
> The first thing I would like to ask you is to verify that the changes to
> the existing modules are free of side effects: Lift should work without OSGi
> just like before. As the changes to lift-util and lift-webkit are merely in
> the manifest, I am very confident, but just to be sure ...
>
> And for those of you interested in OSGi:
> Currently there is only support for resources (templates) contributed from
> Lift-powered bundles to a composite Lift application. Yet no snippets, no
> custom dispatch, etc. Please take a look at sites/examples-osgi/hello. Note
> the new manifest header Lift-Config in the POM (the value is yet without any
> meaning). This bundle contributes its resources under webapp to a composite
> Lift application. The actual work is done by lift-osgi which is an
> implementation of the extender pattern. In order to run the example, I
> suggest you use Pax Runner 
>  with the scala and web profiles and the provided component configuration
> file at sites/examples-osgi/hello/hello.component. Else you will have to
> provision OSGi bundles for Scala, ScalaModules, Lift and all required
> dependencies (take a look into hello.component) by hand.
>
> Of course I would be very glad to get some reviews on my Scala code,
> because I guess there is still a long way of learning ahead ...
>
> Cheers
> Heiko
>
>
> >
>


-- 
Viktor Klang
Senior Systems Analyst

--~--~-~--~~~---~--~~
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 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: OSGi support for Lift

[Timothy Perrett]

If your buying Viktor ;-)

Say, when we having a lift team beer night? Feels like were long overdue for
something like that!

Cheers, Tim

On 12/05/2009 14:50, "Viktor Klang"  wrote:

> I feel I owe Heiko a beer.
> 
> On Tue, May 12, 2009 at 3:36 PM, David Pollak 
> wrote:
>> Very good stuff!
>> 
>> Looking forward to playing with it today.
>> 
>> Thanks for the hard work!
>> 
>> 
>> On Tue, May 12, 2009 at 12:03 AM, Heiko Seeberger
>>  wrote:
>>> Hi Lift folks,
>>> 
>>> Today I checked in the first little step towards OSGi support:
>>> * Modules lift-util and lift-webkit are no longer plain vanilla JARs, but
>>> built as OSGi bundles (OSGi metadata in META-INF/MANIFEST.MF)
>>> * New module lift-osgi which offers (yet very limited) support for Lift
>>> application bundles (to ones you write)
>>> * New example module (under sites) examples-osgi with one (yet very
>>> limited) examples-osgi-hello bundle
>>> The first thing I would like to ask you is to verify that the changes to the
>>> existing modules are free of side effects: Lift should work without OSGi
>>> just like before. As the changes to lift-util and lift-webkit are merely in
>>> the manifest, I am very confident, but just to be sure ...
>>> 
>>> And for those of you interested in OSGi:
>>> Currently there is only support for resources (templates) contributed from
>>> Lift-powered bundles to a composite Lift application. Yet no snippets, no
>>> custom dispatch, etc. Please take a look at sites/examples-osgi/hello. Note
>>> the new manifest header Lift-Config in the POM (the value is yet without any
>>> meaning). This bundle contributes its resources under webapp to a composite
>>> Lift application. The actual work is done by lift-osgi which is an
>>> implementation of the extender pattern. In order to run the example, I
>>> suggest you use Pax Runner 
>>> with the scala and web profiles and the provided component configuration
>>> file at sites/examples-osgi/hello/hello.component. Else you will have to
>>> provision OSGi bundles for Scala, ScalaModules, Lift and all required
>>> dependencies (take a look into hello.component) by hand.
>>> 
>>> Of course I would be very glad to get some reviews on my Scala code, because
>>> I guess there is still a long way of learning ahead ...
>>> 
>>> Cheers
>>> Heiko


--~--~-~--~~~---~--~~
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 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: OSGi support for Lift

[Viktor Klang]

I feel I owe Heiko a beer.

On Tue, May 12, 2009 at 3:36 PM, David Pollak  wrote:

> Very good stuff!
> Looking forward to playing with it today.
>
> Thanks for the hard work!
>
> On Tue, May 12, 2009 at 12:03 AM, Heiko Seeberger <
> heiko.seeber...@googlemail.com> wrote:
>
>> Hi Lift folks,
>>
>> Today I checked in the first little step towards OSGi support:
>>
>>- Modules lift-util and lift-webkit are no longer plain vanilla JARs,
>>but built as OSGi bundles (OSGi metadata in META-INF/MANIFEST.MF)
>>- New module lift-osgi which offers (yet very limited) support for
>>Lift application bundles (to ones you write)
>>- New example module (under sites) examples-osgi with one (yet very
>>limited) examples-osgi-hello bundle
>>
>> The first thing I would like to ask you is to verify that the changes to
>> the existing modules are free of side effects: Lift should work without OSGi
>> just like before. As the changes to lift-util and lift-webkit are merely in
>> the manifest, I am very confident, but just to be sure ...
>>
>> And for those of you interested in OSGi:
>> Currently there is only support for resources (templates) contributed from
>> Lift-powered bundles to a composite Lift application. Yet no snippets, no
>> custom dispatch, etc. Please take a look at sites/examples-osgi/hello.
>> Note the new manifest header Lift-Config in the POM (the value is yet
>> without any meaning). This bundle contributes its resources under webappto a 
>> composite Lift application. The actual work is done by
>> lift-osgi which is an implementation of the extender pattern. In order to
>> run the example, I suggest you use Pax 
>> Runnerwith the scala and web 
>> profiles and the provided component configuration
>> file at sites/examples-osgi/hello/hello.component. Else you will have to
>> provision OSGi bundles for Scala, ScalaModules, Lift and all required
>> dependencies (take a look into hello.component) by hand.
>>
>> Of course I would be very glad to get some reviews on my Scala code,
>> because I guess there is still a long way of learning ahead ...
>>
>> Cheers
>> Heiko
>> --
>> My blog: heikoseeberger.name
>> Follow me: twitter.com/hseeberger
>> OSGi on Scala: www.scalamodules.org
>> Lift, the simply functional web framework: liftweb.net
>>
>>
>>
>
>
> --
> Lift, the simply functional web framework http://liftweb.net
> Beginning Scala http://www.apress.com/book/view/1430219890
> Follow me: http://twitter.com/dpp
> Git some: http://github.com/dpp
>
> >
>


-- 
Viktor Klang
Senior Systems Analyst

--~--~-~--~~~---~--~~
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 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: OSGi support for Lift

[David Pollak]

Very good stuff!
Looking forward to playing with it today.

Thanks for the hard work!

On Tue, May 12, 2009 at 12:03 AM, Heiko Seeberger <
heiko.seeber...@googlemail.com> wrote:

> Hi Lift folks,
>
> Today I checked in the first little step towards OSGi support:
>
>- Modules lift-util and lift-webkit are no longer plain vanilla JARs,
>but built as OSGi bundles (OSGi metadata in META-INF/MANIFEST.MF)
>- New module lift-osgi which offers (yet very limited) support for Lift
>application bundles (to ones you write)
>- New example module (under sites) examples-osgi with one (yet very
>limited) examples-osgi-hello bundle
>
> The first thing I would like to ask you is to verify that the changes to
> the existing modules are free of side effects: Lift should work without OSGi
> just like before. As the changes to lift-util and lift-webkit are merely in
> the manifest, I am very confident, but just to be sure ...
>
> And for those of you interested in OSGi:
> Currently there is only support for resources (templates) contributed from
> Lift-powered bundles to a composite Lift application. Yet no snippets, no
> custom dispatch, etc. Please take a look at sites/examples-osgi/hello.
> Note the new manifest header Lift-Config in the POM (the value is yet
> without any meaning). This bundle contributes its resources under webappto a 
> composite Lift application. The actual work is done by
> lift-osgi which is an implementation of the extender pattern. In order to
> run the example, I suggest you use Pax 
> Runnerwith the scala and web 
> profiles and the provided component configuration
> file at sites/examples-osgi/hello/hello.component. Else you will have to
> provision OSGi bundles for Scala, ScalaModules, Lift and all required
> dependencies (take a look into hello.component) by hand.
>
> Of course I would be very glad to get some reviews on my Scala code,
> because I guess there is still a long way of learning ahead ...
>
> Cheers
> Heiko
> --
> My blog: heikoseeberger.name
> Follow me: twitter.com/hseeberger
> OSGi on Scala: www.scalamodules.org
> Lift, the simply functional web framework: liftweb.net
>
> >
>


-- 
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
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 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: OSGi support for Lift

[Heiko Seeberger]

Very good point, Tim!Everything is Apache License 2.0.

Heiko

2009/5/12 Timothy Perrett 

>
> Oh, one other thing - are the new dependencies present in the osgi
> pom.xml all under non-gpl licenses? DPP will be able to tell you more
> but im sure we have to be carfull about what types of licenses we
> distribute with Lift.
>
> Thanks, Tim
>
> On May 12, 10:25 am, Timothy Perrett  wrote:
> > Oh man, this is going to be nice - loving your work Heiko feels
> > like this is the first brick in the road to something extremely
> > funky.
> >
> > Cheers, Tim
> >
> > On May 12, 8:03 am, Heiko Seeberger 
> > wrote:
> >
> >
> >
> > > Hi Lift folks,
> >
> > > Today I checked in the first little step towards OSGi support:
> >
> > >- Modules lift-util and lift-webkit are no longer plain vanilla
> JARs, but
> > >built as OSGi bundles (OSGi metadata in META-INF/MANIFEST.MF)
> > >- New module lift-osgi which offers (yet very limited) support for
> Lift
> > >application bundles (to ones you write)
> > >- New example module (under sites) examples-osgi with one (yet very
> > >limited) examples-osgi-hello bundle
> >
> > > The first thing I would like to ask you is to verify that the changes
> to the
> > > existing modules are free of side effects: Lift should work without
> OSGi
> > > just like before. As the changes to lift-util and lift-webkit are
> merely in
> > > the manifest, I am very confident, but just to be sure ...
> >
> > > And for those of you interested in OSGi:
> > > Currently there is only support for resources (templates) contributed
> from
> > > Lift-powered bundles to a composite Lift application. Yet no snippets,
> no
> > > custom dispatch, etc. Please take a look at sites/examples-osgi/hello.
> Note
> > > the new manifest header Lift-Config in the POM (the value is yet
> without any
> > > meaning). This bundle contributes its resources under webapp to a
> composite
> > > Lift application. The actual work is done by lift-osgi which is an
> > > implementation of the extender pattern. In order to run the example, I
> > > suggest you use Pax Runner
> > > with the scala and web
> > > profiles and the provided component configuration
> > > file at sites/examples-osgi/hello/hello.component. Else you will have
> to
> > > provision OSGi bundles for Scala, ScalaModules, Lift and all required
> > > dependencies (take a look into hello.component) by hand.
> >
> > > Of course I would be very glad to get some reviews on my Scala code,
> because
> > > I guess there is still a long way of learning ahead ...
> >
> > > Cheers
> > > Heiko
> > > --
> > > My blog: heikoseeberger.name
> > > Follow me: twitter.com/hseeberger
> > > OSGi on Scala:www.scalamodules.org
> > > Lift, the simply functional web framework: liftweb.net
> >
>


-- 
My blog: heikoseeberger.name
Follow me: twitter.com/hseeberger
OSGi on Scala: www.scalamodules.org
Lift, the simply functional web framework: liftweb.net

--~--~-~--~~~---~--~~
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 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: OSGi support for Lift

[Timothy Perrett]

Oh, one other thing - are the new dependencies present in the osgi
pom.xml all under non-gpl licenses? DPP will be able to tell you more
but im sure we have to be carfull about what types of licenses we
distribute with Lift.

Thanks, Tim

On May 12, 10:25 am, Timothy Perrett  wrote:
> Oh man, this is going to be nice - loving your work Heiko feels
> like this is the first brick in the road to something extremely
> funky.
>
> Cheers, Tim
>
> On May 12, 8:03 am, Heiko Seeberger 
> wrote:
>
>
>
> > Hi Lift folks,
>
> > Today I checked in the first little step towards OSGi support:
>
> >    - Modules lift-util and lift-webkit are no longer plain vanilla JARs, but
> >    built as OSGi bundles (OSGi metadata in META-INF/MANIFEST.MF)
> >    - New module lift-osgi which offers (yet very limited) support for Lift
> >    application bundles (to ones you write)
> >    - New example module (under sites) examples-osgi with one (yet very
> >    limited) examples-osgi-hello bundle
>
> > The first thing I would like to ask you is to verify that the changes to the
> > existing modules are free of side effects: Lift should work without OSGi
> > just like before. As the changes to lift-util and lift-webkit are merely in
> > the manifest, I am very confident, but just to be sure ...
>
> > And for those of you interested in OSGi:
> > Currently there is only support for resources (templates) contributed from
> > Lift-powered bundles to a composite Lift application. Yet no snippets, no
> > custom dispatch, etc. Please take a look at sites/examples-osgi/hello. Note
> > the new manifest header Lift-Config in the POM (the value is yet without any
> > meaning). This bundle contributes its resources under webapp to a composite
> > Lift application. The actual work is done by lift-osgi which is an
> > implementation of the extender pattern. In order to run the example, I
> > suggest you use Pax Runner
> > with the scala and web
> > profiles and the provided component configuration
> > file at sites/examples-osgi/hello/hello.component. Else you will have to
> > provision OSGi bundles for Scala, ScalaModules, Lift and all required
> > dependencies (take a look into hello.component) by hand.
>
> > Of course I would be very glad to get some reviews on my Scala code, because
> > I guess there is still a long way of learning ahead ...
>
> > Cheers
> > Heiko
> > --
> > My blog: heikoseeberger.name
> > Follow me: twitter.com/hseeberger
> > OSGi on Scala:www.scalamodules.org
> > Lift, the simply functional web framework: liftweb.net
--~--~-~--~~~---~--~~
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 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: OSGi support for Lift

[Timothy Perrett]

Oh man, this is going to be nice - loving your work Heiko feels
like this is the first brick in the road to something extremely
funky.

Cheers, Tim

On May 12, 8:03 am, Heiko Seeberger 
wrote:
> Hi Lift folks,
>
> Today I checked in the first little step towards OSGi support:
>
>    - Modules lift-util and lift-webkit are no longer plain vanilla JARs, but
>    built as OSGi bundles (OSGi metadata in META-INF/MANIFEST.MF)
>    - New module lift-osgi which offers (yet very limited) support for Lift
>    application bundles (to ones you write)
>    - New example module (under sites) examples-osgi with one (yet very
>    limited) examples-osgi-hello bundle
>
> The first thing I would like to ask you is to verify that the changes to the
> existing modules are free of side effects: Lift should work without OSGi
> just like before. As the changes to lift-util and lift-webkit are merely in
> the manifest, I am very confident, but just to be sure ...
>
> And for those of you interested in OSGi:
> Currently there is only support for resources (templates) contributed from
> Lift-powered bundles to a composite Lift application. Yet no snippets, no
> custom dispatch, etc. Please take a look at sites/examples-osgi/hello. Note
> the new manifest header Lift-Config in the POM (the value is yet without any
> meaning). This bundle contributes its resources under webapp to a composite
> Lift application. The actual work is done by lift-osgi which is an
> implementation of the extender pattern. In order to run the example, I
> suggest you use Pax Runner
> with the scala and web
> profiles and the provided component configuration
> file at sites/examples-osgi/hello/hello.component. Else you will have to
> provision OSGi bundles for Scala, ScalaModules, Lift and all required
> dependencies (take a look into hello.component) by hand.
>
> Of course I would be very glad to get some reviews on my Scala code, because
> I guess there is still a long way of learning ahead ...
>
> Cheers
> Heiko
> --
> My blog: heikoseeberger.name
> Follow me: twitter.com/hseeberger
> OSGi on Scala:www.scalamodules.org
> Lift, the simply functional web framework: liftweb.net
--~--~-~--~~~---~--~~
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 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---