today's article is about adding namespaces to your XML document using Java and Dom4j, so let's get started...

First of all we need an instance of the Dom4j factory, here is how we do it...

//Get an instance of the dom4j document factory
DocumentFactory factory = DocumentFactory.getInstance();

...next we create an element which is going to serve as the root element as well as a new xml document using the factory object.

//use the factory to create a root element
Element rootElement = factory.createElement("RootElement");
//use the factory to create a new document with the previously created root element
Document doc = factory.createDocument(rootElement);

Now we are ready to create our namespaces.

//create some dom4j namespaces that we like to add to our new document
Namespace namespace1 = new Namespace("xsd","http://www.w3.org/2001/XMLSchema#");
Namespace namespace2 = new Namespace("rdfs","http://www.w3.org/2000/01/rdf-schema#");
Namespace namespace3 = new Namespace("rdf","http://www.w3.org/1999/02/22-rdf-syntax-ns#");
Namespace namespace4 = new Namespace("owl","http://www.w3.org/2002/07/owl#");
Namespace namespace5 = new Namespace("some","http://some/other/namespace:-)#");

The last step we have to take is to add all the namespaces to the XML document.

//add the created namespaces to the document
doc.getRootElement().add(namespace1);
doc.getRootElement().add(namespace2);
doc.getRootElement().add(namespace3);
doc.getRootElement().add(namespace4);
doc.getRootElement().add(namespace5);

Finished! To check if everything worked as intended we're going to write the document to an XML file...

try {
//write the created document to an arbitrary file
FileOutputStream fos = new FileOutputStream( "files/output.xml" );

OutputFormat outformat = OutputFormat.createPrettyPrint();
XMLWriter writer = new XMLWriter(fos, outformat);
writer.write(doc);
writer.flush();

} catch (FileNotFoundException e) {
// catch exception
e.printStackTrace();
} catch (UnsupportedEncodingException e) {
// catch exception
e.printStackTrace();
} catch (IOException e) {
// catch exception
e.printStackTrace();
}

...if everything went fine we should end up with an XML file that looks like this:

<?xml version="1.0" encoding="UTF-8"?>

<RootElement xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:owl="http://www.w3.org/2002/07/owl#"
xmlns:some="http://some/other/namespace:-)#">

</RootElement>

So this is how you add namespaces to your xml document via Dom4j...have a nice day and stay tuned for more face-melting articles :o)...

Secondo me è una manovra per calmare le acque con i vari antitrust: volendo potrebbe farlo uscire come patch anche subito, invece sta aspettando volontariamente qualche mese. Molti si dicono preoccupati del fatto che con il supporto ODF in Office l'interesse dei governi e delle grandi istituzioni verso OpenOffice diminuirà, io invece penso che potrebbe succedere proprio il contrario (e secondo me anche Ballmer & Co. non sono così tranquilli).

Con Openoffice 3.0 alle porte il gap di funzionalità con Office si è ridotto di molto, oltretutto nell'ambito delle PA e degli uffici i programmi di videoscrittura e i fogli di calcolo vengono normalmente sfruttati per 10-20% delle loro caratteristiche, e in quel 10-20% openoffice non è inferiore di certo al cugino closed source. Eliminando di fatto uno dei pochi problemi che esistevano oggi, cioè quello della compatibilità di formato, ci si troverebbe nella situazione di dover scegliere fra una costosa suite closed source e una gratuita ma altrettando performante: a questo punto diventerebbe molto difficile per Microsoft, che già oggi sta perdendo mercato in questo settore, vincere la sfida.

I mesi di ritardo sull'uscita sono secondo me stati calcolati molto bene: le PA e le aziende (specialmente quelle medio-piccole che sono la maggioranza qui in Europa)  non aggiornano il loro software a ogni nuova release, ma sovente fanno le migrazioni saltandone 1 o anche 2, in pratica quando il prodotto smette di essere supportato o la nuova release introduce funzionalità insostituibili: ancora oggi infatti non è raro trovare Office XP o Office 2000 in molti uffici (anche di una certa dimensione); ora siccome il supporto esteso per Office 2000  terminerà nella prima metà del 2009 insieme a quello standard di Office 2003 ecco chiaro il perchè aspettare la metà del 2009 per uscire: le aziende e le PA (in italia ma credo anche all'estero) devono dovrebbero per legge utilizzare software aggiornato per un discorso legato alla sicurezza dei dati, quindi nel 2009 (sempre in teoria) tutti quelli che usano ancora Office 2000 dovrebbero migrare alla nuova versione, e anche chi usa Office 2003 avrà solo più le patch di sicurezza, metre tutto il resto diventerà a pagamento quindi potrebbe essere appetibile una migrazione. Ed ecco perchè farlo uscire dopo: cercheranno di sfruttare l'onda delle migrazioni da 2000/Xp/2003 a 2007 togliendo mercato a OpenOffice.

XML views of radio AOD availability

If you head over to bbc.co.uk/radio/aod/availability/:network.xml then you will get an XML file (updated every 3 hours) with details about what's available to listen to now and in the next 48 hours. So for example:

http://www.bbc.co.uk/radio/aod/availability/radio1.xml

Will give you data about Radio 1 data [obviously]. The file contains a bunch of metadata about the episodes including details of the stream URLs.

What you will notice is that we're not pointing you directly at the URLs for the audio instead we're directing you to our 'Media Selector' which we use to maintain the availability window. So if you follow the media selector link you will get back a lump of XML with details of the available media. By the way you'll want to use the /mediaSelection/media/@encoding = real. Ignore the MP3 that's a 'secure' stream used in iPlayer.

Programme schedules as XML, YAML, JSON and Text

Duncan has already written about his work to implement iCal views on the Radio Labs blog:

iCalendar is a standard for calendar data exchange. It is most notably used by Apple's iCal application, Microsoft's Outlook and Google Calendar, to import and export calendar information. We thought that some of the views in /programmes would also work well in the iCal format, so we have exposed a few for you to subscribe to, and play with.

These are available for your regular schedule and for genres [upcoming cricket programmes for example] and for individual programmes. For example:

Upcoming episodes of Eastenders
webcal://bbc.co.uk/programmes/b006m86d/episodes/upcoming.ics
Upcoming (New) episodes of Eastenders
webcal://bbc.co.uk/programmes/b006m86d/episodes/upcoming/debut.ics
Episodes of Eastenders available to watch again
webcal://bbc.co.uk/programmes/b006m86d/episodes/player.ics

In addition to iCal you can also get this data as plain text, XML, JSON or YAML. So the upcoming drama programmes as XML can be found here:

http://www.bbc.co.uk/programmes/genres/drama/schedules/upcoming.xml

Or the Radio 1 schedule as plain text as:

http://www.bbc.co.uk/radio1/programmes/schedules.txt

Artist pages as RDF

We're busy doing a load of work on the music site right now which will be launching really soon. When we do in addition to lots of HTML we'll also me making the data available for machines - including RDF. But if you are into this sort of thing here's a sneaky peak at what will be released:
[sourcecode language='xml']

xmlns:rdfs = "http://www.w3.org/2000/01/rdf-schema#"
xmlns:foaf = "http://xmlns.com/foaf/0.1/"
xmlns:mo = "http://purl.org/ontology/mo/"
xmlns:mf = "http://purl.org/ontology/mo/mf#"
xmlns:owl = "http://www.w3.org/2002/07/owl#"
xmlns:time = "http://www.w3.org/2006/time#"
xmlns:dc = "http://purl.org/dc/elements/1.1/"
xmlns:timeline = "http://purl.org/NET/c4dm/timeline.owl#"
xmlns:event = "http://purl.org/NET/c4dm/event.owl#">

Description of the artist Coldplay

Coldplay

Guy Berryman


Jon Buckland


Will Champion


Chris Martin

[/sourcecode]
We would really welcome your feedback on any of this.

And finally a bit of URL hackery...

Our decision to use opaque IDs for our programmes [episodes, series and programme brands] means that we can provide persistent URL - which is a good thing. The downside is that you can't guess the URL. To fix this you can now enter URLs like this:

www.bbc.co.uk/programmes/eastenders and you will be redirected to www.bbc.co.uk/programmes/a-z/by/eastenders/all

That's a disambiguation page for all programmes with Eastenders in the title. If however there's just one programme with that title, like for example www.bbc.co.uk/programmes/chrismoyles then you will be redirected to that brand page (www.bbc.co.uk/programmes/b006wkqb).

Photo: Data storage - old and new, by Ian-s. Used under licence.

Job Posted Link: Software Engineers, Job at Bangalore - Kasshku Information Technologies Pvt. Ltd

-2008-Jul-18 : Freshers Walk-in - Php, XML, JavaScript, HTML (Bangalore)

Job Posted Link: Freshers Walk-in - Php, XML, JavaScript, HTML, Job at Bangalore - vynco technologies

-2008-Jul-18 : Fresher Trainee Engineer (Mumbai)

Job Posted Link: Fresher Trainee Engineer, Job at Mumbai - I-Source Infosystems Pvt Ltd

-2008-Jul-18 : Fresher Game Tester (Navi-Mumbai)

Job Posted Link: Fresher Game Tester, Job at Navi-Mumbai - Indiagames Ltd

-2008-Jul-18 : Freshers Customer Service Professionals - Technical Support (Bangalore)

Job Posted Link: Freshers Customer Service Professionals - Technical Support, Job at Bangalore - SITEL India Limited

-2008-Jul-18 : Fresher Sales and Marketing Executive (Delhi)

Job Posted Link: Fresher Sales and Marketing Executive, Job at Delhi - Imfinity India Pvt Ltd

-2008-Jul-18 : Fresher Telecom Engineer (Maharastra, Rajasthan, Gujrath, M.P, A.P, Orissa, W.B, Karnataka, Tamil-Nadu, Kerala, SriLanka.( RF,RNO, BTS ))

Job Posted Link: Fresher Telecom Engineer, Job at Maharastra, Rajasthan, Gujrath, M.P, A.P, Orissa, W.B, Karnataka, Tamil-Nadu, Kerala, SriLanka.( RF,RNO, BTS ) - I-Source Infosystems Pvt Ltd

-2008-Jul-18 : Project Trainees (Bangalore)

Job Posted Link: Project Trainees, Job at Bangalore - Kasshku Information Technologies Pvt Ltd

-2008-Jul-18 : Web Publishing Executives (Pune)

Job Posted Link: Web Publishing Executives, Job at Pune - Reality Information Systems Pvt Ltd

-2008-Jul-18 : Freshers Implementation Executive (Bangalore)

Job Posted Link: Freshers Implementation Executive, Job at Bangalore - Relyon Softech Ltd

-2008-Jul-18 : Freshers Receptionist (Bangalore)

Job Posted Link: Freshers Receptionist, Job at Bangalore - Kasshku Information Technologies Pvt Ltd

-2008-Jul-18 : Fresher Game Designer (Mumbai)

Job Posted Link: Fresher Game Designer, Job at Mumbai - Indiagames Ltd

-2008-Jul-18 : Service Desk Co-Ordinator (Bangalore)

Job Posted Link: Service Desk Co-Ordinator, Job at Bangalore - Microland Ltd

-2008-Jul-18 : Wanted Project Trainees In Java&J2EE,DotNet(ASP.Net &C#) And Testing(Manual&Automation)! (Hyderabad)

Job Posted Link: Wanted Project Trainees In Java&J2EE,DotNet(ASP.Net &C#) And Testing(Manual&Automation)!, Job at Hyderabad - HughSoft

-2008-Jul-18 : Walk-in Software Developers [ 18th July and 19th July ] (Gurgaon)

Job Posted Link: Walk-in Software Developers [ 18th July and 19th July ], Job at Gurgaon - Tech Ray Solutions

-2008-Jul-18 : Walkin for J2EE and .NET freshers [ 26th - 27th July ] (Chennai)

Job Posted Link: Walkin for J2EE and .NET freshers [ 26th - 27th July ], Job at Chennai - Aavanor Systems Pvt Ltd.,

-2008-Jul-18 : Fresher Graduate Intern (Bangalore)

Job Posted Link: Fresher Graduate Intern, Job at Bangalore - INTEL INDIA

-2008-Jul-18 : Fresher Management Trainees (Pimpri, Pune)

Job Posted Link: Fresher Management Trainees, Job at Pimpri, Pune - Hindustan Antibiotics Limited

-2008-Jul-18 : Freshers Management & Marketing Walk-in (Bangalore)

Job Posted Link: Freshers Management & Marketing Walk-in, Job at Bangalore - HCL

-2008-Jul-18 : Fresher Software Engineer Trainee Walk-in (Mumbai)

Job Posted Link: Fresher Software Engineer Trainee Walk-in, Job at Mumbai - ACE Software Solutions

-2008-Jul-18 : Software Test Engineers (Hyderabad)

Job Posted Link: Software Test Engineers, Job at Hyderabad - D. E. Shaw India Software Pvt Ltd

-2008-Jul-17 : Fresher Interim Intern - Software Engineer (Hyderabad)

Job Posted Link: Fresher Interim Intern - Software Engineer, Job at Hyderabad - QUALCOMM CDMA Technologies (QCT)

-2008-Jul-17 : Fresher Graduate Engineer Trainee (Hyderabad - AP, India)

Job Posted Link: Fresher Graduate Engineer Trainee, Job at Hyderabad - AP, India - QUALCOMM CDMA Technologies

-2008-Jul-17 : Fresher QA - CAD Engineer (Hyderabad, AP-India)

Job Posted Link: Fresher QA - CAD Engineer, Job at Hyderabad, AP-India - QualCore Logic Ltd

-2008-Jul-17 : Business Development Support Executive (Ahmedabad)

Job Posted Link: Business Development Support Executive, Job at Ahmedabad - TatvaSoft

-2008-Jul-17 : Software Engineers with 0-1 years (Pune)

Job Posted Link: Software Engineers with 0-1 years, Job at Pune - MetrixLine India

-2008-Jul-17 : Fresher Field Application Engineer - Noida (Noida)

Job Posted Link: Fresher Field Application Engineer - Noida, Job at Noida - Sequence Design (I) Pvt Ltd

-2008-Jul-17 : Freshers Customer Service Representative (Mumbai)

Job Posted Link: Freshers Customer Service Representative, Job at Mumbai - i2c World Pvt Ltd

-2008-Jul-17 : Freshers Engineer / Trainee / ITI / Graduate (Rajkot)

Job Posted Link: Freshers Engineer / Trainee / ITI / Graduate, Job at Rajkot - Rajoo Engineers Ltd

-2008-Jul-17 : Fresher Testing Professionals (Bangalore)

Job Posted Link: Fresher Testing Professionals, Job at Bangalore - Tanyasolutions

venue:
no 96, vynco technologies,
airport road domlur
opp to indian oil petrol pump
Bangalore

Phone: 25354040 / 9844442925

More Details are Here

Just a quick post to see if anyone else out there who finds this article via Google or wherever is interested in solving some of the translations issues with InDesign by using XLIFF.  XLIFF is a standard XML-based format for storing translations, simplifying your translations workflow by making the actual containing format for the translations standard - and then having various software vendors implement import/export features to/from XLIFF.

Currently InDesign does not have any integration with XLIFF.  However, InDesign 4 is scheduled to have a great deal more XML support, and there is a possibility that we can get a workable XLIFF import/export workflow happening.  Anyone else interested?

As tecnologias criadas pelo World Wide Web Consortium (W3C) permite projetar e desenvolver websites suportados pela maioria dos navegadores e dispositivos atuais, além de fornecer compatibilidade futura com a evolução dos padrões e dos navegadores.

A prática dos Padrões Web (Web Standards) - também conhecidas como "Tableless" - é indicada em projetos web pois traz muitas vantagens e benefícios.

A utilização da semântica do HTML e da separação de design e conteúdo há uma diminuição dos custos de produção e manutenção, enquanto torna os sites mais acessíveis àqueles com necessidades especiais

O que fazemos

We'll give more details when its ready to go.

Some of the tech highlights:

We've migrated from acegi securit to spring security (pretty straightforward)

Carrying on with our hibernate model

Extending our previous architecture to be more lightweight and more OO-centric - use of worker and helper classes to decouple.

Use of XML to communicate between layers.

Anyone else have some pointers ideas for resources to check out? There are alot of technologies I need to read up on, of those mentioned on the site I only really know JavaScript and basic XML/XSLT but not the "flavours" they are using in the Firefox project.

Para poder usarlo se debe compilar la extención XML, ya que usa la clase XMLReader,  aunque la mayoria de los servidores ya vienen con la extención instalada.

Esta es la función:

    function xml2assoc($xml) {
      $assoc = null;
      while($xml->read()){
        switch ($xml->nodeType) {
          case XMLReader::END_ELEMENT: return $assoc;
          case XMLReader::ELEMENT:
            $assoc[$xml->name] = array('value' => $xml->isEmptyElement ? '' : xml2assoc($xml));
            if($xml->hasAttributes){
              $el =& $assoc[$xml->name][count($assoc[$xml->name]) - 1];
              while($xml->moveToNextAttribute()) $el['attributes'][$xml->name] = $xml->value;
            }
            break;
          case XMLReader::TEXT:
          case XMLReader::CDATA: $assoc .= $xml->value;
        }
      }
      return $assoc;
    }

Y luego solo se crea el objeto y se pasa como parámetro a la función:

$xml = new XMLReader();
$xml->open([XML file]);
$assoc = xml2assoc($xml);
$xml->;close();

Muy util.

Szakmai elvárások:

• HTML, DHTML, XHTML alapos ismerete
• CSS1, CSS2 alapos ismerete
• Szakmai angol megértése
   

Előnyt jelent:

• Javascript, XML, PHP tapasztalat
• Template engine (Pl. Smarty)
• Verzió kezelő alapos ismerete
• Csapatmunkában, specifikáció alapján önálló, koncentrált munkavégzés
• Proaktivitás, kreativitás
• Új technológiák megtanulására való hajlandóság
   

Amit kínálunk:

• Kiemelkedő bérezés
• Fiatal, dinamikus, ugyanakkor professzionális csapat
• Szakmai támogatás és tudásbázis a munkavégzéshez
• Folyamatos fejlődés, kihívások
• Nemzetközi karrierlehetőség
• Cafeteria rendszer
   

Munkaidő, helyszín:

• Modern, jól felszerelt iroda Budapest központjában
• Napi fix, nyolc órás munkaidő

laszlo_spiller@kellyservices.hu

Instead, of late, I've been doing some more playing in php. It's been awhile since I've really programmed in anger, so I'm sort of struggling with how to do it right - so let's document my intent:

PIE, my little php project, is designed to allow me to create a simple website which includes the odd bit of php. I've built a handful of websites that need very little update, customisation and certainly don't need a full on CMS and PIE is designed to make that a little easier.

I create the web pages as XML files (well, invalid XML files really - in fact, they're, so far, nothing but fauX ML files - though it wouldn't be too difficult to make them valid).

They contain:

<title>Title</title>
<summary>Summary</summary>
<body>Body text</body>

This is parsed and the elements extracted into a hash array which is then used in a PHP file which is the docuement template.

Optional elements are:

<template>template name</template> - in case a different template is needed.

<plugins>one,two,three</plugins> - a comma seperated list of PIE plugins to use.

Plugins I've written, include: markdown (ok, I lie, markdown isn't written by me, I just nabbed a copy of it and included it as part of pie) and contactform - generates a contact form (and uses some optional elements to help format it)

If you include a plugin then you can also include an element named for the plugin, this may contain extra elements, so, for example, with markdown:

<markdown>no</markdown> - this tells PIE to NOT use markdown for this one file. (As markdown is included automatically as a plugin, that's why you need this option)

<contactform>
<thankyou>Text to include in thank you message - displayed after form is filled in including <!--email--> the original email.</thankyou>
<sendto>emailaddress-tosendto.com</sendto>
</contactform>

Sendto is the sendto email address, the '-' is replaced with '@' by the plugin. Things to do:

<fields></fields> - list of fields to include in the form, not sure how best to handle this, I suspect something like:

<fields>

FieldName:fieldtype:maxlength*
</fields>

For text:

fieldname*:text:40 (asteriks indicate it is required)
fieldname:textarea:rows:cols (Row and column length)
fieldname*:select:default:option=a,option=b,option=c,option=d,option=e
fieldname*:date:M-D-Y (default value)

That should make the contactform much more useful.

Yang dibutuhkan adalah:

1. Apache Commons IO
2. Apache Commons Configuration 1.5
3. Apache Commons Logging
4. Apache Commons Lang 2.4
5. Apache Commons Collection

Banyak? Nggak juga kok. Sebenarnya itu file-file kecil dan semuanya bisa didownload dari website Apache Foundation.

Saya lebih seneng ngasih tutorial pakai source code. Langsung aja ya dibaca:

Main.java

/*
* To change this template, choose Tools | Templates
* and open the template in the editor.
*/
package belajardulu;

import java.io.InputStream;
import java.util.logging.Level;
import java.util.logging.Logger;
import org.apache.commons.configuration.ConfigurationException;
import org.apache.commons.configuration.XMLConfiguration;
import org.apache.commons.io.IOUtils;

/**
*
* @author Cherry
*/
public class Main {

/**
* @param args the command line arguments
*/
public static void main(String[] args) {
try {
// TODO code application logic here
String xml = "<?xml version=\"1.0\"?>\n" +
"<MethodCall>\n" +
"   <MethodID>" +
"       <Name>Name</Name>\n" +
"   </MethodID>\n" +
"   <TransactionInfo>\n" +
"       <AccountID>AccountID</AccountID>\n" +
"       <ProcCode>ProcCode</ProcCode>\n" +
"       <ChannelType>ChannelType</ChannelType>\n" +
"       <ReffNumber>ReffNumber</ReffNumber>\n" +
"       <TerminalID>TerminalID</TerminalID>" +
"   </TransactionInfo>\n" +
"   <TransactionID>\n" +
"       <STAN>STAN</STAN>\n" +
"       <DateTime>DateTime</DateTime>\n" +
"       <InstID>InstId</InstID>" +
"   </TransactionID>\n" +
"   <TransactionData>\n" +
"       <CustomerID>CustomerId</CustomerID>\n" +
"       <AdditionalData>AdditionalData</AdditionalData>\n" +
"   </TransactionData>\n" +
"</MethodCall>";

InputStream is = IOUtils.toInputStream(xml);

XMLConfiguration xc = new XMLConfiguration();
xc.load(is);
System.out.println(xc.getString("TransactionID.STAN"));
} catch (ConfigurationException ex) {
Logger.getLogger(Main.class.getName()).log(Level.SEVERE, null, ex);
}
}
}

Gimana? Gampang kan?

Saya jelasin:

1. Saya bikin variabel String diisi dengan XML
2. Saya bikin objek InputStream (diambil dari Apache Common IOUtils) dari XML tersebut
3. Saya bikin objek XmlConfiguration
4. Saya minta objek XmlConfiguration untuk meload XML dari InputStream
5. Saya baca isi field tertentu yang diinginkan dengan method getString()

Nb: sebenarnya library yang dibutuhkan adalah Apache Commons Configuration, tetapi ternyata Apache Commons Configuration membutuhkan rekan-rekannya.

Btw, selamat belajar.

http://weblogs.sqlteam.com/travisl/archive/2005/01/04/3931.aspx

Так вот оказывается реально существуют только платные варианты программ для редактирования этих файлов. Посидев полчаса, я накидал класс PHP для парсинга, редактирования и сохранения TMX файлов. Обозвал свое детище AtoL TmxEditor 0.01. Думаю, кому нибудь пригодится. Очень спешил, возможны баги.

Ссылка для скачивания

Uma linguagem ser tão extensa, ao meu ver, acaba tornando java um desafio no mínimo interessante.

Coloquei abaixo algumas siglas referente a java, pesquisadas na web em diversas fontes.

Caso você esteja lendo e diga, mas XML(por exemplo) eu vi quando tava aprendendo outro linguagem. Tudo bem, a idéia é que eu vi e conheci mais a fundo em java. Então tá na minha lista.

JDK: Java Developer Kit. É o kit de desenvolvimento Java oferecido gratuitamente pela Sun.

JRE: Java Runtime Enviroment. É o ambiente de execução Java oferecido gratuitamente pela Sun.

JVM: Java Virtual Machine - Máquina Virtual Java. É o programa que faz um .class java poder ser executado

J2ME: Java 2 Micro Edition. Conjunto de bilbiotecas para desenvolvimento voltado aos dispositívos móveis

J2SE: Java 2 Standard Editon. É o java padrão, utilizado para desenvolvimento desktop

J2EE: Java 2 Enterprise Edition. É um extensão ao J2SE para servidores, implementando várias bibliotecas para facilitar a computação distribuída, como os EJBs

JSP: Java Server Pages. É uma tecnologia para desenvolvimento de aplicações WEB semelhante ao PHP

XML: Extensible Markup Language. Linguagem como o HTML utilizada para armazenamento e troca de informações

EJB: Enterprise JavaBeans. Define um modelo para aplicações com servidores criando componentes reusávei

JCA: Java Connector Architecture - uma arquitetura desenvolvida de modo a facilitar a comunicacao entre servidores J2EE e EIS's.

JMS: Java Messaging System - uma arquitetura existe dentro do universo J2EE que permite troca de mensagens de maneira assíncrona.

MOM: Message Oriented Middleware - é o software que age como um Mediator na arquitetura de mensagens assíncronas.

MDB: Nao, nao é a extensao do banco de dados do Access. É Message-Driven-Bean, ou seja, um EJB capaz de processar mensagens assincronamente.

JDO: Java Data Objects - uma extensao sob o JSR-000012 que regula métodos de persistência de objetos Java em bancos de dados relacionais.

UML: Unified Modeling Language - uma linguagem utilizada durante o processo de análise e desenvolvimento de software capaz de traduzir requerimentos funcionais e nao-funcionais do sistema. (Tá muito suscinta essa descricao).

CORBA: Common Object Request Broker Arquitecture - uma arquitetura que possibilita o desenvolvimento de sistemas construídos em diversas linguagens distintas, atuar de maneira distribuída segunda um protocolo bem definido. O principal elemento que torna isso possível é o ORB (Object Request Broker).

IDL: Interface Definition Language - é a linguagem usada para definir interfaces de comunicacao na arquitetura CORBA.

JAR: Java ARchive - comprimir e criar arquivos "executáveis" em java

AWT: Abstract Window Toolkit - API para desenvolvimento de Janelas.

GUI: Grafic User Interface - São os tipos de interface geráficas para Usuários, nada muito intuitivo.. hehehe

RMI: Remote Method Invocation - Mas centrado em Sistemas distribuídos, semelhante ao CORBA.

POO: Programação Orientada a Objetos

JCE: Java Cryptography Extension. Extensão para utilização de criptografia utilizando providers que fornecem os algoritmos tipo DES, RSA e outros. A SUN tem o seu dentro da propria API SUNJCE, mas tem de outras empresas, como IBM e também alguns free, como o Bouncy Castle

E tem muito mais ainda, facelets, jsf, pojos, a lista é bem grandinha. Mas conforme avançar elas surgiram.

Fonte:

Wikipedia

siglas.com.br

Abraço,
Ederson Melo

While most blogging platforms automatically convert your posts into the language. a few tweaks can be made if you understand the language.  Both Wordpres.com and Typepad allow users to customize their page's CSS for a fee.  In case you completely missed the language expansion, here's a quick reference with definitions and quick start guides.

• XML stands for Extensible Markup Language.  XML differs from XHTML, HTML or CSS because it does not carry any information on how to display the data, therefore it must be combined with the CSS language. 
• HTML stands for Hypertext Markup Language.  HTML is the structure of text information within a document.  It also includes scripting, appearance and semantics of the document or web page.
• XHTML stands for Extensible Hypertext Markup Language.   It is often described as the intersection of HTML and XML. 
• CSS stands for Cascading Style Sheets.  CSS uses HTML and XHTML to communicate with a page as to how it is to be displayed.  CSS can be used to define fonts, sizes, colors, layout, proportion, etc. Using CSS makes your site infinitely more customizable.

The truth is, unless you are heavy into coding and site building, you probably don't need to know more than a simple definition of each language.  If you're looking to customize your site, look into the language your platform uses.  From there, you should be able to modify settings like column width, font type, font size, and background color.  Learning a language isn't for the faint of heart, but having a unique, custom site is worth it!

XQuery 1.0 was developed by the XML Query working group of the W3C. The work was closely coordinated with the development of XSLT 2.0 by the XSL Working Group; the two groups shared responsibility for XPath 2.0, which is a subset of XQuery 1.0. XQuery 1.0 became a W3C Recommendation on January 23, 2007.

"The mission of the XML Query project is to provide flexible query facilities to extract data from real and virtual documents on the World Wide Web, therefore finally providing the needed interaction between the Web world and the database world. Ultimately, collections of XML files will be accessed like databases".

XQuery can be used to:

• Extract information to use in a Web Service
• Generate summary reports
• Transform XML data to XHTML
• Search Web documents for relevant information

XQueryX is a near one-to-one mapping into XML of the formal grammar for the language. Given the complexity of the grammar, this makes XQueryX highly verbose, to the degree that it's nearly impossible for humans to read. Happily, machines -- which are the intended recipients of the language -- don't complain about such things. Listings 1 and 2 provide a comparison of a simple query expressed first in standard XQuery syntax and then in its XQueryX counterpart. Note the significant steroid-like bulk-up factor.
Listing 1. A simple query in standard syntax

				<bib>
 {
  for $b in doc("http://bstore1.example.com/bib.xml")/bib/book
  where $b/publisher = "Addison-Wesley" and $b/@year > 1991
  return
    <book year="{ $b/@year }">
     { $b/title }
    </book>
 }
</bib>

Listing 2 shows the XQueryX equivalent. I've omitted about three-quarters of the listing due to its length. The full listing, lifted directly from the XQueryX working draft, runs to 132 lines:
Listing 2. The Listing 1 query in XQueryX format (snippet)

				<?xml version="1.0"?>
<xqx:module xmlns:xqx="http://www.w3.org/2005/XQueryX" ... >
  <xqx:mainModule>
    <xqx:queryBody>
      <xqx:elementConstructor>
        <xqx:tagName>bib</xqx:tagName>
        <xqx:elementContent>
          <xqx:flworExpr>
            <xqx:forClause>
              <xqx:forClauseItem>
                <xqx:typedVariableBinding>
                  <xqx:varName>b</xqx:varName>
                </xqx:typedVariableBinding>
                <xqx:forExpr>
                  <xqx:pathExpr>
                    <xqx:argExpr>
                      <xqx:functionCallExpr>
                        <xqx:functionName>doc</xqx:functionName>
                        <xqx:arguments>
                          <xqx:stringConstantExpr>
                            <xqx:value>http://bstore1.example.com/bib.xml</xqx:value>
                          </xqx:stringConstantExpr>
                        </xqx:arguments>
                      </xqx:functionCallExpr>
                    </xqx:argExpr>
                    <xqx:stepExpr>
                      <xqx:xpathAxis>child</xqx:xpathAxis>
                      <xqx:nameTest>bib</xqx:nameTest>
                    </xqx:stepExpr>
                    <xqx:stepExpr>
                      <xqx:xpathAxis>child</xqx:xpathAxis>
                      <xqx:nameTest>book</xqx:nameTest>
                    </xqx:stepExpr>
                  </xqx:pathExpr>
                </xqx:forExpr>
              </xqx:forClauseItem>
            </xqx:forClause>
			...

doc("books.xml")

doc("books.xml")/bookstore/book/title

<title lang="en">Everyday Italian</title>
<title lang="en">Harry Potter</title>
<title lang="en">XQuery Kick Start</title>
<title lang="en">Learning XML</title>

doc("books.xml")/bookstore/book[price<30]

Path Expressions and Relationship to XPath

XQuery borrows path expressions from XPath. XQuery can be viewed as a generalization of XPath. Except for some obscure forms (mostly unusual "axis specifiers"), all XPath expressions are also XQuery expressions. For this reason the XPath specification is also being revised by the XQuery committee, with the plan that XQuery 1.0 and XPath 2.0 will be released about the same time. Example

XQuery Tools support

db2expln

The db2expln tool describes the access plan selected for SQL and XQuery statements. It can be used to obtain a quick explanation of the chosen access plan when explain data was not captured. For static SQL and XQuery statements, db2expln examines the packages stored in the system catalog tables. For dynamic SQL and XQuery statements, db2expln examines the sections in the query cache.

AltovaXML 2006

AltovaXML is a FREE XML standards processor that includes the Altova XSLT 1.0 engine, XSLT 2.0 engine, XQuery engine, and XML validating parser. Now developers can use the same engines found in Altova XMLSpy 2006 in their own application, free of charge.

XQuery Tips and Tricks

XQuery Tutorial

XQuery By Example

[wikipedia.org]

[http://www.w3schools.co]

[http://www.ibm.com/developerworks/xml/library/x-xquery.html]

A few points in their roster actually seem valid. Most are weak or flat-out invalid, though, so let's take a peek.

First up, they bash "Character Encoding", referring to the fact that you need to specify an encoding for the text in an XML file, and it's entirely possible to declare encoding X and actually use encoding Y, which screws up parsing. They also bash having to entity-escape things like < and &, and people over-using CDATA sections.

Unfortunately for them, this section does a fine job of illustrating the problems I have with their diatribe. They mix-and-match multiple types of problems and blame it all on XML, when that's not really accurate. In this case:

• Encoding and entity-escaping problems are only an issue with hand-writing XML -- any XML generator worth its salt will take care of it for you programmatically if you are generating XML in an application. Moreover, any non-textual data format CAN'T BE HAND-WRITTEN AT ALL, at least not in any reasonable fashion (ever try to hand-encode an MPEG frame?). XML is imperfect for hand-written data, but it is light-years better than hand-written data in a binary format.
• The CDATA bash needs to be aimed at those who overuse it, not at XML itself. This is a popular theme in XML bashing: blame the format for bad users. It'd be like my blaming a blogging software vendor because their article has issues.

Next up, they bash "Embedding Binary Data", which is indisputable. XML is not geared for that situation and should not be used when that is a requirement.

Next, "Indentation Characters Mixed With Data", which goes back to the hand-written XML "problem". Yes, if you are hand-writing or hand-inspecting XML, dealing with indentation can be a hassle, but it beats the hell out of using a hex editor to hand-write or hand-inspect binary data formats. And, if you are generating or consuming XML programmatically, it's not an issue.

Next, "Textual Representation of Numeric Data" is a case of "you say tom-ay-toe, I say to-mah-toe". They don't like the fact that numbers take up more space than they do in binary. I don't like the fact that binary floating-point representations are intrinsically inaccurate. Both are problems. Neither are big deals, except when they aren't (extremely low-bandwidth situations in their case, currency calculations in mine).

Next, "Unnecessarily Verbose" is another long-standing gripe tossed out by XML bashers. To some extent, I agree, and therefore prefer something like JSON in simple cases. However, there are very very few situations where the verbosity will be an issue, mostly for really big data needs (which is why Google created Protocol Buffers) and really low bandwidth scenarios. For your garden-variety developer, or blogger, or whatever, the extra characters have no real negative impact.

Next, "Human un-readability" is a re-hash of their earlier complaints. Again, while XML is not perfectly readable, it's way better than trying to make sense of bit soup. When developers are stuck embedding nonsense text like "green eggs and ham" in their binary structures, just to be able to pick out key sub-structures when staring at a hex editor screen, XML looks easy by comparison.

Next, "A single XML root element" is a somewhat valid complaint. Historically, XML had a single root element because SGML did, IIRC. There are certainly cases where having multiple roots can be handy, as they outline, and some parsers even support it.

Finally, "SOAP - Oh My God" would be a valid complaint if that's actually what they complained about. Heaven knows I'm no fan of the SOAP structure. However, they claim:

Once you start parsing the XML document you parse it all!

which is only true if you're some programming n00b. There are many types of XML parsers, only some of which (e.g., DOM) always parse the whole document. Others (SAX, XML pull parsers) don't, and in scenarios like what they describe, you'd want to use one of those. Blaming XML because programmers use the wrong tools is just plain goofy.

Don't get me wrong: XML gets misused all the time. It gets applied to circumstances where it is unsuitable, people misuse features like CDATA, and so on. And if somebody wants to suggest a replacement format that offers most of XML's features (e.g., namespaces, schemas) and cures some of its ills (e.g., verbosity), I'm all ears. But if you're going to take the time to write a several-page blog post bashing XML, at least do your readers a service and do a decent job at it.

So I stopped using att_xml_string to re-entity-reference attribute contents. Instead, I'm using HTML::Entities::encode_entities, which is probably what I should have been doing from the start, since it's not XML::Twig's job to make sure the XML I'm building from its output is well-formed.

I think the lesson here is don't always look for the solution from the source of the problem. And that blogs work.