Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 22460 invoked by uid 500); 19 Sep 2001 20:47:09 -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 22352 invoked from network); 19 Sep 2001 20:47:07 -0000 Message-ID: <3BA90462.29CD8CBE@apache.org> Date: Wed, 19 Sep 2001 16:47:30 -0400 From: Berin Loritsch X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: axis-dev@xml.apache.org Subject: Re: Locating JAX RPC docs References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Russell Butek wrote: > > Unfortunately, JAX-RPC isn't public, yet. It's still under development, > and as such it's only available to those companies/organizations in JSR > 101's expert group. We're trying to get Sun to let this group have access > to it as well, but that hasn't happened, yet. > > Welcome to the bleeding edge. Then, I assume somebody knows the API. Have you guys looked at JAXM at all? The only reason I am mentioning it is because there is a public API and docs available. Also, that approach does some to coincide with what we are persuing in Axis. It defines the javax.xml.soap package with many of the same entities we have for SOAP messages. It is more consistent with the JMS client API standard though. The javax.xml.messaging package defines a JAXMServlet that responds to the SOAP messages over HTTP, and has other provider hooks. It's just a thought. Although I may have to troll through the archives to find your reasoning on RPC vs. messaging.... > > Russell Butek > butek@us.ibm.com > > Berin Loritsch on 09/19/2001 02:54:18 PM > > Please respond to axis-dev@xml.apache.org > > To: Axis Development > cc: > Subject: Locating JAX RPC docs > > During the IRC meeting yesterday, it was noted that Axis is > aiming to comply with JAX-RPC standards for the public API. > The URL I was given pointed me to Java's one page description > of the technology. The only link on the page was to the JCP > entry--which also has very little information. > > Can someone either point me to a full URL where I can peruse > the API docs for JAX-RPC or send it to me via email? > > It's very hard to help the effort if I can't find the standards.