Community
Participate
Working Groups
If you create Dynamic web project 3.0 with runtime Glassfish3 the filters and listeners are no longer shown in the Deployment Descriptor node. Without runtime or with Tomcat 7 it works. I am using WTP 3.2.4
To ask explicitly, are they shown if you run the same test when using WTP 3.2.3? I would assume so, but thought it would be good to ask, to know for sure, if a regression?
Do you mean the Filter and listener nodes are not shown? or the filters and listeners you create are not shown under the filter and listener nodes? Does you project have deployment descriptor? Are you filters and listeners annotated? or did you add them to the deployment descriptor? I tested with JBoss and I do see the nodes and the annotated artifacts under the nodes. I still have to test with filters and listeners in the deployment descriptor
I tested adding filters and listeners in deployment descriptor, and they are shown under the appropriate nodes.
I tried this too, and the nodes show up for me, as well. I think this bug report needs a lot more detail to be useful. Some exact reproducible steps.
As mentioned in the tittle this occurs using glass fish runtime only. One good example on how to reproduce this is to make a dynamic web 3.o project with no server runtime. Next create servlet, filter and listener All of them are correctly displayed in deployment descriptor tree. Now from project properties select the project to use glass fish 3 runtime Immediately the filter and listener and the filter mapping disappear from the DD tree only. The resources are there.
I think I see what you mean, now. I misunderstood at first what you meant, and thought you meant the "Filter" node itself ... but, you mean filter (classes) underneath the Filter node. I could recreate using the "new" menu, to create a new filter ... which, creates it using annotations, nothing in web.xml file. In that case, it was displayed using Tomcat, but not glassfish. I see the same incorrect display behavior using Helios SR2 (WTP 3.2.3). Can you confirm? If so, this bug has existed a long time? And no one ever noticed? Or am I (still) seeing something wrong?
Dimitar, it has been 3 months since your last update. I am assigning this to you for the initial investigation- if you find where, within the WTP code, things are going wrong, we can work with you to get them corrected.
I will check it out.
Moving to next maintenance release available.... too late for 3.2.5
I turns out that this is a bug in GlassFish server adapter, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=383293 for more information.
