Hi,
why don't you simply use a base64binary field instead of an attachment? As the
attachment is encoded the same way, I can't see any advantage.
On top of it, attachments are notoriously tricky, especially in interop
scenarios.
Cheers Wolfgang
--- On Tue, 2/2/10, mhuffman
Dear ppl,
I think this leads us nowhere.
Webservices is neither JAVA nor DOTNET nor PHP nor PERL-specific nor should it
be. Webservices is expected to interoperate with all of them. How is this to be
accomplished?
By adhering to the standards laid down for WSDL.
So PLEASE restrain yourself to
Dear ppl,
I think this leads us nowhere.
Webservices is neither JAVA nor DOTNET nor PHP nor PERL-specific nor should it
be. Webservices is expected to interoperate with all of them. How is this to be
accomplished?
By adhering to the standards laid down for WSDL.
So PLEASE restrain yourself to
: Re: [jira] Commented: (AXIS2-3300) minOccurs=0 always generated by
Java2WSDL - problems with .NET client generation
To: axis-dev@ws.apache.org
Date: Thursday, January 7, 2010, 12:16 PM
WJ Krpelan ha scritto:
Dear ppl, I think this leads us nowhere. Webservices
is neither JAVA
nor DOTNET
Hi,
use the same wsdl to create stubs on both sides
dont use any proprietory namespaces like *mircosoft* etc
Cheers Wolfgang
--- On Tue, 12/22/09, abhishah abhishah4...@gmail.com wrote:
From: abhishah abhishah4...@gmail.com
Subject: Webservice and javascript calling
To:
Hi
its no bug, at most its a missing (interoperability-) feature -
cause if you adapt java2wsdl to some specific microsoft behaviour it gets
incompatible with other platforms which makes no sense
you could make a interoperability feature request - either here or with
mircosoft :)
anyway wsdl
Hi,
well, dont expect anything but WSDL-first to work reliably in
interoperability scenarious - ever!
i dont think adopting java2wsdl to some micro* style would be a good idea,
because it would break interoperability elsewhere!
Cheers, Wolfgang
--- On Mon, 11/2/09, Charles Galpin (JIRA)
peers in the mix, including
CXF-based ones, Axis2
ones etc. we are seeing some incompatability issues - for
ex. CXF does not handle
rcp/encoded styles. So how do you suggest we avoid the
migration and manage to
handle these issues?
Thanks again
WJ Krpelan wrote:
Hi
http
if deprecated) styles
programmatically?
Cheers
WJ Krpelan wrote:
Hi,
all SOAP styles except doc/lit are kind of deprecated
by now and are no longer fully supported by most frameworks,
if at all.
You better migrate everything to doc/lit, resp.
doc/lit wrapped I suppose
Cheers, Wolfgang
Hi,
all SOAP styles except doc/lit are kind of deprecated by now and are no longer
fully supported by most frameworks, if at all.
You better migrate everything to doc/lit, resp. doc/lit wrapped I suppose
Cheers, Wolfgang
--- On Thu, 8/27/09, Demetris demet...@ece.neu.edu wrote:
From: Demetris
Hi,
Webservice Engines dont create Standards but try to implement them - as good as
it gets anyhow -
I'd say developers of Web Services should not need to bother with SOAP at all
- apart from extreme cases of interoperability problems.
Using a WSDL first approach you should have no problems
Hi,
your strange characters is standard xml-escaped characters obviously
are you doing soap-processing by hand?
Cheers Wolfgang
--- On Mon, 8/24/09, David Vir virch...@gmail.com wrote:
From: David Vir virch...@gmail.com
Subject: Axis 1.4 strange characters lt; #13;
To:
Hi all,
without claiming knowledge of details here, let me state the obvious: of course
utf-8 cannot be cleanly mapped to 8-bit character sets.
--- On Wed, 8/19/09, Michael Fryars (JIRA) j...@apache.org wrote:
From: Michael Fryars (JIRA) j...@apache.org
Subject: [jira] Commented: (AXIS2-4468)
Hi folks,
Right - by pure doctrine. However, the need to master xml-schema and wsdl
doesnt make life so much easier for web service developers, does it?
Cheers Wolfgang
--- On Thu, 7/30/09, Ajith Ranabahu ajith.ranab...@gmail.com wrote:
From: Ajith Ranabahu ajith.ranab...@gmail.com
Subject:
Hi Matthias,
in my personal view you are asking to much.
to achieve interoperability, its not unusual that one has to adjust
automatically generated wsdls/schemes manually.
if you try to do webservices fully dynamically you'd better make sure the same
webservice-engine is present on both sides
Hi,
your wsdl includes an unmatched any/?
Cheers Wolfgang
--- On Mon, 7/6/09, Sneha (JIRA) axis-dev@ws.apache.org wrote:
From: Sneha (JIRA) axis-dev@ws.apache.org
Subject: [jira] Created: (AXIS-2795) Axis 1.4 support for complex type in
SOAP request
To: axis-dev@ws.apache.org
Date:
Hi,
it goes against the philosophy of web services to become dependent on java
packages or .net assemblies or whatever.
it is essential that a classname within a soap-message is NOT relied upon for
communication purposes to have a special meaning within a certain framework.
you would kill
Hi
you are right inasfar as that wsdl is not correct (invalid)
sorry no way to to dynamic webservices without valid wsdl-document
you could contact the source very well IMHO cause all other consumers will have
the same problem -
Cheers, Wolfgang
--- On Thu, 4/2/09, Clifton B. Sothoron Jr.
Hi,
having looked around a bit I guess the encoding of the SOAP-response is not
UTF-8 at all, but plain old ascii. Still the fault would be on the server side
and there is little you can do about it on the client side.
Mind you the encoding=UTF-8 tag does not force anything but is meant as a
Hi,
short of rewriting AXIS2 on the client side, I see no method to come to terms
with invalid UTF-8 sequences coming with the SOAP-response.
Invalid UTF-8 is not meant to work of course.
Perhaps the server side can change the encoding to UTF-16?
Wolfgang
--- On Mon, 12/1/08, Wesley Mesquita
Hi,
according to your info you are receiving an element which relates to a
different wsdl resp. a different schema.
to verify the location of that element, monitor the SOAP-messages you send and
receive
is your wsdl importing some schemas? watch out for an import tag
Wolfgang
--- On Thu,
Virgil,
pls provide the wsdl
Cheers, Wolfgang
--- On Wed, 10/1/08, Trasca Virgil [EMAIL PROTECTED] wrote:
From: Trasca Virgil [EMAIL PROTECTED]
Subject: getting exceptions while calling .Net web-services with Axis client
To: axis-dev@ws.apache.org
Date: Wednesday, October 1, 2008, 8:15 PM
Hi,
I'd say dont do it this way
AXIS 1.4 is no longer being maintained
you could use base64 encoding with axis 1.4
Cheers,
Wolfgang
--- On Thu, 8/14/08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
Subject: Axis 1.4 and MTOM
To: axis-dev@ws.apache.org
numeric value
Cheeers,
Wolfgang
--- On Mon, 8/11/08, Carsten Burghardt [EMAIL PROTECTED] wrote:
From: Carsten Burghardt [EMAIL PROTECTED]
Subject: Re: Encoding problem
To: axis-dev@ws.apache.org
Date: Monday, August 11, 2008, 4:40 PM
Quoting WJ Krpelan [EMAIL PROTECTED]:
Hi,
hope I got
Hi,
hope I got this right.
The encoding with #hex; looks perfect to me.
You should check wether the actual hex-values correspond to the
UNICODE-CODEPONTS of you Russian Characters.
If this is the case, how did you verify the characters were broken inside the
DOM-tree. Is your tool capable of
Hi
I know what happened ;-)
you tried to serialize XML by hand
my advice: use an appropriate tool
Cheers
--- On Fri, 7/25/08, Dini Omar [EMAIL PROTECTED] wrote:
From: Dini Omar [EMAIL PROTECTED]
Subject: Adding a CDATA element being converted to lt; and gt
To: [EMAIL PROTECTED],
Hi,
if you transport xml within xml-schema strings it is syntactically necessary to
escape certain characters as the embedded xml-strings are no official part of
the surrounding document and the xml-parser would behave unpredictably. This
got nothing to do with AXIS, however so maybe you should
Hi,
I'm sure the client wont do a charset-conversion just because of setting this
property. So in my view the problem is rather on the server side.
Mind that XML-Standards default to UTF-8 or UTF-16 and you probably will lose
some interoperability by using a different charset encoding.
Why dont
Regards!
Raihan
--- On Tue, 7/1/08, WJ Krpelan [EMAIL PROTECTED]
wrote:
From: WJ Krpelan [EMAIL PROTECTED]
Subject: Re: Questions regarding Axis1.4
To: axis-dev@ws.apache.org
Date: Tuesday, July 1, 2008, 6:41 AM
ok,
The errors you are getting are caused by the client
java
) in
C:\TestCourtWS\TestCourtWS\TestCourtWS\Form1.cs:line
269
Thanks so much!
Raihan
--- On Mon, 6/30/08, WJ Krpelan
[EMAIL PROTECTED] wrote:
From: WJ Krpelan [EMAIL PROTECTED]
Subject: Re: Questions regarding Axis1.4
To: axis-dev@ws.apache.org
Date: Monday, June 30, 2008, 10:35
!
Raihan
--- On Sun, 6/29/08, WJ Krpelan
[EMAIL PROTECTED] wrote:
From: WJ Krpelan [EMAIL PROTECTED]
Subject: Re: Questions regarding Axis1.4
To: axis-dev@ws.apache.org
Date: Sunday, June 29, 2008, 5:32 PM
Hi
what you are doing (putting xml documents within xml
documents as strings
Hi ppl,
what I can contribute: the binary representation of utf-8, utf-16, . and
the actual UNICODE-values specified by U+ have no direct relation at all
but are completely different binary representations (hopefully of the same
characters)
Cheers, Wolfgang
--- On Mon, 6/30/08, Deepal
to your personal account in Apache has any
restrictions on attachments.
I hope this will help you see what I am doing wrong.
I again thank you sincerely for taking the time out to look
at this issue.
Raihan
--- On Mon, 6/30/08, WJ Krpelan
[EMAIL PROTECTED] wrote:
From: WJ Krpelan
Hi
what you are doing (putting xml documents within xml documents as strings)
is not considered usual practice. I'm not surprised that you are running into
problems with AXIS 1 using this approach.
I dont understand exactly what you mean by putting it hardcoded vs generated
into the response.
Hi
in principle you just need a http:-server which has
access to a webservice-engine, that is a
xml-serialization and deserialization-program which
knows how to handle SOAP-messages.
in practice you will have to use one of the standard
solutions available, be it in java, dotnet or
elsewhere.
Hi,
First point is your working WSDL is working fine only
because you have all referenced XML-Schemas
accessible.
(doesnt work with me)
Second point is the imported XML-Schema MUST have a
different Namespace than the importing XML-Schema.
Third point is you should qualify all referenced
elements
Hi,
just guessing: could something have changed the actual
encoding to utf-16 on the way (standard encoding with
microsoft windows) ? of course an UTF-8-XML-Document
is not expected to start with 0xFF.
additionaly, using text/xml is not quite safe,
application/xml would be preferrable
Cheers
---
, it might be the case that the
message is UTF-16.
How can I determine that? Or where can I tell axis2
that it should
decode UTF-16 messages?
Thanks,
Simon
WJ Krpelan wrote:
Hi,
just guessing: could something have changed the
actual
encoding to utf-16 on the way (standard encoding
Hi,
in .net the corresponding program is wsdl.exe
I'm very interested whether MTOM-communications is
interoperable so pls tell us your experiences.
Cheers,
Wolfgang
--- Thilina Gunarathne [EMAIL PROTECTED] wrote:
Hi,
Now, I'm trying to create an application to talk
to a .NET web service
Hi,
Its very clear that we have a technical problem when
deserializing cause the second ns1: overwrites the
first. My question is how this serialization comes
about? AXIS 1.4 wasnt built with sending arbitrary
XML-Messages around in mind. I'd suggest start anew
with a WSDL-first approach.
Cheers
Hi Ajit,
A typical Web Service with Axis 1.4 needs half a
second only. What is the size of your payload?
Cheers Wolfgang
--- [EMAIL PROTECTED] wrote:
Hi Group,
I am using Axis 1.4 for my web service development.
One thing I have observed is that the time taken for
the return
Hi,
which Axis version ? Axis 2 1.4 or Axis 1 1.4?
WSDL? SOAP-Trace?
Cheers
Wolfgang
--- [EMAIL PROTECTED] wrote:
Hi Group,
I have an axis java client axis java server which
works fine.
When I use wsdl with a VB client, I am able to hit
the server, but when
I make the call, the
Hi,
could you provide the wsdl and a soap-trace?
which style and encoding are u using?
Cheers Wolfgang
--- Frank Zhou [EMAIL PROTECTED] wrote:
Hi All,
I am re-posting this message, hoping to get some
urgent help.
I am using AXIS 1.4 for my web service needs. I am
now
encounting
Hi,
once upon a time there had been a size limit for
classes of 64K
Just wildly guessing.
Cheers,
--- Hemant Borole [EMAIL PROTECTED] wrote:
Sorry, The binding we are using is rpc.
On Dec 20, 2007 8:16 AM, Hemant Borole
[EMAIL PROTECTED] wrote:
Hi Amila,
This is the same issue that I
Hi
you should generally use doc-lit-wrapped anyway,
Cheers, Wolfgang
--- Terry Zhou [EMAIL PROTECTED] wrote:
Hey Anne,
Sorry my typo the client message is wrong, should be
env:Envelope
xmlns:env=http://schemas.xmlsoap.org/soap/envelope/;
env:Header/
env:Body
math:a
Hello,
mere guess: are you using xhtml in the error-case?
pls send a soap-trace
Cheers
--- BJuma [EMAIL PROTECTED] wrote:
Belal wrote:
The strange thing is if it is OC4J alone, the
auto-generated java client
is working fine as expected. but on the Oracle AS
it is not working.
Hi
the problem with non-perfect XSD is that its no longer
XSD proper and the whole idea of a world-wide agreed
interface standard collapses.
An official XSD-tool must not support inofficial
XSD-modifications.
Your customer cant Schema-validate his non-perfect XML
with standard tools either
Cheers
at with a nightly build.
On 9/27/07, WJ Krpelan [EMAIL PROTECTED] wrote:
Hi
from an XSD point of view, it is possible to
forbid certain kinds of date-formatting by using
patterns. of course, those patterns would have
to be
applied to the original xml-content.
ok from this we can only
Hi
from an XSD point of view, it is possible to
forbid certain kinds of date-formatting by using
patterns. of course, those patterns would have to be
applied to the original xml-content.
Cheers
Wolfgang
--- Jozef Krssak [EMAIL PROTECTED] wrote:
Hi
We have several wsdl and xsd files from
basically, axis 1.1 is hardly being used in
production.
are you referring to the jboss implementation?
--- Ghaznavi, Syed [EMAIL PROTECTED] wrote:
Hi,
I have been trying to resolve this problem for some
time but have not
been able to get my code to work!!
I a sample WSClient
Hi,
look within the generated code for wrapped
worked with Axis 1
Cheers
--- Luciano Resende [EMAIL PROTECTED] wrote:
How can I tell if an AxisOperation is using wrapper
style or not ?
Could someone point me to some place where this is
done in Axis, or
give me some hints, please.
--
Hi
u speaking of some MB ore some GB?
doubt its the JVM. Rather restrictions on
xml-element-size? just guessing
Cheers
--- Thilina Gunarathne [EMAIL PROTECTED] wrote:
You won't be able to send large data inside the
envelope using Base64
binary, as it'll cause Axis2 to load the whole of
data
/wsdl:bindingwsdl:service
name=DocContentService
wsdl:port
binding=impl:DocContentSOAPPortSoapBinding
name=DocContentSOAPPort
/wsdl:port
/wsdl:service
/wsdl:definitions
- Message d'origine
De : WJ Krpelan [EMAIL PROTECTED]
À : axis-dev@ws.apache.org
Envoyé le : Mardi, 4 Septembre 2007
Hi
Generally, only standard xml-schema-data types are
being provided out of the box. The easy way to do it
is to break it up into standard data types. Else I'm
sure IBM is selling some serializing support for its
special data types.
Cheers
--- Thomas Beaujard [EMAIL PROTECTED] wrote:
Hello
I
exchanged, I notice that
the response include CONTENT tag for every single
byte instead of having the array of byte within the
tag CONTENT.
Hope it's not too messy.
Cheers
Thom
- Message d'origine
De : WJ Krpelan [EMAIL PROTECTED]
À : axis-dev@ws.apache.org
Envoyé le : Jeudi, 30
Hello
you can't simply send binary data as on the transport
level its converted to xml, which is basically plain
text.
One simple possibility would be to use datatype
base64binary
Cheers,
--- Thomas Beaujard [EMAIL PROTECTED] wrote:
Hello,
I'm using Axis 1.4.
I have a document style web
, WJ Krpelan [EMAIL PROTECTED] wrote:
Hi
Methinks you shouldn't use type as element name,
and
neither element nor attribute etc. as these
are
kind of reserved words. Use type1 or something
and
it should work imho.
Cheers
Wolfgang Krpelan
--- Amila Suriarachchi
[EMAIL PROTECTED
Hi
Methinks you shouldn't use type as element name, and
neither element nor attribute etc. as these are
kind of reserved words. Use type1 or something and
it should work imho.
Cheers
Wolfgang Krpelan
--- Amila Suriarachchi [EMAIL PROTECTED]
wrote:
Can you please test this for Axis2 1.3
Hi,
why not simply use java2wsdl and extract the schema
from the generated wsdl?
Should be a simple exercise -
Cheers,
--- Josh [EMAIL PROTECTED] wrote:
All,
I am starting to develope contract first web
services. There are many cases
where there are objects in my system that closely
Hi
u calling ant at runtime?
Cheers,
--- Thirumalachar, Shree Rangan
[EMAIL PROTECTED] wrote:
Hi All,
I am trying to call a service from another service
and I am using ALSB
for the messaging.
Here is what I do:
1: My client makes a call to a service through ALSB
dear all,
pls don't create a new bug.
SOAPACTION is REQUIRED for HTTP-Transport (empty or
otherwise) and it is PROHIBITED for every other
transport other than HTTP.
Noone is required to USE it, but there is some
standard-usage within .NET.
Cheers,
Wolfgang Krpelan
--- Amila Suriarachchi [EMAIL
Hi,
got nothing to do with axis nor with webservices
as it is outside of soap:envelope
Lookup http-protocol-messages.
Cheers,
Wolfgang Krpelan
--- HHDirecto.Net [EMAIL PROTECTED] wrote:
Hi,
How can I disable Transfer-Encoding: chunked in
the response of my axis
1.4 webservice?
Thanks
A http-trace of the soap-message would be helpful.
(tcpmon)
Is the server configured to request authentication?
If so, which method?
Cheers
Wolfgang Krpelan
--- Jaliya Ekanayake [EMAIL PROTECTED] wrote:
Hi Nuno,
Can you please check the scenario with Axis only.
Then if it works add
Axis is open source, just do it!
Cheers
Wolfgang Krpelan
--- Domenico Caputi [EMAIL PROTECTED] wrote:
Hi,
I have a new technology that I want expose with web
services, using
Axis. Web Services that I want expose is not a java
class but is a
particular technology that executes some
I'm a little surprised. Google spams??
--- Isuru Suriarachchi [EMAIL PROTECTED] wrote:
---
Isuru Suriarachchi wants to stay in better touch
using some of
Google's coolest new
products.
If you already have Gmail or
Hi,
dont think so. Either the WSDL has been created by
some faulty tool, in this case the error should be
fixed there. Or it has been written by hand, then the
author should have validated it by simply pushing some
button.
Methinks one has to draw the line somewhere.
Cheers
--- Keith Godwin
Hi,
very interesting, where can I find it??
Cheers,
Wolfgang Krpelan
--- Yueqiang [EMAIL PROTECTED] wrote:
Hi All,
We've developed a composite debugger for service
invocations (based on axis 1.x), a web-scale
debugger.
It has following features:
(1) Do not need always to turn on the
Hi
axis 1, no
axis 2, yes
Cheers,
--- Phani Sekhar [EMAIL PROTECTED] wrote:
Hi all,
We are implementing NETCONF on SOAP over HTTP. We
are using Axis.
We require the Axis web service to send some soap
messages
asynchronously to the Axis client without any
initiation.
Ofcourse for the
Sry, without initiation? Dont think so.
Cheers
--- Phani Sekhar [EMAIL PROTECTED] wrote:
Hi all,
We are implementing NETCONF on SOAP over HTTP. We
are using Axis.
We require the Axis web service to send some soap
messages
asynchronously to the Axis client without any
initiation.
Hi,
this seems a minor issue,
dwarfed by the overall soap-overhead and
compensated for by faster dezerialisation.
Cheers,
--- Benjamin Bender [EMAIL PROTECTED] wrote:
Hi I'm using Axis2 for Java and I try to send
messages with the following
content and
the following style between the
Hi cao,
the SOAPAction-Header can hold arbitrary text
(if you're using AXIS both Client and Server)
For other HTTP-Headers, you'll have to use some
HTTPClient.
Cheers,
--- xiangyu cao [EMAIL PROTECTED] wrote:
If the SOAP call is over HTTP, I wonder if I can put
some information in the
HTTP
71 matches
Mail list logo
