Hello, Tim!
Thank you very much for your list of corrections! It's going to be very
useful when creating quickstart-jakarta.
Cheers!
On Tue, Mar 4, 2025 at 7:47 PM D Tim Cummings
wrote:
> Hi Andreas
>
> I don't use tapestry runner myself, but I notice there is a
> t
tryFilter is not a javax.servlet.Filter
>
That's because Quickstart hasn't had a JakartaEE version created yet and
the current one uses javax.servlet. That's something we overlooked when
writing the JakartaEE support.
--
Thiago H. de Paula Figueiredo
Software developer/engineer
A
Hi Andreas
I don't use tapestry runner myself, but I notice there is a
tapestry-runner-jakarta which might be what you are supposed to use.
I use `mvn jetty:run` to run my apps. You could try that. I posted an
email on 10-Oct-2024 which detailed some fixes to get quickstart working
i
tapestry-core-jakarta
${tapestry-version}
compile
jakarta.xml.bind
jaxb-api
jakarta.xml.ws
jaxws-api
Hello, Tapestry community!
Tapestry 5.9.0 was just released. All the details are available at
https://tapestry.apache.org/release-notes-590.html.
Tapestry 5.9.0 is a release with both new features and bugfixes, including
upgrades of old dependencies with security vulnerabilities, being a drop-in
2024 12:57 PM
To: Tapestry users
Subject: Re: Thread locking (deadlock) issue using Tapestry 5.8.7 under heavy
load
[You don't often get email from thiag...@gmail.com. Learn why this is important
at https://aka.ms/LearnAboutSenderIdentification ]
On Fri, Nov 15, 2024 at 12:38 PM
On Fri, Nov 15, 2024 at 12:38 PM Scott McCarthy <
scott.mccar...@clarivate.com> wrote:
> Hi All,
>
Hello!
> We are running a fairly large Tapestry application with hundreds of
> concurrent users.
> When under load, we are occasionally seeing an instance go into deadlock,
Thanks for the tips. We'll use that to see if we can learn anymore.
I guess the main thing I want to try and figure out is if this is a Tapestry
problem, or a problem in something we're doing with Tapestry.
The latter seems more likely but we'll try to find out.
The good news
Hi Scott,
Thanks for bringing this issue to our attention.
I've looked through the JIRA and found
https://issues.apache.org/jira/browse/TAP5-2621 with a similar thread dump
attached.
We're running multiple Tapestry instances with a varying degree of
concurrent users and have yet to e
to explain what we're seeing...
We are running a fairly large Tapestry application with hundreds of concurrent
users.
When under load, we are occasionally seeing an instance go into deadlock,
whereby the Tomcat threads max out, but the CPU is virtually zero.
This can commonly occur when a ne
Looks good to me (and tapestry-security). Ready when you are.
Kalle
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 24.836 s
[INFO] Finished at: 2024-10-31T22:53:51+02:00
[INFO
On Fri, Oct 18, 2024 at 11:20 AM Chelamalasetty Sunil Joshi
wrote:
> Hello, Tapestry Team
>
Hello!
> Still, We see tapestry-spring-5.9.0-preview-2.jar using the
> javax.serlvet.ServletContext Due to that we are facing below error. Kindly
> check this issue
>
If you&
Hello, Tapestry Team
Still, We see tapestry-spring-5.9.0-preview-2.jar using the
javax.serlvet.ServletContext Due to that we are facing below error. Kindly
check this issue
2024-10-18 19:48:15,851 [main] ERROR
org.apache.catalina.core.ContainerBase.[Tomcat].[localhost].[/admin] -
Exception
he mailing list! You haven't changed a bit! Your quality as a
troll is still quite low, I'm afraid. IMHO, good trolls are subtle and make
their targets think. Your message doesn't hit any of that. Howard, creator
of Tapestry and someone I have very deep respect as a software develop
Emmanuel, You clearly have no idea what you are talking about. I've thoroughly
enjoyed working with Tapestry over the past several years on a major Financial
Services SaaS application used by 10s of thousands of people. Tapestry is an
outstanding framework.
I will happily sponsor Thia
My advice? Stop wasting your valuable time on this dead but walking project
that only 5 people worldwide are using. Given alternatives like Angular
(yes, there is a server side option too, not just SPA), React, Vue, Ember,
etc., who in their right mind uses Tapestry in this day and age? Get a life
change the artifactIds in pom.xml
tapestry-core => tapestry-core-jakarta
tapestry-webresources => tapestry-webresources-jakarta
Now the app would run http://localhost:8080
*ISSUE 2*: Lots of classes scanned from multiple locations.
For example
[WARNING] com.google.common.annotations.Beta s
Hello, Tapestry community!
TL;DR: I've joined GitHub Sponsors: https://github.com/sponsors/machina-br
(Machina TI Ltda is my one-person company) to try to be able to work on
Tapestry not just on my free time.
*Summary*
By sponsoring me, Thiago, you're allowing me to take time away f
Hi Chris!
Tapestry's AssetDispatcher/ResourcerStreamer does ETag for assets:
https://github.com/apache/tapestry-5/blob/b01afbedb325897084ab5f2277e99a0e6fe2a02f/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/ResourceStreamerImpl.java#L156-L171
You could implement the
Hello all,
I’m exploring the possibility of adding ETag headers to images my
Tapestry application is serving, to help improve performance on slower
networks.
It seems that Apache Server automatically adds ETag headers to images
sourced from static files (Tapestry @Asset), but not when
Hello, Tapestry community!
Apache Tapestry 5.9.0-preview-2 was released. Notice the '-preview' in the
version name. It's the second one using 2 parallel branches to support both
jakarta.servlet and javax.servlet, so consider this as a public beta so
people can test it and we c
Hello, Tapestry community!
Apache Tapestry 5.9.0-preview was released. Notice the '-preview' in the
version name. It's the first one using 2 parallel branches to support both
jakarta.servlet and javax.servlet, so consider this as a public beta so
people can test it and we can trou
ry minimal changes to the
> Tapestry 5 gradle build. One benefit of this approach is that we were
> able to use the same version number for both javax and jakarta artifacts
> since they effectively have separate namespaces.
>
I've just done something which I believe is similar
Hello, Tapestry community!
Tapestry 5.8.7 has just been released. It's mostly a bugfix release for
regressions caused by the multiple classloader support/better page cache
invalidation feature, but also includes an upgrade of the library used to
minimize JavaScript code.
More details at
Hello All,
We had the same idea about adding a classifier or altering the maven
coordinates. What we found is that adding "-jakarata" to the artifact
names worked extremely well and required very minimal changes to the
Tapestry 5 gradle build. One benefit of this approach is th
e idea. I've even started working on it on a branch:
https://github.com/apache/tapestry-5/commit/f253bc35fa0b201721b13bee5898b69ca17e6edc
I love the Tapestry community. So many smart and clever people. That's one
of the main reasons I've started the thread in the first place. The other
.
Regards,
Dmitry
On Wednesday, July 31, 2024, Thiago H. de Paula Figueiredo <
thiag...@gmail.com> wrote:
> Hello, Tapestry community!
>
> As already discussed, the Jakarta EE an javax.servlet versions of the
> Servlet API have some differences that go beyond the package rename,
trivial amount of work. And I really don't want to leave anyone behind
within reason.
> Thanks for all your work derkoe. I am looking forward to seeing the
> results.
>
I second that motion!
Cheers!
>
> Cheers
>
> Tim
>
> On 1/8/24 08:06, Thiago H. de Paula
don't like change they probably don't need the new features. Security
patches for javax branch would still be required though.
Thanks for all your work derkoe. I am looking forward to seeing the results.
Cheers
Tim
On 1/8/24 08:06, Thiago H. de Paula Figueiredo wrote:
Hello, Tapestry
On Thu, Aug 1, 2024 at 7:35 AM Bob Harner wrote:
> I agree with Kalle and others, call it 6. Permanently locking the version
> at 5 was always a bad idea, in my opinion.
>
I believe the locking ended up being forced on the project by Tapestry 5
not getting a different name when it
never posted it here, so I'll refer to the nickname he's been using
in the mailing list). :)
>
> Best Regards
>
> Carlos Montero
>
> El jue, 1 ago 2024 a las 10:37, Kalle Korhonen (<
> kalle.o.korho...@gmail.com>)
> escribió:
>
> > I would just
Hello, Kall, Carlos and Bob!
I appreciate and respect your suggestions, but I'm afraid going to Tapestry
6 is not happening. We already had a bunch of classes moved from one
package to another or even to new packages and we just went to 5.6 to 5.7.
The framework name is Tapestry 5. It'
I agree with Kalle and others, call it 6. Permanently locking the version
at 5 was always a bad idea, in my opinion.
On Thu, Aug 1, 2024, 6:04 AM Andreas Ernst wrote:
> Am 01.08.24 um 10:36 schrieb Kalle Korhonen:
> > I would just call it Tapestry 6.x. It's not going to be compati
Am 01.08.24 um 10:36 schrieb Kalle Korhonen:
I would just call it Tapestry 6.x. It's not going to be compatible with any
previous version, or even with previous servlet containers. I well know the
history ("there will never be Tapesty 6") but past is past, there's no good
r
Best Regards
Carlos Montero
El jue, 1 ago 2024 a las 10:37, Kalle Korhonen ()
escribió:
> I would just call it Tapestry 6.x. It's not going to be compatible with any
> previous version, or even with previous servlet containers. I well know the
> history ("there will never be Tape
I would just call it Tapestry 6.x. It's not going to be compatible with any
previous version, or even with previous servlet containers. I well know the
history ("there will never be Tapesty 6") but past is past, there's no good
reason to avoid a new major, semantic ver
Hello, Tapestry community!
As already discussed, the Jakarta EE an javax.servlet versions of the
Servlet API have some differences that go beyond the package rename, but,
at the same time, the Tapestry team won't leave the javax.servlet users
behind. We'll have 2 different branches,
e released back to the pool. This was the only little
glitch encountered in getting Tapestry working hand-in-hand with the
WebSocket API, and I'm glad to have it sorted.
I appreciate your pointers which certainly saved me much time.
/**
* Method to manually instruct registry to
ience with Tapestry and WebSockets, so it's
more like an educated guess.
If you look at the Registry, it has a cleanupThread() method, which locks
the Registry and calls cleanup() on the delegates to PerThreadManager.
https://github.com/apache/tapestry-5/blob/5655dd7fcb0441971147670254dd54800b
ation I've been able to narrow down exactly which
calls to HibernateCrudServiceDAO produce these leaked connections. When
this DAO service is invoked using dependency injection - as it is in
most cases - connections do not get leaked. So, for the most part the
tapestry-hibernate module
t took us quite some time and experimentation to get it "just right" for
our use case without any surprises for edge cases, and I dread the day we
have to take another look at it...
Cheers
Ben
On Wed, Jun 5, 2024 at 5:48 AM Christopher Dodunski (Tapestry) <
chrisfromtapes...@christo
Hi,
My application's DAO class is employing an injected Hibernate Session
for accessing a MySQL DB. Connection pooling is provided by C3PO.
My understanding is that the Tapestry Hibernate IoC (per thread) service
takes care of closing DB connections under the hood, releasing them bac
Hello, community!
Another month, another bugfix release which should fix exceptions when
running in production mode. Release notes at
https://tapestry.apache.org/release-notes-586.html.
Happy coding!
--
Thiago H. de Paula Figueiredo
Hello, everyone!
2 different Tapestry users warned me of 2 different issues. Thank you very much!
While one of them should be rare and I couldn't reproduce myself, the
other affecting webapps in production mode, breaking pages or
components using and . That's my fault
and I apologiz
Great work. Thank you all!
Geoff
> On 2 Apr 2024, at 6:07 AM, Thiago H. de Paula Figueiredo
> wrote:
>
> Hello, Tapestry community!
>
> Apache Tapestry 5.8.5 has just been. It's got 2 bugfixes and it's a
> drop-in replacement and recommended upgrade for
Hello, Tapestry community!
Apache Tapestry 5.8.5 has just been. It's got 2 bugfixes and it's a
drop-in replacement and recommended upgrade for Tapestry 5.7.0+ plus
projects.
Release notes at https://tapestry.apache.org/release-notes-581.html .
Happy coding!
Cheers!
--
Thiago H
t; wrote:
>
> > First, thanks for the 5.8.4 release! The timing was perfect since
> > underscore.js was one of the items flagged in a recent vulnerability
> scan.
>
> Nice!
>
> > Given there is no schedule for official Tapestry Jakarta EE support, we
> > decided to create
On Tue, Feb 13, 2024 at 6:57 PM David Taylor
wrote:
> First, thanks for the 5.8.4 release! The timing was perfect since
> underscore.js was one of the items flagged in a recent vulnerability scan.
Nice!
> Given there is no schedule for official Tapestry Jakarta EE support, we
>
November 2023.
Given there is no schedule for official Tapestry Jakarta EE support, we
decided to create and host an internal build of Tapestry. I applied the
changes provided by Christian Köberl in pull request TAP5-2741 to the
5.8.4 sources and everything is looking good so far. Thank you so
On Tue, Feb 13, 2024 at 8:20 AM Carlos Montero Canabal
wrote:
> Good job Tapestry Team, congratulations!
Thanks!
> I have a question. This release supports Java 21 but checking Tomcat
> versions (https://tomcat.apache.org/whichversion.html), If I want to use
> Java 21 I have to use
Good job Tapestry Team, congratulations!
I have a question. This release supports Java 21 but checking Tomcat
versions (https://tomcat.apache.org/whichversion.html), If I want to use
Java 21 I have to use Tomcat 11.0.X and this version requires servlet spec
6.1. From the 6.0 version, servlet is
Happy to see a new release!
On Wed, Feb 7, 2024 at 3:02 AM Thiago H. de Paula Figueiredo <
thiag...@gmail.com> wrote:
> Hello, Tapestry community!
>
> Tapestry 5.8.4 has just been released, including some enhancements and
> bug fixes. It's a
> a drop-in replacement a
Hello, Tapestry community!
Tapestry 5.8.4 has just been released, including some enhancements and
bug fixes. It's a
a drop-in replacement and recommended upgrade for Tapestry 5.7.0+ projects.
The highlights are the support for Java 21 bytecode, an improvement
and a fix in multiple classl
latter… YES!
~150 web sites with t5 and java8
Thomas
Le 03/10/2023 à 19:34, Thiago H. de Paula Figueiredo a écrit :
Hello, everyone!
While planning the next Tapestry steps, one piece of information that
would be useful is whether there's still Tapestry webapps out there
running on Java
Hello,
Same here working with jdk8. Tapestry 5 and Tapestry 4 applications… Still
migrating some tapestry 4 to tapestry 5.
Best regards,
<http://www.dfacto.ch/> Numa Schmederwww.dfacto.ch
<http://www.dfacto.ch/>
n...@dfacto.ch <mailto:n...@dfacto.ch> |
Thank you all for your feedback! It's very important to us. We have no
plans of dropping support for Java 8 in Tapestry.
On Tue, Oct 3, 2023 at 2:34 PM Thiago H. de Paula Figueiredo
wrote:
>
> Hello, everyone!
>
> While planning the next Tapestry steps, one piece of informatio
Sent: Tuesday, October 3, 2023 5:45 PM
To: users@tapestry.apache.org
Subject: Re: Anyone still using Java 8 in Tapestry webapps
CAUTION: This email originated from outside of BAYADA. Beware of links and
attachments.
Hi Thiago,
Yes, I have two apps in production using Java 8.
Best,
Charles
On
Hi Thiago,
Yes, I have two apps in production using Java 8.
Best,
Charles
On 10/3/23 12:34 PM, Thiago H. de Paula Figueiredo wrote:
Hello, everyone!
While planning the next Tapestry steps, one piece of information that
would be useful is whether there's still Tapestry webapps out
YES!
We are still using JDK 1.8! And it will remain so in the future. This is
due to JDK license agreements after 1.8.
Alex
On 3.10.23 г. 20:34 ч., Thiago H. de Paula Figueiredo wrote:
Hello, everyone!
While planning the next Tapestry steps, one piece of information that
would be useful is
Yes. We really want to move up and have done all the work to go from Tapestry
5.4.3 to a later version so that we can upgrade our JDK from 8 to 11 or later,
but got stuck when we found that HighCharts didn’t work properly in PhantomJS
when all our other dependencies were upgraded accordingly
Hello, everyone!
While planning the next Tapestry steps, one piece of information that
would be useful is whether there's still Tapestry webapps out there
running on Java 8. No need to tell what the webapps are, just raise
your virtual hand if the answer is yes.
Thanks in advance.
C
Hello, Tapestry community!
Tapestry 5.8.3, after a long year, has finally been released, and it
has a long list of release notes! :)
It should very soon be accessible at
https://tapestry.apache.org/release-notes-582.html, but here's a text
version of its highlights (which don't i
me was the "default" modifier on the method, as the method
> declarations in the interface don't have a "default" implementations.
> Let's recreate the scenario:
>
> interface Original {
> Number test();
> }
> interface Extended extends Original {
>
interface Extended extends Original {
Double test();
}
Time for some bytecode:
Classfile /Users/ben/code/tapestry/tapestry-5/Extended.class
Last modified 24 Jun 2023; size 254 bytes
SHA-256 checksum
708c3793a9074f5afdd523542cf287559d5cbeee871a0ca9757444dc28edafe3
Compiled from "E
On 21.6.23 20:32, Volker Lamp wrote:
Is there any chance I can motivate you to contribute your test case as
a unit test to the Tapestry code base? Have a look at the test apps in
tapestry-jpa as a starting point.
If I find some free time in the following months to look it up and learn
how
Hi Vangel
> For me, it is very easy to reproduce. I can share the entire source
> code, but there is nothing special to share.
Thank you for the code example!
Is there any chance I can motivate you to contribute your test case as a unit
test to the Tapestry code base? Have a look at th
Hi Vangel
> Is this because the bug only occurs in some very specific environments
> (only some specific OS and some specific JDK combination and some
> specific DB driver), or tapestry-hibernate is not in use any more by
> committers and other developers and tapestry-jpa is the p
On 15.6.23 14:17, Thiago H. de Paula Figueiredo wrote:
Yeah, it doesn't seem to happen for everyone. tapestry-hibernate has
unit and integration tests and they have been successful.
For me, it is very easy to reproduce. I can share the entire source
code, but there is nothing special to
ack Overflow in the last month and now this thread here opened by Chris.
Well, I work with a fairly large project which uses tapestry-hibernate
and Hibernate a lot, in both web and non-web (typically, Quartz jobs,
but not only that) and I haven't run into this problem yet.
> Is this beca
>
> How come nobody else has noticed the bug for two years?
>
In general we're isolating the use of Tapestry to our presentation layer -
The datastore access (and business logic) lives in modules and the UI sits
on top of the business logic layer - The lower level modules are us
only occurs in some very specific environments
(only some specific OS and some specific JDK combination and some
specific DB driver), or tapestry-hibernate is not in use any more by
committers and other developers and tapestry-jpa is the preferred way,
or both are obsolete nowadays and one should
n 11, 2023 at 3:19 AM Christopher Dodunski (Tapestry) <
chrisfromtapes...@christopher.net.nz> wrote:
> Hi Ben,
>
> Thank you for your investigative efforts, even though you weren't yet
> able to pinpoint the exact cause. And thank you, you and Vangel, for
> sharin
Hi Ben,
Thank you for your investigative efforts, even though you weren't yet
able to pinpoint the exact cause. And thank you, you and Vangel, for
sharing that workaround.
Occasionally, this HibernateCrudServiceDAO method works as expected.
Most times not. This seeming randomness fits wit
I've tried to debug the issue again, but to no avail :-/
Here are my observations/findings/notes:
The Session you get injected is actually a shadowed property of
org.apache.tapestry5.hibernate.HibernateSessionManager that is created in
org.apache.tapestry5.hibernate.modules.HibernateCoreModule.bu
On 9.6.23 14:30, Ben Weidig wrote:
we ran into similar issues with custom queries, our workaround is calling
getSession() on the session, like this:
return this.session.getSession().createQuery(sql) //
.setParameter("replyToId", relatedId) //
in the Hibernate session,
and
org.apache.tapestry5.hibernate.modules.HibernateCoreModule.buildSession(HibernateSessionManager,
PropertyShadowBuilder) doesn't work as initially intended anymore.
Cheers
Ben
On Fri, Jun 9, 2023 at 1:43 PM Christopher Dodunski (Tapestry) <
chrisfromtapes.
Hello,
I've encountered an issue after upgrading from Tapestry 5.6.4 to 5.7.3.
This included moving from Hibernate 5.1.0.Final to 5.4.32.Final (as per
the guidelines).
The HibernateCrudServiceDAO method below is now failing to fetch named
queries via the injected org.hibernate.Se
Hello,
Today, with the help of the handy migration tool, I upgraded from
Tapestry 5.6.4 to 5.7.3. Below are some packages which it missed.
Just letting you know in case you might like to add these to the tool's
properties file for future users.
org.apache.tapestry5.beaneditor.Bean
Regular Expression Denial of Service (ReDoS) in ContentType.java.
(GHSL-2022-022) (CVE-2022-31781)
PRODUCT AFFECTED:
This issue affects Apache Tapestry 5.8.1.
PROBLEM:
Severity: low
Apache Tapestry up to version 5.8.1 is vulnerable to Regular
Expression Denial of Service (ReDoS) in the way it
Hello, community!
Tapestry 5.8.2 has just been released. A drop-in replacement and
recommended upgrade for projects using 5.7.0+.
Besides the usual small fixes and enhancements, 5.8.2 introduces CORS
(Cross-Origin Resource Sharing) support. The goal was to cover as many
scenarios as possible by
Dear Tapestry users,
I am writing to you all at Thiago de Paula's recommendation. I am part of
EDRUOM Group (www.edurom.ro<http://www.edurom.ro>), a leading Romanian company
with 20 years of experience in human resources.
For one of our clients, a global digital engineering f
encoder is not
allowed here". Not sure whether this is related to the problem in any
way.
As I understand it, I shouldn't be needing to explicitly provide an
encoder. The objects being sent to Grid's source and row parameters are
Hibernate entities, and the tapestry-
quot;. Not sure
whether this is related to the original problem in any way.
As I understand it, I shouldn't be needing to explicitly provide an
encoder anyway. The objects being sent to Grid's source and row
parameters are Hibernate entities, and the tapestry-hibernate modul
Hi all,
I've identified the source of the problem. It was a small omission in
the HQL which resulted in an Object[] of fields rather than an entire
entity being handed onto the Grid component, hence "[Ljava.lang.Object;"
in the exception message below.
"Could not find a coercion from ty
ski (Tapestry)
> wrote:
>
> Thank you for those suggestions, Volker.
>
> The common theme seems to be that I should allow Tapestry to create a default
> BeanModel rather than create a new instance of one in my Java class, correct?
> Your second suggestion is nearest to wha
You are totally right, Chris, I got you wrong. Sorry for that.
The problem may be constructor related. I remember having a similar problem a
couple of years back. In my case, if I remember correctly, it was a missing
default constructor.
Sorry this is vague. I don't have my repo available as I'
Thank you for those suggestions, Volker.
The common theme seems to be that I should allow Tapestry to create a
default BeanModel rather than create a new instance of one in my Java
class, correct? Your second suggestion is nearest to what I've done,
except that I return a new Bean
Hi Andreas,
tapestry-security (http://www.tynamo.org/tapestry-security+guide/) is a Third
Party project, not an Apache Tapestry module.
The source code is available on GitHub
(https://github.com/tynamo/tapestry-security). Perhaps you can speed things up
by cloning the project, making the
Hi Christopher,
Here are three suggestions to achieve what you are trying to do.
(1) Omit the 'model' parameter to let Tapestry create a default model. Use the
'add' parameter to add a column named 'crewman' to that model. In the template
file, in the body of the
Hi all,
I'm trying out the Tapestry Grid component for the first time in one of
my projects. During rendering I'm presented with the below exception.
"Render queue error in BeginRender[vessel/Read:grid.rows]: Failure
writing parameter 'row' of component vesse
Hi,
are the any Plans to Update Tapestry Security for the new Tapestry Version.
With the latest i got serveral errors, like:
Unable to instantiate class
org.apache.tapestry5.http.modules.TapestryHttpModule as a module:
Exception constructing service 'ServiceOverride': Error invoki
Hi Volker,
Yes thanks, this should Work. I know about the Session Cookie.
But my Problem was a CSRF filter in our Tapestry app, which I Not
recognized directly :-)
All is fine now, thanks again.
Volker Lamp schrieb am Mi., 27. Apr. 2022, 16:40:
> Hello Eric
>
> Not sure about the
Hello Eric
Not sure about the setup of your application server, but likely the session id
is stored in a cookie. So when your users return to your Tapestry app (in
whatever way, e.g. using the browser's back-button; clicking a hyperlink; or
typing the URL into the browser's add
Hi all,
I'm struggling with the following Situation:
>From my Tapestry application with active http session I call a page in
another non Tapestry application in the same browser tab.
But after that I want to navigate back from that application to the
original Tapestry page.
I guess i
Hi Charles,
I gave it a quick look and debugged
org.apache.tapestry5.ioc.internal.services.cron.CronExpression.getTimeAfter(Date)
with your expression and can confirm that there's an issue with handling
"L-".
At first, it got the right day, but then it gets reset to today.
The code is quite com
Hi,
There seems to be an issue with CronExpression using "L" (last day of
month).
When I place the following code in my AppModule, the job is triggered at
the appointed time, and then keeps executing over and over immediately
in a seemingly infinite loop. I can work around by using a
day-of
I am not sure what needs to be done to get Tapestry 5.8.1 Quickstart
into https://repo.maven.apache.org/maven2/archetype-catalog.xml on Maven
Central but it is not there yet. Maybe it is just a case of waiting.
If it is a manual addition then, please add it, and at the same time
remove some
WOW, after all these years, with so many new developments in so many
areas, is Emmanuel Sowah still fixated on Tapestry?
Actually, I'm glad I checked in - you always put a smile on my face.
Every now and then, you need some naked guy running across the
football field to inject some fun.
WOW, after all these years with so many new developments on the Java and
web front, is Tapestry still on version 5 branch? Is this really a serious
project or still a garage one? Thiago and the sect members, please GROW!
On Mon, Apr 4, 2022 at 1:54 PM Thiago H. de Paula Figueiredo <
th
Thank you for the release!
I don't know if this is already known, but I just noticed that the heading
links in the "Latest news" on the front page does not work for the two
5.8.x releases.
The (broken) 5.8.1 link in the list is:
https://tapestry.apache.org/2022/04/04/tapestry-5
1 - 100 of 14900 matches
Mail list logo
