The application is a payment. steps 1 and 2 retrieves user info. step 3 confirmation. upon confirmation, it will call a different program (different earfile) which will do the payment. and then it will go back to my program to update the database since the payment has been done. before the payment, i set session attributes. after the payment i retrieve them. I just received production issues that the payment was successful but the database wasnt updated. I just found out that the session doesnt exist anymore after the payment. It seldom happens actually but it did happen.
THe problem in my company is that we dont use JMS or MDB. pure
jsp and
servlet.. heck! anyway, i decided to use application scope attributes. i know i know it may be worse. THe reason why i may use this solution is because for every transaction, there is a unique case number generated by my program and is returned to me by the payment program after the payment. So il just use this case number as attribute name when setting them before payment and then use this id to retrieve them after the payment.
Now my problem is, if in server A I set the attributes before payment and then the payment program calls my program in the B server. I am not sure if i will successfully retrieve the attributes... hmm... sounds like its gonna fail but im hoping that it wont.. thanks