Major brand connector Website Daquan

September 18, 2011
http://www.jst-mfg.com Japan Crimping / JST connector
http://www.molex.com U.S. molex / molex connector
http://www.tycoelectronics.com U.S. Tyco / tyco connector
http://www.amp.com U.S. AMP / Tyco / AMP connector
http://www.jae.co.jp Japan Aviation Electronics / JAE connector
http://www.hirose . co.jp Japan Hirose / HRS connector
http://www.ket.com Korea KET connector
http://www.jam-net. co.jp Japan JAM connector
http://www.smk.co.jp Japanese SMK connector
http://www.avxcorp.com Japan ELCO connection device
http://www.kyocera.com Japan Kyocera kyocera connector
http://www.mitsumi.co.jp Japan Mitsumi / United States on U.S. MITSUMI connector
http://www.y-connect.com Japanese Yazaki YAZAKI connector
http://www.amphenol.com U.S. Amphenol Amphenol connector
http://www.samtec.com U.S. application Thai Samtec connector
http://www.yeonho.com Korean contingent Lake YH / Yeonho connector
http://www.han-lim.com Korea Han Lin Hanlim connector
http://www.fciconnect.com FCI Framatome Connectors
http://www.bergelect.com Framatome / Berg BERG connector
http://www.uju.com Korea UJU connector
http://www.panasonic-denko.co.jp/ac/c/ connector Panasonic Matsushita Electric of Japan (the original Nais)
http://www.ddknet.co. jp / Japan electronics / DDK connector
http://www.nicomatic.co.uk France Nico Mehdi / Nico Mai Di Nicomatic / CRIMPFLEX connector
http://www.i-pex.com Japan I-PEX connector
http://www.nippon-tanshi.jp Japanese terminal connector
http://www.kel.jp Japan KEL connector
http://www.sumiko-tec.co.jp Japan to live mine connectors
http:/ / www.jst-mfg.com Japan Crimping / JST connector
http://www.molex.com U.S. molex / molex connector
http : / / www.tycoelectronics.com U.S. Tyco / tyco connector
http://www.amp.com American AMP / Tyco / AMP connector
http://www.jae.co.jp Japan Aviation Electronics / JAE connector
http://www.hirose.co.jp Japan Hirose / HRS connector
http://www.ket.com Korea KET connector
http://www.jam-net.co.jp Japan JAM connector
http: / / www.smk.co.jp Japanese SMK connector
http://www.avxcorp.com Japan ELCO connector
http://www.kyocera. com Japanese Kyocera kyocera connector
http://www.mitsumi.co.jp Japan Mitsumi / Mitsumi MITSUMI connector
http://www . y-connect.com Japan Yazaki YAZAKI connector
http://www.amphenol.com U.S. Amphenol Amphenol connector
http://www.samtec . com U.S. application Thai Samtec connector
http://www.yeonho.com Korean natural lake YH / Yeonho connector
http://www.han-lim . com South Korea Han Lin Hanlim connector
http://www.fciconnect.com Framatome FCI connector
http://www.bergelect.com French law Framatome / Berg BERG connector
http://www.uju.com Korea UJU connector
http://www.panasonic-denko.co.jp / ac / c / connector Panasonic Matsushita Electric of Japan (the original Nais)
http://www.ddknet.co.jp / Japan electronics / DDK connector

http://www.nicomatic.co.uk France Nico Mehdi / Nico Mai Di Nicomatic / CRIMPFLEX connector
http://www.i-pex.com Japan I-PEX connector
http://www.nippon-tanshi.jp Japanese terminal connector
http://www.kel.jp Japan KEL connector
http://www.sumiko-tec.co.jp Japan to live mine connectors
http://solutions.3m.com/wps/portal/3M/en_WW/electr onics / home / productsandservices / products / interconnec tsolutions / 3M connector
www.wago.com Germany WAGO

All Products> Electronics> Electronics Accessories> Headphones

, Turkey, the United States wins another title in 16 yearscomment
Description
$ 89.00 – $ 183.45 4 stores)
The i903 frees you from the bondage of a wired environment using < br /> Bluetooth wireless technology. Not only that, More Amazon, but
outside sounds that can be a distraction to pure music enjoyment or
an annoyance during an important phone call virtually
disappear, RegisterLogin
->, helping you focus on what you want to hear and not on
what you have to hear. This … more
All
Products> Electronics > Electronics
Accessories> Headphones
Customer reviews (55)

Better thermal management promises cheaper, greener, cooler electronics

The demonstrator photo (provided by FOAB) shows the micro-cooler
device is running, and thermal energy is taken away by the coolant
flowing through the micro channels. @ Yifeng Fu
< strong> At first glance, supercomputers, car parts,
entertainment systems and radar antennas may not have much in
common, but they all stand to benefit from important advances in
thermal management technology being achieved by an EU-funded
project. Materials developed under the project have been
demonstrated in different application sectors, and some are already
in use commercially, or likely to be in the near
future.
Improving thermal management is essential if processing
power is to continue increasing as electronic components get
ever smaller. Too much heat that can be managed effectively puts
limits on the performance of chips and other microelectronic
components, it reduces reliability, and it
also costs money and harms the environment.
A prime example of the problem from a technical, environmental
and economic perspective are data centres. These vast buildings –
sometimes spreading across the equivalent of several football
pitches – are used by a variety of industries to store and process < br /> data. The banks of computers inside them produce a lot of heat. So
much in fact that around half the cost of building a new data
centre goes on the cooling system, which in turn requires more
energy to operate, resulting in a large carbon
footprint.
The same problems are true in any industry that uses
microelectronics – from telecommunications to aviation. Hence
demand for a better solution is intense. In Europe, companies such
as Thales, Bosch and IBM have joined up with research institutes
and universities, obtaining funding from the European Commission to
try to develop new materials and
processes to solve the thermal management
issue.
Their efforts in the ano packaging technology for interconnect
and heat dissipation (Nanopack) project have resulted in
new hermal interface materials (TIMs) developed with micro-and
nanotechnology to greatly increase heat transfer away from chips
and other electronic
components, in turn reducing the demands placed on cooling
systems, lowering costs and reducing energy consumption. The
materials have been showcased in a series of demonstrators with
applications across a variety of sectors, some of which are in use
commercially or are likely to be in the near
future.
t Thales, we build radar systems for airplanes. Thermal issues
are especially important in that environment because the space
available is very small and very confined. At present, the cost of
the thermal architecture of the radar is something like 40% of the
total cost, ays Afshin Ziaei, a manager of research at Thales
Research

Loaded on more than view.properties SpringMVC development issues

June 17, 2010
use SpringMVC the development process, if you use a mixed view of way, and using the ResourceBundleViewResolver way. The only way to read the default classpath following view.properties (of course, be other properties files, but also with Locale, the basename of the properties can be configured).
For a project to develop if more than one person situation, we have to modify this file is clearly not practical, the best way to have each module below view.properties, in the system whether to automatically start loading, which can increase the concurrent development of the efficiency and reduce the cost of the project synthesis.
simply looked ResourceBundleViewResolver, which would like to start from this class to achieve a ViewResolver, so as to achieve automatic load, the following is achieved:
/ / $ Id: AutoResourceBundleViewResolver. java 2010-6-17 morning 11:26:23
package com.jtv.walllee.common.extend;
import java.io.IOException;
import java.util.HashMap;
import java.util.Iterator;
import java.util.Locale;
import java.util.Map;
import org.springframework.beans.BeansException;
import org.springframework.beans.factory.BeanFactory;
import org.springframework.beans.factory.DisposableBean;
import org.springframework.beans.factory.NoSuchBeanDefini tionException;
import org.springframework.beans.factory.support. Properti esBeanDefinitionReader;
import org.springframework.context.ConfigurableApplicatio nContext;
import org.springframework.core.Ordered;
import org.springframework . core.io.Resource;
import org.springframework.core.io.support.PathMatchingRe sourcePatternResolver;
import org.springframework.core.io.support.ResourcePatter nResolver ;
import org.springframework.web.context.support.GenericWeb ApplicationContext;
import org.springframework.web.servlet.View;
import org.springframework.web.servlet.view.AbstractCachi ngViewResolver;
/ **
*
*

* @ author Wall.Lee (xiaoshan2242@gmail.com)
* /
public class AutoResourceBundleViewResolver extends AbstractCachingViewResolver implements Ordered, DisposableBean {
private int order = Integer.MAX_VALUE; / / default: same as non-Ordered
private String scanFileName; / / scan view filename
private String defaultParentView;
private Locale [] localesToInitialize;
/ * Locale -> BeanFactory * /
private final Map localeCache = new HashMap ();
/ * List of ResourceBundle -> BeanFactory * /
private final Map resourceCache = new HashMap ();
public void setOrder (int order) {
this.order = order;
}

public int getOrder () {
return this.order;
}
public void setDefaultParentView (String defaultParentView) {
< br /> this.defaultParentView = defaultParentView;
}
public void setLocalesToInitialize (Locale [] localesToInitialize) {
this.localesToInitialize = localesToInitialize;
}
protected void initApplicationContext () throws BeansException {
if (this.localesToInitialize! = null) {

for (int i = 0; i initFactory (this.localesToInitialize [i]);
}
}
}
protected View loadView (String viewName, Locale locale) throws Exception {
BeanFactory factory = initFactory (locale) ;
try {
return (View) factory.getBean (viewName, View.class);
}

catch (NoSuchBeanDefinitionException ex) {
return null;
}
}
protected synchronized BeanFactory initFactory (Locale locale) throws BeansException {
if (isCache ()) {
BeanFactory cachedFactory = (BeanFactory) this.localeCache.get (locale);

if (cachedFactory! = null) {
return cachedFactory;
}
}
/ / Build list of ResourceBundle references for Locale.
Resource [] resouces = getAllResources ();
if (isCache ()) {
BeanFactory cachedFactory = ( BeanFactory) this.resourceCache.get (resouces);
if (cachedFactory! = null) {
this.localeCache.put (locale, cachedFactory);
return cachedFactory;
}
}
/ / Create child ApplicationContext for views.
GenericWebApplicationContext factory = new GenericWebApplicationContext ();
factory.setParent (getApplicationContext ());
factory.setServletContext (getServletContext ());
/ / Load bean definitions from resource bundle.
PropertiesBeanDefinitionReader reader = new PropertiesBeanDefinitionReader (factory);
reader.setDefaultParentBean (this.defaultParentView);
reader.loadBeanDefinitions (resouces);
factory.refresh ();
if (isCache ()) {
this.localeCache.put ( locale, factory);
this.resourceCache.put (resouces, factory);
}
return factory;
}
@ SuppressWarnings (“unchecked”)
public void destroy () throws BeansException {
for (Iterator it = this.resourceCache . values ??(). iterator (); it.hasNext ();) {
ConfigurableApplicationContext factory = (ConfigurableApplicationContext) it.next ();
factory.close () ;
}
this.localeCache.clear ();
this.resourceCache.clear ();
}
/ **
* need to search for file system resources
* @ return
* @ throws IOException
* /
private Resource [] getAllResources () {
if (scanFileName == null| “”. equals (scanFileName )) {
scanFileName = “view.properties”;
}
String filePattern = “classpath *:/**/*” scanFileName;
ResourcePatternResolver resoler = new PathMatchingResourcePatternResolver ();
try {
return resoler.getResources (filePattern);
} catch (IOException e) {
e.printStackTrace ();
}
return new Resource [0];

}
public String getScanFileName () {
return scanFileName;
}
public void setScanFileName (String scanFileName) {
this.scanFileName = scanFileName;
}
}
– Configuration < br />
in the *- servlet.xml configuration



which identifies the need to scan documents scanFileName , Note: the default scan path is the classpath.

spring2.5 annotation-driven (B) @ PostConstruct @ PreDestroy

July 19, 2010
Spring container Bean is a life-cycle, Spring allows Bean and Bean in the initialization is complete destruction of the former to perform specific operations, you can only achieve InitializingBean / DisposableBean interface to customize the initialization / destruction before the method of operation, you can also specify element init-method/destroy-method property after initialization / destruction of the operation method is called before
JSR-250 is initialized / destroyed before the specified method defines two comment categories, namely @ PostConstruct and @ PreDestroy, this method can only be applied on the two notes. Marked with @ PostConstruct annotation method is called after the class is instantiated, the method marked @ PreDestroy destroyed in the class is called before we know whether it is through the realization of InitializingBean / DisposableBean interface, or through the init- elements method / destroy-method attribute can be configured for the Bean can only specify an initialization / destruction methods. But the use of annotation @ PostConstruct and @ PreDestroy but you can specify more than one initialization / destruction methods, or those who have been marked @ PostConstruct @ PreDestroy annotated method will be initialized / destroyed is executed, generally designated one, to avoid confusion < br />
package com.baobaotao;
import javax.annotation.Resource;
import javax.annotation.PostConstruct;
import javax.annotation.PreDestroy;
publicclass Boss {
@ Resource
private Car car;
@ Resource (name = “office”)
private Office office;
@ PostConstruct
publicvoid postConstruct1 () {
System.out.println (“postConstruct1″);
}
@ PreDestroy
publicvoid preDestroy1 () {

System.out.println (“preDestroy1″);
}
…
}
test class code
package com.baobaotao;
import org.springframework.context.support.ClassPathXmlAp plicationContext;
publicclass AnnoIoCTest {
publicstaticvoid main (String [] args) {
String [] locations = {“beans.xml”};
ClassPathXmlApplicationContext ctx =

new ClassPathXmlApplicationContext (locations);
Boss boss = (Boss) ctx.getBean (“boss”);
System.out.println (boss);

ctx.destroy (); / / close the Spring container, in order to trigger the execution of methods of destruction Bean
}
}
At this time, you will see marked @ PostConstruct of postConstruct1 () method will start in the Spring container to create Boss Bean is triggered when executed, and marked with @ PreDestroy comments preDestroy1 () method will be destroyed before the closure of the Spring container Boss Bean is triggered when the execution.
use simplify configuration
Spring 2.1 adds a new context of Schema namespace, the namespace of the annotation-driven, the introduction of property file , load-time weaver into other functions provide a convenient configuration. We know that comment alone will not do anything, it only provides metadata information. For metadata information that really works, must deal with the metadata of the processor to work.
We previously described AutowiredAnnotationBeanPostProcessor and CommonAnnotationBeanPostProcessor is to deal with these annotations metadata processor. However, a Spring Bean configuration file to define these seemed more clumsy. Spring provides us a convenient way to register these BeanPostProcessor, which is . Consider the following configuration:

xmlns: xsi =” http://www.w3.org/2001/XMLSchema-instance “
xmlns: context =” http://www.springframework.org/schema/context “
xsi: schemaLocation =” http://www.springframework.org/schema/beans
http: / / www.springframework.org / schema / beans / spring-bean s-2.5.xsd
http://www.springframework.org/schema/context
http : / / www.springframework.org / schema / context / spring-co ntext-2.5.xsd “>





< br />


the Spring container to implicitly registered AutowiredAnnotationBeanPostProcessor, CommonAnnotationBeanPostProcessor, PersistenceAnnotationBeanPostProcessor and equiredAnnotationBeanPostProcessor four BeanPostProcessor.
in the configuration file using the context namespace, you must element in the context namespace declarations.

some of the concepts in the spring IOC

September 28, 2010
java2010-09-28 13:06:23 0 comments Word Count: Spring container supports the use of the XML bean factory assembly class

XmlBeanFactory: a simple BeanFactory, it uses java.io.InputStream
ClassPathXmlApplicationContext: an application context, it is loaded from the classpath, context definition file
FileSystemXmlApplicationContext : an application context, it is loaded from the file system context file
XmlWebApplicationContext: Spring-based Web applications up and down the file, file it down from the Web application context definition file loaded.
2: Basic format




3: prototype and single-instance:
default is a single instance, if you use the prototype, you can use the following form

class = “”
singleton = “false” />

4: instantiated and destroyed
can use the init-method, the Bean is instantiated when Hou was immediately called, and you can set destory -method, remove from the window in the Bean before calling. Spring also provides two interfaces to achieve the same functionality: InitializingBean and DisposableBean.
InitializingBean provides a method afterPropertiesSet (), after setting all properties used in the call, DisposableBean provides a destroy -method for the destruction of Bean

class = “”

init-method = “” destroy-method =”"/>

5: Set method by injecting dependencies
Bean usually there are some simple types of properties, to set the basic types of properties

class = “”>





6: References to other Bean
elements used to set the properties to other Bean . Sub-elements with Let achieve this.

class = “”>





7: Internal Bean
do not use another method of assembly Bean reference element is embedded in a element,


class = “”>



8: assembling a collection
Spring support collection type
XML type
java.awt.List, arrays
java.awt.Set

Not without close connection. But also System.InvalidOperationExcept

Exception Details: System.InvalidOperationException: Timeout expired in connection from the pool before the timeout period has expired. This may have occurred because all pooled connections were in use and max pool size was reached.
I use the datareader. but specifically wrote a class to access the database, each executing statements close the connection and datareader of the.
error when I am in the SQL Enterprise Manager to view the current active process . are only one or two connections do not appear full ah ????!!!! but still see the problem
some posts online. basically because they did not close the connection datareader. but I closed the Yeah.
Daniel who help out now do not know how to get the
To aries1001: Under normal circumstances generally timely close out the datareader and connection bar. have to dispose so extreme it? that case Each operation will once again to the connection string of connection I want to change a little from the program to big trouble

The error correction a problem of C #! ! ! ! I am novice constructor for a lack of understanding.

public class MyObject
{
public MyObject ()
{
}
public void WriteLine (string str)
{
Console.WriteLine ( str);
}
partial void Dispose ()
{
Console.WriteLine (“Disposed”);
}
}
class Program
{
public static void Main (string [] args)
{
using (MyObject myObject = new MyObject ())
{
myObject. Write (“quit”);
}
}
}
should be how to change it? Output?

« Older Entries