Well, there are errors in the originally generated WSDL-- The type
definitions are defined as SOAP Encoding types (tns2 namespace) rather
than XSD types (default namespace), and I suspect that .NET would barf
on these types.
I can't tell you why RC3 is generating the funky > values for the
attribu
Nevermind on this. Copy/Paste error I finally found! :(
- Original Message -
From: "Hollywood" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, February 19, 2005 9:30 AM
Subject: Java2WSDL ant task
> I have the following snippet in my build.xml file:
>
>
>
>
>
>
>
>
I have the following snippet in my build.xml file:
However, it claims it can not find the class file to generate the WSDL from.
Anyone have any thoughts?
Thanks!
Hello,
I'm generating a fairly simple web service in Axis 1.2RC2 (I've tried RC3
too) running under Tomcat 5.0X and Sun Java JRE1.5 which looks as follows:
public interface SAPSync
{
public String syncType1(String sData);
public String syncType2(String sData);
}
I apply the Java2WSDL too
Hello,
I'm generating a fairly simple web service in Axis 1.2RC2 (I've tried RC3
too) running under Tomcat 5.0X and Sun Java JRE1.5 which looks as follows:
public interface SAPSync
{
public String syncType1(String sData);
public String syncType2(String sData);
}
I apply the Java2WSDL too
Hello,
I want to develop a ServiceHandler, which get the ResponseEndpoint(the
endpoint of the client) from the incomming SOAPMessage. Is this possible,
and if yes, would you tell me, how can I do this?
Thank You
tish
Arcor-DSL: die echte Flatrate für alle Bandbreiten. Jetzt ohne Einrichtu
