INSERT INTO TABLE_B (NAME, PHONE) SELECT NAME, PHONE FROM TABLE_A; Table A dan Name ve phone alınıp Table B ye eklenir.

Commit unutmayalım.

1. A developer has more control with JSP, but (should) get easier development with JSF
2. Event handling is done differently in JSP (HTTP) and JSF (Java)
3. The UI is designed differently (or should be at least) with JSP (markup) and JSF (components).
4. The end product should also be defined differently - JSP page versus a JSF application.
Is this the only thing that is need to make a decision for either or? Probably not. There are other pieces that need to be taken in account when deciding which technology to use - tools support, enough components, type of application etc…. At this point there are not enough JSF components (although there are some interesting projects underway - Ajaxfaces, Myfaces, ADF Faces, and WebChart 3d) and enterprise tools support is still limited to a few tools vendor. Looking at our ADF Faces components they are currently available as early access (not production) and demands for these components are stacking up, literally, outside my office doorstep. Although I would love to make them production - now! - it is not a viable solution since we are still checking features and fixing critical bugs.
All this combined - not enough enterprise level components in production, lacking tools support etc… - leave customers in a vacuum where the decision is either to continue with JSP, since it is mature and has a wide developer base, or move forward with JSF not sure if the support, or the developers will be there. This is particularly sensitive to customers that need to get started now and be production by summer.
If you are in this vacuum here are some key points promoting JSF:
1. Fundamental unit is the Component
2. Built in event and state management
3. Component sets can be provided by any vendor
4. Closer to ASP.Net or Swing development
5. Choice of UI technology
6. Scale up (rich clients)
7. Scale down (mobile devices)
8. Built into J2EE containers in J2EE 5.0 (tentative)

to execute this procedure in pgadmin  : select squre_root( 9 );

import java.sql.*;

public class PlSqlTest {
public static void main(String args[]) {
CallableStatement stmt = null;

int a=9;

System.out.println(”\nArray Parameter Test\n”);
try {
Class.forName(”org.postgresql.Driver”);

Connection conn = DriverManager.getConnection(”jdbc:postgresql://localhost/hede”, “hede”,”hede”);

conn.setAutoCommit(false);
stmt = conn.prepareCall(”{?= call squre_root(?)}”);
stmt.registerOutParameter(1, java.sql.Types.DOUBLE);
stmt.setInt(2, a );
stmt.execute();
double result = stmt.getDouble(1);

System.out.println(”\nThe result is ” + result);

conn.close();
}
catch (SQLException se) {
System.out.println(”\nA SQL exception occurred.”);
System.out.println(”\nError code: ” + se.getErrorCode());
System.out.println(”\nSQL state: ” + se.getSQLState());
se.printStackTrace();
}
catch (Exception e) {
System.out.println(”\nSome other exception occurred.\n”);
e.printStackTrace();
}
}
}

autoCreate.newDevice=true

quarantine.newDevice=false

newDevice.notification.emailAddress=email@dns

Note:This autoCreate process doesn’t work properly.like Nokia N80 or N73 ,we expect to see openCDS 5.1 version (may be released in September 2007 ).

If you create your application using XMLRPC This can not include create method.

we solve this problem add a jsp file to subscriberportal to compile this jsp use subscriberportalapi.jar.

<%@page import=”com.sun.content.server.subscriberapi.ISystemService”%>
<%@page import=”com.sun.content.server.subscriberapi.ApiServiceFactory”%>
<%@page import=”com.sun.content.server.subscriberapi.IModel”%>
<%@page import=”com.sun.content.server.subscriberapi.ApiUtil”%>
<%@page import=”com.sun.content.server.server.webapps.common.UIHelper”%>
<%@page import=”com.sun.content.server.subscriberapi.IApiContext”%>

<%
String userAgent = request.getHeader(”user-agent”);
System.out.println(”Model Created info:Starting!!!”);

//while using webbrowser it creates more than more mozilla device types

if (!userAgent.startsWith(”Mozilla”)){
try{
ApiUtil.initTransaction();
UIHelper.configureAPI(request);
IApiContext apiContext = UIHelper.getApiContext(request);
UIHelper.configureAPIRequest(apiContext);
ISystemService ss = ApiServiceFactory.getSystemService(null);
IModel newModel = ss.createModel(request);
System.out.println(”Model Created info:Stopping !!!”);
}
catch(Exception e){
e.printStackTrace();
}
finally{
ApiUtil.commitTransaction();
}
}%>

Use redirection turn back to your aplication. this is a nail ( Turkish called ” çakma “) solution.