Fix formatting

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

View File

@@ -40,8 +40,8 @@ import org.springframework.beans.BeansException;
* {@code BeanFactory} from which it gets the real object, to which it * {@code BeanFactory} from which it gets the real object, to which it
* delegates, then proper Dependency Injection has been achieved. * delegates, then proper Dependency Injection has been achieved.
* *
* <p>As another example, in a complex Java EE app with multiple layers, with each * <p>As another example, in a complex Java EE app with multiple layers, with
* layer having its own {@code ApplicationContext} definition (in a * each layer having its own {@code ApplicationContext} definition (in a
* hierarchy), a class like {@code SingletonBeanFactoryLocator} may be used * hierarchy), a class like {@code SingletonBeanFactoryLocator} may be used
* to demand load these contexts. * to demand load these contexts.
* *

View File

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

View File

@@ -35,7 +35,8 @@ import org.springframework.util.ClassUtils;
* configure JNDI appropriately, so that {@code new InitialContext()} * configure JNDI appropriately, so that {@code new InitialContext()}
* will expose the required objects. Also usable for standalone applications, * 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 * 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: * <p>There are various choices for DataSource implementations:
* <ul> * <ul>

View File

@@ -37,7 +37,8 @@ import org.springframework.util.ReflectionUtils;
* configure JNDI appropriately, so that {@code new InitialContext()} * configure JNDI appropriately, so that {@code new InitialContext()}
* will expose the required objects. Also usable for standalone applications, * 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 * 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: * <p>There are various choices for DataSource implementations:
* <ul> * <ul>