OK, I deleted this library "tapestry-service-cache-3-0.jar" from the
deployment folder and now the exception is not thrown anymore.
I will look what it oes and find a replacement...
Am 19.03.2018 14:56, schrieb Dmitry Gusev:
Hi,
It can still be loaded if you have Tapestry 5.3 jars on class
Then I'd recommend to attach to it with a debugger and look around to check
which class is causing this exception.
I.e. put a breakpoint in constructors of NoClassDefFoundError.
On Mon, Mar 19, 2018 at 5:04 PM, Erich Gormann wrote:
> Hi Dmitry,
>
> I'm sure that there aro no old libs on classpa
Hi Dmitry,
I'm sure that there aro no old libs on classpath...
Regards, Erich
Am 19.03.2018 14:56, schrieb Dmitry Gusev:
Hi,
It can still be loaded if you have Tapestry 5.3 jars on classpath, make
sure to remove them.
On Mon, Mar 19, 2018 at 4:41 PM, Erich Gormann wrote:
Dear all,
afte
Hi,
It can still be loaded if you have Tapestry 5.3 jars on classpath, make
sure to remove them.
On Mon, Mar 19, 2018 at 4:41 PM, Erich Gormann wrote:
> Dear all,
>
> after migrating our application from tapestry 5.3.8 to Tapestry 5.4.3 I'm
> fighting with the exception shown in the stacktrace
Dear all,
after migrating our application from tapestry 5.3.8 to Tapestry 5.4.3
I'm fighting with the exception shown in the stacktrace below.
I'm aware that the ClassFactory is not present in Tapestry 5.4 anymore,
but we do not use it explicetely. I wonder why our application should
try to
