a)<classpath>
<pathelementpath="${classpath}"/>
<pathelementlocation="lib/helper.jar"/>
</classpath>
b)<classpath>
      < pathelementpath="${classpath}"/ > 方式 ① ：引用特定的变量

      < filesetdir="lib" > 方式 ② ：指向特定的文件集
           <includename="**/*.jar"/>
      </fileset>

           < pathelementlocation="classes"/ > 方式 ③ ：指向单个目录

      < dirsetdir="${build.dir}" > 方式 ④ ：指向特定目录集
           <includename="apps/**/classes"/>
           <excludename="apps/**/*Test*"/>
      </dirset>

      < filelistrefid="third-party_jars"/ > 方式 ⑤ ：引用指定文件列表
</classpath>
c) <copy todir="${web.inf.classes}">
  <fileset dir="src/resources">
   <include name="**/spring/*.xml" />
   <include name="**/xfire/*.xml" />
  </fileset>
  <fileset dir="src/main">
   <include name="**/*.xml" />
  </fileset>
 </copy>

3)Failed to setup clustering", what does it mean?

  [JBossCacheService][main] jboss.cache:service=TomcatClusteringCache service to Tomcat clustering not found

  [JBossCacheManager][main] JBossCacheService to Tomcat clustering not found

  [TomcatDeployer][main] Failed to setup clustering, clustering disabled

There's two possibilities here:

1) Since 3.2.6, HTTP session replication is based on JBossCache, and more precisely the TomcatClusteringCache service.In 3.2.6, 3.2.7, 4.0.1 and 4.0.1SP1, the dependency on this service is missing in Tomcat's jboss-service.xml. To fix it, please edit /all/deploy/jbossweb-tomcat5x.sar/META-INF/jboss-service.xml and enable the <depends optional-attribute-name="CacheName?"> element, update the MBean ObjectName as well as the <depends> element itself.

The resulting code should look as follows:

      <!--

         Configuration for HTTP Session Clustering using JBossCache

      -->

      <depends>jboss.cache:service=TomcatClusteringCache</depends>

instead of

      <!--

         Configuration for HTTP Session Clustering using JBossCache

      -->

      <!--

      <depends optional-attribute-name="CacheName">jboss.cache:service=TreeCache</depends>

      -->

2) This error could also come up if you're trying to remove the clustering capabilities from the all configuration as explained in JBossASTuningSliming. Even though you might have modified jbossweb-tomcat5x.sar/META-INF/jboss-service.xml to remove the dependency on

jboss.cache:service=TomcatClusteringCache

, if the web application is deployed as

<distributable/>

, AS will try starting up

jboss.cache:service=TomcatClusteringCache

, for HTTP session replication. In this case, the ERROR message should not be considered as a failure because if it can't start it up, it'll log the ERROR but will continue working as normal.

4) 一次性导出所有oracle sequence

select 'create sequence ABEL.'|| SEQUENCE_NAME || ' minvalue '||MIN_VALUE||' maxvalue '||MAX_VALUE||' start with '||LAST_NUMBER||' increment by '||INCREMENT_BY||' cache '||CACHE_SIZE||' ;' from dba_sequences where SEQUENCE_OWNER = 'TEEMA'

5) Ora-01033: Oracle initialization or shutdown in process.

然后用orca打开rose.msi，删除(VersionNT AND (NOT RSWINXPHOME))OR (DISABLE_PLATFORM_BLOCKS = 1)即可。

另外错误：
应用rational rose 后退出时报错："MEM_BAD_POINTER"

解决办法：
1) extract shw32.dll from the attached zip file.

2) locate the copy of shw32.dll that the affected program (the one
that's giving the MEM_BAD_POINTER error) is using. Rename this file,
or move it to some other directory for safe keeping. Note: this step
is not strictly necessary, BUT if you experience problems with our
new DLL, the first thing we're going to suggest is that you revert to
your old one.

3) with your old shw32.dll renamed or moved for safe keeping, install
the new shw32.dll where the old one used to be. Now run your app as
usual and verify that the error no longer appears.

4) if after step 3 you still see the MEM_BAD_POINTER error, search
your hard drives for any other occurrences of shw32.dll and replace
those (using the above procedures), one at a time, until the error no
longer appears.

下载补丁

四、人为什么要到这个世界来?
http://zhidao.baidu.com/question/5921958.html?pn=25