|
ManningPublications's Profile
|
|
Manning's focus is on computing titles at professional levels. We care about the quality of our books. We work with our authors to coax out of them the best writing they can produce. We consult with technical experts on book proposals and manuscripts, and we may use as many as two dozen reviewers in various stages of preparing a manuscript. The abilities of each author are nurtured to encourage him or her to write a first-rate book. |
|
|
ManningPublications's Articles (91)
|
|
|
|
|
How to test OSGi Applications?
When you're testing OSGi bundles, each of these types of testing requires a different approach—different from the other phases and also different from how you'd do similar testing for an application intended to run on a JEE server or standalone. We'll start by discussing unit testing, since that's the simplest case in many ways. We'll then show you some tools and strategies that we hope you'll find useful for integration and system testing.
Blueprint and Service Dynamism in OSGi
OSGi is a dynamic environment. Stopping a bundle fragment removed translations, and stopping and starting bundles made special offers appear and disappear. This dynamism is amazingly powerful and allows OSGi applications to do things that aren't possible for conventional applications.
Writing an OSGi Web Application
In Java EE, the Servlet and Java Server Pages models have provided the basic building blocks for Java web applications for many years. OSGi Web Applications are a standardized OSGi version of JEE web applications. An OSGi web bundle is very similar to a JEE WAR, except that it also gets the benefits of operating in an OSGi framework. Enterprise OSGi web bundles are known as WABs. (In contrast to WARs, which are Web ARchives, WABs are Web Application Bundles.)
What is Model View Presenter (MVP) in GWT Application?
One of the main selling points of GWT is that it allows you to use an industry-grade language, with an industry-grade set of tools, to build...well...industry-grade web apps. But, as with any large scale development project, you can easily paint yourself into a corner. Far too many times when building GWT-based apps, we find ourselves slinging code wherever necessary to make the app work, and (sometimes more importantly) look good. Fortunately, there is a well known solution to this problem: build your applications based on the model-view-presenter (MVP) paradigm.
Code Splitting in GWT
Another common engineering issue was how to decrease the load time of the application. It is common for a feature full GWT application to approach a megabyte in size. With broadband, this is generally a fast download, but at the same time users have higher expectations that they did with their 56K modem. Users now judge the speed of your application in hundreds of milliseconds and not seconds. If your application takes a full second to start up, it may be considered as being sluggish. So how can you decrease the start time?.This is where code splitting comes in. If you can cut your code into multiple segments, you can kill two birds with one stone. A smaller initial download means faster startup, and loading less-often accessed code only when it loads means smaller total downloads.
|
|
|
|
