and
> better looking. ;)
>
>
> "WSDL first, a good idea. (tm)"
>
>
>
>
> From: Praveen Peddi [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, February 16, 2005 5:43 PM
>
> To: [EMAIL PROTECTED]
> Subject
From: Praveen
Peddi [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 16, 2005 5:43 PM
To: [EMAIL PROTECTED]
Subject: Re: array of recursive beans (doc/literal style)
I don't really like the option 1.
And I don't know how to go for option 2 :). I am trying to apply Er
: [EMAIL PROTECTED]Subject: Re: array of
recursive beans (doc/literal style)
I don't really like the option 1. And I don't know
how to go for option 2 :). I am trying to apply Eric's patch and see if it fixes
my problem (assuming that this patch will be applied to Axis's
Chiesa
To: [EMAIL PROTECTED]
Sent: Wednesday, February 16, 2005 5:06
PM
Subject: RE: array of recursive beans
(doc/literal style)
yes, our most recent messages crossed in the
ether.
From: Praveen Peddi
[mailto:[EMAIL PROTECTED] Sent: Wednesday, February 16, 2005
yes, our most recent messages crossed in the
ether.
From: Praveen Peddi
[mailto:[EMAIL PROTECTED] Sent: Wednesday, February 16, 2005
2:34 PMTo: [EMAIL PROTECTED]Subject: Re: array of
recursive beans (doc/literal style)
The main problem seems to be in the axis response
anyway. So I am
ednesday, February 16, 2005
2:21 PMTo: [EMAIL PROTECTED]; Eugene
ShershnevSubject: Re: array of recursive beans (doc/literal
style)
I changed the wsdl. ContainerBean is now defined as
(my changes are in blue):
2005-01-27T21:21:29.000Z02005-01-27T21:38:41.000ZEnterprise
Library1
- Original Message -
From:
Praveen
Peddi
To: [EMAIL PROTECTED] ; Eugene Shershnev
Sent: Wednesday, February 16, 2005 2:20
PM
Subject: Re: array of recur
ree
with what .NET is expecting, .NET will deserialize nothing. So you
get null for the children.
From: Praveen Peddi
[mailto:[EMAIL PROTECTED] Sent: Wednesday, February 16, 2005
12:40 PMTo: [EMAIL PROTECTED]Subject: Re: array of
recursive beans (doc/literal style)
Thanks for
ry 16, 2005 1:08
PM
Subject: Re: array of recursive beans
(doc/literal style)
Try changing your WSDL so there is no additional
ArrayOd_tns1_ContainerBean type.
Basically, the definition
of ContainerBean:
. .
.
Not sure if this is
Peddi
To: [EMAIL PROTECTED]
Sent: Wednesday, February 16, 2005
12:39p
Subject: Re: array of recursive beans
(doc/literal style)
Thanks for the response Dino.
I am using Axis rc1.2 nightly build from Feb
8th.
I think you are right regarding desinging the
interfaces. Its b
services for long time and everything was working great until I moved
to doc/literal style. I was using rpc/encoded style before.
I looked at the WSDL generated by Axis and it
looked fine to me. May be somone can look at my WSDL and see where it is wrong.
Two elements that need to look at are
chema, and the existing
application on the server side.
Likewise, generate the .NET (client-side) proxies from the
WSDL.
-Dino
MS
From: Praveen Peddi
[mailto:[EMAIL PROTECTED] Sent: Tuesday, February 15, 2005
9:52 PMTo: [EMAIL PROTECTED]Subject: array of
recursive beans (doc/literal s
I have a method getRootContainers that returns
array of ContainerBean[]. Each ContainerBean has reference to an array of child
ContainerBean[]. With Eugene's help I could make the array stuff work. the
method sucessfully returns the array of COntainerBean[] and .NET reads it fine.
But .NET c
Apparently the client is sending an element GetCapabilities (with no
namespace) while the service is expecting getCapabilities.
Jeff
- Original Message -
From: "Richard Holzmeier" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, February 12, 2005 2:06 P
Please help me with the following problem:
I'm trying to invoke a document/literal (unwrapped) service with two
different operations. As soon as the service class contains more than one
public method and the service is beeing invoked an exception is thrown. If
the service class contains only one m
Please help me with the following problem:
I'm trying to invoke a document/literal (unwrapped) service with two
different operations. As soon as the service class contains more than one
public method and the service is beeing invoked an exception is thrown. If
the service class contains only one m
I am trying to change our webservice from type RPC encoded to
Doc/Literal. =3D20
We are running AXIS 1.2 RC2. ...I was hoping all I would need to do is
change in the deployment the attributes on the service. However when I
do this the wsdl generation fails with an error " Please regis
---
From: Henry Lu [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 04, 2004 3:12 PM
To: [EMAIL PROTECTED]
Subject: doc-literal
Could someone show me a working example of following implementation of
interface for both server and client with java Axis1.2rc?
public interface Echo
{
public St
There is an echo implementation included in the samples with the source
code.
-Original Message-
From: Henry Lu [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 04, 2004 3:12 PM
To: [EMAIL PROTECTED]
Subject: doc-literal
Could someone show me a working example of following
Could someone show me a working example of following implementation of
interface for both server and client with java Axis1.2rc?
public interface Echo
{
public String echo(String s);
public String echo_double(String s1, String s2);
}
public EchoImpl implements Echo
{
..
public Str
string arrays with
doc/literal
i have created a very simple web service using doc/literal encoding
to try to test string arrays. my very simple example as a single
method:
with doc/literal
i have created a very simple web service using doc/literal encoding to try
to test string arrays. my very simple example as a single method:
public Bean execute(Bean bean) {
return bean;
}
a Bean is simply:
public class
with doc/literal
i have created a very simple web service using doc/literal encoding to try
to test string arrays. my very simple example as a single method:
public Bean execute(Bean bean) {
return bean;
}
a Bean is simply:
public class
t;[EMAIL PROTECTED]>
10-Sep-2004 15:40
Please respond to [EMAIL PROTECTED]
To
[EMAIL PROTECTED]
cc
Subject
string arrays with doc/literal
i have created a very simple web service using doc/literal
encoding to try to test string arrays. my very si
Hi all,
If we consider interoperating with .NET and Axis, IMO doc/literal is
better than rpc/encoding
Mahen
On Fri, 10 Sep 2004 14:25:13 -0700, Nelson Minar <[EMAIL PROTECTED]> wrote:
> >Whilst everything Jim said is true, rpc/enc has been around the longest
> >in the current
>Whilst everything Jim said is true, rpc/enc has been around the longest
>in the current tools and I think interop is pretty good. Doc/lit is the
>way to go long term, but I think interop today for doc/lit sucks,
>because every tools supports different subsets of XML Schema.
I can second this. In
-Original Message-
From: Jim Murphy [mailto:[EMAIL PROTECTED]
Sent: Friday, September 10, 2004 11:31 AM
To: [EMAIL PROTECTED]
Subject: Re: rpc vs. doc/literal interop
The issues are basically this:
1. With rpc/enc there are many "valid" ways to say the same thing. If
the soap stac
described completely by XML Schema so with less optionality there is a
better chance of more toolktis getting it right.
Jim
Melzer, Steven wrote:
can someone please explain to me the interop issues with rpc vs. doc literal.
specifically, what datatypes (arrays, nested complex types, etc) will int
can someone please explain to me the interop issues with rpc vs. doc literal.
specifically, what datatypes (arrays, nested complex types, etc) will interop.
i am writing some web services and need to support .net and gsoap clients. rpc seems
a lot easier, but not if it won't interop wit
i have created a very simple web service using doc/literal encoding to try to test
string arrays. my very simple example as a single method:
public Bean execute(Bean bean) {
return bean;
}
a Bean is simply:
public class Bean {
private
It seems that AXIS (latest CVS) doesn't serialize properly complex
objects (beans) when in doc/literal.
More precisely it doesn't handle as it should a SOAP body with multiple
namespaces, as shown in the following exemple :
(I've come upon this problem trying to return a tree s
2:20
AM
Subject: RE: multiple objects without
using arrays in doc/literal
Thomas,I agree that client is the one that needs to be
fixed. The client is being generated by Siebel tools and they say the
problem wouldbe fixed in their next version and upgrading the version is
not an o
: Wednesday, August 04, 2004 2:50 PM
To: '[EMAIL PROTECTED]'
Subject: RE: multiple objects without using arrays in doc/literal
Thomas,
I agree that client is the one that needs to be fixed.
The client is being generated by Siebel tools and they say the problem would
be fixed in their next v
om: THOMAS, JAI [AG-Contractor/1000] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 04, 2004 11:21 AM
To: '[EMAIL PROTECTED]'
Subject: RE: multiple objects without using arrays in doc/literal
Vikas,
Since you are using doc/lit, you should be able to get the DOM object and
get hold
ct xml doc.
Jai
-Original Message-
From: Vikas Phonsa [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 04, 2004 12:33 PM
To: '[EMAIL PROTECTED]'
Subject: multiple objects without using arrays in doc/literal
Hi Everybody,
I am developing a doc/literal style web service an
Hi Everybody,
I am developing a doc/literal style web service and the implementation java
class has only one method:
Public String insertOrUpdate(Contact contact).
And the contact object has an array of addresses. So the SOAP message should
look like this:
addr1
addr2
There is an
Hi;
I created a very simple web service (pass nothing, returns a
string) and created it using doc/literal.
It runs fine on the server and my java client can access it
with no problem.
When I try to access it with C#, I get an arrayindexoutofbounds
exception on the call to
PROTECTED]
Subject: RE: Exposing an EJB as a doc-literal web service
> can u suggest me a web services book which you feel is the best? may
> be you should write one
She already did! :-)
http://www.informit.com/title/0321185773
Best regards,
Robert Lowe
http://RMLowe.com/
> can u suggest me a web services book which you feel is the best?
> may be you should write one
She already did! :-)
http://www.informit.com/title/0321185773
Best regards,
Robert Lowe
http://RMLowe.com/
cc
PM
Subject
RE: WS-I Test on doc/literal Web
Please respond to Service
hings up...
can u suggest me a web services book which you feel is the best?
may be you should write one
thanks again.
Rahul.
From: "Anne Thomas Manes" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
Subject: RE: Exposing an EJB as a doc-literal we
ecognizing that you
have no parts.
I suggest you report this as a bug.
Anne
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 17, 2004 1:51 PM
To: [EMAIL PROTECTED]
Subject: Re: WS-I Test on doc/literal Web Service
coded
- rpc/literal
- doc/literal
Note that there is no such thing as doc/encoded. Note also that wrapped is a
programming convention, not a message encoding style.
There are fundamentally two types of programming style:
- method invocation
- messaging
Axis supports three types of method invoc
omas Manes" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
Subject: RE: Exposing an EJB as a doc-literal web service
Date: Wed, 16 Jun 2004 18:17:00 -0400
Rahul,
> 1.) What is the "Message" message style you referred to below? I have
> seen that be
PM
Subject
Re: WS-I Test on doc/literal Web
Please respond to Service
[EMAIL PROTECTED]
What does your Binding look like?
Jim
Mindreef, Inc.
[EMAIL PROTECTED] wrote:
This is not a question on Axis, but rather a problem that I'm facing while
running the WS-I test tool on my doc/literal Web Services. I have
doc/literal Web Services with some operations whose return type is void
This is not a question on Axis, but rather a problem that I'm facing while
running the WS-I test tool on my doc/literal Web Services. I have
doc/literal Web Services with some operations whose return type is void.
The WSDL looks
s also an unofficial WSDL style known as the wrapped convention, which
is a form of document style that simulates the rpc style. (It's an
alternative to rpc/literal.) .NET uses the wrapped convention by default.
These styles correspond as follows:
WSDD WSDL
RPC
how the object interface
could look like for a wrapped-literal or a pure doc-literal service (or
for any style of service),
especailly in terms of the parameters it accepts/returns. But from some
of the posts on the Axis
archive, it would seems that if one wants to use a doc-literal s
Title: RE: Exposing an EJB as a doc-literal web service
Found one of your discussions of
Document/Literal Wrapped at the following link. Very informative...thanks!
http://www.burtongroup.com/weblogs/annethomasmanes/archives/2004/04/000187.html
-Wei
-Original Message
Title: RE: Exposing an EJB as a doc-literal web service
Wrapped style imposes a lot of restrictions on the schema structure of your
message: no attributes, only sequences (no union or choice, etc).
Is this true? Where can I get more information on that? I'm pretty sure I've
[mailto:[EMAIL PROTECTED]
> Sent: Monday, June 14, 2004 5:07 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Exposing an EJB as a doc-literal web
> service
>
> The following article is short and to the point:
>
> Which style of WSDL should I use?
> RPC/encoded, RPC/literal, d
/Literal.
Anne
-Original Message-
From: Flores, Raul [mailto:[EMAIL PROTECTED]
Sent: Monday, June 14, 2004 5:07 PM
To: [EMAIL PROTECTED]
Subject: RE: Exposing an EJB as a doc-literal web service
The following article is short and to the point:
Which style of WSDL should I use?
RPC/encoded
indicates which provider to route the message to (RPC, EJB, MSG,
or a custom provider). The provider processes the message, maps the message
elements to Java or DOM objects, and invokes the appropriate method.
The key distinction between RPC/encoded and Doc/Literal is in the way the
message is c
Hi,
I'have downloaded the nightly build(14/06/2004). Always the same error
Pascal PRIOUX
- Original Message -
From: "Davanum Srinivas" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, June 14, 2004 5:44 PM
Subject: Re: WS-I doc-literal ,wscompile an
-Original Message-
From: Rahul Jain [mailto:[EMAIL PROTECTED]
Sent: Monday, June 14, 2004 1:35 PM
To: [EMAIL PROTECTED]
Subject: RE: Exposing an EJB as a doc-literal web service
Hi,
Sorry...here is the attachd WSDL for the non-wrapped doc-literal
service.
Rahul.
>From: "Rahul Jain&
Hi,
Sorry...here is the attachd WSDL for the non-wrapped doc-literal service.
Rahul.
From: "Rahul Jain" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: RE: Exposing an EJB as a doc-literal web service
Date: Mon, 14 Jun 2004 11:28:16 -0700
Hi Anne,
APPED and it was fine. So does this
mean that doc-literal services should always take one param and not more?
Also can you clarify something: According to me, say there is a class with a
method signature (from my case)
public String loadXMLData(String user, String xmlData)
and if one wants to e
ransport="http://schemas.xmlsoap.org/soap/http"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
http://ppx-ps.enitab.fr:8080/jmeprovisioning/control/services"/>
- Original Message --
try changing the method signature to from Vector to Collection
-- dims
On Mon, 14 Jun 2004 15:55:59 +0200, Pascal Prioux <[EMAIL PROTECTED]> wrote:
>
>
> Hi,
> Evething works fine now
> (http://marc.theaimsgroup.com/?l=axis-user&m=108695341411607&w=2)
> Thanks for the responses
>
> Except for
Hi,
Evething works fine now
(http://marc.theaimsgroup.com/?l=axis-user&m=108695341411607&w=2)
Thanks for the responses
Except for a method wich returns a Vector
.(getVectorOfMIDPRecordStoreRecord)
the wscompile tool (bundled with JME SDK 2.1) generates the following error:
error: Found unknown
Is it a bug? It fialed to runa simple example with doc/literal style.
//my interface:
//
public interface Echo
{
public String echoString(String arg);
public String echoString_double(String arg1, String arg2);
}
//my interface
Can you send us your WSDL?
My first hunch is that you aren't using a wrapper element for your two
parameters. A doc/literal message must contain only one child element in the
. Axis will process only the first element and ignore any
subsequent elements. That first child element should
Can you send us your WSDL?
My first hunch is that you aren't using a wrapper element for your two
parameters. A doc/literal message must contain only one child element in the
. Axis will process only the first element and ignore any
subsequent elements. That first child element should
exception.
Thanks.
Rahul.
From: Wei Hsu <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
Subject: RE: Exposing an EJB as a doc-literal web service
Date: Mon, 7 Jun 2004 15:53:45 -0700
Actually, the build-in Axis EJB Provi
Title: RE: Exposing an EJB as a doc-literal web service
Actually, the build-in Axis EJB Provider can expose the EJB as a doc-literal web service. In the simplest case, all you have to do is change one line in your deploy.wsdd:
From
to
If you want to use straight up doc-lit and
Hi,
Can somebody plz gudie me how I would expose an EJB as a doc-literal web
service? The build-in Axis EJB Provider exposes it as a RPC service only.
Thanks.
Rahul.
_
Looking to buy a house? Get informed with the Home Buying Guide
lt;[EMAIL PROTECTED]> cc:
Subject: RE: Can the same Axis Web
Service have both rpc/encoded and doc/literal
20/04/04 15
MAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 20, 2004 3:28 AM
To: [EMAIL PROTECTED]
Subject: RE: Can the same Axis Web Service have both rpc/encoded and
doc/literal methods? ['Watchdog': Virus checked] ['Watchdog': checked]
Anne I accept what u say...
But
Hi,
Does anyone know how I can unsubscribe ?
Cheers,
AH
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: RE: Can the same Axis Web Service have both rpc/encoded and
doc/literal methods? ['Watchdog': Virus checked] ['Watchdog': checked]
Date:
TECTED]> cc:
Subject: RE: Can the same Axis Web
Service have both rpc/encoded and doc/literal
16/04/04 17:47methods? ['Watchdog&#
e Axis Web Service have both rpc/encoded and doc/literal
methods?
Will Axis support both rpc/encoded and doc/literal methods in the same web
service?
Thanks.
e Axis Web Service have both rpc/encoded and doc/literal
methods?
Will Axis support both rpc/encoded and doc/literal methods in the same web
service?
Thanks.
Will Axis support both rpc/encoded and doc/literal methods in the same web
service?
Thanks.
>My suggestion is that we fix Axis so that it appends the and
> elements to existing definitions.
I like that idea.
: [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 WSDL definition (plus it's referenced definitions) -- not with a complete WSDL document including
and elements. The binding inform
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
start
When "starting with WSDL", what that really menas if that you should be
starting with a WSDL definition (plus it's referenced definitions) -- not with a complete WSDL document including
and elements. The binding information should be
specified during packaging and deployment. The element sh
FWIW, ASP.NET does this very thing when generating WSDL. The actual
service endpoint depends on the request url for the WSDL
so if I request http://www.fred.com/foo/bar.asmx?wsdl the generated wsdl
would contain a serice port to http://www.fred.com/foo/bar.asmx.
Makes it kinda fun with our WSD
>There are a bunch of doc/lit specific bugs that have been fixed in both the
>straight 1.2 alpha release and the latest Axis CVS.
Understood. This is really frustrating if you're trying to use Axis
1.1. A beta of Axis 1.2 that passes all tests would be very welcome.
>As to your template WSDL sugg
nt: Thursday, 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
The definitive source of information for all things happening in the world
of XML is Robin Cover's Cover Pages [1]. I also plan to start a blog thread
that summariezes all the latest standards/specification efforts -- I just
need to find the time to do so. Perhaps this weekend...I'll post a note
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 1.1? And
do you mean the alpha release or the latest Axis CVS?
You mention that if you use ,
>Endpo
Anne Thomas Manes helpfully writes:
>We will solve the security problem in the very near future.
>OASIS WSS SOAP Message Security (the standardized version of WS-Security)
>should be ratified as a formal OASIS standard by the end of the month.
I believe the documents are available here:
http://
Note that TREX was merged with RELAX to create RELAX NG.
Also -- more to the point -- note that RELAX NG does not define a type
system. It defers to XML Schema for the type system. Unfortunately, we
really can't escape XML Schema.
Sun, Microsoft, and everyone else has standardized in XML Schema
Regarding standard SOAP headers:
We will solve the security problem in the very near future.
OASIS WSS SOAP Message Security (the standardized version of WS-Security)
should be ratified as a formal OASIS standard by the end of the month.
OASIS WSS defines standard tags for you to put authentica
Anderson Jonathan wrote:
Jim Murphy wrote:
Why wouldn't a very thin Axis working with several Java
binding/marshaling layers be a compelling approach?
Problem is, I have yet to see a SOAP stack that works this way. "Consuming
one stream and producing another" implies that each intermediar
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 marshaling/bin
Anderson Jonathan wrote:
The problems is that intermediary nodes can change the content of the SOAP
envelope, plain and simple. This really complicates that SOAP XML data
binding issue. Intermediary node implementations need access to the SOAP
header information at the very least... any type of
e wire and how this gets
produced is of secondary importance IMHO ...
best,
alek
-Original Message-
From: Jim Murphy [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 17, 2004 2:21 PM
To: [EMAIL PROTECTED]
Subject: Re: XmlBeans and Axis? [Re: Doc/Literal support in axis
I favor the appr
ED]
Sent: Wednesday, March 17, 2004 2:21 PM
To: [EMAIL PROTECTED]
Subject: Re: XmlBeans and Axis? [Re: Doc/Literal support in axis
I favor the approach this suggests:
Make the SOAP stack an XML delivery and minimal SOAP processing engine
and leave XML<->Java type translation to another
Jim Murphy wrote:
Dennis Sosnoski wrote:
doc/lit means you don't need to care about 1 or 3 - you specify the
XML format and let the clients worry about how they want to handle
it. 2 is a separate issue...
Really? I can see how it would be liberating to think this way but I
can break away from
I favor the approach this suggests:
Make the SOAP stack an XML delivery and minimal SOAP processing engine
and leave XML<->Java type translation to another layer. Chose Castor,
XmlBeans, JAXB 1.0, 2.0 whatever. The choice is dictated by how I want
to work witht he XML recognizing that the XML is
Dennis Sosnoski wrote:
Jim Murphy wrote:
IMHO, Web Service Message design has been an afterthought of the spec
working groups that comprise your typical WS stack. You need to know
a lot of grunge to design an easy to consume service:
1. XSD - what to use and what to avoid is the hard part esp
Nelson Minar wrote:
This discussion has been very useful. Thank you!
Jim Murphy of MindReef/SOAPScope said:
What that means to me is that SOAP is the ... tags that allow service
designers to put application stuff in one bucket (soap:Body) and keep
that separate from non-functional stuff that goes
Hi all,
Has anyone here had any experience working with attachments
for a document literal service in AXIS? Also, how does SOAP with attachment
for AXIS stack up with attachment support in Apache SOAP? Really appreciate
any insights you can give. Thanks!
Wei
Aleksander Slominski wrote:
Dennis Sosnoski wrote:
I've got my own lightweight SOAP framework built around JiBX. I'll try
to get something out about that, probably adding it as a subproject in
conjunction with the beta 3a release next week, so that people who are
interested in a decoupled ap
Dennis Sosnoski wrote:
This is great to hear about, but information on WS/XSUL looks scarce
(I found your slide set - or is that slajd set?).
woes of trying to do power point to html conversion ... (BTW "slajd" is
in Polish for slide :) )
Can you point me at anything that's usable?
WS/XSUL ju
Aleksander Slominski wrote:
Dennis Sosnoski wrote:
Long term it's clear that real data binding support needs to be
integrated into the SOAP framework
do you know if anybody tried to add support for XmlBeans
(http://xml.apache.org/xmlbeans/) to AXIS?
we have XmlBeans integrated in WS/XS
1 - 100 of 244 matches
Mail list logo
