java - websphere network deployment v8.5.5.0 not scanning annotated web service classes during deployment -

I have a simple ear file that contains a war file in which the local EasyWeb class is annotated with WebServity.

  @WebService @Stateless @LocalBean Public Square TestWS {@WebMethod} Public Int wordfile () {return 42;}}  

My web The XML file is as follows:

  & lt ;? XML version = "1.0" encoding = "UTF-8"? & Gt; & Lt; Web-app xmlns = "http://java.sun.com/xml/ns/javaee" xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance" XSI: Schema location = "Http : //java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd "Metadata-FULL =" false "version =" 3.0 "& gt; ; & Lt; / Web application & gt;  

When I keep this file on my test server (WebSpace application server v 8.5.5.0 packed with RAD v9.0), scan and deploy web services And I can see them in the configuration, access the screen and WSDL files properly.

However, when I try to apply the application to webserver application server network deployment V 8.5.5.0, the annotation not scan and I The Web service can not see the prodware configuration settings when I click on the app from the WebPier Admin console and its end point URL is not resolved.

Interesting, scanning was active at last (ear) deployment but when I put the same ear file in the server for a second time, then it also failed

Because the web.xml shown above Version 3.0, should be scanning And because Websphere 8.5 is fully compliant with Java AE6, it should do so.

Setting UseWSFEP61ScanPolicy to Correct in Management. MF does not work even if it should scan the class file.

I started spending days to solve this problem and I probably appreciate anyone with WebSpace knowledge to guide me.

Update: The metadata-full feature is defintely wrong in the setup and I further ensure that it is unchecked in the deployment.

Check that this is your deployed application.

You can do this with NAD Console:

Enterprise Application > Your App > for Metadata Module > Uncheck the Metadata-Full Attributes checkbox, synchronize with the node and restart your app.

If this does not work, then uninstall / reinstall it application but be careful when setting metadata-full as disabled during TO deployment.