


Problem with spring+mybatis+axis2 publishing webservice interface on myeclipse
Premise:
Suddenly one day this month, there was a project docking that required the use of the interface published by axis2. This stumped me. After all, I didn’t even know how to publish the webservice interface before. Later, the first interface - sayHi() was released from HelloWorld; up to this step everything went smoothly. Only when integrating with axis2, a problem occurred. The dao layer of spring was in the interface after axis2 was released. , has always been null, it seems that spring has not been initialized. During this period, I tested to execute a request according to the normal process, and it was correct. However, it did not work after integrating with axis2. During this test, it was very painful. It's very painful. I have tried all imaginable methods one by one, including forced acquisition of dao and singleton mode, but nothing works. So I had to settle for the next best thing, first use spring+mybatis+cxf to publish a usable interface as a proxy, and then use the axis2 box to publish a separate method to call the proxy to achieve project docking. Let's start with the introduction of spring+mybatis+cxf:
1. Create the project directory:
First, we create an entity class Person.java
package com.srit.user.model;public class Person {private String id; private String name; private int age; private String birthday; private double hight; public String getId() { return id; } public void setId(String id) { this.id = id; } public String getName() { return name; } public void setName(String name) { this.name = name; } public int getAge() { return age; } public void setAge(int age) { this.age = age; } public String getBirthday() { return birthday; } public void setBirthday(String birthday) { this.birthday = birthday; } public double getHight() { return hight; } public void setHight(double hight) { this.hight = hight; } }
Then let’s first write PersonDao.java in dao. It is an interface. It mainly performs simple addition, deletion, modification and query
package com.srit.user.dao;import java.util.List;import javax.jws.WebMethod;import javax.jws.WebService;import com.srit.user.model.Person;public interface PersonDao {public void insertPerson(Person person); public void updatePerson(Person person); public List<person> findPerson(String name); public void deletePerson(String id); }</person>
The following is the implementation class PersonDaoImpl.java
1 package com.srit.user.dao.impl; 2 3 import java.util.List; 4 5 import javax.annotation.Resource; 6 7 import org.mybatis.spring.SqlSessionTemplate; 8 import org.mybatis.spring.support.SqlSessionDaoSupport; 9 10 import com.srit.user.dao.PersonDao;11 import com.srit.user.model.Person;12 13 public class PersonDaoImpl extends SqlSessionDaoSupport implements PersonDao {14 15 private SqlSessionTemplate sqlSessionTemplate; 16 17 public SqlSessionTemplate getSqlSessionTemplate() { 18 return sqlSessionTemplate; 19 } 20 21 @Resource(name="sqlSessionTemplate") 22 public void setSqlSessionTemplate(SqlSessionTemplate sqlSessionTemplate) { 23 this.sqlSessionTemplate = sqlSessionTemplate; 24 } 25 26 public void deletePerson(String id) { 27 getSqlSession().delete("com.srit.usr.dao.PersonDao.deletePerson", id); 28 } 29 30 public List<person> findPerson(String name) { 31 return getSqlSession().selectList("com.srit.user.dao.PersonDao.findPerson", name); 32 } 33 34 public void insertPerson(Person person) { 35 getSqlSession().insert("com.srit.user.dao.PersonDao.insertPerson", person); 36 } 37 38 public void updatePerson(Person person) { 39 getSqlSession().update("com.srit.user.dao.PersonDao.updatePerson", person); 40 } 41 42 43 }</person>
of the dao layer, followed by the service layer PersonService.java
package com.srit.user.service;import java.util.List;import com.srit.user.model.Person;public interface PersonService {public void insertPerson(Person person); public void updatePerson(Person person); public List<person> findPerson(String name); public void deletePerson(String id); }</person>
Next is the implementation class of the service layer, PersonServiceImpl.java
package com.srit.user.service.impl;import java.util.List;import javax.annotation.Resource;import org.springframework.stereotype.Service;import org.springframework.transaction.annotation.Transactional;import org.springframework.web.context.ContextLoader;import org.springframework.web.context.WebApplicationContext;import com.srit.user.dao.PersonDao;import com.srit.user.model.Person;import com.srit.user.service.PersonService; @Service @Transactional public class PersonServiceImpl implements PersonService { @Resource private PersonDao personDao; public PersonDao getPersonDao() { return personDao; } public void setPersonDao(PersonDao personDao) { this.personDao = personDao; // WebApplicationContext context=ContextLoader.getCurrentWebApplicationContext();// personDao =(PersonDao)context.getBean("personDao"); } public void deletePerson(String id) { personDao.deletePerson(id); } public List<person> findPerson(String name) { return personDao.findPerson(name); } public void insertPerson(Person person) { personDao.insertPerson(person); } public void updatePerson(Person person) { personDao.updatePerson(person); } }</person>
, and then the service interface we want to publish, MyWebservice.java
1 package com.srit.user.webservice;2 3 import com.srit.user.model.Person;4 5 public interface MyWebservice {6 public String czDate(Person person); 7 }
Of course it must have its implementation class MyWebserviceImpl.java
After get off work. . . Next time I’ll write
The above is the detailed content of Problem with spring+mybatis+axis2 publishing webservice interface on myeclipse. For more information, please follow other related articles on the PHP Chinese website!

MySQLoffersvariousstorageengines,eachsuitedfordifferentusecases:1)InnoDBisidealforapplicationsneedingACIDcomplianceandhighconcurrency,supportingtransactionsandforeignkeys.2)MyISAMisbestforread-heavyworkloads,lackingtransactionsupport.3)Memoryengineis

Common security vulnerabilities in MySQL include SQL injection, weak passwords, improper permission configuration, and unupdated software. 1. SQL injection can be prevented by using preprocessing statements. 2. Weak passwords can be avoided by forcibly using strong password strategies. 3. Improper permission configuration can be resolved through regular review and adjustment of user permissions. 4. Unupdated software can be patched by regularly checking and updating the MySQL version.

Identifying slow queries in MySQL can be achieved by enabling slow query logs and setting thresholds. 1. Enable slow query logs and set thresholds. 2. View and analyze slow query log files, and use tools such as mysqldumpslow or pt-query-digest for in-depth analysis. 3. Optimizing slow queries can be achieved through index optimization, query rewriting and avoiding the use of SELECT*.

To monitor the health and performance of MySQL servers, you should pay attention to system health, performance metrics and query execution. 1) Monitor system health: Use top, htop or SHOWGLOBALSTATUS commands to view CPU, memory, disk I/O and network activities. 2) Track performance indicators: monitor key indicators such as query number per second, average query time and cache hit rate. 3) Ensure query execution optimization: Enable slow query logs, record and optimize queries whose execution time exceeds the set threshold.

The main difference between MySQL and MariaDB is performance, functionality and license: 1. MySQL is developed by Oracle, and MariaDB is its fork. 2. MariaDB may perform better in high load environments. 3.MariaDB provides more storage engines and functions. 4.MySQL adopts a dual license, and MariaDB is completely open source. The existing infrastructure, performance requirements, functional requirements and license costs should be taken into account when choosing.

MySQL uses a GPL license. 1) The GPL license allows the free use, modification and distribution of MySQL, but the modified distribution must comply with GPL. 2) Commercial licenses can avoid public modifications and are suitable for commercial applications that require confidentiality.

The situations when choosing InnoDB instead of MyISAM include: 1) transaction support, 2) high concurrency environment, 3) high data consistency; conversely, the situation when choosing MyISAM includes: 1) mainly read operations, 2) no transaction support is required. InnoDB is suitable for applications that require high data consistency and transaction processing, such as e-commerce platforms, while MyISAM is suitable for read-intensive and transaction-free applications such as blog systems.

In MySQL, the function of foreign keys is to establish the relationship between tables and ensure the consistency and integrity of the data. Foreign keys maintain the effectiveness of data through reference integrity checks and cascading operations. Pay attention to performance optimization and avoid common errors when using them.


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

WebStorm Mac version
Useful JavaScript development tools

mPDF
mPDF is a PHP library that can generate PDF files from UTF-8 encoded HTML. The original author, Ian Back, wrote mPDF to output PDF files "on the fly" from his website and handle different languages. It is slower than original scripts like HTML2FPDF and produces larger files when using Unicode fonts, but supports CSS styles etc. and has a lot of enhancements. Supports almost all languages, including RTL (Arabic and Hebrew) and CJK (Chinese, Japanese and Korean). Supports nested block-level elements (such as P, DIV),

EditPlus Chinese cracked version
Small size, syntax highlighting, does not support code prompt function

DVWA
Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software

SublimeText3 English version
Recommended: Win version, supports code prompts!
