It turns out the HowTo I wrote earlier this year is one of the more popular pages on my humble little blog.  Since I was upgrading, I decided to review the HowTo for v0.11 and the latest version of Ubuntu, Hardy Heron.  The result is a new HowTo I posted this evening under my HowTos section.  I hope it helps someone out.

Para comenzar, iremos a Sistema > Administración > Gestor de paquetes Synaptic

ahi seleccionaremos los siguientes paquetes

envyng-core
envyng-gtk

estos serviran para instalar el programa. Luego lo abrimos llendo a Aplicaciones > Herramientas del sistema (nuevo menú que se crea tras la instalación) > EnvyNG

Luego seleccionamos si queremos drivers AIT o NVIDIA, y elegimos la primera opción "Instala el controlador NVIDIA (Detección automática de hardware)", y pulsamos Aplicar, y despues de aqui todo rapido y facil, algo importante, no tengan ningun gestor de paquetes abiertos porque la instalación da errores :)

Cuando termina de descargar e instalar aparecerá la siguiente pantalla diciendo "Operación completada", y luego si deseamos reiniciar el equipo, aqui ponemos que no

Luego iremos a Sistema > Administración > Gestor de paquetes Synaptic y seleccionaremos para descargar e instalar

nvidia-xconfig

y sus dependencias que se marcan automáticamente

Pulsamos aplicar cambios y esperemos pacientes.

El hecho de descargar esta mini-aplicación es para configurar luego la placa aceleradora, porque al reiniciar Ubuntu nos encontraremos que ha reacomodado todo para el uso de la placa gráfica, pero a veces no son nuestros gustos, por ejemplo a mi me bajo la resolución de 1024*768 a 800*600 que no le hace bien a mis ojos, y me es incómoda, al intentar cambiarla desde las propiedades de ubuntu me daba como la más alta 800*600 (siempre me hace lo mismo!! no me quiere!! jaja) con esta aplicacion NVIDIA X Server Settings podemos modificar todo, sin meter mano en la consola ni en el archivo xorg.conf (mi peor enemigo)

Estos son 2 pantallazos del programa, si notamos en el segundo ahi aparecen las configuraciones, pero cada vez que cambien algo deben apretar el botón "Save to X Configuration File" que lo que hace ni mas ni menos es modificar el xorg.conf para que siempre use estas configuraciones :)

Para ATI no investigue mucho porque no tengo donde probar :( si algun dia tengo oportunidad lo hago :)

Bueno aqui temina mi primier HOWTO hecho solo por mi :) y ahora a disfrutar de las placas aceleradoras :)

Saludos y exitos

Emanuel

Grundsätzlich gilt: es funktioniert. Allerdings unterliegen DS in FB einigen Besonderheiten:

• XML-Files: Die Service-Komponenten-Beschreibungen können beliebig im Host- oder Fragment-Bundle abgelegt werden. Sie können beliebige Klassen aus beiden Bundles reservieren, da ja beide zur Laufzeit zu einem Bundle verschmolzen werden und sich den Classpath teilen.
• Manifest-Files: Jetzt die schlechte Nachricht, das Element Service-Component
darf nur in der Manifest-File des Host-Bundles eingetragen sein, im Manifest des Fragments wird es ignoriert. Es können jedoch mehrere Service-Component-Elemente im Host-Manifest "auf Vorrat" eingetragen werden, wenn man sich dann an den Fehlermeldungen im Log nicht stört.
• Konflikte: Was passiert, wenn man mehrere gleichnamige XML-Files in Host- und Fragmenten liegen, diese aber unterschiedliche Service-Komponenten deklarieren?? Es steht wahrscheinlich in keiner Spezifkation, was dann geschieht, bei Eclipse Equinox passiert folgendes: Es werden zwei eigenständige Service-Komponenten erstellt und gestartet. Es findet keine Überschreibung oder Überlagerung statt. Man kann sich das so vorstellen, als lägen beide in unterschiedlichen Files im gleichen Bundle. Falls es vorkommt, dass die Service-Komponenten einen identischen Namen haben (too much copy-paste ;) ),  so kollidieren bei so wie im Normalfall.

On other notes.. I'll be in Angola starting October 3rd.

I seriously doubt many people actually attempt to look for this statement although it should be included in all major websites.

Amazon has a good example of how it looks.  Just go to amazon.com and click View->Web Page Privacy Policy.  You will see how this will look.  Yahoo sends the location of the P3P file via the response header but does not work in IE or FireFox.  I am guessing they are still using an old implementation of P3P.  I tried the header on my server but FireFox nor IE7 was able to pick it up and use it in any way.

Creating a compact privacy policy is very simple and here is how to do it:

Step 1 - Create Compact Privacy Policy Directory and Files

- Create a folder named /w3c in the root site

- Create two files, p3p.xml and p3p_full.xml

Step 2 - XML Compact Privacy Policy Information

- p3p.xml:

<META xmlns="http://www.w3.org/2002/01/P3Pv1">
   <POLICY-REFERENCES>
      <POLICY-REF about="http://www.mydomain.com/w3c/p3p_full.xml">
         <INCLUDE>\*</INCLUDE>
         <COOKIE-INCLUDE name="*" value="*" domain="*" path="*"/>
      </POLICY-REF>
   </POLICY-REFERENCES>
</META>

- p3p_full.xml:

<POLICY name="forBrowsers"
discuri="http://www.mydomain.com/privacy.php">
<ENTITY>
<DATA-GROUP>
<DATA ref="#business.name">mydomain.com</DATA>
<DATA ref="#business.contact-info.postal.street">123 Example St</DATA>
<DATA ref="#business.contact-info.postal.city">Anytown</DATA>
<DATA ref="#business.contact-info.postal.stateprov">CA</DATA>
<DATA ref="#business.contact-info.postal.postalcode">90240</DATA>
<DATA ref="#business.contact-info.postal.country">USA</DATA>
<DATA ref="#business.contact-info.online.email">me@mydomain.com</DATA>
<DATA ref="#business.contact-info.telecom.telephone.intcode">1</DATA>
<DATA ref="#business.contact-info.telecom.telephone.loccode">123</DATA>
<DATA ref="#business.contact-info.telecom.telephone.number">4567890</DATA>
</DATA-GROUP>
</ENTITY>
<ACCESS><nonident/></ACCESS>
<DISPUTES-GROUP>
<DISPUTES resolution-type="independent"
service="http://www.mydomain.com"
short-description="mydomain.com">
<IMG src="http://www.mydomain.com/images/privacy.jpg" alt="Privacy Logo"/>
<REMEDIES><correct/></REMEDIES>
</DISPUTES>
</DISPUTES-GROUP>
<STATEMENT><br /> <PURPOSE><admin/><develop/></PURPOSE>
<RECIPIENT><ours/></RECIPIENT>
<RETENTION><stated-purpose/></RETENTION>
<DATA-GROUP>
<DATA ref="#dynamic.clickstream"/>
<DATA ref="#dynamic.http"/>
</DATA-GROUP>
</STATEMENT>
</POLICY>

At the top of p3p full file, you will see a link to the privacy policy page.  Here you will just insert the link where it is located on your server.

The privacy logo can be just about any image you want.  You can even use the trust-e image if you have it or want to link to it.

There is a lot more information you can provide in the full p3p file (2).

1. “Section 2 What is P3P and How Does it Work?,” http://p3ptoolbox.org/guide/section2.shtml#IIa.
2. “The Platform for Privacy Preferences 1.0 (P3P1.0) Specification,” http://www.w3.org/TR/P3P/.
3. “Web Analytics Insight: P3P - Do we really care about it?,” http://rkapoor.blogspot.com/2007/07/p3p-do-we-really-care-about-it.html.

"Olá a todos, para quem gosta do Ubuntu System Panel, resolvi traduzir o tutorial de instalação dele, o qual pode ser encontrado aqui:
http://code.google.com/p/ubuntu-system-panel/wiki/Installation

AVISO: Se você estiver rodando o compiz/beryl será preciso definir o foco para "Nenhum" para usar o USP (Ubuntu System Panel).

Para realizar a instalação, é necessário que você possua o Subversion, caso não possua faça o download dele através deste comando:
sudo apt-get install subversion

Crie um diretório para baixar o USP nele, e use o comando cd para ir nele, no meu caso usei a pasta SVN com este comando:
cd Área\ de\ Trabalho/SVN

E use este comando:
svn checkout http://ubuntu-system-panel.googlecode.com/svn/trunk/ ubuntu-system-panel

Este comando irá baixar todos os arquivos do USP, após terminar o download, use este comando para ir para a pasta baixada:
cd ubuntu-system-panel

E para instalar, use este comando:
./usp_update install fresh

Pronto, você instalou com sucesso o USP, agora clique com o botão direito no painel, clique em Adicionar ao painel..., vá até o final da lista e adicione o Ubuntu System Panel."

• First of all download and install Xampp, Subversion and ToirtoiseSVN

• After installing Xampp, point your browser at http://localhost to make sure that your server is running.

• Copy the files mod_authz_svn.so and mod_dav_svn.so found under your subversion bin directory (e.g. C:/Program Files/Subversion/bin/) to the C:\xampp\apache\modules directory,

• Now edit your Apache httpd.conf found under C:\xampp\apache\conf (keep a backup for peace of mind) and enable the lines

LoadModule dav_svn_module modules/mod_dav_svn.so

LoadModule authz_svn_module modules/mod_authz_svn.so

If you can't see these lines copy-paste them from here. Then go at the end of the file and add the following lines:

# Configure Subversion repository
<Location /svn>
DAV svn
SVNPath "C:\svn"
AuthType Basic
AuthName "Subversion repository"
AuthUserFile "c:\svn_conf\passwd"
Require valid-user
</Location>

• Save and close the httpd.conf file, then restart Apache.

NOTE: In case apache does not start this means that there is something wrong in the httpd.conf file. Go to the xampp/apache/bin folder in your drive and run apache from the command line to see exactly at which line the problem is. In my Vista box for example I had to remove the quotes on the above lines to get it to work. So you need to experiment until apache gets up and running correctly.

Also note that If you have Skype running you might not be able to start any of the Xampp service due to some strange conflict. Close skype, start the xampp services you want and then start skype again. This should solve it.

• Now create two folders in your C:\ drive, one called svn and the other called svn_conf.

• In order to password protect your repository fire up a command prompt and browse into the apache/bin folder C:\xampp\apache\bin and then type htpasswd -c C:\svn_conf\passwd yourname

• Now it's time to create your first repository. Go in the C:\svn folder just created and right-click in it. From the drop-down menu choose ToirtoiseSVN ->Create repository here. If all goes fine ToirtoiseSVN will inform you that the repository was created sucessfuly.

• Finally in order to import the directory where you keep your source code into your repository right-click on the source code directory and choose ToirtoiseSVN->Import. In the window that shows up type the path to your svn repository, that is file:///C:/svn.

Test your setup by pointing your browser to http://localhost/svn and entering the username/password combination that you have defined.

inspiration & credits:lifehacker

I just love the logo:

http://www.ubuntukungfu.org/

First of all, install open-iscsi

aptitude install open-iscsi

and remove the broken init scripts (they are going to give you lots of headaches when rebooting, if you don't do this.)

update-rc.d -f open-iscsi remove

create a couple of symlinks to fix paths needed to automatically detect targets on reboot, and thus creating the sdX devices

ln -s /etc/{iscsid.conf,initiatorname.iscsi} /etc/iscsi/


edit /etc/iscsi/iscsid.conf and make sure that

node.startup = automatic


Restart open-iscsi
/etc/init.d/open-iscsi restart

Now, let's discover the iSCSI targets connected to the net:

iscsiadm -m discovery -t sendtargets -p $SAN_IP_ADDRESS


Restart open-iscsi again, now you should see sdX appear in dmesg!
/etc/init.d/open-iscsi restart

You can now partition and format the new disk(s) just as they were phisically attached disks... but beware, it's not over yet, you'll have to keep in mind and tweak a couple of things.
First, when you add the disk entry in your /etc/fstab, remember to use the -_netdev option, so for example:


/dev/sdb1 /mnt/logs ext3 defaults,auto,_netdev 0 0


This will make scripts like /etc/init.d/umountnfs.sh aware that they are remote network resources and... do nothing different because as I said Debian Etch is bugged as hell when dealing with iSCSI. :(
The default behaviour is, in fact, to kill the iscsid process and bring down the network interfaces before umounting the iSCSI disk, with effects ranging from kernel panics to "normal" lock-ups when rebooting the machine.
So, edit /etc/network/interfaces with your favourite editor and put something like this in the network interface you're using to connect to the iSCSI SAN:

post-up echo "Waiting for network to come up before starting iSCSI..." && sleep 5
post-up /etc/init.d/open-iscsi start
pre-down umount -a -O _netdev
pre-down /etc/init.d/open-iscsi stop


moreover, edit /etc/default/rcS and put

ASYNCMOUNTNFS=no


to disable async mounting which in theory works better but in practice doesn't work very well in Debian Etch when dealing with iSCSI.

The sleep is to assure that the interface is really up&running before trying to start open-iscsi, otherwise automounting on boot won't work. I know, it looks like an hack and indeed it's an ugly, awful hack, but it works, at least in my environment :)
The other thing we have to tweak is the /etc/init.d/sendsigs script, which is used to kill all the running processes when rebooting/shutting down the server. This script is going to kill the iscsid daemon before umounting can happen, so making impossible to reboot your machine without physical access (and we all leave our machines in datacenters, don't we?). So, here it is another simple hack to work around the problem:

mv /etc/rc6.d/S20sendsigs /etc/rc6.d/S39sendsigs
mv /etc/rc0.d/S20sendsigs /etc/rc0.d/S39sendsigs
(runlevel 0 is halt, runlevel 6 is reboot)

this way we tell init to execute sendsigs after umountnfs.sh, networking, ifupdown, thus solving our problem. :)
And that's all now, you should be able to reboot your machine and have it to boot again, mounting your iSCSI volumes automatically.

Keep in mind that this howto is thought for servers in front of the SAN, so I'm supposing you're not going to mount/umount things all the time, or bring up and down interfaces all the time. So for example do not complain if with a ifdown $IFACE you are bringing all the iSCSI infrastructure down.

One last note: I've been inspired by these post I found on the Internet, but they are not completly working with Debian bugs or they do things in a more complicated way (at least for me). Anyway thanks to their authors, they were really useful posts:

Debian / Ubuntu Linux Connect to an iSCSI Volume

Montando un iniciador iSCSI en Linux (in spanish)

Una vez que tenemos a este registrado desde Debian o cualquier distribución que utilize los paquetes .deb, realizamos:

#: apt-get install ddclient

Si utilizan FedoraCore pueden realizar:

#: yum install ddclient

Esperamos que descargue e instale y procedemos a modificar el archivo /etc/ddclient.conf, para ello con nuestro editor de textos favoritos (yo elegi Vim), abrimos el archivo.

#: vim /etc/ddclient

Y en el contenido del mismo ponemos lo siguiente:

# Configuration file for ddclient generated by debconf
#
# /etc/ddclient.conf

pid=/var/run/ddclient.pid
protocol=dyndns2
use=web, if=eth0
server=members.dyndns.org
login=miusuario
password='password'
midominio.homelinux.net

• La línea pid especifica el archivo en que debe guardarse el pid del proceso ddclient.
• La línea protocol, el protocolo que utilizaremos, en este caso dyndns2.
• La línea use web, le dice que utilize el puerto 80 para validar y sincronizar nuestro IP.
• La línea if es la interfaz que debe utilizar para realizar dicha actualización, en mi caso eth0.
  Si utilizamos por ejemplo ppp0 para conectarnos debemos remplazarla por esta.
• La línea server es el servidor mediante el cual nos autentificaremos.
• La línea login es el nombre de usuario que hemos obtenido al registrarnos.
• La línea password como bien dice, es la contraseña de nuestra cuenta.
• Y al final de todo procederemos a indicar el dominio o los dominios que queremos utilizar.

Bien con esto ya escrito, procedemos a guardar los cambios de dicha modificación y a cambiar los permisos del archivo ddclient.conf.

#: chmod 600 /etc/ddclient.conf

Con esto unicamente le damos permisos de lectura y escritura (4+2 / wr) al propietario del fichero que debe ser root.
Estos permisos son importantes ya que en /etc/ddclient.conf se almacenan datos importantes, tales como un username y una password, que se encuentran en texto plano y podrian ser vistos por cualquier otro usuario.

Ahora lo que debemos hacer es indicarle a ddclient que debe correr como demonio, para ello con vim editamos el siguiente archivo

#: vim /etc/default/ddclient

Y dentro de este especificamos como true el campo run_daemon, de esta forma le decimos que debe ejecutarse como un demonio, y daemon_interval, es el tiempo de actualización entre cada actualización de nuestra IP que debe hacer ddclient.

# Configuration for ddclient scripts
# generated from debconf on sáb ago 16 10:43:35 ART 2008
#
# /etc/default/ddclient

# Set to "true" if ddclient should be run every time a new ppp connection is
# established. This might be useful, if you are using dial-on-demand
run_ipup="false"

# Set to "true" if ddclient should run in daemon mode
run_daemon="true"

# Set the time interval between the updates of the dynamic DNS name.
# This option only takes effect if the ddclient runs in daemon mode.
daemon_interval="300"

Con esto listo deberiamos poder iniciar el proceso, por lo cual ejecutamos:

#: /etc/init.d/ddclient start

Y listo ddclient ya se esta ejecutando y ha obtenido un IP.
En caso de querer actualizar el IP, sin esperar a que transcurra el intervalo de actualización en la shell ejecutamos:

#: ddclient

Y listo, tenemos nuestra IP dinámica sincronizada a un nombre de dominio, para poder montar nuestros propios servidores caseros, sin necesidad de tener un IP estatica.

During my last job I got the chance to work at Portugal's largest mobile operator, TMN, and I was relocated to Marocco for one month, on a Bandwidth Control project.

Although I was thinking about leaving PTInovação, I recieved a job offer from Lisbon. One of Portugal's top consultancy firms, which plays head to head with Accenture and Deloitte in both national and international markets, gave me an offer I couldn't refuse, and I didn't.

So here I am, at Novabase ACD, over-looking the Lisbon Casino and the Tejo River from my desk. This is prime real-estate. Simply one of the best places to work in Lisbon.

So here go the perks:

Dell Laptop

Nokia Phone (Calls Paid)

Health Insurance (In Portugal its not that common)

And a pretty decent salary pakage.

Oh, ya.. and my next country to be relocated to will be Angola..

See you soon :)

apt-get install python2.4

2) Install Twisted library 1.1 or greater

apt-get install python2.4-twisted python2.4-crypto python2.4-pyopenssl

3) Download PyMSNt from http://msn-transport.jabberstudio.org/tarballs/pymsnt-0.10.2.tar.gz

4) Extract and move the archive under /opt

tar -zxvf pymsnt-0.10.2.tar.gz
mv pymsnt-0.10.2 /opt

5) Create a configuration file from the sample given

cd /opt/pymsnt-0.10.2
cp config-example.xml config.xml

6) Now open config.xml in your favourite editor and make the following changes.

<jid>msn.host.domain.com</jid># replacehost.domain.com with your FQDN
<mainServer>xx.xx.xx.xx</mainServer> # IP address of the jive messenger server
<mainServerJID>host.com</mainServerJID> # FQDN
<port>10015</port> # Jive messenger connects to the external components using this port by default
<secret>secret</secret> # password which is assigned to connect to the external components

Note: If you make changes to the port and the password on the Jive Messenger, ensure that you make the changes here also.

7) Create a spool directory under /opt/pymsnt-0.10.2

mkdir /opt/pymsnt-0.10.2/msn.host.domain.com # replace host.domain.com appropriately

Now you can start the transport by issuing

cd /opt/pymsnt-0.10.2
./PyMSNt &

Once the above steps are done, you can see the MSN transport listed under external components on the Jive Messenger.

Happy chatting!

Jive Messenger supports the following features:

* Server to Server Support (c2s)
* Plugins (installation can never be simpler than this!)
* LDAP Authentication
* Transports (currently it supports MSN, ICQ, AIM - Yahoo is still in beta)
* SSL and TLS

Installation

The installation was done on Ubuntu 5.10.

1) Install Ubuntu through server-expert mode.
2) Install JDK or JRE 1.5.0 or greater. Download the binary here
3) Download the latest Jive Messenger from here
4) Extract the tar archive using the following command

tar -zxvf jive_messenger_2_2_2.tar.gz
cd jive_messenger_2_2_2
mv jive_messenger /opt

5) Start the service by executing the following command:

/opt/jive_messenger/bin/messenger start

6) Stop the service by executing the following commmand:

/opt/jive_messenger/bin/messenger stop

Note: If you would like to install Jive Messenger as a service, two scripts are provided in the /opt/jive_messenger/bin/extras folder

7) The configuration file (jive-messenger.xml) is available under /opt/jive_messenger/conf/ (create a backup of this configuration file as you may need it for reference

(8) Edit jive-messenger.xml using your favourite editor and make the following changes. Locate the following lines and replace host.domain.com with your hostname.

<host>host.domain.com</host>
<port>9090</port>
<securePort>9091</securePort>

Ensure that the hostname (FQDN) is registered in your DNS server.

9) Restart the messenger service. 

Jive messenger has got its own embedded database for storage. However you can choose to use an external database such as MySQL, SQL or Oracle. Once the messenger service is started, you must prepare it before proceeding with the installation by running appropriate database schema. Jive Messenger database setup instructions are available here

10) The default port for the web-based admin console is 9090. Now the admin console can be accessed from http://host.domain.com:9090 using your favourite browser. Major part of the configuration can be done using this console.

Run the initial configuration wizard from the console and the steps are self-explanatory. Login using the admin account with the password you had given in the earlier step. Using any of the jabber clients like Gaim, Exodus, Psi or Pandion, you can register your account on the server. Note: Login names given between<authorizedUsernames>name1, name2</authorizedUsernames> can administer the server.

The above installation is more than enough for a smaller setup. However if you already have an active directory running at your end, you may choose to authenticate using LDAP and the steps are given below:

LDAP Authentication

Make the following changes to jive-messenger.xml and restart the service.

Uncomment or remove after <!-- before <ldap> and remove --> after </provider> 

<ldap>
<host>ldap.server.ip.address</host>
<port>389</port>
<usernameField>uid</usernameField>
<nameField>cn</nameField>
<emailField><emailField/>
<baseDN>ou=People;dc=domain;dc=com</baseDN>
<adminDN>cn=admin;dc=domain;dc=com</adminDN>
<adminPassword>AdminPasswordHere</adminPassword>
<debugEnabled>true</debugEnabled>
</ldap>

Disable in-band registration from the web console.

Now you should be able to authenticate using LDAP.

Plugins

As I had informed earlier, currently there are about 7 plugins available for download. The plugins such as Broadcast, Content Filter and Registration are useful for administration. The installation of these plugins are very simple as you would just need to copy the jar files to the plugin directory (/opt/jive_messenger/plugins) and refresh the admin console on your browser!

Will write a note on the transport installation very soon. So stay tuned!

1. Make sure gcc , gcc-c++ , bison , flex , make , openssl and openssl-devel are present

2. yum -y install boost-devel

3. export BOOST_ROOT=/usr/include/

4. Get ACE Here .

5. tar xvf ACE-5.5.tar.gz

6. cd ACE_wrappers

7. mkdir build

8. cd build

9. Patch the configure file

--- configure.orig 2008-08-05 11:11:19.000000000 -0800
+++ configure 2008-08-05 11:13:30.000000000 -0800
...
@@ -10329,7 +10329,7 @@ _ACEOF
*)
{ echo "$as_me:$LINENO: enabling GNU G++ visibility attribute support" >&5
echo "$as_me: enabling GNU G++ visibility attribute support" >&6;}
- ACE_GXX_VISIBILITY_FLAGS="-fvisibility=hidden -fvisibility-inlines-hidden"
+ ACE_GXX_VISIBILITY_FLAGS="-fvisibility=hidden"
ACE_CXXFLAGS="$ACE_CXXFLAGS $ACE_GXX_VISIBILITY_FLAGS"
cat >>confdefs.h <<\_ACEOF

10. cd build ; ../configure

11. make && make install

12. export ACE_ROOT=/usr/local/src/ACE_wrappers/

13. tar xvf opendiameter-1.0.7-i.tar.gz

14. cd opendiameter-1.0.7-i

15. ./configure

16. make

17. make install

Em Ferramentas, na guia Rede, no item Servidor Proxy, habilite: Usar configuração do ambiente.

Em Contas, Gerenciar contas, escolha a conta a ser modificada.

Messenger

Em Avançado, habilite Usar método HTTP, e em Opções de proxy, escolha Usar configuração global de proxy.

Google Talk

Em Avançado, habilite Forçar SSL antigo (porta 5223), em Porta de conexão, altere para 443 e em Opções de proxy, escolha Usar configuração global de proxy.

Até a próxima.

Die folgende Checkliste wurde unter der Verwendung von Eclipse Equinox erstellt.

Checkliste: Was wird für Declarative Services benötigt?

• Die Implementierung der Deklarative Services erfolgt durch das Bundle org.eclipse.equinox.ds. Dieses Bundle muss immer mit geladen werden, bevor die DS verwendet werden können.
• Zusätzlich wird die Klasse ComponentContext aus dem Bundle org.osgi.service.component benötigt.
• Die eigentliche Implementierung des DS erfolgt als sog. Service Component, also einer Klasse, welche den Service (besser gesagt: das Service Interface) implementiert. Im Gegensatz zu einem Activator wird diese nicht abgeleitet oder implementiert eine Interface. Sie muss trotzdem folgende zwei Funktionen enthalten, damit die ServiceComponent funktioniert. Diese Funktionieren ähnlich wie die start und stop Methoden des Bundle-Activators.
  • protected void activate(Component context){...}
  • protected void deactivate(Component context){...}
    
• Eine Konfigurationsdatei in XML: Diese Datei wird üblicherweise in einem Verzeichnis namens OSGI-INF abgelegt, der Dateiname ist beliebig. Die XML-Datei selbst folgt dem hier zu findenden Schema. Wichtig ist hier, dass alle Inhalte der XML-Datei, also Tags, Attribute aber Paket- und Klassennamen richtig geschrieben sind, ansonsten kann die Service Component nicht aktiviert werden.

• Änderung im Manifest-File des Bundles: Füge eine neue Zeile hinzu, der Inhalt ist Service-Component: OSGI-INF/service.xml (wenn die XML-Datei service.xml heißt)

Beispiel:

Hierzu ein kleines Beispiel: Eine ServiceComponent soll erstellt werden, die einen Service mit dem Interface MyServiceInterface bereitstellt. Sie soll außerdem eine Liste von Services des Interface OtherService beinhalten. Dazu bindet sie diesen Service (der auch über eine Service Component realisiert werden muss) mit der cardinality="1..n", so dass mindestens ein OtherService vorhanden sein muss, um die Service Component zu aktivieren. Die einzige Funktion in MyServiceInterface gibt die Anzahl der angebundenen OtherService zurück.

Service Interface:

package org.example.ds
import ...
public interface MyServiceInterface {
    int getCount();
}

Implementierungs-Klasse:

package org.example.ds.internal
import ...
public class MyServiceImplementation implements MyServiceInterface {

    private ComponentContext context;
    private List<OtherService> servicelist = new Vector<OtherService>(0);

    protected void activate(ComponentContext context){
        this.context = context;
    }

    protected void deactivate(ComponentContext context){
        this.context = null;
    }

    protected void bindOtherService(OtherService otherservice){
        this.servicelist.add(otherservice)
    }

    protected void unbindOtherService(OtherService otherservice){
        this.servicelist.remove(otherservice)
    }

    public int getCount(){
        return this.servicelist.size();
    }
}

Die XML-Datei im OSGI-INF Ordner:

<?xml version="1.0" encoding="UTF-8"?>
<component name="myServiceComponent">
    <implementation class="org.example.ds.MyServiceImplementation"/>
    <service>
        <provide interface="org.example.ds.MyServiceInterface"/>
    </service>
    <reference
        name="otherservice"
        interface="org.example.ds.OtherService"
        bind="bindOtherService"
        unbind="unbindOtherService"
        cardinality="1..n"
        policy="static"
    />
</component>

Fehlersuche:

• Das Bundle startet, aber die Service Component nicht. Dies kann viele Ursachen haben:
  • Schreibfehler in der Manifest- oder XML-File. Am besten nochmal nachschauen, ob alle Paket- und Klassennamen stimmen.
  • Eine geforderte Referenz ist nicht verfügbar. Untersuche alle Referenzen, ob deren Service Components vollständig gestartet wurden.
  • Eintrag in der Manifest-File fehlt oder ist ungültig. Mein absoluter Lieblings-Fehler ;)
  • Funktionen wie activate/deactivate bzw. bind/unbind fehlen oder sind ungültig.
• NullPointerException oder andere krude Exceptions werden geworfen: Dies kann auftreten, wenn Klassenmember in der activate-Funtion belegt werden. Diese wird nämlich erst dann aufgerufen, wenn alle Referenzen erfüllt sind, also erst nach den bind-Funktionen. Wenn in bind schon auf das Member zugegriffen wird, ist es dann noch null und die NullPointerException wird geworfen.
• Hilfe, ich sehe nicht ob sich irgendwas tut!!!
  • Der Status einer Service Component kann leider nicht einfach über den status-Befehl abgefragt werden, da Service Components ein relativ neues Konzept sind.
  • Eine Service Component meldet ihre Services sofort an der Service Registry an, der Befehl services gibt also keinerlei Aufschluss über den Status ser Service Component.
  • Am besten kann der Lebenszyklus über den Log-Service verfolgt werden, den Equinox mitliefert. Er kann über das Bundle org.eclipse.equinox.log angebunden werden

wenn man in einer tabelle A alle spalten a auf einen bestimmten wert setzen möchte, die eine bestimmte bedingung (A.b = B.b) mit einer anderen tabelle B erfüllen, geht das in oracle so:

UPDATE A
set A.a =
(SELECT B.a
FROM B
WHERE A.b = B.b)

in access würde es so gehen:

update A inner join B on
A.b = B.b
SET A.a = B.a

in SQL server so:
UPDATE A
SET A.a = B.a
INNER JOIN B
ON A.b = B.b

siehe z.b. auch sql-tutorial