You can also specify the methods to expose,
using the -m option.
Tony
Tim K. wrote on 01/12/2004 19:21:04:
Vy Ho wrote:
I wonder if you declare an interface for this service, then use
it to
generate wsdl.
This shields you from how you implement your service.
Right, that's the
Hello all,
one year ago we have developed a web service that has a few parameters,
one of which is a byte[]. At that time this parameter was used to get a
binary file (for example midi or gif) with size up to 150 KB (max). We
have had excellent results, both in terms of reliability and speed.
Nige White wrote:
Will the Axis HTTP client classes follow redirects?
No it doesn't! It just throws a (301)Moved Permanently error.
This means standard, generated Axis clients won't be able to use our
Soap server. The programmers of the client will have to modify the
BindingStub class do the
Have you thought about SOAP headers? The
first response could include a header giving a new URL for subsequent calls.
On the client, a handler could check for the header and, if present, store
the value as the endpoint address. You could probably work out how to then
modify the Service object or
[EMAIL PROTECTED] wrote:
Have you thought about SOAP headers? The
first response could include a header giving a new URL for subsequent
calls.
On the client, a handler could check for the header and, if present,
store
the value as the endpoint address. You could probably work out how to
Nige,
As an FYI ...
Another way to accomplish dynamic endpoints would be to use a UDDI (e.g.
jUDDI), and have the client locate services using a standard interface.
Tom Gordon
Nige White wrote:
[EMAIL PROTECTED] wrote:
Have you thought about SOAP headers? The first response could include
a
TMG wrote:
Nige,
As an FYI ...
Another way to accomplish dynamic endpoints would be to use a UDDI
(e.g. jUDDI), and have the client locate services using a standard
interface.
Woah!! I've just mastered the complexities of a Soap envelope and soap
encoding serialization/deserialization. I'm
At the moment, I am developing a program which consist of Web services.
This program is started by one managing Java application.
Then ,these Webservies call to each other and repeat treating received data
until these finish process.
Data sent and received Web service to Webservie are
Nige,
Axis supports handlers that can get at the SOAP request and response on
the way out and on the way back. It supports this on the client and server
sides. You just have to configure the client and server side WSDD files
and supply classes for the handlers. Axis calls the invoke method of
After some more thoughts it looks that we are not doing buffered I/O
while reading the attachment from disk. As suggested in many places (for
example
http://java.sun.com/docs/books/performance/1st_edition/html/JPIOPerformance.fm.html)
I/O operations in java are by default unbuffered.
Shame on
hey,
I guess this is the most looked for topic in the list. I 've gone through
all the posting and I still am not able to solve this issue. Am deploying
my service in Tomcat. My wsdd looks like this
deployment xmlns=http://xml.apache.org/axis/wsdd/;
Hi all
I'm using AXIS in closed pure Java system, and it seems for us a
combination of dynamic invocation and the DoAutoTypes property in
TypeMappingImpl might make the use of Web Services very easy.
However, the property is defaulted to false, and I can't see the
approved way to set it.
There
Patrick,
As i mentioned in the bug report, i need to know that it works at
least for a specific use case / test scenario before letting it in.
Here's how we can tackle this:
Step #1: Get latest CVS, make the fix as suggested in the bug report.
Step #2: come up with a sample web service and
Hi, I hope you can provide some ideas or direct me to some tutorials, examples, etc. to helpexplain how to create a simple web service that receives SOAP requests over SMTP to call a remote procedure. My problem isI have only 2 weeks to write and test this, soif possible, I hopesomebody candirect
Which in effect does the same thing, it creates an interface for you
with only those methods, right?
Personally I prefer defining the interface myself rather than doing it
via command line options, you get more compile time checking and catch
mistakes early than deal with sometimes obscure
Thanks dims
I'm more than happy to do this: just some more questions.
[i] Is there a deadline I need to work to?
[ii]I currently only need to use Call.invoke() to make the calls on
the client - is this enough?
[iii] I currently only use JWS to expose web services - is this
enough?
[iv]
Any thoughts on this? has anyone been successful in getting this to work?
Thanks, David
David Robison wrote:
I have a web service that provides both web pages via a servlet and
also SOAP services. I use basic authentication for the web pages and
that works fine. I want the SOAP services to use
Nige,
UDDIs are there own topic, so I don't want to clutter this list.
To get started, take a look at:
http://www.uddi.org/
http://ws.apache.org/juddi
The Apache jUDDI project has its own mailing list, etc... if you go down
that path.
Tom Gordon
Nige White wrote:
TMG wrote:
Nige,
As an FYI ...
[i] as soon as you can (3-5 days?)
[ii] Yep
[iii] Yep
[iv] Yep
Thanks,
dims
On Thu, 2 Dec 2004 17:51:24 -, Patrick Martin
[EMAIL PROTECTED] wrote:
Thanks dims
I'm more than happy to do this: just some more questions.
[i] Is there a deadline I need to work to?
[ii]I currently
hey folks,
I think I know what the problem is. Its the URLClassLoader. My service
method does the following
Class.forName(...ApiResponse, urlClassLoader);
where urlClassLoader has been instantiated with a set of URL's to look for
the classes. The service method uses the above to create the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am using Axis 1.2RC2 and I have a function:
public byte[] lookupSelectLocationsString(Item input)
~From the wsdl file I have this:
wsdl:message name=lookupSelectLocationsStringResponse
wsdl:part name=result type=xsd:byte/
/wsdl:message
This is
Hi,
I'm running the test cases generated by WSDL2JAVA on some document style
web services and have been getting some no operation errors that directly
relate to the use of namespace prefixes in related SOAP messages. When I
run my test case the SOAP message generated by Axis is:
Hi,
We are looking into implementing validation on rpc/encoded messages. It
seems that mapping the schema in a WSDL file to an XML schema for the
SOAP message (when the operation uses SOAP encoding) and then validating
the message with the schema is one approach. Has anyone transformed
SOAP
I solved my own problem. In the web-resource-collection I needed to
add a url-pattern for my SOAP service. I also hade to modify the
handler
type=java:org.apache.axis.handlers.SimpleAuthorizationHandler/ to
define allowByDefault: as
handler
I'm using WSDL2Java to create a service consumed by a .NET client I can't
change for a WSDL we're mandated to use. It has a service called GetService
defined as follows in the WSDL (details omitted):
complexType name=ArrayOfstring
complexContent
restriction base=SOAP-ENC:Array
Hi folks,
Iam still grappling with my problem, not yet solved.
The web service is rightly deployed but on running the
client, i keep on getting simpledeserializer error
thrown by the server! Any ideas where i might have
totally mesed up?
Here is how it looks:
My company is trying to make the product more scalable. We
are using Apache Soap right now. So, we are considering migrating from Soap to
Axis as one of the important sources to enhance the scalability/performance of
the product.
Can anyone provide any official documentation on how
Pramodh Peddi wrote:
My company is trying to make the product more scalable. We are using
Apache Soap right now. So, we are considering migrating from Soap to
Axis as one of the important sources to enhance the
scalability/performance of the product.
I am not comparing apache soap to axis
Hi Luc,
I just tested with timeout set to -1, but it throws out runtime exception:
'timeout can't be negative'.
Do you know any other way to set no timeout for the client request?
Thanks,
Georgia
-Original Message-
From: Bernolet, Luc [PRDBE Extern] [mailto:[EMAIL PROTECTED]
Sent:
Set it to 0
-Original Message-
From: Zhou Jian Han [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 02, 2004 3:54 PM
To: [EMAIL PROTECTED]
Subject: RE: Connection Timeout
Hi Luc,
I just tested with timeout set to -1, but it throws out
runtime exception: 'timeout can't be
Sorry, misleading header, I was talking about WSDL2Java. Also, I noticed that
the other server returns type as xsd:string[8] and Axis returns it as
soapenc:string[8]. Is that related? Please help. -- Andy
[EMAIL PROTECTED] 12/02/04 03:23PM
I'm using WSDL2Java to create a service consumed by a
Yes, .NET doesn't support the soap encoding types. This seems to be a
feature of axis 1.2, there was talk on the axis-dev list of changing
this back to match axis 1.1, but I don't know what the current status of
that is.
Cheers
Simon
-Original Message-
From: ANDREW MICONE
Should be fixed in latest CVS.
-- dims
On Thu, 2 Dec 2004 16:11:13 -0800, Simon Fell [EMAIL PROTECTED] wrote:
Yes, .NET doesn't support the soap encoding types. This seems to be a
feature of axis 1.2, there was talk on the axis-dev list of changing
this back to match axis 1.1, but I don't
Great! That clears it up. Unfortunately I can't get a clean compile out of the
latest CVS checkout. Inbetween the warnings about enum and deprecation warnings
(yes, yikes, JDK1.5). I get the following errors. Any advice on how to get just
WSDL2Java compiled?
[javac]
Ok...I answered my own question and switched back to JDK1.2_04 to compile and
that works, but the strings are still soap encoded when I run the client, and
therefore incompatible with .NET. Any hints? Has it just not been checked in
yet?
Also, is axis-ant.jar no longer part of the build or is
Georgia,
Sorry: it should be 0 (not -1).
Luc.
-Original Message-
From: Zhou Jian Han [mailto:[EMAIL PROTECTED]
Sent: vrijdag 3 december 2004 00:54
To: [EMAIL PROTECTED]
Subject: RE: Connection Timeout
Hi Luc,
I just tested with timeout set to -1, but it throws out runtime exception:
On deployment of the latest-greatest CVS daily of Axis from tomcat, the
following error appears. If you look in axis.jar you find that the class is
indeed not in there. A problem with the build or a problem with the code? I see
the source in the java directory but I don't see a class file in
Fixed my own problem again. I'm learning more about ant files every day. Steps
to compile for other newbies in pain:
1) Switch to J2EE 1.4.2_04 SDK instead of 1.5
2) Make sure tomcat's servlet api jar is in the CLASSPATH.
3) Make sure activation.jar and mail.jar is in WEB-INF/lib
4) Make sure
38 matches
Mail list logo
