Well, now this is getting a little o/t, but suffice to say that although I'm not using Websphere at this time, I am using another non-Axis Web service provider. And up until now have been using a generated WSDL to invoke a Web Service. Now I do not know the precise details of how Websphere exposes a Web Service interface, but I am assuming it will involve a WSDL somewhere. In which case I can use the code I'm developing right now.
> -----Original Message----- > From: Martin Gainty [mailto:[EMAIL PROTECTED] > Sent: 24 August 2006 13:14 > To: [email protected] > Subject: Re: Using Axis/WSS4J without deployment descriptor file > > start at > How to write a Service Domain application and deplot it over a Web > Application server > http://www-128.ibm.com/developerworks/library/gr-servicegrid4/ > > Notice the statement that says > "To deploy in this environment, we first create WSDD" > > My question to you is Are the IBM Websphere engineers wrong? > > Good Luck, > M- > ********************************************************************* > This email message and any files transmitted with it contain confidential > information intended only for the person(s) to whom this email message is > addressed. If you have received this email message in error, please > notify > the sender immediately by telephone or email and destroy the original > message without making a copy. Thank you. > > > > ----- Original Message ----- > From: "Andrew Fielden" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Thursday, August 24, 2006 6:46 AM > Subject: RE: Using Axis/WSS4J without deployment descriptor file > > > Thanks for that code fragment Robert. My handler is now being invoked, > and to clarify, a client-side WSDD file is not required. My client > registers the handler in the following way > > List list = service.getHandlerRegistry().getHandlerChain(portQN); > list.add(new > javax.xml.rpc.handler.HandlerInfo(WSSCallbackHandler.class,null,null)); > > > My WSSCallbackHandler class is declared as follows: > > public class WSSCallbackHandler extends GenericHandler > { > ... > } > > > > > > -----Original Message----- > > From: robert lazarski [mailto:[EMAIL PROTECTED] > > Sent: 23 August 2006 20:42 > > To: [email protected] > > Subject: Re: Using Axis/WSS4J without deployment descriptor file > > > > Digging out my old axis 1.x code , you could also do... > > > > QName svcQName = new QName(endpoint, nameSpaceUri); > > ServiceFactory sf = ServiceFactory.newInstance(); > > Service svc = sf.createService(svcQName); > > QName portQN = new QName(endpoint, pq); > > //add ClientHandler to chain of events > > java.util.List list = > > svc.getHandlerRegistry().getHandlerChain(portQN); > > list.add(new > > > javax.xml.rpc.handler.HandlerInfo(ClientHandler.class,this.handlerConfig > ,n > > ull)); > > > > Call call = (Call) svc.createCall(portQN); > > > > HTH, > > Robert > > http://www.braziloutsource.com/ > > > > On 8/23/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > > > You need to define a client-side WSDD file. > > > > > > On 8/23/06, Andrew Fielden <[EMAIL PROTECTED]> wrote: > > > > Let's suppose I have a Web Service which is provided by WebSphere. > > > > I'm using Axis in my client to invoke this Web Service. > > > > I have no deployment descriptor file, the Web Service is being > invoked > > > > via a WSDL, specifying a target service and port. > > > > > > > > Looking at the WSS4J examples, they are all based on modifying an > > > > existing .wsdd file to specify handler classes. > > > > > > > > In my case I do not have a .wsdd file > > > > > > > > How then, do I configure Axis to invoke my handler class? > > > > > > > > I wish to add username, SAML or X509 security tokens to ALL > outgoing > > > > SOAP messages, not just for one specific Web Service. > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
