Java EE application development basics: A letter to the course representative

The following is a letter I wrote to the class representatives.

 

Haha, I learned about Java through Zhang Cong and CaO Wenjie two days ago.
The idea of the EE application development basics course is very responsible for the two course representatives. They respectively wrote an email to give me your thoughts and content that I want to talk about, after carefully reading the two emails, I sent them an email respectively. Today, I sorted out the content of my reply and reported it to you. If you have any ideas, you are welcome to communicate with me.

 

My reply (I have attached the original email ):

The suggestions are very good. I will take them seriously: 1. There is no problem in the classroom demonstration, but the development environment cannot be installed on the classroom computer. I can bring a notebook without every class, and the network environment of the classroom is not very good, so sometimes the prepared code demo cannot proceed smoothly, but it will delay the course progress. In the future, I will try my best to give you a more intuitive experience. 2. The experiment is based on the document. I will provide experimental videos for each experiment, but the video cannot provide sound. Please understand that I have recorded sound at home, however, the effect is poor and there is a lot of noise. I will provide you with "silent" video reference for subsequent experiments. 3. The key code of the experiment document will be marked with special colors. 4. I will record the video in advance. 5. In fact, I have always wanted to use eclipse as a development tool. However, I have tried it before. The effect is very poor. You are not familiar with eclipse and the Java basics are also uneven. If eclipse is used, I will spend too much effort on development tools (especially the installation of various plug-ins), so I finally chose myeclipse, saving you the trouble of installing plug-ins, focus on the Java EE technology. If you are proficient in myeclipse development, it is easy to develop on Eclipse. They are just plug-ins, and there is no difference in IDE, when opening the lab, I will add some plug-ins installed on Eclipse. 6. At the end of this course, we will have a comprehensive experiment for 15 or 16 weeks. We will build a relatively complete project, but it will not be enterprise-level, but only at the curriculum design level, from mastering the Basic Java EE technology to the enterprise level, some accumulation is required. These accumulation takes time and requires the amount of code. If you are interested in Java EE, we will provide you with a software project training in the last semester of the fourth grade, so that you can simulate a relatively large project.   I would also like to take this course well. I had a lot of ideas when I took this course last year, but I also came up with some questions. After all, this is just a class, it is impossible for me to take too much time for everyone, give too many learning tasks to everyone, and give too many things to everyone like a training institution. After all, this is just a course! Through this course, you can master some basic technologies and skills. This is enough. We will have a training session in the next semester, the graduation project of one semester will allow you to learn this content more deeply. Please do not worry, master the basic content in a down-to-earth manner, and complete basic experiments step by step, in the end, it will naturally be "A Matter Of course.   The content to be taught will be detailed in the comprehensive experiment in the last two weeks.   Finally, I wish you a smooth learning and good health!

 

 

Original Email:

INSTRUCTOR: There are some suggestions for learning this course in our class. Let's summarize it with you. I interviewed people in the dormitory, asked questions, and discussed them in the group. For the current javaee learning, we are divided into classes and labs. First of all, in the class, many people reflect that the theory in the class is a little fast and I don't know much about it. It is better to watch the demonstration experiment you have done in the class. We suggest you do more demonstrations in the class, if the time is too short, just demonstrate the code you have done. Most of the students said that the knowledge learned and understood in the class is not as good as that obtained through practice in the lab class. By doing experiments, we can have a more perceptual knowledge and improve our troubleshooting capabilities. In the lab course, I learned from my classmates that, instead of taking us with you, we should watch the document on our own, because in the previous experiments, many of you may not be able to keep up with your pace. Once you leave your mind behind, you will not be able to continue, and you are still doing it step by step. You may not be able to keep up with your classmates, or simply quit. Another important thing is that, even if you keep up with the code, you don't have time to consider what the code is, because you are busy typing code to catch up with your progress, you have no time to think about what the code means. In yesterday's lab class, our class watched the experiment documentation and the videos you prepared. They all reflected that the results were better than the original ones. In addition, many people reflect that the video you recorded is quite good. When you encounter an error, you will know what went wrong when you review the video. Although I did not watch the video, many people have reported this from next week, we did experiments in section 1st and section 2 of our class. If you can, it would be best to have a video recorded in advance. However, this increases your workload. I also have a small suggestion for us to watch the document and do it. I think it is better to directly copy and paste the document to gain a perceptual knowledge. If all the code is typed, time is not enough, so if you can, I think the experiment documentation can be adjusted a little, mark some key code and code that is necessary to familiarize us with in red or other eye-catching colors, so that we can copy and paste the selected code during the experiment, the results will be much better if the key code is typed by myself. I also saw this practice in a javaee book I bought. I think I can try it. In addition, some students want to learn how to use eclipse for development. In fact, I also want to know what compilation tools are most used for enterprise development. If this is necessary, it can be used as a supplement when the lab is open. Another part of the students who are better at learning have shown that it is okay for us to look at the document, but it won't happen after we leave the document. I also think that we lack this practice. I think we can do some lab tasks that are close to the requirements of the enterprise level. At the very least, we can't do all the code, just like doing lab courses, I think you can give us more specific system functions, development ideas and steps, or give us specific practices and some key code, as long as you don't give all the code. It gives us some space for independent development. I think this must be exercised. Of course, in this case, the progress of each lab course may be slow. However, I think it is also worth it. Once it is done, it can be arranged in the open lab, for students who love to learn or want to engage in this course, they can take time to complete the course. For those who want to get mixed credits, they can only do that part of the lab course. Also, since the focus of this course is on the three frameworks that have just been completed, it is necessary to add three frameworks to be integrated into a more complex exercise. Well, basically, that's all. It's a bit messy and a bit cool. Let me explain it separately. 1. There are more demos in the class, so you don't need to knock on the Code. Slow down. Just take us to understand the key code. 2. We recommend that you cancel the code step by step so that we can read the document. 3. It is recommended that key codes be marked with special colors in the experiment document. 4. Before the Lab Course, you can record the Demo Video in advance. 5. Is there any need to add learning to use eclipse for development when opening the lab. 6. Some practical opportunities for enterprise-level development will be added. Part of the lab courses will be completed, and the rest will be completed. Okay, that's all. This is a small summary of my suggestions and situations. Let's take a look at it. If it makes sense, you can try it.

 

Another one is the content that needs to be taught again:

1. Use of struts2 internationalization and Struts 2 interceptor 2. Verify the validate method in the framework (XML) and Action classes. 3. hibernatesessionfactory and hibernate core Interfaces 4. hibernate relationship ing 5. Main spring Interfaces 6. Dynamic proxy (invoke)

 

Wish everyone a smooth learning!