Our templates are still getting resolved on WEB-INF/app just fine, but I just found out we have a problem with NLS .properties files getting resolved that is the same as the template resolution problem.
So it looks like Tapestry is now looking on the classpath first for .properties files whereas it used to look on the context first (specifically for us this would also be WEB-INF/app). Would it be possible to change this back to look at the context first like it used to? Sorry to bother with this yet again! Thanks, Ben -----Original Message----- From: Ben Dotte [mailto:[EMAIL PROTECTED] Sent: Thursday, May 03, 2007 3:01 PM To: Tapestry users Subject: RE: 4.1.2 snapshot changes 4-20 to 4-30 Ok, I hate to bring this up yet again but things still aren't working the way they need to. Tapestry used to search the context for the templates first, then it searched the classpath. Now it searches the classpath first. Our templates technically get output to both places, but the ones we need Tapestry to use are in WEB-INF/app. So I changed our build process to no longer output templates to the classpath so it would be forced to go to the context. Now pages render just fine from the context but we get a huge pile of stack traces to the console as documented on this case: http://issues.apache.org/jira/browse/TAPESTRY-1437 If Tapestry just looked at the context first like it used to, everything would work fine for us. Alternately, these stack traces really need to be suppressed. I am talking 15,000 lines of stack traces just to get to our home page. Ouch. Thanks, Ben -----Original Message----- From: Jesse Kuhnert [mailto:[EMAIL PROTECTED] Sent: Thursday, May 03, 2007 1:37 PM To: Tapestry users Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30 Sheww....Finally :) Yeah I don't think the classpath search is going to be the most typical type either so it doesn't make sense to take the perf hit on resolving them for that. I'm not nearly done with these changes though ......Need to re-factor things so that only one service/object has knowledge of all the various places to search / how / etc.. On 5/3/07, Ben Dotte <[EMAIL PROTECTED]> wrote: > > Cool, it seems to be finding the component templates again like it used > to. The only difference is it used to search on the context first, then > the classpath.. but I'm not going to split hairs, works plenty good for > me. > > Thanks Jesse! > > -----Original Message----- > From: Jesse Kuhnert [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 03, 2007 12:23 PM > To: Tapestry users > Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30 > > Ok that's making more sense now. I've made some changes and can no > longer > find any combination that breaks it. What a pita .....It should now find > them in > > -) classpath relative to component class > -) relative to context root > -) relative to context + WEB-INF root > -) relative to context + WEB-INF + app name root > > Jar should be deployed by the time you read this email. > > On 5/3/07, Ben Dotte <[EMAIL PROTECTED]> wrote: > > > > 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] > > > > > > > -- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
