attribute with the same name but different prefixes should be ok as
long as the prefixes are bound to namespace URL's.
Br's,
Marius
On Jun 3, 12:24 am, Derek Chen-Becker dchenbec...@gmail.com wrote:
I think that this has been discussed on the list before. It's definitely an
issue with having
On 3 Jun 2009, marius d. wrote:
attribute with the same name but different prefixes should be ok as
long as the prefixes are bound to namespace URL's.
But the problem here is that the attributes are in an inner template,
which, I presume, will be read before the outer template (with the
This is a bug in the Scala XML parser... I'll fix (work around) the bug
today.
On Wed, Jun 3, 2009 at 7:20 AM, Jeppe Nejsum Madsen je...@ingolfs.dkwrote:
On 3 Jun 2009, marius d. wrote:
attribute with the same name but different prefixes should be ok as
long as the prefixes are bound to
On 3 Jun 2009, David Pollak wrote:
I've pushed up a fix
Excellent, thanks! When I finally figured out how to use the li_*
attributes I thought it was a very nice way to make the snippets
configurable. Great was the dismay when I found it didn't work :-(
/Jeppe
Please post the exception
On Tue, Jun 2, 2009 at 7:47 AM, Jeppe Nejsum Madsen je...@ingolfs.dkwrote:
Running 1.1-SNAPSHOT, the following construct
lift:Menu.builder li_path:class=pathclass
li_item:class=itemclass/
Seems to results in an exception when Lift processes the template.
On 2 Jun 2009, David Pollak wrote:
Please post the exception
The code is just the basic archetype with the above template changes and
a new menu item as child of Home to show the path style.
No exception on the console, but I get this in the browser:
Exception occured while processing /
This is an XML parsing error. Something in your XML is non-parsable. It's
not Lift, but the underlying XML parsing library.
On Tue, Jun 2, 2009 at 8:14 AM, Jeppe Nejsum Madsen je...@ingolfs.dkwrote:
On 2 Jun 2009, David Pollak wrote:
Please post the exception
The code is just the
On 2 Jun 2009, David Pollak wrote:
This is an XML parsing error. Something in your XML is non-parsable.
It's not Lift, but the underlying XML parsing library.
Yes, it would seem so. It looks like a bug/non-implemented feature that
the parser is unable to read two attributes with the same
I think that this has been discussed on the list before. It's definitely an
issue with having the same attribute name with different prefixes. I don't
know that using proper namespace declarations will fix it. It seems that
this is a bug in the Scala XML parser.
Derek
On Tue, Jun 2, 2009 at 2:55
