This week Terrence Barr reports from the Sun Tech Days in Frankfurt, Germany and Roger Brinkley talks about his time at FOSS/IN in Bangalore, India and the Sun India Tech Days. You are invited to take a new survey and Terrence interviews Michael Samarin from FUTURICE.
Java Mobility And Micros
2008-09-07 22:19:38 laksoy
[Reply | View]
Java ME has become a popular option for creating games for cell phones, as they can be emulated on a PC during the development (evden eve nakliyat in my language)stage and easily uploaded to phones. This contrasts with the difficulty of developing, testing, and loading games for other special gaming platforms such as those made by Nintendo, Sony, Microsoft, and others, as expensive system-specific hardware and kits are required.
Java ME devices implement a profile. The most common of these are the Mobile Information Device Profile aimed at mobile devices(estetik in my language), such as cell phones, and the Personal Profile aimed (saç ekimi in my language)at consumer products and embedded devices like Set-top boxes and PDAs.
Profiles are subsets of configurations, of which there are currently two: the Connected Limited Device Configuration and the Connected Device Configuration.
good article
2008-09-04 05:34:14 units
[Reply | View]
HSQLD problem
2008-04-29 05:42:22 javaneto
[Reply | View]
HSQLD is a mature, high-performant database written in Java. It is used in several high profile popular commercial and open source products like Open Office 2.0 (Office productivity suite; competitor of MS Office), JBoss (Application Server), JFox (Application Server), Jonas (Application Server), Mathemetica, Hibernate (ORM), Jira (Defect Tracking), TrackStudio (Defect Tracking), C-JDBC (Database Clustering) etc.
It is a lightweight, embeddable database which eliminates the challenge of separate installation and configuration for the database component as with other databases like Oracle, SQL Server or MySQL.
The database is available as SQL scripts which makes it very easy to debug it, manually inspect and even modify the data.
It is tightly integrated with Java, making is very easy to use in Java applications. For example it supports Java stored procedures, functions and Triggers. 95% of JDBC interface is supported with full JDBC 2 DatabaseMetaData and ResultSetMetaData, batch statement and scrollable ResultSet functionality.
It supports standard SQL syntax which will make it easy for you to migrate to other databases down the road, should you want to. It supports disk tables upto 8GB and text tables upto 2GB which should be sufficient for most projects.
It can be used from applets, jar files, read-only media like CD, webstart and embedded applications. Did I mention that it is free and comes with source code?
I used it for several high-profile client projects with astounding success and highly recommend it. Two web application I developed for Invitrogen with HSQLDB as backend are:
EvoTrack Online - EvoTrack Online is a secure, online tool to track your custom antibody project. This is a complimentary service Invitrogen offers to all Custom Antibody customers.
EvoZone - EvoTrack Custom Library Services. EvoZone (internal name) is actually an application developer which allows rapid development of custom web based applications. It also can seamlessly integrate with external application and provides unified authentication & entitlements services from a central console.
The present text-book is a new-modeling and rewriting of Swinton's
_Word-Analysis_, first published in 1871. It has grown out of a large
amount of testimony to the effect that the older book, while valuable as a
manual of methods, in the hands of teachers, is deficient in practice-work
for pupils.
This testimony dictated a double procedure: first, to retain the old
_methods_; secondly, to add an adequate amount of new _matter_.
Accordingly, in the present manual, the few Latin roots and derivatives,
with the exercises thereon, have been retained--under "Part II.: The Latin
Element"--as simply a _method of study_.[1] There have then been added, in
"Division II.: Abbreviated Latin Derivatives," no fewer than two hundred
and twenty Latin root-words with their most important English offshoots. In
order to concentrate into the limited available space so large an amount of
new matter, it was requisite to devise a novel mode of indicating the
English derivatives. What this mode is, teachers will see in the section,
pages 50-104. The author trusts that it will prove well suited to
class-room work, and in many other ways interesting and valuable: should it
not, a good deal of labor, both of the lamp and of the file, will have been
misplaced.
To one matter of detail in connection with the Latin and Greek derivatives,
the author wishes to call special attention: the Latin and the Greek roots
are, as key-words, given in this book in the form of the _present
infinitive_,--the present indicative and the supine being, of course,
added. For this there is one sufficient justification, to wit: that the
present infinitive is the form in which a Latin or a Greek root is always
given in Webster and other received lexicographic authorities. It is a
curious fact, that, in all the school etymologies, the present indicative
should have been given as the root, and is explicable only from the
accident that it is the key-form in the Latin dictionaries. The change into
conformity with our English dictionaries needs no defense, and will
probably hereafter be imitated by all authors of school etymologies.
In this compilation the author has followed, in the main, the last edition
of Webster's Unabridged, the etymologies in which carry the authoritative
sanction of Dr. Mahn; but reference has constantly been had to the works of
Wedgwood, Latham, and Haldeman, as also to the "English Etymology" of Dr.
James Douglass, to whom the author is specially indebted in the Greek and
Anglo-Saxon sections.
As mentioned, URL and URLConnection rely on protocol handlers which must be present, otherwise an Exception is thrown. This is the major difference with URIs which only identify resources, and therefore don't need to have access to the protocol handler. So, while it is possible to create an URI with any kind of protocol scheme (e.g. myproto://myhost.mydomain/resource/), a similar URL will try to instantiate the handler for the specified protocol, if it doesn't exist an exception will be thrown.
By default the protocol handlers are loaded dynamically from the default location. It is, however, possible to add to the search path by setting the java.protocol.handler.pkgs system property. For instance if it is set to myapp.protocols, then the URL code will try, in the case of http, first to load myapp.protocols.http.Handler, then, if this fails, http.Handler from the default location.
like you said..
2008-03-13 07:11:04 javaneto
[Reply | View]
Well,as you pointed in your story, it's difficult to find a way from this situation. I'm crossing fingers for everybody who is in this situation. Good luck!.
java.net RSS Feeds
