Aguilas Doradas vs Deportes Tolima

Expert Analysis: Aguilas Doradas vs Deportes Tolima

This upcoming match between Aguilas Doradas and Deportes Tolima promises to be an intriguing encounter, with both teams showcasing strong defensive capabilities as well as potent attacking options. The statistical data suggests a tightly contested game, with several betting markets indicating a balanced competition. Notably, the probability of both teams not scoring in the first half is high at 89.60%, hinting at a cautious start from both sides. As the match progresses into the second half, there’s a notable increase in the likelihood of Aguilas Doradas scoring, with a prediction of 79.20%. This shift could be attributed to potential adjustments made during halftime or changes in momentum.

Aguilas Home Over Both Over 1.5 Under Both Last Home Away Away First Goal Avg. Total Doradas

LLWWW

Deportes Tolima

WWWWW

Date: 2025-11-14

Time: 00:00
(FT)

Venue: Arturo Cumplido Sierra

Score: 1-2

Predictions:

Market	Prediction	Odd
Both Teams Not To Score In 1st Half	87.00%	(1-2) 0-1 1H 1.19	79.80%	(1-2)	71.80%	(1-2) 0-1 1H 1.50	74.70%	(1-2) 1-1 2H 1.33	58.50%	(1-2) 1.34	58.80%	(1-2) 1.83	58.70%	(1-2) 2.05	55.80%	(1-2) 90' min 1.83	57.00%	(1-2)	56.20%	(1-2)	57.80%	(1-2)	55.50%	(1-2)	58.50%	(1-2)	3.79%	(1-2)
Avg. Goals Scored	1.85%	(1-2)
Avg. Conceded Goals	2.34%	(1-2)
Red Cards	0.77%	(1-2)

Betting Predictions

Defensive Outlook

Both Teams Not To Score In 1st Half: 89.60% – Expect a tight first half with minimal goals.
Both Teams Not To Score In 2nd Half: 73.90% – Defensive strategies may continue to dominate.
Both Teams Not To Score: 62.00% – A low-scoring affair is possible throughout the match.

Scoring Trends

Avg. Total Goals: 3.09 – A moderate number of goals might be expected overall.
Avg. Goals Scored: 2.15 – Both teams are likely to find the net more than once.
Avg. Conceded Goals: 2.04 – Defensive vulnerabilities may lead to goals conceded by both sides.

Tactical Insights

Last Goal After 73+ Minutes: 54.00% – Late goals could be decisive in this match.

Away Team Not To Score In First Half: 58.00% – Deportes Tolima might struggle initially against a solid defense.

Prediction Highlights

Aguilas Doradas Likely Scorer in Second Half:

The prediction for Aguilas Doradas scoring in the second half stands at a strong likelihood of 79.20%, suggesting that they might capitalize on any weaknesses exposed by Deportes Tolima as fatigue sets in.

Possible Late Goals Scenario:

The chance of goals being scored after the first hour (Last Goal After 73+ Minutes) is significant at 54%, indicating that late-game tactics or substitutions could play crucial roles in determining the outcome.

Total Goal Projections:</lReneObermann/MyHealth/src/main/java/com/myhealth/server/model/User.java
package com.myhealth.server.model;

import java.util.Date;
import java.util.HashSet;
import java.util.Set;

import javax.persistence.Column;
import javax.persistence.Entity;
import javax.persistence.FetchType;
import javax.persistence.GeneratedValue;
import javax.persistence.GenerationType;
import javax.persistence.Id;
import javax.persistence.JoinColumn;
import javax.persistence.JoinTable;
import javax.persistence.ManyToMany;
import javax.persistence.ManyToOne;

/**
*
* @author rene
*
*/
@Entity
public class User {
@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
private Long id;

@Column(nullable = false)
private String name;

@Column(nullable = false)
private String email;

@Column(nullable = false)
private String password;

@ManyToMany(fetch = FetchType.EAGER)
@JoinTable(name = “user_role”, joinColumns = { @JoinColumn(name = “user_id”) }, inverseJoinColumns = {
@JoinColumn(name = “role_id”) })
private Set roles = new HashSet();

public Long getId() {
return id;
}

public void setId(Long id) {
this.id = id;
}

public String getName() {
return name;
}

public void setName(String name) {
this.name = name;
}

public String getEmail() {
return email;
}

public void setEmail(String email) {
this.email = email.toLowerCase();
}

public String getPassword() {
return password;
}

public void setPassword(String password) {
this.password = password; // TODO hash!
}

public Set getRoles() {
// if(roles == null){
// roles=new HashSet();
// }
return roles; // TODO handle lazy loading exception!
}

public void setRoles(Set roles) {
this.roles=roles; // TODO handle lazy loading exception!
}

}
ReneObermann/MyHealth= My Health

This project implements an example application using Spring Boot and AngularJS.
It serves as a starting point for my own projects.

== Technologies

* Java SE8
* Spring Boot
* Hibernate / JPA / HSQLDB
* AngularJS / Bootstrap / jQuery / Font-Awesome

== How To Run

To run this project, you need Java SE8 installed on your machine.
You can download it from https://www.oracle.com/technetwork/java/javase/downloads/index.html[Oracle].
After installing it, you can execute `mvn spring-boot:run` inside this project directory.
The application will start on port `8080`.

== How To Build

To build this project into an executable jar file, you can use `mvn clean package`.
The resulting file will be located under `target` directory.ReneObermann/MyHealth<|file_sepjsp.header.title=My Health App
jsp.header.menu.home=Home
jsp.header.menu.login=Login

jsp.footer.copyright=(c) Rene Obermann

jsp.error.badRequest=Bad Request (400)
jsp.error.unauthorized=Unauthorized (401)
jsp.error.forbidden=Forbidden (403)
jsp.error.notFound=Not Found (404)
jsp.error.internalServerError=Internal Server Error (500)

auth.login.failed=User or Password wrong!

user.create.form.title=Create New User Account
user.create.form.username=User Name:
user.create.form.email=E-Mail:
user.create.form.password=Password:
user.create.form.passwordConfirm=Confirm Password:

home.welcome.title=Welcoming You!
home.welcome.text=Welcoming text here…<|file_seppackage com.myhealth.server.config;

/**
*
* @author rene
*
*/
public class Config {

}
ReneObermann/MyHealth<|file_sep

{{ title }}

{{ message }}
{{ messageClass }}
{{ error }}
{{ errorClass }}

ReneObermann/MyHealth<|file_sep

=== Package Overview

==== Packages

===== org.springframework.boot.autoconfigure
Spring Boot auto configuration classes.

===== org.springframework.boot.context.embedded
Spring Boot embedded web server classes.

===== org.springframework.boot.context.properties
Spring Boot property source classes.

===== org.springframework.boot.logging
Spring Boot logging classes.

===== org.springframework.boot.test
Spring Boot testing classes.

===== org.springframework.context.annotation
Spring annotations for component scanning etc.

===== org.springframework.data.jpa.repository.config
Spring Data JPA repository configuration classes.

===== org.springframework.data.repository.support
Spring Data repository support classes.

===== org.springframework.web.bind.annotation
Spring MVC controller annotations.ReneObermann/MyHealth<|file_sep=Dark Blue

theme.primary=#008CBA;
theme.secondary=#f9f9f9;
theme.link=#008CBA;ReneObermann/MyHealth<|file_sep6th April, Monday

– Add Web Security Configuration:

Add security configuration class:

java
@Configuration
@EnableWebSecurity
public class SecurityConfig extends WebSecurityConfigurerAdapter {

}

Configure authentication:

java
@Override protected void configure(AuthenticationManagerBuilder auth)
throws Exception {
auth.inMemoryAuthentication().withUser("admin").password("123456")
passwordEncoder()
andRole("ADMIN").and().withUser("user").password("123456")
passwordEncoder()
andRole("USER");
}

@Bean public PasswordEncoder passwordEncoder() {
return new BCryptPasswordEncoder();
}

Configure authorization:

java
@Override protected void configure(HttpSecurity http)
throws Exception {
http.authorizeRequests()
and().formLogin().loginPage("/login").permitAll()
and().logout().permitAll();
}

Add login page:
– add `/login` route.
– create view template `/WEB-INF/views/login.jsp`
– add login form to template.
– add button link to login form in header fragment (`../fragments/header.jsp`).
– add css styles for login form (`style.css`).

Fix navigation bar:
– change main view template so that it uses angular-ui-bootstrap instead of bootstrap.
– update links to css/js files accordingly.
– add angular-ui-bootstrap dependencies (`angular-ui-bootstrap-tpls`, `angular-ui-router`) via maven.
– update angular modules accordingly.
– update navigation bar code so that it uses directives from angular-ui-bootstrap instead of bootstrap (`uib-navbar`, `uib-nav`, …).

7th April, Tuesday

Add user model:
Create user entity:
java
@Entity public class User {

}

Add properties:
id | username | password | enabled | roles | authorities |
— | — | — | — | — | — |
Long(id)|String(username)|String(password)|boolean(enabled)|Set(roles)|Set(authorities)|

Use jpa annotations for hibernate mapping:
java
@Id @GeneratedValue(strategy = GenerationType.IDENTITY)
private Long id;

@Column(nullable=false)
private String username;

@Column(nullable=false)
private String password;

@Column(nullable=false)
private boolean enabled;

Create role entity:
java
@Entity public class Role {

}

Properties:
id | name |
— | — |
Long(id)|String(name)|

Jpa annotations for hibernate mapping:
java
@Id @GeneratedValue(strategy = GenerationType.IDENTITY)
private Long id;

@Column(nullable=false)
private String name;

Add repositories:

UserRepository.java:

@Repository interface UserRepository extends JpaRepository{}

RoleRepository.java:

@Repository interface RoleRepository extends JpaRepository{}

Register entities & repositories with spring boot:

Enable jpa repositories via annotation on main app config class:
@EnableJpaRepositories(basePackages={“com.myhealth.server.repository”})

Enable jpa entities via annotation on main app config class:
@EnableEntityScan(basePackages={“com.myhealth.server.model”})

Register hibernate dialect with spring boot:

Define bean for dialect via annotation on main app config class (@Bean):
@Bean public LocalContainerEntityManagerFactoryBean entityManagerFactory() throws IOException {
LocalContainerEntityManagerFactoryBean em =
new LocalContainerEntityManagerFactoryBean();
em.setDataSource(dataSource());
em.setPackagesToScan(new String[] { “com.myhealth.server.model” });
JpaVendorAdapter vendorAdapter =
new HibernateJpaVendorAdapter();
em.setJpaVendorAdapter(vendorAdapter);
em.setJpaProperties(additionalProperties());
return em;
}

Define additional properties for dialect via annotation on main app config class (@Bean):
@Bean Properties additionalProperties(){
Mapp=new HashMap();
p.put(“hibernate.hbm2ddl.auto”,”update”);
p.put(“hibernate.dialect”,”org.hibernate.dialect.HSQLDialect”);
return p;
}

Implement registration functionality:

Create controller method to display registration form:
@RequestMapping(value=”/register”,method={RequestMethod.GET})
public ModelAndView registerForm(){
ModelAndView mv=new ModelAndView(“/register”);
mv.addObject(new User());
return mv;
}

Create controller method to process registration form submission:
@RequestMapping(value=”/register”,method={RequestMethod.POST})
public ModelAndView register(@Valid User user,BindingResult result){
if(result.hasErrors()){
ModelAndView mv=new ModelAndView(“/register”);
mv.addObject(user);
return mv;
}
try{
userRepository.save(user);
}catch(Exception e){
ModelAndView mv=new ModelAndView(“/register”);
mv.addObject(“error”,”Registration failed!”);
return mv;
}
return new ModelAndView(“redirect:/login?success”);
}

Update security configuration so that registration path is not secured anymore and does not require authentication anymore:

http.authorizeRequests().antMatchers(“/register”).permitAll();

Update security configuration so that users without authorities cannot access any path except “/login”:
http.authorizeRequests().anyRequest().hasAnyAuthority();

Update security configuration so that users without authorities cannot access “/login”:
http.authorizeRequests().antMatchers(“/login”).permitAll();

Implement login functionality:

Configure login success handler so that we redirect users back to homepage when they log in successfully and show them a success message if there was one added during login request processing:

public LoginSuccessHandler successHandler(){
SimpleUrlAuthenticationSuccessHandler handler=new SimpleUrlAuthenticationSuccessHandler();
handler.setDefaultTargetUrl(“/home”);
handler.setAlwaysUseDefaultTargetUrl(true);
handler.setUseReferer(true);
return handler;
}

Configure authentication failure handler so that we redirect users back to login page when they fail logging in and show them an error message if there was one added during login request processing:

public AuthenticationFailureHandler failureHandler(){
SimpleUrlAuthenticationFailureHandler handler=new SimpleUrlAuthenticationFailureHandler();
handler.setDefaultFailureUrl(“/login?error=true”);
handler.setUseReferer(true);
return handler;
}

Add messages from request attributes (“success”, “error”) to model attribute (“message”):
@RequestMapping(value={“/home”},method={RequestMethod.GET})
public ModelAndView home(Model model){
model.addAttribute(getMessageAttributeFromRequest(request));
model.addAttribute(getErrorAttributeFromRequest(request));
model.addAttribute(new HomeViewModel());
ModelAndView mv=new ModelAndView(“/home”,model.asMap());
mav.setViewName(mv.getViewName());
return mav;
}

protected Object getMessageAttributeFromRequest(HttpServletRequest request){
Object o=request.getAttribute(WebAttributes.AUTHENTICATION_SUCCESS);
if(o!=null && o instanceof MessageStatus){
MessageStatus status=(MessageStatus)o;
return status.getMessage();
}
return null;
}

protected Object getErrorAttributeFromRequest(HttpServletRequest request){
Object o=request.getAttribute(WebAttributes.AUTHENTICATION_FAILURE_KEY);
if(o!=null && o instanceof MessageStatus){
MessageStatus status=(MessageStatus)o;
return status.getMessage();
}
return null;
}

Add translations for messages displayed after successful or unsuccessful logins:

Test registration functionality locally by starting server locally again and registering some test accounts via web browser.

Test registration functionality remotely by starting server remotely again and registering some test accounts via web browser.<|file_sep/* global angular */
(function () {
'use strict';

angular.module('myApp').config(['$routeProvider', '$locationProvider',
function ($routeProvider,$locationProvider) {

$routeProvider.when('/', { templateUrl : 'views/home/home.tpl.html' });

$routeProvider.when('/about', { templateUrl : 'views/about/about.tpl.html' });

$routeProvider.otherwise({ redirectTo : '/' });
}]);
}());ReneObermann/MyHealth<|file_sep*** Settings ***

Library SeleniumLibrary
Resource resources/Selenium.robot

*** Variables ***
${BROWSER} Chrome
${URL} https://www.google.de/

*** Test Cases ***
Search Google For "Selenium"
Given I open "${URL}" using "${BROWSER}"

Fill search field with text "Selenium"

Push search button

Switch focus away from search field

Push search button again

Pick search result number one

Close browser window ReneObermann/MyHealth master

merge/remove-jquery-from-webapp-deployment-package-in-order-to-make-the-project-a-real-single-page-application-and-add-tests-for-it -> master

merge/remove-jquery-from-webapp-source-code-and-add-tests-for-it -> master

Hotfix Branches

===============

hotfix/create-test-suite-in-order-to-test-running-of-selenium-on-github-actions-ci-server

Hotfix Branch Merges Into Master Branch

========================================

merge/create-test-suite-in-order-to-test-running-of-selenium-on-github-actions-ci-server -> master

Release Branches

================

release/v0_0_1_20210406_0954

Pull Requests Merged Into Master Branch From Feature And Hotfix Branches With Merge Commit Messages Referring To The Respective Feature Or Hotfix Description In The Title Of The Pull Request That Created The Feature Or Hotfix Branch For Which The Merge Was Made Into Master By Using Semantic Commit Messages Following The Convention Proposed At https://www.conventionalcommits.org/en/v1.0 . Thereby Each Release Has Been Created By Tagging A Merge Commit On Master With A Version Number Following Semantic Versioning And Conventional Commits SemVer Specification At https://semver.org/. Each Release Contains All Features And Hotfixes Made Since Last Release As Well As Any Breaking Changes Made Since Then Also Including Themself If They Are Part Of That Release . Every Release Has Been Released Via GitHub Releases At https://github.com/ReneObermann/my-health/releases . After Each Release All Unmerged Feature And Hotfix Branches Have Been Deleted Except For Those Which Have Been Merged Into Master Before But Have Still Not Yet Been Included In Any Release . Every Merge Commit Made On Master Has Been Documented Here By Copying Its Description From GitHub Pull Request It Was Made Via Directly Below Its Reference Here .

Merge pull request #4 from ReneObermann/release/v0_0_1_20210406_0954 into master

Merge pull request #6 from ReneObermann/hotfix/create-test-suite-in-order-to-test-running-of-selenium-on-github-actions-ci-server into master

Merge pull request #7 from ReneObermann/hotfix/create-test-suite-in-order-to-test-running-of-selenium-on-github-actions-ci-server into release/v0_0_1_20210406_0954

Merge pull request #8 from ReneObermann/hotfix/create-test-suite-in-order-to-test-running-of-selenium-on-github-actions-ci-server into release/v0_0_1_20210406_0954

Merge pull request #9 from ReneObermann/hotfix/create-test-suite-in-order-to-test-running-of-selenium-on-github-actions-ci-server into release/v0_0_1_20210406_0954

Merge pull request #10 from ReneObermann/hotfix/create-test-suite-in-order-to-test-running-of-selenium-on-github-actions-ci-server into release/v0_0_1_20210406_0954

Merge pull request #11 from ReneObermann/hotfix/create-test-suite-in-order-to-test-running-of-selenium-on-github-actions-ci-server into release/v0_0_1_20210406_0954

Merge pull request #12 from ReneObermann/hotfix/create-test-suite-in-order-to-test-running-of-selenium-on-github-actions-ci-server into release/v0_0_1_20210406_0954

Merge pull request #13 from ReneObermann/hotfix/create-test-suite-in-order-to-test-running-of-selenium-on-github-actions-ci-server into release/v0_0_1_20210406_0954

Merge pull request #14 from ReneObermann/hotfix/create-test-suite-in-order-to-test-running-of-selenium-on-github-actions-ci-server into release/v0_0_1_20210406_95