I think in T 5.4 @Submodule has been deprecated in favor of @ImportModule
On Wed, Jul 9, 2014 at 6:05 PM, Thiago H de Paula Figueiredo <
thiag...@gmail.com> wrote:
> On Wed, 09 Jul 2014 17:38:04 -0300, Ilya Obshadko
> wrote:
>
> - component that was moved into separate module can't be loaded b
On Wed, 09 Jul 2014 17:38:04 -0300, Ilya Obshadko
wrote:
- component that was moved into separate module can't be loaded by main
application using standard namespace; is there any way to fix that? (that
is, results in UknownValueException);
That's expected: When you changed the component f
Hi Ilya,
[caveat, I am using T 5.3.7]
Is each of your modules a fully functioning web app, or just partial?
You can specify the namespace of components in the project's module class
I am doing something similar to this with my project, Graphene
https://github.com/Sotera/graphene
The graphene-we
I would like to modularize my application into several modules, so that
each one of them would be a separate Maven artifact. I'm trying to
reproduce what I can borrow from tapestry-upload module source, but still
have questions:
- component that was moved into separate module can't be loaded by ma
Hello,
I would like to know if it is possible in an to replace
the Addrowlink by a t:Select that adds different values depending on what
is chosen in the list ?
