On 13-09-15 19:34, françois facon wrote:
Good news!
I had to face the same problem with some tapestry5-jquery components
Your issue is related to TAP5-2463.
This should be fix in next version.
Anyway, if you don't have any legacy code that use prototype.js, it is
better to only use jQuery.
:
Good news!
I had to face the same problem with some tapestry5-jquery components
Your issue is related to TAP5-2463.
This should be fix in next version.
Anyway, if you don't have any legacy code that use prototype.js, it is
better to only use jQuery.
Best regards
François
2015-09-13 17:46 GMT+0
On 13-09-15 11:12, françois facon wrote:
Hi Christine,
Did you try to force the use of jQuery whithout prototype in your beta35
version ?
This could be done by adding the following code configuration.add(
SymbolConstants.JAVASCRIPT_INFRASTRUCTURE_PROVIDER, "jquery");
in the contributeApplicat
On 13-09-15 11:12, françois facon wrote:
Hi Christine,
Did you try to force the use of jQuery whithout prototype in your beta35
version ?
I will try.
After I created a .war file from the app and uploaded it to the server,
running jetty8, the app worked, but the ajax call doesn't. I think it
You can go with the HTML code, but then, in order to render it, you'd have
to use something like this:
On Fri, Sep 11, 2015 at 11:57 AM, Andreas Fink
wrote:
> Tapestry handles properties files as UTF-8 (
> https://tapestry.apache.org/localization.html ).
> As long as you make sure that your id
Hi Christine,
Did you try to force the use of jQuery whithout prototype in your beta35
version ?
This could be done by adding the following code configuration.add(
SymbolConstants.JAVASCRIPT_INFRASTRUCTURE_PROVIDER, "jquery");
in the contributeApplicationDefaults part of your AppModule.
Best
