wood burning stoves 2.0*
The moose likes Other Java Products and Servers and the fly likes Platform Dependence? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Products » Other Java Products and Servers
Bookmark "Platform Dependence?" Watch "Platform Dependence?" New topic
Author

Platform Dependence?

Toby Eggitt
Ranch Hand

Joined: Dec 08, 2004
Posts: 41
I have a strange problem with the RI (beta-Q4, 2004 version)

I and a few of my colleagues are trying to get familiar with this, we have various windows systems, and a Solaris 9 box.

Some of us find that we build the "converter" example application from the J2EE Tutorial and get deployment failures. Closer investigation shows that the .ear files are failing to verify. So far, this has only happened under windows. However, it's happened to three of us, while six others (five on various windows variants, and one on the Solaris box) have perfect success.

In desperation, I copied the working ear file from the Solaris box to my windows sytems, and found that the exact same ear file that verifies correctly on Solaris, fails to verify under windows.

The exact output from the verifier is:

war-ic.war tests.web.elements.WebEjbReferencesElement FAILED
app-client-ic.jar tests.appclient.elements.AppClientEjbReferencesElement FAILED

I suspected this might be trying to say that I haven't resolved the JNDI lookup in the two clients to a real JNDI reference, but the "Sun Specific Settings" for the application shows:

EJB Ref ConverterClient ejb/SimpleConverter ConverterBean
EJB Ref WebApp ejb/TheConverter ConverterBean

And, of course, the self-same ear verifies (and runs) under Solaris.

Any offers please?
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Platform Dependence?