Spring/spring-framework
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix formatting

Browse Source 
Closes gh-1206
This commit is contained in:
Stephane Nicoll
2016-10-15 11:55:07 +03:00
parent ae5b0c6fb5
commit fc8bad36c9
4 changed files with 9 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
spring-context/src/main/java/org/springframework/ejb/access/AbstractRemoteSlsbInvokerInterceptor.java
View File

@@ -53,9 +53,9 @@ public abstract class AbstractRemoteSlsbInvokerInterceptor extends AbstractSlsbI
* Set a home interface that this invoker will narrow to before performing
* the parameterless SLSB {@code create()} call that returns the actual
* SLSB proxy.
* <p>Default is none, which will work on all Java EE servers that are not based
* on CORBA. A plain {@code javax.ejb.EJBHome} interface is known to be
* sufficient to make a WebSphere 5.0 Remote SLSB work. On other servers,
* <p>Default is none, which will work on all Java EE servers that are not
* based on CORBA. A plain {@code javax.ejb.EJBHome} interface is known to
* be sufficient to make a WebSphere 5.0 Remote SLSB work. On other servers,
* the specific home interface for the target SLSB might be necessary.
*/
public void setHomeInterface(Class<?> homeInterface) {

3
spring-context/src/test/java/org/springframework/tests/mock/jndi/SimpleNamingContextBuilder.java
View File

@@ -35,7 +35,8 @@ import org.springframework.util.ClassUtils;
* configure JNDI appropriately, so that {@code new InitialContext()}
* will expose the required objects. Also usable for standalone applications,
* e.g. for binding a JDBC DataSource to a well-known JNDI location, to be
* able to use traditional Java EE data access code outside of a Java EE container.
* able to use traditional Java EE data access code outside of a Java EE
* container.
*
* <p>There are various choices for DataSource implementations:
* <ul>