I agree that order rejections could be handled better. I also agree that there should probably an indication of error in the GUI if that occurs. I'll address these in one of the next release.
In regards to logging, this is what EventReport is for. It's easy to add extra information to it if you need to. I don't believe that any etra level of logging is neccessary with log4j. I see, but in my opinion this needs to be improved. > > JBT must receive the rejection from market and react properly. First > warning the user and then going on with other strategies. > > Besides, JBT needs a better logging as I said in previous messages. At > least it needs a way to show on-screen real-time events (same events that > get recorded on EventReport.html should be enough) to see if anything is > going wrong. > > These are my thoughs. I'm looking forward to read your comments > > > -- You received this message because you are subscribed to the Google Groups "JBookTrader" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jbooktrader?hl=en.
