• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

SCEA part 2 - Assumptions

 
karthikeyan kumar
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
I am working on a scenario where my main system has to interface with another external sytem for example payment processing system and it can handle internet transactions. Here can i assume that it uses any java interface like JMS ? Supports Internet transaction could mean anything to me. so i just wonder how we should assume here.

Thanks
Karthi
 
Cameron Wallace McKenzie
author and cow tipper
Saloon Keeper
Posts: 4968
1
Hibernate Spring Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You can pull any JEE component out of your toolkit to solve your problem. If messaging is a good solution, then you're welcome to implement messaging. It might be a good solution.

The criteria will be somewhat 'vague.' You've got to know what someone means when they say 'internet transaction' or something like that. Remember, the reason we have architects is because the people putting together the user requirements aren't always that Java savvy.

-Cameron McKenzie
 
karthikeyan kumar
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks.


I am still thinking that when the customer wants something to buy and he will most likely wants to see the order confirmation or atleast payment approval by using his credit card. So using JMS / Async technology wont be good. But technology like XML-RPC with Https or WebServices will be a good choice and this will provide immediate response to the customer after the credit card validation.


Regards
Karthi

 
Cameron Wallace McKenzie
author and cow tipper
Saloon Keeper
Posts: 4968
1
Hibernate Spring Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sounds good!

-Cameron McKenzie
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic