How important is that? New to all this, so my concern is just being able to send secure/encrypted web service calls from our clients to our server and back again. I don't know that it is imperative that I stick to this JAXRPC stuff or not. Is it? I mean, we plan to integrate with other services down the road, so is it imperative to stick by JAXRPC?
By the way, is JAX-RPC THE standard now? I remember dabbling with web services a few years back with apache soap was the only implementation open-sourced at the time, and I think GLUE was catching on then too for a price. Is it dramatically different now? What I would prefer to do is "control" the actual building of the calls, if manually coded that is fine. I am a little afraid of all this schema/dtd/wsdl/jws stuff. I suppose a good book that is new may explain this... the books I have seen are about 2 years old, so anyone recommend a good NEW published book that is up to date? In a nutshell I am building the architecture behind a sort of messaging system that will need to allow a swing desktop client, and down the road pda and cell phones, access to our server. I have been guessing that web services is the way to go for this even though apparently web services is barely catching on in the business world (I could be wrong... just going by some articles I've read). I need to transmit and get back data securely with at least 128-bit if not better. Authentication is another issue, we were thinking of an encrypted MD5 hash or something to maximize security. Lastly, we will eventually grow to millions of page views an hour (I know.. it sounds like wishful thinking but we are confident it will turn out this way and more so, want to plan for the future now). Because of this, I want to make sure I am setting up the right hardware/software combo. We were thinking a scalable front end with 2 or 3 servers per cluster group (island) so that we can easily add another group if the performance degrades due to traffic. We were also thinking of a cache layer between the servers and the DB since we are mostly polling data from the database, very little transactions going on. So, is Tomcat 5.5+, Spring/Hibernate able to handle this? We are thinking dual or quad opteron servers with 16GB of memory on the web tier, and probably some caching servers with 32GB of memory in between to cache as much as possible to eliminate any bottlenecks with the database. This is a bit off topic now, but to get back on topic, is axis (or xfire) capable of such high performance? Or is there some other magic I am missing in the hardware setup, such as ssl hardware or something along that lines? Thanks all. I appreciate all the help. --- Alick Buckley <[EMAIL PROTECTED]> wrote: > > Hi Andy, > > I hope this helps. > > I needed to trace the SOAP request / response > payload to a file, so I added > a handler. > > The handler is called twice, once for the oubound > request and again for the > response. > > I extended the HandlerInfo class so I could pass > extra information. > > http://java.sun.com/j2ee/1.4/docs/api/javax/xml/soap/SOAPMessage.html > > > I noticed that the SOAP request is missing the XML > declaration. > > This missing XML declaration was noticed by another > axis user. > > XML declaration no longer exists in Envelope > > http://marc.theaimsgroup.com/?l=axis-user&m=110739322015013&w=2 > > ============================================================================ > ============== > > QName portName = stub.getPortName () ; > > Service service = stub._getService () ; // Axis > 1.2 RC2 > > HandlerRegistry handlerRegistry = > service.getHandlerRegistry () ; > > List handlerChain = > handlerRegistry.getHandlerChain ( portName ) ; > > MyHandlerInfo handlerInfo = new > MyMessageHandlerInfo () ; > > handlerInfo.setHandlerClass ( > com.lansa.jsm.service.SOAPAgentMessageHandler.class > ) ; > > handlerChain.add ( handlerInfo ) ; > > handlerRegistry.setHandlerChain ( portName, > handlerChain ) ; > > ============================================================================ > ============== > > public class MyHandlerInfo extends HandlerInfo > { > > } > > ============================================================================ > ============== > > public class MyHandler implements Handler > { > public void init ( HandlerInfo handlerInfo ) > throws JAXRPCException > { > if ( handlerInfo instanceof MyHandlerInfo ) > { > > } > } > > public void destroy () throws JAXRPCException > { > } > > public QName[] getHeaders () > { > return new QName[0] ; > } > > public boolean handleFault ( MessageContext > messageContext ) throws > JAXRPCException > { > return true ; // return true to continue > processing > } > > public boolean handleRequest ( MessageContext > messageContext ) throws > JAXRPCException > { > SOAPMessage message = > ((SOAPMessageContext)messageContext).getMessage () ; > > // message.writeTo ( outputStream ) ; > > return true ; // return true to continue > processing > } > > public boolean handleResponse ( MessageContext > messageContext ) throws > JAXRPCException > { > return true ; // return true to continue > processing > } > > ============================================================================ > ============== > > > > -----Original Message----- > From: Andy Dolbey [mailto:[EMAIL PROTECTED] > Sent: Saturday, 26 February 2005 2:49 PM > To: [email protected] > Subject: client-side access to request SOAP message, > before submission > > > Does Axis offer any way for a client class to > examine and perhaps > modify a SOAP request message immediately before the > message is sent > across the wire? If so, this might offer me a > chance to mend some > tricky interop problem cases I've been having with > complex data types. > > If anyone knows about this, and/or has had > experiences with it, please > let me know. > > Thanks! > > Andy > __________________________________ Do you Yahoo!? Yahoo! Mail - Helps protect you from nasty viruses. http://promotions.yahoo.com/new_mail
