Password strength ...

[Juan M Garrido de Paz]

Hello... does Tapestry have any kind of component or something to show
password strength besides a password field in a form as you type? A
progress bar with colours.

I've been looking for it but didn't find much about it... doing it with
bootstrap maybe.

How do you do it? Bootstrap or are there another good possibilities?

Thank you.

Re: hide special pages ...

[Juan M Garrido de Paz]

It doesn't work for me though in some cases, for example when Spring
Security sends a 403 response in its default behaviour, and the 403 page is
a "hidden" one.

I will have to see in detail.

Thank you.


2016-08-30 13:21 GMT+02:00 Juan M Garrido de Paz <
juanm.garrido@gmail.com>:

> Oh yes, sorry, I didn't realize onActivate had no args.
>
> Same approach that index page, but with no args, in every page I wanna
> "hide".
>
> It's ok... thank you very much!
>
>
> 2016-08-30 13:09 GMT+02:00 Chris Poulsen [via Apache Tapestry Mailing List
> Archives] :
>
>> The code pasted is from one of our property block pages. The activate
>> ensures that the page cannot be accessed as a "normal page"
>>
>> --
>> Chris
>>
>> On Tue, Aug 30, 2016 at 10:56 AM, Juan M Garrido de Paz <
>> [hidden email] <http:///user/SendEmail.jtp?type=node&node=5732930&i=0>>
>> wrote:
>>
>> > Hi, yes , I do return that in my activate already. It is for telling
>> > tapestry not to consider the text following the index page name as
>> context
>> > param, and instead of that throw 404 error. It works ok.
>> >
>> > But what I am asking is about error page location. How to put it under
>> > web-inf folder? I think it is a best practice to hide it. I mean not
>> just
>> > error pages... also propertyblocks pages should be hidden from users to
>> > type their url shouldnt they?
>> >
>> > But as my project is jar packaging with embedded tomcat, I dont have
>> webapp
>> > source folder with web-inf .
>> >
>> > Thank you.
>> > El 30/8/2016 8:53, "Chris Poulsen" <[hidden email]
>> <http:///user/SendEmail.jtp?type=node&node=5732930&i=1>> escribió:
>> >
>> > > Just return something from you activate, e.g:
>> > >
>> > > Object onActivate()
>> > > {
>> > > return new HttpError( 404, "Resource not found");
>> > > }
>> > >
>> > >
>> > > On Tue, Aug 30, 2016 at 1:25 AM, Juan M Garrido de Paz <
>> > > [hidden email]
>> <http:///user/SendEmail.jtp?type=node&node=5732930&i=2>> wrote:
>> > >
>> > > > Hello, I'm using Tapestry with Spring Boot and embedded tomcat (jar
>> > > > packaging).
>> > > >
>> > > > Is it posible to hide certain pages like for example errors 403,
>> 404,
>> > > 500;
>> > > > or the pages for propertyblocks... so that the user can't type
>> their
>> > url
>> > > > and get them?
>> > > >
>> > > > Thank you.
>> > > >
>> > >
>> >
>>
>>
>> --
>> If you reply to this email, your message will be added to the discussion
>> below:
>> http://apache-tapestry-mailing-list-archives.1045711.n5.
>> nabble.com/hide-special-pages-tp5732923p5732930.html
>> To unsubscribe from Apache Tapestry Mailing List Archives, click here
>> <http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2375124&code=anVhbm0uZ2Fycmlkby5wYXpAZ21haWwuY29tfDIzNzUxMjR8LTU2NTA3OTQwOQ==>
>> .
>> NAML
>> <http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>
>
>

Re: hide special pages ...

[Juan M Garrido de Paz]

Oh yes, sorry, I didn't realize onActivate had no args.

Same approach that index page, but with no args, in every page I wanna
"hide".

It's ok... thank you very much!


2016-08-30 13:09 GMT+02:00 Chris Poulsen [via Apache Tapestry Mailing List
Archives] :

> The code pasted is from one of our property block pages. The activate
> ensures that the page cannot be accessed as a "normal page"
>
> --
> Chris
>
> On Tue, Aug 30, 2016 at 10:56 AM, Juan M Garrido de Paz <
> [hidden email] <http:///user/SendEmail.jtp?type=node&node=5732930&i=0>>
> wrote:
>
> > Hi, yes , I do return that in my activate already. It is for telling
> > tapestry not to consider the text following the index page name as
> context
> > param, and instead of that throw 404 error. It works ok.
> >
> > But what I am asking is about error page location. How to put it under
> > web-inf folder? I think it is a best practice to hide it. I mean not
> just
> > error pages... also propertyblocks pages should be hidden from users to
> > type their url shouldnt they?
> >
> > But as my project is jar packaging with embedded tomcat, I dont have
> webapp
> > source folder with web-inf .
> >
> > Thank you.
> > El 30/8/2016 8:53, "Chris Poulsen" <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=5732930&i=1>> escribió:
> >
> > > Just return something from you activate, e.g:
> > >
> > > Object onActivate()
> > > {
> > > return new HttpError( 404, "Resource not found");
> > > }
> > >
> > >
> > > On Tue, Aug 30, 2016 at 1:25 AM, Juan M Garrido de Paz <
> > > [hidden email] <http:///user/SendEmail.jtp?type=node&node=5732930&i=2>>
> wrote:
> > >
> > > > Hello, I'm using Tapestry with Spring Boot and embedded tomcat (jar
> > > > packaging).
> > > >
> > > > Is it posible to hide certain pages like for example errors 403,
> 404,
> > > 500;
> > > > or the pages for propertyblocks... so that the user can't type their
> > url
> > > > and get them?
> > > >
> > > > Thank you.
> > > >
> > >
> >
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-tapestry-mailing-list-archives.1045711.
> n5.nabble.com/hide-special-pages-tp5732923p5732930.html
> To unsubscribe from Apache Tapestry Mailing List Archives, click here
> <http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2375124&code=anVhbm0uZ2Fycmlkby5wYXpAZ21haWwuY29tfDIzNzUxMjR8LTU2NTA3OTQwOQ==>
> .
> NAML
> <http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>

Re: hide special pages ...

[Juan M Garrido de Paz]

Hi, yes , I do return that in my activate already. It is for telling
tapestry not to consider the text following the index page name as context
param, and instead of that throw 404 error. It works ok.

But what I am asking is about error page location. How to put it under
web-inf folder? I think it is a best practice to hide it. I mean not just
error pages... also propertyblocks pages should be hidden from users to
type their url shouldnt they?

But as my project is jar packaging with embedded tomcat, I dont have webapp
source folder with web-inf .

Thank you.
El 30/8/2016 8:53, "Chris Poulsen"  escribió:

> Just return something from you activate, e.g:
>
> Object onActivate()
> {
> return new HttpError( 404, "Resource not found");
> }
>
>
> On Tue, Aug 30, 2016 at 1:25 AM, Juan M Garrido de Paz <
> juanm.garrido@gmail.com> wrote:
>
> > Hello, I'm using Tapestry with Spring Boot and embedded tomcat (jar
> > packaging).
> >
> > Is it posible to hide certain pages like for example errors 403, 404,
> 500;
> > or the pages for propertyblocks... so that the user can't type their url
> > and get them?
> >
> > Thank you.
> >
>

hide special pages ...

[Juan M Garrido de Paz]

Hello, I'm using Tapestry with Spring Boot and embedded tomcat (jar
packaging).

Is it posible to hide certain pages like for example errors 403, 404, 500;
or the pages for propertyblocks... so that the user can't type their url
and get them?

Thank you.

Re: Project Folder Structure ...

[Juan M Garrido de Paz]

Hola Thiago...

maybe I will take a look some day to component libraries, sure it's the way
to go to have the whole app well organized by feature.

But by now, I think I will use the util package by feature, with the
downside of having pages, components,... separated. The problem, as always,
is time, and I think component libraries is too complicated to do it
quickly. My project is medium size.

Just one more question...

Do you think that it's ok to have (in the root package) a base package as I
have, containing "abstract page" to inherit from it the common services and
other stuff? and maybe another abstract classes for another types of
objects.

Thank you very much for your answers, and for the tip about the component
libraries (I think it's the right way to go, when I have time :D )

Bye.



2016-08-19 0:43 GMT+02:00 Thiago H de Paula Figueiredo :

> On Thu, 18 Aug 2016 18:59:43 -0300, Juan M Garrido de Paz <
> juanm.garrido@gmail.com> wrote:
>
> Thank you Thiago.
>>
>
> De nada! :D
>
> I knew there were the posibility to have several root packages, but never
>> looked into it to learn about it, and I didn't imagine it could be useful
>> for this purpose. You mean that each feature would have a root package
>> (feature = root package = "component library")? In this case each feature
>> have their own pages, components, etc (they dont have to be centralized)?
>>
>
> Yes, that's a way you can leverage library components to have a more
> flexible package structure, which seems to be the your goal here.
>
> I've just realized that another way could be to organize my "util" package
>> directly by feature instead of encoders, grid, etc. What do you think about
>> this? It would be simplier than using "component-libraries"?
>>
>
> I think it would work. It would be simpler than component libraries, with
> the downside of a feature's pages, components and mixins not being as close
> to their other classes of the same feature (such as ValueEncoders,
> Tapestry-IoC services, etc).
>
> How do you organize your projects?
>>
>
> It depends a lot on their size. Small ones can have everything in the same
> place. Larger ones would definitely be separated in component libraries,
> which would make the application way more modular. Setting up a component
> library is a one-time cost which can be done relatively quickly.
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>

Re: Project Folder Structure ...

[Juan M Garrido de Paz]

Thank you Thiago.

I knew there were the posibility to have several root packages, but never
looked into it to learn about it, and I didn't imagine it could be useful
for this purpose. You mean that each feature would have a root package
(feature = root package = "component library")? In this case each feature
have their own pages, components, etc (they dont have to be centralized)?

I've just realized that another way could be to organize my "util" package
directly by feature instead of encoders, grid, etc. What do you think about
this? It would be simplier than using "component-libraries"?

How do you organize your projects?

Thank you.


2016-08-18 23:40 GMT+02:00 Thiago H de Paula Figueiredo 
:

> On Thu, 18 Aug 2016 17:43:07 -0300, Juan M Garrido de Paz <
> juanm.garrido@gmail.com> wrote:
>
> Hello...
>>
>
> Hi!
>
> how do you organize the packages/folders in your projects? (I mean other
>> than pages, components, mixins, services).
>>
>> Due to tapestry force us to have separate pakages for pages, components,
>> etc... I guess we cannot (or shouldn't) organize the whole root package
>> by "features" of business layer. For example, for "employee" feature, I
>> cannot
>> put a EmployeeGridDataSource in the page package with the pages of that
>> feature, because it is not a page.
>>
>
> That's correct. Tapestry applies bytecode transformation to pages,
> components, mixins and classes in the 'base' packages, so it needs to know
> exactly in what packages these classes are.
>
> One thing you haven't thought is that you don't need to have a single root
> package, so you can organize your sources, packages and classes by feature.
> You just need to treat each one as a separate component library, even if
> they're in the same project/source tree. https://tapestry.apache.org/co
> mponent-libraries.html tells you how.
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>

Project Folder Structure ...

[Juan M Garrido de Paz]

Hello...

how do you organize the packages/folders in your projects? (I mean other
than pages, components, mixins, services).

Due to tapestry force us to have separate pakages for pages, components,
etc... I guess we cannot (or shouldn't) organize the whole root package by
"features" of business layer. For example, for "employee" feature, I cannot
put a EmployeeGridDataSource in the page package with the pages of that
feature, because it is not a page.

In the project I'm developing now I have:

pages --> organized by "features" of the business layer
components
...
util
 encoders ---> date encoder, search criteria encoder, etc
 grid ---> for grid data sources and related classes (for example
pagination)
 select --> for custom implementations of certain select models
 viewobjects --> for example classes for store form fields, and classes
that convert them to dto objects for the business layer
 ...
 WebUtils.java --> static methods for general utilities concerned with
web layer
base
 AbstractBasePage.java --> pages inherit from it (attributes/services
like log, messages, etc)


Do you think this approach is ok?
Do you have any best practices or rules to organize better the project?

Inside each util subfolder, do you organize the classes by "feature"? Now I
don't, for example I have all the encoders mixed in the ecoder folder.

Thank you.

Re: Tapestry vs Spring MVC + REST + Angular

[Juan M Garrido de Paz]

Thanks Thiago.

I was just wondering wether doing the integration at the front end, using
tapestry for offering rest services, would be easier than the approach i
took.

Never did it before, nor i have experience with js client frameworks,
that's why i asked . What you have to do is identiftying the requests in
the html web app, and call the appropiate  ws of the tapestry app,  that
will return json?
On Tue, 02 Aug 2016 14:41:24 -0300, Juan M Garrido de Paz
<[hidden email] <http:///user/SendEmail.jtp?type=node&node=5732810&i=0>>
wrote:

> How is the approach of use tapestry just to offer web services to the
> frontend? In this case tapestry just serves json objects? Then you dont
> need tapestry components and other features for anything , do you? I dont
> see the point of using tapestry in this case.

Live class reloading makes your development way faster.

> And using tapestry pages instead of web services? Pages here are for
> nothing but to hold the event listener method that do the job by calling
> the model service, arent they?

In this case, yes.

> I dont see why to use tapestry as the web framework in this cases, as you
> just use it as a middleware to call model services. You dont use pages,
> components, zones, etc.

You lose using the Tapestry pipelines (specially RequestFilter) for access

control, profiling, logging, etc.

> Anyway what do you think is better, using tapestry generating the
> required front end code? Or using tapestry just to offer the services to

> the front
> end ? (either by web services or by page listeners).
>
> Which approach do you prefer?

I believe the answer is very dependent on the actual scenario you have to
implement, so I won't give any broad answers.

I'm just saying that REST services can be done. I'm not saying it's the
best solution.

-- 
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br

-
To unsubscribe, e-mail: [hidden email]
<http:///user/SendEmail.jtp?type=node&node=5732810&i=1>
For additional commands, e-mail: [hidden email]
<http:///user/SendEmail.jtp?type=node&node=5732810&i=2>



--
If you reply to this email, your message will be added to the discussion
below:
http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/Tapestry-vs-Spring-MVC-REST-Angular-tp5732799p5732810.html
To unsubscribe from Apache Tapestry Mailing List Archives, click here
<http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2375124&code=anVhbm0uZ2Fycmlkby5wYXpAZ21haWwuY29tfDIzNzUxMjR8LTU2NTA3OTQwOQ==>
.
NAML
<http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>

Re: Tapestry vs Spring MVC + REST + Angular

[Juan M Garrido de Paz]

Hello I'm facing a new project from scratch where i have the desired look
and feel of the clint pages, done with html 5,  js, bootstrap and jquery.
They work as a simple page webapp.

Which is the best option... integration at the front end or at the backend?

I began doing a web app as i always did,  using tapestry as the web
framework, and spring as the model framework, which offers  the model
services that i inject in tapestry pages. But i'm realizing that creating
the html code from tapestry templates and making it work is not easy.

How is the approach of use tapestry just to offer web services to the
frontend? In this case tapestry just serves json objects? Then you dont
need tapestry components and other features for anything , do you? I dont
see the point of using tapestry in this case.

And using tapestry pages instead of web services? Pages here are for
nothing but to hold the event listener method that do the job by calling
the model service, arent they?

I dont see why to use tapestry as the web framework in this cases, as you
just use it as a middleware to call model services. You dont use pages,
components, zones, etc.

Anyway what do you think is better, using tapestry generating the required
front end code? Or using tapestry just to offer the services to the front
end ? (either by web services or by page listeners).

Which approach do you prefer?
El 2/8/2016 18:39, "Thiago H de Paula Figueiredo" 
escribió:

> On Tue, 02 Aug 2016 12:23:39 -0300, Qbyte Consulting
> <[hidden email] >
> wrote:
>
> > It would be cool if Tapestry components could be bound directly to
> > RESTful resources in the client side instead of directly to page classes
>
> > for their data input and output.
>
> Why not just using pages as REST endpoints? I don't see why using
> components for that would be better.
>
> > I have had problems migrating apps from T5.3.6 to T5.4 so not entirely
> > happy.
>
> Which ones?
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
> -
> To unsubscribe, e-mail: [hidden email]
> 
> For additional commands, e-mail: [hidden email]
> 
>
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/Tapestry-vs-Spring-MVC-REST-Angular-tp5732799p5732808.html
> To unsubscribe from Apache Tapestry Mailing List Archives, click here
> 
> .
> NAML
> 
>