This week's book giveaway is in the OCPJP forum. We're giving away four copies of OCA/OCP Java SE 7 Programmer I & II Study Guide and have Kathy Sierra & Bert Bates on-line! See this thread for details.
i am developing online credit card payment for a site that sells products .can you please advice me on the following
[color=darkred][color=darkred]1.which server to use:-tomcat 5.0/jboss.i have worked only on these 2 servers.2.should i use EJB's for transactions or just normal java classes would do[/color]3.how should i deal with the socket connections? i have no idea about these things .4.how i get the API's to validate credit card numbers and check for failure or success.[/color]
Ulf Dittmer wrote:Have you signed up with a payment processing provider yet? There is no standard Java API for that, so the proprietary API of whichever one you work with determines some of this.
Other than that, I wouldn't think that the decision between Tomcat and JBoss, and whether or not to use EJB, depends in any meaningful way on the choice of payment processing company.
thanks for the reply..i haven't yet signed up with payment provider..if any of you can suggest a good one it will be helpful.t]rearding the server i ma yet to start developemnt .so i wanted to know which would be a better one jboss or tomcat 5.0 from my perspective for this kind of application.
Joined: Apr 12, 2007
is it necessary and safer to use EJB's for online money transactions or a servlet page is sufficient to direct the data from server to payment processor.what do you suggest .is jboss a stable server than tomcat.
There really isn't a clear-cut answer to the questions you are posing. Ultimately, a lot of it comes down to personal taste.
I find that using a commercial/open source Java EE 5 application server like JBoss, GlassFish or WebLogic with EJB 3 is a lot easier in terms of a learning curve and configuration (perhaps also using Seam). The customers who choose Tomcat (perhaps with Spring) often have a very strong open source bend, create their own frameworks/APIs, want flexibilty and create their own solution stack (perhaps with iBATIS, Quartz, Spring JDBC, AspectJ etc). I also have customers that integrate EJB 3 with Spring on a full-scale Java EE application server where they need Spring features while leveraging container features/simpler application configuration. As mentioned, it is also possible to use EJB 3 with Tomcat utilizing OpenEJB (this is also surprisingly popular).
Hope it helps,
Independent Consultant — Author, EJB 3 in Action — Expert Group Member, Java EE 6 and EJB 3.1