| RE: [wtp-incubator-dev] Integrating the JAX-WS DOM Tools contribution |
|
We could perhaps look at a property tester that would scan the project for classes annotated with at @WebService and combine that test with a test for either a jst.web 2.5 or a jst.ejb 3.0 project. I've opened a bug to track this: https://bugs.eclipse.org/bugs/show_bug.cgi?id=304428 Shane > Date: Tue, 2 Mar 2010 17:21:09 +0000 > Subject: Re: [wtp-incubator-dev] Integrating the JAX-WS DOM Tools contribution > From: oisin.hurley@xxxxxxxxx > To: wtp-incubator-dev@xxxxxxxxxxx > > > I would personally vote for the options to always display web services in > > case they are available. > > I think this make sense, I would add though that there should never be a > situation where a 'Web Services' container node would display as empty > if there were no Web services in the project (e.g. see the 'Servers' node > when you add a server and remove it - empty node stays). > > --oh > _______________________________________________ > wtp-incubator-dev mailing list > wtp-incubator-dev@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev Hotmail: Trusted email with powerful SPAM protection. Sign up now. |