Wednesday, September 15, 2004
Change to ant build file
Hi Andrew,
Good find. Let’s see if I can solve the problems about the warnings. I am a little concerned about the deprecated calls though. I am positive that we removed all deprecated calls from all code in the entire application.
I will get back to you.
hi Rajeev,
I found out why we weren't getting the validator warnings we should be getting. prsserverclasses.jar wasn't on the validator's class path.
If you find these lines and append the -cp option as I've done, you'll get some interesting warning output about deviations from the ejb spec (see attached)!! Warnings can be disabled with the -nowarn flag.
It looks as though we might be using some deprecated calls - java.rmi.RemoteException is one example.
EJBDeploy options are:
echo Syntax: EJBDeploy inputJar workingDirectory outputJar [options]echo Options:echo -cp "" classpathecho -codegen Only generate the deployment code, do not run RMIC or Javacecho -dbname "Name" The name of the database to createecho -dbschema "Schema" The name of the schema to createecho -dbvendor DBTYPE Set the database vendor type, to one of:echo SQL92 SQL99 DB2UDBWIN_V71 DB2UDBWIN_V72 DB2UDBWIN_V81echo DB2UDBOS390_V6 DB2UDBOS390_V7 DB2UDBAS400_V4R5 DB2UDBAS400_V5echo ORACLE_V8 ORACLE_V9I INFORMIX_V73 INFORMIX_V92 SYBASE_V1192echo SYBASE_V1200 MSSQLSERVER_V7 MSSQLSERVER_2000 MYSQL_V323echo -keep Do not delete the contents of the working directoryecho -ignoreErrors Do not halt for compilation or validation errorsecho -quiet Only output errors, suppress informational messagesecho -novalidate Disable the validation stepsecho -nowarn Disable warning and informational messagesecho -noinform Disable informational messagesecho -rmic "options" Set additional options to use for RMICecho -35 Use the WebSphere 3.5 compatible mapping rulesecho -trace Enable internal tracing
Good find. Let’s see if I can solve the problems about the warnings. I am a little concerned about the deprecated calls though. I am positive that we removed all deprecated calls from all code in the entire application.
I will get back to you.
hi Rajeev,
I found out why we weren't getting the validator warnings we should be getting. prsserverclasses.jar wasn't on the validator's class path.
If you find these lines and append the -cp option as I've done, you'll get some interesting warning output about deviations from the ejb spec (see attached)!! Warnings can be disabled with the -nowarn flag.
It looks as though we might be using some deprecated calls - java.rmi.RemoteException is one example.
EJBDeploy options are:
echo Syntax: EJBDeploy inputJar workingDirectory outputJar [options]echo Options:echo -cp "
