# Liquibase 2.0.5 and JBoss 7.1.1 supported

**URL:** https://forum.liquibase.org/t/liquibase-2-0-5-and-jboss-7-1-1-supported/2339
**Category:** General Discussion
**Created:** [August 1, 2013, 6:01am UTC](https://forum.liquibase.org/t/liquibase-2-0-5-and-jboss-7-1-1-supported/2339 "2013-08-01T06:01:00Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Bas](https://avatars.discourse-cdn.com/v4/letter/b/a587f6/32.png) [@Bas](https://forum.liquibase.org/u/Bas)
#### Post date: [August 1, 2013, 6:01am UTC](https://forum.liquibase.org/t/liquibase-2-0-5-and-jboss-7-1-1-supported/2339/1 "2013-08-01T06:01:00Z")

</div>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; We call liquibase programmatically and it works ok when the application runs standalone.&nbsp; When we run it inside jBoss however we get a ‘no parser found for changelog.xml’.&nbsp; In the find method around line 119 in DefaultPackageScanClassResolver I see that it checks for the FILE and JAR protocol, but we are having a jBoss module class loader which has the ‘vfs’ protocol.  
Does that mean we need to upgrade to using liquibase 3.0.2 or is there some other way around this?  
  
  
Mmm I upgraded to 3.0.2 and now getting an exception reported at [https://liquibase.jira.com/browse/CORE-1325](https://liquibase.jira.com/browse/CORE-1325) that causes my war deployment to roll back.