Community
Participate
Working Groups
This will create new content types that cover the EE7 namespace... It will follow the same scheme the previous versions used. Going through the Fast (QuickPeek) parse operation for reading XML headers....
Created attachment 229979 [details] Proposed master patch Here there are some changes to support EE7 contentypes. Some questions: 1. What's the Web Fragment version in EE7? 2.Is this OK? public final static QualifiedName JEEVERSION = new QualifiedName("jee-version", "5.0"); is 5.0. The version 5.0 is still in JEE6ContentDescriber 3. Should the ResourceFactories classes be modified or create new ones for EE7?
1) Web Fragment version for Java EE 7 is 3.1 (same as Web) 2) That looks like a bug on the JEE6ContentDescriber. Make it 7.0 3) Modifying the Javaee ones should be sufficient
Created attachment 230022 [details] New Patch
PMC Review requested due to UI change We are adding several string in to org.eclipse.jst.jee/plugin.properties Explain why you believe this is a stop-ship defect. Or, if it is a "hotbug" (requested by an adopter) please document it as such. This is needed to help finalize our support of Java EE 7. Is there a work-around? If so, why do you believe the work-around is insufficient? There is no work-around. This is all new support for Java EE 7. This adds in the same Content Types and ContentDescriber for Java EE 7 that were added in for Java EE 6. How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added? The Java EE Tools JUnit bucket has been run against this fix. Furthermore, it has been tested as part of the work for bug 400484 Give a brief technical overview. Who has reviewed this fix? This adds in the same Content Types and ContentDescriber for Java EE 7 that were added in for Java EE 6. Carl Anderson has reviewed this fix. What is the risk associated with this fix? Relatively low
Committed http://git.eclipse.org/c/jeetools/webtools.javaee.git/commit/?id=5e2b4349a92be2a625eb72237c69cef44e027b49 And released using tag v201305012100 to WTP 3.5 Note that I did not commit the change to MANIFEST.MF, because the version of the plugin had been already updated for WTP 3.5