In 2012 Desktops ruled. In 2014 Smart Phones are the only game in town. Connect to your customers and business users with RWD, AWD, Ux re-design and software re-engineering.
Category: Software Development
Produce alone won’t grow a grocery business. Get ahead of the competition with great eCommerce apps and responsive web design for mobile devices.
Numbers don’t lie. Where do you stand? Are you ready for Tsunami?
It might surprise you to find out that sending email using Gmail SMTP can sometimes create an issue for developers and cause them to spend lot of time finding a solution. If you have encountered this issue, there are few important verifications required before you can resolve the problem.
1. UserDefaultCredentials = False, must always appear before Credentials = new System.Net.NetworkCredential. If you insert this below Credentials, it will clear the authentication object and wait for new authentication parameters. Add UserDefaultCredentials before supplying authentication credentials and you will solve this problem.
2. Gmail supports two PORTS for sending an email, 587 and 465. If you trying to send using System.Net.Mail, it will not work with PORT 465, because System.NET.Mail only supports Explicit SSL. You can get more details on Explicit and Implicit SSL from http://blogs.msdn.com/b/webdav_101/archive/2008/06/02/system-net-mail-with-ssl-to-authenticate-against-port-465.aspx, if you need more information. Use port 587, rather than 465 so you do not experience an error, like connection timeout etc.
3. If you have a Google premium account, e.g., name@yourdomain.com, and you don’t have enough rights to allow other applications to send email using your email ID and password, you will need to employ a 2-step verification process so that other apps can send email using your authentication. You should also consider contacting your Administrator to get permission to establish and change settings and allow other application to send email with your authentication. If premium account authentication doesn’t work try a gmail ID like this: name@gmail.com. That should do the trick.
The Jenkins tool is an open source Continuous Integration tool which is written in Java, and runs in a servlet container like Apache Tomcat. It can be used to build software written in various languages such as Java, .Net, PHP, C++ etc. This open-source, free software is available under MIT License.
According to a global survey from CIO Strategic Marketing Services and Triangle Publishing Services, data loss and other security breaches related to mobile devices, was a real concern. When you consider Mobile Application Development services be sure you go with an IT partner who is experienced and skilled in mobile application security compliance.
If you have worked on a software development team, you will recognize these scenarios:
- You have a large team of engineers developing a software application. While committing the code in the repository, one of the developers forgets to commit one or two files. When other team members take the repository updates, they find problems in the code due to the missing file changes, and they have to spend a long time debugging the problems.
- Your engineering team is developing a software product. Your Business Analysis team needs frequent updates of the code to validate the changes or demonstrate new features to the customers. Preparing a new build and deploying it on the staging server for a BA team takes a significant amount of a developer’s valuable time.
Every designer and developer knows that user input Validation is a vital part of development for any application. Since the inception of the various MVC frameworks like Struts, Spring, JSF etc., the method of implementing validation has been included in application design considerations. These frameworks set the standards for implementing validation by providing the necessary supporting classes, and certainly, having clean design for validation has its benefits with respect to application maintenance.Prior to the release of version 3.0 of Spring, validation implementation required that the validator class is registered using a Spring configuration XML file. In addition, developer had to validate the fields and ensure error registration using ValidationUtils in the validate() method of the validator class. After the introduction of annotations in Spring 3.0, implementation of validation was simpler and cleaner. Developers can reduce the code by using the Hibernate Validator framework along with Spring. As of this writing, the latest version of the Hibernate Validator Framework is 5.0, which is the reference implementation of JSR-303). The following illustrates the implementation of constraints and validation using JSR-303 annotations:
JAR Dependencies: You’ll need to put the JAR files from Hibernate Validator Framework in the application classpath, which is WEB-INF/lib in a Java Web Project. Hibernate Validator 5.0 ships with a number of various JARs. While some are optional, the following are required JARs for validation implementation.
hibernate-validator-5.1.0.Final
validation-api-1.1.0.Final
classmate-1.0.0
jboss-logging-3.1.3.GA
Annotate model properties: Once you have entered the above JARs in the classpath, you can use the annotations provided by them. The following is an example of a model class where you would need to annotate the properties with required constraints. Note how @Size and @NotEmpty are used.