#2 Ability to deploy Context is missing

[Jochen Wiedmann]

I've got a project with a .tomcatplugin file (see below) and <nature>net.sf.eclipse.tomcat.tomcatnature</nature> in .project. Consequently, I'd expect something like "Tomcat/Refresh context.xml" in the projects context menu. (Because that is what was in the original Sysdeo plugin.) However, there's no "Tomcat" in the context menu.

<tomcatProjectProperties> <rootDir>/target/appComposerWebapp</rootDir> <exportSource>false</exportSource> <reloadable>true</reloadable> <redirectLogger>true</redirectLogger> <updateXml>true</updateXml> <warLocation></warLocation> <extraInfo></extraInfo> <webPath>/appcomposer</webPath> </tomcatProjectProperties>

[MarkusK]

At least I see that there is no Tomcat sub menu entry in a tomcat project's context menu.

But I am not sure how it can have gone missing, as I took the original sources from Sysdeo and just did some additions to in my opinion unrelated spots.

[Jochen Wiedmann]

Well, Markus: Can you reproduce, or not?

[MarkusK]

Sub menu entry was missing. So yes, I could reproduce the missing context menu. But as I said, I am not sure how it could have gone missing.

[Jochen Wiedmann]

Well. My obligation as a user is to provide a reproducible case. That being done, I'll leave the case up to you. For now, I am reverting to the Sysdeo Plugin.

[MarkusK]

I still have a few questions. What should that action do? I never needed that feature up to now. Did you notice it in a certain version of Sysdeo? How did you create the project?

So it might increase possibility of fixing if you'd help by answering those questions.

[Jochen Wiedmann]

The action creates a file Catalina/localhost/WebappName.xml.

This is required, if you don't wish to deploy a war file into Tomcat. (Saves quite some time in development.) This feature has been present in all versions of Sysdeo that I am aware of (version 2, or around that, until 3.3.1)

[Jochen Wiedmann]

I don't understand too much from Eclipse and its Plugins. But, I believe that the following entry in plugin.xml ought to provide what I am missing:

     <action
           label="%menu.nature.updateContext.label"
           class="net.sf.eclipse.tomcat.actions.UpdateTomcatContextActionDelegate"
           menubarPath="com.sysdeo.eclipse.tomcat.action.popup.javaProject.menu/group"
           id="com.sysdeo.eclipse.tomcat.updateContextToServerXml">
     </action>

Why that doesn't happen, escapes me, though. Is the "com.sysdeo.eclipse" prefix correct?

[Jochen Wiedmann]

Think, I've got it: The filter entry in plugin.xml seems to me to be wrong:

     <filter
           name="projectNature"
           value="com.sysdeo.eclipse.tomcat.tomcatnature">
     </filter>

According to the TomcatLauncherPlugin class, the nature ID is net.sf.eclipse.tomcat.tomcatnature. Could you, please, fix that?

Thanks,

Jochen

[Markus]

Thank you for your analysis, I will see if I can find some time in the next days to have a closer look into it. At a first glance I assume your analysis is correct.

[MarkusK]

Fixed, release pending.