This release adds the “follow_api” to SteemJ, which includes 10 new api calls. Beside that a lot of fixes and improvements have been made.

Previous 0.2.x releases: 0.2.6 v0.2.5 v0.2.4 v0.2.3 v0.2.2 v0.2.1 v0.2.0

#SteemJ v0.3.0 has been released

Hello Steemians!

So another two weeks have passed since the last update and here is what happened. According to the page views and numbers of clones on GitHub more and more people start to test and use SteemJ for their projects. This is absolutly great and makes me really happy =). Do you know what the best part is when people start to use your stuff? They help you to improve! Here are two bigs “thank you”s to @sesangsokuro, who requested the implementation of the “follow_api” in the comment section of the last update post and [saggammahesh](https://github.com/saggammahesh] on GitHub, who found some really critical issues in SteemJ.

I hope this release fixes everything you need to continue your projects – Otherwise, please let me know it =) I am always happy about any feedback, request or bug report and will try to help you as soon as possible.

Before we have a look at the detailed changes, let’s take a look at the SonarQube dashboard for this release.

While adding integration tests for each new feature, the overall coverage still went down a little bit. This is caused by not checking all/enough fields of the objects and should be improved for the upcoming releases.

Changelog

Let’s now have a look at the detailed changelog.

Functional Updates

• The follow_api has been implemented which includes the following api calls:
• getBlogAuthors
• getRebloggedBy
• getAccountReputations
• getBlog
• getBlogEntries
• getFeed
• getFeedEntries
• getFollowCount
• getFollowing
• getFollowers
• The following issues have been fixed:
  • #24 Not able to send comments with more the 127 characters.
  • Fix getBlock method which now returns a SignedBlockWithInfo object instead of a Block object
  • Fix getNextScheduledHarfork method which used the wrong api
  • Fix parsing issues of BlockHeaderExtension
  • Fix parsing issues of CommentOptionsExtension
• The following model objects have been added:
  • HardforkVersionVote
  • CommentPayoutBeneficiaries
  • BeneficiaryRouteType
• The “Content” object has been splitted into a “Comment” and a “Discussion” object as it is done by Steem.
• The package structure has changed from “steem.api.wrapper” to “steemj”.

Code Quality Improvements

• Additional integration tests have been added.

Documentation

• The example application has been updated.
• Additional JavaDoc has been added to several methods and fields

Sadly, the Wiki is not up to date yet, but I’ll try to solve this in the upcoming days.

General information

What is SteemJ?

SteemJ is a project that allows you to communicate with a Steem node using Java. So far, the project supports most of the API calls and is also able to broadcast most of the common operation types. Further information can be found on GitHub.

https://github.com/marvin-we/steem-java-api-wrapper

How to add it to your project?

SteemJ binaries are pushed into the maven central repository and can be integrated with a bunch of build management tools like Maven. The Wiki provides a lot of examples for the most common build tools. If you do not use a build management tool you can download the binaries as described here.

Contribute

The project became quite big and there is still a lot to do. If you want to support the project simply clone the git repository and submit a pull request. I would really appreciate it =).

git clone https://github.com/marvin-we/steem-java-api-wrapper.git

Get in touch!

Most of my projects are pretty time consuming and I always try to provide some useful stuff to the community. What keeps me going for that is your feedback and your support. For that reason I would love to get some Feedback from you <3. Just contact me here on Steemit or ping me on GitHub.

---

If you want to stay up to date or just like the stuff I am doing it would be great if you could press the button below =).

Thanks for reading and best regards,
@dez1337