Comments inlined, prefixed with: "david>" Jung , Dr. Christoph wrote: > >>Because most site administrators I've dealt with will not allow RMI >>through their firewall. However, they're just about always okay with >>HTTP (since chances are they've already got that going and are familiar >>with it). So if you need to give remote access via HTTP to clients you >>know are java, this works. I know it doesn't work for non-java clients >>but it does solve a very common problem. > > > That is a necessary, but not sufficient reason to jump on SOAP. You could > use > a jrmp-http-tunnel alternatively. It becomes sufficient when you state that > you like to > avoid persistent http sessions in order to minimize vulnerability of the > connections.
david> jrmp-http-tunnel? Sounds very cool. Can you point out a starting place for me to learn about and play with this? >>Now, I would love to use something that can handle complex object graphs >>that contain custom objets that further do not adhere completely to the >>JavaBeans spec - but I haven't found anything. Point me at a >>Serializer/Deserializer combo that does this (and that will work with >>both Java and M$ clients), and I'll jump all over it. > > > But this is the idea of having serializer/deserializer factory. You will not > be able to > write a single piece of code (or rather: two classes!) that will bridge all > of your runtime > environments and if there would be, I�m surely not the one to maintain it. > > Instead have special-purpose serializers for special-purpose classes/schemas > and plug them > together to provide complexity. david> That makes sense. > Axis does the graph thing for you. david> Sure, if I use typed arrays or Vectors (as you mentioned earlier). Why it can't handle any kind of Collection I'm not sure. If they can do a Vector, why can't they do an (Arary)List? Maybe just not implemented yet on their end. Still, this lacking stopped me from doing what I wanted to do with it. > Axis also provides a lot of features when > it comes to present > the resulting meta-data in wsdl. The beanserializer does some stuff good, > others bad - david> Yeah; it probably wasn't trivial to write. It's unfortunate though that it is so strict about gets() without sets(). > I�m currently > Subclassing it to get it running smoothly with entity beans. > But the BeanSerializer is not everything and for all purposes. E.g., I�m > also investigating > special-purpose serializers that let java objects look like Ado DataSets. If > it was, we would be back > at the good old java.io.ObjectxxxStream and that is like I perceive the > java.beans.XML stuff, too. > > If there is enough interest in using Jboss.net just for tunneling purposes, > you can surely add > the almighty Object->xsd:binary xsd:binary->Object pair to the codebase. But > that is not quite > how I perceive Web Services to be fruitful. > david> I'm seeing the light... Thanks again for your help, and especially for all the great work you did on JBoss.net. _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
