+1 and….
I’d even like to take this request a little further. How much I like to see e.g. webservices added to myeclipse, I’d rather see the use of xdoclet taken to a higher level. Let me describe it in more detail.
I’m a fan of eclipse and myeclipse and try to promote it in our company, I showed 2.7.2 to one of my collegues today and he was initially impressed by the xdoclet support… this impression disappeared after…
– A web module was created and xdoclet was not automagically configured for this using the right directories / parameters.
– The servlet wizzard was used which directly added configuration elements to web.xml but did not create the xdoclet tags, so they had to be added manually
– This webmodule was made struts aware and nice classes were generated with xdoclet tags, the struts-config was ‘generated’ but no doclets were added to the xdoclet config and they were not configured. Also the web.xml was populated with the tld’s etc but not via xdoclet!
To get a project configured in the right way to use xdoclet is not easy, in fact it is cumbersome.
I moved (luckily not removed) my web.xml and struts-config.xml and started to try to get my web project configured so that xdoclet would generate the config files in the right place with the right content so they would match the ‘original’ ones. It took me a great while to even come close, and I am a ‘experienced’ myeclipse/xdoclet user.
So therefore two proposals:
– Projects/Modules should add/create default xdoclet configurations
– Wizzards should add the right xdoclet tags to the sourcecode, activate/add the doclets and run the corresponding xdoclet task
btw… struts is working fairly well… good job. Any change on adding some semantic checks e.g. if there is no form name attribute matching with an action name attribute?
Ronald