Yes, so an example would be WEB-INF/app/About.html. I'm a little fuzzy
on the historical reason for this but it has certainly been a valid
choice since Tapestry 3 at least. I noticed
AbstractSpecificationResolver.java has two different methods,
getWebInfLocation() and getWebInfAppLocation(), the latter of which is
documented with "Returns the location of the application-specific
subdirectory, under /WEB-INF/, in the servlet context."

So presumably for us that application-specific subdirectory is app.
Perhaps that is because the <servlet-name> is defined as "app" for us in
web.xml but I'm not 100% sure where that is coming from.

Yes, our .application file is also in that directory.

-----Original Message-----
From: Jesse Kuhnert [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 03, 2007 11:41 AM
To: Tapestry users
Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30

Where/how does the "app" part come in? Is there literally a directory
called
"app" where you have stuff, and if so is your .application file there as
well?

On 5/3/07, Ben Dotte <[EMAIL PROTECTED]> wrote:
>
> The issue where component templates cannot be found in WEB-INF/app for
> specless apps. Yes, Marcus mentioned the same problem on TAPESTRY-1396
> yesterday. And yes, it is still a problem with the snapshot that just
> went out (tapestry-framework-4.1.2-20070503.160951-67.jar).
>
> To recreate, just put a component template with no spec under
> WEB-INF/app and Tapestry will be unable to find it on any of the
> post-4-30 snapshots.
>
> -----Original Message-----
> From: Jesse Kuhnert [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 03, 2007 11:13 AM
> To: Tapestry users
> Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
>
> Which issue is still a problem? Is it anything discussed in
> https://issues.apache.org/jira/browse/TAPESTRY-1396 ?
>
> Perhaps your failure is slightly different ? I may need more specific
> information (to re-create) . ...Either way an update just went out a
few
> seconds ago. Maybe that fixed it.
>
> On 5/3/07, Ben Dotte <[EMAIL PROTECTED]> wrote:
> >
> > It appears this is still a problem, even with the newest snapshot
> > (tapestry-framework-4.1.2-20070503.050340-66.jar)
> > <snipped>
> >
>
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Jesse Kuhnert
Tapestry/Dojo team member/developer

Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to