Hello Thiago,
I migrated coming from 5.3.8 and I saw, that it is recommended now to
put all assets in the META-INF directory and js libs in a modules sub
dir under above.
But if one keeps the old structure for assets, according to the docs
only a warning should be raised, no exception, or an I
Hi Cezary,
thanks a lot, yes it works now again, I was just confused and overwelmed
by the Tapestry migration...
Regards, Erich
Am 19.03.2018 20:08, schrieb Cezary Biernacki:
Hi Erich,
I have a similar Tapestry 5.4 application with multiple modules in
different JARs. The application contribu
Hi Thiago,
yes, you're completely right, I missed for one oy my component libs and
now it works!
Thanks for your explanations!
Regards, Erich
Am 19.03.2018 20:13, schrieb Thiago H. de Paula Figueiredo:
On Mon, Mar 19, 2018 at 12:13 PM, Erich Gormann
wrote:
It seems using library mappings
On Mon, Mar 19, 2018 at 12:13 PM, Erich Gormann
wrote:
> It seems using library mappings is not the correct way to address pages.
I'm sorry, but your statement above is incorrect. Library mappings is still
the correct way to address pages.
--
Thiago
One typo: And nothing related to component libraries *changed*.
On Mon, Mar 19, 2018 at 4:10 PM, Thiago H. de Paula Figueiredo <
thiag...@gmail.com> wrote:
> On Mon, Mar 19, 2018 at 12:13 PM, Erich Gormann
> wrote:
>
>> Hello all,
>>
>
> Hi!
>
>
>>
>> another question about Tapestry 5.4.x:
>>
>>
On Mon, Mar 19, 2018 at 12:13 PM, Erich Gormann
wrote:
> Hello all,
>
Hi!
>
> another question about Tapestry 5.4.x:
>
> I'm a little confused about some new configuration possibilities in
> Tapestry 5.4.x. There is the new "module-path-prefix" entry.
>
This is about a prefix for the whole ap
Hi Erich,
I have a similar Tapestry 5.4 application with multiple modules in
different JARs. The application contributes LibraryMappings to
ComponentClassResolver, to tell Tapestry what are roots for module
packages, e.g.:
@Contribute(ComponentClassResolver.class)
public static void addMap
Hello!
>From which version did you upgrade? I may be wrong, of course, but I don't
remember any changes being made to JavaScriptSupportImpl since 5.4.0 or
5.4.1.
On Mon, Mar 19, 2018 at 2:50 PM, Erich Gormann wrote:
> Hello all,
>
> I hope my last question for today:
>
> After the migration to
Hello all,
I hope my last question for today:
After the migration to Tapestry 5.4.3 I got this stacktrace below on
calling any page of our application.
Does anyone else faced this problem, is it known?
Thanks for your help!
Best Regards, Erich
java.lang.NullPointerException
org.
Hello all,
another question about Tapestry 5.4.x:
I'm a little confused about some new configuration possibilities in
Tapestry 5.4.x. There is the new "module-path-prefix" entry.
My question: I have a number of different Tapestry application modules
bundled in jars and I want to navigate bet
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
15 matches
Mail list logo