[jboss-dev-forums] [Design of JBoss ESB] - Re: Action Processing Pipelines, updated Trailblazer etc...

"kurt.stam(a)jboss.com" wrote : Yes the banks are using XStream, they are standalone bank applications. Why is the loanbroker now using XStream? We should be using our own marshalling implementation, why was this changed? I'm afraid I can't answer that one Kurt!! I just checked ProcessCreditResponse.java in the beta1 release and I can see now how this was able to work before. See in the sendJMSToBank method - it registers an alias such that org.jboss.soa.esb.samples.loanbroker.banks.BanksQuoteRequest gets mapped to org.jboss.soa.esb.samples.loanbroker.banks.BankQuoteRequest. Look really hard and you'll spot the difference. ObjectToXStream just uses the class name of the object passed in. So, we can either remove XStream from one end or the other, or leave things as they are. There's no point going back to the beta1 way of doing things because that's no less confusing than it is now. I'd go for removing XStream from the Bank code because ObjectToXStream is an OK demo of how to write reusable action processors. The demo isn't really about how to write banking systems using XStream. "kurt.stam(a)jboss.com" wrote : | The BankQuoteRequest should not be the same class. These are independent systems and this will make the demo code confusing I think. +1 Sounds like something to be added to JIRA :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972925#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...