Articles & Samples

IEnumerable vs IQueryable

2012-01-27T04:50:00.000-08:00

The difference is that IQueryable is the interface that allows LINQ-to-SQL (LINQ.-to-anything really) to work. So if you further refine your query on an IQueryable, that query will be executed in the database, if possible.
For the IEnumerable case, it will be LINQ-to-object, meaning that all objects matching the original query will have to be loaded into memory from the database.
In code:

IQueryable<Customer> custs = ...;
// ..
var customers = custs.Where(c => c.IsGold);

That code will execute SQL to only select gold customers. The following code, on the other hand, will execute the original query in the database, then filtering out the non-gold customers in the memory:

IEnumerable<Customer> custs = ...;
// ..
var customers = custs.Where(c => c.IsGold);

This is quite an important difference, and working on IQueryable can in many cases save you from returning too many rows from the database. Another prime example is doing paging: If you use Take and Skip on IQueryable, you will only get the number of rows requested; doing that on an IEnumerable will cause all of your rows to be loaded in memory.

Linq to DataTable

2012-01-25T03:44:00.001-08:00

public static DataTable LINQToDataTable(IEnumerable varlist)
        {   // Mucahid USLU mucuslu@hotmail.com

             DataTable dtReturn = new DataTable();

             // column names
             PropertyInfo[] oProps = null;

             if (varlist == null) return dtReturn;

             foreach (T rec in varlist)
             {
                 // Use reflection to get property names, to create table, Only first time, others will follow
                  if (oProps == null)
                  {
                       oProps = ((Type)rec.GetType()).GetProperties();
                       foreach (PropertyInfo pi in oProps)
                       {
                            Type colType = pi.PropertyType;

                            if ((colType.IsGenericType) && (colType.GetGenericTypeDefinition()
                            ==typeof(Nullable<>)))
                             {
                                 colType = colType.GetGenericArguments()[0];
                             }

                            dtReturn.Columns.Add(new DataColumn(pi.Name, colType));
                       }
                  }

                  DataRow dr = dtReturn.NewRow();

                  foreach (PropertyInfo pi in oProps)
                  {
                       dr[pi.Name] = pi.GetValue(rec, null) == null ?DBNull.Value :pi.GetValue
                       (rec,null);
                  }

                  dtReturn.Rows.Add(dr);
             }
             return dtReturn;
        }

HTML ASCII Characters

2011-12-01T01:00:00.001-08:00

HTML ASCII Characters
codes	characters	character names
		ASCII: space (usually one em wide)
!	!	ASCII: exclamation mark
"	"	ASCII: quotation mark
#	#	ASCII: number sign
$	$	ASCII: dollar sign
%	%	ASCII: percent sign
&	&	ASCII: ampersand
'	'	ASCII: apostrophe-quote
(	(	ASCII: opening parenthesis
)	)	ASCII: closing parenthesis
*	*	ASCII: asterisk
+	+	ASCII: plus sign
,	,	ASCII: comma
-	-	ASCII: hyphen-minus
.	.	ASCII: period
/	/	ASCII: slash
0	0	ASCII: digit zero
1	1	ASCII: digit one
2	2	ASCII: digit two
3	3	ASCII: digit three
4	4	ASCII: digit four
5	5	ASCII: digit five
6	6	ASCII: digit six
7	7	ASCII: digit seven
8	8	ASCII: digit eight
9	9	ASCII: digit nine
:	:	ASCII: colon
;	;	ASCII: semicolon
<	<	ASCII: less-than sign
=	=	ASCII: equals sign
>	>	ASCII: greater-than sign
?	?	ASCII: question mark
@	@	ASCII: commercial at
A	A	ASCII: Latin Capital Letter A
B	B	ASCII: Latin Capital Letter B
C	C	ASCII: Latin Capital Letter C
D	D	ASCII: Latin Capital Letter D
E	E	ASCII: Latin Capital Letter E
F	F	ASCII: Latin Capital Letter F
G	G	ASCII: Latin Capital Letter G
H	H	ASCII: Latin Capital Letter H
I	I	ASCII: Latin Capital Letter I
J	J	ASCII: Latin Capital Letter J
K	K	ASCII: Latin Capital Letter K
L	L	ASCII: Latin Capital Letter L
M	M	ASCII: Latin Capital Letter M
N	N	ASCII: Latin Capital Letter N
O	O	ASCII: Latin Capital Letter O
P	P	ASCII: Latin Capital Letter P
Q	Q	ASCII: Latin Capital Letter Q
R	R	ASCII: Latin Capital Letter R
S	S	ASCII: Latin Capital Letter S
T	T	ASCII: Latin Capital Letter T
U	U	ASCII: Latin Capital Letter U
V	V	ASCII: Latin Capital Letter V
W	W	ASCII: Latin Capital Letter W
X	X	ASCII: Latin Capital Letter X
Y	Y	ASCII: Latin Capital Letter Y
Z	Z	ASCII: Latin Capital Letter Z
[	[	ASCII: opening square bracket
\	\	ASCII: backslash
]	]	ASCII: closing square bracket
^	^	ASCII: spacing circumflex
_	_	ASCII: spacing underscore
`	`	ASCII: spacing grave
a	a	ASCII: Latin Small Letter A
b	b	ASCII: Latin Small Letter B
c	c	ASCII: Latin Small Letter C
d	d	ASCII: Latin Small Letter D
e	e	ASCII: Latin Small Letter E
f	f	ASCII: Latin Small Letter F
g	g	ASCII: Latin Small Letter G
h	h	ASCII: Latin Small Letter H
i	i	ASCII: Latin Small Letter I
j	j	ASCII: Latin Small Letter J
k	k	ASCII: Latin Small Letter K
l	l	ASCII: Latin Small Letter L
m	m	ASCII: Latin Small Letter M
n	n	ASCII: Latin Small Letter N
o	o	ASCII: Latin Small Letter O
p	p	ASCII: Latin Small Letter P
q	q	ASCII: Latin Small Letter Q
r	r	ASCII: Latin Small Letter R
s	s	ASCII: Latin Small Letter S
t	t	ASCII: Latin Small Letter T
u	u	ASCII: Latin Small Letter U
v	v	ASCII: Latin Small Letter V
w	w	ASCII: Latin Small Letter W
x	x	ASCII: Latin Small Letter X
y	y	ASCII: Latin Small Letter Y
z	z	ASCII: Latin Small Letter Z
{	{	ASCII: opening curly bracket
\|	\|	ASCII: vertical bar
}	}	ASCII: closing curly bracket
~	~	ASCII: tilde
		ASCII: DEL (ctrl DELETE)
€	?

‚	‚	ASCII: Comma
ƒ	ƒ	ASCII: Latin Small Letter F Script
„	„	ASCII: Double Prime Quote Mark Low
…	…	ASCII: Ellipsis Low
†	†	ASCII: Dagger
‡	‡	ASCII: Double Dagger
ˆ	ˆ	ASCII: Circumflex
‰	‰	ASCII: Per Mille (thousand) sign
Š	Š	ASCII: Latin Capital Letter S Hacek
‹	‹	ASCII: Less-than sign
Œ	Œ	ASCII: Latin Capital Letter OE

Ž	Ž


‘	‘	ASCII: Opening Single Quotation Mark
’	’	ASCII: Closing Single Quotation Mark
“	“	ASCII: Opening Double Quotation Mark
”	”	ASCII: Closing Double Quotation Mark
•	•	ASCII: Bullet
–	–	ASCII: Hyphen or En-dash
—	—	ASCII: Em-dash
˜	˜	ASCII: Tilde accent
™	™	ASCII: Trade Mark sign
š	š	ASCII: Latin Small Letter S Hacek
›	›	ASCII: Greater-Than sign
œ	œ	ASCII: Latin Small Letter OE

ž	ž
Ÿ	Ÿ	ASCII: Latin Capital Letter Y Umlaut

¡	¡	ASCII: Latin Small Letter I
¢	¢	ASCII: Cent
£	£	ASCII: Pound Sterling
¤	¤	ASCII: Currency sign
¥	¥	ASCII: Yen
¦	¦	ASCII: Latin Letter Pipe
§	§	ASCII: Section sign
¨	¨	ASCII: Umlaut accent
©	©	ASCII: Copyright sign
ª	ª	ASCII: Superscript Small Letter A
«	«	ASCII: Left Double-Angle Quotation Mark
¬	¬	ASCII: NOT (Math)
		ASCII: Hyphen
®	®	ASCII: Registered Name
¯	¯	ASCII: APL Overbar. Macron accent
°	°	ASCII: Ring accent
±	±	ASCII: Plus-Minus sign
²	²	ASCII: Superscript Numeral Two, Squared
³	³	ASCII: Superscript Numeral Three, Cubed
´	´	ASCII: Grave accent (?)
µ	µ	ASCII: Mu or Micro sign
¶	¶	ASCII: Paragraph or Pilcrow sign
·	·	ASCII: Middle Dot
¸	¸	ASCII: Cedilla Accent
¹	¹	ASCII: Superscript Numeral One
º	º	ASCII: Degree, Ring Accent
»	»	ASCII: Right Double-Angle Quotation Mark
¼	¼	ASCII: One Quarter
½	½	ASCII: One Half
¾	¾	ASCII: Three Quarters
¿	¿	ASCII: Turned Question Mark
À	À	ASCII: Capital Letter A Grave
Á	Á	ASCII: Latin Capital Letter A Acute
Â	Â	ASCII: Latin Capital Letter A Circumflex
Ã	Ã	ASCII: Latin Capital Letter A Tilde
Ä	Ä	ASCII: Latin Capital Letter A Umlaut
Å	Å	ASCII: Latin Capital Letter A Ring
Æ	Æ	ASCII: Latin Capital Letter AE
Ç	Ç	ASCII: Latin Capital Letter C Cedilla
È	È	ASCII: Latin Capital Letter E Grave
É	É	ASCII: Latin Capital Letter A Acute
Ê	Ê	ASCII: Latin Capital Letter E Circumflex
Ë	Ë	ASCII: Latin Capital Letter E Umlaut
Ì	Ì	ASCII: Latin Capital Letter I Grave
Í	Í	ASCII: Latin Capital Letter I Acute
Î	Î	ASCII: Latin Capital Letter I Circumflex
Ï	Ï	ASCII: Latin Capital Letter I Umlaut
Ð	Ð	ASCII: Latin Capital Letter Eth, D Bar
Ñ	Ñ	ASCII: Latin Capital Letter N Tilde
Ò	Ò	ASCII: Latin Capital Letter O Grave
Ó	Ó	ASCII: Latin Capital Letter O Acute
Ô	Ô	ASCII: Latin Capital Letter O Circumflex
Õ	Õ	ASCII: Latin Capital Letter O Tilde
Ö	Ö	ASCII: Latin Capital Letter O Umlaut
×	×	ASCII: Multiplication sign
Ø	Ø	ASCII: Greek Letter Phi
Ù	Ù	ASCII: Latin Capital Letter U Grave
Ú	Ú	ASCII: Latin Capital Letter U Acute
Û	Û	ASCII: Latin Capital Letter U Circumflex
Ü	Ü	ASCII: Latin Capital Letter U Umlaut
Ý	Ý	ASCII: Latin Capital Letter Y Acute
Þ	Þ	ASCII: Latin Small Letter Thorn
ß	ß	ASCII: Latin Small Letter Sharp S, Ess-Zed
à	à	ASCII: Latin Small Letter A Grave
á	á	ASCII: Latin Small Letter A Acute
â	â	ASCII: Latin Small Letter A Circumflex
ã	ã	ASCII: Latin Small Letter A Tilde
ä	ä	ASCII: Latin Small Letter A Umlaut
å	å	ASCII: Latin Small Letter A Ring
æ	æ	ASCII: Latin Small Letter AE
ç	ç	ASCII: Latin Small Letter C Cedilla
è	è	ASCII: Latin Small Letter E Grave
é	é	ASCII: Latin Small Letter E Acute
ê	ê	ASCII: Latin Small Letter E Circumflex
ë	ë	ASCII: Latin Small Letter E Umlaut
ì	ì	ASCII: Latin Small Letter I Grave
í	í	ASCII: Latin Small Letter I Acute
î	î	ASCII: Latin Small Letter I Circumflex
ï	ï	ASCII: Latin Small Letter I Umlaut
ð	ð	ASCII: Latin Small Letter Eth
ñ	ñ	ASCII: Latin Small Letter N Tilde
ò	ò	ASCII: Latin Small Letter O Grave
ó	ó	ASCII: Latin Small Letter O Acute
ô	ô	ASCII: Latin Small Letter O Circumflex
õ	õ	ASCII: Latin Small Letter O Tilde
ö	ö	ASCII: Latin Small Letter O Umlaut
÷	÷	ASCII: Division sign
ø	ø	ASCII: Greek Small Letter Phi
ù	ù	ASCII: Latin Small Letter U Grave
ú	ú	ASCII: Latin Small Letter U Acute
û	û	ASCII: Latin Small Letter U Circumflex
ü	ü	ASCII: Latin Small Letter U Umlaut
ý	ý	ASCII: Latin Small Letter Y Acute
þ	þ	ASCII: Latin Capital Letter Thorn
ÿ	ÿ	ASCII: Latin Small Letter Y Umlaut

How to set jQuery intellisense plugin onto VS 2008 ?

2010-10-30T10:19:00.000-07:00

This instruction is compliant with Windows 7.

1- Install VS 2008 SP1 , you can download it for free here.

2- After installation of SP1, restart windows

3- Then, install jQuery intellisense hotfix, you can download for free here. (KB958502)

4- Restart VS 2008.

5 - Add jQuery library and its vsdoc file to your application. You can download jQuery here and vsdoc for 1.4.2

Finally we can start to take advantage of jquery by adding reference to your code as shown below;

Generally accepted principles of software architecting

2010-10-26T01:25:00.000-07:00

SRP - The Single Responsibility Principle -
A class should have one, and only one, reason to change.

OCP - The Open Closed Principle -
You should be able to extend a classes behavior, without modifying it.

LSP - The Liskov Substitution Principle-
Derived classes must be substitutable for their base classes.

DIP - The Dependency Inversion Principle-
Depend on abstractions, not on concretions.

ISP - The Interface Segregation Principle-
Make fine grained interfaces that are client specific

Interface Declaration

2010-10-24T00:46:00.000-07:00

in Java:

public interface Report {

public void prepare(Document doc);

public void preview();

public void print(Document doc);

}

in C#:

public interface Report {

void prepare(Document doc);

void preview();

public void print(Document doc); // ! wrong , compiler throws error that " The modifier //'public' is not valid for this item"

}

Of course, modifiers are unneccesary in Interfaces, because of the classes have to implements methods of Interface, .net platform forces us to clean than unneccesary spesifications.

Replace Text Fields in Binary Data File

2010-10-06T23:53:00.000-07:00

/*
* @author Mucahid Uslu
* E-Mail: mucuslu@gmail.com
* Java Developer
*/

public static InputStream binaryReplace(File file, String oldStr, String newStr) {
RandomAccessFile raf=null;
List nchars=new ArrayList();
try {
raf = new RandomAccessFile(file, "r");
long high = file.length();

long p = 0; // baslangic pos
long x=0; // kacinci byte uzerinde
long sline=0; // kacinci satirda
while (x <>= x) {
raf.seek(p);
char c = (char) raf.readByte();
if (c == '\n') {
raf.skipBytes((int)p);
x=p;
sline++;
System.out.println("Line no:"+sline+" char no: "+ p);
nchars.add(p);
p++;
break;
}
p++;
}
}
raf.close();
} catch (IOException e) {
try {
raf.close();
} catch (IOException f) {
// TODO
}
}

ByteBuffer bufContent = ByteBuffer.allocate(2*(int)file.length()); // thats enough space to //replace some text fields, if you append additional data, you should have allocate more.. M.U.

String newLine=null;
InputStream in=null;
byte[] sbyte=null;
long size=0;
long off=0;
long endLine=0;

try {
in = new java.io.FileInputStream(file);
} catch (FileNotFoundException e) {
// TODO
}

ListIterator nlist = nchars.listIterator();
try {
while(nlist.hasNext()){
endLine=(Long)nlist.next();
size=endLine-off;
sbyte=new byte[(int)size];
in.read(sbyte, 0, (int)size);
newLine=new String(sbyte);
if(newLine.indexOf(newStr)>0){
newLine=newLine.replaceAll(oldStr,newStr);
bufContent.put(newLine.getBytes());
}else{
bufContent.put(sbyte);
}
off=endLine;
}
} catch (IOException e) {
// TODO
}
bufContent.position(0);
return ByteBufferToInputStream(bufContent);

}

private static InputStream ByteBufferToInputStream(final ByteBuffer buf) { // M.U.
return new InputStream() {
public synchronized int read() throws IOException {
return buf.hasRemaining() ? buf.get() : -1;
}

public synchronized int read(byte[] bytes, int off, int len) throws IOException {
int rv = Math.min(len, buf.remaining());
buf.get(bytes, off, rv);
return rv == 0 ? -1 : rv;
}
};
}

Java Swing - Look And Feel

2010-09-28T08:10:00.000-07:00

1- (system default) UIManager.setLookAndFeel( UIManager.getSystemLookAndFeelClassName() );

2- (windows) UIManager.setLookAndFeel( "com.sun.java.swing.plaf.windows.WindowsLookAndFeel" );

3- (metal) UIManager.setLookAndFeel( "javax.swing.plaf.metal.MetalLookAndFeel" );

SpringSource Update Site for Eclipse

2010-09-22T02:02:00.000-07:00

Verify that the dialog list the following update sites as enabled

Eclipse 3.5

• Galileo
(http://download.eclipse.org/releases/galileo)
• SpringSource Update Site for Eclipse 3.5 (Snapshot)
(http://dist.springsource.com/snapshot/TOOLS/update/e3.5)
• SpringSource Update Site for Eclipse 3.5 (Snapshot, Dependencies)
(http://dist.springsource.com/snapshot/TOOLS/composite/e3.5)

Eclipse 3.6

• Helios
(http://download.eclipse.org/releases/helios)
• SpringSource Update Site for Eclipse 3.6 (Snapshot)
(http://dist.springsource.com/snapshot/TOOLS/update/e3.6)
• SpringSource Update Site for Eclipse 3.6 (Snapshot, Dependencies)
(http://dist.springsource.com/snapshot/TOOLS/composite/e3.6)
h. If those update sites are correctly listed close the preference

What is the difference between CLOB and BLOB ?

2010-07-28T23:42:00.000-07:00

A BLOB is a binary large object, and a CLOB is a
character large object. The difference between characters and bytes is the
Character set, i.e. the mapping between a character and the byte sequence
it represents.
- With a blob, you have to use the right character set to retrive the data,
e.g. if someone writes a text into a BLOB using UTF-8 and you read it back
using ISO-8859-1, you do not get the same string back out.
- With a CLOB, the database takes care of the character set, you supply a
String, and you get a String back, and you do not have to worry about which
bytes are used to represent the characters. in fact, you do not have access
to the byte represetnation, so its uselessi if you want to store bytes.

So in any other database, if you want to store large text, use a CLOB, if
you want to store an image, use a BLOB.

Having said this, it seems to me (although I did not research it) that the
Oracle drivers specify a default character set even for BLOBs, the method
oracle.sql.BLOB.characterStreamValue() seems to do this(I never used it).
So a Oracle BLOB can also be used with CLOB functionality. Looking at the
jdbc specification, this seems to be a oracle-specific extension. It seems
tom me that it is only a oracle-specific _jdbc_ extension. E.g. you cannot
display a BLOB on console, whereas you can display a CLOB.

So the short answer is, if you only use an oracle database and only use
oracle jdbc, you can also use BLOBs for text. If you want other access
(e.g. sqlplus(console)) access to the text you stored, use a CLOB.
I would consider it cleaner if one would always use a CLOB for text (Rather
rely on standards as opposed to vendor-specific extensions)

How To Run A Process in C# .Net

2009-06-18T00:51:00.001-07:00

String cmdString = @"net use /delete " + mapdrive; // just a sample script, custom here..

ManagementClass processClass = new ManagementClass("Win32_Process");

object[] methodArgs = { cmdString, null, null, 0 };

object result = processClass.InvokeMethod("Create", methodArgs);

Fix Debugging Problem On Forms 10g

2009-05-13T04:20:00.000-07:00

If you work at shared library path and forms path has been registered in windows registry,

it unable to debug because forms path defined in \forms\server\default.env file

find and comment line like that

#FORMS_PATH=C:\ORA10G\forms

then restart oc4j server and forms developer ,

then it works as you see.

Generate Random Alpha-Numeric Values (C#.Net)

2009-05-05T00:27:00.000-07:00

private string GenerateRandomChars() {
Random rnd = new Random();
byte[] _byt=new byte[8];
rnd.NextBytes(_byt);
return Convert.ToBase64String(_byt);
}

Adf Nedir?

2009-04-01T01:38:00.000-07:00

Oracle ADF

Oracle'ın özellikle Forms uygulamalarını yeni nesil web tabanlı teknolojilere yükseltmek için geliştirdiği framework.

Mimari olarak MVC - Model View Controller, kullanıcı arayüzünde 11g sürümü ile birlikte RichClient library'ye geçişin gözlendiği, yazılım bileşenlerinin kendi içerisinde ajax özelliği taşıması, bileşen kütüphanesinin yaygınlaşması ve gelişebilmesi için kaynak kodlarının Apache ile paylaşıldığı ve neticesinde Apache Trinidad MyFaces Component kütüphanesine ait bileşenlerin de kullanılabildiği, Oracle 'ın uygulama geliştirme alanındaki geliştirmesine bu yönde devam etme kararı aldığı, bir java framework'üdür.

Model katmanında kullanılabilen Oracle Business Components sayesinde kod yazmadan dahi uygulama geliştirme mümkün. Öte yandan java tabanlı olduğu için platformdan bağımsız bir IDE + Uygulama Sunucusu imkanı sunuyor.

Uygulama sunucusu olarak WebLogic kullanılmakta.

Bu konu hakkında Oracle'ın resmi sitesinde pekçok kaynak bulmak mümkün, ayrıca şu blog sitelerinden yararlanılabilir;

-US- [1] -NL- [2] -TR- [adf]

Samples - ADF How to

2009-03-01T23:34:00.000-08:00

How to do page redirect in managed bean

How to set session invalid

How to get session parameters

How to set session parameters

How to set parameter value of stored procedure in managed bean

Using Programmatic View Objects for Alternative Data Sources

How to Create a View Object on a REF CURSOR

SQL Tracing in an Application Module

How to execute a stored procedure in oracle adf ?

WEBLOGIC 10.3 and ADF Installation

JSEXT

2009-01-17T12:48:00.000-08:00

Server Side Javascript, jsx extension

JSEXT

Some popular Ajax Toolkits

2009-01-16T01:36:00.000-08:00

Some popular Ajax Toolkits

Name	Client/Server	High/Low-level	Comments
Prototype (http://prototypejs.org)	Client	Low	Remodels and extends JavaScript following the Ruby scripting language. Many features for arrays, functions, XHR, DOM and forms.
Scriptaculous (http://script.aculo.us)	Client	High	Special effects, drag and drop, and widgets built on top of prototype.
dojo (http://dojotoolkit.org)	Client	Low-high	Comprehensive set of libraries covering everything from packaging & language features through Ajax to UI widgets.
Yahoo User Interface (YUI) (http://developer.yahoo.com/yui/)	Client	Low-high	Another comprehensive set of libraries covering many aspects of Ajax development.
Ext (http://extjs.com)	Client	High	Widget-based set of user interface components with Ajax support.
sarissa (http://sarissa.sf.net)	Client	Low	Rich library for working with XML, providing cross-browser XPath and XSLT.
Mochikit (http://mochikit.com)	Client	Low-high	General-purpose Ajax and DHTML library, inspired by Python.
jQuery (http://jquery.com)	Client	Low	Small, concise Ajax and DOM helper library.
MooTools (http://mootools.net)	Client	Low-high	Modular library covering everything from core classes to special effects. A promising newcomer.
Ruby on Rails (http://www.rubyonrails.org)	Server	Low-high	Primarily a server-side toolkit, but has first-rate support for Ajax, using Prototype and Scriptaculous. Allows large parts of the client tier to be written on the server, in Ruby.
GWT (http://code.google.com/webtoolkit)	Client	High	Java framework that allows Ajax client tier to be written in Java.
JSF (various vendors)	Server	High	Various JSF vendors have Ajax-enabled some of their components, again allowing some Ajax functionality without hand-writing JavaScript.

AJAX - Get Started

2009-01-16T01:15:00.000-08:00

The standard way to do Ajax is to use the XMLHttpRequest object, known as XHR by its friends. Use XHR directly, or via one of the helpful Ajax libraries such as Prototype or jQuery. How do we use XHR “by hand”? To start with, we need to get a reference to it:

if (window.XMLHttpRequest) {

xhr = new XMLHttpRequest();

} else if (window.ActiveXObject) {

xhr = new ActiveXObject(“Microsoft.XMLHTTP”);

}

We can then open a connection to a URL:

Specify a callback function to receive the response:

and then send the request:

The server may be busy, or the network may be slow. We don’t want to sit around doing nothing until the response arrives, and because we’ve assigned the callback function, we don’t have to. That’s the five-minute guide for the impatient. For those who like to know the details, we’ve listed the fuller details of the XHR object below.

xhr.open(

“GET”,

“my-dynamic-content.jsp?id=”

+encodeURI(myId),

true

);

xhr.onreadystatechange = function(){

processReqChange(req);

}

xhr.send(null);

Method Name	Parameters and Descriptions
open(method, url, async)	open a connection to a URL method = HTTP verb (GET, POST, etc.) url = url to open, may include querystring async = whether to make asynchronous request
onreadystatechange	assign a function object as callback (similar to onclick, onload, etc. in browser event model)
setRequestHeader(namevalue)	add a header to the HTTP request
send(body)	send the request body = string to be used as request body
abort()	stop the XHR from listening for the response
readyState	stage in lifecycle of response (only populated after send() is called)
httpStatus	The HTTP return code (integer, only populated after response reaches the loaded state)
responseText	body of response as a JavaScript string (only set after response reaches the interactive readyState)
responseXML	body of the response as a XML document object (only set after response reaches the interactive readyState)
getResponseHeader(name)	read a response header by name
getAllResponseHeaders()	Get an array of all response header names

James Cahill: Christmas blog

2008-12-30T12:51:00.000-08:00

James Cahill: Christmas blog

Weblogic 10.3 Install and configuration for ADF Applications

2008-11-05T23:56:00.000-08:00

Follow setup gui, after complete start quick launch, the server will be configured default weblogic user and password has been set weblogic.
Before deploy your adf application, add these libraries to

wlserver_10. 3/common/ deployable-libraries/

and install the libraries.

- adf.oracle.domain.ear
- jsf-ri-12. war
- jstl-1. 2. war

Now, it is ready to install your adf application.

Also you can create a jdbc data source at following menu,

Services/JDBC/Data Sources/

Also look at: http://adf.webloji.net

Mücahid Uslu

Easily ftp access with Java

2008-10-15T05:45:00.000-07:00

I'd like to share at following code that my java class which contains ftp download and upload methods. Hope to enjoy it!

Note: Here the buffer has been set to 32MB (33554432), It is recommended to set it dynmically depend on the file size in your code.

package muco;

import java.io.*;
import java.net.*;

public class FTPClient {
public final String host;
public final String user;
protected final String password;
protected URLConnection urlc;
public FTPClient(String _host, String _user, String _password) {
host= _host; user= _user; password= _password;
urlc = null;
}
private URL makeURL(String targetfile) throws MalformedURLException {
if (user== null)
return new URL("ftp://"+ host+ "/"+ targetfile+ ";type=i");
else
return new URL("ftp://"+ user+ ":"+ password+ "@"+ host+ "/"+ targetfile+ ";type=i");
}
protected InputStream openDownloadStream(String targetfile) throws Exception {
URL url= makeURL(targetfile);
urlc = url.openConnection();
InputStream is = urlc.getInputStream();
return is;
}
protected OutputStream openUploadStream(String targetfile) throws Exception {
URL url= makeURL(targetfile);
urlc = url.openConnection();
OutputStream os = urlc.getOutputStream();
return os;
}
protected void close() {
urlc= null;
}
public void Upload(String _localfile, String _targetfile) {
try {
OutputStream os= openUploadStream(_targetfile);
FileInputStream is= new FileInputStream(_localfile);
byte[] buf= new byte[33554432];
int c;
while (true) {
//System.out.print(".");
c= is.read(buf);
if (c<= 0) break;
//System.out.print("[");
os.write(buf, 0, c);
//System.out.print("]");
}
os.close();
is.close();
close();
}catch(Exception E) {
System.err.println(E.getMessage());
E.printStackTrace();
}
}
public void Download(
String _localfile, String _targetfile) {
try {
InputStream is= openDownloadStream(_targetfile);
FileOutputStream os= new FileOutputStream(_localfile);
byte[] buf= new byte[33554432];
int c;
while (true) {
c= is.read(buf);
if (c<= 0) break;
os.write(buf, 0, c);
}
is.close();
os.close();
close();
}catch(Exception E) {
System.err.println(E.getMessage());
E.printStackTrace();
}
}
}

ADF Faces / Access to Data Model from Backing/Managed Bean

2008-05-23T07:40:00.001-07:00

import javax.faces.application.Application;
import javax.faces.context.FacesContext;

import oracle.binding.OperationBinding;
import oracle.adf.model.binding.DCBindingContainer;
import oracle.adf.model.binding.DCDataControl;
import oracle.adf.model.binding.DCIteratorBinding;

import oracle.adf.view.faces.component.core.data.CoreTable;

import oracle.adf.view.faces.context.AdfFacesContext;

import oracle.binding.BindingContainer;

import oracle.jbo.ApplicationModule;

import oracle.jbo.Row;
import oracle.jbo.RowSet;
import oracle.jbo.server.EntityImpl;
import oracle.jbo.RowSetIterator;
import oracle.jbo.ViewObject;
import oracle.jbo.server.ViewRowImpl;
import oracle.jbo.uicli.binding.JUCtrlValueBindingRef;

public class ManagedBeanBase {

/**
* Contains page binding references
* This can be populated manually or
* automatically based on config setting
* in faces-config.xml
*
* This is a sample of an entry you would put in
* the faces-config.xml file. Notice the 'managed-property'
* tag with property name 'bindings'. This property will be
* set by the faces servlet using the setBindings method below.
*
*
* MyPageBackingBean
* MyPageMB
* request
*
* bindings
* #{bindings}
*
*
*/
*/
protected BindingContainer bindings;

public ManagedBeanBase() {
}

public BindingContainer getBindings() {

return this.bindings;
}

public void setBindings(BindingContainer bindings) {
this.bindings = bindings;
}

/**
* Use this to manually set page bindingings.
*/
public void setBindings(){
FacesContext context = FacesContext.getCurrentInstance();
Application app = context.getApplication();
bindings = (DCBindingContainer) app.getVariableResolver().resolveVariable(context, "bindings");
}

/**
* Call this method to refresh the binding container
* with any changes.
*/
protected void refreshBindingContainer(){

DCBindingContainer dcBind = (DCBindingContainer)bindings;
dcBind.refresh();

}

/**
* This method is used the removed the currently selected
* row from and ADF (JSF) table. The method requires
* that the table object be passed in as a parameter.
*/
protected void deleteSelectedRow(CoreTable pageTable){

JUCtrlValueBindingRef rwData = (JUCtrlValueBindingRef)pageTable.getSelectedRowData();

Row rw = rwData.getRow();

rw.remove();

}

/**
* This method takes the name of a given iterator (as defined in the page def file)
* and returns the current rowset.
*/
protected RowSetIterator getRowSetIterator(String p_iterator){

DCBindingContainer dcBind = (DCBindingContainer)bindings;
DCIteratorBinding iterBind= (DCIteratorBinding)dcBind.get(p_iterator);

return iterBind.getLovRowSetIterator();

}

/**
* This method will return the ViewObject (object) associated
* with a given iterator.
*/
protected ViewObject getViewObjectFromIterator(String p_iterator){

DCBindingContainer dcBind = (DCBindingContainer)bindings;
DCIteratorBinding iterBind= (DCIteratorBinding)dcBind.get(p_iterator);

return iterBind.getViewObject();

}

/**
* This method will execute the query associated the view object
* with which the iterator is associated.
*/
protected void executeIterQuery(String p_iterator){

DCBindingContainer dcBind = (DCBindingContainer)bindings;

DCIteratorBinding iterBind= (DCIteratorBinding)dcBind.get(p_iterator);

iterBind.executeQuery();

}

/**
* This method issues a rollback again the current transaction.
*/
protected void rollbackCurrentChanges(){

DCBindingContainer dcBind = (DCBindingContainer)bindings;
dcBind.getDataControl().getApplicationModule().getTransaction().rollback();

}

/**
* Manually add a page component to the partial target list
* for partial page refresh.
*/
protected void addPartialTarget(UIComponent p_target_object){
AdfFacesContext.getCurrentInstance().addPartialTarget(p_target_object);
}

}

Links:

http://adf.webloji.net/

2008-05-23T07:40:00.000-07:00

An ADF Faces Base Class for a Backing/Managed Bean

Over the last few months, I've been working on an ADF based project for my current employer. The project is my first venture into JSF and ADF. In this time I've developed a little base class that I extend when creating a backing bean (or managed bean) for my pages. The base class contains several helpful utility methods that I thought I would share. Some of these I discovered for myself, and a few others were inspired by samples provided by folks like: Steve Muench, Frank Nimphius, and Jonas Jacobi. I have put the code below. Each method has a comment at the top to explain what the method does:

The Code ...

import javax.faces.application.Application;
import javax.faces.context.FacesContext;

import oracle.binding.OperationBinding;
import oracle.adf.model.binding.DCBindingContainer;
import oracle.adf.model.binding.DCDataControl;
import oracle.adf.model.binding.DCIteratorBinding;

import oracle.adf.view.faces.component.core.data.CoreTable;

import oracle.adf.view.faces.context.AdfFacesContext;

import oracle.binding.BindingContainer;

import oracle.jbo.ApplicationModule;

import oracle.jbo.Row;
import oracle.jbo.RowSet;
import oracle.jbo.server.EntityImpl;
import oracle.jbo.RowSetIterator;
import oracle.jbo.ViewObject;
import oracle.jbo.server.ViewRowImpl;
import oracle.jbo.uicli.binding.JUCtrlValueBindingRef;

public class ManagedBeanBase {

/**
* Contains page binding references
* This can be populated manually or
* automatically based on config setting
* in faces-config.xml
*
* This is a sample of an entry you would put in
* the faces-config.xml file. Notice the 'managed-property'
* tag with property name 'bindings'. This property will be
* set by the faces servlet using the setBindings method below.
*
*
* MyPageBackingBean
* MyPageMB
* request
*
* bindings
* #{bindings}
*
*
*/
*/
protected BindingContainer bindings;

public ManagedBeanBase() {
}

public BindingContainer getBindings() {

return this.bindings;
}

public void setBindings(BindingContainer bindings) {
this.bindings = bindings;
}

/**
* Use this to manually set page bindingings.
*/
public void setBindings(){
FacesContext context = FacesContext.getCurrentInstance();
Application app = context.getApplication();
bindings = (DCBindingContainer) app.getVariableResolver().resolveVariable(context, "bindings");
}

/**
* Call this method to refresh the binding container
* with any changes.
*/
protected void refreshBindingContainer(){

DCBindingContainer dcBind = (DCBindingContainer)bindings;
dcBind.refresh();

}

/**
* This method is used the removed the currently selected
* row from and ADF (JSF) table. The method requires
* that the table object be passed in as a parameter.
*/
protected void deleteSelectedRow(CoreTable pageTable){

JUCtrlValueBindingRef rwData = (JUCtrlValueBindingRef)pageTable.getSelectedRowData();

Row rw = rwData.getRow();

rw.remove();

}

/**
* This method takes the name of a given iterator (as defined in the page def file)
* and returns the current rowset.
*/
protected RowSetIterator getRowSetIterator(String p_iterator){

DCBindingContainer dcBind = (DCBindingContainer)bindings;
DCIteratorBinding iterBind= (DCIteratorBinding)dcBind.get(p_iterator);

return iterBind.getLovRowSetIterator();

}

/**
* This method will return the ViewObject (object) associated
* with a given iterator.
*/
protected ViewObject getViewObjectFromIterator(String p_iterator){

DCBindingContainer dcBind = (DCBindingContainer)bindings;
DCIteratorBinding iterBind= (DCIteratorBinding)dcBind.get(p_iterator);

return iterBind.getViewObject();

}

/**
* This method will execute the query associated the view object
* with which the iterator is associated.
*/
protected void executeIterQuery(String p_iterator){

DCBindingContainer dcBind = (DCBindingContainer)bindings;

DCIteratorBinding iterBind= (DCIteratorBinding)dcBind.get(p_iterator);

iterBind.executeQuery();

}

/**
* This method issues a rollback again the current transaction.
*/
protected void rollbackCurrentChanges(){

DCBindingContainer dcBind = (DCBindingContainer)bindings;
dcBind.getDataControl().getApplicationModule().getTransaction().rollback();

}

/**
* Manually add a page component to the partial target list
* for partial page refresh.
*/
protected void addPartialTarget(UIComponent p_target_object){
AdfFacesContext.getCurrentInstance().addPartialTarget(p_target_object);
}

}

Programmatic View Object / Using Ref Cursor / Using Static Data

2008-05-22T23:08:00.000-07:00

27.8.1 How to Create a Read-Only Programmatic View Object

To create a read-only programmatic view object, use the Create View Object wizard and follow these steps:

1.

In step 1 on the Name panel, provide a name and package for the view object. In the What kind of data do you need this view object to manage? radio group, select Rows Populated Programmatically, not Based on a Query
2.

In step 2 on the Attributes panel, click New one or more times to define the view object attributes your programmatic view object requires.
3.

In step 3 on the Attribute Settings panel, adjust any setting you may need to for the attributes you defined.
4.

In step 4 on the Java panel, enable a custom view object class to contain your code.
5.

Click Finish to create the view object.

In your view object's custom Java class, override the methods described in Section 27.8.3, "Key Framework Methods to Override for Programmatic View Objects" to implement your custom data retrieval strategy.
27.8.2 How to Create an Entity-Based Programmatic View Object

To create a entity-based view object with programmatic data retrieval, create the view object in the normal way, enable a custom Java class for it, and override the methods described in the next section to implement your custom data retrieval strategy.
27.8.3 Key Framework Methods to Override for Programmatic View Objects

A programmatic view object typically overrides all of the following methods of the base ViewObjectImpl class to implement its custom strategy for retrieving data:

*

create()

This method is called when the view object instance is created and can be used to initialize any state required by the programmatic view object. At a minimum, this overridden method will contain the following lines to ensure the programmatic view object has no trace of a SQL query related to it:

// Wipe out all traces of a query for this VO
getViewDef().setQuery(null);
getViewDef().setSelectClause(null);
setQuery(null);

*

executeQueryForCollection()

This method is called whenever the view object's query needs to be executed (or re-executed).
*

hasNextForCollection()

This method is called to support the hasNext() method on the row set iterator for a row set created from this view object. Your implementation returns true if you have not yet exhausted the rows to retrieve from your programmatic data source.
*

createRowFromResultSet()

This method is called to populate each row of "fetched" data. Your implementation will call createNewRowForCollection() to create a new blank row and then populateAttributeForRow() to populate each attribute of data for the row.
*

getQueryHitCount()

This method is called to support the getEstimatedRowCount() method. Your implementation returns a count, or estimated count, of the number of rows that will be retrieved by the programmatic view object's query.
*

protected void releaseUserDataForCollection()

Your code can store and retrieve a user data context object with each row set. This method is called to allow you to release any resources that may be associated with a row set that is being closed.

Since the view object component can be related to several active row sets at runtime, many of the above framework methods receive an Object parameter named qc in which the framework will pass the collection of rows in question that your code is supposed to be filling, as well as the array of bind variable values that might affect which rows get populated into the specific collection.

You can store a user-data object with each collection of rows so your custom datasource implementation can associate any needed datasource context information. The framework provides the setUserDataForCollection() and getUserDataForCollection() methods to get and set this per-collection context information. Each time one of the overridden framework methods is called, you can use the getUserDataForCollection() method to retrieve the correct ResultSet object associated with the collection of rows the framework wants you to populate.

The examples in the following sections each override these methods to implement different kinds of programmatic view objects.
27.8.4 How to Create a View Object on a REF CURSOR

Sometimes your application might need to work with the results of a query that is encapsulated within a stored procedure. PL/SQL allows you to open a cursor to iterate through the results of a query, and then return a reference to this cursor to the client. This so-called REF CURSOR is a handle with which the client can then iterate the results of the query. This is possible even though the client never actually issued the original SQL SELECT statement.

Note:
The examples in this section refer to the ViewObjectOnRefCursor project in the AdvancedViewObjectExamples workspace. See the note at the beginning of this chapter for download instructions. Run the CreateRefCursorPackage.sql script in the Resources folder against the SRDemo connection to set up the additional database objects required for the project.

Declaring a PL/SQL package with a function that returns a REF CURSOR is straightforward. For example, your package might look like this:

CREATE OR REPLACE PACKAGE RefCursorExample IS
TYPE ref_cursor IS REF CURSOR;
FUNCTION get_requests_for_tech(p_email VARCHAR2) RETURN ref_cursor;
FUNCTION count_requests_for_tech(p_email VARCHAR2) RETURN NUMBER;
END RefCursorExample;

After defining an entity-based RequestForTech view object with an entity usage for a ServiceRequest entity object, go to its custom Java class RequestForTechImpl.java. At the top of the view object class, define some constant Strings to hold the anonymous blocks of PL/SQL that you'll execute using JDBC CallableStatement objects to invoke the stored functions:

/*
* Execute this block to retrieve the REF CURSOR
*/
private static final String SQL =
"begin ? := RefCursorSample.getEmployeesForDept(?);end;";
/*
* Execute this block to retrieve the count of service requests that
* would be returned if you executed the statement above.
*/
private static final String COUNTSQL =
"begin ? := RefCursorSample.countEmployeesForDept(?);end;";

Then, override the methods of the view object as described in the following sections.
27.8.4.1 The Overridden create() Method

The create() method removes all traces of a SQL query for this view object.

protected void create() {
getViewDef().setQuery(null);
getViewDef().setSelectClause(null);
setQuery(null);
}

27.8.4.2 The Overridden executeQueryForCollection() Method

The executeQueryForCollection() method calls a helper method retrieveRefCursor() to execute the stored function and return the REF CURSOR return value, cast as a JDBC ResultSet. Then, it calls the helper method storeNewResultSet() that uses the setUserDataForCollection() method to store this ResultSet with the collection of rows for which the framework is asking to execute the query.

protected void executeQueryForCollection(Object qc,Object[] params,
int numUserParams) {
storeNewResultSet(qc,retrieveRefCursor(qc,params));
super.executeQueryForCollection(qc, params, numUserParams);
}

The retrieveRefCursor() uses the helper method described in Section 25.5, "Invoking Stored Procedures and Functions" to invoke the stored function and return the REF CURSOR:

private ResultSet retrieveRefCursor(Object qc, Object[] params) {
ResultSet rs = (ResultSet)callStoredFunction(OracleTypes.CURSOR,
"RefCursorExample.get_requests_for_tech(?)",
new Object[]{getNamedBindParamValue("Email",params)});
return rs ;
}

27.8.4.3 The Overridden createRowFromResultSet() Method

For each row that the framework needs fetched from the datasource, it will invoke your overridden createRowFromResultSet() method. The implementation retrieves the collection-specific ResultSet object from the user-data context, uses the createNewRowForCollection() method to create a new blank row in the collection, and then use the populateAttributeForRow() method to populate the attribute values for each attribute defined at design time in the View Object Editor.

protected ViewRowImpl createRowFromResultSet(Object qc, ResultSet rs) {
/*
* We ignore the JDBC ResultSet passed by the framework (null anyway) and
* use the resultset that we've stored in the query-collection-private
* user data storage
*/
rs = getResultSet(qc);

/*
* Create a new row to populate
*/
ViewRowImpl r = createNewRowForCollection(qc);
try {
/*
* Populate new row by attribute slot number for current row in Result Set
*/
populateAttributeForRow(r,0, rs.getLong(1));
populateAttributeForRow(r,1, rs.getString(2));
populateAttributeForRow(r,2, rs.getString(3));
}
catch (SQLException s) {
throw new JboException(s);
}
return r;
}

27.8.4.4 The Overridden hasNextForCollectionMethod()

The overridden implementation of the framework method hasNextForCollection() has the responsibility to return true or false based on whether there are more rows to fetch. When you've hit the end, you call the setFetchCompleteForCollection() to tell view object that this collection is done being populated.

protected boolean hasNextForCollection(Object qc) {
ResultSet rs = getResultSet(qc);
boolean nextOne = false;
try {
nextOne = rs.next();
/*
* When were at the end of the result set, mark the query collection
* as "FetchComplete".
*/
if (!nextOne) {
setFetchCompleteForCollection(qc, true);
/*
* Close the result set, we're done with it
*/
rs.close();
}
}
catch (SQLException s) {
throw new JboException(s);
}
return nextOne;
}

27.8.4.5 The Overridden releaseUserDataForCollection() Method

Once the collection is done with its fetch-processing, the overridden releaseUserDataForCollection() method gets invoked and closes the ResultSet cleanly so no database cursors are left open.

protected void releaseUserDataForCollection(Object qc, Object rs) {
ResultSet userDataRS = getResultSet(qc);
if (userDataRS != null) {
try {
userDataRS.close();
}
catch (SQLException s) {
/* Ignore */
}
}
super.releaseUserDataForCollection(qc, rs);
}

27.8.4.6 The Overridden getQueryHitCount() Method

Lastly, in order to properly support the view object's getEstimatedRowCount() method, the overridden getQueryHitCount() method returns a count of the rows that would be retrieved if all rows were fetched from the row set. Here the code uses a CallableStatement to get the job done. Since the query is completely encapsulated behind the stored function API, the code also relies on the PL/SQL package to provide an implementation of the count logic as well to support this functionality.

public long getQueryHitCount(ViewRowSetImpl viewRowSet) {
Object[] params = viewRowSet.getParameters(true);
BigDecimal id = (BigDecimal)params[0];
CallableStatement st = null;
try {
st = getDBTransaction().createCallableStatement(COUNTSQL,
DBTransaction.DEFAULT);
/*
* Register the first bind parameter as our return value of type CURSOR
*/
st.registerOutParameter(1,Types.NUMERIC);
/*
* Set the value of the 2nd bind variable to pass id as argument
*/
if (id == null) st.setNull(2,Types.NUMERIC);
else st.setBigDecimal(2,id);
st.execute();
return st.getLong(1);
}
catch (SQLException s) {
throw new JboException(s);
}
finally {try {st.close();} catch (SQLException s) {}}
}

27.8.5 Populating a View Object from Static Data

The SRDemo application's SRStaticDataViewObjectImpl class in the FrameworkExtensions project provides a programmatic view object implementation you can extend to populate code and description "lookup" data from static data in an in-memory array.

As shown in Example 27-29, it performs the following tasks in its overridden implementation of the key programmatic view object methods:

*

create()

When the view object is created, the data is loaded from the in-memory array. It calls a helper method to set up the codesAndDescriptions array of codes and descriptions and wipes out all traces of a query for this view object.
*

executeQueryForCollection()

Since the data is static, you don't really need to perform any query, but you still need to call the super to allow other framework setup for the row set to be done correctly. Since the code nulls out of traces of a query in the create() method, the view object won't actually perform any query during the call to super.
*

hasNextForCollection()

The code returns true if the fetchPosition is still less than the number of rows in the in-memory array
*

createRowFromResultSet()

Populates the "fetched" data for one row when the base view object implementation asks it to. It gets the data from the codesAndDescriptions array to populate the first and second attributes in the view object row (by zero-based index position).
*

getQueryHitCount()

The code returns the number of "rows" in the codesAndDescriptions array that was previously stored in the rows member field.

In addition, the following other methods help get the data setup:

*

setFetchPos()

Sets the current fetch position for the query collection. Since one view object can be used to create multiple row sets, you need to keep track of the current fetch position of each rowset in its "user data" context. It calls the setFetchCompleteForCollection() to signal to the view object that it's done fetching rows.
*

getFetchPos()

Get the current fetch position for the query collection. This returns the fetch position for a given row set that was stored in its user data context.
*

initializeStaticData()

Subclasses override this method to initialize the static data for display.
*

setCodesAndDescriptions()

Sets the static code and description data for this view object.

Example 27-29 Custom View Object Class to Populate Data from a Static Array

package oracle.srdemo.model.frameworkExt;
// Imports omitted
public class SRStaticDataViewObjectImpl extends SRViewObjectImpl {
private static final int CODE = 0;
private static final int DESCRIPTION = 1;
int rows = -1;
private String[][] codesAndDescriptions = null;

protected void executeQueryForCollection(Object rowset, Object[] params,
int noUserParams) {
// Initialize our fetch position for the query collection
setFetchPos(rowset, 0);
super.executeQueryForCollection(rowset, params, noUserParams);
}
// Help the hasNext() method know if there are more rows to fetch or not
protected boolean hasNextForCollection(Object rowset) {
return getFetchPos(rowset) < rows;
}
// Create and populate the "next" row in the rowset when needed
protected ViewRowImpl createRowFromResultSet(Object rowset,ResultSet rs) {
ViewRowImpl r = createNewRowForCollection(rowset);
int pos = getFetchPos(rowset);
populateAttributeForRow(r, 0, codesAndDescriptions[pos][CODE]);
populateAttributeForRow(r, 1, codesAndDescriptions[pos][DESCRIPTION]);
setFetchPos(rowset, pos + 1);
return r;
}
// When created, initialize static data and remove trace of any SQL query
protected void create() {
super.create();
// Setup string arrays of codes and values from VO custom properties
initializeStaticData();
rows = (codesAndDescriptions != null) ? codesAndDescriptions.length : 0;
// Wipe out all traces of a query for this VO
getViewDef().setQuery(null);
getViewDef().setSelectClause(null);
setQuery(null);
}
// Return the estimatedRowCount of the collection
public long getQueryHitCount(ViewRowSetImpl viewRowSet) {
return rows;
}
// Subclasses override this to initialize their static data
protected void initializeStaticData() {
setCodesAndDescriptions(new String[][]{
{"Code1","Description1"},
{"Code2","Description2"}
});
}
// Allow subclasses to initialize the codesAndDescriptions array
protected void setCodesAndDescriptions(String[][] codesAndDescriptions) {
this.codesAndDescriptions = codesAndDescriptions;
}
// Store the current fetch position in the user data context
private void setFetchPos(Object rowset, int pos) {
if (pos == rows) {
setFetchCompleteForCollection(rowset, true);
}
setUserDataForCollection(rowset, new Integer(pos));
}
// Get the current fetch position from the user data context
private int getFetchPos(Object rowset) {
return ((Integer)getUserDataForCollection(rowset)).intValue();
}
}

27.8.5.1 Basing Lookup View Object on SRStaticDataViewObjectImpl

The ServiceRequestStatusList view object in the SRDemo application defines two String attributes named Code and Description, and extends the SRStaticDataViewObjectImpl class. It overrides the initializeStaticData() method to supply the values of the legal service request status codes:

public class ServiceRequestStatusListImpl
extends SRStaticDataViewObjectImpl {
protected void initializeStaticData() {
setCodesAndDescriptions(new String[][]{
{"Open","Open"},
{"Pending","Pending"},
{"Closed","Closed"}
});
}
}

27.8.5.2 Creating a View Object Based on Static Data from a Properties File

Rather than compiling the static data for a view object into the Java class itself, it can be convenient to externalize it into a standard Java properties file with a Name=Value format like this:

#This is the property file format. Comments like this are ok
US=United States
IT=Italy

The SRPropertiesFileViewObjectImpl in the SRDemo application extends SRStaticDataViewObjectImpl to override the initializeStaticData() method and invoke the loadDataFromPropertiesFile() method shown in Example 27-30 to read the static data from a properties file. This method does the following basic steps:

1.

Derives the property file name based on the view definition name.

For example, a CountryList view object in a x.y.z.queries package that extends this class would expect to read the properties file named ./x/y/z/queries/CountryList.properties file.
2.

Initializes a list to hold the name=value pairs.
3.

Opens an input stream to read the properties file from the class path.
4.

Loops over each line in the properties file.
5.

If line contains and equals sign and is not a comment line that begins with a hash, then add a string array of {code,description} to the list.
6.

Closes the line number reader and input stream.
7.

Returns the list contains as a two-dimensional String array.

Example 27-30 Reading Static Data for a View Object from a Properties File

// In SRPropertiesFileViewObjectImpl.java
private synchronized String[][] loadDataFromPropertiesFile() {
// 1. Derive the property file name based on the view definition name
String propertyFile =
getViewDef().getFullName().replace('.', '/') + ".properties";
// 2. Initialize a list to hold the name=value pairs
List codesAndDescriptionsList = new ArrayList(20);
try {
// 3. Open an input stream to read the properties file from the class path
InputStream is = Thread.currentThread().getContextClassLoader()
.getResourceAsStream(propertyFile);
LineNumberReader lnr = new LineNumberReader(new InputStreamReader(is));
String line = null;
// 4. Loop over each line in the properties file
while ((line = lnr.readLine()) != null) {
line.trim();
int eqPos = line.indexOf('=');
if ((eqPos >= 1) && (line.charAt(0) != '#')) {
// 5. If line contains "=" and isn't a comment, add String[]
// of {code,description} to the list
codesAndDescriptionsList.add(new String[]{
line.substring(0, eqPos),
line.substring(eqPos + 1)});
}
}
// 6. Close the line number reader and input stream
lnr.close();
is.close();
} catch (IOException iox) {
iox.printStackTrace();
return new String[0][0];
}
// 7. Return the list contains as a two-dimensional String array
return (String[][])codesAndDescriptionsList.toArray();
}

27.8.5.3 Creating Your Own View Object with Static Data

To create your own view object with static data that extends one of the example classes provided in the SRDemo application, define a new read-only programmatic view object with String attributes named Code and Description. On the Java panel of the View Object Editor, click Class Extends to specify the fully-qualified name of the SRStaticDataViewObjectImpl or SRPropertiesFileViewObjectImpl class as the custom class in the Object field. Then, enable a custom Java class for your view object and do the following:

If you extend SRStaticDataViewObjectImpl...

Then override the initializeStaticData() method and invoke the loadDataFromPropertiesFile() method shown
If you extend SRStaticDataViewObjectImpl ...

Then create the appropriate *.properties file in the same directory as the view object's XML component definition, with a name that matches the name of the view object (ViewObjectName.properties).

http://download.oracle.com/docs/html/B25947_01/bcadvvo008.htm#sthref2681

Farklı Java ve Browser versiyonları ile Oracle Forms

2008-04-01T06:36:00.000-07:00

Farklı Forms, Java ve Browser versiyonları için
Kurulum Prosedürü
Hazırlayan: Mücahid USLU / Yazılım - Temel Bankacılık
1- Kullanılan Forms versiyonuna uygun browser aşağıdaki tablodan seçilir.
2- Seçilen browser’a uygun client platform (java plug-in ve Jınitiator tablodan tespit edilir.
3- Hem ias tarafında hem de client larda aynı java plug-in olmasına dikkat edilir.(Client tarafında daha üst java versiyonun bulunması genelde sorun teşkil etmez ancak aynı olması tavsiye olunur.)
4- Yapılan seçimlere uygun forms patchlerinin yüklenmesi tavsiye edilir.
5- Çağrılan ilk html sayfası edit edilir, yapılan seçimlere uygun olarak object classid ="clsid:CAFECAFE-0013-0001-0028-ABCDEFABCDEF"
Ve EMBED SRC="" PLUGINSPAGE=""
type="application/x-jinit-applet;version=1.3.1.28" kısımları değiştirilir.
6- Eğer kullanılacak olan browser Netscape ya da Firefox ise, bunlara ait /plugins dizinlerine NPJinit131XX.dll dosyası kopyalanır.Bu dosya Jınitiator klasörü altından temin edilir.Eğer Jınitiator kurulumu browser kurulumundan sonra yapıldıysa kopyalamaya gerek kalmaz kendisi atar, yine de mutlaka varlığı kontrol edilmelidir.
7- Birden fazla tipte browser kullanımı için, çağrılan html sayfası değişik isimlerde yaratılarak kullanım sağlanmış olunur. Ör: start_ie.html, start_fir.html gibi..
8- JInitiator tüm sürümleri (şu anda en günceli 1.3.1.28) jdk1.3 ile develop edilmiştir, ancak uygulama içerisinde PrintRequestAttributeSet gibi java1.4 e ait class kullanılmaktaysa benim uygulamamdaki gibi ki bu class jdk1.4 ün bir üyesidir. Bu nedenle kullanılan Jınitiator sürümüne ait /lib dizininde rt.jar dosyası extract edilerek, içerisine jdk1.4 rt.jar javax paketi içerinden alınacak olan /printer dizini kopyalanır ve tekrar jar dosyası haline getirilerek client’lara kopyalanır. Aksi halde aşağıdaki gibi hata alınır;
java.lang.NoClassDefFoundError: javax/print/attribute/PrintRequestAttributeSet
at baysis.josefin.oracle.PrintWrapper.(PrintWrapper.java:11)
9- Ayrıca kullandiginiz jar dosyalari ve f90all.jar dosyaları da buraya kopyalanmalıdır.

Learn About Service Oriented Architecture (SOA)

2008-02-15T02:11:00.000-08:00

What is Service Oriented Architecture?
IT departments are managing increasingly complex IT portfolios. Yet as business needs change, these departments must still ensure that their technologies remain aligned with business goals. Failure to do so compromises organizational agility.
The problem for IT departments is typically not insufficient functionality; rather, it is that critical business systems such as customer relationship management (CRM) and enterprise resource planning (ERP) operate in isolation from other critical business systems—despite the fact that business processes often span multiple applications. To obtain an end-to-end view of a complex business process necessitates integration of information and process silos. In the past, this has been accomplished either though time-consuming manual interventions, or through hard-coded solutions that are difficult to maintain.
Service orientation is an approach to organizing distributed IT resources into an integrated solution that breaks down information silos and maximizes business agility. Service orientation modularizes IT resources, creating loosely coupled business processes that integrate information across business systems. Critical to a well-designed service-oriented architecture is producing business process solutions that are relatively free from the constraints of the underlying IT infrastructure, because this enables the greater agility that businesses are seeking.
Service Oriented Architecture (SOA) ultimately enables the delivery of a new generation of dynamic applications (sometimes called composite applications). These applications provide end users with more accurate and comprehensive information and insight into processes, as well as the flexibility to access it in the most suitable form and presentation factor, whether through the Web or through a rich client or mobile device. Dynamic applications are what enable businesses to improve and automate manual tasks, to realize a consistent view of customers and partner relations, and to orchestrate business processes that comply with internal mandates and external regulations. The net result is that these businesses are able to gain the agility necessary for superior marketplace performance.

SOA defined
Service orientation is a means for integrating across diverse systems. Each IT resource, whether an application, system, or trading partner, can be accessed as a service. These capabilities are available through interfaces; complexity arises when service providers differ in their operating system or communication protocols, resulting in inoperability.
Service orientation uses standard protocols and conventional interfaces—usually Web services—to facilitate access to business logic and information among diverse services. Specifically, SOA allows the underlying service capabilities and interfaces to be composed into processes. Each process is itself a service, one that now offers up a new, aggregated capability. Because each new process is exposed through a standardized interface, the underlying implementation of the individual service providers is free to change without impacting how the service is consumed.

Why SOA?
Complex, distributed IT resources are a concern for businesses. Too frequently, the existing IT portfolio does not adequately meet specific business needs, is costly to manage and maintain, and is inflexible in the face of business growth and change. The solution, however, is not to rip and replace systems or applications, nor to completely renovate them, but rather to find a way to leverage existing IT investments so that overall organizational goals are effectively supported.
Service orientation helps to accomplish these goals by making systems more responsive to business needs, simpler to develop, and easier to maintain and manage. Implementing a solution architecture based upon service orientation helps organizations plan ahead for change, rather than responding reactively.

Who does SOA?
Strictly speaking, SOA is done by developers and solution architects. However, stakeholders in a service-oriented solution span a range of roles, and it is critical that their interests not only be taken into account but that they actively drive the design of the SOA solution.
Starting with those interests, the business analyst is concerned with bringing IT investments more in line with the business strategy. For the developer, this means that the SOA solution must map the sources of business information—systems, staff, trading partners—into a unified and comprehensive view such that the business analyst has greater insight into the costs and benefits of various investments.
The chief technology officer (CTO) of the organization will work with developers to ensure that when designing a solution to meet the needs of the business analyst, the integrity of existing IT systems and applications resources are preserved, even as new capabilities are developed.
And the IT manager, concerned with effectively integrating distributed systems such that management is simplified, will work with the developer to ensure that these goals are also met.
Ultimately, the developers and solution architects are concerned with creating dynamic collaborative applications that meet the goals of the various stakeholders. The service orientation approach enables them to do so in a way that meets the needs of the organization as a whole.

What SOA isn’t
There are numerous misconceptions about what SOA is—that it is a product that can be purchased (it is not; it is a design philosophy that informs how the solution should be built); that the goal is to build a SOA (it is not; SOA is a means to an end); or that SOA requires a complete technological and business process overhaul (it doesn’t; SOA solutions should be incremental and built on current investments).
SOA is also often equated with Web services, and the terms used interchangeably. While it is true that SOA is made easier and more pervasive through the broad adoption of Web services–based standards and protocols, the two are distinct. SOA is an approach to designing systems—in effect the architectural drawings or blueprint—that directs how IT resources will be integrated and which services will be exposed for use. In contrast, Web services is an implementation methodology that uses specific standards and language protocols to execute on a SOA solution.

Before starting a SOA
Before a developer writes a single line of code, it is critical to identify both specific business drivers of the SOA endeavor and the dependencies between the business and the underlying technologies. Neglecting the business context can result in a project in which SOA infrastructure is pursued for its own sake, or where investments are made that do not line up well with the needs and priorities of the business.
Two approaches are commonly pursued for implementing SOA: top-down and bottom-up. Both approaches have possible pitfalls that can prevent success. Many organizations that have attempted to roll out SOA infrastructure through a top-down approach have discovered that when the infrastructure is finally delivered it is out of sync with the needs of the business. Likewise, a bottom-up approach can fail as well, because it can lead to a chaotic implementation of services created without regard to organizational goals.
The “middle-out” approach is a successful hybrid of the two other approaches. Business drivers and strategic vision are first employed to set clear direction and priorities. Based on these, the organization takes multiple iterative steps to build out slices of end-to-end capabilities, with each iteration delivering a new, dynamic application back to the business that is used to create business return. Microsoft has long advocated this “real-world” approach to leveraging service-oriented architectures: The approach is focused on rapid time-to-value, and it delivers business results through iterative, incremental steps that facilitate close alignment of IT resources with changing business conditions.

What is the SOA life cycle?
The core IT assets of any organization include its data, legacy systems, line-of-business applications, packaged applications, and trading partners. Each of these resources is a service provider responsible for producing numerous highly specific outputs, such as inventories and customer data.
Service orientation ties together these disparate and autonomous sources of information, bridging a wide range of operating systems, technologies, and communication protocols. The process by which it does this is an iterative one of creating (“exposing”) new services, aggregating (“composing”) these services into larger composite applications, and making the outputs available for consumption by the business user.

Expose
The expose phase of the SOA approach focuses on which services to create from the underlying applications and data. Service creation can be fine-grained (a single service that maps to a single business process) or coarse-grained (multiple services come together to perform a related set of business functions).
The expose phase is also concerned with how the services are implemented. The functionality of underlying IT resources can be made available natively if they already speak Web services, or can be made available as Web services though the use of an adapter.
Compose
Once services are created, they can be combined into more complex services, applications, or cross-functional business processes. Because services exist independently of one another as well as of the underlying IT infrastructure, they can be combined and reused with maximum flexibility. And as business processes evolve, business rules and practices can be adjusted without constraint from the limitations of the underlying applications.
Consume
Once a new application or business process has been created, that functionality must be made available for access (consumption) by either other IT systems or by end users. The goal of the consumption process is to deliver new, dynamic applications that enable increased productivity and enhanced insight into business performance. Users can consume the composed service through a number of avenues, including Web portals, rich clients, Office business applications, and mobile devices.

What are the benefits of SOA?
Service-oriented architecture is, first and foremost, a means of attaining greater business agility from existing IT investments. SOA-based solutions connect systems and thereby automate previously manual information-transfer processes whether the goal is to develop new applications; to connect systems, workgroups, or geographically distributed subsidiaries; or to collaborate with trading partners. At the same time, SOA solutions build in the essential services required to ensure that the appropriate resources are accessed by the appropriate users.
SOA benefits accrue for the organization at two different levels, that of the IT organization and that of the business user; in the end, all benefits add up to a dramatic increase in agility and productivity.
From the IT department’s point of view, SOA-based integration simplifies management of distributed resources across multiple platforms, requires less hardware, is more reliable, is standards-based, and is less costly.
From the business point of view, SOA enables development of a new generation of dynamic applications addressing a number of top-level business concerns that are central to growth and competitiveness. SOA solutions promote:
• Stronger connections with customers and suppliers. By making dynamic applications and business services available to external customers and suppliers, not only is richer collaboration possible, but also customer/partner satisfaction is increased. SOA unlocks critical supply and demand chain processes—such as outsourcing of specific business tasks—from the constraints of underlying IT architectures, thereby enabling better alignment of processes with organizational strategy.
• Enhanced business decision making. By aggregating access to business services and information into a set of dynamic, composite business applications, decision makers gain more accurate and more comprehensive information. They also gain the flexibility to access that information in the form and presentation factor (Web, rich client, mobile device) that meets their needs.
• Greater employee productivity. By providing streamlined access to systems and information and enabling business process improvement, businesses can drive greater employee productivity. Employees can focus their energies on addressing the important, value-added processes and on collaborative, semi-structured activities, rather than having to conform to the limitations and restrictions of the underlying IT systems.

What are the challenges associated with SOA?
SOA confers obvious business benefits associated with integration and the creation of new services. However, insufficient attention to governance—the management and monitoring of services, their performance and reliability, and especially their security—can cause inefficiencies and disrupt business processes and the end users they support.
As business needs evolve, it is critical to have policies in place that help determine how to prioritize new business processes and services under consideration for implementation, who will be responsible for designing those processes, how they should be implemented, and how the success of the new implementations will be measured. This is especially important given the inherent cross-functional nature of SOA solutions.
Reuse of services, once touted as a primary SOA advantage, is really a byproduct of the approach rather than the goal itself. Reuse is also proving to be more challenging than expected. An existing service may not provide exactly what a different business process requires and so may call for additional work. And designing a service so that it can be reused in the future requires accurately predicting what future needs will be, something notoriously difficult to do.

How can your organization get started with SOA?
1. Make sure that you have sound business drivers. When an organization struggles to justify their SOA projects, it is almost always because they are trying to “do SOA” rather than address a business need.
2. Top-down approaches do not work in the real world. Bottom-up approaches are not manageable either. In contrast, organizations that are successful with SOA often adopt a middle-out approach. These organizations all have something in common—they start with clear business challenges and focus on creating business value.
3. Try to avoid subscribing to the “build it and they will come” approach. Some organizations spend 18 to 30 months building a services infrastructure. When they finally reach the service consumption or user-experience layer, they find that the business needs have changed, rendering the investments a waste of time and money. It is often more practical to partition your usage scenarios into small sets and build out the entire scenario top to bottom, from the data through to the application consuming the services. Partitioning functionality in this manner can help you track changing business needs much more effectively.
4. Demonstrate value in rapid iterations. Time-to-value is a critical, healthy metric. The “trust-me” approach is not a healthy model for successfully leveraging SOA.
5. Last, but not least, organizations that have successfully adopted a SOA solution often use a “snowball” approach. How do you build a big snowball? You start with a small snowball. This is probably the most important take-away with respect to leveraging SOA to drive business value.

Source: microsoft

Introduction to Javaserver Faces - What is JSF?

2008-02-14T00:17:00.000-08:00

What is JSF?

JavaServer Faces (JSF) is a new standard Java framework for building Web applications. It simplifies development by providing a component-centric approach to developing Java Web user interfaces. JavaServer Faces also appeals to a diverse audience of Java/Web developers. "Corporate developers" and Web designers will find that JSF development can be as simple as dragging and dropping user interface (UI) components onto a page, while "systems developers" will find that the rich and robust JSF API offers them unsurpassed power and programming flexibility. JSF also ensures that applications are well designed with greater maintainability by integrating the well established Model-View-Controller (MVC) design pattern into it's architecture. Finally, since JSF is a Java standard developed through Java Community Process (JCP), development tools vendors are fully empowered to provide easy to use, visual, and productive develop environments for JavaServer Faces.

JSF Architecture

JavaServer Faces' Implementation of MVC
One of the key advantages of JSF is that it is both a Java Web user-interface standard as well as a framework that firmly follows the Model-View-Controller(MVC) design pattern. This makes JSF applications much more manageable because the user-interface code (View) is cleanly separated from the application data and logic (Model). To prepare the JSF context, which provides application data access to the pages, and to guard against unauthorized or improper access of the pages, all user interactions with the application are handled by a front-end "Faces" servlet (Controller).

The JSF LifecycleThe Faces Controller servlet serves as the link between the user and the JSF application. It operates within the confines of a well defined JSF Lifecycle which dictates the entire flow of events between user requests. For example, upon an initial Web request to access a JSF application, the Faces controller servlet handles the request by first preparing the JSF context, which is a Java object that holds all application data. The controller then routes the user to the requested page. The page usually renders application data from the JSF context using a simple Expression Language. Upon subsequent requests, the controller updates any Model data, providing any new input has been entered. JSF developers have programmatic access to the entire JSF lifecycle at any time during its execution thus affording a high degree of control over the application's behavior at all times.

JavaServer Faces' User-Interface Components
The true power of JavaServer Faces lies in its user-interface component model where applications are merely built from collections of components that can render themselves in diverse ways for multiple client types. Vaguely similar to other proprietary technologies such ASP.Net, JSF's UI Component model technology offers unprecendented productivity by allowing the developer to construct Web user interfaces using pre-built user-interface (UI) Components as opposed to having to construct the user interface entirely from scratch. JSF UI Components come in many forms and can be as simple as an outputLabel which simply displays text or as complex as a dataTable which can represent a tabular data from collections of data such as from a database table.

The JavaServer Faces specification provides a set of base UI Components in its Reference Implementation which are very useful on their own. These include two libraries of components such as the "HTML" component library which largely mirrors the standard HTML input elements along with a "Core" library which aids in common application development tasks such as internationalization, and validating/converting input data. In addition to providing a base library of UI Components, the JSF API offers the ability to extend and create custom JSF UI Components providing additional functionality above and beyond the base components.

Additional User-Interface Component Libraries
Because of the richness and flexibility of the JSF API, many Java developers are beginning to create new JSF Component libraries and implementations. Oracle's ADF Faces is a fully compliant JSF component library which offers a broad set of enhanced UI Components for JSF application development. These include multiple renderers per client type, advanced tables, color and date pickers along with a host of general components such as menus, command buttons, shuttle choosers and progress meters.

In addition to Oracle's ADF Faces there are other new JSF Component Libraries beginning to appear from both the Open Source and software vendor communities. MyFaces is an example of a new JSF UI Component Library being offered as an Open Source project through Apache. Myfaces also serves as an enhancement to the JSF base UI components in that they also have more extensive UI capabilities such as integrated Tiles support, Javascript enabled menus and Tree controls.

JSF UI Components' Pluggable Rendering Technology
One of the most compelling aspects of JSF's UI Component technology is it's pluggable rendering capability. JSF UI Components have the ability to render themselves differently depending on the client type viewing the component. For example a HTML browser will view an "HTML Browser Friendly" version of a particular UI Component whereas a Wireless or WAP enabled micro-device would view a "WML friendly" version of the same UI component! JSF makes this possible by de-coupling the UI Component from its rendering logic making it possible to create multiple renderers for the same UI Component. Different renders can be associated with the UI Component and at runtime the UI component can decide which renderer to use based on the requesting client type.

It should also be pointed out that because of JSF's pluggable rendering capability it is possible for JSF UI Components to render any kind of data be it markup, such as HTML, XML, WML etc.., or binary data. For example UI Components can also render binary data such as an image streams or different document types such as SVG, PDF and Word.

A New Community of JSF Component Developers
As the community of JSF developers and enthusiasts continues to grow, there are now several Websites dedicated to further empowering independent JSF development.. JSFCentral is an example of a new Website solely dedicated to the JSF development community. It contains JSF technical information, product/component information as well as a vast listing of numerous JSF related articles.

(JSFCentral is located at: http://jsfcentral.com)
JSF Development Tools
Because JavaServer Faces is a standard Java technology, software development tools are fully empowered to offer advanced integrated development tools support for JavaServer Faces. This greatly enhances JSF's ease of use and power in that multiple vendors are now supporting JSF development to varying degrees. Oracle, Sun , Borland and IBM each offer development environments for JavaServer Faces. Since development tools vendors are competing at providing better, easier and more development environments, the future of IDE based JSF development looks great!

Summary
JavaServer Faces solves many of the historical problems of Java Web development by providing a clean implementation of the Model-View-Controller design pattern while providing a productive, component-centric development without sacrificing development power and flexibility. Additionally since JSF is a Java standard, multiple software vendors will continue to provide evermore productive and efficient development environments which will no doubt rival and most probably surpass proprietary visual development environments. Stay tuned!

Chris Schalk , Oracle Corporation

How to delete files in a directory (java)

2008-02-12T03:32:00.000-08:00

private void deleteDir(File dir) {
if (dir.isDirectory()) {
String[] _file = dir.list();
for (int i=0; i<_file.length; i++) {
deleteDir(new File(dir, _file[i]));

}
}else{
dir.delete();}

}

How to sign an applet

2008-02-07T06:46:00.000-08:00

1. Generate key: keytool -genkey -keyalg rsa -alias tstkey
Enter keystore password: *******
What is your first and last name?
[Unknown]: Your Name
What is the name of your organizational unit?
[Unknown]: YourUnit
What is the name of your organization?
[Unknown]: YourOrg
What is the name of your City or Locality?
[Unknown]: YourCity
What is the name of your State or Province?
[Unknown]: YS
What is the two-letter country code for this unit?
[Unknown]: US
Is CN=Your Name, OU=YourUnit, O=YourOrg, L=YourCity, ST=YS, C=US
correct?
[no]: yes

(wait...)

Enter key password for tstkey
(RETURN if same as keystore password):

(press [enter])

2. Export key: keytool -export -alias tstkey -file tstcert.crt

Enter keystore password: *******
Certificate stored in file tstcert.crt

3. Create JAR: jar cvf tst.jar tst.class
Add all classes used in your project by typing the classnames in the
same line.

added manifest
adding: tst.class(in = 849) (out= 536)(deflated 36%)

4. Verify JAR: jar tvf tst.jar

Thu Jul 27 12:58:28 GMT+02:00 2000 META-INF/
68 Thu Jul 27 12:58:28 GMT+02:00 2000 META-INF/MANIFEST.MF
849 Thu Jul 27 12:49:04 GMT+02:00 2000 tst.class

5. Sign JAR: jarsigner tst.jar tstkey
Enter Passphrase for keystore: *******

6. Verifiy Signing: jarsigner -verify -verbose -certs tst.jar

130 Thu Jul 27 13:04:12 GMT+02:00 2000 META-INF/MANIFEST.MF
183 Thu Jul 27 13:04:12 GMT+02:00 2000 META-INF/TSTKEY.SF
920 Thu Jul 27 13:04:12 GMT+02:00 2000 META-INF/TSTKEY.RSA
Thu Jul 27 12:58:28 GMT+02:00 2000 META-INF/
smk 849 Thu Jul 27 12:49:04 GMT+02:00 2000 tst.class

X.509, CN=Your Name, OU=YourUnit, O=YourOrg, L=YourCity, ST=YS, C=US
(tstkey)

s = signature was verified
m = entry is listed in manifest
k = at least one certificate was found in keystore
i = at least one certificate was found in identity scope

jar verified.

Note: even if it returns "jar unsigned", put jar file to your server, it will work :) i have tried. there may be a problem in verifier.

Mücahid Uslu

REPCMD Utility / Using Oracle Repository (SCM)

2008-02-07T05:50:00.000-08:00

Open a command screen;

To run util;
C:> REPCMD

To connect to scm;
C:> CONNECT username/password@SID

To set workarea;
C:> SET WORKAREA waname

To see list of checkouted files;
C:> LSCHECKOUT (or LSCO)

CHECK-IN a file;
-------
CHECKIN \waname\other path\filename.fmb

UPLOAD a file;
-------
UPLOAD C:\filename.fmb \waname\other path\

to see all commands;
C:> HELP

If you wannt to reach from a program to util, you can to run a bat file which contents related commands.

for example;

Run a bat file following;
create a bat file in java code

PrintWriter fileOut=null;
try
{
if(iAction==9){
fileOut = new PrintWriter(new FileWriter("c:\\scm123.bat"));
}else{fileOut = new PrintWriter(new FileWriter(sBatFileName));}
} catch (Exception e)
{
System.out.println(e.getMessage());
}

fileOut.println("CONNECT "+mydb.GetSCMUser()+"/"+mydb.GetSCMPass()+"@"+mydb.GetSCMTNSSID());
fileOut.println("SET WORKAREA "+sWorkArea);
fileOut.println("UPLOAD c:\\"+_filename+"."+_fileext+" \\"+sSCMPath+"\\"+_fileext.toUpperCase()+"\\"+_filename.substring(0,1).toUpperCase()+"\\ -ow");
fileOut.println("CHECKIN \\"+sSCMPath+"\\"+_fileext.toUpperCase()+"\\"+_filename.substring(0,1).toUpperCase()+"\\"+_filename+"."+_fileext);
fileOut.println("COMMIT");
fileOut.println("DISCONNECT");
fileOut.println("EXIT");

and run this command; example for java;

try
{
System.out.println("SCM Script begin..");
Runtime rt = Runtime.getRuntime();
Process child=rt.exec("cmd /c start /min repcmd @"+"c:\\myfile.bat");
child.waitFor();
System.out.println("SCM Script finished..");
}

catch(IOException e)
{
System.err.println("scm script error! "+e.getMessage());
}

Mücahid Uslu

Articles & Samples

IEnumerable vs IQueryable

Linq to DataTable

HTML ASCII Characters

HTML ASCII Characters

codes

characters

character names

How to set jQuery intellisense plugin onto VS 2008 ?

Generally accepted principles of software architecting

Interface Declaration

Replace Text Fields in Binary Data File

Java Swing - Look And Feel

SpringSource Update Site for Eclipse

What is the difference between CLOB and BLOB ?

How To Run A Process in C# .Net

Fix Debugging Problem On Forms 10g

Generate Random Alpha-Numeric Values (C#.Net)

Adf Nedir?

Samples - ADF How to

JSEXT

Some popular Ajax Toolkits

AJAX - Get Started

James Cahill: Christmas blog

Weblogic 10.3 Install and configuration for ADF Applications

Easily ftp access with Java

ADF Faces / Access to Data Model from Backing/Managed Bean

Programmatic View Object / Using Ref Cursor / Using Static Data

Farklı Java ve Browser versiyonları ile Oracle Forms

Learn About Service Oriented Architecture (SOA)

Introduction to Javaserver Faces - What is JSF?

How to delete files in a directory (java)

How to sign an applet

REPCMD Utility / Using Oracle Repository (SCM)