I agree that it would be nice to be able to have an "index" page/class that
can be accessed by navigating to that directory/package in the URL, while
still having nested pages/classes accessible.
I hit this list about that a while back:
http://www.nabble.com/forum/ViewPost.jtp?post=12846148&frame
Could anyone give me any pointers or directions on how to stream the html
output that Tapestry generates out to a text file, which would be stored in
a specific directory outside the Tapestry project?
I would also like to be able to do the same with assets such as css and
javascript files, though
u
would never actually see the class/page name in the URL; only the
package/directory name. Maybe 'packageDefault' ?
Anyway, that's just one reason. The existence of 'pretty URLs' to some
degree invites more direct user manipulation of the URL. It would be nice to
be able to
But visiting
'www.mydomain.com/myapp/package1'
actually does work in that scenario, as long as there is a '/' at the end.
And visiting
'www.mydomain.com/myapp/package1/package1/'
doesn't work at all. This is actually what I was trying to accomplish,
except for the fact that the ab
ke myself.
Sorry for the clutter.
patrick whalen wrote:
>
> Strangely, this only works if there's another class in the same package,
> and you visit that page first. If you don't visit that page first, you get
> a 404 error. If you do, it works. After that, you can delete
you will then be able to visit -
www.mydomain.com/myapp/package1
without getting a 404 error.
patrick whalen wrote:
>
> I see now that it does work to put a class of the same name as the
> package, inside the package. The redundant name is then filtered out.
>
>
I see now that it does work to put a class of the same name as the package,
inside the package. The redundant name is then filtered out.
Chris Lewis-5 wrote:
>
> Check out:
>
> http://tapestry.apache.org/tapestry5/tapestry-core/guide/component-classes.html
>
> Specifically the section on "Sub
Right in front of my nose. I practically stole my example right out of the
chapter.
Any insight though into the main part of my question where I am trying to
create a page that has the same name as a package?
It doesn't seem as though the optimizations described in that chapter should
have an ef
