Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 82612 invoked by uid 500); 19 Jun 2002 18:10:15 -0000 Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 82573 invoked from network); 19 Jun 2002 18:10:15 -0000 Message-ID: <8C82D82C4A94B14EB45423741EFFC78D03AF88@msgdal544nts.fmr.com> From: "Day, Andy" To: "'axis-dev@xml.apache.org'" Subject: RE: Client Call Invocation Date: Wed, 19 Jun 2002 14:10:09 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2654.89) Content-Type: multipart/mixed; boundary="------------InterScan_NT_MIME_Boundary" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --------------InterScan_NT_MIME_Boundary Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C217BC.8C3CCAC0" ------_=_NextPart_001_01C217BC.8C3CCAC0 Content-Type: text/plain; charset="iso-8859-1" It looks like the latest version of the JAX-RPC (released June 11th) has taken care of this issue. It provides the following: package javax.xml.rpc; public interface Service { java.rmi.Remote getPort(QName portName, Class serviceEndpointInterface) throws ServiceException; } -Andy -----Original Message----- From: Day, Andy [mailto:Andy.Day@fmr.com] Sent: Wednesday, June 19, 2002 12:35 PM To: 'axis-dev@xml.apache.org' Subject: RE: Client Call Invocation Excellent. Has any request been made to update JAX-RPC with the additional getPort(uri, class) method?? Cheers, Andy -----Original Message----- From: butek@us.ibm.com [mailto:butek@us.ibm.com] Sent: Wednesday, June 19, 2002 12:17 PM To: axis-dev@xml.apache.org Subject: Re: Client Call Invocation You can get a dynamic proxy from the Service object: The JAX-RPC way of doing this is: ISomObject stub = (ISomeObject) service.getPort(ISomeObject.class); // We know "stub" is of type javax.xml.rpc.Stub, so we can do... ((Stub)stub)._setProperty(Stub.ENDPOINT_ADDRESS_PROPERTY, "someUri"); AXIS provides a shortcut technique to do this (NOT part of the JAX-RPC spec): ISomeObject stub = (ISomeObject) service.getPort("someUri", ISomeObject.class); Russell Butek butek@us.ibm.com Please respond to axis-dev@xml.apache.org To: "'axis-dev@xml.apache.org'" cc: Subject: Client Call Invocation Greetings, After perusing the Axis architectural and api documentation, I was disappointed to find no automatic Interface Proxy generation available to the client. For instance if I was given the Interface ISomeObject as follows: public interface ISomeObject { public void someMethod(int someParam); } I would love to be able to do the following on the client-side: ... ISomeObject someObject = (ISomeObject)axisClient.getServiceObject("someUri"); someObject.someMethod(param); ... GLUE provides this level of client access. I had expected Axis to do so also. Did I miss something? Is this already possible? If not, are there any plans to provide this?? Cheers, Andy Andy Day andy.day@fmr.com ------_=_NextPart_001_01C217BC.8C3CCAC0 Content-Type: text/html; charset="iso-8859-1"

It looks like the latest version of the JAX-RPC (released June 11th) has taken care of this issue. It provides the following:

package javax.xml.rpc;

public interface Service {
java.rmi.Remote getPort(QName portName, Class serviceEndpointInterface)
throws ServiceException;
}

-Andy

-----Original Message-----
From: Day, Andy [mailto:Andy.Day@fmr.com]
Sent: Wednesday, June 19, 2002 12:35 PM
To: 'axis-dev@xml.apache.org'
Subject: RE: Client Call Invocation

Excellent. Has any request been made to update JAX-RPC with the additional getPort(uri, class) method??

Cheers,

Andy

-----Original Message-----
From: butek@us.ibm.com [mailto:butek@us.ibm.com]
Sent: Wednesday, June 19, 2002 12:17 PM
To: axis-dev@xml.apache.org
Subject: Re: Client Call Invocation

You can get a dynamic proxy from the Service object: The JAX-RPC way of doing this is:

ISomObject stub = (ISomeObject) service.getPort(ISomeObject.class);

// We know "stub" is of type javax.xml.rpc.Stub, so we can do...
((Stub)stub)._setProperty(Stub.ENDPOINT_ADDRESS_PROPERTY, "someUri");

AXIS provides a shortcut technique to do this (NOT part of the JAX-RPC spec):

ISomeObject stub = (ISomeObject) service.getPort("someUri", ISomeObject.class);

Russell Butek
butek@us.ibm.com

Please respond to axis-dev@xml.apache.org
To: "'axis-dev@xml.apache.org'" <axis-dev@xml.apache.org>
cc:
Subject: Client Call Invocation

Greetings,
After perusing the Axis architectural and api documentation, I was disappointed to find no automatic Interface Proxy generation available to the client. For instance if I was given the Interface ISomeObject as follows:
public interface ISomeObject {
public void someMethod(int someParam); }
I would love to be able to do the following on the client-side:
... ISomeObject someObject = (ISomeObject)axisClient.getServiceObject("someUri"); someObject.someMethod(param); ...
GLUE provides this level of client access. I had expected Axis to do so also. Did I miss something? Is this already possible? If not, are there any plans to provide this??

Cheers, Andy
Andy Day andy.day@fmr.com

------_=_NextPart_001_01C217BC.8C3CCAC0-- --------------InterScan_NT_MIME_Boundary--