I would guess that these different interfaces
and their implementations are separate for a reason. If so, why not keep
the web services separate, for the same reasons, plus the additional reason
that you don't end up with a huge, incomprehensible WSDL?
Incidentally, you don't have to create a
To my mind, unless you are writing code purely
as a web service (that is, code that could never possibly be reused), it's
best to go with writing the business logic separately. In this way, it
can be tested without needing any web service infrastructure in place,
and can be written for
How can I register Custom Deserializer for xsd:int using typemapping ?
Ephemeris Lappis a écrit :
I'm not a SOAP expert ! I think i had understood the difference between
document and wrapped styles, and i suppose tools that will process the
repective wsdl files will not generate similar codes : both use xml messages
without soap encoding, but in document mode the
In fact, to be more precise, it means that there is a schema element, with
the same name as the operation, that contains (wraps) the actual document
element representing all the parameters.
ie:
wrapped
A
AElement/ (of type X)
/A
document
AElement/ (of type X)
I believe this is not part of
Daniel Beland a écrit :
In fact, to be more precise, it means that there is a schema element, with
the same name as the operation, that contains (wraps) the actual document
element representing all the parameters.
ie:
wrapped
A
AElement/ (of type X)
/A
document
AElement/ (of type X)
I believe
hi,
i'am new to axis and cannot get running.
the happyaxis-page says The core axis libraries are present. but when i
try the
links from the install-page, for example
http://localhost:8080/axis/services/Version?method=getVersion
i get a 500 internal server error instead of the mentioned xml page.
Hi Hans
I spent several days with different errors and Exceptions trying to follow
the guide from axis-1_1\docs\install.html until I updated my axis from 1.1
to 1.2RC2. I know it doesn't solve all your problem, but i strongly
recommend it. I don't know why but somehow Tomcat 5.x and axis1.1 won't
Title: Message
I am
not sure it answers your question but...
If you
use SOAPBodyElement instances as parameters (instead of Java
class/basictypes), Axis switches to messaging mode, where user-defined XML
structure are passed in the SOAPBody element, within the SOAP
request.
Of
course,
Thank you for your help. The code below did not get exactly what I wanted but it pointed me in the right direction. I had to go about three child elements deeper to find the actual value I wanted. I actually replaced the getChildElements with getFirstChild and then called
Here is a wsdl-centric way of looking at the 'wrapped' form:
If the wsdl is for a doc/lit operation, regardless of wrapping, the wire
format is fixed by the wsdl. If the request message has parts p1..n
specified by elements e1..n, the soap body must be
Body
e1.../e1
...
en.../en
Does AXIS supports WS-RM?
Thanks,
Jian J Zhang a écrit :
Does AXIS supports WS-RM?
Thanks,
A first implementation exists :
http://ws.apache.org/ws-fx/sandesha/
But I don't know if it's mature.
--
Julien
Mohit,
Can
you provide specifics of the service your client is consuming.
Looks
like what you need is amessage style method. If your server supports it
you should be able to supply an xml doc.
Jai
-Original Message-From: Adaptive Protocols
[mailto:[EMAIL PROTECTED]Sent:
This page:
http://www.webmethods.com/meta/default/folder/006959
seems to suggest that WS-ReliableMessaging competes with WS-RM from OASIS.
Aren't the two the same?
Thanks,
WAJSBERG Julien RD-BIZZ
[EMAIL PROTECTED]
12/21/2004 11:48 AM
Please respond to
axis-user
To
[EMAIL
In my experience, if you're on JDK1.5 with Axis 1.1, you need to use the
xerces parser, axis sets some optional properties on the parser, and
under the version of crimson in 1.5 they now throw exceptions which axis
doesn't handle, if you switch to xerces it should work.
Cheers
Simon
no, WS-ReliableMessaging is a vendor consortium spec from
Microsoft Tibco (amongst others), WS-RM is the result of an OASIS
standardization process of the WS-Reliablilty spec.
Cheers
Simon
From: Jian J Zhang [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 21, 2004 9:36 AMTo:
Title: Message
Greetings,
We are looking to
use Axis to invoke a server-side over the internet, using HTTPS (not
HTTP).
I looked at the
documntatino that comes with Axis and I did nto find much.
Does anybody have
pointers to documentations andexamples on how to configure Axis (server
Hello.
I'm not sure i have understood it all. Sincerly, i remember, years ago, i
had a look at the CORBA/GIOP/IIOP marshalling protocols, and finished the
day with the same headache ! But, once more, we were lucky : we had IDL to
write our interfaces...
As i understand, wsdl doesn't give a clear
So then AXIS does not support WS-RM,
but WS-ReliableMessaging?
Thanks,
Simon Fell
[EMAIL PROTECTED]
12/21/2004 01:09 PM
Please respond to
axis-user
To
[EMAIL PROTECTED]
cc
Subject
RE: WS-RM support?
no, WS-ReliableMessaging is a
vendor consortium spec from Microsoft
Hi folks,
I get this error every time I try to run my applet that has the
following import:
import org.apache.axis.client.Service;
It appears to be a classpath problem, but I'm not sure. To test that idea
I
set my classpath to:
AXIS_LIB=c:\java_classes
Yeah, it would be nice to keep them separate, I've posted a while ago on
the same topic. My concern is that I am not controlling what WS toolkit
clients will use on the client side and these modules have the concept
of a common session for all of them to work together, so I am not sure
whether
I'm running Java Axis v.1.2 RC 2 on Tomcat v.4.1.31. I followed the
install instructions correctly (I think), and am now deploying some
trivial web services to find my way around.
I've written a small handful of Java clients that consume the web
services using the Service and Call classes.
Hello,
We have an Axis based WebService Server with some of the consumers on
the .net platform. The clients on the .net platform is having trouble
with the wsdl that is generated by Axis, though other Axis based
clients and some perl based clients are running fine.
This Axis generated wsdl for
Hi Renuka,
I think, you need to register a type mapping on server side wsdd for this. i.e. define a type mapping in server-config.wsdd with xml type as xsd:int, java type as int class and you custom deserializer factory, which will return custom deserializer.
This should solve the purpose.
Hi Jai, Hi Christian
Thanks for the help.
You are right that the requirements are very likely by fulfilled by using message style communication. But we have a different scenario, that is
on server we may have any kind of web service, that can be rpc-literal-encoded or wrapped-literal etc; but
Hi Russell,
Check the log4j. properties file inaxis classpath. It should be there with proper settings.
Thanks,
MohitRussell Lane [EMAIL PROTECTED] wrote:
I'm running Java Axis v.1.2 RC 2 on Tomcat v.4.1.31. I followed the install instructions correctly (I think), and am now deploying some
Hi All,
I am waiting for a kind response for this problem. I am just stuck with this one. Any clue would be a great help for me.
Thanks,
Mohit
Adaptive Protocols [EMAIL PROTECTED] wrote:
Thanks Anne. I am trying with Wrapped Document/Literal.
But here also, I am facing the same problem. I
Title: Message
You will need to configure your webserver
to enable HTTPS, generate the required certificates and change the port to SSL
port while calling the service from client.
For TOMCAT + Axis, you can find the
following documentation useful:
29 matches
Mail list logo
