i searched this question and gave this answer First, read about Portable Java EE clients and "How To Write a Stand-alone Client". The best option would be to change the client to an Application Client or to follow our stand-alone java client recommendations. If that's not possible, you can request that static RMI-IIOP stubs be generated during deployment by using the --generatermistubs option on the asadmin deploy command. In this case, the static RMI-IIOP stubs will be placed within the client.jar file. E.g.
After the command executes, the client.jar containing the static RMI-IIOP stubs will be in /home/user1/clientstubdir/fooappClient.jar.
The reason static RMI-IIOP stubs are still needed in this case is that if the CosNaming provider is instantiated, it is not using the client naming provider from our appserver implementation. It instead uses an ORB from Java SE which does not support dynamic RMI-IIOP.
somebody can help me how can i implement. i need code example please
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com