A solution is to use the find in files functionality of the IDE. Other
ideas just comes in to mind: the applicatoin server probably can show
the servlet mappings, or you can write a little application that read
all the classes, and examines if the classes have annotations.
ps: handle this email with care, the author don't speak english perfectly.
On 2014-03-01 03:12, Hayden Jones wrote:
Thanks for the idea clay but even if we deployed with an embedded web
server it would still leave a question as to where to find the servlet
mappings.
On Thursday, February 13, 2014 3:18:55 PM UTC-5, clay wrote:
Have you considered an embedded server rather than the traditional
multi-tenant approach with .war/.ear archives and web.xml descriptors?
On Monday, February 3, 2014 10:42:58 AM UTC-6, Hayden Jones wrote:
I am writing a java ee 6 application and am trying to decide to
mark my filters with the @WebFilter annotation or configure it
in the web.xml
Currently, I am leaning towards using the web.xml as the IDE I
am using does not list servlet filters if they are only annotated.
Are there IDEs that support a capability to see the WebFilters
all together? (NetBeans 7.4 does not seem to do this) and what
do people thing the best practice should be?
Thanks.
--
You received this message because you are subscribed to the Google
Groups "Java Posse" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/javaposse.
For more options, visit https://groups.google.com/groups/opt_out.
--
Üdvözlettel,
Böszörményi Péter
--
You received this message because you are subscribed to the Google Groups "Java
Posse" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/javaposse.
For more options, visit https://groups.google.com/groups/opt_out.
