Tapestry gives you a bunch of options here and elsewhere. Perhaps
thats a failing, but it means you can adopt the practices that make
sense to you, in terms of naming and organization.
On Fri, Jul 8, 2011 at 7:51 AM, Thiago H. de Paula Figueiredo
wrote:
> On Fri, 08 Jul 2011 11:06:42 -0300, Nicol
On Fri, 08 Jul 2011 11:06:42 -0300, Nicolas Barrera
wrote:
Hi,
Hi!
As it's not mandatory to have a @Component variable in Index.java I
started to think that including comp1 just as a tag in the tml may
result in a more difficult way of finding which pages
depend/include comp1.
Good
Hi,
although the example worked out with the suggestions Thiago and Taha made...
I kept wondering around on this:
consider I include or use a certain component on my Index.tml
http://tapestry.apache.org/schema/tapestry_5_1_0.xsd";
> xmlns:p="tapestry:parameter">
>
> ${message:greeting}
>
>
Thanks both, you just hit the note...,
though I was pretty sure I had put it on the right place,... well... I
didn't.
Sorry for the buzz
Nicolás.-
On Thu, Jul 7, 2011 at 12:29 PM, Taha Hafeez wrote:
> Hi
>
> Where have you placed the component template, it should go in
> src/main/resources/te
Are you sure the component template is in the classpath in the same
package as the component class?
On Thu, 07 Jul 2011 11:54:35 -0300, Nicolas Barrera
wrote:
Hi,
I just wanted to run this test..., I got a tapestry archetype and added
this
code in the components package:
Comp1.java:
Hi
Where have you placed the component template, it should go in
src/main/resources/testComponent/components in case your application package
is testComponent.
regards
Taha
On Thu, Jul 7, 2011 at 8:24 PM, Nicolas Barrera wrote:
> Hi,
>
> I just wanted to run this test..., I got a tapestry arch
Hi,
I just wanted to run this test..., I got a tapestry archetype and added this
code in the components package:
Comp1.java:
package testComponent.components;
>
> public class Comp1 {
>
> }
>
>
Comp1.tml
http://tapestry.apache.org/schema/tapestry_5_1_0.xsd";
> xmlns:p="tapestry:parameter">
