Awesome thanks, I'll look at it during the next triage. (Which should be
soon now since the date i18n issues seem to be fixed. )
FYI - you don't even need a jetty configuration file to configure it with
maven. It's literally like 2-3 lines of configuration in the pom.xml file.
On 9/28/06, Christ
https://issues.apache.org/jira/browse/TAPESTRY-1100
I tried to post this the "mark reynold's way", with a maven2 sample
application attached, except that I don't use Jetty (I use Tomcat), so no
Jetty configuration.
Hope this helps
Ch.
2006/9/27, Jesse Kuhnert <[EMAIL PROTECTED]>:
HmmmCan y
HmmmCan you still post a bug in JIRA anyways? This sounds like a
possible bug in one the services. (be as detailed as possible about what you
did to have it happen, if that's possible..)
On 9/27/06, Christian Dutaret <[EMAIL PROTECTED]> wrote:
I was running my application with caching disab
I was running my application with caching disabled on my dev environment. If
I enable caching, then guess what... it works as expected (events are sent
only once when A changes). Amazing.
After a closer look, it seems that the updated event registration script is
sent with a different id (formEven
