Re: Apache Tapestry for Java 11
Hi Paul, it's in latest 5.5.0-beta-3 On Sat, Oct 26, 2019 at 12:55 AM Paul Stanton wrote: > "We can push a new 5.5 beta for early testers." > > ^-- is this available? if not, any eta? > > On 11/09/2019 4:43 am, Thiago H. de Paula Figueiredo wrote: > > On Tue, Sep 10, 2019 at 4:31 AM Chris Poulsen > > wrote: > > > >> I did roll an "internal" 5.5-beta version based on the code from 12th > July > >> as there are some fixes in HEAD that are not in the beta-2 and that > bastard > >> build is what we currently are using without problems. > >> > > We can push a new 5.5 beta for early testers. > > > > > >> If 5.5 isn't 100% ready for release yet, it seems to be really close > and it > >> would be good to get it finalized IMO. > >> > > Yes, we're close. I'd just want to finish the support for running without > > Bootstrap (or with Bootstrap 4) before releasing 5.5. I don't see any > other > > blockers or nice-to-haves. Other people may have their own, of course. :) > > > > And yes, 5.5 supports Java 11 bytecode, and that's exactly the issue that > > most probably took the team the longer to develop. > > > > > >> -- > >> Chris > >> > >> On Mon, Sep 9, 2019 at 9:11 PM Charles Roth wrote: > >> > >>> Sounds good to me. We'd be very happy to test a 5.5-beta. (Large > >>> application that has about 1M LOC, including unit-tests, TML, etc.) > >>> > >>> On 9/9/2019 3:08 PM, Dmitry Gusev wrote: > Hi Charles, > > Current state of the master branch should run just fine on Java 11; > >>> there's > no release you can download though. > > We should probably start a vote on another Tapestry 5.5-beta soon to > release current state of the master branch, > and maybe make a first 5.5.0 release right after we get some feedback > >>> from > community. > > > On Mon, Sep 9, 2019 at 9:54 PM Charles Roth > >> wrote: > > Is there any new(ish) word on Tapestry 5.5 or any other release that > > will run under Java 9, 10, and maybe 11? > > > > Thanks! > > > > On 10/8/2018 12:54 PM, Bob Harner wrote: > >> Yes. The unreleased 5.5 version passses all tests with the Java 9+ > >> compatible version of ASM (which was the obstacle for running > >> Tapestry > > 5.4 > >> under Java 9+) and should be usable for Java 9 and 10 now (once > > released), > >> although it hasn't been tested enough by others. I haven't checked > it > > with > >> Java 11 yet. The Tapestry nightly snapshot process is broken > >> currently, > > and > >> that's the principal obstacle to the 5.5 release. > >> > >> > >> https://issues.apache.org/jira/plugins/servlet/mobile#issue/TAP5-2588 > >> My weekends have been occupied by other projects the last few weeks > >>> but I > >> hope to get back on it next weekend. > >> > >> On Mon, Oct 8, 2018, 9:49 AM gard sæbø > >> wrote: > >> > >>> Hi! > >>> > >>> We are upgrading all our Java applications, which currently runs on > >>> Java > >>> 8, to Java 11. > >>> > >>> Our web applications use Apache Tapestry as the frontend framework, > >>> but > > it > >>> seems a bit quite on the Tapestry commit log in comparison with > >> other > >>> frontend frameworks. > >>> > >>> Will there be any upgrade which will support Java 11 and future > Java > >>> versions? > >>> > >>> Best regards, > >>> Gard Sæbø > >>> > >> - > >>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > >>> For additional commands, e-mail: users-h...@tapestry.apache.org > >>> > >>> > > - > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > > >>> - > >>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > >>> For additional commands, e-mail: users-h...@tapestry.apache.org > >>> > >>> > > > > > - > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Dmitry Gusev AnjLab Team http://anjlab.com
Re: Apache Tapestry for Java 11
"We can push a new 5.5 beta for early testers." ^-- is this available? if not, any eta? On 11/09/2019 4:43 am, Thiago H. de Paula Figueiredo wrote: On Tue, Sep 10, 2019 at 4:31 AM Chris Poulsen wrote: I did roll an "internal" 5.5-beta version based on the code from 12th July as there are some fixes in HEAD that are not in the beta-2 and that bastard build is what we currently are using without problems. We can push a new 5.5 beta for early testers. If 5.5 isn't 100% ready for release yet, it seems to be really close and it would be good to get it finalized IMO. Yes, we're close. I'd just want to finish the support for running without Bootstrap (or with Bootstrap 4) before releasing 5.5. I don't see any other blockers or nice-to-haves. Other people may have their own, of course. :) And yes, 5.5 supports Java 11 bytecode, and that's exactly the issue that most probably took the team the longer to develop. -- Chris On Mon, Sep 9, 2019 at 9:11 PM Charles Roth wrote: Sounds good to me. We'd be very happy to test a 5.5-beta. (Large application that has about 1M LOC, including unit-tests, TML, etc.) On 9/9/2019 3:08 PM, Dmitry Gusev wrote: Hi Charles, Current state of the master branch should run just fine on Java 11; there's no release you can download though. We should probably start a vote on another Tapestry 5.5-beta soon to release current state of the master branch, and maybe make a first 5.5.0 release right after we get some feedback from community. On Mon, Sep 9, 2019 at 9:54 PM Charles Roth wrote: Is there any new(ish) word on Tapestry 5.5 or any other release that will run under Java 9, 10, and maybe 11? Thanks! On 10/8/2018 12:54 PM, Bob Harner wrote: Yes. The unreleased 5.5 version passses all tests with the Java 9+ compatible version of ASM (which was the obstacle for running Tapestry 5.4 under Java 9+) and should be usable for Java 9 and 10 now (once released), although it hasn't been tested enough by others. I haven't checked it with Java 11 yet. The Tapestry nightly snapshot process is broken currently, and that's the principal obstacle to the 5.5 release. https://issues.apache.org/jira/plugins/servlet/mobile#issue/TAP5-2588 My weekends have been occupied by other projects the last few weeks but I hope to get back on it next weekend. On Mon, Oct 8, 2018, 9:49 AM gard sæbø Hi! We are upgrading all our Java applications, which currently runs on Java 8, to Java 11. Our web applications use Apache Tapestry as the frontend framework, but it seems a bit quite on the Tapestry commit log in comparison with other frontend frameworks. Will there be any upgrade which will support Java 11 and future Java versions? Best regards, Gard Sæbø - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Recompiling of .less file triggered in prod unexpectedly
Thank you Cezary. This is invaluable. As a first step I’ve added some logging
of the caching to see whether this is the culprit.
Geoff
> On 25 Oct 2019, at 7:38 am, Cezary Biernacki wrote:
>
> Assuming that my suggestion is correct, the simplest solution would be to
> give more heap space to JVM if there is enough RAM on machines you are
> deploying.
>
> Otherwise, I would attempt to create a StreamableResourceSource decorator
> that would cache only selected resources that are heavy to compute (e.g.
> less files in your case), but otherwise not very memory consuming in a
> ConcurrentMap using normal references (i.e. not SoftReference). As there is
> already a stack of decorators for SRS (see
> org.apache.tapestry5.modules.AssetsModule) you should be careful how to
> order that new decorator. Try @Order("before:GZIpCompression",
> "after:CacheCompressed").
>
> But in longer term, some way to precompile files for the production would
> be more sustainable. I would a consider a solution that adds
> another StreamableResourceSource decorator (or a ResourceTransformerFactory
> decorator) which works in two modes, In the first mode it saves streamable
> resources to a specified directory on the file system, in the second mode
> it retrieves cached data from a JAR (using Java's Resource). During the
> build process a script would start the application in the first mode,
> trigger compilation of key assets, and finally pack it to a JAR. In the
> production the second mode could be be used.
>
> Best regards,
> Cezary
>
>
>
> On Thu, Oct 24, 2019 at 11:18 PM JumpStart <
> geoff.callender.jumpst...@gmail.com> wrote:
>
>> That’s great information. So is the solution to precompile them for
>> production, or to override SRSCachingInterceptor, or something else
>> altogether?
>>
>>> On 24 Oct 2019, at 11:09 pm, Cezary Biernacki
>> wrote:
>>>
>>> Tapestry caches compiled files in memory using SoftReference<> so it is
>>> possible for the garbage collector to remove them (see
>>> org.apache.tapestry5.internal.services.assets.SRSCachingInterceptor). In
>>> the development mode Tapestry also caches compilations in a temporary
>>> directory, but unfortunately this mechanism is disabled in the production
>>> mode
>>> (see
>> org.apache.tapestry5.internal.webresources.ResourceTransformerFactoryImpl#createCompiler).
>>>
>>> Cezary
>>>
>>>
>>> On Thu, Oct 24, 2019 at 2:57 AM JumpStart <
>>> geoff.callender.jumpst...@gmail.com> wrote:
>>>
I’m observing that after startup, and then after every 20 minutes or so
>> -
actually, it seems to be quite variable - the first page after login
>> will
take 20 or more seconds to be displayed. The rest of the time it is
>> almost
instantaneous.
I’ve run a sampler over it during one of these 20+ sec periods and it
seems to be spending all its time in the Less compiler. The page is
>> using
@Import:
@Import(stylesheet = { "css/client.less" })
public class Home extends LoggedIn {
I’m using tapestry-webresources-5.4.3.jar.
I was expecting this to be a one-time event, on first visit to the page
after startup. Under what circumstances would you expect it to happen
>> more
than once?
Regards,
Geoff
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>> For additional commands, e-mail: users-h...@tapestry.apache.org
>>
>>
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
