Put the determination of how to add the <? xml ?> stuff into LiftRules.

Currently MappedManyToMany.children throws an error when, in the process of looking up the child elements via the join table, a join found to be broken (no child element for it).
Instead, it should use flatMap to skip broken joins. This requires some conversion of indexes between the join list and the children list.

It is spelled reset.pasword.confirmarion

Update Lift and JPA page on Wiki

Lighthouse #23: https://liftweb.lighthouseapp.com/projects/26102/tickets/23

Support for changing the context root for requests so the root can be blank even if the actual context path is not or that a context path can be added (and all requests will be rewritten removing that context path from the head of the path) or subtracted.

Add Twitter IDs to the team page.

Lighthouse #3: https://liftweb.lighthouseapp.com/projects/26102/tickets/3

There should be support for image maps in SHtml. See https://groups.google.com/group/liftweb/browse_frm/thread/84fee9386108a922?hl=en#

https://groups.google.com/group/liftweb/browse_thread/thread/39d38f2124b4b2c7

Problems with MappedStringIndex (Derby / H2)

Lighthouse #26: https://liftweb.lighthouseapp.com/projects/26102/tickets/26

the default autocomplete options i.e.

val autocompleteOptions = JsRaw(...

need to be more easily set. I had to override and copy-paste the render function to change these. Making them settable without extending the class would be ideal. making the autocompleteOptions val an overridable outer function would be fine though.

It should be reconfigured to use Joda Time

It would be nice if LIftRules has support for formatting/parsing of numbers in the same way as for dates. Both integers and decimals should be supported

When this is complete, Mapper should use this machinery in MappedInt (for thousand separators) and MappedDouble/Decimal

Problem:
On heavily JavaScript based forms (sections appearing/enabling depending on user input) it is good practice to outsource form creation code to widget/component classes (homegrown). It improves readability of Snippet code and reusability of widgets. For event registration and other client side code, each component class would generate a head/lift:tail and a script tag. While head/tail tags are merged by the Lift framework, the resulting HTML code still remains cluttered with script tags (example below).

Suggested solution:
Introduce a script merge that similarly to head/tail merge merges all script tags in head into one and all script tags in tail into a second one.

ECMA-262 (https://www.ecma-international.org/publications/files/ECMA-ST/ECMA-262.pdf) section
11.1.5 describes the object initializer syntax as being either empty braces or braces containing PropertyNameAndValueList. PropertyNameAndValueList is comma-separated sequence of PropertyName : AssignmentExpression. PropertyName is one of Identifier, StringLiteral, or NumericLiteral.

However, JE.JsObj.apply and JsObj both require the key to be a String, so what I would think the natural translation from the JavaScript:

{
    headers: {
        1: { sortable: false }
    }
}

To Lift:

JsObj("headers" -> JsObj(1 -> JsObj("sortable" -> false)))

Does not work:

<console>:7: error: type mismatch;
 found   : (Int, net.liftweb.http.js.JsObj)
 required: (String, net.liftweb.http.js.JsExp)
       JsObj("headers" -> JsObj(1 -> JsObj("sortable" -> false)))
                                  ^

as 1 is not a String. This is trivially worked around by either making ones own JsExp or by converting the Int to a String:

JsObj("headers" -> JsObj("1" -> JsObj("sortable" -> false)))

Apparently because JavaScript is entirely willing to treat strings as numbers and vice versa in property names, however it seems like it would be more natural.

This is low priority to me.

Related discussion here: https://groups.google.com/group/liftweb/browse_thread/thread/7de2d785a38bf27f

Br's,
Marius

Hi, i newbie for lift and scala.. im using eclipse. i create project by maven and i try to run. thats all bu i get :

INFO - CREATE TABLE users (id BIGINT NOT NULL GENERATED ALWAYS AS IDENTITY , firstname VARCHAR(32) , lastname VARCHAR(32) , email VARCHAR(48) , locale VARCHAR(16) , timezone VARCHAR(32) , password_pw VARCHAR(48) , password_slt VARCHAR(20) , textarea VARCHAR(2048) , superuser SMALLINT , validated SMALLINT , uniqueıd VARCHAR(32))
INFO - ALTER TABLE users ADD CONSTRAINT users_PK PRIMARY KEY(id)
INFO - ALTER TABLE users ADD COLUMN id BIGINT NOT NULL GENERATED ALWAYS AS IDENTITY
ERROR - Failed to Boot
java.sql.SQLSyntaxErrorException: ALTER TABLE statement cannot add an IDENTITY column to a table.
at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)

at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)

Add core nl_NL language file. Will also add as default nl language file since nl_BE isn't available.

Add Ext Core support to Lift

Please make the Scala identifier to database identifier translation convention dependent on whether the database supports case sensitive or case insensitive identifiers.

For example, Hibernate offers an Enhanced Naming Convention that translates Java camelCase to a more Oracle friendly snake_case. I am interested in doing the same thing with Lift Mapper/
Record. In the mean time, I need to override dbTableName and dbColumnName, but I'd like to avoid that and just agree on the convention.

I could imagine that the Database Provider would maintain a flag to say whether the database is case sensitive or not, and then based on that flag, would pass either the camelCase directly (for case sensitive), or snake_case(camelCase) (for case insensitive).

I am specifically using Lift Mapper with Oracle, but I think this issue relates to Lift Record too as well as any other case insensitive database.

See discussion: https://groups.google.com/group/liftweb/t/e7f85ede13b303da

Please add valMinLen and valMaxLen validation functions to net.liftweb.record.field.StringField. If it's preferred to put them in a separate helper object that would be fine as well.

Also, a companion object for LocaleField that has a list of all possible locales (similar to TimeZoneField) would be nice.

Thanks

The *SNAPSHOT-sources.jar doesn't seem to contain any scala source files, only static resources

Add a way for allowing easy specification of custom HTTP header attributes.

Br's,
Marius

Run lift-examples/example from SNAPSHOT (11/5) on a local server, autocompletion isn't happening on the AJAX Samples page. The rest of the Ajax stuff seems to work fine.

Normally, the Lift session is not created in the rewrite phase. It could be useful to manually force a lift session to be created.

More details here: https://groups.google.com/group/liftweb/browse_thread/thread/efb58c2bd56556ef

Within the session scope. This is the phase that should be used by CRUDify.

Discussion(s):
1) https://groups.google.com/group/liftweb/browse_thread/thread/bca1ae85f1fa6a3a/b5b97a0da8b517f9?lnk=gst&q=metamapper#b5b97a0da8b517f9
2) https://groups.google.com/group/liftweb/browse_thread/thread/e295526e8a7905c8/d35f233879445ad7?lnk=gst&q=metamapper#d35f233879445ad7

Runnable test case here:
https://github.com/opyate/bug.liftweb.metamapper

To re-create:

export JETPORT=8081
cd /tmp
git clone git://github.com/opyate/bug.liftweb.metamapper.git
cd bug.liftweb.metamapper/metamapperbug
mvn -U clean jetty:run -Djetty.port=$JETPORT
# now open your browser on https://localhost:$JETPORT

#+ and enter an ID into the input box and click save

Generated exception:
Message: java.lang.NullPointerException: Trying to open an empty Box

net.liftweb.common.EmptyBox.open_$bang(Box.scala:370)
net.liftweb.common.EmptyBox.open_$bang(Box.scala:366)
net.liftweb.mapper.MetaMapper$$anonfun$runAppliers$1$1.apply(MetaMapper.scala:617)

Currently, the "def menus" collide.

Details here:https://groups.google.com/group/liftweb/browse_thread/thread/6f17647690d9aa59/32ccdf5e2907ba83#32ccdf5e2907ba83

if a Ajax functions throws exceptions these are not provided to LiftRules.exceptionHander.

Br's,
Marius

https://groups.google.com/group/liftweb/browse_thread/thread/e189fc4a2726a94f

Hi,

Using the default MegaProtoUser trait for my User class, the following query fails on oracle but works just fine on H2:

    scala> User.findAll(By(User.superUser, false))
    java.sql.SQLException: Invalid column type
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:208)
    at oracle.jdbc.driver.OraclePreparedStatement.setObjectCritical(OraclePreparedStatement.java:9168)
    at ora...

Surprisingly however, the following statement works as it should:

    scala> User.findAll.head.superUser
    res22: object com.mi.ahl.hal.ooh.model.User#superUser = true

Is there a quick fix for this issue?

Regards, Mathias

Add Kris Nuttycombe's DataBinding types & traits to lift-webkit.

If, for example, I have some json:

{ "user": {

"id": 12,
"name": "Harry",
"age": 31,

} }

I should be able to construct a User Mapper object such that I can then do:

val user = // build user object from json
user.age(32).save

and have the data be correctly saved back to the DB.

https://groups.google.com/group/liftweb/browse_thread/thread/6db3cded182fe7ca