Both Maven and Gradle have to be configured individually to communicate through a proxy.
For configuring Maven, the settings.xml file in the {user.home}/.m2/
directory has to be edited. Create a new settings.xml if it does not exist. Within that file add the following tags to allow Maven to communicate through a proxy:
<settings>
<proxies>
<proxy>
<id>example</id>
<active>true</active>
<protocol>http</protocol>
<host>{IP-address of the proxy}</host>
<port>{port of the proxy}</port>
<nonProxyHosts>{excluded IP adresses}</nonProxyHosts>
</proxy>
</proxies>
</settings>
To allow communication using the https protocol, use <protocol>https</protocol>
or add an additional proxy configuration for https.
To configure Gradle to communicate through a proxy, the gradle.properties file located in the {user.home}/.gradle/
directory is modified. As with Maven, if it file does not exists, create a new one. Within that file, the properties for http and https proxies can be configured using the following expressions:
systemProp.http.proxyHost= {IP-address of the proxy}
systemProp.http.proxyPort= {port of the proxy}
systemProp.http.nonProxyHost= {excluded IP adresses}
systemProp.https.proxyHost= {IP-address of the proxy}
systemProp.https.proxyPort= {port of the proxy}
systemProp.https.nonProxyHost= {excluded IP adresses}
In both Maven and Gradle configurations, the nonProxyHost
property marks IP addresses which should be accessed without communicating through the proxy.
Two options for fetching data are possible: FetchType.EAGER and FetchType.LAZY. Collections are loaded EAGER when they are fetched fully at the time their parent is fetched. That is, with nested classes the whole class hierarchy is fetched, even if all the subentities (children) are not needed.
With the LAZY option, data is loaded on-demand, e.g. when a certain entity is requested explicitly. Thus, when the parent entity is loaded with the lazy option, the children entities are not loaded per default. Only in case they are really needed (e.g. a certain method was called via GUI).
Here is an example how entities are marked to be loaded lazily:
@Entity
public class Parent {
@Id
private String id;
private String name;
@OneToMany(fetch = FetchType.LAZY)
private List children;
// etc.
}
One solution to this problem is:
-Open Chrome on your computer.
-At the top right, click More and then click configuration.
-At the bottom, click Advanced settings.
-In the "Passwords and forms" section, click Manage passwords.
-In the "Saved passwords" section, on the right side of the website, click More and then click on Delete