Jaikiran Pai wrote:A non-persistence timer would still be transactional. It just won't be able to maintain state across restarts.
Jaikiran Pai wrote:Using persistent or non-persistent timers is something that your application has to decide. For example, what behaviour do you want to see if a timer is scheduled 30 minutes from now and the server is stopped before the timer is triggered? Would you want to trigger it when the server is up (let's say 5 hours later)?
Already I have used weblogic API to deploy my ear file, it was successful.
Now, I have a typical problem like I would like create a single program through which I want to deploy ear file on different app servers (say weblogic, websphere, oas etc.).
So, I would like to use pure jsr 88 API (from sun java), so that it would be a common API and only class differs is that app server specific classes for registering the implementation factory.
I am able to get the DeploymentManager instance using jsr 88 APIs. Now, next step is getting the DeployableObject for the given ear file, as far as I have searched there is no implementation class for this interface or any classes seem to give the instance of DeployableObject. But, I have seen WebLogicDeployableObject implements DeployableObject, but it would be narrow to weblogic. If I use this class, then for other app servers, I need to have app server specific DeployableObject, isn't it? So, looking for pure jsr 88 api for this.