a bpel data manipulation tutor + I18N: BPCOR-3023: Selection Failure

i liked the tutor, so lets share the link:
http://www.oracle.com/technology/products/ias/bpel/pdf/orabpel-Tutorial3-DataManipulationTutorial.pdf

some other links:
http://jsexton0.blogspot.com/2009/01/openesb-bpel-assignment-tips.html
http://n2.nabble.com/ignoreMissingFromData-usage-td2474810.html

btw, all this research was due to the following error with open esb + glassfish combination:

Caused by: com.sun.jbi.engine.bpel.core.bpel.exception.StandardException: I18N: BPCOR-3023: Selection Failure occurred in BPEL({http://enterprise.netbeans.org/bpel/Balistika2010Bpel/IncidentRegistration}IncidentRegistration) at line 71!
BPCOR-6129:Line Number is 69
BPCOR-6130:Activity Name is AssignExtractDaimData
at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.createVirtualFaultUnit(BPELInterpreter.java:235)
at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:203)

issue about ignoreMissingData attribute on assign element
https://open-jbi-components.dev.java.net/issues/show_bug.cgi?id=181


sound problem in opensuse 11.2 for intel ich9

in my case, the problem is there is no sound..

and fortunately, the solution was simple.. i just run the following command as root:
cp /etc/modprobe.d/50-sound.conf /etc/modprobe.d/sound.conf

btw, prior to executing the command, there was no /etc/modprobe.d/sound.conf file..

also, i still can not get sound from the earphones at the front side of the tower, i use the one at the back..

some links:
http://medwinz.blogsome.com/2009/11/30/workaround-for-soundproblem-in-opensuse-112-for-intel-ich9/
http://en.opensuse.org/SDB:AudioTroubleshooting

smartctl

yesterday, unfortunately my computer crashed due to a raid failure (http://www.datarecovery.org/raid-failure.html) i still do not know why.. we assumed that one of the hard disks is problematic and took it off .
in order to figure out if there is a problem on hard disks, we have to test bothof them, before installing open suse on the machine again.. we used smartctl to do that.
an article on smart : http://www.linuxjournal.com/article/6983
some commands:

smartctl -t long /dev/sda : starts long test on specified disk
smartctl -t short /dev/sda : starts short test on specified disk
smartctl -l selftest /dev/sda : reports about all tests carried out on specified disk

btw, in my computer, starting a new test caused the previously started test on the same disk to abort..