If memory serves thats not an external API; what's your use case for this?Cheers, Tim
--
You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to lif...@googlegroups.com.
To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
I'm using Lift with other frameworks which already use the same suffixes as Lift wants.
On Thu, Feb 10, 2011 at 11:44 AM, Timothy Perrett <tim...@getintheloop.eu> wrote:
If memory serves thats not an external API; what's your use case for this?Cheers, Tim--
You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to lif...@googlegroups.com.
To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
--
You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to lif...@googlegroups.com.
To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
In one case *.xhtml and *.html are occupied by JSF. Currently I'm making it work by mapping /lift/* to the Lift-filter, and replicating the directory-structure there. Ideally I'd like to mix my lift-files with other view-files, which are grouped by functional domain. I'd really appreciate not having to replicate a directory-structure under /lift/* as well. I think Lift will face the challenge of co-existing side-by-side of other frameworks more and more in the future, and in order to achieve greater adoption it should be possible with as little effort as possible.So; I would like to have Lift recognise *.lift (or any other arbitrary suffix) and mix lift-files with the JSF-view files (*.[x]html). Is it, or will it be possible?