|
By
using XML as argument passing mechanism, you're adding one more layer of
complexity that is going to have impact on the performance among other things.
The problem is that XML parsing is expensive operation and in this scenario
doesn't buy you much. Maintaining session beans APIs is by far easier than
maintaining your XML structure and parsing classes even if you use JAXB.
Marshalling/unmarshalling of arguments is already done for you by ejb mechanisms
and it works fine, why mess with it?
Why is
binary compatibility important? Not having to change the signature (interfaces)
of your session beans can be achieved in other ways if that's really important
to you. Pass Collection or Map as an argument (I'm not suggesting you do this
thou).
Nedim.
Got a question about Java and XML:
Let's say you are interacting
with some sort of Session bean and the method you are going to access is going
to return a collection. It seems to me that you could do this just as easily
by returning an XML string to the client. The problem that I am having is that
I can't find anyone who supports this idea, via examples or in technical
articles, so it makes me wonder if I am wrong but I just don't know it yet
:P
As well, I spoke to a VB
developer friend of mine and they use XML to pass a method parameters. He said
this was extremely useful because if he wants to add a parameter to a public
method that he does not have to break his binary compatibility. Once again,
this sounds great for Java but I have not been able to find any examples in
how-to's or technical articles.
I'm interested in hearing
some feedback on the up's and down's of using XML to send parameters and
return collections or lists. As well as, where I might find some examples of
how someone else has implemented it.
Thank you,
|