-----Urspr�ngliche Nachricht----- >Von: David Ward [mailto:[EMAIL PROTECTED]] >Gesendet: Dienstag, 11. Juni 2002 15:10 >An: [EMAIL PROTECTED] >Betreff: Re: AW: AW: [JBoss-user] IllegalArgumentException from jboss.net to S LSB
>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. >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. Axis does the graph thing for you. 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 - 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. CGJ ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ _______________________________________________________________ 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
