Re: Clients, Authorization, and more Fun!

[NYY96]

This doesn't work for two reasons. The first reason is that for the code you referenced:   com.blah.ExampleService s = new com.blah.ExampleServiceLocator(); com.blah.Example e = s.getexample(); ((javax.xml.rpc.Stub)e)._setProperty(javax.xml.rpc.Call.USERNAME_PROPERTY, "username");   the client will need to reference the web service libraries, which is not a desirable thing for clients to have access to the code.   Secondly, many of the libraries referenced here do not exist. For example, the Service type simply does not have a method getExample.   Any ideas?   James   In a message dated 7/29/2004 11:55:23 AM Eastern Standard Time, [EMAIL PROTECTED] writes: you can typecast the thing returned from the locator to javax.xml.rpc.Stub (http://java.sun.com/j2ee/1.4/docs/api/javax/xml/rpc/Stub.html) and use the _setProperty with USERNAME_PROPERTY and PASSWORD_PROPERTY to set the userid and password. See http://marc.theaimsgroup.com/?l=axis-dev&m=106561261721783&w=2 for an example -- dims ----- Original Message ----- From: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Thu, 29 Jul 2004 11:24:16 EDT Subject: Re: Clients, Authorization, and more Fun! To: [EMAIL PROTECTED] Not for the clients but most of the dirty work files are from WSDL2Java..   In a message dated 7/29/2004 11:23:38 AM Eastern Standard Time, [EMAIL PROTECTED] writes: Are u using stubs generated by WSDL2Java? ----- Original Message ----- From: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Thu, 29 Jul 2004 11:17:36 EDT Subject: Re: Clients, Authorization, and more Fun! To: [EMAIL PROTECTED] No I don't think it's a bug. All that I'm saying is that if I use the created Handler class and call it that way, I get a nice output of the envelopes to the screen and the return type is equal to the return type of the axis function. If I use the Call type than I don't get these things. I believe I need to use the Call type to get the authentication done. I was wondering if I could merge the benefits of both.   In a message dated 7/29/2004 11:16:13 AM Eastern Standard Time, [EMAIL PROTECTED] writes: If there's a bug, we can fix it in 1.2 that's why i am asking. thanks, dims ----- Original Message ----- From: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Thu, 29 Jul 2004 11:08:21 EDT Subject: Re: Clients, Authorization, and more Fun! To: [EMAIL PROTECTED] I have to go to production with this product eventually. Axis 1.1 is all I am using currently.   In a message dated 7/29/2004 11:06:11 AM Eastern Standard Time, [EMAIL PROTECTED] writes: Are u using Axis 1.2 Beta 2? ----- Original Message ----- From: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Thu, 29 Jul 2004 10:59:23 EDT Subject: Re: Clients, Authorization, and more Fun! To: [EMAIL PROTECTED] In short I was wondering if I can merge both of the methods below to have a handler easily call the funciton but also by implementing HTTP Authentication   In a message dated 7/29/2004 10:57:57 AM Eastern Standard Time, [EMAIL PROTECTED] writes: Hello Everyone,   Previously I was calling my Axis Service very effectively using a handler and using the following call:   boolean success = handler.postReport(groupName, password, accountName, Data);   Now I am moving forward with the service and want to add HTTP Authentication. I have read up on this and I realize I can do it the following way by using the Call type:                Call call = (Call) s.createCall();                 call.setTargetEndpointAddress( new java.net.URL(endpoint) );                 call.setOperationName(new QName("post"));          call.setUsername(groupName);                 call.setPassword(password);          Object success = call.invoke(new Object[] {groupName, password, "Polio", Data});   Previously the Handler was wonderful for outputting errors, showing the SOAP Envelopes, and for clarity purposes. When I use call.invoke, I don't get such a luxury. In fact, the return value becomes object instead of Boolean, so I am not even getting the true value of the call returned.   Is there any way I can incorporate the simple calling of the service with the handler              List handlerChain = s.getHandlerRegistry().getHandlerChain(portName);            HandlerInfo hi = new HandlerInfo(LoggingHandler.class,null,null);            handlerChain.add(hi);   AdminHandler handler = (AdminHandler) s.getPort(portName, AdminHandler.class);   and HTTP Authentication without losing the vlaue I get by the handler when using Call?   THanks for your help everyone! James Crosson   -- Davanum Srinivas - http://webservices.apache.org/~dims/   -- Davanum Srinivas - http://webservices.apache.org/~dims/   -- Davanum Srinivas - http://webservices.apache.org/~dims/   -- Davanum Srinivas - http://webservices.apache.org/~dims/