Labels

_fuxi (75) _IV (146) _misc (5) {610610 (30) algo (1) automatedTrading (8) banking/economy (3) book (14) c++misc (125) c++real (15) c++STL/java_container (7) cppTemplate (1) db (13) DB_tuning (4) deepUnder (1) dotnet (69) eTip (17) excelVBA (12) finance+sys (34) financeMisc (24) financeRisk (2) financeTechMisc (4) financeVol (21) finmath (17) fixedIncome (25) forex (16) IDE (24) invest (1) java (43) latency (4) LinearAlgebra (3) math (30) matlab (24) memoryMgmt (11) metaPrograming (2) MOM (15) msfm (1) murex (4) nofx (11) nosql (3) OO_Design (1) original_content (4) scriptUnixAutosys (19) SOA (7) socket/stream (15) sticky (1) subquery+join (2) swing (32) sybase (6) tech_orphan (12) tech+fin_career (30) telco (11) thread (21) timeSaver (13) tune (10) US_imm (2) US_misc (2) windoz (20) z_algo+dataStructure (4) z_arch (2) z_c#GUI (30) z_career (10) z_career]US^Asia (2) z_careerBig20 (1) z_careerFinanceTech (11) z_FIX (6) z_forex (31) z_hib (2) z_ikm (7) z_inMemDB (3) z_j2ee (10) z_oq (14) z_php (1) z_py (26) z_quant (4) z_skillist (3) z_spr (5)
Showing posts with label z_j2ee. Show all posts
Showing posts with label z_j2ee. Show all posts

Sunday, April 19, 2015

RESTful - phrase book

agile –

 

coupling – less coupling between client and server, so server side changes are easier. I think SOAP requires client rebuild.

 

b2b – still dominated by SOAP

 

resource-oriented services –

 

object – each URL logically represents an object, which you can Get (query), POST (create), PUT (update its content) or DELETE

 

Tuesday, April 14, 2015

entity means ...in ORM lingo

It means an object in memory, backed by a DB record... see [[beginning java EE 7]]

Sunday, April 12, 2015

DOM and other components of ajax

[[beginning java ee7]] P372 points out that ajax technology stack includes

• DOM
• xhtml as "final data format" to render the page on browser
• xml or json or plan text as payload

data types in jason

numbers, strings, booleans

 

arrays

 

object – basically associative array of name-value pairs

JPA2 supports stored proc (empty

 

Thursday, July 26, 2007

cluster admin server

In Weblogic (perhaps similar elsewhere), a cluster needs an admin server that's not one of the cluster nodes.
 
j4: single point to deploy application, but without admin server, we can have similar convenience?
j4: watch tower to monitor the nodes, but without it, we can monitor them from another place?
j4: single location to store node-configuration

Saturday, December 10, 2005

soa AR 4 q&&A

A: corba and dcom. seems like "dist obj" architecture"

A: Traditionally, connections between applications have been tightly coupled, as with CORBA (Common Object Request Broker Architecture). For example, flipping a wall switch to turn on a light is a tightly coupled system. However, making a telephone call to order a book is a loosely coupled system.

A: provider, consumer and a broker, just like JMS. Broker can also be a registry.
provider would PUBLISH its list of services to the registry

A: a Web service is little more than an SOA. However, an SOA doesn't require the use of Web services as we understand them, and some types of Web services can be deployed without an SOA.

Simple SOA block diagram http://www.computerworld.com/computerworld/records/images/story/HowSOAWorks_large.gif

Q: 3 basic roles (processes) for an SOA interaction?

Q: relation to web corba?

Q: relation to web services?

Q: similiar ideas to SOA?

Saturday, May 14, 2005

dao-jsp-struts q&&a

q: every browser request would trigger an instantiation of the DAO?
A: i think so, from the DAO factory. In fact, if the request uses 2 tables, then you need 1 DAO intance for each table.

q: at a minimum, how do u keep the dao instance persistent throughout the session?
A: I don't think you want that. If you keep 3000 DAO object in that many sessions, then you need that many connection objects! See also P 360 [[ JSP ]]

q: dao objects are placed in jndi/app/session/request scope?
A: I think you can put in request scope.

[lopri] q: jndi?

q: in a non-trivial system like hib or struts, what are the most basic "interface points" of DAO
- how does a client get a DAO? jndi?
- where does the DAO return result to? in a bean? a value object?
- how does the client receive the result?

Friday, May 13, 2005

core DAO q&&a

q0: every call to the dao creates a new connection?
A0: every DAO instance HAS-A connection object, perhaps from a pool. A connection object is usually open and usable. Before the link is established with the DB, the connection object probably doesn't exist.

q1: methods in the dao object?
get*() like getSomethingByPrimaryKey(int key)
insert*()
special methods? getConnection()?

q2: a single DAO or teacherDAO, departmentDAO, courseDAO, projectDAO.. .?
A2: multiple is more common. Consider CMP.
A2: Even a daoFactory class should be defined for a particular db table like CatalogDAOFactory.getDAO() -- static method

q3: where is sql stored?
a3: a studentDAO would expose many getAge(), setNationality(), updateMatricYear(), insertCourse()... methods. Where do u think the sql is?

q: how is the connection obj created and passed?
a: The connection URL is often harded-coded in the dao (or dao-factory)

[lopri] q: singleton? probably not, we need many instances of DAO

[lopri] q: dao is an iface or ...?
A: We have seen simple cases, where interface is unnecessary.

[lopri] q: dao factory? not always necessary? how about in strusts?