Re: [Axis2][0.94] How can i shutdown connection after call

[Saminda Abeyruwan]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Forwarded with Axis2 prefix;

Filipp Akinfiev wrote:
> Hi all,
> in my client class  i have function like :
>   public TFileSendResponse storeFile(int type, String fileName, String 
> pathToFile) {
>   TFileSendResponse response = null;
>   try {
>   response = FileSend.response(makeCall(FileSend.request(new 
> TFileSend("", 
> "", type, fileName, pathToFile)), "storeFile"));  
>   } catch (Exception e) {
>   e.printStackTrace();
>   }
>   return response;
>   }
> 
> it's call function makeCall:
> 
> private MessageContext makeCall(MessageContext requestContext, String 
> action) {
>   ServiceClient client;
>   MessageContext result = null;
>   try {
>   // creating the Service
>   AxisService service = new AxisService("IXMLWS2");
> 
>   // creating the operations
>   AxisOperation operation = new OutInAxisOperation();
>   operation.setName(new 
> javax.xml.namespace.QName("urn:XMLWSIntf-IXMLWS", action));
>   service.addOperation(operation);
>   client = new ServiceClient(new 
> ConfigurationContextFactory().createConfigurationContextFromFileSystem(AXIS2_HOME),
>  
> service);
>   client.getOptions().setTo(targetEPR);
>   client.getOptions().setSoapAction("urn:XMLWSIntf2-IXMLWS2#" + 
> action);
>   client.getOptions().setExceptionToBeThrownOnSOAPFault(true);
>   
> client.getOptions().setTransportInProtocol(Constants.TRANSPORT_TCP);
>   
> client.getOptions().setProperty(org.apache.axis2.context.MessageContextConstants.CHUNKED,org.apache.axis2.Constants.VALUE_FALSE);
>   
> client.getOptions().setProperty(Constants.Configuration.ENABLE_MTOM, 
> Constants.VALUE_TRUE);
> 
>   OperationClient opClient = client.createClient(new 
> javax.xml.namespace.QName("urn:XMLWSIntf-IXMLWS", action));
> 
>   opClient.addMessageContext(requestContext);
>   opClient.execute(true);
>
>   return 
> opClient.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);
>   } catch (AxisFault e) {
>   e.printStackTrace();
>   }
>   return result;
> }
> 
> after execute, i have open connection to axis server, how can i terminate it ?
> 
> thanks in advance!
> 

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEF6MSYmklbLuW6wYRAlTGAJ4n3SH1JWxetBKHCEKQrrElU6mSDgCfeWfo
dmgUxQMXh+WqSEftnO+OGJ8=
=jW7k
-END PGP SIGNATURE-

Re: failure when trying to build axis2

[Ajith Ranabahu]

Hi,
Did you guys update the build files. The mentioned jars are not
available anymore and the dependencies have been modified. Please get
the latest update from SVN.

Ajith

On 3/15/06, Sricharan Anand <[EMAIL PROTECTED]> wrote:
> I am also getting the same error. Any clues?
>
> Thanks,
> Sricharan
>
> Loreno Oliveira <[EMAIL PROTECTED]> wrote:
>  Hi,
>
> when I try to build the axis source I got the following problem:
>
> +
> | Executing multiproject:install-callback Apache Axis 2.0 - WSDL
> | Memory: 8M/11M
> +
> Attempting to download XmlSchema-SNAPSHOT.jar.
> Response content length is not known
> Response content length is not known
> Response content length is not known
> Response content length is not known
> WARNING: Failed to download XmlSchema-SNAPSHOT.jar.
> Attempting to download ws-policy-SNAPSHOT.jar.
> Response content length is not known
> Response content length is not known
> Response content length is not known
> Response content length is no t known
> WARNING: Failed to download ws-policy-SNAPSHOT.jar.
>
> BUILD FAILED
> File.. C:\Documents and Settings\Loreno
> Oliveira\.maven\cache\maven-multiproject-plugin-1.3.1\plugin.jelly
> Element... maven:reactor
>  Line.. 217
> Column 9
> The build cannot continue because of the following unsatisfied dependencies:
>
> XmlSchema-SNAPSHOT.jar
> ws-policy-SNAPSHOT.jar
>
> Total time: 1 minutes 34 seconds
> Finished at: Mon Mar 13 15:08:23 BRT 2006
>
> C:\axis2-src>
>
> Does anybody knows why these two jars are not being downloaded??
>
> Thanks in advance..
>
> Loreno
>
>
>
>  
>  Yahoo! Mail
>  Use Photomail to share photos without annoying attachments.
>
>


--
Ajith Ranabahu

RE: How to use "long" for parameter type?

[Alick Buckley]

Title: RE: How to use "long" for parameter type?






Vartan,


You could look for all axis.jar files ( and other axis jar files - wsdl4j-15.1.jar, etc.. )


org.apache.axis.wsdl.Java2WSDL class is in axis.jar


The classes are dated 5/10/2005 5:23 PM


Also the generated WSDL has the build date.


 


-Original Message-
From: Rhimbo [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 15 March 2006 3:12 PM
To: axis-user@ws.apache.org
Subject: RE: How to use "long" for parameter type?



Alick,


Thanks much.  It still fails for me.  Very strange.  


I deleted all of my files except my original interface definition, 
Family.java and my FamilyImpl.java, which is the implementation code. 


I'm wondering if I have some incompatible libraries in my 
Tomcat/AXIS installation for two reasons:


1. You get it to work; I can't.
2. Trying the -y wrapped or --style wrapped makes Java2WSDL die
   a dramatic death.


Is there any way to figure out which version of the Java2WSDL
class file I have (something like a "-version" option)?  


Vartan




--- Alick Buckley <[EMAIL PROTECTED]> wrote:


> 
> Hi Vartan,
> 
> I have had no problems with long parameters using RPC or Wrapped style.
> 
> I did a quick test using my wizard and the Axis 1.3 generated WSDL is
> ok.
> 
> See attached FamilyServer.wsdl
> 
>

> ==
> 
> package com.acme.service.soap ;
> 
> public interface FamilyServerProvider
> {
> public int register ( String in0, String in1, long in2, String in3
> ) ;
> }
> 
>

> ==
> 
> package com.acme.service.soap ;
> 
> public class FamilyServerProviderStub implements FamilyServerProvider
> {
> /*
> Service implementation
> */
> 
> public final int register ( String in0, String in1, long in2,
> String in3
> )
> {
> return 0 ;
> }
> }
> 
>

> ==
> Create WSDL from source started
> 
> java
> -classpath
>
"C:\Studio_Beta\workspace\SOAP-GENERAL\solutions\FamilyServer\soap-compile"
> "-Djava.ext.dirs=C:\Studio_Beta\lib\ext;"
> org.apache.axis.wsdl.Java2WSDL
> -l
> http://www.acme.com/cgi-bin/jsmdirect?myservice
> -o
>
C:\Studio_Beta\workspace\SOAP-GENERAL\solutions\FamilyServer\FamilyServerSer
> vice.wsdl
> -b
> FamilyServerServiceBinding
> -S
> FamilyServerServiceService
> -s
> FamilyServerServicePort
> -P
> FamilyServerServicePortType
> -y
> RPC
> -u
> ENCODED
> -T
> 1.2
> -A
> OPERATION
> -i
> com.acme.service.soap.FamilyServerProviderStub
> com.acme.service.soap.FamilyServerProvider
> 
> Create WSDL from source completed
> 
>

> ==
> 
> 
> 
> -Original Message-
> From: Rhimbo [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, 15 March 2006 1:56 PM
> To: Axis users
> Subject: How to use "long" for parameter type?
> 
> 
> Hi folks,
> 
> Tomcat 5.5.15, AXIS 1.3, Linux fedora core 4
> 
> Java2WSDL does not generate the correct method signature in the 
> *SoapBindingImpl.java file.  Here is the scenario.
> 
> I have the following method declaration in my Family.java file, which
> defines one interface.
> 
> public interface Family 
> {
>   public int register(String email, 
>         String password, 
>         long birthDate, 
>         String affiliateName)
>   throws RemoteException;
> 
> ...
> }
> 
> I execute:
> 
> $ java org.apache.axis.wsdl.Java2WSDL -o family.wsdl \
>   -l"http://localhost:8080/axis/services/family-accounts" \
>   -n urn:family-accounts \
>   -p"family-accounts" urn:disney.dis.family \
>   disney.dis.family.Family 
> 
> to produce the family.wsdl file, which I've attached to this email.
> 
> 
> I execute:
> 
> $ 
> $ java org.apache.axis.wsdl.WSDL2Java -o . -d Session -s \
>   -p disney.dis.family family.wsdl
> 
> to produce the auto-generated files.  The file that contains the
> SOAP binding implementation has the following signature
> corresponding to the interface method declaration above:
> 
> public int register(java.lang.String in0, 
> java.lang.String in1, 
>  java.lang.String in2) 
>  throws java.rmi.RemoteException 
> {
> return -3;
> }
> 
> It should be like this:
> 
> public int register(java.lang.String in0, 
> java.lang.String in1, 
> long in2,
> java.lang.String in3) 
>  throws java.rmi.RemoteException 
> {
> return -3;
> }
> 
> 
> Can anyone tell me what's wrong?  How can I specify "long" 
> type parameters?
> 
> Many thanks,
> 
> Vartan
> 
> __
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> 
> 

Re: How to use "long" for parameter type?

[Dies Koper]

Vartan,
Could you try explicitly setting the classpath (with your classes in front)?
Also, make sure there are no old compiled generated classes in your 
classpath.


Can you reproduce it with only that method in your interface? (without 
isRegistered and login)?


Regards,
Dies


Rhimbo wrote:

Alick,

Thanks much.  It still fails for me.  Very strange.  

I deleted all of my files except my original interface definition, 
Family.java and my FamilyImpl.java, which is the implementation code. 

I'm wondering if I have some incompatible libraries in my 
Tomcat/AXIS installation for two reasons:


1. You get it to work; I can't.
2. Trying the -y wrapped or --style wrapped makes Java2WSDL die
   a dramatic death.

Is there any way to figure out which version of the Java2WSDL
class file I have (something like a "-version" option)?  


Vartan



--- Alick Buckley <[EMAIL PROTECTED]> wrote:


Hi Vartan,

I have had no problems with long parameters using RPC or Wrapped style.

I did a quick test using my wizard and the Axis 1.3 generated WSDL is
ok.

See attached FamilyServer.wsdl





==

package com.acme.service.soap ;

public interface FamilyServerProvider
{
public int register ( String in0, String in1, long in2, String in3
) ;
}





==

package com.acme.service.soap ;

public class FamilyServerProviderStub implements FamilyServerProvider
{
/*
Service implementation
*/

public final int register ( String in0, String in1, long in2,
String in3
)
{
return 0 ;
}
}





==
Create WSDL from source started

java
-classpath


"C:\Studio_Beta\workspace\SOAP-GENERAL\solutions\FamilyServer\soap-compile"

"-Djava.ext.dirs=C:\Studio_Beta\lib\ext;"
org.apache.axis.wsdl.Java2WSDL
-l
http://www.acme.com/cgi-bin/jsmdirect?myservice
-o


C:\Studio_Beta\workspace\SOAP-GENERAL\solutions\FamilyServer\FamilyServerSer

vice.wsdl
-b
FamilyServerServiceBinding
-S
FamilyServerServiceService
-s
FamilyServerServicePort
-P
FamilyServerServicePortType
-y
RPC
-u
ENCODED
-T
1.2
-A
OPERATION
-i
com.acme.service.soap.FamilyServerProviderStub
com.acme.service.soap.FamilyServerProvider

Create WSDL from source completed





==



-Original Message-
From: Rhimbo [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 15 March 2006 1:56 PM
To: Axis users
Subject: How to use "long" for parameter type?


Hi folks,

Tomcat 5.5.15, AXIS 1.3, Linux fedora core 4

Java2WSDL does not generate the correct method signature in the 
*SoapBindingImpl.java file.  Here is the scenario.


I have the following method declaration in my Family.java file, which
defines one interface.

public interface Family 
{
  public int register(String email, 
		  String password, 
		  long birthDate, 
		  String affiliateName)

  throws RemoteException;

...
}

I execute:

$ java org.apache.axis.wsdl.Java2WSDL -o family.wsdl \
  -l"http://localhost:8080/axis/services/family-accounts"; \
  -n urn:family-accounts \
  -p"family-accounts" urn:disney.dis.family \
  disney.dis.family.Family 


to produce the family.wsdl file, which I've attached to this email.


I execute:

$ 
$ java org.apache.axis.wsdl.WSDL2Java -o . -d Session -s \

  -p disney.dis.family family.wsdl

to produce the auto-generated files.  The file that contains the
SOAP binding implementation has the following signature
corresponding to the interface method declaration above:

public int register(java.lang.String in0, 
java.lang.String in1, 
 java.lang.String in2) 
 throws java.rmi.RemoteException 
{

return -3;
}

It should be like this:

public int register(java.lang.String in0, 
java.lang.String in1, 
long in2,
java.lang.String in3) 
 throws java.rmi.RemoteException 
{

return -3;
}


Can anyone tell me what's wrong?  How can I specify "long" 
type parameters?


Many thanks,

Vartan

Re: [Axis2] WSDL2Java client code creation

[Ajith Ranabahu]

Hi all,
This prefix in targetNamepace attribute issue was reported to us
earlier but we could not recreate it. My guess is that it arises in a
particular JDK/OS combination and we need to recreate it so that we
can fix it. Details of your environment would be very helpful to us in
doing so.
BTW thanks Anne for pointing out the issues. We'll fix the WSDL
generation bugs soon (if they are still there) and logging a Jira
issue would be helpful in keeping track of it.

Ajith

On 3/15/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
> If Axis2 generated that WSDL, then you should log a bug in Jira -- make sure
> you're using the latest build, though. I recall a bug like this in 0.94,
> which I'm pretty sure has been fixed now.
>
> Anne
>
>
>  On 3/14/06, Sebastian J. Schultheiss <[EMAIL PROTECTED]> wrote:
> > Hi Anne!
> >
> > Thanks a lot for your comments. We just used the WSDL of our class that
> was
> > generated by AXIS itself. After uploading the class we downloaded the WSDL
> and
> > without modifying it in any way we wanted to use it as input for the
> WSDL2Java
> > client code creation tool. We weren't aware that AXIS creates faulty
> WSDLs.
> > We'll check out the corrections you suggested and get back tomorrow.
> >
> > Thanks again!
> >
> > -- Sebi
> >
> > Anne Thomas Manes wrote:
> > > The targetNamespace problem is caused by the fact that you specified:
> > >
> > > ns2:targetNamespace="http://org.apache.axis2/xsd";
> > >
> > > Rather than:
> > >
> > > targetNamespace="http://org.apache.axis2/xsd";
> > >
> > > Schema attributes must not be namespace qualified.(I also strongly
> recommend
> > > that you get in the habit of using more descriptive namespaces -- use a
> name
> > > that indicates the nature of the service, and preferably unique to your
> > > organization.)
> > > Likewise you need to remove the namespace prefix from the following
> > > attributes in the  definition:
> > >
> > >   ns1:elementFormDefault="qualified"
> > >   ns0:attributeFormDefault="unqualified"
> > >
> > > As well as all the attributes within the rest of the schema, e.g., this:
> > >
> > > 
> > >   
> > > 
> > >xmlns:ns1="http://www.w3.org/2001/XMLSchema "
> > > ns0:name="param0" ns1:type="xs:anyType"/>
> > > 
> > >   
> > > 
> > >
> > > Should be:
> > >
> > > 
> > >   
> > > 
> > >   
> > > 
> > >   
> > > 
> > >
> > > By the way, You find things work much better when you use defined types
> > > rather than "xs:anyType".
> > >
> > > Based on a quick glance through the rest of the WSDL, I didn't see any
> > > glaring errors, except that you must remove the namespace attributes
> from
> > > the  definitions. e.g.; this:
> > >
> > > http://www.org.apache.axis2"/>
> > >
> > > should be this:
> > >
> > > 
> > >
> > > (You use the namespace attribute only when using "rpc" style.)
> > >
> > > Anne
> > >
> > > On 3/14/06, robert lazarski <[EMAIL PROTECTED]> wrote:
> > >> The attached file is neither vaild xml or valid wsdl. Try using an xml
> > >> editor - I use kxmleditor on linux - and get the file to at least load.
> From
> > >> there - try getting the wsdl to validate via an wsdl validator (can't
> > >> recommend one at the moment, sorry).
> > >>
> > >> HTH,
> > >> Robert
> > >> http://www.braziloutsource.com/
> > >>
> > >>
> > >> On 3/14/06, Sebastian J. Schultheiss < [EMAIL PROTECTED]> wrote:
> > >>> Hi all,
> > >>>
> > >>> we are playing around with the samples from the tutorial... we have
> > >>> extended the
> > >>> MyService to take a comlpexType (a string, an int and a double) and
> > >>> would like
> > >>> to create the client from the WSDL.
> > >>>
> > >>> Axis has created the attached WSDL from our service, but WSDL2Java
> fails
> > >>> when
> > >>> called like this:
> > >>> ---
> > >>> axis2/bin# WSDL2Java -uri ..\samples\MyService.wsdl -o ..\samples\src
> -p
> > >>> org.apache.axis2
> > >>> -
> > >>>
> > >>> with this error:
> > >>> --
> > >>> Exception in thread "main"
> > >>> org.apache.axis2.wsdl.codegen.CodeGenerationException
> > >>> :
> org.apache.axis2.wsdl.codegen.CodeGenerationException :
> Invalid WSDL:
> > >>> The WSDL
> > >>> Types Schema does not define a targetNamespace in file:../samples/
> > >>> at
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate
> > >>> (CodeGener
> > >>> ationEngine.java:118)
> > >>> at
> org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:31)
> > >>> at
> org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java :21)
> > >>> Caused by:
> org.apache.axis2.wsdl.codegen.CodeGenerationException:
> > >>> Invalid WSDL:
> > >>> The WSDL Types Schema does not define a targetNamespace in
> > >>> file:../samples/
> > >>> at
> > >>>
> org.apache.axis2.wsdl.codegen.extension.WSDLValidatorExtension.engage
> > >>> (WSDLValidatorExtension.java:70)
> > >>> at
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate
> > >>> (CodeGener
> > >>> ationEngine.java

Re: WSDL2Java and Java2WSDL

[Dies Koper]

If it is just the namespace -> Java package mapping you are concerned 
about, try the following options:


-N, --NStoPkg =
   mapping of namespace to package

-p, --PkgtoNS =
   package=namespace, name value pairs


Siddhartha Subramanian wrote:

Well I understand the changes and the need for them, but once my WSDL
has been published and the clients using it expect the client side to be
in a certain way (packaging wise, namespaces etc.) but with 1.3 I cannot
say regenerate the WSDL and publish it because what you are suggesting
of generating the code from the new WSDL does not produce the same
client side stubs expected. So we have to manipulate the WSDL by hand to
conform to the namespacing and there by producing the old packaging
structure. 




From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, March 14, 2006 6:32 PM

To: axis-user@ws.apache.org
Subject: Re: WSDL2Java and Java2WSDL

 


One way to ensure that your WSDLs are the same is to generate your code
from the WSDL rather than vice versa. 


But most likely, your Axis 1.1 WSDL will produce interoperability
errors. If they contain arrays, they probably have errors. Axis 1.2 and
later releases added support for JAX-RPC 1.1 and the WS-I Basic Profile,
and they dramatically improved support for document/literal. Lots and
lots of changes were made in dealing with arrays.

Anne

On 3/14/06, Siddhartha Subramanian <[EMAIL PROTECTED]>
wrote:

I have been trying something using 1.1 final and 1.3 WSDL2Java and
Java2WSDL produces different types of WSDLs with the Java2WSDL and
WSDL2Java produces different java packaging with the different versions.

Can anyone tell me why the change and what changed between 1.1 and 1.3?
I believe there is no way to generate the same WSDL as the 1.1 final
produced with the 1.3 version. Am I wrong with this statement?

 





--
Dies KOPER <[EMAIL PROTECTED]> (changed on 1 July 2005)
Fujitsu Ltd - MWPF1  (changed from MWPF3 on 21 Nov 2005)
2-15-16, Shin-Yokohama, Kouhoku-ku, Yokohama, 222-0033, Japan
Tel. +81(45)-475-5605  (internal 7181-4217)

RE: How to use "long" for parameter type?

[Rhimbo]

Alick,

Thanks much.  It still fails for me.  Very strange.  

I deleted all of my files except my original interface definition, 
Family.java and my FamilyImpl.java, which is the implementation code. 

I'm wondering if I have some incompatible libraries in my 
Tomcat/AXIS installation for two reasons:

1. You get it to work; I can't.
2. Trying the -y wrapped or --style wrapped makes Java2WSDL die
   a dramatic death.

Is there any way to figure out which version of the Java2WSDL
class file I have (something like a "-version" option)?  

Vartan



--- Alick Buckley <[EMAIL PROTECTED]> wrote:

> 
> Hi Vartan,
> 
> I have had no problems with long parameters using RPC or Wrapped style.
> 
> I did a quick test using my wizard and the Axis 1.3 generated WSDL is
> ok.
> 
> See attached FamilyServer.wsdl
> 
>

> ==
> 
> package com.acme.service.soap ;
> 
> public interface FamilyServerProvider
> {
> public int register ( String in0, String in1, long in2, String in3
> ) ;
> }
> 
>

> ==
> 
> package com.acme.service.soap ;
> 
> public class FamilyServerProviderStub implements FamilyServerProvider
> {
> /*
> Service implementation
> */
> 
> public final int register ( String in0, String in1, long in2,
> String in3
> )
> {
> return 0 ;
> }
> }
> 
>

> ==
> Create WSDL from source started
> 
> java
> -classpath
>
"C:\Studio_Beta\workspace\SOAP-GENERAL\solutions\FamilyServer\soap-compile"
> "-Djava.ext.dirs=C:\Studio_Beta\lib\ext;"
> org.apache.axis.wsdl.Java2WSDL
> -l
> http://www.acme.com/cgi-bin/jsmdirect?myservice
> -o
>
C:\Studio_Beta\workspace\SOAP-GENERAL\solutions\FamilyServer\FamilyServerSer
> vice.wsdl
> -b
> FamilyServerServiceBinding
> -S
> FamilyServerServiceService
> -s
> FamilyServerServicePort
> -P
> FamilyServerServicePortType
> -y
> RPC
> -u
> ENCODED
> -T
> 1.2
> -A
> OPERATION
> -i
> com.acme.service.soap.FamilyServerProviderStub
> com.acme.service.soap.FamilyServerProvider
> 
> Create WSDL from source completed
> 
>

> ==
> 
> 
> 
> -Original Message-
> From: Rhimbo [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 15 March 2006 1:56 PM
> To: Axis users
> Subject: How to use "long" for parameter type?
> 
> 
> Hi folks,
> 
> Tomcat 5.5.15, AXIS 1.3, Linux fedora core 4
> 
> Java2WSDL does not generate the correct method signature in the 
> *SoapBindingImpl.java file.  Here is the scenario.
> 
> I have the following method declaration in my Family.java file, which
> defines one interface.
> 
> public interface Family 
> {
>   public int register(String email, 
> String password, 
> long birthDate, 
> String affiliateName)
>   throws RemoteException;
> 
> ...
> }
> 
> I execute:
> 
> $ java org.apache.axis.wsdl.Java2WSDL -o family.wsdl \
>   -l"http://localhost:8080/axis/services/family-accounts"; \
>   -n urn:family-accounts \
>   -p"family-accounts" urn:disney.dis.family \
>   disney.dis.family.Family 
> 
> to produce the family.wsdl file, which I've attached to this email.
> 
> 
> I execute:
> 
> $ 
> $ java org.apache.axis.wsdl.WSDL2Java -o . -d Session -s \
>   -p disney.dis.family family.wsdl
> 
> to produce the auto-generated files.  The file that contains the
> SOAP binding implementation has the following signature
> corresponding to the interface method declaration above:
> 
> public int register(java.lang.String in0, 
> java.lang.String in1, 
>  java.lang.String in2) 
>  throws java.rmi.RemoteException 
> {
> return -3;
> }
> 
> It should be like this:
> 
> public int register(java.lang.String in0, 
> java.lang.String in1, 
> long in2,
> java.lang.String in3) 
>  throws java.rmi.RemoteException 
> {
> return -3;
> }
> 
> 
> Can anyone tell me what's wrong?  How can I specify "long" 
> type parameters?
> 
> Many thanks,
> 
> Vartan
> 
> __
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> 
> 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: How to use "long" for parameter type?

[Rhimbo]

Hmm, now I'm really confused.  :-)

I went to look up the command line args to try setting style to 
"wrapped". 

I did

$ java org.apache.axis.wsdl.Java2WSDL -h

and got this (abbreviated) output.

   -y, --style 
The style of binding in the WSDL, either DOCUMENT, RPC, 
or WRAPPED.

So I added this to my Java2WSDL command

$ java org.apache.axis.wsdl.Java2WSDL -o family.wsdl \
  -l"http://localhost:8080/axis/services/family-accounts"; \
  -n urn:family-accounts \
  -p"family-accounts" urn:disney.dis.family \
  --style wrapped  disney.dis.family.Family

I also tried the
   -y wrapped

option.  I got the following trace back spit back at me!!  
If I remove the 
   --style wrapped 

option it completes without error (but still the parameter
problem).  

Might I have a bad version of Java2WSDL?  Any ideas?  





AxisFault
 faultCode: {http://xml.apache.org/axis/}Server.generalException
 faultSubcode:
 faultString: Attempted to write duplicate schema element :
{urn:family-accounts}isRegistered
 faultActor:
 faultNode:
 faultDetail:
{http://xml.apache.org/axis/}stackTrace:Attempted to write
duplicate schema element : {urn:family-accounts}isRegistered
at
org.apache.axis.wsdl.fromJava.Types.writeSchemaElementDecl(Types.java:865)
at
org.apache.axis.wsdl.fromJava.Types.writeWrapperElement(Types.java:566)
at
org.apache.axis.wsdl.fromJava.Emitter.writeWrapperPart(Emitter.java:1651)
at
org.apache.axis.wsdl.fromJava.Emitter.writeRequestMessage(Emitter.java:1467)
at
org.apache.axis.wsdl.fromJava.Emitter.writeMessages(Emitter.java:1106)
at
org.apache.axis.wsdl.fromJava.Emitter.writePortType(Emitter.java:1075)
at
org.apache.axis.wsdl.fromJava.Emitter.getWSDL(Emitter.java:484)
at org.apache.axis.wsdl.fromJava.Emitter.emit(Emitter.java:331)
at org.apache.axis.wsdl.fromJava.Emitter.emit(Emitter.java:430)
at org.apache.axis.wsdl.Java2WSDL.run(Java2WSDL.java:588)
at org.apache.axis.wsdl.Java2WSDL.main(Java2WSDL.java:682)

{http://xml.apache.org/axis/}hostname:NH-VPIROUMI-DT1

Attempted to write duplicate schema element :
{urn:family-accounts}isRegistered
at
org.apache.axis.wsdl.fromJava.Types.writeSchemaElementDecl(Types.java:865)
at
org.apache.axis.wsdl.fromJava.Types.writeWrapperElement(Types.java:566)
at
org.apache.axis.wsdl.fromJava.Emitter.writeWrapperPart(Emitter.java:1651)
at
org.apache.axis.wsdl.fromJava.Emitter.writeRequestMessage(Emitter.java:1467)
at
org.apache.axis.wsdl.fromJava.Emitter.writeMessages(Emitter.java:1106)
at
org.apache.axis.wsdl.fromJava.Emitter.writePortType(Emitter.java:1075)
at
org.apache.axis.wsdl.fromJava.Emitter.getWSDL(Emitter.java:484)
at org.apache.axis.wsdl.fromJava.Emitter.emit(Emitter.java:331)
at org.apache.axis.wsdl.fromJava.Emitter.emit(Emitter.java:430)
at org.apache.axis.wsdl.Java2WSDL.run(Java2WSDL.java:588)
at org.apache.axis.wsdl.Java2WSDL.main(Java2WSDL.java:682)
$








--- Anne Thomas Manes <[EMAIL PROTECTED]> wrote:

> Is there a reason why you have to use rpc/encoded?
> Try generating style="wrapped" and see if that fixes the problem.
> 
> Anne
> 
> On 3/14/06, Rhimbo <[EMAIL PROTECTED]> wrote:
> >
> > Hi folks,
> >
> > Tomcat 5.5.15, AXIS 1.3, Linux fedora core 4
> >
> > Java2WSDL does not generate the correct method signature in the
> > *SoapBindingImpl.java file.  Here is the scenario.
> >
> > I have the following method declaration in my Family.java file, which
> > defines one interface.
> >
> > public interface Family
> > {
> >   public int register(String email,
> >   String password,
> >   long birthDate,
> >   String affiliateName)
> >   throws RemoteException;
> >
> > ...
> > }
> >
> > I execute:
> >
> > $ java org.apache.axis.wsdl.Java2WSDL -o family.wsdl \
> >   -l"http://localhost:8080/axis/services/family-accounts"; \
> >   -n urn:family-accounts \
> >   -p"family-accounts" urn:disney.dis.family \
> >   disney.dis.family.Family
> >
> > to produce the family.wsdl file, which I've attached to this email.
> >
> >
> > I execute:
> >
> > $
> > $ java org.apache.axis.wsdl.WSDL2Java -o . -d Session -s \
> >   -p disney.dis.family family.wsdl
> >
> > to produce the auto-generated files.  The file that contains the
> > SOAP binding implementation has the following signature
> > corresponding to the interface method declaration above:
> >
> > public int register(java.lang.String in0,
> > java.lang.String in1,
> >  java.lang.String in2)
> >  throws java.rmi.RemoteException
> > {
> > return -3;
> > }
> >
> > It should be like this:
> >
> > public int register(java.lang.String in0,
> > java.lang.String in1,
> > long in2,
> > java.lang.String in3)
> >

RE: WSDL2Java and Java2WSDL

[Siddhartha Subramanian]

What I meant to say was that I would have expected Axis to be
backward compatible with older versions











From: Subramanian,
Siddhartha [RICH1:B630:EXCH] 
Sent: Tuesday, March 14, 2006 9:22
PM
To: axis-user@ws.apache.org
Subject: RE: WSDL2Java and
Java2WSDL



 



Well I understand the changes and the need for them, but once
my WSDL has been published and the clients using it expect the client side to
be in a certain way (packaging wise, namespaces etc.) but with 1.3 I cannot say
regenerate the WSDL and publish it because what you are suggesting of
generating the code from the new WSDL does not produce the same client side
stubs expected. So we have to manipulate the WSDL by hand to conform to the
namespacing and there by producing the old packaging structure. 











From: Anne Thomas Manes
[mailto:[EMAIL PROTECTED] 
Sent: Tuesday, March 14, 2006 6:32
PM
To: axis-user@ws.apache.org
Subject: Re: WSDL2Java and
Java2WSDL



 

One way to ensure that your WSDLs
are the same is to generate your code from the WSDL rather than vice versa. 

But most likely, your Axis 1.1 WSDL will produce interoperability errors. If
they contain arrays, they probably have errors. Axis 1.2 and later releases
added support for JAX-RPC 1.1 and the WS-I Basic Profile, and they dramatically
improved support for document/literal. Lots and lots of changes were made in
dealing with arrays.

Anne



On 3/14/06, Siddhartha Subramanian <[EMAIL PROTECTED]>
wrote:

I have been trying something using 1.1 final and 1.3
WSDL2Java and
Java2WSDL produces different types of WSDLs with the Java2WSDL and
WSDL2Java produces different java packaging with the different versions.

Can anyone tell me why the change and what changed between 1.1 and 1.3?
I believe there is no way to generate the same WSDL as the 1.1 final
produced with the 1.3 version. Am I wrong with this statement?



 

RE: WSDL2Java and Java2WSDL

[Siddhartha Subramanian]

Well I understand the changes and the need for them, but once
my WSDL has been published and the clients using it expect the client side to
be in a certain way (packaging wise, namespaces etc.) but with 1.3 I cannot say
regenerate the WSDL and publish it because what you are suggesting of
generating the code from the new WSDL does not produce the same client side stubs
expected. So we have to manipulate the WSDL by hand to conform to the
namespacing and there by producing the old packaging structure. 











From: Anne Thomas Manes
[mailto:[EMAIL PROTECTED] 
Sent: Tuesday, March 14, 2006 6:32
PM
To: axis-user@ws.apache.org
Subject: Re: WSDL2Java and
Java2WSDL



 

One way to ensure that your WSDLs
are the same is to generate your code from the WSDL rather than vice versa. 

But most likely, your Axis 1.1 WSDL will produce interoperability errors. If
they contain arrays, they probably have errors. Axis 1.2 and later releases
added support for JAX-RPC 1.1 and the WS-I Basic Profile, and they dramatically
improved support for document/literal. Lots and lots of changes were made in
dealing with arrays.

Anne



On 3/14/06, Siddhartha Subramanian <[EMAIL PROTECTED]>
wrote:

I have been trying something using 1.1 final and 1.3
WSDL2Java and
Java2WSDL produces different types of WSDLs with the Java2WSDL and
WSDL2Java produces different java packaging with the different versions.

Can anyone tell me why the change and what changed between 1.1 and 1.3?
I believe there is no way to generate the same WSDL as the 1.1 final
produced with the 1.3 version. Am I wrong with this statement?



 

RE: How to use "long" for parameter type?

[Alick Buckley]

Title: RE: How to use "long" for parameter type?






Hi Vartan,


I have had no problems with long parameters using RPC or Wrapped style.


I did a quick test using my wizard and the Axis 1.3 generated WSDL is ok.


See attached FamilyServer.wsdl


==


package com.acme.service.soap ;


public interface FamilyServerProvider
{
    public int register ( String in0, String in1, long in2, String in3 ) ;
}


==


package com.acme.service.soap ;


public class FamilyServerProviderStub implements FamilyServerProvider
{
    /*
    Service implementation
    */


    public final int register ( String in0, String in1, long in2, String in3 )
    {
    return 0 ;
    }
}


==
Create WSDL from source started


java
-classpath
"C:\Studio_Beta\workspace\SOAP-GENERAL\solutions\FamilyServer\soap-compile"
"-Djava.ext.dirs=C:\Studio_Beta\lib\ext;"
org.apache.axis.wsdl.Java2WSDL
-l
http://www.acme.com/cgi-bin/jsmdirect?myservice
-o
C:\Studio_Beta\workspace\SOAP-GENERAL\solutions\FamilyServer\FamilyServerService.wsdl
-b
FamilyServerServiceBinding
-S
FamilyServerServiceService
-s
FamilyServerServicePort
-P
FamilyServerServicePortType
-y
RPC
-u
ENCODED
-T
1.2
-A
OPERATION
-i
com.acme.service.soap.FamilyServerProviderStub
com.acme.service.soap.FamilyServerProvider


Create WSDL from source completed


==




-Original Message-
From: Rhimbo [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 15 March 2006 1:56 PM
To: Axis users
Subject: How to use "long" for parameter type?



Hi folks,


Tomcat 5.5.15, AXIS 1.3, Linux fedora core 4


Java2WSDL does not generate the correct method signature in the 
*SoapBindingImpl.java file.  Here is the scenario.


I have the following method declaration in my Family.java file, which
defines one interface.


public interface Family 
{
  public int register(String email, 
          String password, 
          long birthDate, 
          String affiliateName)
  throws RemoteException;


...
}


I execute:


$ java org.apache.axis.wsdl.Java2WSDL -o family.wsdl \
  -l"http://localhost:8080/axis/services/family-accounts" \
  -n urn:family-accounts \
  -p"family-accounts" urn:disney.dis.family \
  disney.dis.family.Family 


to produce the family.wsdl file, which I've attached to this email.



I execute:


$ 
$ java org.apache.axis.wsdl.WSDL2Java -o . -d Session -s \
  -p disney.dis.family family.wsdl


to produce the auto-generated files.  The file that contains the
SOAP binding implementation has the following signature
corresponding to the interface method declaration above:


    public int register(java.lang.String in0, 
    java.lang.String in1, 
 java.lang.String in2) 
 throws java.rmi.RemoteException 
    {
    return -3;
    }


It should be like this:


    public int register(java.lang.String in0, 
    java.lang.String in1, 
    long in2,
    java.lang.String in3) 
 throws java.rmi.RemoteException 
    {
    return -3;
    }



Can anyone tell me what's wrong?  How can I specify "long" 
type parameters?


Many thanks,


Vartan


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


 




FamilyServerService.wsdl
Description: Binary data


Wizard.gif
Description: GIF image

Re: How to use "long" for parameter type?

[Anne Thomas Manes]

Is there a reason why you have to use rpc/encoded?Try generating style="wrapped" and see if that fixes the problem.AnneOn 3/14/06, Rhimbo
 <[EMAIL PROTECTED]> wrote:Hi folks,
Tomcat 5.5.15, AXIS 1.3, Linux fedora core 4Java2WSDL does not generate the correct method signature in the*SoapBindingImpl.java file.  Here is the scenario.I have the following method declaration in my 
Family.java file, whichdefines one interface.public interface Family{  public int register(String email,  String password,  long birthDate,  String affiliateName)
  throws RemoteException;...}I execute:$ java org.apache.axis.wsdl.Java2WSDL -o family.wsdl \  -l"http://localhost:8080/axis/services/family-accounts
" \  -n urn:family-accounts \  -p"family-accounts" urn:disney.dis.family \  disney.dis.family.Familyto produce the family.wsdl file, which I've attached to this email.I execute:
$$ java org.apache.axis.wsdl.WSDL2Java -o . -d Session -s \  -p disney.dis.family family.wsdlto produce the auto-generated files.  The file that contains theSOAP binding implementation has the following signature
corresponding to the interface method declaration above:public int register(java.lang.String in0,java.lang.String in1, java.lang.String in2) throws 
java.rmi.RemoteException{return -3;}It should be like this:public int register(java.lang.String in0,java.lang.String in1,long in2,
java.lang.String in3) throws java.rmi.RemoteException{return -3;}Can anyone tell me what's wrong?  How can I specify "long"
type parameters?Many thanks,Vartan__Do You Yahoo!?Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

How to use "long" for parameter type?

[Rhimbo]

Hi folks,

Tomcat 5.5.15, AXIS 1.3, Linux fedora core 4

Java2WSDL does not generate the correct method signature in the 
*SoapBindingImpl.java file.  Here is the scenario.

I have the following method declaration in my Family.java file, which
defines one interface.

public interface Family 
{
  public int register(String email, 
  String password, 
  long birthDate, 
  String affiliateName)
  throws RemoteException;

...
}

I execute:

$ java org.apache.axis.wsdl.Java2WSDL -o family.wsdl \
  -l"http://localhost:8080/axis/services/family-accounts"; \
  -n urn:family-accounts \
  -p"family-accounts" urn:disney.dis.family \
  disney.dis.family.Family 

to produce the family.wsdl file, which I've attached to this email.


I execute:

$ 
$ java org.apache.axis.wsdl.WSDL2Java -o . -d Session -s \
  -p disney.dis.family family.wsdl

to produce the auto-generated files.  The file that contains the
SOAP binding implementation has the following signature
corresponding to the interface method declaration above:

public int register(java.lang.String in0, 
java.lang.String in1, 
 java.lang.String in2) 
 throws java.rmi.RemoteException 
{
return -3;
}

It should be like this:

public int register(java.lang.String in0, 
java.lang.String in1, 
long in2,
java.lang.String in3) 
 throws java.rmi.RemoteException 
{
return -3;
}


Can anyone tell me what's wrong?  How can I specify "long" 
type parameters?

Many thanks,

Vartan

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

family.wsdl
Description: 105362022-family.wsdl

Re: failure when trying to build axis2

[Sricharan Anand]

I am also getting the same error. Any clues?Thanks,SricharanLoreno Oliveira <[EMAIL PROTECTED]> wrote: Hi,when I try to build the axis source I got the following problem:+| Executing multiproject:install-callback Apache Axis 2.0 - WSDL| Memory: 8M/11M+ Attempting to download XmlSchema-SNAPSHOT.jar.Response content length is not knownResponse content length is not knownResponse content length is not knownResponse content length is not knownWARNING: Failed to download  XmlSchema-SNAPSHOT.jar.Attempting to download ws-policy-SNAPSHOT.jar.Response content length is not knownResponse content length is not knownResponse content length is not knownResponse content length is no
 t known
 WARNING: Failed to download ws-policy-SNAPSHOT.jar.BUILD FAILEDFile.. C:\Documents and Settings\Loreno Oliveira\.maven\cache\maven-multiproject-plugin-1.3.1\plugin.jellyElement... maven:reactor Line.. 217Column 9The build cannot continue because of the following unsatisfied dependencies:XmlSchema-SNAPSHOT.jarws-policy-SNAPSHOT.jarTotal time: 1 minutes 34 secondsFinished at: Mon Mar 13 15:08:23 BRT 2006 C:\axis2-src>Does anybody knows why these two jars are not being downloaded??Thanks in advance..Loreno 
		 Yahoo! Mail 
Use Photomail to share photos without annoying attachments.

Re: WSDL2Java and SimpleType doing *strange* things.

[Dies Koper]

Hello Scott,

Why not not use the ?wsdl generated wsdl?
(i.e. specify the original one in the WSDD instead)

Regards,
Dies


Scott McCoy wrote:

When given the declaration...



  




  



WSDL2Java generates a Bean class that has a get_value (named after the
internal _value a less complex type declaration has?) and set_value method
for accessing the value, but when deployed Axis outputs a wsdl that has an
*attribute* named _value for the keyword complexType.

When given










WSDL2Java generates exactly what I expect, but then when deployed axis
returns a wsdl that contains:



  




  



How do I get WSDL2Java to do what I want?  Heh.  I'd prefer to my markup to
look like:

The
Keyword

But having an attribute named value containing the keyword is a close runner
up in perferred behaviors.

Thanks,
Scott S. McCoy

Re: [axis2 v0.95] code generation exception

[Diego]

Hi Robert,

thanks a lot for your help!

That's the ant task that I've executed:



 
  
  
  
  
  
  
 



and that's the wsdl:



http://astrodas.org/ws/peer";
xmlns:tns="http://astrodas.org/ws/peer";
   xmlns:tns1="http://astrodas.org/ws/model";
   xmlns:tns2="http://www.ivoa.net/xml/VOTable/v1.1";
   xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
   xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>

 
  targetNamespace="http://astrodas.org/ws/model";>

   http://www.w3.org/2001/XMLSchema"; />
   http://www.ivoa.net/xml/VOTable/v1.1"; 
schemaLocation="http://www.ivoa.net/xml/VOTable/v1.1"; />

   
   

 type="xsd:integer" />
 type="xsd:integer" />
 type="xsd:string" />
 type="xsd:boolean" />


   
   

 type="xsd:integer" />
 type="xsd:string" />
 type="xsd:string" />
 type="xsd:string" />


   
   

 
  
   name="external-object" type="tns1:external-object" />
   type="xsd:string" />
   name="reliability" type="xsd:float" />
   type="xsd:double" />
  type="xsd:double" />

  
 

   
   

 
  name="mapping-annotation" type="tns1:mapping-annotation" />

 

   
   

 
  type="xsd:int" />

 

   
   
   

 
  type="xsd:string" />

 

   
   

 
  
 

   
  
 

 
 
  
 
 
  
 
 
 
  
 
 
  element="tns1:executeGlobalMappingTableQueryResponse" />

 

 
  
   Stores an array of annotations in the annotation 
backend database

   
   
  
  
   Executes a query on the global mapping table of 
the p2p network of annotation

   
   message="tns:executeGlobalMappingTableQueryResponseMessage" />

  
 

 
  http://schemas.xmlsoap.org/soap/http"; 
style="document" />

  
   
   

   
   

   
  
  
   
   

   
   

   
  
 

 
  
   location="http://localhost:8080/axis2/services/astrodas-peer"; />

  
 




Thanks!

Diego


robert lazarski wrote:

Hi Diego,

Post your wsdl and command line options and perhaps we can help.

Robert
http://www.braziloutsource.com/

On 3/14/06, *Diego* <[EMAIL PROTECTED] > 
wrote:


Hi!

I have to generate code using org.apache.axis2.wsdl.WSDL2Code having in
input a wsdl where some web service return a votable.  The votable
schema is specified at the following address:

http://www.ivoa.net/xml/VOTable/v1.1

I've successfully executed wsdl2code with axis2 up to version 0.93.  Now
I'm using axis2 v0.94 and I have also checked out and build v0.95.  With
both these versions I get the following exception:

org.apache.axis2.wsdl.codegen.CodeGenerationException :
java.lang.RuntimeException: java.lang.RuntimeException: Schema for
namespace 'http://www.ivoa.net/xml/VOTable/v1.1' already contains type
'token
 at
org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:180)
 at org.apache.tools.ant.taskdefs.Java.run(Java.java:710)
 at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:178)
 at org.apache.tools.ant.taskdefs.Java.execute(Java.java:84)
 at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
 at org.apache.tools.ant.Task.perform(Task.java:364)
 at org.apache.tools.ant.Target.execute (Target.java:341)
 at org.apache.tools.ant.Target.performTasks(Target.java:369)
 at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
 at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets
(SingleCheckExecutor.java:37)
 at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
 at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
 at
org.apache.tools.ant.taskdefs.CallTarget.execute (CallTarget.java:107)
 at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
 at org.apache.tools.ant.Task.perform(Task.java:364)
 at org.apache.tools.ant.Target.execute(Target.java:341)
 at org.apache.tools.ant.Target.performTasks(Target.java:369)
 at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
 at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
 at

org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
 at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
 at org.apache.tools.ant.Main.runBuild(Main.java :668)
 at org.apache.tools.ant.Main.startAnt(Main.java:187)
 at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
 at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)

Thanks for any help!

Diego

Re: WSDL2Java and Java2WSDL

[Anne Thomas Manes]

One way to ensure that your WSDLs are the same is to generate your code from the WSDL rather than vice versa. But most likely, your Axis 1.1 WSDL will produce interoperability errors. If they contain arrays, they probably have errors. Axis 
1.2 and later releases added support for JAX-RPC 1.1 and the WS-I Basic Profile, and they dramatically improved support for document/literal. Lots and lots of changes were made in dealing with arrays.Anne
On 3/14/06, Siddhartha Subramanian <[EMAIL PROTECTED]> wrote:
I have been trying something using 1.1 final and 1.3 WSDL2Java andJava2WSDL produces different types of WSDLs with the Java2WSDL andWSDL2Java produces different java packaging with the different versions.Can anyone tell me why the change and what changed between 
1.1 and 1.3?I believe there is no way to generate the same WSDL as the 1.1 finalproduced with the 1.3 version. Am I wrong with this statement?

Re: java.lang.IllegalArgumentException

[Dies Koper]

Hello William,

I do not know the conditions for them to be generated, but generated 
Javabean classes often get helper methods such as:

- getTypeDesc
- getSerializer
- getDeserializer

WSDL2Java has an option to have these methods not inserted in the 
Javabean classes, but in separate files.


Either way, I think they are required in certain circumstances to 
serialize/deserialize SOAP messages correctly.


If you did not modify (overwrite them with your original, etc.) or 
forget to include them, then I suppose it's okay.


When happens if you put the JSP in a different Tomcat instance 
(different process) from the web service running in Axis?


Regards,
Dies

William Ward wrote:

Hello Dies,
  I didn't modify any of the classes generated by WSDL2Java, but
I don't see any helper methods in the generated client stubs, should I
be seeing these ??

Regards,
William 



-Original Message-
From: Dies Koper [mailto:[EMAIL PROTECTED] 
Sent: 14 March 2006 14:02

To: axis-user@ws.apache.org
Subject: Re: java.lang.IllegalArgumentException

Hello William,

We'd need to see the WSDL to see if the SOAP message is right.
Unfortunately the SOAP message is rather long and complicated. You might
not get any replies.

As you seem to use complex structures (array of complex types?) I
imagine the Axis engine relies on the Helper classes (or helper code in
the generated Javabeans) on the client side. Just checking, but you did
not happen to have removed these classes/methods?

Regards,
Dies


William Ward wrote:

Hello Dies,
  thank you for the reply, I used tcpmon to capture the SOAP 
message, I believe the problem is at the receiving end as I get the 
response back from the Web Service no problem, it looks like it has a 
problem de-serializing the response.


The odd thing is if I call the same Web Serice using just a test Java 
application, I don't see any exception on the Axis side It seems to be


just when I use JSP, Tomcat and Axis, I have tried just creating a 
simple JSP page that has the same code as the test Java Application, 
but I always get the Axis exception when using JSP & Tomcat, even 
though it is the same code & libraries for both applications


below is the SOAP request / response that I see using tcpmon :

Regards,
William

Re: Axis fault question

[Dies Koper]

Hello Charlton,

Can you confirm whether your method was actually entered?
Just to make sure the exception is not happening within your own code..

I am not familiar with Axis's logging functions, so I'd either use
Eclipse in debugging mode and make it stop when an
InvocationTargetException is generated, or try harder to figure out what
could cause such exception.
I believe an InvocationTargetException is generally thrown by the
Class.invoke method. This method would be used to either instantiate
your impl instance, a Javabean or user exception class, or to call a
method on it. You could put something in the default constructor of your
impl to check whether instantiation went successfully. Same for your
retrieve(String, String) method.

If your WSDL uses Doc/lit then we could check the elements in your
request are correct (could it be trying to call a non-existing method),
maybe compare them with what's in your WSDD.

Regards,
Dies

Charlton Jackson wrote:
> Hello Dies,
> 
> Thank you very much for your help.
> 
> You are correct, I misinterpreted some of my debugging output; I am
> hitting the server.  I took your suggestion and used tcpmon and see
> that the SOAP request is properly formed but the response is the
> InvocationTargetException mentioned previously.  I cranked the server
> logging up to 'DEBUG' but see nothing that would indicate a problem
> (it doesn't even tell me that a SOAP Fault was generated).  So, the
> server receives the request but faults before it's ever sent to my
> service.
> 
> Would you have any other suggestions as to things to try or approaches
> to further debug this problem?  (I've pasted the server log and tcpmon
> request/response below).  I'm stumped...
> 
> Thanks again,
> 
> Charlton
> 
> 
> Server log:
> DEBUG http-8080-Processor24 org.apache.commons.modeler.Registry - 
> Managed= Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1
> DEBUG http-8080-Processor24 org.apache.commons.modeler.Registry - 
> Managed= Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1
> DEBUG http-8080-Processor24 org.apache.commons.modeler.BaseModelMBean - 
> default constructor
> DEBUG http-8080-Processor24 org.apache.commons.modeler.BaseModelMBean - 
> default constructor
> DEBUG http-8080-Processor24 org.apache.commons.modeler.BaseModelMBean - 
> preRegister [EMAIL PROTECTED] 
> Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1
> DEBUG http-8080-Processor24 org.apache.commons.modeler.BaseModelMBean - 
> preRegister [EMAIL PROTECTED] 
> Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1
> DEBUG http-8080-Processor24 org.apache.coyote.tomcat5.MapperListener - 
> Handle Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1
> DEBUG http-8080-Processor24 org.apache.coyote.tomcat5.MapperListener - 
> Handle Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1
> DEBUG http-8080-Processor24 org.apache.coyote.tomcat5.MapperListener - 
> Handle Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1
> DEBUG http-8080-Processor24 org.apache.coyote.tomcat5.MapperListener - 
> Handle Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1
> DEBUG http-8080-Processor24 org.apache.tomcat.util.threads.ThreadPool - 
> Getting new thread data
> DEBUG http-8080-Processor24 org.apache.tomcat.util.threads.ThreadPool - 
> Getting new thread data
> DEBUG http-8080-Processor25 org.apache.catalina.core.StandardWrapper - 
> Allocating non-STM instance
> DEBUG http-8080-Processor25 org.apache.catalina.core.StandardWrapper - 
> Allocating non-STM instance
> DEBUG http-8080-Processor25 org.apache.catalina.core.StandardWrapper -   
> Returning non-STM instance
> DEBUG http-8080-Processor25 org.apache.catalina.core.StandardWrapper -   
> Returning non-STM instance
> 
> Request (from TCPMonitor):
> POST /axis/services/is HTTP/1.0
> Content-Type: text/xml; charset=utf-8
> Accept: application/soap+xml, application/dime, multipart/related, text/*
> User-Agent: Axis/1.1
> Host: 127.0.0.1
> Cache-Control: no-cache
> Pragma: no-cache
> SOAPAction: ""
> Content-Length: 518
> 
>  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; 
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> 
>   soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; 
> xmlns:ns1="urn:is">
>   c=us,o=company,ou=div,cn=principal1
>   urn:info:resource1
>  
> 
> 
> 
> Response (from TCPMonitor):
> HTTP/1.1 500 Internal Server Error
> Content-Type: text/xml;charset=utf-8
> Date: Tue, 14 Mar 2006 22:06:06 GMT
> Server: Apache-Coyote/1.1
> Connection: close
> 
>  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; 
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> 
>  
>   soapenv:Server.userException
>   java.lang.reflect.InvocationTargetException
>   
>  
> 
> 
> 
> 
>> From: Dies Koper <[EMAIL PROTECTED]>
>> Rep

Re: WSDL2Java and Java2WSDL

[Dies Koper]

Lots of things have been improved since Axis 1.1. The changes you see 
could either be because the generated files were improved to follow 
specifications (JAX-RPC 1.1 in particular), bugs were fixed, but also 
new bugs that were introduced.
Your questions are not easy to answer, as the changes were made over 
time by many people. Try having a look at release-notes.html and the 
svn/cvs logs if you are really interested.


Regards,
Dies


Siddhartha Subramanian wrote:

I have been trying something using 1.1 final and 1.3 WSDL2Java and
Java2WSDL produces different types of WSDLs with the Java2WSDL and
WSDL2Java produces different java packaging with the different versions.

Can anyone tell me why the change and what changed between 1.1 and 1.3?
I believe there is no way to generate the same WSDL as the 1.1 final
produced with the 1.3 version. Am I wrong with this statement?

Re: [Axis2] WSDL2Java client code creation

[Anne Thomas Manes]

If Axis2 generated that WSDL, then you should log a bug in Jira -- make sure you're using the latest build, though. I recall a bug like this in 0.94, which I'm pretty sure has been fixed now.Anne
On 3/14/06, Sebastian J. Schultheiss <[EMAIL PROTECTED]> wrote:
Hi Anne!Thanks a lot for your comments. We just used the WSDL of our class that wasgenerated by AXIS itself. After uploading the class we downloaded the WSDL andwithout modifying it in any way we wanted to use it as input for the WSDL2Java
client code creation tool. We weren't aware that AXIS creates faulty WSDLs.We'll check out the corrections you suggested and get back tomorrow.Thanks again!-- SebiAnne Thomas Manes wrote:
> The targetNamespace problem is caused by the fact that you specified:>> ns2:targetNamespace="http://org.apache.axis2/xsd">> Rather than:
>> targetNamespace="http://org.apache.axis2/xsd">> Schema attributes must not be namespace qualified.(I also strongly recommend> that you get in the habit of using more descriptive namespaces -- use a name
> that indicates the nature of the service, and preferably unique to your> organization.)> Likewise you need to remove the namespace prefix from the following> attributes in the  definition:
>>   ns1:elementFormDefault="qualified">   ns0:attributeFormDefault="unqualified">> As well as all the attributes within the rest of the schema, e.g., this:>
> >   > >   http://www.w3.org/2001/XMLSchema
"> ns0:name="param0" ns1:type="xs:anyType"/>> >   > >> Should be:>
> >   > >   > 
>   > >> By the way, You find things work much better when you use defined types> rather than "xs:anyType".>> Based on a quick glance through the rest of the WSDL, I didn't see any
> glaring errors, except that you must remove the namespace attributes from> the  definitions. e.g.; this:>> 
http://www.org.apache.axis2"/>>> should be this:>> >> (You use the namespace attribute only when using "rpc" style.)
>> Anne>> On 3/14/06, robert lazarski <[EMAIL PROTECTED]> wrote:>> The attached file is neither vaild xml or valid wsdl. Try using an xml
>> editor - I use kxmleditor on linux - and get the file to at least load. From>> there - try getting the wsdl to validate via an wsdl validator (can't>> recommend one at the moment, sorry).
 HTH,>> Robert>> http://www.braziloutsource.com/>> On 3/14/06, Sebastian J. Schultheiss < 
[EMAIL PROTECTED]> wrote:>>> Hi all,>> we are playing around with the samples from the tutorial... we have>>> extended the>>> MyService to take a comlpexType (a string, an int and a double) and
>>> would like>>> to create the client from the WSDL.>> Axis has created the attached WSDL from our service, but WSDL2Java fails>>> when>>> called like this:
>>> --->>> axis2/bin# WSDL2Java -uri ..\samples\MyService.wsdl -o ..\samples\src -p>>> org.apache.axis2>>> ->> with this error:
>>> -->>> Exception in thread "main">>> org.apache.axis2.wsdl.codegen.CodeGenerationException>>> : org.apache.axis2.wsdl.codegen.CodeGenerationException
: Invalid WSDL:>>> The WSDL>>> Types Schema does not define a targetNamespace in file:../samples/>>> at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate>>> (CodeGener
>>> ationEngine.java:118)>>> at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:31)>>> at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java :21)>>> Caused by: 
org.apache.axis2.wsdl.codegen.CodeGenerationException:>>> Invalid WSDL:>>> The WSDL Types Schema does not define a targetNamespace in>>> file:../samples/>>> at
>>> org.apache.axis2.wsdl.codegen.extension.WSDLValidatorExtension.engage>>> (WSDLValidatorExtension.java:70)>>> at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate
>>> (CodeGener>>> ationEngine.java:80)>>> ... 2 more> If we try to enter anything else in the targetNamespace attribute in the>>> WSDL,
>>> it gives us a NullPointerException instead.>> Any clues?>> Thanks a lot in advance!>> -- Sebi>>

Re: [Axis2] How to specifiy operation name

[Dong Liu]

You may need to use the tcp monitor or other tools to see the HTTP message. Cheers,DongOn 3/14/06, Michael Robinson <
[EMAIL PROTECTED]> wrote:













Thanks!!

 

One question though: 

 

    options.setSoapAction("actionName");

    options.setAction("actionName");

 

both fixed the problem. Is there a
difference? 

 

Thanks again for both replies. 

 

Michael 

Re: [Axis2] A question about asynchronous services and message queue

[Dong Liu]

I agree that Axis2 should be simple and lightweight, and just for soap processing. WS-RM does cover some of my requirements. However, I have a question in my mind about asynchronous "service" and "client" for a long time. As I know, the current implementation of async dual client in axis2 is to listen to a specific port, 6060 by default. That makes problem when running several async dual clients on the same machine at the same time. What I expect is to remove the difference between client and server so that all services can be accessed through the same port for a certain transportation, the http or tcp or JMS transportation components are always there listening, and the correlated service will be triggered based on ws-addressing. 
Cheers,DonOn 3/14/06, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote:
On Tue, 2006-03-14 at 10:59 -0600, Dong Liu wrote:> Maybe I should clarify my point here:>>  1. A service can support asynchronous communication with a> message queue stands before it, no matter whether or not this
> service is able to support asynchronous messaging by nature.>  2. It is hard for an asynchronous service to handle long-run> service requests without the support of a message queue and
> more important a persistence layer.> I am not sure if they are correct. Any comments?It seems to me that you're looking for WS-Reliable Messaging likefeatures. Have you looked at Sandesha2? That will give behavior you're
looking for.I think the core Axis2 platform should continue to have a simple,lightweight async model based purely on threads to cover simplepatterns. If you really need reliable, long running async behavior then
its time to use WS-RM.Sanjiva.

WS-Security UsernameToken Issue (WSS4J-based Java client vs. .NET server)

[Soactive Inc]

 Hi All,I am trying to access a .NET service with a Java/Axis client (using WSS4J) and am getting a security-related error. Here are the details:* Web Service: on .NET uses WS-Security UsernameToken (with Password Digest)
* Request Messagehttp://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="
http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">  http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">TestDev http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest" xmlns:wsse="
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">R7bh5dDlYgjCurx6Dwq9ki39lQg= http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">/tA24bdIc0uwX7euUqvMVQ== http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">2006-03-14T22:34:50.971Z  
[EMAIL PROTECTED]   * Response Message
http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance">   soapenv:FailedAuthentication The security token could not be authenticated or authorized 
http://ws.mycoservices.com/mycoEmailValidation/V2/EmailValidation.asmx  
Any inputs towards appropriately troubleshooting and resolving this issue would be appreciated.Regards.

Re: Axis fault question

[Charlton Jackson]

Hello Dies,

Thank you very much for your help.

You are correct, I misinterpreted some of my debugging output; I am
hitting the server.  I took your suggestion and used tcpmon and see
that the SOAP request is properly formed but the response is the
InvocationTargetException mentioned previously.  I cranked the server
logging up to 'DEBUG' but see nothing that would indicate a problem
(it doesn't even tell me that a SOAP Fault was generated).  So, the
server receives the request but faults before it's ever sent to my
service.

Would you have any other suggestions as to things to try or approaches
to further debug this problem?  (I've pasted the server log and tcpmon
request/response below).  I'm stumped...

Thanks again,

Charlton


Server log:
DEBUG http-8080-Processor24 org.apache.commons.modeler.Registry - Managed= 
Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1
DEBUG http-8080-Processor24 org.apache.commons.modeler.Registry - Managed= 
Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1
DEBUG http-8080-Processor24 org.apache.commons.modeler.BaseModelMBean - 
default constructor
DEBUG http-8080-Processor24 org.apache.commons.modeler.BaseModelMBean - 
default constructor
DEBUG http-8080-Processor24 org.apache.commons.modeler.BaseModelMBean - 
preRegister [EMAIL PROTECTED] 
Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1
DEBUG http-8080-Processor24 org.apache.commons.modeler.BaseModelMBean - 
preRegister [EMAIL PROTECTED] 
Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1
DEBUG http-8080-Processor24 org.apache.coyote.tomcat5.MapperListener - 
Handle Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1
DEBUG http-8080-Processor24 org.apache.coyote.tomcat5.MapperListener - 
Handle Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1
DEBUG http-8080-Processor24 org.apache.coyote.tomcat5.MapperListener - 
Handle Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1
DEBUG http-8080-Processor24 org.apache.coyote.tomcat5.MapperListener - 
Handle Catalina:type=RequestProcessor,worker=http-8080,name=HttpRequest1
DEBUG http-8080-Processor24 org.apache.tomcat.util.threads.ThreadPool - 
Getting new thread data
DEBUG http-8080-Processor24 org.apache.tomcat.util.threads.ThreadPool - 
Getting new thread data
DEBUG http-8080-Processor25 org.apache.catalina.core.StandardWrapper - 
Allocating non-STM instance
DEBUG http-8080-Processor25 org.apache.catalina.core.StandardWrapper - 
Allocating non-STM instance
DEBUG http-8080-Processor25 org.apache.catalina.core.StandardWrapper -   
Returning non-STM instance
DEBUG http-8080-Processor25 org.apache.catalina.core.StandardWrapper -   
Returning non-STM instance


Request (from TCPMonitor):
POST /axis/services/is HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/1.1
Host: 127.0.0.1
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: ""
Content-Length: 518

http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>


 soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; 
xmlns:ns1="urn:is">

  c=us,o=company,ou=div,cn=principal1
  urn:info:resource1
 



Response (from TCPMonitor):
HTTP/1.1 500 Internal Server Error
Content-Type: text/xml;charset=utf-8
Date: Tue, 14 Mar 2006 22:06:06 GMT
Server: Apache-Coyote/1.1
Connection: close

http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>


 
  soapenv:Server.userException
  java.lang.reflect.InvocationTargetException
  
 





From: Dies Koper <[EMAIL PROTECTED]>
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: Re: Axis fault question
Date: Sat, 11 Mar 2006 13:55:07 +0900

Hello Charlton,

Are you sure you are not hitting the server?
Judging from the stacktrace the stub send the request and got a
response. The response contained a fault: an InvocationTargetException
occurred at the server.
The server is the _Axis server_, it does not need to be your _service_.
In fact, InvocationTargetException probably means the Axis server could
not invoke the method on your service.
You can use tcpmon to confirm your request was send, SOAP message was
correct, and a response (the fault) came from the server, and not
happened in your stub.
To find out more details about why the InvocationTargetException
occurred, you'd have to check the server-side logs.

Regards,
Dies

Charlton Jackson wrote:
> I'm getting the fault below when running an Axis client.  Does anyone 
know

> what could be causing this, or have any ideas as to the kind of things I
> can
> try in an attempt to isolate the problem?  I'm not even hitting the 
server,

> so I'm confused why the client would be doing any deserialization (as
> evidenced by the stack trace) at this poi

Re: [axis2 v0.95] code generation exception

[robert lazarski]

Hi Diego, 


Post your wsdl and command line options and perhaps we can help.

Robert
http://www.braziloutsource.com/On 3/14/06, Diego <[EMAIL PROTECTED]
> wrote:Hi!I have to generate code using org.apache.axis2.wsdl.WSDL2Code
 having ininput a wsdl where some web service return a votable.  The votableschema is specified at the following address:http://www.ivoa.net/xml/VOTable/v1.1
I've successfully executed wsdl2code with axis2 up to version 0.93.  NowI'm using axis2 v0.94 and I have also checked out and build v0.95.  Withboth these versions I get the following exception:org.apache.axis2.wsdl.codegen.CodeGenerationException
:java.lang.RuntimeException: java.lang.RuntimeException: Schema fornamespace 'http://www.ivoa.net/xml/VOTable/v1.1' already contains type'token at
org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:180) at org.apache.tools.ant.taskdefs.Java.run(Java.java:710) at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:178) at 
org.apache.tools.ant.taskdefs.Java.execute(Java.java:84) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute
(Target.java:341) at org.apache.tools.ant.Target.performTasks(Target.java:369) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) atorg.apache.tools.ant.helper.SingleCheckExecutor.executeTargets
(SingleCheckExecutor.java:37) at org.apache.tools.ant.Project.executeTargets(Project.java:1068) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382) atorg.apache.tools.ant.taskdefs.CallTarget.execute
(CallTarget.java:107) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341)
 at org.apache.tools.ant.Target.performTasks(Target.java:369) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
 atorg.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40) at org.apache.tools.ant.Project.executeTargets(Project.java:1068) at org.apache.tools.ant.Main.runBuild(Main.java
:668) at org.apache.tools.ant.Main.startAnt(Main.java:187) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)Thanks for any help!
Diego

WSDL2Java and Java2WSDL

[Siddhartha Subramanian]

I have been trying something using 1.1 final and 1.3 WSDL2Java and
Java2WSDL produces different types of WSDLs with the Java2WSDL and
WSDL2Java produces different java packaging with the different versions.

Can anyone tell me why the change and what changed between 1.1 and 1.3?
I believe there is no way to generate the same WSDL as the 1.1 final
produced with the 1.3 version. Am I wrong with this statement?

Re: [Axis2] WSDL2Java client code creation

[Sebastian J. Schultheiss]

Hi Anne!

Thanks a lot for your comments. We just used the WSDL of our class that was
generated by AXIS itself. After uploading the class we downloaded the WSDL and
without modifying it in any way we wanted to use it as input for the WSDL2Java
client code creation tool. We weren't aware that AXIS creates faulty WSDLs.
We'll check out the corrections you suggested and get back tomorrow.

Thanks again!

-- Sebi

Anne Thomas Manes wrote:
> The targetNamespace problem is caused by the fact that you specified:
> 
> ns2:targetNamespace="http://org.apache.axis2/xsd";
> 
> Rather than:
> 
> targetNamespace="http://org.apache.axis2/xsd";
> 
> Schema attributes must not be namespace qualified.(I also strongly recommend
> that you get in the habit of using more descriptive namespaces -- use a name
> that indicates the nature of the service, and preferably unique to your
> organization.)
> Likewise you need to remove the namespace prefix from the following
> attributes in the  definition:
> 
>   ns1:elementFormDefault="qualified"
>   ns0:attributeFormDefault="unqualified"
> 
> As well as all the attributes within the rest of the schema, e.g., this:
> 
> 
>   
> 
>   http://www.w3.org/2001/XMLSchema";
> ns0:name="param0" ns1:type="xs:anyType"/>
> 
>   
> 
> 
> Should be:
> 
> 
>   
> 
>   
> 
>   
> 
> 
> By the way, You find things work much better when you use defined types
> rather than "xs:anyType".
> 
> Based on a quick glance through the rest of the WSDL, I didn't see any
> glaring errors, except that you must remove the namespace attributes from
> the  definitions. e.g.; this:
> 
> http://www.org.apache.axis2"/>
> 
> should be this:
> 
> 
> 
> (You use the namespace attribute only when using "rpc" style.)
> 
> Anne
> 
> On 3/14/06, robert lazarski <[EMAIL PROTECTED]> wrote:
>> The attached file is neither vaild xml or valid wsdl. Try using an xml
>> editor - I use kxmleditor on linux - and get the file to at least load. From
>> there - try getting the wsdl to validate via an wsdl validator (can't
>> recommend one at the moment, sorry).
>>
>> HTH,
>> Robert
>> http://www.braziloutsource.com/
>>
>>
>> On 3/14/06, Sebastian J. Schultheiss < [EMAIL PROTECTED]> wrote:
>>> Hi all,
>>>
>>> we are playing around with the samples from the tutorial... we have
>>> extended the
>>> MyService to take a comlpexType (a string, an int and a double) and
>>> would like
>>> to create the client from the WSDL.
>>>
>>> Axis has created the attached WSDL from our service, but WSDL2Java fails
>>> when
>>> called like this:
>>> ---
>>> axis2/bin# WSDL2Java -uri ..\samples\MyService.wsdl -o ..\samples\src -p
>>> org.apache.axis2
>>> -
>>>
>>> with this error:
>>> --
>>> Exception in thread "main"
>>> org.apache.axis2.wsdl.codegen.CodeGenerationException
>>> : org.apache.axis2.wsdl.codegen.CodeGenerationException: Invalid WSDL:
>>> The WSDL
>>> Types Schema does not define a targetNamespace in file:../samples/
>>> at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate
>>> (CodeGener
>>> ationEngine.java:118)
>>> at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:31)
>>> at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java :21)
>>> Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException:
>>> Invalid WSDL:
>>> The WSDL Types Schema does not define a targetNamespace in
>>> file:../samples/
>>> at
>>> org.apache.axis2.wsdl.codegen.extension.WSDLValidatorExtension.engage
>>> (WSDLValidatorExtension.java:70)
>>> at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate
>>> (CodeGener
>>> ationEngine.java:80)
>>> ... 2 more
>>>
>>>
>>> If we try to enter anything else in the targetNamespace attribute in the
>>> WSDL,
>>> it gives us a NullPointerException instead.
>>>
>>> Any clues?
>>>
>>> Thanks a lot in advance!
>>>
>>> -- Sebi
>>>
>>>
>>>
> 

[axis2 v0.95] code generation exception

[Diego]

Hi!

I have to generate code using org.apache.axis2.wsdl.WSDL2Code having in 
input a wsdl where some web service return a votable.  The votable 
schema is specified at the following address:


http://www.ivoa.net/xml/VOTable/v1.1

I've successfully executed wsdl2code with axis2 up to version 0.93.  Now 
I'm using axis2 v0.94 and I have also checked out and build v0.95.  With 
both these versions I get the following exception:


org.apache.axis2.wsdl.codegen.CodeGenerationException: 
java.lang.RuntimeException: java.lang.RuntimeException: Schema for 
namespace 'http://www.ivoa.net/xml/VOTable/v1.1' already contains type 
'token
at 
org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:180)

at org.apache.tools.ant.taskdefs.Java.run(Java.java:710)
at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:178)
at org.apache.tools.ant.taskdefs.Java.execute(Java.java:84)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at 
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:37)

at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
at 
org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:107)

at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at 
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)

at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.Main.runBuild(Main.java:668)
at org.apache.tools.ant.Main.startAnt(Main.java:187)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)

Thanks for any help!

Diego

Re: [Axis2] WSDL2Java client code creation

[Anne Thomas Manes]

The targetNamespace problem is caused by the fact that you specified:ns2:targetNamespace="http://org.apache.axis2/xsd"
Rather than:targetNamespace="http://org.apache.axis2/xsd"Schema attributes must not be namespace qualified.(I also strongly recommend that you get in the habit of using more
descriptive namespaces -- use a name that indicates the nature of the
service, and preferably unique to your organization.)Likewise you need to remove the namespace prefix from the following attributes in the  definition:
  ns1:elementFormDefault="qualified"   ns0:attributeFormDefault="unqualified"As well as all the attributes within the rest of the schema, e.g., this:
        http://www.w3.org/2001/XMLSchema
"        ns0:name="param0" ns1:type="xs:anyType"/>      Should be:

  
    
  
    
  
By the way, You find things work much better when you use defined types rather than "xs:anyType". Based on a quick glance through the rest of the WSDL, I didn't see any glaring errors, except that you must remove the namespace attributes from the  definitions. 
e.g.; this:http://www.org.apache.axis2"/>should be this:
(You use the namespace attribute only when using "rpc" style.)AnneOn 3/14/06, 
robert lazarski <[EMAIL PROTECTED]> wrote:
The attached file is neither vaild xml or valid wsdl. Try using an xml
editor - I use kxmleditor on linux - and get the file to at least load.
>From there - try getting the wsdl to validate via an wsdl validator
(can't recommend one at the moment, sorry). 

HTH,
Robert 
http://www.braziloutsource.com/
On 3/14/06, Sebastian J. Schultheiss <
[EMAIL PROTECTED]> wrote:Hi all,we are playing around with the samples from the tutorial... we have extended the
MyService to take a comlpexType (a string, an int and a double) and would liketo create the client from the WSDL.Axis has created the attached WSDL from our service, but WSDL2Java fails whencalled like this:
---axis2/bin# WSDL2Java -uri ..\samples\MyService.wsdl -o ..\samples\src -porg.apache.axis2-with this error:--Exception in thread "main" 
org.apache.axis2.wsdl.codegen.CodeGenerationException: org.apache.axis2.wsdl.codegen.CodeGenerationException: Invalid WSDL: The WSDLTypes Schema does not define a targetNamespace in file:../samples/at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:118)at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:31)at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java

:21)Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: Invalid WSDL:The WSDL Types Schema does not define a targetNamespace in file:../samples/at org.apache.axis2.wsdl.codegen.extension.WSDLValidatorExtension.engage

(WSDLValidatorExtension.java:70)at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:80)... 2 moreIf we try to enter anything else in the targetNamespace attribute in the WSDL,
it gives us a NullPointerException instead.Any clues?Thanks a lot in advance!-- Sebi

Axis2 version 1.0

[Brennan, Sean \(IMS\)]

Hey all,

Anybody have a general idea when version 1.0 will be released?

Thanks.
 
  


Information in this e-mail may be confidential. It is intended only for the 
addressee(s) identified above. If you are not the addressee(s), or an employee 
or agent of the addressee(s), please note that any dissemination, distribution, 
or copying of this communication is strictly prohibited. If you have received 
this e-mail in error, please notify the sender of the error.

Re: [Axis2] A question about asynchronous services and message queue

[Sanjiva Weerawarana]

On Tue, 2006-03-14 at 10:59 -0600, Dong Liu wrote:
> Maybe I should clarify my point here: 
> 
>  1. A service can support asynchronous communication with a
> message queue stands before it, no matter whether or not this
> service is able to support asynchronous messaging by nature.
>  2. It is hard for an asynchronous service to handle long-run
> service requests without the support of a message queue and
> more important a persistence layer. 
> I am not sure if they are correct. Any comments? 

It seems to me that you're looking for WS-Reliable Messaging like
features. Have you looked at Sandesha2? That will give behavior you're
looking for. 

I think the core Axis2 platform should continue to have a simple,
lightweight async model based purely on threads to cover simple
patterns. If you really need reliable, long running async behavior then
its time to use WS-RM.

Sanjiva.

Re: [Axis2] A question about asynchronous services and message queue

[Dong Liu]

Maybe I should clarify my point here: A service can support asynchronous communication with a message queue stands before it, no matter whether or not this service is able to support asynchronous messaging by nature.
It is hard for an asynchronous service to handle long-run service requests without the support of a message queue and more important a persistence layer. I am not sure if they are correct. Any comments? 
Cheers,DonOn 3/12/06, Dong Liu <[EMAIL PROTECTED]> wrote:
Hi, folks,When trying to deploy some async services to compare their performance to the sync ones, I realize that the async services make no sense with the support of a message queue. What is your idea? 
Cheers,
Don

Re: [Axis2] WSDL2Java client code creation

[robert lazarski]

The attached file is neither vaild xml or valid wsdl. Try using an xml
editor - I use kxmleditor on linux - and get the file to at least load.
>From there - try getting the wsdl to validate via an wsdl validator
(can't recommend one at the moment, sorry). 

HTH,
Robert 
http://www.braziloutsource.com/On 3/14/06, Sebastian J. Schultheiss <
[EMAIL PROTECTED]> wrote:Hi all,we are playing around with the samples from the tutorial... we have extended the
MyService to take a comlpexType (a string, an int and a double) and would liketo create the client from the WSDL.Axis has created the attached WSDL from our service, but WSDL2Java fails whencalled like this:
---axis2/bin# WSDL2Java -uri ..\samples\MyService.wsdl -o ..\samples\src -porg.apache.axis2-with this error:--Exception in thread "main" 
org.apache.axis2.wsdl.codegen.CodeGenerationException: org.apache.axis2.wsdl.codegen.CodeGenerationException: Invalid WSDL: The WSDLTypes Schema does not define a targetNamespace in file:../samples/at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:118)at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:31)at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java
:21)Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: Invalid WSDL:The WSDL Types Schema does not define a targetNamespace in file:../samples/at org.apache.axis2.wsdl.codegen.extension.WSDLValidatorExtension.engage
(WSDLValidatorExtension.java:70)at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:80)... 2 moreIf we try to enter anything else in the targetNamespace attribute in the WSDL,
it gives us a NullPointerException instead.Any clues?Thanks a lot in advance!-- Sebi

Re: null namespace generated for qualified elements

[Vikas Singh]

Anne,It worked after fixing the error i.e. tns:PutConfigRequest -> tns:PutSCIRequest  thank you,Vikas+Now, according to your WSDL, the child element of the SOAP Body should be
called cAnneOn 3/13/06, Vikas Singh <[EMAIL PROTECTED]> wrote:
Anne, Thanks for your help.I tried changes suggested by you but it did not work.WSDL file:

http://schemas.xmlsoap.org/wsdl/soap/"
	xmlns:tns="
http://myns/schemas/2006/02/26/sciwsdl"	xmlns:wsdl="
http://schemas.xmlsoap.org/wsdl/"	xmlns:xsd="
http://www.w3.org/2001/XMLSchema" name="NewWSDLFile"	targetNamespace="
http://myns/schemas/2006/02/26/sciwsdl"	xmlns:xsd1="

http://myns/schemas/2006/3/3/sci">		targetNamespace="
http://myns/schemas/2006/02/26/sciwsdl"			xmlns:scx="
http://myns/schemas/2006/3/3/sci"			elementFormDefault="qualified">			namespace="
http://myns/schemas/2006/3/3/sci"schemaLocation="
http://localhost:8080/jce/sci.xsd" />			

		
			
		

		

			
		transport="
http://schemas.xmlsoap.org/soap/http
" />	soapAction="
http://myns/schemas/2006/02/26/sciwsdl/putSCI
" />	
		
	name="config">
			location="http://localhost:8080/jce/services/config" />
			
Pre-serialization request body : 
http://myns/schemas/2006/02/26/sciwsdl
">http://myns/schemas/2006/3/3/sci/"	xmlns:thttp="

http://myns/schemas/2006/3/3/transport/http/" 	schemaLocation="http://localhost:8080/jce/sci.xsd
"	serviceGroup="travelDepartment">
		false
			true
			Post-serialization request body 

(in ) :
http://myns/schemas/2006/02/26/sciwsdl
">
http://localhost:8080/jce/sci.xsd"
serviceGroup="travelDepartment"
xmlns:scx="http://myns/schemas/2006/3/3/sci/"
xmlns:thttp="http://myns/schemas/2006/3/3/transport/http/"> 
   xmlns:scx="">		
  xmlns:thttp="">			
xmlns:thttp=""
>false			
xmlns:thttp="">true			

 	
  
   


I get the following exception:org.xml.sax.SAXParseException: The value of the attribute "prefix="xmlns",localpart="scx",rawname="xmlns:scx"" is invalid. Prefixed namespace bindings may not be empty.
When I change the pre-serialization request body to contain explicit namespace defintions for all the elements :

http://myns/schemas/2006/02/26/sciwsdl">http://myns/schemas/2006/3/3/sci/
"	xmlns:thttp="
http://myns/schemas/2006/3/3/transport/http/" 	schemaLocation="http://localhost:8080/jce/sci.xsd
"	serviceGroup="travelDepartment">
	http://myns/schemas/2006/3/3/sci/">
  	xmlns:thttp="
http://myns/schemas/2006/3/3/transport/http/" >
		  xmlns:thttp="
http://myns/schemas/2006/3/3/transport/http/" >false		 	xmlns:thttp="
http://myns/schemas/2006/3/3/transport/http/
" >true			Axis, post serialization does not insert any empty namespace defintions but the handler method is not found.
Couldn't find an appropriate operation for XML QName {
http://myns/schemas/2006/02/26/sciwsdl}PutConfigRequest
when I tried changing  http://myns/schemas/2006/02/26/sciwsdl
">to http://myns/schemas/2006/02/26/sciwsdl">it worked.
But the issue is I have to 
hack all the elements with the namespace definition.Thanks,Vikas+++=

Vikas,When using the message style interface, your application is responsible forconstructing the SOAP Body exactly as you've defined it in your WSDL.According to your WSDL, the Body should contain an element called
http://myns/schemas/2006/3/3/sci/sciwsdl}PutConfigRequest (not putConfig).Note that your WSDL has a critical namespace error: you don't declare the
"tns" namespace (the WSDL target namespace).
AnneOn 3/11/06, Vikas Singh <[EMAIL PROTECTED]
> wrote:> > Hi,> > Following is the WSDL:> > > > http://schemas.xmlsoap.org/wsdl/soap/"
> xmlns:wsdl="
http://schemas.xmlsoap.org/wsdl/"> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
 name="NewWSDLFile"> targetNamespace=" 
http://myns/schemas/2006/3/3/sci//sciwsdl"> xmlns:xsd1=" http://myns/schemas/2006/3/3/sci/sci
> ">> > > targetNamespace=" http://myns/schemas/2006/3/3/sci/sciwsdl"> > xmlns:scx="
http://myns/schemas/2006/3/3/sci/
 "> elementFormDefault="qualified">> > namespace=" 
http://myns/schemas/2006/3/3/sci/sci<
http://myns/schemas/2006/3/3/sci//s \> ci> "> schemaLocation="
http://localhost:8080/schemas/sci.xsd " />> 
> > > > > > > 
> > > > > > > 
> > > > > 
> > > > > 
> > > > > 
> > transport="http://schemas.xmlsoap.org/soap/http
 " />> 
> > soapAction=" http://myns/schemas/2006/3/3/sci/putSCI"
 />> > 
> > > > > > 

> > > > > > name="config">> > 

> > location=" http://localhost:8080/jce/services/config"
 />> > > > 
> > > > > > I wrap my request xml (which goes into the envelop body into a putConfig> to help it identify the 'Message' type method on the server.

> public SOAPBodyElement[] putConfig(SOAPBodyElement[] bodies)> > > The xml which I set in the SOA

Re: Axis2 and JBoss 4.0 and Asynchronous Webservices

[robert lazarski]

I looked more into this out of curiosity: 

1) JBoss 4.0.x internally uses a modified version of Axis 1.x. However, they only support their own stacks: 

http://wiki.jboss.org/wiki/Wiki.jsp?page=WebServiceStacks

"Any stack not listed above is not supported. This includes Standalone Apache Axis, and the JWSDP Web Services Stack. Only the wscompile tool in the JWSDP is supported.
"

This primarily means EJB - of course nothing is stopping you from using
your WAR, handling your transactions via spring, hibernate etc. 
 
2) The modified Axis 1.x stack is being phased out for their own stack, which supports JAXWS-2.0: 

http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossWS

3) They have a page "Why is Apache Axis not supported
" 

http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3889456#3889456

HTH,
Robert
http://www.braziloutsource.com/On 3/14/06, robert lazarski <
[EMAIL PROTECTED]> wrote:Just to clarify - what you mention makes sense from a WAR standpoint.
I'm unsure, however, how one would wire an EAR or SAR with EJB into an
Axis2 Web Service. I've done a lot with EJB, JWSDP and JBoss, and using
Axis 1.x would in several ways be similair. Axis2, however, doesn't
currently support JAX-RPC which is what the EJB 2.1 spec is based on -
and what JBoss is expecting. 

Now I could be wrong - in which case I would be pleasantly happy to
admit. My frame of mind currently is that it'd take a few days to see
if it is possible. Just my 2 cents. 

HTH,
Robert 
http://www.braziloutsource.com/
On 3/14/06, Antony Wilson <[EMAIL PROTECTED]
> wrote:Brian,I really did not do anything special for deploying Axis2 to JBoss 
4.0.3.I unzipped the Axis2 war into the JBoss "deploy" directory and deployedthe Axis2 webservices to the Axis2 "services" directory (as described inthe Axis2 docs). By default, JBoss 4.0.2+

 uses tomcat's classloadingimplementation vice their own unified/flat classloader. This approachisolates the classes/libraries per web application...so you avoid thelibrary/jar conflicts that can sometime arise from using a unified
classloader (e.g., the default JBoss classloader). So as I understandit...it is basically like running on Axis2 on standalone Tomcat. If youare using an earlier version of JBoss 4.0.1sp1 or lower...you should

modify a few lines in home>\server\default\deploy\jbossweb-tomcat50.sar\META-INF\jboss-service.xmlas follows:false−
falseThis will properly isolate the Axis2 classes and has worked for me. Fromthis point on...I just followed the instructions is in the Axis2 docs
for deploying webservices.As mentioned in my earlier email...I have had problems with theEchoNonBlockingDualClient example...at this point I'm reasonablyconvinced that it is due to the fact that the webservice is not
asynchronous. After reading a few earlier threads, I believe I have toextend the AbstractInOutAsyncMessageReceiver to create an asynchronousservice. Not that much fun:-( I really wish there was an example or

default implementation in the Axis2 distro. But I guess it's a smallprice to pay for the power/flexibility of Axis2;-)Hope this helps,TonyBrian Shields wrote:> Thats a bit disappointing, maybe i was a bit naive thinking it would
> be straight forward. I need to have a serious think how i will> progress. I am not willing to stop using axis2, ive too much time> invested now and everything set up the way i need it for my own

> research. Unfortunately i also have committments on a project that> uses JBoss 4.0. How much of WS-Security is implemented in the most> recent stable release of JBoss? How straightforward is it to implement
> security on existing (Web) SessionBeans? I particularly like the> modular approach of axis2 which completely abstracts the security> layer from the developer of the endpoint and vice versa.> Any other help, pointers etc (maybe a url to a walk thru of deploying
> axis2 on JBoss 4 ; ) ) greatly appreciated.> Regards,> Brian.>> robert lazarski wrote:>>> I haven't mixed JBoss and Axis2 together yet - but I know both>> reasonably well independently. I've used JBoss and EJB with JWSDP alot.
 Internally JBoss 4.0.x comes with Axis 1.x - though strangely their>> docs and examples favor JWSDP. Furthermore, It tends to be more>> natural to use a Statelful session bean with web services.
 There are Handlers that are part of Java itself and can be used with>> Axis 1 and JWSDP - javax.xml.rpc.handler.Handler is one I've used a>> lot. However, axis2 does not currently support JAX-RPC. JBoss is
>> pretty wired into JAX-RPC. So to make Web Services function with JBoss and EJB you'll need to>> edit and create a lot of files, and using axis2 in jboss and ejb is a>> bit bleeding edge. Don't get me wrong - it'd be a cool project and
>> yes I think it can be done. But if you don't know Jboss or axis2>> well, there are not going to be a lot of docs to help you. My>> personal experience on the jboss lists have not been good - they
>> strongly encourage paid support. Another option I would

[Axis2] WSDL2Java client code creation

[Sebastian J. Schultheiss]

Hi all,

we are playing around with the samples from the tutorial... we have extended the
MyService to take a comlpexType (a string, an int and a double) and would like
to create the client from the WSDL.

Axis has created the attached WSDL from our service, but WSDL2Java fails when
called like this:
---
axis2/bin# WSDL2Java -uri ..\samples\MyService.wsdl -o ..\samples\src -p
org.apache.axis2
-

with this error:
--
Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException
: org.apache.axis2.wsdl.codegen.CodeGenerationException: Invalid WSDL: The WSDL
Types Schema does not define a targetNamespace in file:../samples/
at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener
ationEngine.java:118)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:31)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: Invalid WSDL:
The WSDL Types Schema does not define a targetNamespace in file:../samples/
at org.apache.axis2.wsdl.codegen.extension.WSDLValidatorExtension.engage
(WSDLValidatorExtension.java:70)
at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener
ationEngine.java:80)
... 2 more


If we try to enter anything else in the targetNamespace attribute in the WSDL,
it gives us a NullPointerException instead.

Any clues?

Thanks a lot in advance!

-- Sebi
http://org.apache.axis2/xsd"; 
xmlns:xs="http://www.w3.org/2001/XMLSchema"; 
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; 
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; 
xmlns:tns="http://org.apache.axis2/"; 
targetNamespace="http://org.apache.axis2/";>http://www.w3.org/2001/XMLSchema"; 
xmlns:ns2="http://www.w3.org/2001/XMLSchema"; 
xmlns:ns0="http://www.w3.org/2001/XMLSchema"; 
xmlns:ns1="http://org.apache.axis2/xsd"; ns1:elementFormDefault="qualified" 
ns0:attributeFormDefault="unqualified" 
ns2:targetNamespace="http://org.apache.axis2/xsd";>



http://www.w3.org/2001/XMLSchema"; ns0:name="param0" 
ns1:type="xs:anyType"/>






http://www.w3.org/2001/XMLSchema"; ns0:name="return" 
ns1:type="xs:anyType"/>






http://www.w3.org/2001/XMLSchema"; ns0:name="param0" 
ns1:type="xs:anyType"/>






http://www.w3.org/2001/XMLSchema"; ns0:name="param0" 
ns1:type="xs:string"/>
http://www.w3.org/2001/XMLSchema"; ns0:name="param1" 
ns1:type="xs:int"/>
http://www.w3.org/2001/XMLSchema"; ns0:name="param2" 
ns1:type="xs:double"/>






http://www.w3.org/2001/XMLSchema"; ns0:name="return" 
ns1:type="xs:anyType"/>






http://www.w3.org/2001/XMLSchema"; ns0:name="param0" 
ns1:type="xs:anyType"/>



http://schemas.xmlsoap.org/soap/http"; 
style="document"/>http://www.org.apache.axis2"/>http://www.org.apache.axis2"/>http://www.org.apache.axis2"/>http://www.org.apache.axis2"/>http://www.org.apache.axis2"/>http://www.org.apache.axis2"/>http://localhost/axis2/services/MyService"/>

[0.94] How can i shutdown connection after call

[Filipp Akinfiev]

Hi all,
in my client class  i have function like :
  public TFileSendResponse storeFile(int type, String fileName, String 
pathToFile) {
TFileSendResponse response = null;
try {
response = FileSend.response(makeCall(FileSend.request(new 
TFileSend("", 
"", type, fileName, pathToFile)), "storeFile"));
} catch (Exception e) {
e.printStackTrace();
}
return response;
}

it's call function makeCall:

private MessageContext makeCall(MessageContext requestContext, String 
action) {
ServiceClient client;
MessageContext result = null;
try {
// creating the Service
AxisService service = new AxisService("IXMLWS2");

// creating the operations
AxisOperation operation = new OutInAxisOperation();
operation.setName(new 
javax.xml.namespace.QName("urn:XMLWSIntf-IXMLWS", action));
service.addOperation(operation);
client = new ServiceClient(new 
ConfigurationContextFactory().createConfigurationContextFromFileSystem(AXIS2_HOME),
 
service);
client.getOptions().setTo(targetEPR);
client.getOptions().setSoapAction("urn:XMLWSIntf2-IXMLWS2#" + 
action);
client.getOptions().setExceptionToBeThrownOnSOAPFault(true);

client.getOptions().setTransportInProtocol(Constants.TRANSPORT_TCP);

client.getOptions().setProperty(org.apache.axis2.context.MessageContextConstants.CHUNKED,org.apache.axis2.Constants.VALUE_FALSE);

client.getOptions().setProperty(Constants.Configuration.ENABLE_MTOM, 
Constants.VALUE_TRUE);

OperationClient opClient = client.createClient(new 
javax.xml.namespace.QName("urn:XMLWSIntf-IXMLWS", action));

opClient.addMessageContext(requestContext);
opClient.execute(true);
 
return 
opClient.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);
} catch (AxisFault e) {
e.printStackTrace();
}
return result;
}

after execute, i have open connection to axis server, how can i terminate it ?

thanks in advance!

RE: org.apache.axis.message.MessageElement.getAsString() not in online JavaDoc

[Neuendorff, Richard]

Does anyone have any info on this? 

Thanks again,
Richard A. Neuendorff

> I spent quite a bit of time researching then including the Xerces 
> libraries to serialize a MessageElement object into a string because I

> was unaware of getAsString().  I stumbled upon it while trying to do 
> something else and found that it is in my downloaded JavaDoc for 1.2.1

> and 1.3.1.  Is there a reason it is not in the online JavaDoc?  Is it 
> a method that should be avoided for some reason?
> 
> Thanks,
> Richard A. Neuendorff

RE: java.lang.IllegalArgumentException

[William Ward]

Hello Dies,
  I didn't modify any of the classes generated by WSDL2Java, but
I don't see any helper methods in the generated client stubs, should I
be seeing these ??

Regards,
William 


-Original Message-
From: Dies Koper [mailto:[EMAIL PROTECTED] 
Sent: 14 March 2006 14:02
To: axis-user@ws.apache.org
Subject: Re: java.lang.IllegalArgumentException

Hello William,

We'd need to see the WSDL to see if the SOAP message is right.
Unfortunately the SOAP message is rather long and complicated. You might
not get any replies.

As you seem to use complex structures (array of complex types?) I
imagine the Axis engine relies on the Helper classes (or helper code in
the generated Javabeans) on the client side. Just checking, but you did
not happen to have removed these classes/methods?

Regards,
Dies


William Ward wrote:
> Hello Dies,
>   thank you for the reply, I used tcpmon to capture the SOAP 
> message, I believe the problem is at the receiving end as I get the 
> response back from the Web Service no problem, it looks like it has a 
> problem de-serializing the response.
> 
> The odd thing is if I call the same Web Serice using just a test Java 
> application, I don't see any exception on the Axis side It seems to be

> just when I use JSP, Tomcat and Axis, I have tried just creating a 
> simple JSP page that has the same code as the test Java Application, 
> but I always get the Axis exception when using JSP & Tomcat, even 
> though it is the same code & libraries for both applications
> 
> below is the SOAP request / response that I see using tcpmon :
> 
> Regards,
> William
> 
> 
> ==
> Listen Port: 8081
> Target Host: 47.166.106.127
> Target Port: 80
> 
> 
>  Request 
> POST /ccmmwebservices/CICustomerWs.asmx HTTP/1.0
> Content-Type: text/xml; charset=utf-8
> Accept: application/soap+xml, application/dime, multipart/related,
> text/*
> User-Agent: Axis/1.2
> Host: 47.166.106.127:8081
> Cache-Control: no-cache
> Pragma: no-cache
> SOAPAction:
> "http://webservices.ci.ccmm.applications.nortel.com/ReadCustomerContac
> tH
> istory"
> Content-Length: 423
> 
> 
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>   
>   xmlns="http://webservices.ci.ccmm.applications.nortel.com";>
> 35
> 2qrc3E7a00
>  
>   
>
>
>
>
>
>  Response 
> HTTP/1.1 200 OK
> Connection: close
> Date: Tue, 14 Mar 2006 13:46:05 GMT
> Server: Microsoft-IIS/6.0
> X-Powered-By: ASP.NET
> X-AspNet-Version: 1.1.4322
> Cache-Control: private, max-age=0
> Content-Type: text/xml; charset=utf-8
> Content-Length: 4823
> 
> 
>http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
>   
>   xmlns="http://webservices.ci.ccmm.applications.nortel.com";>
> 
>
xmlns="http://datatypes.ci.ccmm.applications.nortel.com";>35
> xmlns="http://datatypes.ci.ccmm.applications.nortel.com";>
>   
>  80
>  35
>  sfs
>  Web
>  New
>  
> 10
> OB_Test1
> false
> Unspecified
>  
>  Unspecified
>  0
>  
> 2006-03-14T10:39:28.000-00:00
>  
>  0
>  ScheduledCallback
>  
> 
>203
>80
>sfs
>dfsdfdf
>
>  
> 2006-03-14T10:39:28.4678080-00:00
>
>
Unspecified
>
>  
> 2006-03-14T10:39:28.000-00:00
>
>  
> Callback_Request_from_Customer
>0
>0
>
>ScheduledCallback
> 
>  
>   
>   
>  81
>  35
>  sfsdf
>  Web
>  New
>  
> 2
> OB_Default_Skillset
> false
> Unspecified
> 
>  
>  Unspecified
>  0
>  
> 2006-03-14T10:39:34.000-00:00
>  
>  0
>  ScheduledCallba

Re: An RFC example needed! - 2

[Niels Baloe]

Hi all,

Well, I fixed the problem, by enabling the java.net debug mode, I could 
easily track down the problem and solve it (reading between the lines of 
encoded and decoded stuff). Yesterday I ended up with the XML message as 
I've sended it, without knowing it I was nearly finished. I only had to 
specify the return type (because it is an array-agr), and voila.


Note that I'm not unhappy with Axis, actually I'm quite happy with it. I 
hope the things I say help improving Axis. Like the suggestion to return the 
plain HTTP-output when the response serialiser doesn't receive anything it 
can parse (for example when you are talking to a Microsoft webservice which 
doesn't use SOAP:FAULT to say things back but only in plain text without any 
soap headers).


I hope Axis2 will end up as good as Axis1. For example, it's a good thing to 
use a deploy mechanism that looks more like Tomcat. I wondered why you'ld 
want to introduce another deploy language (the one in Apache SOAP and now 
the one in Apache Axis1) when already having the services.xml mechanism in 
Tomcat.


Thanks for now,

Niels Gorisse

_
Don't just search. Find. Check out the new MSN Search! 
http://search.msn.com/

Re: java.lang.IllegalArgumentException

[Dies Koper]

Hello William,

We'd need to see the WSDL to see if the SOAP message is right.
Unfortunately the SOAP message is rather long and complicated. You might 
not get any replies.


As you seem to use complex structures (array of complex types?) I 
imagine the Axis engine relies on the Helper classes (or helper code in 
the generated Javabeans) on the client side. Just checking, but you did 
not happen to have removed these classes/methods?


Regards,
Dies


William Ward wrote:

Hello Dies,
  thank you for the reply, I used tcpmon to capture the SOAP
message, I believe the problem is at the receiving end as I get the
response back from the Web Service no problem, it looks like it has a
problem de-serializing the response.

The odd thing is if I call the same Web Serice using just a test Java
application, I don't see any exception on the Axis side
It seems to be just when I use JSP, Tomcat and Axis,
I have tried just creating a simple JSP page that has the same code as
the test Java Application, but I always get the Axis exception when
using JSP & Tomcat, even though it is the same code & libraries for both
applications

below is the SOAP request / response that I see using tcpmon :

Regards,
William


==
Listen Port: 8081
Target Host: 47.166.106.127
Target Port: 80


 Request 
POST /ccmmwebservices/CICustomerWs.asmx HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related,
text/*
User-Agent: Axis/1.2
Host: 47.166.106.127:8081
Cache-Control: no-cache
Pragma: no-cache
SOAPAction:
"http://webservices.ci.ccmm.applications.nortel.com/ReadCustomerContactH
istory"
Content-Length: 423


   http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
  
 http://webservices.ci.ccmm.applications.nortel.com";>
35
2qrc3E7a00
 
  
   
   
   
   
   
 Response 

HTTP/1.1 200 OK
Connection: close
Date: Tue, 14 Mar 2006 13:46:05 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 1.1.4322
Cache-Control: private, max-age=0
Content-Type: text/xml; charset=utf-8
Content-Length: 4823


   http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
  
 http://webservices.ci.ccmm.applications.nortel.com";>

   http://datatypes.ci.ccmm.applications.nortel.com";>35
   http://datatypes.ci.ccmm.applications.nortel.com";>
  
 80
 35
 sfs
 Web
 New
 
10
OB_Test1
false
Unspecified
 
 Unspecified
 0
 
2006-03-14T10:39:28.000-00:00
 
 0
 ScheduledCallback
 

   203
   80
   sfs
   dfsdfdf
   
 
2006-03-14T10:39:28.4678080-00:00

   
   Unspecified
   
 
2006-03-14T10:39:28.000-00:00

   
 
Callback_Request_from_Customer

   0
   0
   
   ScheduledCallback

 
  
  
 81
 35
 sfsdf
 Web
 New
 
2
OB_Default_Skillset
false
Unspecified

 
 Unspecified
 0
 
2006-03-14T10:39:34.000-00:00
 
 0
 ScheduledCallback
 

   204
   81
   sfsdf
   sdfdsf
   
 
2006-03-14T10:39:34.9053080-00:00

   
   Unspecified
   
 
2006-03-14T10:39:34.000-00:00

   
 
Callback_Request_from_Customer

   0
   0
   
   ScheduledCallback

 
  
  
   

Re: [Axis2] EchoNonBlockingDualClient problem

[Diego]

Hi everybody!

I'm also experiencing the same problem.  I run axis2 v0.93 on tomcat 
5.5.7.  My code is slightly different than the EchoNonBlockingDualClient 
but it's basically the same:



public void 
startinsertMappingAnnotations(InsertMappingAnnotationsDocument requestDoc,
 final 
AstrodasPeerCallbackHandler callback)

   throws RemoteException {
   Call call = new Call(_serviceContext);
   call.setClientOptions(_clientOptions);
   MessageContext messageContext = getMessageContext();
   _clientOptions.setSoapAction("insertMappingAnnotations");
   // Uses two separate listeners: dual transport.
   call.engageModule(new QName(Constants.MODULE_ADDRESSING));
   _clientOptions.setListenerTransportProtocol(Constants.TRANSPORT_HTTP);
   _clientOptions.setUseSeparateListener(true);
   // Sets the exception throwing status.
   _clientOptions.setExceptionToBeThrownOnSOAPFault(true);
   // Sets the properties.
   SOAPEnvelope envelope = createEnvelope();

setValueDoc(envelope,AstrodasPeerinsertMappingAnnotationsDatabindingSupporter.toOM(requestDoc));
   messageContext.setEnvelope(envelope);
   call.invokeNonBlocking(operations[0], messageContext,
   new Callback() {
   public void onComplete(AsyncResult result) {
   Object object = 
AstrodasPeerinsertMappingAnnotationsDatabindingSupporter


.fromOM(getElement(result.getResponseEnvelope(),"doc"),

InsertMappingAnnotationsResponseDocument.class);

callback.receiveResultinsertMappingAnnotations((InsertMappingAnnotationsResponseDocument) 
object);

   }
   public void reportError(Exception e) {
   callback.receiveErrorinsertMappingAnnotations(e);
   }
   });
}


I also get the same problem using a dual transport blocking client:


public InsertMappingAnnotationsResponseDocument 
insertMappingAnnotations(InsertMappingAnnotationsDocument requestDoc)

throws RemoteException {
MessageContext messageContext = getMessageContext();
Call call = new Call(_serviceContext);
_clientOptions.setSoapAction("insertMappingAnnotations");
call.setClientOptions(_clientOptions);
// Uses two separate listeners: dual transport.
call.engageModule(new QName(Constants.MODULE_ADDRESSING));
_clientOptions.setListenerTransportProtocol(Constants.TRANSPORT_HTTP);
_clientOptions.setUseSeparateListener(true);
// Sets the exception throwing status.
// Sets the properties.
populateModules(call);
SOAPEnvelope envelope = createEnvelope();
// Style is Doc.

setValueDoc(envelope,AstrodasPeerinsertMappingAnnotationsDatabindingSupporter.toOM(requestDoc));
messageContext.setEnvelope(envelope);
MessageContext responseMessageContext = 
call.invokeBlocking(operations[0],messageContext);

SOAPEnvelope responseEnvelope = responseMessageContext.getEnvelope();
Object obj = AstrodasPeerinsertMappingAnnotationsDatabindingSupporter

.fromOM(getElement(responseEnvelope,"doc"),InsertMappingAnnotationsResponseDocument.class);
return (InsertMappingAnnotationsResponseDocument)obj;
}


The request arrives to the client and is executed successfully but the 
client doesn't get any response.  Actually, the server sends a response 
to the client, here it is:




xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> 


  
  

  Client
  
 For input string: "0:0:0:0:0:0:1:6060"; nested exception is:
.java.net.MalformedURLException: For input string: 
"0:0:0:0:0:0:1:6060"; nested exception is:
.org.apache.axis2.AxisFault: For input string: 
"0:0:0:0:0:0:1:6060"; nested exception is:
.java.net.MalformedURLException: For input string: 
"0:0:0:0:0:0:1:6060"
   



  http://myAxisServer/role/default
  

  org.apache.axis2.AxisFault: For input string: 
"0:0:0:0:0:0:1:6060"; nested exception is:

  .java.net.MalformedURLException: For input string: "
  0:0:0:0:0:0:1:6060"; nested exception is:
  .org.apache.axis2.AxisFault: For input string: 
"0:0:0:0:0:0:1:6060"; nested exception is:
  .java.net.MalformedURLException: For input string: 
"0:0:0:0:0:0:1:6060"
  .at 
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:265)
  .at 
org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:93) 

  .at 
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:42)
  .at 
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:158)
  .at 
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:211)
  .at 
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:181)

  .at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
  .at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

RE: java.lang.IllegalArgumentException

[William Ward]

Hello Dies,
  thank you for the reply, I used tcpmon to capture the SOAP
message, I believe the problem is at the receiving end as I get the
response back from the Web Service no problem, it looks like it has a
problem de-serializing the response.

The odd thing is if I call the same Web Serice using just a test Java
application, I don't see any exception on the Axis side
It seems to be just when I use JSP, Tomcat and Axis,
I have tried just creating a simple JSP page that has the same code as
the test Java Application, but I always get the Axis exception when
using JSP & Tomcat, even though it is the same code & libraries for both
applications

below is the SOAP request / response that I see using tcpmon :

Regards,
William


==
Listen Port: 8081
Target Host: 47.166.106.127
Target Port: 80


 Request 
POST /ccmmwebservices/CICustomerWs.asmx HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related,
text/*
User-Agent: Axis/1.2
Host: 47.166.106.127:8081
Cache-Control: no-cache
Pragma: no-cache
SOAPAction:
"http://webservices.ci.ccmm.applications.nortel.com/ReadCustomerContactH
istory"
Content-Length: 423


   http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
  
 http://webservices.ci.ccmm.applications.nortel.com";>
35
2qrc3E7a00
 
  
   
   
   
   
   
 Response 
HTTP/1.1 200 OK
Connection: close
Date: Tue, 14 Mar 2006 13:46:05 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 1.1.4322
Cache-Control: private, max-age=0
Content-Type: text/xml; charset=utf-8
Content-Length: 4823


   http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
  
 http://webservices.ci.ccmm.applications.nortel.com";>

   http://datatypes.ci.ccmm.applications.nortel.com";>35
   http://datatypes.ci.ccmm.applications.nortel.com";>
  
 80
 35
 sfs
 Web
 New
 
10
OB_Test1
false
Unspecified
 
 Unspecified
 0
 
2006-03-14T10:39:28.000-00:00
 
 0
 ScheduledCallback
 

   203
   80
   sfs
   dfsdfdf
   
 
2006-03-14T10:39:28.4678080-00:00
   
   Unspecified
   
 
2006-03-14T10:39:28.000-00:00
   
 
Callback_Request_from_Customer
   0
   0
   
   ScheduledCallback

 
  
  
 81
 35
 sfsdf
 Web
 New
 
2
OB_Default_Skillset
false
Unspecified

 
 Unspecified
 0
 
2006-03-14T10:39:34.000-00:00
 
 0
 ScheduledCallback
 

   204
   81
   sfsdf
   sdfdsf
   
 
2006-03-14T10:39:34.9053080-00:00
   
   Unspecified
   
 
2006-03-14T10:39:34.000-00:00
   
 
Callback_Request_from_Customer
   0
   0
   
   ScheduledCallback

 
  
  
 82
 35
 sfs
 Web
 New
 
10
OB_Test1
false
Unspecified
 
 Unspecified
 0
 
2006-03-14T10:39:41.000-00:00
 
 0
 Sc

Re: An RFC example needed!

[Niels Baloe]

Hi all,

Thanks for your reply's.


Take a look at the migration guide:

http://ws.apache.org/axis2/0_93/migration.html


Yes I've seen it, I took some time to implement that example, but it isn't 
complete. It uses the echo example, look at the the word 'ClientUtil' in " 
ClientUtil.getEchoOMElement();  " while at the same time the Axis1 example 
above clearly shows that you can work with the 'String' type right out of 
the box (and it's terribly simple to register other types as well!!). On the 
other hand, Axis2 introduces an 'OMElement' but nothing clearly shows (at 
least for me) how to work with it. I've seen some registering stuff in the 
echo example though, but it didn't work out. Really, a simple example which 
completely works (like with a class Address { String name,String telephone} 
) is needed. Simple examples makes an API good.


Another thing, I don't like a lot of code being added to my data classes. 
I've seen what axis2 does to my classes. Is that really needed? In Axis1 I 
don't have any generated garbage in my classes (except get and set functions 
which are harmless); in fact there's only one _method_ (not even a class) 
which calls the service, complete with registering and everything. It looks 
like in Axis2 all classes will be filled with generated stuff, before I can 
be a client application. Or am I wrong?



http://issues.apache.org/jira/browse/AXIS2-485?page=all


I'll look to it in a moment, thanks! Perhaps I can help?

BTW, the address example in the axis 1.x uses WSDL style 'rpc encoded' . 
For

the time being you need to use document / literal with axis2 .


I switched to wrapped/literal right away because I'm talking with .NET 
clients too. But I'm not using that example at all, I wrote my own;). I only 
looked at it as it is a clear way of how to write my client-method. That was 
about two weeks ago.


You're right -- the Apache SOAP page should provide a warning that tells 
you to use Axis 1 instead.


Thanks. Is there a place where I should mail it to?
Of course, Axis2 doesn't look complete yet, in the future the main Axis1 
page should say that it is depreciated.


After you have refined your WSDL file, then you want to use wsdl2java to 
regenerate your service skeleton and WSDD file.


Perhaps if you posted your WSDL and WSDD files we could provide you with a 
little more assistance.


Well, in fact, I simply did that, I generated the WSDL, it looked fine, then 
I gave it to the .NET service, and they implemented it accordingly. No 
wonder: everything works fine (this computer being a server and running the 
client code to access this computer). But really, the WSDL or the message is 
not the issue at all. I manually wrote a serialiser to get capitals inside 
some headers, untill the generated message worked fine (peeking with the 
TCPTunneler), while manually sending the message itsself with some a 
pure-java code. If I send the captured message with a normal Java socket, it 
works perfectly, but if Axis1 does the trick, it simply doesn't work. And 
the only difference in the two messages is the \1.0 -- \1.1 number. See for 
yourself below! So, how do I force the HTTP\1.1 usage?


Thank you very much!,
Niels


-


Sending with a pure-java client:
""
POST /axis/services/rpcrouter HTTP/1.1
Content-Type: text/xml; charset=utf-8
SOAPAction: "http://www.voorst.nl/VoorstVariant/getGemeenteInfo";
User-Agent: Java/1.5.0_06
Host: localhost:90
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
Content-Length: 1198


  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>

 
xmlns:ns1="http://www.voorst.nl/VoorstVariant/";>

   
   ***
   ***

 
 
http://www.voorst.nl/VoorstVariant/";>
   xmlns:ns2="http://www.voorst.nl/VoorstVariant/";>
  xsi:type="xsd:string">203000,471000 
203600,472000 203700,472000 203700,471900 
203600,471900

   

 
  
"

Sending with Axis1:

""
POST /axis/services/rpcrouter HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/1.4
Host: localhost:90
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: "http://www.voorst.nl/VoorstVariant/getGemeenteInfo";
Content-Length: 1057


  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>

 
xmlns:ns1="http://www.voorst.nl/VoorstVariant/";>

   
   ***
   ***

 
 
http://www.voorst.nl/VoorstVariant/";>
   xmlns:ns2="http://www.voorst.nl/VoorstVariant/";>
  xsi:type="x

Re: java.lang.IllegalArgumentException

[Dies Koper]

Hello William,

Looks like a tough one.. For starters, use tcpmon to capture the SOAP 
message. Checking the SOAP message usually helps to determine whether 
the problem is on the sending or receiving end.


Regards,
Dies


William Ward wrote:

Hi,
  I get the following exception when calling a web service using Axis, 
I am calling the Web Service from a JSP page on Tomcat


Any ideas how I can find out what is causing this problem

{http://xml.apache.org/axis/}stackTrace:java.lang.IllegalArgumentExcepti
on
at
org.apache.axis.encoding.ser.SimpleDeserializer.onEndElement(SimpleDeser
ializer.java:176)
at
org.apache.axis.encoding.DeserializerImpl.endElement(DeserializerImpl.ja
va:502)
at
org.apache.axis.encoding.DeserializationContext.endElement(Deserializati
onContext.java:1087)
at
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:
171)
at
org.apache.axis.message.MessageElement.publishToHandler(MessageElement.j
ava:1140)
at
org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
at
org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
at org.apache.axis.client.Call.invoke(Call.java:2448)
at org.apache.axis.client.Call.invoke(Call.java:2347)
at org.apache.axis.client.Call.invoke(Call.java:1804)

Re: some axis2 deployment questions

[robert lazarski]

See my responses inline:On 3/14/06, SOA Work <[EMAIL PROTECTED]> wrote:
Hi,I'm going to publish a simple service using axis2 war distribution.Now I'm running into some (maybe simple) questions, which I can not solve with the user guide:1) what's the difference between RawXML and RPC message receivers?
With
RawXML the methods signature gets OMElement input and output? If I
don't want to change my business class I have to use
RPCMessageReceiver, right?

I haven't used RPCMessageReceiver - but the version.aar does and it
just returns a String - unlike the other recievers that use OMElement.
RPCCallTest also works with Strings. 
2)
can I use patterns like: "*" or multiple operations names like
"getString getInt"  to publish a bunch of operations?

I believe just * is supported.  
3)
If I don't specify any operation inside my  element all
operations are published. Can I set the messageReceiver to use for all
operations?
Not sure. 
 4) My resulting wsdl file is literal but I want ther rpc encoded style. How can I change this?
rpc encoded currently is not supported.  
thx a lotDominik__
Verschicken Sie romantische, coole und witzige Bilder per SMS!Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

Re: Axis2 and JBoss 4.0 and Asynchronous Webservices

[robert lazarski]

Just to clarify - what you mention makes sense from a WAR standpoint.
I'm unsure, however, how one would wire an EAR or SAR with EJB into an
Axis2 Web Service. I've done a lot with EJB, JWSDP and JBoss, and using
Axis 1.x would in several ways be similair. Axis2, however, doesn't
currently support JAX-RPC which is what the EJB 2.1 spec is based on -
and what JBoss is expecting. 

Now I could be wrong - in which case I would be pleasantly happy to
admit. My frame of mind currently is that it'd take a few days to see
if it is possible. Just my 2 cents. 

HTH,
Robert 
http://www.braziloutsource.com/On 3/14/06, Antony Wilson <[EMAIL PROTECTED]
> wrote:Brian,I really did not do anything special for deploying Axis2 to JBoss 
4.0.3.I unzipped the Axis2 war into the JBoss "deploy" directory and deployedthe Axis2 webservices to the Axis2 "services" directory (as described inthe Axis2 docs). By default, JBoss 4.0.2+
 uses tomcat's classloadingimplementation vice their own unified/flat classloader. This approachisolates the classes/libraries per web application...so you avoid thelibrary/jar conflicts that can sometime arise from using a unified
classloader (e.g., the default JBoss classloader). So as I understandit...it is basically like running on Axis2 on standalone Tomcat. If youare using an earlier version of JBoss 4.0.1sp1 or lower...you should
modify a few lines in home>\server\default\deploy\jbossweb-tomcat50.sar\META-INF\jboss-service.xmlas follows:false−
falseThis will properly isolate the Axis2 classes and has worked for me. Fromthis point on...I just followed the instructions is in the Axis2 docs
for deploying webservices.As mentioned in my earlier email...I have had problems with theEchoNonBlockingDualClient example...at this point I'm reasonablyconvinced that it is due to the fact that the webservice is not
asynchronous. After reading a few earlier threads, I believe I have toextend the AbstractInOutAsyncMessageReceiver to create an asynchronousservice. Not that much fun:-( I really wish there was an example or
default implementation in the Axis2 distro. But I guess it's a smallprice to pay for the power/flexibility of Axis2;-)Hope this helps,TonyBrian Shields wrote:> Thats a bit disappointing, maybe i was a bit naive thinking it would
> be straight forward. I need to have a serious think how i will> progress. I am not willing to stop using axis2, ive too much time> invested now and everything set up the way i need it for my own
> research. Unfortunately i also have committments on a project that> uses JBoss 4.0. How much of WS-Security is implemented in the most> recent stable release of JBoss? How straightforward is it to implement
> security on existing (Web) SessionBeans? I particularly like the> modular approach of axis2 which completely abstracts the security> layer from the developer of the endpoint and vice versa.> Any other help, pointers etc (maybe a url to a walk thru of deploying
> axis2 on JBoss 4 ; ) ) greatly appreciated.> Regards,> Brian.>> robert lazarski wrote:>>> I haven't mixed JBoss and Axis2 together yet - but I know both>> reasonably well independently. I've used JBoss and EJB with JWSDP alot.
 Internally JBoss 4.0.x comes with Axis 1.x - though strangely their>> docs and examples favor JWSDP. Furthermore, It tends to be more>> natural to use a Statelful session bean with web services.
 There are Handlers that are part of Java itself and can be used with>> Axis 1 and JWSDP - javax.xml.rpc.handler.Handler is one I've used a>> lot. However, axis2 does not currently support JAX-RPC. JBoss is
>> pretty wired into JAX-RPC. So to make Web Services function with JBoss and EJB you'll need to>> edit and create a lot of files, and using axis2 in jboss and ejb is a>> bit bleeding edge. Don't get me wrong - it'd be a cool project and
>> yes I think it can be done. But if you don't know Jboss or axis2>> well, there are not going to be a lot of docs to help you. My>> personal experience on the jboss lists have not been good - they
>> strongly encourage paid support. Another option I would strongly consider is just use hibernate if you>> have a choice - instead of EJB. It'll be a lot simpler config. Sounds
>> like your commited to EJB though. If you still decide to use axis2 with jboss, look at the jboss guide>> chapter 12. Look at their files: webservices.xml
>> ejb-jar.xml>> jboss.xml Know what config-*.xml does HTH,>> Robert>> http://www.braziloutsource.com/
 On 3/13/06, * Brian Shields* < [EMAIL PROTECTED]>> 
[EMAIL PROTECTED]>> wrote: Hi All,>> I am currently using Axis2 and WSS4J as a test environment for some>> secure services. I want to now deploy these secure services on a JBoss
>> 4.0 AS. My experience with JBoss is limited, this work has been>> carried>> out by another member of the group. We have an ejb application which>> uses a stateless session bean to implement the web services interface.
>> At the moment this is all deployed using JBossWS. 

Re: [Axis2] EchoNonBlockingDualClient problem

[Ali Sadik Kumlali]

Hi,I have the same problem with Tomcat 5.5 and have two questions:1) Why does my client HTTP server is immediately closed and i get  I/O exception when server tries to post the response? 2) Why does it print "waiting" when options.setUseSeparateListener() is passed false? (This is Antony Wilson's question actually) Thanks a lot.Ali Sadik KumlaliFIRST CASE    + Original EchoNonBlockingDualClient.java    + System.out.println("waiting..."); in while loopClient Log---testEchoNonBlockingDualClient: [java] - Deploying module : addressing [java] - Starting to process SOAP 1.1 message [java] v="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://10.10.10.103:6060/axis2/services/__ANONYMOUS_SERVICE__/__OPERATION_OUT_IN__http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://127.0.0.1:8080/axis2/services/MyService="http://schemas.xmlsoap.org/ws/2004/08/addressing">D3C49495E884E3019B11423375911122975BF946D7CFA918C611423375837211Axis2 Echo String example1:echo> [java] [SimpleHTTPServer] Stop calledServer Log--- Deploying module : addressing- Deploying module : security- Starting to process SOAP 1.1 message- I/O exception (org.apache.commons.httpclient.NoHttpResponseException) caught   when processing request: The server 10.10.10.103 failed to respond- Retrying requestSECOND CASE:     + Original EchoNonBlockingDualClient.java     + System.out.println("waiting..."); in while loop   &nbs
 p; +
 options.setUseSeparateListener(false); Client Log---testEchoNonBlockingDualClient: [java] - Deploying module : addressing [java] waiting... [java] - Starting to process SOAP 1.1 message [java] v="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymoushttp://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymoushttp://127.0.0.1:8080/axis2/services/MyServiceD3C49495E884E3019B11423376489274>:RelationshipType="wsa:Reply">6439FE16DCA2252A8E11423376486611soapenv:Header>Axis2 Echo String penv:Body>Server Log--- De
 ploying
 module : addressing- Deploying module : security- Starting to process SOAP 1.1 messagerobert lazarski <[EMAIL PROTECTED]> wrote: Could you start another thread with an axis2 prefix mentioning jboss ? I know jboss with web services ok, but it was with either axis 1 or jwsdp - not axis2 . Are you using wsdl and ejb ?   Robert http://www.braziloutsource.com/On 3/13/06, Brian Shields < [EMAIL PROTECTED]> wrote:Tony,Apologies for jumping into this thread on an unr
 elated
 issue but i notice you have axis2 deployed on JBoss 4.0. I am about to undertakethis task and was wondering if there was any resources on the web tohelp in it. I dont have a lot of experience with JBoss so not looking forward to it!!Regards,BrianAntony Wilson wrote:>> I have not been able to get the EchonNonBlockingDualClient example to> work as described in the documentation.  In my setup, I have Axis2 > deployed to JBoss 4.0.3 and I have modified the> userguide.example1.MyService to delay for about 10 seconds before> responding (leaving the 'echo' method).  After packaging and deploying> the  MyService.aar to Axis2, I run EchoNonBlockingDualClient> example...slightly modified to add a print statement within the while> loop...like so>>public static void main(String[] args)
 {>try { >OMElement payload = ClientUtil.getEchoOMElement();>>Options options = new Options();>options.setTo(targetEPR);>options.setTransportInProtocol (Constants.TRANSPORT_HTTP);>options.setUseSeparateListener(true);>>//Callback to handle the response>Callback callback = new Callback()
 {>public void onComplete(AsyncResult result) {>try {>StringWriter writer = new StringWriter();>> result.getResponseEnvelope().serialize(XMLOutputFactory.newInstance()>.createXMLStreamWriter(writer));>writer.flush
 ();>System.out.println(writer.toString());>>>} catch (XMLStreamException e) {>onError(e);>}>}>>public void onError(Exception e)
 {>e.printStackTrace();>}>};>>//Non-Blocking Invocation>ServiceClient sender = new ServiceClient(); >sender.setOptions(options);>sender.sendReceiveNonblocking(paylo

java.lang.IllegalArgumentException

[William Ward]

Hi,
  I get the following exception when calling a web service using Axis, 
I am calling the Web Service from a JSP page on Tomcat

Any ideas how I can find out what is causing this problem

{http://xml.apache.org/axis/}stackTrace:java.lang.IllegalArgumentExcepti
on
at
org.apache.axis.encoding.ser.SimpleDeserializer.onEndElement(SimpleDeser
ializer.java:176)
at
org.apache.axis.encoding.DeserializerImpl.endElement(DeserializerImpl.ja
va:502)
at
org.apache.axis.encoding.DeserializationContext.endElement(Deserializati
onContext.java:1087)
at
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:
171)
at
org.apache.axis.message.MessageElement.publishToHandler(MessageElement.j
ava:1140)
at
org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
at
org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
at org.apache.axis.client.Call.invoke(Call.java:2448)
at org.apache.axis.client.Call.invoke(Call.java:2347)
at org.apache.axis.client.Call.invoke(Call.java:1804)



Thanks,
William

some axis2 deployment questions

[SOA Work]

Hi,

I'm going to publish a simple service using axis2 war distribution.
Now I'm running into some (maybe simple) questions, which I can not solve with 
the user guide:

1) what's the difference between RawXML and RPC message receivers?
With RawXML the methods signature gets OMElement input and output? If I don't 
want to change my business class I have to use RPCMessageReceiver, right?

2) can I use patterns like: "*" or multiple operations names like "getString 
getInt"  to publish a bunch of operations?

3) If I don't specify any operation inside my  element all operations 
are published. Can I set the messageReceiver to use for all operations?

4) My resulting wsdl file is literal but I want ther rpc encoded style. How can 
I change this?

thx a lot
Dominik
__
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

Deploy does nothing

[Christina Wulf]

Hi there :O)

 

I was hoping that
someone could help me with an axis problem.

I have generated a web
service with the tools Java2WSDL and WSDL2Java, I have filled in the blanks in
the SoapBindingImpl and compiled the files.

I have packaged the
class files in a jar file and saved it in the WEB-INF\lib dir. Now I have
deployed my web service, no problem!

The problem is that the
deploy.wsdd apparently does absolutely nothing…. The server-conf is
unchanged and there is no service running.

What to do?!

 

Med Venlig Hilsen

 

Christina Wulf

 

E-mail: [EMAIL PROTECTED]

Mobil: 51 94 61 04