Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@kaffeebaum
Copy link
Contributor

Fixed java.io.NotActiveException: writeFields() may only be called when the fields have not yet been written

Based on issue with dom4j 1.6.1 on JBoss EAP 6+, see http://stackoverflow.com/questions/28740888/cant-serialize-org-dom4j-document-using-jboss-marshalling-api

Fixed java.io.NotActiveException: writeFields() may only be called when the fields have not yet been written

Based on issue with dom4j 1.6.1 on JBoss EAP 6+, see http://stackoverflow.com/questions/28740888/cant-serialize-org-dom4j-document-using-jboss-marshalling-api
@codecov-io
Copy link

Current coverage is 39.28% (diff: 100%)

Merging #17 into master will not change coverage

@@             master        #17   diff @@
==========================================
  Files           144        144          
  Lines          9477       9477          
  Methods           0          0          
  Messages          0          0          
  Branches       1480       1480          
==========================================
  Hits           3723       3723          
  Misses         5377       5377          
  Partials        377        377          

Powered by Codecov. Last update aae6a47...c97d480

@FilipJirsak FilipJirsak added this to the 2.0.1 milestone Oct 26, 2016
@kaffeebaum
Copy link
Contributor Author

@FilipJirsak Do you know when you are going to release 2.0.1? We are still stuck with our self-patched 1.6.1 version and would like to switch to 2.0.1.

@FilipJirsak FilipJirsak merged commit ae66810 into dom4j:master Jun 17, 2017
@FilipJirsak
Copy link
Contributor

@kaffeebaum dom4j-2.0.1 released today. You can download it from GitHub, or it can reach Maven Central repository within few hours.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Development

Successfully merging this pull request may close these issues.

3 participants