{"action":"opened","issue":{"url":"https://api.github.com/repos/spring-cloud/spring-cloud-netflix/issues/205","labels_url":"https://api.github.com/repos/spring-cloud/spring-cloud-netflix/issues/205/labels{/name}","comments_url":"https://api.github.com/repos/spring-cloud/spring-cloud-netflix/issues/205/comments","events_url":"https://api.github.com/repos/spring-cloud/spring-cloud-netflix/issues/205/events","html_url":"https://github.com/spring-cloud/spring-cloud-netflix/issues/205","id":57200218,"number":205,"title":"Spring Cloud Eureka doesn't work on Jboss EAP","user":{"login":"krosangit","id":6663110,"avatar_url":"https://avatars.githubusercontent.com/u/6663110?v=3","gravatar_id":"","url":"https://api.github.com/users/krosangit","html_url":"https://github.com/krosangit","followers_url":"https://api.github.com/users/krosangit/followers","following_url":"https://api.github.com/users/krosangit/following{/other_user}","gists_url":"https://api.github.com/users/krosangit/gists{/gist_id}","starred_url":"https://api.github.com/users/krosangit/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/krosangit/subscriptions","organizations_url":"https://api.github.com/users/krosangit/orgs","repos_url":"https://api.github.com/users/krosangit/repos","events_url":"https://api.github.com/users/krosangit/events{/privacy}","received_events_url":"https://api.github.com/users/krosangit/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-02-10T16:42:05Z","updated_at":"2015-02-10T16:42:05Z","closed_at":null,"body":"Aside from a logging issue ([use logback by default in Eureka server](https://github.com/spring-cloud/spring-cloud-netflix/commit/069afb2a73778a227897a87714070c20ccf42847)) deploying a Spring boot app annotated with @EnableEurekaServer on Jboss EAP 6.3 still doesn't really work.\r\n\r\nUsing log4j, an issue arises with Jersey classpath scanning.\r\n\r\n    com.sun.jersey.api.container.ContainerException: The ResourceConfig instance does not contain any root resource classes.\r\n\r\nWhen deploying on embedded tomcat with debug logging turned on this should look like this:\r\n\r\n```\r\nINFO  com.sun.jersey.api.core.PackagesResourceConfig  - Scanning for root resource and provider classes in the packages:\r\n  com.netflix.discovery\r\n  com.netflix.eureka\r\nINFO  com.sun.jersey.api.core.ScanningResourceConfig  - Root resource classes found:\r\n  class com.netflix.eureka.resources.StatusResource\r\n  class com.netflix.eureka.resources.ASGResource\r\n  class com.netflix.eureka.resources.VIPResource\r\n  class com.netflix.eureka.resources.ApplicationsResource\r\n  class com.netflix.eureka.resources.PeerReplicationResource\r\n  class com.netflix.eureka.resources.SecureVIPResource\r\n  class com.netflix.eureka.resources.InstancesResource\r\nINFO  com.sun.jersey.api.core.ScanningResourceConfig  - Provider classes found:\r\n  class com.netflix.discovery.provider.DiscoveryJerseyProvider\r\nINFO  com.sun.jersey.server.impl.application.WebApplicationImpl  - Initiating Jersey application, version 'Jersey: 1.13 06/29/2012 05:14 PM'\r\n```\r\n\r\nThings I've done and tried:\r\n- Added [some Jboss VFS implementation code](https://code.google.com/p/reflections/wiki/JBossIntegration) as part of my Jboss-SpringBootServletInitializer.\r\n- Made sure eureka-core and eureka-client are being unpacked on building with the spring boot maven plugin\r\n- Adding the packages Jersey needs to scan to the boot application as such:\r\n```\r\n@Bean\r\n\tpublic ServletRegistrationBean dispatcherServletRegistration() {\r\n\t\tServletRegistrationBean registration = new ServletRegistrationBean();\r\n\t\tMap<String, String> params = new HashMap<String, String>();\r\n\t\tparams.put(\"com.sun.jersey.config.property.packages\", \"com.netflix.eureka.resources;com.netflix.discovery;com.netflix.eureka\");\r\n\t\tregistration.setInitParameters(params);\r\n\t\treturn registration;\r\n\t}\r\n```\r\n\r\nKind regards,\r\nAndreas Evers"}}