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 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
