See the following, which I found somewhat useful in sorting this out:
http://www-106.ibm.com/developerworks/webservices/library/ws-docstyle.html
http://java.sun.com/developer/technicalArticles/xml/jaxrpcpatterns/
http://www.devchannel.org/webserviceschannel/03/07/11/210.shtml?tid=25&t
id=38
> Should we stick with Axis 1.1 and rpc/encoded style for a while longer,
> or should we make the jump to Axis 1.2 and doc/literal? Or should we
> make the jump to Axis 1.2 but stick with rpc/encoded style?
I was confused for a time regarding what implementation differences would
exist between
Title: Message
You can build your configurable service locator code however you want,
and use the ServiceLocator method that takes the URL determined from
configuration.
-Original Message-From: Wagle, Shriniwas
[mailto:[EMAIL PROTECTED] Sent: Monday, August 23, 2004 8:52
AM
I am interested in hearing more about WS-Security support in Axis. What is
the future of WSS4J?
I've been asked to modify an existing Axis-based web service client to
access a service where WS-Security is required. I'm trying to get a sense of
what options exist now, and what might exist in the fu
I liked the java web services by O-Reilly.
Not too big, good first reference on WSDL and sun specs. Not a long-term
reference, but it helped a lot when I had to come up to speed on the basics
fast.
Peter
-Original Message-
From: Tania Durán
[mailto:[EMAIL PROTECTED]
Sent:
I suspect a prompt reply on this topic has not come because it's been
discussed so much in the past - a search should reveal lots of good posts on
it. But since I have gotten so much from this community and need to keep my
karma up, I'll summarize what I've collected:
Axis has built in logging. By
Title: RE: need an alternative to Sun's JAX-RPC RI in JWSDP 1.2
I can't comment on #2, but I will
say that in regards to #1, I found Axis much easier to use, configure, and get
help on. I also had a problem with the JWSDP wsdl2java tool. It had a problem
with the WSDL that a customer had g
I must completely agree. I don't think it is intended for use beyond a
reference. We encountered problems with the WSDL generation tool, and were
unable to gain any support or ideas.
Axis is the appropriate alternative. And I have found the support of this
group quite useful.
Peter
-Origina
A customer of ours exposes some web services for app integration. We use
Axis, they use Weblogic. In their WSDL, some fields are required, and some
aren't. For the most part, we've done our homework to make sure that we're
always populating required fields. In at least one case we're not, so when
w
I can't, but I would imagine it would offer much of the same elements of a
distributed component (like a CORBA service) document. Which broadens the
scope of examples.
One suggestion - whether you are just writing a client, or just exposing a
service - you should obtain detailed performance requir
We are embarking on a short project to validate Axis performance within a
particular web service client application. I've seen a few recent posts that
refer to timing data for web service calls. How are folks getting timing
information? Are you using a third-party tool like JProbe? Relying on
homeg
x it by copying Xercesimpl.jar, dom.jar,
and jaxp-api.jar to axis lib directory?
Brian
-Original Message-
From: Pascale, Peter H. [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 13, 2003 11:37 AM
To: '[EMAIL PROTECTED]'
Subject: RE: xerces.jar vs. xercesImpl.jar
Actually, I just f
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 13, 2003 1:40 PM
To: [EMAIL PROTECTED]
Subject: RE: xerces.jar vs. xercesImpl.jar
where did you get xercesImpl?
-Original Message-
From: Pascale, Peter H. [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 13, 2003 1:37 P
: Thursday, March 13, 2003 1:31 PM
To: [EMAIL PROTECTED]
Subject: RE: xerces.jar vs. xercesImpl.jar
I believe that you've probably got two versions of xerces on your
classpath somewhere...
James
-Original Message-
From: Pascale, Peter H. [mailto:[EMAIL PROTECTED]
Sent: Thursday, Mar
I am surprised to find that axis seems to require a specific parser -
xerces, and will not accept xercesImpl. I thought both would be JAXP 1.1
compliant parsers, as the set-up instructions describe:
"In the WEB-INF directory, you'll find a "lib" directory.
In this directory, copy the jars asso
We generate client stubs from WSDL using Axis WSDL2Java. The services we are
currently interacting with have a number of complex types as parameters. So
several javabean classes are generated. We may at some point substitute our
own javabean classes, and try to use the type mapping capability of Ax
I have the following requirement for an Axis client app:
The application must support logging of SOAP messages. Requests messages
must be logged. Logging response messages is a secondary requirement
(desired). Logging must be configurable, so that logging can be initiated
without recompiling.
So,
scale, Peter H." <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 27, 2003 11:01
Subject: configurable endpoints
> As part of developing a WS client with axis for SOAP-RPC calls, I would
like
> the ability to configure the HTTP service location, so that th
As part of developing a WS client with axis for SOAP-RPC calls, I would like
the ability to configure the HTTP service location, so that the client could
look to the external, true implementation of the service, or look to an
internal, dummy implementation (that was built on the same WSDL).
I can
Message-
From: Steve Loughran [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 25, 2003 10:37 AM
To: [EMAIL PROTECTED]
Subject: Re: wsdl and documentation
- Original Message -
From: "Pascale, Peter H." <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, F
This is an interesting thought - it doesn't seem like it would be that hard.
Is anyone doing this, or interested in pairing up on it? I'd be game. How
can you find out if someone else is already working it out?
Peter
-Original Message-
From: James Black [mailto:[EMAIL PROTECTED]
Sent: Tu
21 matches
Mail list logo
