OSGi , Spring OSGi and the server-side. Part 4
Sunday, 8 July 2007
Now , I want to tell you about server-side of OSGi technology.
Nowadays, better support of server-side gives Eclipse Equinox OSGi framework.
From a code point of view, Equinox is an implementation of the OSGi
R4 core framework specification, a set of bundles that implement various optional OSGi services and other infrastructure for running OSGi-based systems.
More generally, the goal of the Equinox project is to be a first class OSGi community and foster the vision of Eclipse as a landscape of bundles. As part of this, it is responsible for developing and delivering the OSGi framework implementation used for all of Eclipse. In addition. the project is open to:
- Implementation of all aspects of the OSGi specification (including the MEG and VEG work)
- Investigation and research related to future versions of OSGi specifications and related runtime issues
- Development of non-standard infrastructure deemed to be essential to the running and management of OSGi-based systems
- Implementation of key framework services and extensions needed for running Eclipse (e.g., the Eclipse Adaptor, Extension registry) and deemed generally useful to people using OSGi.
Server-Side Equinox
Equinox can be used on the server to serve up static content and to run servlets or JSPs. In each of these cases you need to setup an HTTP server and then configure it with the appropriate content. There are two basic ways of running an HTTP server in Equinox;
Follow the steps for the configuration best suited to your scenario then return here to write your bundle based web application.
HintEmbed a server in Equinox is the easiest configuration to setup and run. This will allow you to do all your development and debugging. Only when you go to production or in special circumstances will you need to embed Equinox in an existing servlet container.
Posted byEugene at 05:01 1 comments
Rethinking JSF - The Real Problem. By Joseph Ottinger
Saturday, 7 July 2007
This article is worth to look at. The main problem that discussed there is that JSF, for a component framework, has so few components.
It is hard to disagree with that.
"So... where are the login box components? Where are the search box components? Where are the data input components? Where's the ability to manage "pretty URLs?" ("Pretty URLs" are also known as bookmarkable URLs, or search-engine-friendly URLs.) Where is the data flow? Where's the conversational state?
There's absolutely nothing in JSF that prevents these things from being made, and some groups (vendors, open source groups) have already made some of them - frameworks and implementations like Seam, IceFaces, RichFaces, Tomahawk, NetAdvantage, and others. For others, code is readily available in books like "JSF: The Complete Reference" (Schalk, Burns), "JSF In Action" (Mann), and "Core JSF" (Geary). Some elements are even available on the web (for example, how to manage pretty URLs). There are also sites with lots of JSF information: IBM developerWorks, Java.sun.com, www.jsfcentral.com, www.jsftutorials.net, and TheServerSide itself. "
"Advice for new component authors: stop reinventing the wheel! Everyone has a tab panel, a menu component, a spinner, a drag-and-drop mechanism. It's been done. While perhaps newer and better ways to do things will always be welcomed, aiming for a "me-too" implementation doesn't help propagate the technology in any real way. What JSF needs is a set of components that use interfaces as models, along with a "standard implementation" of those interfaces that can be replaced at runtime with specific functionality. Along with this set of components, documentation that addresses the learning curve would be welcomed."
Full article
Posted byEugene at 06:55 1 comments
Ajax Experience: What's interesting for Java developers?
"The Ajax Experience, scheduled for July 25-27 2007 in San Francisco, has a lot of great sessions of interest to Java developers - whether you're following JSF, GWT, Struts, or even hand-coding your client-side UIs yourself. The Ajax Experience caters to the technology behind Web 2.0 - you should check it out.
Topical tracks include architecture, performance, design and effects, and specific frameworks. Speakers include framework developers like Brad Neuberg (Dojo), Patrick Lightbody (Struts2), Joe Walker (DWR), and more. Specific sessions of interest to Java developers include "Flash: Strengths vs. Weaknesses and How to Best Utilize it in Projects," by Geoff Stearns, a Youtube engineer; Advanced Prototype usage (Prototype is the underlying toolkit used by many Ajax frameworks); Continuations in Javascript; Advanced Web Security with Joe Walker, and more.
Of course, these are only the tip of the iceberg for Ajax developers.
So what makes this conference useful? Well, consider: for most users and applications, the web interface is the primary (or even only) point of contact. The back end may be elegant, incredibly fast, amazingly efficient, but with a clunky interface, nobody will care. The killer applications today tend to focus on the user experience: useful menus, dynamic behavior that caters to the way users want to use the application.
With a few rare exceptions, the way people make their application interfaces sing today is with Ajax, rich client interfaces that offer interactivity and rapid response to users.
The Ajax Experience is a great way for Java developers to leverage this technology, whether as experts or as people needing introduction to the concepts, whether you need to understand how the basic architecture works or if you need to optimize how your application already leverages the technology.
What stands out to you in the Ajax Experience?"
By TheServerSide.COM
Posted byEugene at 06:53 0 comments
JSR-275 - Units and Measures for Java 7 - draft terminates soon
Friday, 6 July 2007
I really interested in what it would be? And how it would be implemented?
This is what they say:
"Java developers who work with physical quantities (such as developers in the scientific, engineering, medical, and manufacturing domains) need to be able to handle measurements of these quantities in their programs. Inadequate models of physical measurements can lead to significant programmatic
errors. In particular, the practice of modeling a measure as a simple number with no regard to the units it represents creates fragile code. Another developer or another part of the code may misinterpret the number as representing a different unit of measurement. For example, it may be unclear whether a person's weight is expressed in pounds, kilograms, or stones.
Developers must either use inadequate models of measurements, or must create their own solutions. A common solution can be safer and can save development time for domain-specific work. This JSR proposes to establish safe and useful methods for modeling physical quantities."
JSR-275 "Measures and Units" Early Draft Public Review terminates soon (July 8). Your comments/feedback are important to us (the latest version 0.8 is available here).
The JSR-275 should be a major enhancement for Java 7 by providing "strong" typing (through class parameterization) and easy internationalization of Java programs (preventing conversion errors). The reference implementation is provided by the JScience project under BSD License.
Let's wait and will take a look when all will be done.
Posted byEugene at 00:57 0 comments
WhoDoes, free web-based project management software
Monday, 2 July 2007
GotThingsDone.comhas released WhoDoes, a new intuitive web-based project management software developed with Ruby on Rails.
Whodoesis suitable both for firms and professionals that have to plan and manage various projects of diverse complexity, where a lot of people, united or distributed anywhere, have to be coordinated and have to collaborate with tracking the advancement of the developed activities.
WhoDoes is designed to assist Project Managers and team members in the planning and management of projects with varying complexities.
It makes managing of complex projects easy, and facilitates the convenient planning of short-term small activities.
The major hitch in project management is making all the team members aware of what they have to do daily, so a successful project management tool must first of all answer the following question: What do I have to do today?
WhoDoesis designed to manage activities and share real time information with all the team members, whether they are in the same office or distributed all over the World.
Among its key features:
- Web-based: WhoDoesis usable from every computer connected to the Internet. No installation is required, it's totally cross-platform and cross-browser.
- Easy to use: A simple and easy web application helps to reduce the time spent on project planning.
- Team co-ordination: WhoDoes has a control panel to communicate and collaborate with all team members anywhere, filling the communication gap between who plans and who works.
- Roles division: Roles and permissions are divided for each project user.
- Easy time tracking: Gives detailed real-time informations and time control on tasks, project times and delays, allowing project managers to manage delays at the right moment.
- Repository: A shared archive for project documentation, a common space where all the team members could share materials and find the last official version of the project documents.
WhoDoesis completely free to use. All the features included in this version will remain free even when chargeable versions come out in the future.Follow this link to register for a new WhoDoes account.
Posted byEugene at 01:18 1 comments