Hi, I know I just raved about #liftweb error reporting on Twitter,
but... now that I found out what was wrong, I still have a gripe about
it. I am very unforgiving on error reporting logic, but most of the
time people's error handling is so hopeless that I just throw up my
arms and emit some mock
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
Hi folks,
I have an obscure problem with rendering on Safari (both 3 and 4). I
get the same behavior using 1.1-M1 and 1.1-M3.
When I initiate any ajaxy traffic, be it a text field, a checkbox or a
drop-down, the entire content area literally collapses onto itself.
From what I can tell it
AM, Kjetil Valstadsve valstad...@gmail.comwrote:
Hi folks,
I have an obscure problem with rendering on Safari (both 3 and 4). I
get the same behavior using 1.1-M1 and 1.1-M3.
When I initiate any ajaxy traffic, be it a text field, a checkbox or a
drop-down, the entire content area
On Jun 20, 5:01 pm, Heiko Seeberger heiko.seeber...@googlemail.com
wrote:
Of course I would like to stick to the more common approach described above.
Maybe you want to take a look at the POMs and analyze if/how the Felix
Bundle plug-in can pick the compressed JavaScript libraries?
I was
Looking at the OSGi-enabled Lift poms, I find it curious that the M.O.
for building bundles looks like a two-step:
1) Build a bundle with maven-bundle-plugin
2) Dig out the manifest and use it in the jar
This works ok, but given my experience with Maven, it seems to be a
case of challenging
