Skip to main content

Why Java?




The Java 2 Enterprise Edition (J2EE) architecture and platform is a powerful open source vendor providing a platform independent, object-oriented, distributed framework for developing and deploying robust and secure enterprise applications and solutions.  Furthermore, it has huge enterprise support from Sun Microsystems and now Oracle.

Some of the Java technologies we have used to deliver our projects so far are:


GWT, APACHEWICKET,JQUERY,MOOTOOLS,HIBERNATE,SPRING,STRUTS,J2EE

Java Platforms – Java 2 Enterprise Edition (J2EE) and Java 2 Standard Edition (J2SE)

Web Frameworks – for web applications, we have delivered projects using the Google Web Toolkit (GWT), Wicket, Struts, Java Server Faces (JSF), Java Server Pages (JSP) and Servlets.

Persistence Layers – we use Hibernate and Enterprise Java Beans (EJB) to deliver powerful persistence with databases.
Layered Java/J2EE application platforms – The Spring framework, with it’s powerful Dependency Injection (DI),  is used for development of a layered architecture and easily configurable code.

Web Services – Java has recently integrated excellent support for Web Services Support and for Service Oriented Architecture (SOA)

AJAX – the demands of some applications require Asynchronous JavaScript and XML (AJAX) to provide Rich Web Applications. We utilise different JavaScript frameworks to achieve our clients’ goals – including some powerful libraries such as MooTools and JQuery.
To support our Java efforts, we use the latest servers and application servers which serve our purpose best including:
APACHE, JBOSS,GLASSFISH,IBM(WEBSPHERE),TOMCAT,APACHE DERBY

Comments

Post a Comment

Popular posts from this blog

Google re-branded the support Android libraries to AndroidX

It is important to note, you cannot mix AppCompat and Jetpack in the same project. You must convert everything to use Jetpack if you want to upgrade. The support library artifacts are being deprecated and all future development is going into AndroidX , so there's no avoiding this migration. Alan Viverette sums this up nicely: “There won’t be a 29.0.0, so Android Q APIs will only be in AndroidX” The stable release of 28.0.0 will be the final feature release packaged as android.support . All subsequent feature releases will only be made available as androidx-packaged artifacts. Below tips will give you a clearer transition path. The current version of AppCompat (v28.x) is exactly the same as AndroidX (v1.x). In fact, the AppCompat libraries are machine generated by changing maven coordinates and package names of the AndroidX codebase. For example, android.support.v7.app.AppCompatActivity is now androidx.appcompat.app.AppCompatActivity For a complete listi
Post a Comment
Read more

Android Beginners Guide

                                                                                                               Android Operation System: Android is an operating system based on Linux with a Java programming interface. It provides tools, e.g. a compiler, debugger and a device emulator as well as its own Java Virtual machine (Dalvik Virtual Machine - DVM). Android is created by the Open Handset Alliance which is lead by Google. Android uses a special virtual machine, e.g. the Dalvik Virtual Machine. Dalvik uses special bytecode. Therefore you cannot run standard Java bytecode on Android. Android provides a tool "dx" which allows to convert Java Class files into "dex" (Dalvik Executable) files. Android applications are packed into an .apk (Android Package) file by the program "aapt" (Android Asset Packaging Tool) To simplify development Google provides the Android Development Tools (ADT) for Eclipse. The ADT performs automatically the conversion f
2 comments
Read more

Android Pi migration(28 API support)

I am here to give some inputs on android PI migration. .  Apps must target at least API level 28 to ensure it is built on the latest APIs optimized for security and performance . From August 2019, new apps must target at least Android 9.0 (API level 28) . The objective here is to make sure that your existing app works as-is on Android 9. Because some platform changes might affect the way your app behaves, some adjustments might be necessary, but you do not need to use new APIs or change your targetSdkVersion. Android Service Problem On Oreo, startService() will throw IllegalStateException. This can be fixed by changing it to startForegroundService(). but it also stops the service immediately if you don’t bind to the Notification with Service.startForeground() within 5 seconds. For other background service we decided to use the WorkManager . Implementation: Since we have minSdkVersion 19, We migrated to workmanger for scheduled tasks and we still use JobIntentSer
1 comment
Read more