Let me be more specific about the 2 areas that have troubled me since I
was second in line of kicking off this long thread. I provide this as
input and food for thought.
As I mentioned previously, I have no axe to grind. I'm fairly well aware
of tradeoffs with open source and no open source.
While I have to solve the same problem, I'm not so sure that the
proposed approach is a solution that would work for me. I have looked
into doing this independently. That is, I would define my own
interfaces to insure that my consumers in my company coded to it and
that I would ensure they did
to you if you would like. I had to add a custom
ant task to modify the
server-config.wsdd to change to the XMLBeans serializer but it was no
big deal.
--- Paul Grillo [EMAIL PROTECTED] wrote:
Let me be more specific about the 2 areas that have troubled me since
I
was second in line of kicking off
I would like to add that, to a large extent, I feel Kurt's pain. We
used Axis 1.2 to deploy a single SOAP service that was required of us by
one of our major partners that dictated a .NET interface complete with
SOAP element signature, timestamp, and encryption. I will say that we
got this
,
See my comments inline
On 10/27/05, Paul
Grillo [EMAIL PROTECTED]
wrote:
Short
question: Can I use XMLBeans as distributed by xmlbeans.apache.org as my
serializer/deserializer in Axis2? If so how?
Yes. The default databinding framework is XMLBeans :) don't specifiy any -d
flag
Short question: Can I use XMLBeans as distributed by xmlbeans.apache.org
as my serializer/deserializer in Axis2? If so how? It appears to be different
than what is contained in Axis2
I have a simple WSDL backed up by a few Schemas. They generate clean
java classes in Axis 1.2
So I
on how would be helpful
I thank anybody that can help.
From: Paul Grillo
Sent: Monday, October 24, 2005
12:15 PM
To: axis-user@ws.apache.org
Subject: How to access and use
Serializer independently?
Ive been playing with this for awhile, and there just
seems to be a lot
AM
To: axis-user@ws.apache.org
Subject: RE: How to access and use
Serializer independently?
Hi Paul,
I would guess yes. You
will have to write a handler for it.
Thanks,
Parikh, Pratik
From: Paul
Grillo [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 26, 2005
8:42 AM
guess yes. You
will have to write a handler for it.
Thanks,
Parikh, Pratik
From: Paul
Grillo [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 26, 2005
8:42 AM
To: axis-user@ws.apache.org
Subject: FW: How to access and use
Serializer independently?
Cant believe that nobody has tried
Ive been playing with this for awhile, and there just seems
to be a lot of coupling that makes it difficult to do this.
Essentially I have a service running perfectly using the default
serializer/deserializer for Axis 1.2
Now I would like to incorporate a REST interface on a few
I currently am getting the following fault returned from my Server when
communicating.
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
soapenv:Body
Is there any way that I can capture and log any/all Axis Fault messages
on the server? These can come from any place, from serialization
errors, to signature verification, etc. Is there a way to place a
handler somewhere where these can be caught? Or some code to catch the
fault? any way that
For client side Axis use, I'm following/using the pattern as generated
by the WSDLtoJava.
Essentially an org.apache.axis.client.Service is created by feeding it
a client.wsdd file. From this service I get a
org.apache.axis.client.Stub by constructing one using the
aforementioned Service.
Now,
There are very few questions, and less answers on DIME support for Axis
out there, but Ill give this a try.
If I turn on DIME support and attach normally, the system appears to send
using DIME making assumptions, I assume, as to how to fill out the header
information.
I noticed
Perhaps this is so easy, I shouldnt be asking. Im
simply using the client org.apache.axis.client.Stub and adding a attachmentPart.
It all goes fine except I would like base64 encoding, not binary.
Is there an easy setting for this? Or do I have to tell the system
what serializer to use
Hoping somebody has seen this. Perhaps it's a library issue or a
setting I missed. Not sure whats happening.
After straightening out client side axis and insuring server received
messages by just returning a null, I just now added returning a non-null
message and the client throws an exception
I know there is sort of a lot to see here, but I wanted it to be
complete. Any help will be very very much appreciated.
I've been looking at this for a couple of days, and can't figure out how
to get axis to generate an xml instance consistent with my consumer's
requirements. If anybody might
17 matches
Mail list logo
