]
Subject: RE: Need suggestions on web service interop and design
David, you may be understating the problem a bit. Building interoperable,
WS-I compliant SOAP services with Axis is a little involved.
Yeah, a little too involved. Shouldn't this be easier? No specific
criticism of Axis intended
not convinced
that it belongs in either one. Anyone on this list care to initiate a JSR?
Anne
-Original Message-
From: Nelson Minar [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 14, 2004 7:47 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: Need suggestions on web service interop
not convinced
that it belongs in either one. Anyone on this list care to initiate a JSR?
Anne
-Original Message-
From: Nelson Minar [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 14, 2004 7:47 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: Need suggestions on web service interop
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.
all Java SOAP platforms? (was RE: Need suggestions on web service
interop and design)
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
all Java SOAP platforms? (was RE: Need suggestions on web service
interop and design)
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
: RE: What is needed from the JCP to ensure SOAP service portability
across all Java SOAP platforms? (was RE: Need suggestions on web service
interop and design)
Supposedly... according to the latest revision of the JCP bylaws ... future
JCP proceedings will be more transparent to developers.
See
Henrik,
The WS-I Basic Profile disallows the use of SOAP Encoding. It allows only
Document/Literal and RPC/Literal. Technically, WS-I BP doesn't *require*
support for RPC/Literal, though. Microsoft fought long and hard to exclude
RPC-style from the WS-I BP, but they lost that vote. In any case,
Henrik,
The WS-I Basic Profile disallows the use of SOAP Encoding. It allows only
Document/Literal and RPC/Literal. Technically, WS-I BP doesn't *require*
support for RPC/Literal, though. Microsoft fought long and hard to exclude
RPC-style from the WS-I BP, but they lost that vote. In any case,
is alpha...Anyone knows of the beta or final release
plans..?
Best regards
Henrik
- Original Message -
From: Anne Thomas Manes [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, April 14, 2004 3:38 PM
Subject: RE: Need suggestions on web service interop and design
Henrik,
The WS
HG writes:
I can see that Axis 1.2 is alpha...Anyone knows of the beta or final
release plans..?
There is a beta, but for some inexplicable reason it's not visible on
the site. You can find it here:
http://archive.apache.org/dist/ws/axis/1_2beta/
I'm having good luck with it.
Anne Thomas Manes
Speaking for myself (and I think lots of others), while a tutorial would be wonderful,
if you could just tell us what method to use to create a server using java under
access that .net can access - that's 90% of what we need.
Especially if one of the existing axis examples implementes that
Thielen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 14, 2004 12:18 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Need suggestions on web service interop and design
Speaking for myself (and I think lots of others), while a tutorial would be
wonderful, if you could just tell us what
David, you may be understating the problem a bit. Building interoperable,
WS-I compliant SOAP services with Axis is a little involved.
Yeah, a little too involved. Shouldn't this be easier? No specific
criticism of Axis intended. I'm just amazed at how much effort I'm
going through to pass
Nelson Minar wrote:
Yeah, a little too involved. Shouldn't this be easier? No specific
criticism of Axis intended. I'm just amazed at how much effort I'm
going through to pass arrays of numbers around.
Just create an array of ints and pass that, and no problem.
The client or server will
]; [EMAIL PROTECTED]
Subject: Re: Need suggestions on web service interop and design
Speaking for myself (and I think lots of others), while a tutorial would be
wonderful, if you could just tell us what method to use to create a server
using java under access that .net can access - that's 90% of what
PROTECTED]
Subject: RE: Need suggestions on web service interop and design
David, you may be understating the problem a bit. Building interoperable,
WS-I compliant SOAP services with Axis is a little involved.
Yeah, a little too involved. Shouldn't this be easier? No specific
criticism of Axis
-
From: David Thielen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 14, 2004 3:22 PM
To: [EMAIL PROTECTED]
Subject: RE: Need suggestions on web service interop and design
Your link is really helpful - and where I was thinking we were heading.
That said, any place that can help a newbie through
-
From: Nelson Minar [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 14, 2004 1:30 PM
To: [EMAIL PROTECTED]
Subject: RE: Need suggestions on web service interop and design
David, you may be understating the problem a bit. Building interoperable,
WS-I compliant SOAP services with Axis
-DocLiteral.wsdl/
/target
Regards,
Jonathan Anderson
Booz Allen Hamilton
-Original Message-
From: David Thielen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 14, 2004 3:22 PM
To: [EMAIL PROTECTED]
Subject: RE: Need suggestions on web service interop and design
Your link is really
PROTECTED]
Subject: RE: Need suggestions on web service interop and design
Jonathan,
Good effort! While I was able to create simple doc/literal service which
works
with .NET (in this case InfoPath), the stumbling block is having arrays of
simple types as return types. If you could extend your example
on web service interop and design
David, you may be understating the problem a bit. Building interoperable,
WS-I compliant SOAP services with Axis is a little involved.
Yeah, a little too involved. Shouldn't this be easier? No specific
criticism of Axis intended. I'm just amazed at how much effort
]
Subject: RE: Need suggestions on web service interop and design
It can be eaiser. Download the Systinet developer tools for eclipse.
Given the .java file it generated a doc/literal wsdl.
Ross
-Original Message-
From: Nelson Minar [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 14, 2004
Anderson
Booz Allen Hamilton
-Original Message-
From: Yakulis, Ross (Ross) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 14, 2004 5:35 PM
To: [EMAIL PROTECTED]
Subject: RE: Need suggestions on web service interop and design
Note, that while Axis cannot currently generate this wsdl file
Manes [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, April 14, 2004 3:38 PM
Subject: RE: Need suggestions on web service interop and design
Henrik,
The WS-I Basic Profile disallows the use of SOAP Encoding. It allows
only
Document/Literal and RPC/Literal. Technically, WS-I BP doesn't
: Anderson Jonathan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 14, 2004 3:02 PM
To: [EMAIL PROTECTED]
Subject: RE: Need suggestions on web service interop and design
You are touching on an interesting and deep running debate, my friend.
In order to build a SOAP service, should you be modeling
/Papers/vanilla-xml2003.html
It proposes making XML a first class language type.
Anne
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 14, 2004 6:08 PM
To: [EMAIL PROTECTED]
Subject: RE: Need suggestions on web service interop and design
Now
/Papers/vanilla-xml2003.html
It proposes making XML a first class language type.
Anne
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 14, 2004 6:08 PM
To: [EMAIL PROTECTED]
Subject: RE: Need suggestions on web service interop and design
Now
: Wednesday, April 14, 2004 3:38 PM
Subject: RE: Need suggestions on web service interop and design
Henrik,
The WS-I Basic Profile disallows the use of SOAP Encoding. It allows
only
Document/Literal and RPC/Literal. Technically, WS-I BP doesn't
*require*
support for RPC/Literal, though. Microsoft
You are advocating an approach that builds Java language specific types
first and generating WSDL + Schema from them, using a SOAP platform
specific
WSDL emitter. Not everyone is sold on this approach, given that the
different SOAP platforms on the market right now all have a) differing
levels of
What would be ideal would be a standard (hopefully JCP-defined, or
perhaps W3C-defined) for converting JDK-1.5-attribute-enhanced Java
classes to *standard* WSDL.
What is .NET / Indigo doing for this? Is there a readable overview?
They have the same problem - even more so, since .NET is
: RE: Need suggestions on web service interop and design
I see you've discovered the impedance mismatch between language types
and
XML types. For example, Java can't subclass by restriction -- only by
extension (hence Axis's conversion of your string restriction to a
string
extension).
Here's some
Hi;
What happens if you come
from the .net side? We have to make some java code a web service that both .net
and java can hit. But what if I create a C# class that models the interface. Then
use .net to create the WSDL?
Then use that
WSDL to create the java server and client code?
java.lang.String
description;
...
... // appropriate getters and setters adn
constructor.
...
}
Ross
-Original Message-From: David Thielen
[mailto:[EMAIL PROTECTED]Sent: Wednesday, April 14, 2004 6:55
PMTo: [EMAIL PROTECTED]Subject: RE: Need
suggestions on web service interop
PROTECTED]
Sent: Wednesday, April 14, 2004 3:38 PM
Subject: RE: Need suggestions on web service interop and design
Henrik,
The WS-I Basic Profile disallows the use of SOAP Encoding. It allows
only
Document/Literal and RPC/Literal. Technically, WS-I BP doesn't *require*
support for RPC
35 matches
Mail list logo
