issueSpring MVC提交form表单后台通过@ModelAttribute获取参数为乱码Spring MVC submit form and get random code parameters through `@ModelAttribute
Java Config WebInitializer
傻了，将CharacterEncodingFilter部分放到DispatcherServlet部分前面就可以了
1 | public class WebInitializer implements WebApplicationInitializer { |
SQL and QL injection can be effectively prevented with the use of JPA Named Queries. In the contrary to the CMP 2.X spec, JPA QL are in general more flexible and can be parameterized.
You can cover almost 90% of all cases with named queries. However, named queries only works in case the structure of the query is stable, and the parameters vary.
Sometimes more flexibility is needed. Building the queries with Strings has several drawbacks:
Lack or IDE support
Syntax is evaluated at runtime. (affects performance and stability)
QL/SQL injection is possible.
With a little “hack” and builder pattern, it is possible to use almost the old syntax more conveniently.
Instead of writing a something like this:
1 | String expected = "SELECT e FROM Customer e WHERE e.name = :name"; |
You could chain methods, which looks like this:
1 | EntityQuery query = new EntityQuery.SELECT().ENTITY().FROM(Customer.class).WHERE().attribute("name").build(); |
A static inner class with the name SELECT implements the builder pattern and takes the responsibility for building the queries:
1 | public class EntityQuery { |
The Entity Query Builder, as well as the unit tests are available from http://qlb.dev.java.net. I’m working now on the EntityManager integration. First samples should be available in few days.
——————–华丽丽的分割线————————
I miss you.
(づ｡◕‿‿◕｡)づ 外面浪了一天，好累，我想静静，内容待补充…… 2016年2月14日01:46:12
update：然后就没然后了，反正我也不记得了，laudukang，2017-11-25 22:39:39
Retrieves an entity by its id.
Parameters:
id - must not be null.
Returns:
the entity with the given id or null if none found
Throws:
IllegalArgumentException - if id is null
Returns a reference to the entity with the given identifier.
Parameters:
id - must not be null.
Returns:
a reference to the entity with the given identifier.
See Also:
EntityManager.getReference(Class, Object)
{ % ossimag os-admin-debug.png % }
DEBUG下：osAdmin 为getOne()查询的结果，osAdmin2为findOne查询的结果
Caused by: org.springframework.data.mapping.PropertyReferenceException: No property saveAdmin found for type OsAdmin!
Exception message:
1 | java.lang.IllegalStateException: Failed to load ApplicationContext |
Solution:
在git中如果想忽略掉某个文件，不让这个文件提交到版本库中，可以使用修改 .gitignore 文件的方法。
这个文件每一行保存了一个匹配的规则例如：
1 | #此为注释 – 将被 Git 忽略 |
另外 git 提供了一个全局的.gitignore，你可以在你的用户目录下创建~/.gitignoreglobal文件，以同样的规则来划定哪些文件是不需要版本控制的。
需要执行以下命令来使得它生效。
1 | git config --global core.excludesfile ~/.gitignoreglobal |
其他的一些过滤条件
1 | * ？：代表任意的一个字符 |
由于git不会加入空目录，所以下面做法会导致tmp不会存在
1 | tmp/* //忽略tmp文件夹所有文件 |
改下方法，在tmp下也加一个.gitignore，内容为
1 | * |
还有一种情况，就是已经commit了，再加入gitignore是无效的，所以需要删除下缓存
1 | git rm -rf --cached ignore_file |
.gitignore只能忽略那些原来没有被track的文件，如果某些文件已经被纳入了版本管理中，则修改.gitignore是无效的。
另外 git 还提供了另一种 exclude 的方式来做同样的事情，不同的是 .gitignore 这个文件本身会提交到版本库中去。用来保存的是公共的需要排除的文件。而.git/info/exclude这里设置的则是你自己本地需要排除的文件。
他不会影响到其他人。也不会提交到版本库中去。
.gitignore 还有个有意思的小功能， 一个空的 .gitignore 文件 可以当作是一个 placeholder 。当你需要为项目创建一个空的 log 目录时， 这就变的很有用。 你可以创建一个 log 目录 在里面放置一个空的 .gitignore 文件。这样当你 clone 这个 repo 的时候 git 会自动的创建好一个空的 log 目录了。
reference:
Few months ago I started playing with Spring Framework, which I really enjoy. Looking for the tutorials I found some really great resources on the web as well as books. Unfortunately many of them were written for Spring 2.x, which lacks some recent features, mainly ability to configure everything by Java annotations (a.k.a. JavaConfig) rather than XML. That was something that kept me away from Spring at the first place - doing it programmatically gives much more sense of control and is more readable. So, that’s what I’m trying to achieve here, I’ll try to show you how to do it in more ‘modern’ way, showing integrations with various software packages along the way.
Let’s start with a simple skeleton Spring MVC application. Since version 3.1 it has Servlet 3 API support, I won’t use web.xml for configuring DispatcherServlet, rather I’ll configure it programmatically.
Full source code for this article is here on GitHub
Most important dependencies for this project will be spring-webmvc, which provides DispatcherServlet and pulls other Spring artifacts together with it and Servlet 3.0 API.
1 | <dependency> |
AppInitializer is a class that implements WebApplicationInitializer interface. We hook up to onStartup() method, to add DispatcherServlet to ServletContext.
1 | public class AppInitializer implements WebApplicationInitializer { |
Several things happen here:
The main AppConfig configuration class doesn’t do anything but hits Spring on where to look for its components through @ComponentScan annotation.
1 |
|
WebMvcConfig class enables Spring MVC with @EnableWebMvc annotation. It extends WebMvcConfigurerAdapter, which provides empty methods that can be overridden to customize default configuration of Spring MVC. We will stick to default configuration at this time, but it’s advised for you to see what the possibilities are.
1 |
|
Controllers are annotated with @Controller. It is found by Spring because of @ComponentScan annotation in AppConfig. The method will intercept GET request to “/“ to which the response will be sent. @ResponseBody indicates that whatever this method returns will be response body, and in this case it’s just a “Hello world” String.
1 |
|
That is all that is needed for skeleton Spring MVC application written using pure JavaConfig and for Servlet 3 API, without web.xml.
See the working example you can play around with - https://github.com/bkielczewski/example-spring-mvc-initializer
reference:
7.1.2
谷歌又玩我23333
自7.1.2（开始？），”captive_portal_detection_enabled”设置已被废弃，现在改为了”captive_portal_mode”选项，该选项可设置为以下3种值：
0：彻底禁用检测(Don’t attempt to detect captive portals.)
1：检测到需要登录则弹窗提醒（默认值）(When detecting a captive portal, display a notification that prompts the user to sign in.)
2：检测到需要登录则自动断开此热点并不再自动连接(When detecting a captive portal, immediately disconnect from the network and do not reconnect to that network in the future.)
叹号杀手已经更新以支持该版本。
但愿以后谷歌不要再乱改了233333
感谢 jingyu9575 的帮助 https://github.com/Noisyfox/NoExclamation/issues/2
7.1.1
从7.1.1开始，检测用的服务器地址储存格式发生了变化，改为了：
1 | private static String getCaptivePortalServerHttpsUrl(Context context) { |
以及
1 | public static String getCaptivePortalServerHttpUrl(Context context) { |
可以看到，系统不会自动加入”generate_204″的后缀了，这意味着url可以设计的更加灵活，同时也意味着在设置的时候需要填入完整的url：
1 | adb shell "settings put global captive_portal_https_url https://www.noisyfox.cn/generate_204" |
当然如果只有http的话，可以执行：
1 | adb shell "settings put global captive_portal_use_https 0" |
请参考
Java工程师成神之路~