In my previous post I talked about how to support both JSON and XML in a Spring MVC web service. The observant reader might have noticed that if a request was made with an Accept header with neither application/json nor application/xml specified then the data was returned in XML. The integration test in the example code used to illustrate this looked like this: @Test public void getUserWithUnsuppo
REST is an alternate and simpler approach for implementing WebServices. It is based on the HTTP protocol and hence leverages a lot of existing infrastructures. It uses an uniform interface thus making it easy to build client applications. In this session we will look at the fundamental concepts behind REST (Resource, URI, Stateless Conversation ..) and how to apply it in the context of a real appl
In the last couple of years, REST has emerged as a compelling alternative to SOAP/WSDL/WS-*-based distributed architectures. So when we started to plan our work on the next major release of Spring - version 3.0, it was quite clear to us that we had to focus on making the development of 'RESTful' Web services and applications easier. Now, what is and isn't 'RESTful' could be the topic of a whole ne
This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. Red Hat, as the licensor of this document, waives the right to enforce, and ag
Introduction In my earlier post announcing Spring 3.1 M1, I discussed the new bean definition profiles feature as applied when using Spring <beans/> XML to configure the container. Today we'll introduce the new @Profile annotation and see how this same feature can be applied when using @Configuration classes instead of XML. Along the way we'll cover some best practices for designing @Configuration
Categories 2.0 (29) 2.5/2.1 (18) 3.0 (37) 3.1 (15) AMQP (7) Android (4) AOP (19) Apache Tomcat (7) Books (3) Builds (15) Bundlor (1) Business (26) Cloud Computing (46) Cloud Foundry (18) Containers (11) Data Access (38) dm Server (64) Enterprise Integration (17) Google (3) Green Beans (6) Groovy/Grails (47) Hyperic HQ (6) Hyperic IQ (1) IOC Container (31) Java (68) JMS (6) JMX (4) JSF (2) Manageme
In 2014, we announced the retirement of our legacy forum, forum.spring.io, in favor of providing an improved community experience on stackoverflow.com. As part of that announcement, we put our forum into read-only mode, preserving forum posts that were referenced in various Spring issue trackers. On February 28, 2019, we plan to take the forum completely offline. In preparation for this end-of-lif
本企画では、Springの主要プロダクトを順に取り上げ、その役割や使い方を簡単に紹介している。 今回取り上げるのは「Spring Security」。同プロダクトはSpring Sourceが提供するユーザ認証・アクセス制御のためのプロダクトである。以下ではSpring Securityの基本的な利用方法に加えて、拡張に備えたクラス構造の説明をする。 Spring Securityとは Spring Securityは、Bean定義ファイルを書き換えることで、様々な要件のシステムに対応することが可能だ。また、長大になりがちなBean定義ファイルも、Spring Security専用のXML名前空間のタグ(以下Securityタグ)を利用することで、設定の柔軟性を失わずに簡潔に記述することが可能になっている。 Spring SecurityはSecurityという名前がついているが、あくまで
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く