RE: Creating, deploying a Java app jar file from WDSCi and runnin g on iSeries...

[Colin Williams <colin.williams@xxxxxxxxxxxx>]

Mike,

Try copying the classes directly to the IFS, and running it outside of a
jar, to see if your code works that way

cheers
Colin.W
 
Extension   5800
Direct dial   0870 429 5800


-----Original Message-----
From: Mike Burdette [mailto:Mike.Burdette@xxxxxxxxxxxxx] 
Sent: 27 September 2004 19:00
To: java400-l@xxxxxxxxxxxx
Subject: RE: Creating, deploying a Java app jar file from WDSCi and running
on iSeries...


Colin:

I misspoke. It is a standard application not a web app and I am able to 
run it in WDSCi as a stand alone app, not in WAS Test Env.

My RUNJVA command is like you said: the fully qualified class name 
including the package and the JAR file listed in the CLASSPATH parm. 



Mike,

Are you talking about a standard application or a web application. WAS 
Test
Environment is for running web applications, in which case they must be
distributed as EAR or WAR files.

If your talking standard java application, what is your RUNJVA command. 
The
class name including package should be specified on the CLASS  (unless you
specify it in the JAR manifest). The jar file should be listed on the
CLASSPATH 

cheers
Colin.W
 
Extension   5800
Direct dial   0870 429 5800


-----Original Message-----
From: Mike Burdette [mailto:Mike.Burdette@xxxxxxxxxxxxx] 
Sent: 27 September 2004 14:53
To: JAVA400-L@xxxxxxxxxxxx
Subject: Creating, deploying a Java app jar file from WDSCi and running on
iSeries...


I have a Java application that I have developed in WDSCi and wish to 
export in a jar file to the iSeries and run it from there using the RUNJVA 

command.

The app runs from within WDSCi on my PC in the WAS Test Environment. But 
when I export it to the iSeries, the app never loads. I cannot even run it 

in debug as it blows up before the first statement. Here are the errors I 
am getting:

.....
Loading class java/security/BasicPermissionCollection.class from 
/QIBM/ProdData/OS400/Java400/jdk/lib/rt.jar 
Loading class java/lang/VerifyError.class from 
/QIBM/ProdData/OS400/Java400/jdk/lib/rt.jar 
Loading class java/beans/PropertyVetoException.class from 
/QIBM/ProdData/OS400/Java400/jdk/lib/rt.jar 
FATAL ERROR in native method: Received NULL object reference Java program
completed with exit code 134 

I have contacted IBM support, and they have been somewhat helpful, but 
they say the problem is with the way I am creating the jar file. 

Any ideas/suggestions on what might be the problem? Any good resources on 
creating a Java app in/deploying from WDSCi to the iSeries?

Thanks.

BTW, I am running V5R2. 


Mike Burdette


Mike Burdette

Comporium Data Services
Web Development
471 Lakeshore Parkway
PO Box 270
Rock Hill, SC 29731

803 326-4153
803 326-4252 fax
--
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.


This e-mail has been sent by a company of Bertram Group Ltd, whose registered 
office is 1 Broadland Business Park, Norwich, NR7 0WF. 
This message, and any attachments, are intended solely for the addressee and 
may contain privileged or confidential information.  If you are not the 
intended recipient, any disclosure, copying, distribution or any action taken 
or omitted to be taken in reliance on it, is prohibited and may be unlawful.  
If you believe that you have received this email in error, please contact the 
sender immediately. Opinions, conclusions and statements of intent in this 
e-mail are those of the sender and will not bind a Bertram Group Ltd company 
unless confirmed in writing by a director independently of this message. 
Although we have taken steps to ensure that this email and any attachments are 
free from any virus, we advise that in keeping with good computing practice the 
recipient should ensure they are actually virus free.