On 1/17/07, Michael Horwitz <[EMAIL PROTECTED]> wrote:
Matt,
I have successfully used Dojo with SpringMVC while still keeping the .html
extension by using a filter to redirect any non-dojo requests to the Spring
servlet. This approach has two nice side effects: 1) the servlet container
can use its default handling for all static content and 2) one can reduce
the number of filters that get applied to such content.
If people are interested I would be more than happy to share the solution.
I'd definitely be interested in this and having folks test it with
Struts 2. It might be best to post it here, as well as in JIRA
(http://issues.appfuse.org/browse/APF-431).
Matt
Mike.
On 1/17/07, Matt Raible <[EMAIL PROTECTED]> wrote:
> I've created a poll so everyone can vote on their favorite extension.
>
> http://appfuse.org/pages/viewpage.action?pageId=495
>
> You'll need to create an account and login to vote. To do this, go to
> View > Account > Sign Up (or login if you already have an account).
>
> Thanks!
>
> Matt
>
> On 1/16/07, Sanjiv Jivan <[EMAIL PROTECTED]> wrote:
> > I like .html but the problem I've faced with using this extension is
that
> > serving static html file with the .html file extension (like
documentation,
> > Dojo templates or FckEditor files) becomes very hard to map to not go to
the
> > applications MVC controller. I've spent countless number of hours
messing
> > with the url-pattern in web.xml without much success.
> >
> > So I usually use .htm for the application extension.
> >
> > Sanjiv
> >
> >
> > On 9/20/06, Matt Raible < [EMAIL PROTECTED]> wrote:
> > >
> > > Dear AppFuse users,
> > >
> > > As many of you likely know, there are a couple of issues with using
> > > the *.html extension with some frameworks in AppFuse. For example,
> > > with WebWork - it loads Dojo template files from a *.html extension.
> > > If you want to use Dojo with WebWork, you have to modify your default
> > > extension.
> > >
> > > http://issues.appfuse.org/browse/APF-431
> > >
> > > Because of this, we're starting to look at other extensions. I'd
> > > rather use one for all frameworks, rather than the recommended ones
> > > for each framework b/c it allows us to have one security.xml files,
> > > rather than one for each framework. Another option is to use
> > > path-based mapping, for example:
> > >
> > > http://localhost:8080/yourapp/go/users
> > >
> > > Where "/go/*" is the path that front-controller servlet/filters are
> > > mapped to. The only problem with this is stat trackers typically like
> > > to track extensions, and so we'd be unfriendly to those companies who
> > > like to watch their stats.
> > >
> > > Here's a couple thoughts - feel free to add your own suggestions and
> > thoughts:
> > >
> > > 1. *.htm
> > > 2. *.aspx
> > > 3. *.php
> > > 4. *.app
> > > 5. *.a
> > > 6. *.o
> > > 7. *.apf (would help us track AppFuse-based applications, but it's a
> > > pretty ugly extension)
> > > 8. *.em
> > > 9. *.fun
> > > 10. *.page
> > >
> > > I still like *.html the best b/c it doesn't give away the underlying
> > > technology, so *.htm seems like the best option after that. But of
> > > course, I'm open to suggestions. ;-)
> > >
> > > Matt
> > >
> > >
> >
---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> > [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> >
>
>
> --
> http://raibledesigns.com
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
[EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
http://raibledesigns.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
