Good call.  But, I'd vote for WARN.  In tapestry 4.0, it's never going to
find your page classes without a .application file to tell it what package
they're in right?  Not many applications can go without creating at least
one custom page class.  So, I'd say 99% of all "real" applications should
have a .application file.  It should be appropriate to spit out a warning if
it can't find the file.


-----Original Message-----
From: Brian K. Wallace [mailto:[EMAIL PROTECTED] 
Sent: Friday, May 12, 2006 9:25 AM
To: Tapestry users
Subject: Re: Strange situation with ognl

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

When Tapestry can't find the application specification, it currently
outputs a DEBUG message indicating as much ("Could not find an
application specification for application servlet <servlet-name>").
Given the ramifications (in a lot of situations) of not finding this,
should we bump this up to INFO? (I wouldn't suggest anything higher -
possibly WARN, but INFO should work)

Rui Pacheco wrote:
> Many thanks for the help!
> 
> On 5/12/06, James Carman <[EMAIL PROTECTED]> wrote:
>>
>> I told you it would be something simple.  Happy Tapestrying! :-)
>>
>>
>> -----Original Message-----
>> From: Rui Pacheco [mailto:[EMAIL PROTECTED]
>> Sent: Friday, May 12, 2006 9:09 AM
>> To: Tapestry users
>> Subject: Re: Strange situation with ognl
>>
>> The name of the .application file was wrong. I changed it, redeployed the
>> application and now everything works like a charm.
>>
>> On 5/12/06, James Carman <[EMAIL PROTECTED]> wrote:
>> >
>> > Is the page template called Abreviatura.html?  Sorry for the silly
>> > questions, but this is going to turn out to be something simple.  I'm
>> sure
>> > of it.  Is the .application file named the same thing as your
>> servlet in
>> > your web.xml file?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)

iD8DBQFEZIyXaCoPKRow/gARAqDsAKDXRlFAc1+J1XmSksxZ+7CvaRh1OwCg7P6x
zt/JMzBKJtOfNZCRrWjiXzI=
=ERqO
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
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]

Reply via email to