First, read this if you haven't:
http://www.javaworld.com/javaworld/jw-10-2003/jw-1003-wsstyles.html
Bottom line is that you can't do doc/literal with Axis 1.1. We're currently
using Axis 1.2 alpha builds to publish doc/literal Web services. It goes
something a little like this:
Build XML
In most of our experiments all of the doc/lit WSDL emitted by Axis 1.2a's
java2WSDL tool was either invalid or not WS-I compliant.
I define invalid to mean not immediately usable for a client to bind to
and successfully invoke the service.
I define not WS-I compliant to mean failing Mindreef
A really great WS-I WSDL/XSD testing tool is Mindreef SOAPScope
(www.mindreef.com). We successfully used their 2.0 release to ensure that
our doc/lit WSDL/XSD was WS-I compliant before running Axis 1.2 alpha
wsdl2java against it. Their current release, 3.0, touts further WS-I
testing
Hey gang,
Time for my two cents. We've been using Axis 1.2 alpha builds since
November '03 to build WS-I compliant document literal web services. How is
this possible? Here's our cookbook:
1) Create XML schema in Altova XMLSpy that defines the datatypes that the
web service is to
No easy answer, as it all depends on the deployment environment that you
need to support.
Who is consuming the service? Is it a portal? Do you own the portal server
that is consuming it? What about the service itself? Do you own the whole
server? Where are they located? Are they both on a
Jim, Nelson, all,
So, now that we all agree that SOAP is just a framing protocol and
processing model, and XML Schema is that de-facto type system for defining
interoperable data types...
The $50,000 Question:
What problems can we solve with SOAP based Web Services?
A colleague of mine has
Dennis Sosnoski wrote:
As I've said before, I think it's unfortunate that JAX-RPC/Axis is
coming from such a strong rpc/enc orientation. I think an API for
doc/lit services can be *much* simpler than the current mess of stubs,
ties, wire, duct tape, chewing gum, etc.
Is this not where everyone
.
Maybe we'll see an XML Schema Lite in the future?
-Jon
-Original Message-
From: Dennis Sosnoski [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 16, 2004 5:29 PM
To: [EMAIL PROTECTED]
Subject: Re: Doc/Literal support in axis
Anderson Jonathan wrote:
...
The $5000 Question
Awesome. I was aware of TREX, but not of RELAX or RELAX NG. I'd honestly
forgotten there were alternatives to W3C XML Schema, which is most likely an
unfortunate side effect of having my head down in the SOAP bubbles for too
long.
So the question really, as you pointed out, is toolkit support.
The only problem with decoupling the SOAP processing layer from the Java
data binding layer is the implications such an approach has on intermediary
node processing. Almost every SOAP stack I've seen implements SOAP
intermediary nodes as some sort of interceptor (Axis handlers, JAX-RPC
handlers,
Jim Murphy wrote:
I don't get why this is a problem. Say I have a handler that wants to
transform a request in some way (decrypt, remove a Header whatever).
Isn't that just consuming one stream and producing another? If it wants
to consume one stream map that to Java using some
, March 18, 2004 3:33 PM
To: Anderson Jonathan
Cc: [EMAIL PROTECTED]
Subject: RE: Doc/Literal support in axis
I was looking again at your excellent cookbook for doing doc/literal
in Axis and had a couple of followup practical questions:
You specify using Axis 1.2 alpha. Is there any hope with Axis
I second that suggestion. :)
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Friday, March 19, 2004 2:08 PM
To: [EMAIL PROTECTED]
Subject: RE: Doc/Literal support in axis
When starting with WSDL, what that really menas if that you should be
starting with a
I heard grumblings awhile ago that Microsoft might be dropping support for
DIME in lieu of some WS-I discussions concerning attachments. Might wanna
try googling around for more information, but this probably won't occur
until the next .Net/Vis Studio release anyway.
-Jon
-Original
Anne,
Any idea if and/or when JAX-RPC will standardize this? So far it seems
like an Axis specific thing - has anyone seen it elsewhere? (Glue?
CapeClear?)
Would it not make sense to give the developer the choice of either using the
XML - Java data binding facilities that a particular
Anne, Monika -
Check out Rich Turner's blog entry:
http://blogs.msdn.com/richturner666/archive/2004/03/10/87602.aspx
Thankfully, the Microsoft guys involved with Indigo blog pretty regularly.
Makes it easier to read the tea leaves. :)
Regards,
Jonathan Anderson
Booz Allen Hamilton
1. What are the benefits of using Axis generated classes as against
using standard like JAXB?
More robust XML Schema support is my guess - but I'm fuzzy on which Java -
XML data binding engines support what.
2. Will JAXB generation be included as part of the next version of
JAX-RPC spec?
Not
Henrik,
Axis 1.2 beta is out...
http://archive.apache.org/dist/ws/axis/1_2beta/
Though if you're the adventurous type you can always pull straight from CVS
and build it yourself.
And yes, we're ALL struggling not only with building WS-I compliant SOAP
services, but WS-I complaint SOAP services
David, you may be understating the problem a bit. Building interoperable,
WS-I compliant SOAP services with Axis is a little involved.
See:
http://marc.theaimsgroup.com/?l=axis-userm=107945370506044w=2
Regards,
Jonathan Anderson
Booz Allen Hamilton
-Original Message-
From: David
Between you, me, and Axis User :) - amidst my searching to grasp the SOAP
based SOA big picture, I'm starting to feel as if SOAP support is just being
bolted onto the J2EE stack. JAX-RPC, SAAJ, JAXM, JAXR, yadda, yadda. The
fact that it's hard to quantify exactly what Axis is (saying that it is
file for document/literal) I would really appreciate it.
thanks - dave
ps - The people who created axis have done an extraordinary job both with
the product, the documentation, and the samples.
-- Original Message --
From: Anderson Jonathan [EMAIL PROTECTED
Paul,
Sounds like you might be hung up on W3C XML schema. Why not just do
something like this?
complexType name=BooksType
sequence minOccurs=1 maxOccurs=unbounded
element name=Book type=string/
/sequence
/complexType
element name=Books type=tns:BooksType/
That way, you could have XML
There are a number of doc/lit showstopper bugs in Axis 1.1 - the ones I
encountered were in the WSDL2Java emitter, I believe.
Check out JIRA, the Apache bug tracking tool. Go here:
http://nagoya.apache.org/jira/secure/Dashboard.jspa
Then click on Axis, then click on Find Issues. In the Text
You are touching on an interesting and deep running debate, my friend.
In order to build a SOAP service, should you be modeling the data types that
you wish to exchange (the message payloads) in your native object oriented
programming language (Java, C#, etc) or in your XML schema? Modeling the
Anne Thomas Manes wrote to axis-user:
JAX-RPC 1.1 defined standard mappings between Java types and RPC/Encoded,
but it doesn't do the same for Doc/Literal (even though Sun claims it
does).
It could be done as part of JAXB 2.0 or JAX-RPC 2.0, but I'm not convinced
that it belongs in either one.
Greetings everyone,
I want to get a reality check before entering a JIRA bug report. Thanks go
out to the SOAPtest guys over at Parasoft for helping me realize this
problem - it was quite subtle. In the following WSDL, I do the following:
BankService-DocLiteral.wsdl, target namespace:
I would venture to say that 80% of the complications and frustrations
implementing interoperable (WS-I compliant Doc/Literal) SOAP web services on
Java platforms stem from the XML datatype to Java datatype binding problem.
If you take the time to learn W3C XML Schema, you'll see the problem: it's
not tying my service layer to my DAO layer. My reasons
are more personal preferrance then need. But, I can take my DAO and
put it behind something else with little changing except creating a
new broker.
-Joe
- Original Message -
From: Anderson Jonathan [EMAIL PROTECTED]
To: [EMAIL
. But, I can take my DAO and put it
behind something else with little changing except creating a new broker.
-Joe
- Original Message -
From: Anderson Jonathan [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, May 12, 2004 10:03 AM
Subject: RE: Best Practices?
I would
Java2WSDL implies that you are modeling the documents being exchanged by
your document/literal SOAP web service as Java objects, or in other words
Java types.
Given that W3C XML Schema is not an object oriented type system, you are
then required to trust your Java2WSDL GUI (BEA Weblogic Workshop,
Try Mindreef SOAPScope 3.0. It runs as a web app on your local machine, and
you can either upload a WSDL to it or point it at a ?WSDL endpoint. It
consumes the WSDL and constructs an HTML form page that allows you to
populate the SOAP request. Click invoke, see the response. Very handy -
can
We're running Axis in Weblogic 8.1 SP2 with only the following modification
to the startManagedWeblogic.cmd startup script:
set
JAVA_OPTIONS=-Djavax.xml.soap.SOAPFactory=org.apache.axis.soap.SOAPFactoryIm
pl
But this has nothing to do with JAXP XML parsers (Xerces) or JAXP XML
processors (Xalan)
Ever looked into Axis MSG style calls? This is client code, but you can do
the same thing on the server side as well, assuming you've built a MSG style
service. Check out the Axis docs for more information.
Service service = new Service();
Call call = (Call) service.createCall();
I
think of it this way:
Axis
is essentially a servlet, and you deploy it in a WAR via the WEB-INF/web.xml
deployment descriptor.
Well,
how do you tell Axis what services to deploy?
The
Axis WEB-INF/server-config.wsdd deployment descriptor tells Axis what classes to
deploy as services
My team has been building WS-I compliant doc/lit services and clients for
months now using Axis 1.2 alphas, beta 1, and beta 2.
We just build our services from the XSD+WSDL in (WSDL2Java), instead of from
the Java code out (Java2WSDL). Very important to understand the
implications of either
You are going to need to get in touch with the owners of that Web Service so
that you can determine *exactly* what it is expecting.
A) Exactly what type of XML Signature does it expect? OASIS WS-Security
2004? Microsoft WS-Security 2002? An enveloped signature inside the SOAP
envelope (which
No binaries exist. Checkout from CVS and
build.
-Jon
From: Ry. [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 16, 2005 2:07 PMTo:
[EMAIL PROTECTED]Subject: Where are WSS4J
Binaries?
Hi, I am looking forward to using WSS4J in my project but I don't
knowwhere to find the binaries
37 matches
Mail list logo
