Title: Message
Even
for an existing project that you want to expose as a web service, you can still
create a separate interface for it that is different than the interface or
classes that are used elsewhere. In the web service I created, I used this
method. The original code had a huge class
Title: Message
If you
are going to trick java2wsdl into using the State class, then you might as well
return a State object from getState(), since that kinda defeats the purpose of
returning an interface in the first place, right?
I see
alot of questions on this list where someone is tryin
Here is a repost of my answer to the first question:
According to the user guide:
"Write and compile a Java interface (or class) that describes the web
service interface. Note: If you compile your class with debug information,
Java2WSDL will use the debug information to obtain the method parameter
r structure for
this specific purpose.
Mayur
--- Bill Werth <[EMAIL PROTECTED]> wrote:
> Why not just create an interface for the Web service
> something like:
>
> public interface EchoBase64 {
> public void echo(String name, int[] data);
> }
>
> Run Java2WSDL
Why not just create an interface for the Web service something like:
public interface EchoBase64 {
public void echo(String name, int[] data);
}
Run Java2WSDL to create your WSDL based on this interface. If you want to
echo more than one, just make multiple calls. You don't really need a
s
That is a great article. It is the one I used to get started. It is only
missing how to setup Axis and what you need to do to set the classpath
correctly to compile your interface before generating the WSDL file.
-Original Message-
From: Meloro, John [mailto:[EMAIL PROTECTED]
Sent: Tuesday
Thanks. I'll keep that in mind if we go to production code with this.
Although none of the links below seem to explain how to set up using https
without setting the url in the WSDL file. Being somewhat green in how Tomcat
works, "You can make any Web service available on https based only on
config
Yes, that is what I did. You need to create a new WSDL file that has the
https endpoint url. I created my WSDL with Java2WSDL, so I only changed the
-l parameter to the new url. Be sure that you use the same server name as
will be used when you create the SSL certificate which now will be required
g command to deploy the webserivce but the WSDL output
was the same as before...
java org.apache.axis.client.AdminClient deploy.wsdd -l
http://x.y.z:8080/myWebApplication/servlet/AxisServlet -ddd
any clues or suggestions??
Thanks a lot for quick responses.
Bill Werth <[EMAIL PROTECTED]&
r suggestions??
Thanks a lot for quick responses.
Bill Werth <[EMAIL PROTECTED]> wrote:
>According to the user guide:
>"Write and compile a Java interface (or class) that describes the web
>service interface. Note: If you compile your class with debug information,
>Java
According to the user guide:
"Write and compile a Java interface (or class) that describes the web
service interface. Note: If you compile your class with debug information,
Java2WSDL will use the debug information to obtain the method parameter
names. Use the Java2WSDL tool to create a WSDL file f
I'm fairly new to
Web services, but I'm wondering if this could have something to do with
it:
The user manual says
that the Standard mappings from WSDL to Java is:
xsd:dateTime
java.util.Calendar
So it looks like you
could resolve the problem by using the Calendar class i
PROTECTED]Sent: Friday, July 02, 2004 9:33
AMTo: [EMAIL PROTECTED]Subject: RE: Method
parameter names not appearing in WSDL
Is
the java file a class or interface? Param names only work for classes
and not interfaces.
-Original Message-From: Bill Werth
[mailto:[EMAIL
I've spent a few
hours going through the archive and reading the user guide.
I've seen posts
about this, but nothing seems to work. When I create the WSDL from a java
file, the method parameters are named In0, In1, In2, instead of something like
UserID, Password, etc.
I have a file named
14 matches
Mail list logo
