On Thu, Jan 21, 2010 at 1:24 AM, aw anth...@whitford.com wrote:
I think I discovered that my issue is related to the fact that the
code is part of a CometActor/CometListener, and it sounds like S isn't
fully functional from this perspective... My clue was the
inStatefulScope_? method
Tim,
thank you for your reply.
I've updated updated to 2.0-SNAPSHOT now. The submenu items still do
not appear, though.
Do I need to set some options or is it still the bug you mentioned?
Regards,
Joachim
On Jan 16, 4:36 pm, Tim Nelson tnell...@gmail.com wrote:
There was a bug that's been
Try:
mvn -U clean jetty:run
Cheers, Tim
On 16 Jan 2010, at 17:15, Tim Nelson wrote:
Did you clean out your code before you updated? I don't use maven,
so I'm not sure of the exact command, but that seems to come up a lot
on this list.
If you indeed did clean out the code before updating,
Tim,
thanks again for the reply.
I did clean out the old code.
In 1.1 I've hit the bug, I think.
I found the reason why it did not work with 2.0. I had to use
expandAll and had to adjust the css for the menu.
It's working fine now.
Thanks guys!
Joachim
On Jan 16, 6:15 pm, Tim Nelson
On Wed, Nov 4, 2009 at 10:02 AM, jon jonhoff...@gmail.com wrote:
Hi,
I just noticed OrderBy statements cause Inner selects to break in h2:
I query such as: User.findAll(In(User.id, Dog.owner, OrderBy(Dog.name,
Ascending)), MaxRows(5))
Produces:
Message: org.h2.jdbc.JdbcSQLException:
I just verified that the newer h2 fixes the problem. Thanks for
investigating!
On Nov 5, 6:33 pm, David Pollak feeder.of.the.be...@gmail.com wrote:
On Wed, Nov 4, 2009 at 10:02 AM, jon jonhoff...@gmail.com wrote:
Hi,
I just noticed OrderBy statements cause Inner selects to break in h2:
On Thu, Nov 5, 2009 at 3:47 PM, jon jonhoff...@gmail.com wrote:
I just verified that the newer h2 fixes the problem. Thanks for
investigating!
Sure thing. Party on!
On Nov 5, 6:33 pm, David Pollak feeder.of.the.be...@gmail.com wrote:
On Wed, Nov 4, 2009 at 10:02 AM, jon
On Wed, Nov 4, 2009 at 10:02 AM, jon jonhoff...@gmail.com wrote:
Hi,
I just noticed OrderBy statements cause Inner selects to break in h2:
I query such as: User.findAll(In(User.id, Dog.owner, OrderBy(Dog.name,
Ascending)), MaxRows(5))
Produces:
Message: org.h2.jdbc.JdbcSQLException:
That would be great. Would it also be published to the scala-tools
repo?
On Nov 4, 1:18 pm, David Pollak feeder.of.the.be...@gmail.com wrote:
On Wed, Nov 4, 2009 at 10:02 AM, jon jonhoff...@gmail.com wrote:
Hi,
I just noticed OrderBy statements cause Inner selects to break in h2:
I
Wow, congrats!
On Nov 4, 1:46 pm, David Pollak feeder.of.the.be...@gmail.com wrote:
On Wed, Nov 4, 2009 at 10:36 AM, jon jonhoff...@gmail.com wrote:
That would be great. Would it also be published to the scala-tools
repo?
Dunno. Got to figure out how to get it published. But we can
On Wed, Nov 4, 2009 at 11:04 AM, jon jonhoff...@gmail.com wrote:
Wow, congrats!
No... not that way... I've got 5 year old twins... but our nanny's on
vacation and my wife http://www.orrick.com/lawyers/Bio.asp?ID=227282 is
way too busy on a huge case, so I'm primary childcare.
On Nov 4,
After the fix, I'm having a different problem now with latest 1.1-SNAPSHOT
(10/30 1:54:48PM build) with tables in the DB that have uppercase anywhere
in either the dbTableName or dbColumnName name... the Mapper is creating SQL
that throws exceptions due to unknown column in MySQL (which is case
I'm going to revert the fix.
I'm going to add tests for mixed-case column and table names. If you care
to donate some of these tests, that'd be great.
Please open a ticket.
On Sat, Oct 31, 2009 at 5:35 AM, Troy Noble econop...@gmail.com wrote:
After the fix, I'm having a different problem
Thanks for your support... and I'm very sorry to be the instigator of the
breakage. I feel really bad that everything broke for all the MySQL and SQL
server users (I gotta believe I'm not the only freak still using MySQL or
SQL Server ;-)
The only way to INTEGRATION test right now would be to
David,
I opened ticket # 151. And I have some test cases written for uppercase
dbTableName and dbColumnName. They are very simple-minded re-use of the Dog
mapped class, but they do demostrate the same sort of failure behavior I was
seeing in 1.1-SNAPSHOT, this time against the pre-145-fix
On Thu, Oct 29, 2009 at 10:15 PM, Troy Noble econop...@gmail.com wrote:
We are using Mapper with a legacy database with many columns that we
are not allowed to rename in our database. For example CREATE_DATE
for which we created the following seemingly simple mapped field in
our model:
Certainly. I will open a ticket. I might have found 3 different issues...
(one each for Mapper, schemify, CRUDify) all related to dbColumnName (see
details below).
I created a new scaled down project against 1.1-SNAPSHOT and an embedded
Derby database, and it exhibits the Mapper dbColumnName
I have seen EXACTLY same behavior when dbColumnName returned _upcased_ names
lopex
--~--~-~--~~~---~--~~
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
Turns out this was the problem. Some RDBMSs are case insensitive on
table/column names... others are not.
I committed a fix (now on master thanks to fast review board turn-around)
that causes all table and column names to lower case for all SQL
transactions.
2009/10/30 Marcin Mielżyński
Thanks. I'll give it try. Dumb newbie question though... how do I access
the update? Git + build from github, or can I just grab the latest
1.1-SNAPSHOT?
Thanks again, Troy
On Fri, Oct 30, 2009 at 3:01 PM, David Pollak feeder.of.the.be...@gmail.com
wrote:
Turns out this was the problem.
On Fri, Oct 30, 2009 at 3:06 PM, Troy Noble econop...@gmail.com wrote:
Thanks. I'll give it try. Dumb newbie question though... how do I access
the update? Git + build from github, or can I just grab the latest
1.1-SNAPSHOT?
Check http://hudson.scala-tools.org/job/Lift/
You can see if the
Jack,
This question has been asked quite a number of times recently on list.
Change:
version1.0/version
on the liftweb dependencies in your pom.xml to be:
version1.1-SNAPSHOT/version
That will give you the latest HEAD build. If you want a known point in
time, use M6:
version1.1-M6/version
Thanks Tim. And next time I will search more before asking.
On Sun, Oct 25, 2009 at 2:26 PM, Timothy Perrett timo...@getintheloop.euwrote:
Jack,
This question has been asked quite a number of times recently on list.
Change:
version1.0/version
on the liftweb dependencies in your pom.xml
Your welcome Jack. Have fun.
Cheers, Tim
On 25 Oct 2009, at 18:28, Jack Widman wrote:
Thanks Tim. And next time I will search more before asking.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift group.
To
Anyways, I was definitely screwed up ... forcing maven to actually do
what it was supposed to fixed my problem. Thanks for the pointer
Marius.
~Thomas
On Sat, Oct 3, 2009 at 5:39 PM, Thomas Rampelberg pyronic...@gmail.com wrote:
I thought that I'd just updated all the versions . from that
What verions of lift are you using? It appears that lift-util is a
different version than lift ?
Br's,
Marius
On Oct 3, 11:11 pm, Thomas Rampelberg pyronic...@gmail.com wrote:
I just synced up to main this morning and now whenever I try and use
one of my snippets, I'm getting the traceback
I thought that I'd just updated all the versions . from that stack
trace, how do you tell which version lift-util is?
On Sat, Oct 3, 2009 at 1:39 PM, marius d. marius.dan...@gmail.com wrote:
What verions of lift are you using? It appears that lift-util is a
different version than lift ?
Thanks for taking a look at this issue. If the solution is as simple
as clearing/removing a cookie, that's great news. I'll give it a try
and let you know how it worked. Thanks again!
- Mark
On Aug 26, 2:57 am, Atsuhiko Yamanaka atsuhiko.yaman...@gmail.com
wrote:
Hi,
On Mon, Aug 17, 2009 at
I was able to confirm that clearing the cookie gets rid of the
ClassNotFoundException.
I have a hypothesis as to what happened: It appears that sometime
after the M4 milestone, the SessionToServletBridge moved from the
net.liftweb.http package to net.liftweb.http.provider.servlet. So, the
M4
I was able to confirm that clearing the cookie gets rid of the
ClassNotFoundException.
I have a hypothesis as to what happened: It appears that sometime
after the M4 milestone, the SessionToServletBridge moved from the
net.liftweb.http package to net.liftweb.http.provider.servlet. So, the
M4
Ok here's the problem stripped down. The merge happens but the head
node isn't being removed from the body
Let me know if you'd like it in some other format.
templates-hidden/outer.html:
html
head
meta name=description content=Head Merge Test /
/head
body
lift:bind name=content
Many 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
Hi,
On Mon, Aug 17, 2009 at 9:18 AM, Mark Tyemark...@gmail.com wrote:
...
I don't know if compatibility with App Engine is a priority for the
Lift team, but if this doesn't get fixed, I face an ugly choice
between remaining frozen at 1.1-M4 as Lift development moves forward,
or migrating
Probably caused by this if you're in a dev environment:
http://groups.google.com/group/liftweb/t/90750187a6c29c2c
On Aug 26, 9:36 pm, E. Biggs tacoban...@gmail.com wrote:
Hi there,
I just did a mvn -U jetty:run
and my site that I know was working fine before is now broken with
this error
I've just pushed a new version live that will behave more gracefully if the
xsd cannot be loaded.
On Wed, Aug 26, 2009 at 7:39 PM, Justin Reardon justin.rear...@gmail.comwrote:
Probably caused by this if you're in a dev environment:
http://groups.google.com/group/liftweb/t/90750187a6c29c2c
Thanks David! My pages now render - although broken... the cause
appears to be a failed head merge between my template's head and the
surrounding template's head.
On Aug 26, 7:51 pm, David Pollak feeder.of.the.be...@gmail.com
wrote:
I've just pushed a new version live that will behave more
On Wed, Aug 26, 2009 at 8:32 PM, E. Biggs tacoban...@gmail.com wrote:
Thanks David! My pages now render - although broken... the cause
appears to be a failed head merge between my template's head and the
surrounding template's head.
Can you post an example of the failing use case and I'll
Hi,
On Wed, Aug 26, 2009 at 6:35 AM, David
Pollakfeeder.of.the.be...@gmail.com wrote:
Atsuhiko-san,
Have you seen this note on the Lift list?
I have not seen such a note on this list yet and I had not tried
1.1-SNAPSHOT on
GAE/J in these days, but today I tried it and have also encountered
On Tue, Apr 28, 2009 at 9:08 AM, Andrew Scherpbier and...@scherpbier.orgwrote:
Are the 1.1-SNAPSHOT API docs online somewhere?
http://scala-tools.org/mvnsites-snapshots/liftweb/lift-util/scaladocs/index.html
http://scala-tools.org/mvnsites-snapshots/liftweb/lift-webkit/scaladocs/index.html
The webkit docs are here:
http://scala-tools.org/mvnsites-snapshots/liftweb/lift-webkit/scaladocs/inde
x.html
If you want to generate them locally, just download the lift src and run
this from the top level directory:
mvn install scala:doc
Cheers, Tim
On 28/04/2009 17:08, Andrew Scherpbier
On Wed, Mar 4, 2009 at 9:47 PM, Lee Mighdoll leemighd...@gmail.com wrote:
I've been thinking about browser-server data sync for use in my next
project. Sync is potentially more interesting than RPC style ajax,
especially for rich clients, and I think sync could be a grand thing to add
to
41 matches
Mail list logo
