Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
From: "Anne Thomas Manes" <anne@manes.net>
To: <axis-user@ws.apache.org>
Subject: RE: File upload example
Date: Wed, 14 May 2003 12:34:41 -0400
Message-ID: <ECEDLFLFGIEENIPIEJJPGEPEEDAA.anne@manes.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Importance: Normal
In-Reply-To: 
 <61C1CA24B8657047893FCF3570BC757D017D90A8@daebe008.americas.nokia.com>

Just to clarify:

1- The JAX-RPC API is not a "required package" within J2SE. It is an
"optional package" in J2SE.
IF the JCP decides that it wants to include intergrated, required support
for SOAP in J2SE, they will need to develop a client-only JAX-RPC API
(comparable to Java IDL) -- and that's what would be included in J2SE. Sun's
JAX-RPC reference implementation (RI) isn't appropriate to be included with
J2SE. The JAX-RPC RI *requires* Tomcat, which is not part of J2SE. Sun's
JWSDP is a separate add-on product that runs on J2SE.

2- The JAX-RPC API will be a "required package" in J2EE, but that doesn't
require or even encourage you to use Sun's JAX-RPC RI. The API and the RI
are different things. In order to get certified as a J2EE 1.4 compliant
application server, a J2EE vendor will need to add support for (i.e.
implement) the JAX-RPC, SAAJ, JAXR, and WSEE APIs. Sun will include the
JAX-RPC RI in the J2EE 1.4 RI and also in Sun ONE Application Server. But I
can guarantee that WebLogic, WebSphere, JRun, Borland ES, IONA ASP, JBoss,
OrionServer, Sybase EAServer, and all the other third party J2EE servers
will *NOT* include Sun's JAX-RPC RI. These products will include other
JAX-RPC implementations. And, oh by the way, WebSphere, JRun, Borland ES,
JBoss, EAServer, and propbably OrionServer will all use Axis.

There is absolutely no reason to switch from Axis to Sun's JAX-RPC RI. I'm
sure you can make an argument to your management to make them see clearly.
Axis will be much more pervasive than Sun's JAX-RPC RI.

Best regards,
Anne

> -----Original Message-----
> From: Bruno.Melloni@nokia.com [mailto:Bruno.Melloni@nokia.com]
> Sent: Wednesday, May 14, 2003 10:44 AM
> To: axis-user@ws.apache.org
> Subject: RE: File upload example
>
>
> Thank you for the note on sticking to the formal spec.
>
> I like Axis much better than Sun's JAX-RPC included with J2SE 1.4
> and soon J2EE 1.4(aside from the fact that Sun's JAX-RPC
> documentation is absolutely pityful), but I am pragmatic enough
> to know that the time will come when I will "have to" switch to
> the standard Sun implementation.  (Yes, I am aware that Axis also
> fully implements the JAX-RPC standard, but you know managers and
> other paper-pushers...)
>
> Bruno
>
> -----Original Message-----
> From: ext Praveen Peddi [mailto:ppeddi@contextmedia.com]
> Sent: Tuesday, May 13, 2003 2:12 PM
> To: axis-user@ws.apache.org
> Subject: Re: File upload example
>
>
> Doesn't option 2 tie you to axis. What if u want to change from axis to
> something else in the future. In that case you will have to
> re-write ur soap
> service completely.
>
> I think its better to keep your soap services transparent of tool apis. If
> you adopt the first option and since DataHandler is part of activation api
> (not axis api), you won't have to change your code at all even if u change
> from axis to something else.
>
> Praveen
> ----- Original Message -----
> From: "Duane Gran" <dgran@spinweb.net>
> To: <axis-user@ws.apache.org>
> Sent: Tuesday, May 13, 2003 1:22 PM
> Subject: Re: File upload example
>
>
> > Bruno,
> >
> > I cut my teeth on this one recently, so I'll be happy to share what I
> > have.  From what I've seen, there are two typical ways of doing this
> > from the client side:
> >
> > 1) Encode the attachment as a DataHandler, serialize it and send it as
> > a parameter
> > 2) Like above, encode as a DataHandler and put into an attachment (dime
> > or mime)
> >
> > My code supports both ways, but at the moment I prefer #2.  Someone
> > else may be able to shed more light, but it seems to have more promise
> > for interoperability, but at this time my environment is Java-only, so
> > that is just conjecture on my part.
> >
> > My application deals specifically with converting a binary file (MARC)
> > into an XML format (MARCXML), so don't get hung up on the extraneous
> > details.  In MarcXmlMapper the key parts to look at are the two convert
> > methods and getAttachments.  The TextMarcXmlMapper is a JUnit test that
> > loosely ensures that the connection was accepted and some manner of
> > String data came back.  The test is pretty weak right now, but it will
> > do.  I am including my wsdd file if that may be helpful.
> >
> > Feel free to email me if you have any questions.
> >
> > Duane
> >
> >
> >
>
>
> ------------------------------------------------------------------
> ----------
> ----
>
>
> >
> >
> >
> > On Tuesday, May 13, 2003, at 12:13  PM, <Bruno.Melloni@nokia.com> wrote:
> >
> > > Hello,
> > >
> > > Does anyone have a sample of a web service and client call for doing a
> > > file upload using Axis?
> > >
> > > I have found samples for the old Apache Soap, but it seems that things
> > > are usually simpler when done with Axis.
> > >
> > > Thanks,
> > >
> > > Bruno
> >
>