Community
Participate
Working Groups
The Servlet 3.0 specification comes as part of the Java EE 6 specification. WTP should align its tooling to conform with new level of the specification.
This support should definitely be done in WTP, but we cannot commit enough dev resources for Galileo.
Let us know when the work is happening, we can test it with our server adapter and EE 6 runtime (GlassFish). For now, we have our own servlet 3.0 wizard that generates an annotated servlet ready to go (emitting some text on the web page)...Nothing to type to do simple demos. Same for other EE 6 web artifacts (listeners,...)
(In reply to comment #2) > For now, we have our own servlet 3.0 wizard ... Maybe I'm misreading this, but have you considered contributing it? Something that prohibits that? Your end? Ours? Just wondering.
not on my end...We could maybe attach a patch and you'll take it from there? What is the rule for a patch in a bug report? Need to be a committer?
Wow ... we should advertise more! :) Anyone can attach a patch to a bug. Committers will review and decide if they can accept it and commit it to the (cvs) code stream. We usually like them against the HEAD version of the project(s) affected. I should say, I'm not speaking on behalf of the server team ... maybe they have one already? Maybe they have some special system or framework they'd want you to fit into? But, I do know even if not accepted for whatever reason, it gets committers attention a lot better. :)
(In reply to comment #5) > I should say, I'm not speaking on behalf of the server team ... Oh, I should have said JEE team ... server, servlet ... I should read closer. Just wanted to clarify since that'd be confusing.
Hi Ludo, The JEE team will be really happy to evaluate any patches contributed by your team.
Good, we are investigating the details on our side. Stay tune and enjoy the coming holiday break.
Still investigating the legal aspect, and I hope I can give a patch soon. Anyway, I am preparing it on my side, will see when the lawyers are happy with that.
This bug somehow has been forgotten. We deferred it to Future at the time of the Galileo planning and forgot to include it in the Helios plan. Indeed, in Helios we implemented Servlet 3.0 support as part of other enhancements and bugs: - Web project can be created upon the Servlet 3.0 spec. - Web artifacts (servlets, filter, etc.) are generated with Servlet 3.0 annotations - Internals models in WTP are updated for the Servlet 3.0 spec. - Import/Exports mechanisms are updated for the Servlet 3.0 use case. - Web fragments are supported. Here is list of bugs that covers the above: bug 290033 - Default model providers for Java EE 6 facets bug 252615 - Java EE 6 models bug 252618 - Update Java EE artifact wizards for Java EE 6 bug 299747 - Project Explorer metadata content for Java EE 6 projects bug 272014 - Define facet and facet version for web fragments bug 258191 - Ensure EE6 archives can be imported/exported and are supported in binary mode bug 290040 - Java EE 6 Project creation for core module types bug 252613 - Define facet versions for the Java EE 6 projects
