Take a look at
http://biryani.med.yale.edu:8081/axis/index.jsp?which=6
there is some code for each service available.
Volkmann, Mark wrote:
message-style frustrations (this time in plain text)
I'm trying to learn how to use message-style services
in Axis. The
projects that have not actually published something
yet, so I don't know what they are aiming for.
remko
Anne Thomas Manes wrote:
See BPWS4J: http://alphaworks.ibm.com/tech/bpws4j
- Original Message -
From: "remko de knikker" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sen
Often, one makes a decision to develop RPC or Doc oriented services.
That's what I did. Since interoperability and uniform data format was a
key factor, I chose DOC.
But now I am trying to develop choreographies, I discover that there not
a lot (none?) (open source/free) choreography engines
Problem/Question:
when Axis generates the wsdl for my webservice, whose wsdl contains an
import it doesn't 'expand'/or import the reference, but merely
reprints the import statement.
Am I doing something wrong, or is this the (in my opinion, if so, not
very practical) preferred method??
I am
to. Similarly for any client code that
reads the wsdl. The human reader has to find it manually and look at it.
Jeff
- Original Message -
From: "remko de knikker" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, July 30, 2003 8:56 AM
Subject: Axis wsdl-generation w
Does it work with
public String doIt(String emptyString){
return now it's filled;
}
??
pablo-bh wrote:
Hi guys!!
I have a class with a method like this:
public String doIt() {
}
I have done deploy and got the wsdl
using ?wsdl.
When I tryed to use the WSDL2Java I
got the error:
I don't seem to have a problem with it.
here's my example which creates a SOAPResponse on the SOAPMonitor. Could
it be that your server is configured to override and handle the exception,
I remember that I once had that issue, although I am no expert on this.
import javax.xml.soap.SOAPBody;
.
Thanx for the input ...
dumdum420
-Original Message[Bhanu
Pabreja]-
From: remko de knikker[mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 15, 2003 12:16PM
To: [EMAIL PROTECTED]
Subject: Re: Message StyleService and Exception
the AxisFault scenario a littel bit more
... cause the invoke() method is invoked at the cleint.
and your client is on .NET so u dont even have
the invoke() call.
How is it working ...
Bhanu Pabreja
-Original Message-
From: remko de knikker
Shouldn't you make sure that there is an appropiate serializer instead??
This looks like avoiding the problem instead of solving it (which works
fine of course)?
It looks to me that the getAsDocument() method sh/could be called in the
serializer, not in the web service itself.
remko
Huaming Liu
I had the same error message on .NET and solved it, by taking out the second
schema declaration.
r
Davanum Srinivas wrote:
Anne,
The problem is that the WSDL is auto-generated by Axis and we need to fix it...
-- dims
--- Anne Thomas Manes [EMAIL PROTECTED] wrote:
I see the
cument dom){}
and I have clients which are going to be VB.Net based so tell me how should
I work on my error.
Also can you explain me more about the mandatory elements and values.
Send me the Handler and I will see if can put it in my evironment.
BP
-Original Message-
From: remko de knikker [
I am browsing through Systinet's WASP web services server, and what I
think is a great feature, is their integration with the IDE (in casu:
Eclipse).
Anychance Axis is offering a GUI/Admin plugin ??
remko
://www.improve-technologies.com/alpha/axis/
I haven't tried it out myself, but I imagine it should at least be worth a
look...
Ian
Ian D. Stewart
Open Systems Engineer II
Enterprise Midrange - Bank One Infrastructure Operations
[EMAIL PROTECTED]
(614) 213-6100
remko de knikker [EMAIL PROTECTED] on 07/11
I've seen that Wrox is about to publish a new book on Axis (was set to some
date in July actually) (i.e. NOT the Next Generation ...)
Most books that cover Axis within a broader perspective of Web Services do
not cover more than the manual does, probably even copied the examples.
I haven't
Here's what I did:
Since the ..invoke() call throws a RemoteException
I used
... throws RemoteException {
try {
...
}
catch (RemoteException e1) {
sb1 =
MessageContext.getCurrentContext().getResponseMessage().getSOAPPart().getEnvelope().getBody();
SOAPFault fault =
Is the AdminServlet in web.xml uncommented?
Is the server running on port 8080? if not use -p 8081 for instance
...
SUNILK_CHAMARTI wrote:
I am getting this error even though the server is up and running.
Regards,
Sunil
-Original Message-
From: Sameer Bombatkar [mailto:[EMAIL
I noticed that you use -p instead of -p
include the space...
the AdminService (AdminServlet in web.xml) is not found, is it uncommented?
Srinath Perera wrote:
Hi
just a TIP
try weather "http://localhost:8080/axis/servlet/AdminServlet".works
with your browser. if not you should
I had two difficulties when I was trying to create a message style service
with other signatures than the examples:
- to create a correct wsdd for message-style services
- to create a client
The Axis call.invoke method always receives an Object type as response no
matter what the return type
In addition I have to notice that in the latest release a DocumentSerializer
is added, I need to upgrade!
r
remko de knikker wrote:
I had two difficulties when I was trying to create a message style
service with other signatures than the examples:
- to create a correct wsdd
I saw the new version has the DocumentSerializer added, try again...
r
Jim Poulsen wrote:
A guy just responded to your post on the newsgroup.
It appears that he also is only able to make the public Element[]
evaluate(Element[]) type method work in the axis framework. There is also a
very good
I have a running service on Axis 1_1RC2
(which has a Document method(Document doc) signature, in doc/literal
message-style ws )
in order to test out if the new version Axis_1_1final works 'purer' with
the added org.apache.axis.encoding.ser.DocumentSerializer
instead of having to use the
to the faults accordingly.
Anne
-
Original Message -
From:
remko de knikker
To:
[EMAIL PROTECTED]
Sent:
Friday, June 27, 2003 1:31 PM
Subject:
Re: Exception handling strategy question
Situation:
OK
t. I could be wrong but it seems like soap fault should only be
thrown
if there was a conformance issue. Someone please correct me if I am wrong.
--George
-Original Message-----
From: remko de knikker [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 24, 2003 3:22 PM
To: [EMAIL
of your exceptions, and then
tell Axis to map the exceptions to the faults accordingly.
Anne
-
Original Message -
From:
remkode knikker
To:
[EMAIL PROTECTED]
Sent:
Friday, June 27, 2003 1:31 PM
Subject:
Re: Exception
I included in my wsdd the wsdlInputSchema which includes my own inputmessage's schema, but it seems as if axis changes the name of the request messsage
and defines its own input schema regardless/or on top of my self defined one?? It now points to the axis generated inputSchema of
I am using the WsdlInputSchema tag in the wsdd file:
eg.
parameter name="wsdlInputSchema" value="your_url/your_schema.xsd"/
This will include the schema in the generated wsdl from the ?wsdl-query.
I just haven't figured out how to include both input and output schema's.
Does anyone know?
1. How about all the rest of your service, is that all working fine?
2. Did you follow the deployment steps using
java org.apache.axis.client.AdminClient deploymentfile.wsdd
?
r
Sochea Meas (LMC) wrote:
automatic wsdl generation
Hi all,
When I append "?wsdl"
privyet,
I am creating a SOAPFault element within the body to return. Then it is up to the user/client to do some error-handling.
You can call MessageContext and .getBody().
Look also into customizing Handlers perhaps, I haven't looked into this too much yet.
r
List: axis-user
Subject:
Send a message to
[EMAIL PROTECTED]
Dariusz Blada wrote:
Hello,
Do you know how can I unsubscribe from [EMAIL PROTECTED] mailling list
please help
Dariusz
30 matches
Mail list logo