Let's talk about the activiti user manual and a book.

When I was idle, I read some java information and accidentally found activiti. I planned to run several examples on my own to see what happened. I have been working on the underlying layer, and I have to occasionally care about the extent to which the underlying layer actually develops.

The miserable process was like this. First, the activiti User Manual. The first time I saw such a messy user manual, it completely broke the "Hello World" process. Once you have not seen what activiti is, you can post various configuration codes as if you are afraid of not going to scare you. The entire user manual is not organized for research. If it is viewed in order, it cannot be viewed at all. In the end, I have not figured out how this user manual is organized. I have to say that open-source software has been engaged for more than two years. The first time such a user manual has been defeated, it seems like a mysterious feeling. The focus is not prominent, and the document does not have a sense of attention. It is completely speechless, which is also a major reason why many people speak about activiti beginners. (Decline: You can do it, this kind of childish thinking. Turn left when going out .)

In addition, I wanted to vomit a book. I searched for the book and found it in a big series (the specific book name was not mentioned, saving the effort to pull hatred ), this series gives me a good impression, especially for new contacts, meticulous and hands-on teaching. But this activiti book I want to talk about my next time. The details of this book are very detailed, the introduction to APIs in the user manual of the large section occupies the vast majority of the book. In addition, the book contains a large amount of internal code, and does not provide a CD, nor provide a place to download the code. The first example shows that this part needs to be searched separately. I just want to say that it is really good to find people, do you still need to read this book ?! Although I also advocate more hands-on work, a user's manual or a book is better than the first example. Let's have a general understanding first and then introduce the main sections, the secondary part can be supplemented by the reader, so that everyone can go deeper. There is a lot of suspicion of money fraud like this book. I don't know whether the author of this big series is clear or not, but it's a sign.

Attach some of your own lessons:

1. MAVEN must be used. It has never been used. activiti is mainly used for dependency library management. You don't need maven. It's very troublesome. (In this book, if you don't want to read the activiti source code, you don't need to use it here. Haha)

2. Before buying a book, you must find an electronic version to flip it over. No matter how good this series of books are, it doesn't mean it is now.

Let's talk about the activiti user manual and a book.