jquery ui tabs tab selected callback

If you are using the tabs()-element of the jqueryui you might want to perform a custom action after the selection of the tab. The tab()-element is offering different methods.

1. is executed before the tab switches. You have the possiblity to cancel the action.
2. is executed after the tab has switched. You got e.g. the option to set the focus to a specific element

http://api.jqueryui.com/1.8/tabs/#event-show $("#mytabs").tabs({ show: function( event, ui ) { alert("aftr change");} }); An other option is just to bind the tabsshow $("#mytabs").bind("tabsshow", function(event, ui) { if (ui.index == 0) { $("#e1").focus(); } else { $("#e2").focus(); } }); http://api.jqueryui.com/1.8/tabs/#event-select

using jquery's spinner in custom component

Assumtion/prerequirements

1. You are using jQuery
2. You are using jQuery UI

By using jquery ui's autocomplete you get this nice spinner in your input-tag.
It is pretty easy to reuse the spinner in you own component.

$('#user_id').addClass( "ui-autocomplete-loading");

$('#user_id').removeClass( "ui-autocomplete-loading");




In my case I used an following ajax-call:

$('#user_suchen').click(function() {
  $('#user_id').addClass( "ui-autocomplete-loading" );
  var userId = $('#user_id').val();
  $.ajax({
    url : '${getUserData}',
    data : { "userId" : userId },
    dataType : "json",
    success : function(data, textStatus, jqXHR) {
      $('#name').val(data.name);
      $('#oe').val(data.oe_bezeichnung);
      $('#user_id').val(data.userId);
      $('#user_id').removeClass( "ui-autocomplete-loading" );
    },
    error : function( jqXHR, jqXHR, textStatus,errorThrown ) {
      $('#user_id').removeClass( "ui-autocomplete-loading" );
    }
  });
});

WAS choose faces implementation

Because WAS7 ist JEE5 compiant -
and every JEE5 container need to deliver a JSF 1.2 .
WAS7 gives you the option to choose which JSF-Implementation you want to provide for the app.

The following Screenshot tells you how to do this.

By the way - Did you notice that IBM does not offer the option to choose an IBM-Implementation of JSF 1.2
That's the reason why we have to deal with the old JSF 1.1 version in our app.
Migration is very difficult.
>
I read that with JEE7 (comming mai 2013) - JSF 2.2 will be part of the spezifikation.

OpenJPA DB2 hellojpa

In order to execute the sample app, you need to create the table in your Database.
In our case the user/owner ist called TESTUSR.
The table definition works fine with the sample, and it has soem adtional features.

CREATE TABLE TESTUSR.MESSAGE (
 ID BIGINT GENERATED BY DEFAULT AS IDENTITY(START WITH 1) PRIMARY KEY,
 CREATED DATE DEFAULT CURRENT_DATE NOT NULL,
 MESSAGE VARCHAR(2000) NOT NULL
);

INSERT INTO TESTUSR.MESSAGE (MESSAGE ) VALUES  ( 'hi2' )

don't forget the configuration of your persistence.xml.
In our case we set 4 parameters.
It is also possible to use a datasource in hosted appserverenvironment.
Because we are assuming the simple we choose to set the minimal necessary parameters.
<properties> <property name="openjpa.ConnectionURL" value="jdbc:db2://myhostname:50128/TESTDB1:retrieveMessagesFromServerOnGetMessage=true;"/> <property name="openjpa.ConnectionDriverName" value="com.ibm.db2.jcc.DB2Driver"/> <property name="openjpa.ConnectionUserName" value="testusr"/> <property name="openjpa.ConnectionPassword" value="xxxxx"/> </properties> <!-- This can also be performed from a cmdline as - java -cp .:openjpa-all-<version>.jar:derby-10.8.2.2.jar -Dopenjpa.ConnectionDriverName="org.apache.derby.jdbc.EmbeddedDriver" -Dopenjpa.ConnectionURL="jdbc:derby:mapping-database;create=true" -Dopenjpa.ConnectionUserName= -Dopenjpa.ConnectionPassword= org.apache.openjpa.jdbc.meta.MappingTool BuildSchemaPC.class -a buildSchema -->

WAS7 enable debugging

In order to connect to a remote java process. The JVM must be started in debugging-mode.

Application servers > server1 > Process definition > Java Virtual Machine

Debug arguments

Drucken-Link

Um eine HTML-Seite zu drucken kann man einen Link in seine HTML-Seite einfügen.

window.print();

Seite-Drucken

Reparieren eines kaputten WAS7 Profiles

C:\Programme\IBM\SDP75\runtimes\base_v7\bin\ProfileManagement\pmt.bat

Sobald das Tool gestartet ist, kann man sehen, wie das aktuelle Profil heisst.

C:\Programme\IBM\SDP75\runtimes\base_v7\bin>manageprofiles -delete -profileName was70profile1 INSTCONFSUCCESS: Erfolg: Das Profil ist nicht mehr vorhanden.

C:\Programme\IBM\SDP75\runtimes\base_v7\bin>manageprofiles -create -profileName was7profile1 INSTCONFSUCCESS: Erfolg: Das Profil was7profile1 ist jetzt vorhanden. Weitere In formationen zu diesem Profil finden Sie in der Datei "C:\Programme\IBM\SDP75\run times\base_v7\profiles\was7profile1\logs\AboutThisProfile.txt".

Nach der Reparatur des defecten Profiles kann man den Server wieder wie gewohnt starten.

C:\Programme\IBM\SDP75\runtimes\base_v7\bin>startserver server1 ADMU0116I: Tool information is being logged in file C:\Programme\IBM\SDP75\runtimes\base_v7\profiles\was7profile1\logs\s rver1\startServer.log ADMU0128I: Starting tool with the was7profile1 profile ADMU3100I: Reading configuration for server: server1 ADMU3200I: Server launched. Waiting for initialization status. ADMU3000I: Server server1 open for e-business; process id is 1720

http://localhost:9060/ibm/console

• Port der Administrationskonsole: 9060
• Sicherer Port der Administrationskonsole: 9043
• Port für HTTP-Transport: 9080
• Port für HTTPS-Transport: 9443
• Bootstrap-Port: 2809
• SOAP-Connector-Port: 8880