zhan's profile肩膀上的阳光PhotosBlog Tools Help
August 18

xsl:variable 与 xsl:param

     
      
      先看个例子:
      <xsl:call-template name="footer"><xsl:with-param name="date"
      select="@lastupdate"/></xsl:call-template>
      <xsl:template name="footer"> <xsl:param name="date">today</xsl:param>
      <hr/> <xsl:text>Last update: </xsl:text> <xsl:value-of
      select="$date"/></xsl:template>
      对xml模板 来说,name属性是很关键的 call-template /apply-template 的name必须要和模板的name
      相对应。模板相当于一个函数,可以暂时这么看。而name相当于函数名称把。
      在call-template中 使用xsl:with-param 相当于函数参数输入
      而参数声明相当就是在xsl:template的 xsl:param
 
      说到xsl:variable。
      可以用<xsl:variable name="ShowDepth"><计算的值></xsl:variable>来声明
      相当于c中的 const 因为变量一旦声明就无法再被改变。
      对于xsl:param和xsl:variable 都可以用 $+name 来直接选择比如
      <xsl:value-of select="$date"/> 就是选择date变量或者参数
      变量和参数,都是有声明范围的 这点和语言中的道理一样。
      最后最最重要一点 :xsl的variable是常量不能再改变
      不要被它的名称迷惑、
August 16

WebSphere JNDI Standalone client

来源:http://forum.java.sun.com/thread.jspa?threadID=425223&start=0

WebSphere JNDI Standalone client
Author: User___Id

Jul 21, 2003 5:18 AM
Hi,

i have some trouble to connect from JBoss to WebSphere 5.0 EJB's. Has someone experience with this topic?

To connect from JBoss I use this settings:
-----
Properties props = new Properties();
props.put(Context.INITIAL_CONTEXT_FACTORY, "com.ibm.websphere.naming.WsnInitialContextFactory");
props.put(Context.PROVIDER_URL, "IIOP://localhost:900");

InitialContext initCtx = new InitialContext(props);
-----

But to get this peace of code working, I need classes from WebSphere. Where are they, and are there any other additional classes and configurations or is there a manual or tutorial about this use case?

All suggestions are welcome
 
Re: WebSphere JNDI Standalone client
Author: gusto2
May 24, 2004 5:58 AM (reply 1 of 39)
Hi,

as far I found out, you have to install WAS Client (it's IBM JRE and libraries). Then
if you use WAS 5.0 EJBs, you'll need tu use iiop://localhost:2809 as PROVIDER_URL and run your standalona app on IBM's JRE.

I still need to call EJB from Sun's JRE, but I still did not succeed

Hope this helps
gusto
 
Re: WebSphere JNDI Standalone client
Author: John_McPeek
May 24, 2004 11:26 AM (reply 2 of 39)
JNDI is CORBA under the covers. You need to use the JBoss factory. I think there is a nameing client jar that the JBOSS docs talk about. The key is that CORBA does NOT require you to use the other "guys" classes (just the stubs and interfaces from you classes). I just got this working myself (a couple weeks ago) from the Sun JVM to Websphere. You use the context factory of the land you live in. In Sun's JVM -> com.sun.jndi.cosnaming.CNCtxFactory. I think that JBOSS built there own JNDI stuff and you will have to use there factory. I think it is "org.jnp.interfaces.NamingContextFactory". I just found something that might help, take a look at it anyway.

http://www.amitysolutions.com.au/documents/JBossTomcatJNDI-technote.pdf
 
Re: WebSphere JNDI Standalone client
Author: sreekav
May 24, 2004 12:09 PM (reply 3 of 39)
WebSphere JNDI Standalone client will only work with the IBM JRE.

And IBM does not ship their JRE standalone. (atleast their 1.4 JRE)

So, you have to do what gusto told you to do. Get the WAS Client and do something with it to get it to work.

It sucks bigtime.

What is the purpose of EJB Clients when you cannot run them outside a piece of software provided by the vendor.

You will find other irritating surprises also.

The ejb client jar that you use needs to be run through their ejbDeploy process before it can be used.

What a horrible architecture.

And getting security to work is another nightmare.

Good Luck.

If you face any specific problems, post back. There are few people who have helped me out in this forum with WebSphere before.

 
Re: WebSphere JNDI Standalone client
Author: John_McPeek
May 24, 2004 5:58 PM (reply 4 of 39)
That is amazing! I have a test client working just as I described it without a single IBM jar. Maybe you have been misinformed. What do you need, the source and instruction on how to install it?
 
Re: WebSphere JNDI Standalone client
Author: sreekav
May 25, 2004 6:45 AM (reply 5 of 39)
Thanks for the info.

I was told by IBM folks that I had to use their JDK to call their EJBs.

I would be interested in knowing how not to use the IBM JDK.

Are you making secure EJB calls?

 
Re: WebSphere JNDI Standalone client
Author: John_McPeek
May 25, 2004 9:20 AM (reply 6 of 39)
Secure EJB calls? I haven't heard of such a thing.

I think you were using WAS5, yes? I think that there was an interoperability issue in days gone by. That was related to differences in the information used in the IBM orb and others. Sun changed the spec to ensure such issues went away. All complient implementations should interoperate out of the box now.

The thing is, you get the ContextFactoy for your JVM and as long a the stubs and interfaces are available the CORBA under the covers makes everything happy. I went through a lot of looking to figure out how to make it work, because there are several people still saying the "you need the JVM of the container you are hitting" thing. In fact as you are using JBOSS and I assume you are using the Sun JVM, you can ignore the JBOSS JNDI (JNP) stuff and use the Sun ContextFactoy (com.sun.jndi.cosnaming.CNCtxFactory). Just set the ContextFactoy and the URL (corbaloc:iiop:myWASserver:2809) and magic. Remember outside the container you are calling (WAS) you don't use java:comp/...... it looks like

cell/nodes/myNode/servers/server1/ejb/myCoolNewEjb

Are you using WSAD? Makes life easier. Write an EJB ( String ping(String) ) and a client to call it. Get the client working using the WAS factory and the IBM JVM. Then, move to a box with Sun's JVM installed and run it again but with com.sun.jndi.cosnaming.CNCtxFactory in stead of com.ibm.websphere.naming.WsnInitialContextFactory. To run the client on the WAS JVM you will need the IBM j2ee.jar, namingClient.jar, ecutils.jar. To run the client on the Sun JVM all you need is Sun's j2ee.jar.

Let me know how it come out.
 
Re: WebSphere JNDI Standalone client
Author: sreekav
May 26, 2004 4:38 AM (reply 7 of 39)
I will try out your suggestions.

By secure EJB calls, I meant calling ejb's that are declaratively secured by the container.
 
Re: WebSphere JNDI Standalone client
Author: John_McPeek
May 26, 2004 5:25 PM (reply 8 of 39)
Hey someone left this in a post and I keep it around because it has some good stuff in it. It seems to talk about secure EJB access.

http://docs.sun.com/source/817-6087/dgacc.html#wp1010634

Tell me what you think.
 
Re: WebSphere JNDI Standalone client
Author: mduvall_vt
Jul 29, 2004 2:44 PM (reply 9 of 39)
John McPeek,

We are trying to access items in the WAS JNDI via a client that is using a Sun JRE, and we are having problems.
Specifically, we are trying to look up on MQ Connection Factory. When I try the lookup the object in the
JNDI, I get back a JNDI Reference object that has the correct name but the class name and class factory fields
are blank.(Which is probably why I'm getting a Reference object rather than the actual Connection Factory; because
it can't figure out how to instantiate it) I'm able to access the very same JNDI registry with an IBM JRE client
and it works just fine.

In your previous posts on this thread, I believe that you stated that you had been able to access
the Websphere JNDI via a client using a Sun JRE and had offered to the source code and install instructions.

I would very much appreciate it if you could post your sample code and install instructions, or email the same to me. You can email me at:

mrduvallNOSPAM@excite.com (remove the "NOSPAM" part).



Thanks,
Mike
 
Re: WebSphere JNDI Standalone client
Author: java_vishnu_ak
Aug 1, 2004 8:17 PM (reply 10 of 39)
Hi,

I had the same problem connecting to a websphere ejb from sun jdk 1.4, finally got it working using "Sun ContextFactoy (com.sun.jndi.cosnaming.CNCtxFactory)", it works cool, but when trying to connect to MQ, it doesnt work as the objects are returned as null.... To work-around this, you can try creating a simple TCPIP Client for MQ and totally ignore the contextfactory... Hope this helps...

Thanks
Vishnu
 
Re: WebSphere JNDI Standalone client
Author: thanghv
Sep 23, 2004 1:57 AM (reply 11 of 39)
i do like your guide, use ibm jdk 1.4.2, j2ee.jar, clientNaming.jar, from wsas 5.0. but i've got following exception:


Unable to read required resource: implfactory.properties
java.lang.NullPointerException
at java.io.Reader.<init>(Reader.java:74)
at java.io.InputStreamReader.<init>(InputStreamReader.java:118)
at java.util.Properties.load(Properties.java:298)
at com.ibm.ws.util.ImplFactory$1.run(ImplFactory.java:38)
at java.security.AccessController.doPrivileged1(Native Method)
at java.security.AccessController.doPrivileged(AccessController.java:351
)
at com.ibm.ws.util.ImplFactory.<clinit>(ImplFactory.java:33)
at com.ibm.ejs.jts.jts.CurrentFactory.<clinit>(CurrentFactory.java:56)
at com.ibm.ws.naming.jndicos.CNContextImpl.suspendTransaction(CNContextI
mpl.java:3847)
at com.ibm.ws.naming.jndicos.CNContextImpl.cosResolve(CNContextImpl.java
:3307)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1
496)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1
457)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:116
7)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:132)
at javax.naming.InitialContext.lookup(InitialContext.java:361)
at Test.main(Test.java:18)
Exception in thread "P=794604:O=0:CT" javax.naming.NamingException: The JNDI ope
ration "lookup"on the context "localhost/nodes/localhost/servers/server1" with t
he name "localhost/nodes/localhost/servers/server1/ejb/com/cicat/TestHome" faile
d. Please get the root cause Throwable contained in this NamingException for mo
re information. Root exception is java.lang.NoClassDefFoundError: Invalid Imple
mentation Key, com.ibm.ws.transaction.TXCurrent
at com.ibm.ws.util.ImplFactory.loadClassFromKey(ImplFactory.java:104)
at com.ibm.ejs.jts.jts.CurrentFactory.<clinit>(CurrentFactory.java:56)
at com.ibm.ws.naming.jndicos.CNContextImpl.suspendTransaction(CNContextI
mpl.java:3847)
at com.ibm.ws.naming.jndicos.CNContextImpl.cosResolve(CNContextImpl.java
:3307)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1
496)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1
457)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:116
7)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:132)
at javax.naming.InitialContext.lookup(InitialContext.java:361)
at Test.main(Test.java:18)
Press any key to continue...

and i must add %"WSAD_HOME%"\runtimes\base_v5\properties to class path, so it cand find implfactory.properties. and it work after many hard day.
 
Re: WebSphere JNDI Standalone client
Author: John_McPeek
Sep 26, 2004 9:22 AM (reply 12 of 39)
Are you using WSAD to do this? WSAD does the MQ stuff in memory and you can't access the Queues from a stand-alone client. WAS is a different story. It should work with a real MQ Queue using the SUN JVM.
 
Re: WebSphere JNDI Standalone client
Author: John_McPeek
Sep 26, 2004 10:11 AM (reply 13 of 39)
Ok,
Here is code I wrote for the test (changed the names to protect the innocent). You need to take the EJB classes and run RMIC on them. That will generate the stubs for CORBA. If you are using WSAD you can make this simple - start an Enterprise App and add an EJB project. Add an EJB to the EJB project and use PingEjb as the name. Once the EJB code is generated replace with the code below for each of the 3 files. After you add the ejb (with the name PingEjb) to the EJB project, right click on the EJB project and "Generate ....". This will call RMIC and generate a bunch of stuff. The client will need the PingEjb and PingEjbHome classes as well as the stubs. The stubs are used by the CORBA stuff and look like this ( _PingEjb_Stub.class ).


Client Code:
package com.bcbsfl.vo.sae.pingtest.facade;
 
import java.util.Hashtable;
 
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.rmi.PortableRemoteObject;
 
import com.big.company.x.pingtest.PingEjb;
import com.big.company.x.pingtest.PingEjbHome;
 
/**
 * @author a1wr
 */
public class PingRemoteEJB {
 PingEjb ejbPinger;
 
 PingRemoteEJB(
   String jndiPath,
   String contextFactory,
   String host,
   String port ) throws Exception {
  
  Hashtable env = new Hashtable();
  env.put(Context.INITIAL_CONTEXT_FACTORY, contextFactory );
  env.put(Context.PROVIDER_URL, "corbaloc:iiop:" + host + ":" + port );
  
  Context initial = new InitialContext( env );
    
  Object objref = initial.lookup( jndiPath );
  
  PingEjbHome home = (PingEjbHome) PortableRemoteObject.narrow( objref, PingEjbHome.class );
   
  ejbPinger = home.create();
 }
 
 /**
  * @see com.bcbsfl.vo.sae.pingtest.Pinger#ping(String)
  */
 public String ping( String pingMessage ) {
  String responce = null;
  
  try {
   responce = ejbPinger.ping( pingMessage );
  } catch ( Exception e ) {
   e.printStackTrace();
  }
  
  return responce;
 }
 
 public static void Main(String[] args) throws Exception {
  
  //Note this stuff is dependent on your setup
  String jndiPath = "cell/nodes/localhost/servers/server1/ejb/PingEjbHome";
  String contextFactory = null;
  String host = "youMachineNameHere";
  String port = "2809";
  
  String factory =  
   /*
   "IBM_JDK";
   /*/
   "SUN_JDK"; //*/// this factory name also works for Oracle i.e. 9iAS
  
  if (factory.equals( "IBM_JDK" )) {
   contextFactory = "com.ibm.websphere.naming.WsnInitialContextFactory";
  }
  else if (factory.equals( "SUN_JDK" )) {
   contextFactory = "com.sun.jndi.cosnaming.CNCtxFactory";
  }
 
  PingRemoteEJB pinger = new PingRemoteEJB( jndiPath, contextFactory, host, port );
  
  String message = pinger.ping( "All that work and this is all it does.!?" );
  
  System.out.println( message );
 }
 
}


PingEjb.java
package com.big.company.x.pingtest;
 
import java.rmi.RemoteException;
 
/**
 * Remote interface for Enterprise Bean: PingEJB
 */
public interface PingEjb
 extends javax.ejb.EJBObject {
  
 public String ping(String pingMessage) throws RemoteException;
}


PingEjbHome.java
package com.big.company.x.pingtest;
/**
 * Home interface for Enterprise Bean: PingEJB
 */
public interface PingEjbHome extends javax.ejb.EJBHome {
 
 /**
  * Creates a default instance of Session Bean: PingEJB
  */
 public com.big.company.x.pingtest.PingEjb create()
  throws javax.ejb.CreateException, java.rmi.RemoteException;
}


PingEjbBean.java
package com.big.company.x.pingtest;
 
 
/**
 * Ping bean to show that JNDI works without the other guys stuff.
 */
public class PingEjbBean implements javax.ejb.SessionBean { 
 
 private javax.ejb.SessionContext mySessionCtx;
 
 /**
  * Passthrough pingMessage back to the caller.
  * 
  * @param pingMessage The message to be sent back.
  * 
  * @return The same message that was sent in.
  */
 public String ping(String pingMessage) {
  return pingMessage;
 }
 
/*****************************************************************************
 These are just the standard EJB methods you have to implement. WSAD generated
 these for me. Life is good like that.
*****************************************************************************/ 
 
 /**
  * getSessionContext
  */
 public javax.ejb.SessionContext getSessionContext() {
  return mySessionCtx;
 }
 
 /**
  * setSessionContext
  */
 public void setSessionContext(javax.ejb.SessionContext ctx) {
 }
 
 /**
  * ejbCreate
  */
 public void ejbCreate() throws javax.ejb.CreateException {
 }
 
 /**
  * ejbActivate
  */
 public void ejbActivate() {
 }
 
 /**
  * ejbPassivate
  */
 public void ejbPassivate() {
 }
 
 /**
  * ejbRemove
  */
 public void ejbRemove() {
 }
}

 
Re: WebSphere JNDI Standalone client
Author: John_McPeek
Sep 26, 2004 10:22 AM (reply 14 of 39)
Ok,
Here is code I wrote for the test (changed the names to protect the innocent). You need to take the EJB classes and run RMIC on them. That will generate the stubs for CORBA. If you are using WSAD you can make this simple - start an Enterprise App and add an EJB project. Add an EJB to the EJB project and use PingEjb as the name. Once the EJB code is generated replace with the code below for each of the 3 files. After you add the ejb (with the name PingEjb) to the EJB project, right click on the EJB project and "Generate ....". This will call RMIC and generate a bunch of stuff. The client will need the PingEjb and PingEjbHome classes as well as the stubs. The stubs are used by the CORBA stuff and look like this ( _PingEjb_Stub.class ). Put the EJB stuff is the path for the client and run it.

Client code:
package com.big.company.x.ping.client;
 
import java.util.Hashtable;
 
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.rmi.PortableRemoteObject;
 
import com.big.company.x.pingtest.PingEjb;
import com.big.company.x.pingtest.PingEjbHome;
 
/**
 * @author John
 */
public class PingRemoteEJB {
 PingEjb ejbPinger;
 
 PingRemoteEJB(
   String jndiPath,
   String contextFactory,
   String host,
   String port ) throws Exception {
  
  Hashtable env = new Hashtable();
  env.put(Context.INITIAL_CONTEXT_FACTORY, contextFactory );
  env.put(Context.PROVIDER_URL, "corbaloc:iiop:" + host + ":" + port );
  
  Context initial = new InitialContext( env );
    
  Object objref = initial.lookup( jndiPath );
  
  PingEjbHome home = (PingEjbHome) PortableRemoteObject.narrow( objref, PingEjbHome.class );
   
  ejbPinger = home.create();
 }
 
 /**
  */
 public String ping( String pingMessage ) {
  String responce = null;
  
  try {
   responce = ejbPinger.ping( pingMessage );
  } catch ( Exception e ) {
   e.printStackTrace();
  }
  
  return responce;
 }
 
 public static void Main(String[] args) throws Exception {
  
  //Note this stuff is dependent on your setup
  String jndiPath = "cell/nodes/localhost/servers/server1/ejb/PingEjbHome";
  String contextFactory = null;
  String host = "youMachineNameHere";
  String port = "2809";
  
  String factory =  
   //"IBM_JDK";
   "SUN_JDK"; // This factory name also works for Oracle i.e. 9iAS 
  
  if (factory.equals( "IBM_JDK" )) {
   contextFactory = "com.ibm.websphere.naming.WsnInitialContextFactory";
  }
  else if (factory.equals( "SUN_JDK" )) {
   contextFactory = "com.sun.jndi.cosnaming.CNCtxFactory";
  }
 
  PingRemoteEJB pinger = new PingRemoteEJB( jndiPath, contextFactory, host, port );
  
  String message = pinger.ping( "All that work and this is all it does.!?" );
  
  System.out.println( message );
 }
 
}


PingEjb.java :
package com.big.company.x.pingtest;
 
import java.rmi.RemoteException;
 
/**
 * Remote interface for Enterprise Bean: PingEJB
 */
public interface PingEjb
 extends javax.ejb.EJBObject {
  
 public String ping(String pingMessage) throws RemoteException;
}


PingEjbHome.java :
package com.big.company.x.pingtest;
/**
 * Home interface for Enterprise Bean: PingEJB
 */
public interface PingEjbHome extends javax.ejb.EJBHome {
 
 /**
  * Creates a default instance of Session Bean: PingEJB
  */
 public com.big.company.x.pingtest.PingEjb create()
  throws javax.ejb.CreateException, java.rmi.RemoteException;
}


PingEjbBean.java :
package com.big.company.x.pingtest;
 
 
/**
 * Ping bean to show that JNDI works without the other guys stuff.
 */
public class PingEjbBean implements javax.ejb.SessionBean { 
 
 private javax.ejb.SessionContext mySessionCtx;
 
 /**
  * Passthrough pingMessage back to the caller.
  * 
  * @param pingMessage The message to be sent back.
  * 
  * @return The same message that was sent in.
  */
 public String ping(String pingMessage) {
  return pingMessage;
 }
 
/*****************************************************************************
 These are just the standard EJB methods you have to implement. WSAD generated
 these for me. Life is good like that.
*****************************************************************************/ 
 
 /**
  * getSessionContext
  */
 public javax.ejb.SessionContext getSessionContext() {
  return mySessionCtx;
 }
 
 /**
  * setSessionContext
  */
 public void setSessionContext(javax.ejb.SessionContext ctx) {
 }
 
 /**
  * ejbCreate
  */
 public void ejbCreate() throws javax.ejb.CreateException {
 }
 
 /**
  * ejbActivate
  */
 public void ejbActivate() {
 }
 
 /**
  * ejbPassivate
  */
 public void ejbPassivate() {
 }
 
 /**
  * ejbRemove
  */
 public void ejbRemove() {
 }
}
August 03

BPM_jBPMvsWFMOpen

以下是本人在学习两个工作流系统时做了一些粗略的对比,不对之处请指正!

JBPM与WFMOPEN规范的比较
JBPM
采用自己的流程定义(JPDL),虽然针对性强,灵活度高,但由于没有提供规范接口,从而不易于与其它工作流引擎进行交互使用.
WFMOPEN
整体构架严格遵循WFMC与OMG制定的接口标准.

JBPM与WFMOPEN流程定义语言的比较
JBPM(JPDL)
商务逻辑定义采用自己定义的JPDL.
JBPM把整个业务流程看成UML状态图(图).
JPDL描述的是流程的过程,是通过状态表示,流程由以下元素组成(图)

 


JBPM与WFMOPEN流程定义语言的比较

WFMOPEN(XPDL)
商务逻辑定义采用业界标准XPDL.
 XPDL把一个业务流程看成一个UML活动图(图)


JBPM与WFMOPEN辅助工具的比较
JBPM
对于JBPM来说最大的缺点就是辅助工具太少,很多东西要自己定义.
    表现在:
没有图形画的流程监控工具.
流程图形画定义工具太弱.
与其他系统集成时是需要特别编写代码
WFMOPEN
 同JBPM相比,WFMOPEN有较强的流程图形化定义工具(JAWE).
 WFMOPEN还提供一个管理平台以便对流程进行监控以及一个工作平台.
可以通过AGENT TOOL方便的与其他业务系统集成


JBPM与WFMOPEN运行机制的比较
角色的分配
JBPM
角色在processdefinition.xml 被定义,当流程到了某一个State时,可以通过调用已定义的AssignmentHandler进行识别和分配.
WFMOPEN
首先根据人来创建一个资源,然后根据这个资源来得到与这个资源相关的Activity.

 

JBPM与WFMOPEN运行机制的比较
与Application的交互
JBPM
如果流程中的某一步需要调用一个外部应用时, 必须在ActionHandler实现调用.
WFMOPEN
提供了一组工具代理(JBPM所不具备的),工具代理就相当于给工作流引擎加了一个Wrapper,加上它又支持业界标准,能够做到与Application分开,也就是说当Application要参与到流程中时,只需在应用集中扩展相应属性即可.

结论
虽然现在出的JBPM3.0 Alpha比起JBPM2.0有了不少改进,如提供流程编辑器,JPDL中多引进了一些元素,但本质上还是没有什么变化,并不支持规范标准,尽管有预测JBPM3.0最终将支持BPEL4WS,但目前还没有,此外它是Alpha版的, 综合上述,WFMOPEN更接近于一个成熟的工作流产品.

 

 

中国一些流行词语的英文表达

1.素质教育:Quality Education
2. EQ:分两种,一种为教育商数Educational quotient, 另一种情感商数Emotional
quotient
3.保险业:the insurance industry
4.保证重点指出:ensure funding for priority areas
5.补发拖欠的养老金:clear up pension payments in arrears
6.不良贷款:non-perFORMing loan
7.层层转包和违法分包:mutlti-level contracting and illegal
subcontracting
8.城乡信用社:credit cooperative in both urban and rural areas
9.城镇居民最低生活保障:a minimum standard of living for city residents
10.城镇职工医疗保障制度:the system of medical insurance for
urban workers
11.出口信贷:export credit
12.贷款质量:loan quality
13.贷款质量五级分类办法:the five-category assets classification
for bank loans
14.防范和化解金融风险:take precautions against and reduce
financial risks
15.防洪工程:flood-prevention project
16.非法外汇交易:illegal foreign exchange transaction
17.非贸易收汇:foreign exchange earnings through nontrade channels
18.非银行金融机构:non-bank financial institutions
19.费改税:transFORM administrative feessintostaxes
20.跟踪审计:foolow-up auditing
21.工程监理制度:the monitoring system for projects
22.国有资产安全:the safety of state-owned assets
23.过度开垦:excess reclamation
24.合同管理制度:the contract system for governing projects
25.积极的财政政策:pro-active fiscal policy
26.基本生活费:basic allowance
27.解除劳动关系:sever labor relation
28.金融监管责任制:the responsibility system for financial supervision
29.经济安全:economic security
30.靠扩大财政赤字搞建设:to increase the deficit to spend more on
development
31.扩大国内需求:the expansion of domestic demand
32.拉动经济增长:fuel economic growth
33.粮食仓库:grain depot
34.粮食收购企业:grain collection and storage enterprise
35.粮食收购资金实行封闭运行:closed operation of grain purchase funds
36.粮食销售市场:grain sales market
37.劣质工程:shoddy engineering
38.乱收费、乱摊派、乱罚款:arbitrary charges, fund-raising, quotas and
fines
39.骗汇、逃汇、套汇:obtain foreign currency under false pretenses, not
turn over foreign owed to the government and illegal arbitrage
40.融资渠道:financing channels
41.商业信贷原则:the principles for commercial credit
42.社会保险机构:social security institution
43.失业保险金:unemployment insurance benefits
44.偷税、骗税、逃税、抗税:tax evasion, tax fraud and refusal to pay taxes
45.外汇收支:foreign exchange revenue and spending
46.安居工程:housing project for low-income urban residents
47.信息化:inFORMation-based; inFORMationization
48.智力密集型:concentration of brain power; knowledge- intensive
49.外资企业:overseas-funded enterprises
50.下岗职工:laid-off workers
51.分流:reposition of redundant personnel
52.素质教育:education for all-round development
53.豆腐渣工程:jerry-built projects
54.社会治安情况:law-and-order situation
55.民族国家:nation state
56.“台独”:"independence of Taiwan"
57.台湾当局:Taiwan authorities
58.台湾同胞:Taiwan compatriots
59.台湾是中国领土不可分割的一部分:Taiwan is an inalienable part of the
Chinese territory.
60.西部大开发:Development of the West Regions
61.可持续性发展:sustainable development
62.风险投资:risk investment
63.通货紧缩:deflation
64.扩大内需:to expand domestic demand
65.计算机辅助教学:computer-assisted instruction ( CAI )
66.网络空间:cyberspace
67.虚拟现实:virtual reality
68.网民:netizen ( net citizen )
69.电脑犯罪:computer crime
70.电子商务:the e-business
71.网上购物:shopping online
72.应试教育:exam-oriented education
73.学生减负:to reduce study load
74.“厄尔尼诺”:(EL Nino)
75.“拉尼娜”:(La Nina)
76.“智商”:(IQ)
77.“情商”:(EQ)
78.“第三产业”:(third/tertiary industry,service sector,third
sequence of enterprises)79.“第四产业”:(quaternary/inFORMation
industry)
79.“军嫂”:(military spouse)
80.“峰会”(香港译“极峰会议”)”:summit(conference)
81.“克隆”:clone
82.“冰毒”:ice
83.“摇头丸”:dancing outreach
84.“传销”:multi level marketing
85.“(计算机)2000年问题”:Y2K problem(y for year, k for kilo or
thousand)
86.“白皮书”:white paper(不是white cover book)
87.“傻瓜相机”:Instamatic(商标名,焦距、镜头均固定,被称为
foolproof相机);
88.“白条”:IOU note(IOU:债款、债务,由I owe you的读音缩略
转义而来)
89.“巡回招聘”:milk round(一种招聘毕业生的方式,大公司走访各
大学及学院,
向求职者介绍本公司情况并与报名者晤谈)。
90.“减员增效”:increase efficiency by downsizing staff;
91.“抓大放小”:manage large enterprises well while ease control
over small ones;
92.“市政府要办的X件实事”:x major projects that should be given
top priority as designated on the municipal government’s working agenda;
93.“两个基本点”:two focal points,two of the major points of
the line set by the 13th Congress of the CPC,I.e.upholding the four
cardinal principles
and the policies
reFORM,opening to the outside world and invigorating domestic
economy。
94.“投资热点”:a region attractive to investors,a muchsought
piece of hand, popular investment spot
95.“移动电话”:本系cellular(有时简作cel)或mobile(tele)phone
96.“三角债”:chain debts或debt chains
97.“拳头产品”:knockout product
98.“投诉热线”:dial-a-cheat confidential hotline(打电话告诉一 件欺诈事件)
99.“三通”的现译文three links:link of trade,travel and post
100.“外资”:overseas investments
101.“开放”:open to the outside world
102.“联防”:community/teampolicing(一种由警察和辖区居民共同参与的治安管
理)
103.“三陪服务”:escort services(陪伴服务)。
104.“五讲四美”:five stresses and four points of beauty
105.“暴利”:excessive/extravagant/exorbitant/sudden huge profit
(windfall profit也好)
106.“暴发户”:upstart,parvenu,noov(e),nouveau riche(new rich),
jumped-up people(口语)
107.“快餐”:snack(food),quick meal,fast(food,meal),takeaway,
carryout,MRE(meals ready to eat)“一次(性/用)”
108.一次处理:single/primary treatment;
109.一次污染:primary pollution;
110.一次冻透:straight;freez-ing;
111.一次空气:fresh/primary air;
112.一次爆破:onepull;
113.一次付清:pay in full;
114.一次消费:one-time-consumption;
115.一次误差:first-order error;
116.一次成像照片:a Polaroid picture;
117.一次偿还信贷:non-in-stallment;
118.一次性杯子:sanitary cup;
119.一次性筷子:disposable chopsticks;
120.一次性收入:lump-sum payment;
121.一次用包装:non-returnable container;
122.一次用相机:single-use camera
123.西部开发:Develop Western Regions
124.假日经济:Holiday Economy
125.手机的利与弊:Advantages and Disadvantages of the CellPhone
126.传呼机不久将会被淘汰吗?:Can Beepers Be Soon Out of
Use?
127.电脑病毒:Computer Viruses
128.网上犯罪:Cyber Crimes
129.旅游热:Tourism Wave
130.打拐:Cracking Down on the Abduction of Women and Children
131.反毒斗争:Anti-drug Battle
132.黑客:Hackers
133.减负:Reduction of Students’Study Load
134.中国加入世贸组织:China’s Entrysintosthe WTO
135.沙尘暴:Sandstorms
136.告别1999:Farewell to the Special Year 1999
137.千年虫:The Millennium Bug
138.千禧年的梦想:My Millennium Dreams
139.拥抱新千年:Embracing the New Millennium
140.网上购物:Shopping on the Net
141.参考书的负面效应:My View on the Negative Effects of
Reference Books
142.因特网的利与弊:Positive and Negative Aspects of Internet
143.人类第一张基因草图的意义:The Significance of the First Working Draft
of Human Genome Map
144.高校合并:The Merging of Universities
145.网上求职:Hunting for A Job on Internet
146.何为新世纪的好老师?:What Is a Good Teacher in the Next
Century?
147.中国的外资:China’s foreign Investment
148.中国的人才流失:The Talent Flight in China
149.性教育:Sex Education
150.明天的因特网:The Future Tomorrows Internet
151.课堂是以教师为中心还是以学生为中心?:A Teacher-centered
Class or A Student-centered Class?
152.现有的考试制度的利与弊:The Positive and Negative Aspects
of Exams and the Existing Examination System
153.中国的因特网:Internet in China
154.中国的电脑:Computers in China
155.中国的大学英语教学:College English Teaching in China
156.新的收费政策把学生拒之门外了吗?:Does New Tuition Policy Keep
Students Away?
157.家教的利与弊:Positive and Negative Aspects of Home Tutoring
158.教师,国家的未来:Teachers, A Nation’s Future
159.电子词典:Electronic Dictionaries
160.教育应是应试教育还是素质教育:Education:Examination-oriented
or Quality- oriented
161.提倡创新精神:Develop Our Creative Mind
162.计算机辅助教学:CAI/Computer Assisted Instruction
163.自动取款机的利与弊:Advantages and Disadvantages of the ATM
164.展望廿一世纪:Looking Forward to the 21st Century
165.盗版问题:Problem of Piracy
166.学会如何学习:Learn How to Learn
167.假文凭:Fake Diplomas
168.书的不良影响:My View on the Negative Effects of Books
169.人们为什么热衷于摸彩票?:Why Do People Like to Try Their
Luck on Lottery?
170.兼职工作:My View on a Part-time Job
171.无偿献血:Blood Donation without Repayment
172.留学海外:Studying Abroad
173.发展经济还是保护环境?:Developing Economy or Protecting
the Environment?
174.电子邮件:The Internet E-mail
175.拥抱知识经济的新时代:Embracing the Knowledge Economy Age
176.努力更新知识:Trying to Renew Knowledge
177.深化(中国的)改革:Deepen China’s ReFORM
178.因特网的利与弊:The Advantages and Disadvantages of Internet
179.我们需要因特网吗?:Do We Need Internet?
180.大学英语考试:College English Test
181.大学英语四、六级考试有必要吗?:Is the College English Test
Band 4/Band 6 Necessary?
182.廿一世纪的青年人:The Youth of the 21st Century

真绝,中国特色的错别字

植树造“零”
白“收”起家
勤“捞”致富
选“霸”干部
任人唯“闲”
择“油”录取
“得财”兼“币”
检查“宴”收
大力支“吃”
为民“储”害
提“钱”释放
“攻官”小姐
爱“名”如子
“酒精”考验
“明”主选举
两袖“勤俸”(清风)
繁荣“娼”盛
一代“痿”人
秉“贡”执法
“私”而后已
领导特“色”(这个并不是错别字,而是双关语!)
人民政“腐”
饮酒吃职(引咎辞职)
人民万“税
 

zhan zhan

快乐就是这样,它往往在为着一个明确的目的忙得无暇顾及其他的时候,突然来访
Photo 1 of 2