{"action":"opened","issue":{"url":"https://api.github.com/repos/wildfly-extras/db-bootstrap/issues/18","labels_url":"https://api.github.com/repos/wildfly-extras/db-bootstrap/issues/18/labels{/name}","comments_url":"https://api.github.com/repos/wildfly-extras/db-bootstrap/issues/18/comments","events_url":"https://api.github.com/repos/wildfly-extras/db-bootstrap/issues/18/events","html_url":"https://github.com/wildfly-extras/db-bootstrap/issues/18","id":109749390,"number":18,"title":"db_bootstrap incompatible with change in JBoss Tools 4.3.0.Beta2 and newer","user":{"login":"mkjensen","id":1149537,"avatar_url":"https://avatars.githubusercontent.com/u/1149537?v=3","gravatar_id":"","url":"https://api.github.com/users/mkjensen","html_url":"https://github.com/mkjensen","followers_url":"https://api.github.com/users/mkjensen/followers","following_url":"https://api.github.com/users/mkjensen/following{/other_user}","gists_url":"https://api.github.com/users/mkjensen/gists{/gist_id}","starred_url":"https://api.github.com/users/mkjensen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mkjensen/subscriptions","organizations_url":"https://api.github.com/users/mkjensen/orgs","repos_url":"https://api.github.com/users/mkjensen/repos","events_url":"https://api.github.com/users/mkjensen/events{/privacy}","received_events_url":"https://api.github.com/users/mkjensen/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-10-05T08:10:59Z","updated_at":"2015-10-05T08:10:59Z","closed_at":null,"body":"JBoss Tools 4.3.0.Beta2 and newer includes a new feature (always on) that explodes jars in a deployment if the server adaptor supports it. WildFly does.\r\n\r\nThis means that you now have exploded jars inside an exploded deployment which apparently is a problem for db_bootstrap because it cannot find the classes specified in its configuration.\r\n\r\nWhile the configuration below works with JBoss Tool 4.3.0.Beta1, it breaks in JBoss Tool 4.3.0.Beta2 and newer with a ClassNotFoundException for com.example.Bootstrapper. The difference being that in Beta2, the class is located in some com.example\\*.jar while in Beta2, the class is exploded in the *directory* com.example\\*.jar/com.example. It also fails if the filter-on-name attribute is removed.\r\n\r\n```\r\n<scan name=\"Myname\" filename=\"MyEar.ear\" filter-on-name=\"com.example*.jar\">\r\n<class name=\"operation\" classname=\"com.example.Bootstrapper\" />\r\n</scan>\r\n```\r\n\r\nThe JBoss Tools 4.3.0.Beta2 feature: https://issues.jboss.org/browse/JBIDE-15250"}}