date:20060615




Aasi kukar,
Another way is to save a local copy of the wsdl and try WSDL2Java 
;-)

  -Original Message-From: [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED]Sent: Thursday, June 15, 2006 
  12:42 PMTo: axis-user@ws.apache.orgSubject: [SPAM] - RE: 
  [Axis 1.2] WSDL2Java for HTTPs url throws exception. - Message is from an 
  unknown sender
  
  Hi 
  Remy,
  
  I agree with 
  your first point that SSL enforces the name of the certificate and the server 
  host.
  I agree that is 
  what is happening in the first case. (The exception being thrown 
  below).
  
  But in the 
  client I suppose the URL that we talk is the same URL that we give as the 
  targetEndPointAddress.
  
  I have changed 
  this address from https://ip-address/prwp/services/UploadServices to 
  https://host-name/prwp/services/UploadServices and vice versa and I 
  can access the web service successfully. I don't understand the reason for 
  that.
  
  I have added a 
  aliastopaz.wipro.com/alias 
  for the Host "192.168.134.145" ... 
  / to the tomcat server.xml so that I can invoke my 
  webservices using both ip address and host name.
  
  Shouldn't the 
  same work with WSDL2Java also. Can you throw or some other Axis Developers 
  throw some light on this.
  
  Regards,
  
  


  
Subir 
S
  


  


  

  
  
  
  
  
  From: Remy 
  Bertrand [mailto:[EMAIL PROTECTED] Sent: Thursday, June 15, 2006 1:16 
  AMTo: axis-user@ws.apache.orgSubject: Re: [Axis 1.2] WSDL2Java for 
  HTTPs url throws exception.
  
  
  The problem is not that WSDL2Java 
  cannot resolve IP address, it's that https protocol enforce that the name of 
  the certificate must correspond to the server 
  host.
  
  
  
  If you generate the certificate 
  with name topaz.subir.com, you have to give this name to WSDL2java, not the IP 
  address.
  
  
  
  If you were doing that in a 
  browser, you would have an alert because the name in the certificate doesn't 
  correspond to the hostname. In a Java program, this is an 
  exception...
  
  
  
  And lasts, your client probably 
  uses the host name in his own code, thats why he can connect to the 
  service.
  
  
  
  Rémy
  

- Original Message - 


From: [EMAIL PROTECTED] 


To: axis-user@ws.apache.org 


Sent: 
Wednesday, June 14, 2006 11:50 AM

Subject: [Axis 
1.2] WSDL2Java for HTTPs url throws 
exception.


Hi,

I 
am getting a weird error when trying run WSDL2Java using https 
connection.

I 
have SSL enabled using mod-ssl in Apache server connected to tomcat server 
using JK2.

Jdk 
is 1.5.0_03, tomcat 5.0.9, apache 2.0.52

I use the 
following to generate the stubs

java 
-Djavax.net.ssl.trustStore=C:\TraceLogs\tempstore.jks 
-Djavax.net.ssl.trustStorePassword=subir123 org.apache.axis.wsdl.WSDL2Java 
https://192.168.134.145:443/prwp/services/UploadServices?wsdl -p 
prwp.soapclient -o .

I get the 
following exception.

java.io.IOException: 
HTTPS hostname wrong: should be 
192.168.134.145
 
at 
sun.net.www.protocol.https.HttpsClient.checkURLSpoofing(HttpsClient.j
ava:493)
 
at 
sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:
418)
 
at 
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect
(AbstractDelegateHttpsURLConnection.java:170)
 
at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon
nection.java:913)
 
at 
sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Http
sURLConnectionImpl.java:234)
 
at 
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrent
Entity(XMLEntityManager.java:973)
 
at 
com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineD
ocVersion(XMLVersionDetector.java:184)
 
at 
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(X
ML11Configuration.java:798)
 
at 
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(X
ML11Configuration.java:764)
 
at 
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.
java:148)
 
at 
com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.
java:250)
 
at 
com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Doc
umentBuilderImpl.java:292)
 
at 
org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:369)
 
at 
org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:420)
 
at 
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav
a:480)
 
at 
org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:360)
 
at

Re: [Axis2] Hot reloading of classes

2006-06-15 Thread Michele Mazzucco

Hi Ali,

what are the service handlers shown in fig. 2 [1]? If the service uses
any custom module/handler, this should go into a separate .mar archive,
am I right?

Thanks,
Michele

[1] http://jaxmag.com/itr/online_artikel/psecom,id,757,nodeid,147.html

Ali Sadik Kumlali wrote:
 Hi Andrew,
 
 Could you please check following links out?
 
 http://www.mail-archive.com/axis-user@ws.apache.org/msg12077.html
 http://jaxmag.com/itr/online_artikel/psecom,id,757,nodeid,147.html
 
 Regards,
 
 Ali Sadik Kumlali
 
 - Original Message 
 From: Andrew B [EMAIL PROTECTED]
 To: axis-user@ws.apache.org
 Sent: Wednesday, June 14, 2006 11:28:17 PM
 Subject: [Axis2] Hot reloading of classes
 
 Hello,
 
 Is it possible to hot-reload classes in an Axis2 service? Or do I have
 to restart the app server every time I make a change?
 
 Thanks!
 
 __
 Do You Yahoo!?
 Tired of spam? Yahoo! Mail has the best spam protection around
 http://mail.yahoo.com
 
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [SPAM] - RE: [Axis 1.2] WSDL2Java for HTTPs url throws exception. - Message is from an unknown sender

2006-06-15 Thread subir.sasikumar









That is a good
suggestion!!!

But that means you
think that WSDL2Java will not work with https based urlsisnt it???






 
  
  -Subir S
  
  
  
  
 
 
  
  
  
 
 
  
  
  
 














From: Dhakshinamoorthy,
Hariharasudhan [mailto:[EMAIL PROTECTED] 
Sent: Thursday, June 15, 2006
12:46 PM
To: axis-user@ws.apache.org
Subject: RE: [SPAM] - RE: [Axis
1.2] WSDL2Java for HTTPs url throws exception. - Message is from an unknown
sender







Aasi
kukar,





Another way
is to save a local copy of the wsdl and try WSDL2Java ;-)





-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Thursday, June 15, 2006
12:42 PM
To: axis-user@ws.apache.org
Subject: [SPAM] - RE: [Axis 1.2]
WSDL2Java for HTTPs url throws exception. - Message is from an unknown sender

Hi Remy,



I agree with your
first point that SSL enforces the name of the certificate and the server host.

I agree that is what
is happening in the first case. (The exception being thrown below).



But in the client I
suppose the URL that we talk is the same URL that we give as the
targetEndPointAddress.



I have changed this
address from https://ip-address/prwp/services/UploadServices to
https://host-name/prwp/services/UploadServices and vice versa and I can
access the web service successfully. I don't understand the reason for that.



I have added a aliastopaz.subir.com/alias
for the Host 192.168.134.145
... / to the tomcat server.xml
so that I can invoke my webservices using both ip address and host name.



Shouldn't the same
work with WSDL2Java also. Can you throw or some other Axis Developers throw
some light on this.



Regards,




 
  
  Subir S
  
  
  
  
 
 
  
  
  
 
 
  
  
  
 














From: Remy Bertrand
[mailto:[EMAIL PROTECTED] 
Sent: Thursday, June 15, 2006 1:16
AM
To: axis-user@ws.apache.org
Subject: Re: [Axis 1.2] WSDL2Java
for HTTPs url throws exception.







The problem is not that WSDL2Java cannot resolve IP address,
it's that https protocol enforce that the name of the certificate must
correspond to the server host.











If you generate the certificate with name topaz.subir.com,
you have to give this name to WSDL2java, not the IP address.











If you were doing that in a browser, you would have an alert
because the name in the certificate doesn't correspond to the hostname. In a
Java program, this is an exception...











And lasts, your client probably uses the host name in his
own code, thats why he can connect to the service.











Rémy







- Original Message - 





From: [EMAIL PROTECTED]






To: axis-user@ws.apache.org






Sent: Wednesday, June
14, 2006 11:50 AM





Subject: [Axis 1.2]
WSDL2Java for HTTPs url throws exception.









Hi,



I
am getting a weird error when trying run WSDL2Java using https connection.



I
have SSL enabled using mod-ssl in Apache server connected to tomcat server
using JK2.



Jdk
is 1.5.0_03, tomcat 5.0.9, apache 2.0.52



I use the following
to generate the stubs



java
-Djavax.net.ssl.trustStore=C:\TraceLogs\tempstore.jks
-Djavax.net.ssl.trustStorePassword=subir123 org.apache.axis.wsdl.WSDL2Java
https://192.168.134.145:443/prwp/services/UploadServices?wsdl -p
prwp.soapclient -o .



I get the following
exception.



java.io.IOException:
HTTPS hostname wrong: should be 192.168.134.145


at sun.net.www.protocol.https.HttpsClient.checkURLSpoofing(HttpsClient.j

ava:493)


at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:

418)


at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect

(AbstractDelegateHttpsURLConnection.java:170)


at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon

nection.java:913)


at
sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Http

sURLConnectionImpl.java:234)


at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrent

Entity(XMLEntityManager.java:973)


at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineD

ocVersion(XMLVersionDetector.java:184)


at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(X

ML11Configuration.java:798)


at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(X

ML11Configuration.java:764)


at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.

java:148)


at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.

java:250)


at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Doc

umentBuilderImpl.java:292)


at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:369)


at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:420)


at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav

a:480)


at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:360)


at java.lang.Thread.run(Thread.java:595)



The
host name corresponding to the IP address 192.168.134.145 is topaz.subir.com

A
dummy server certificate is

[Axis2] Client cookie support

2006-06-15 Thread Sai Arunachalam

Hi,  Is there a way I can set a cookie (my own) in the HTTP requests sent to a web service via Axis2 clients? The cookie I wish to set contains authentication information and not session information.I currently use HttpClient wherein I am able to set the cookie as follows:
  HttpState initialState = new HttpState( ); initialState.addCookie( mycookie ); httpclient.setState(initialState);I am trying to move my codebase to use Axis2 and am not able to find out how to do this in Axis2? If anyone can provide me with links to examples or any resource, that would be a great help.
Thanks,Sai

Re: Axis2 Deployment Model Deficiency

2006-06-15 Thread Warren Crossing

Is that a valid call? servletcontext.getRealPath(WEB-INF) be careful 
here not to open a security violation.


servlet spec says this.

A special directory exists within the application hierarchy named 
“WEB-INF”.
This directory contains all things related to the application that 
aren’t in the

document root of the application. The WEB-INF node is not part of the public
document tree of the application. No ﬁle contained in the WEB-INF 
directory may
be served directly to a client by the container. However, the contents 
of the WEB-
INF directory are visible to servlet code using the getResource and 
getResource-

AsStream method calls on the ServletContext, and may be exposed using the
RequestDispatcher calls. Hence, if the Application Developer needs 
access, from
servlet code, to application speciﬁc conﬁguration information that he 
does not
wish to be exposed directly to the Web client, he may place it under 
this directory.

Since requests are matched to resource mappings in a case-sensitive manner,
client requests for ‘/WEB-INF/foo’, ‘/WEb-iNf/foo’, for example, should 
not result
in contents of the Web application located under /WEB-INF being 
returned, nor

any form of directory listing thereof.



[EMAIL PROTECTED] wrote:

Dims,

I haven't tried the latest nightly. I'll give it a shot.

Thanks,
Junaid



   
 Davanum  
 Srinivas 
 [EMAIL PROTECTED]  To 
 maxis-user@ws.apache.org 
cc 
 06/14/2006 11:43  
 AMSubject 
   Re: Axis2 Deployment Model  
   Deficiency  
 Please respond to 
 [EMAIL PROTECTED] 
  he.org   
   
   
   





Junaid,

Did you try latest nightly? I believe this is fixed.

thanks,
dims

On 6/14/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:


Hi,

Here's my scenario which I believe might be a common requirement for a


lot


of enterprise applications. I'm trying to bundle Axis2 webapp as part of


a


bigger EAR application and deploy in an application server such as
WebLogic. I would like to package up all of the Web Services inside of


the


webapp/EAR file. The problem is that Axis2 cannot seem to load the


services


from within the EAR file in WebLogic..

The issue arises due to the fact that Axis2 relies on the concept of a
repository, which MUST be a folder on the file system. On certain
application servers like WebSphere, this is not an issue since they
internally explode the EAR when you deploy it and Axis2 does not seem to
have a problem. However application servers like WebLogic do NOT explode
the EAR, hence Axis2 cannot find/load the services from the repository.

Here is the offending code in WarBasedAxisConfigurator:

   repository =
config.getServletContext().getRealPath(/WEB-INF);  --- this returns


null


in Weblogic
   axis2Steram = new FileInputStream(repository +
/conf/axis2.xml);

There are 2 work-arounds as I understand it:
1) Always deploy the application in an exploded format (WebLogic provides
this feature). However this is not an option for us.
2) Use a repository folder OUTSIDE of the EAR by specifiying the
axis2.xml.path in web.xml. However this option also poses a problem in a
cluster scenario where you need to have a common accessible folder, which
will serve as the repository and EVERY machine in the cluster must be
mapped to this common folder. It's a setup  maintenance headache.

I worked previously with Axis 1.x and it did not have a problem loading
services from within the EAR file. Ofcourse any changes you make to the
configuration while it was running would be lost on a server re-start
(since server-config.wsdd was read-only). But it still worked.

I believe this is a critical change that is needed and should be


addressed


in the next version, unless I'm missing something here. Let me know if I
should open up an enhancement request JIRA.

Thanks,
Junaid


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






--

RE: [Axis 1.2] WSDL2Java for HTTPs url throws exception. -




Iam not sure , i too had the same issue with https , then i 
did this to solve the issue 
Did it work for anyone ? please let us 
know.
[Hariharasudhan.D]-Original 
Message-From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED]Sent: Thursday, June 15, 2006 3:14 
PMTo: axis-user@ws.apache.orgSubject: [SPAM] - RE: [SPAM] 
- RE: [Axis 1.2] WSDL2Java for HTTPs url throws exception. - Message is from an 
unknown sender - Message is from an unknown sender

  
  That is a good 
  suggestion!!!
  But that means 
  you think that WSDL2Java will not work with https based urls...isn't 
  it???
  
  
  


  
-Subir 
S
  


  


  

  
  
  
  
  
  From: 
  Dhakshinamoorthy, Hariharasudhan 
  [mailto:[EMAIL PROTECTED] Sent: Thursday, June 15, 2006 12:46 
  PMTo: axis-user@ws.apache.orgSubject: RE: [SPAM] - RE: [Axis 1.2] 
  WSDL2Java for HTTPs url throws exception. - Message is from an unknown 
  sender
  
  
  Aasi 
  kukar,
  
  Another 
  way is to save a local copy of the wsdl and try WSDL2Java 
  ;-)
  
-Original 
Message-From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]Sent: Thursday, June 15, 2006 12:42 
PMTo: axis-user@ws.apache.orgSubject: [SPAM] - RE: [Axis 1.2] 
WSDL2Java for HTTPs url throws exception. - Message is from an unknown 
sender
Hi 
Remy,

I agree with 
your first point that SSL enforces the name of the certificate and the 
server host.
I agree that 
is what is happening in the first case. (The exception being thrown 
below).

But in the 
client I suppose the URL that we talk is the same URL that we give as the 
targetEndPointAddress.

I have changed 
this address from https://ip-address/prwp/services/UploadServices to 
https://host-name/prwp/services/UploadServices and vice versa and I 
can access the web service successfully. I don't understand the reason for 
that.

I have added a 
aliastopaz.subir.com/alias 
for the Host "192.168.134.145" ... 
/ to the tomcat server.xml so that I can invoke my 
webservices using both ip address and host 
name.

Shouldn't the 
same work with WSDL2Java also. Can you throw or some other Axis Developers 
throw some light on this.

Regards,


  
  

  Subir 
  S

  
  

  
  

  





From: Remy 
Bertrand [mailto:[EMAIL PROTECTED] Sent: Thursday, June 15, 2006 1:16 
AMTo: axis-user@ws.apache.orgSubject: Re: [Axis 1.2] WSDL2Java for 
HTTPs url throws exception.


The problem is not that 
WSDL2Java cannot resolve IP address, it's that https protocol enforce that 
the name of the certificate must correspond to the server 
host.



If you generate the certificate 
with name topaz.subir.com, you have to give this name to WSDL2java, not the 
IP address.



If you were doing that in a 
browser, you would have an alert because the name in the certificate doesn't 
correspond to the hostname. In a Java program, this is an 
exception...



And lasts, your client probably 
uses the host name in his own code, thats why he can connect to the 
service.



Rémy

  
  - Original Message - 
  
  
  From: [EMAIL PROTECTED] 
  
  
  To: axis-user@ws.apache.org 
  
  
  Sent: 
  Wednesday, June 14, 2006 11:50 AM
  
  Subject: [Axis 
  1.2] WSDL2Java for HTTPs url throws 
  exception.
  
  
  Hi,
  
  I 
  am getting a weird error when trying run WSDL2Java using https 
  connection.
  
  I 
  have SSL enabled using mod-ssl in Apache server connected to tomcat server 
  using JK2.
  
  Jdk 
  is 1.5.0_03, tomcat 5.0.9, apache 2.0.52
  
  I use the 
  following to generate the stubs
  
  java 
  -Djavax.net.ssl.trustStore=C:\TraceLogs\tempstore.jks 
  -Djavax.net.ssl.trustStorePassword=subir123 org.apache.axis.wsdl.WSDL2Java 
  https://192.168.134.145:443/prwp/services/UploadServices?wsdl -p 
  prwp.soapclient -o .
  
  I get the 
  following exception.
  
  java.io.IOException: 
  HTTPS hostname wrong: should be 
  192.168.134.145
   
  at 
  sun.net.www.protocol.https.HttpsClient.checkURLSpoofing(HttpsClient.j
  ava:493)
   
  at 
  sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:
  418)
   
  at 
  sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect
  (AbstractDelegateHttpsURLConnection.java:170)
   
  at 
  sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon
  nection.java:913)
   
  at

RE: [SPAM] - [Axis2] Client cookie support - Bayesian Filter detected spam

Sai
Arunachalam,

I don't think you can set a cookie in the HTTP
Request and send it to a webservice , webserives are not dependent on a
particular transport , i mean its not only for HTTP there could be other
transport too.Best way is to set your credentials in the SOAP Header and send
it

Google .. the best place for examples ;-) , incase if you
have troubles finding a good example let me .., will do advanced google
programming for you

-Original Message-From: Sai Arunachalam
[mailto:[EMAIL PROTECTED]Sent: Thursday, June 15, 2006
3:24 PMTo: axis-user@ws.apache.orgSubject: [SPAM] -
[Axis2] Client cookie support - Bayesian Filter detected
spamHi, Is there a way I can
set a cookie (my own) in the HTTP requests sent to a web service via Axis2
clients? The cookie I wish to set contains authentication information and not
session information.I currently use HttpClient wherein I am able to
set the cookie as follows:
HttpState initialState = new HttpState( );
initialState.addCookie( mycookie );
httpclient.setState(initialState);I am trying to move my codebase to
use Axis2 and am not able to find out how to do this in Axis2? If anyone can
provide me with links to examples or any resource, that would be a great help.
Thanks,Sai Confidential: This electronic message and all contents contain information from Syntel, Inc. which may be privileged, confidential or otherwise protected from disclosure. The information is intended to be for the addressee only. If you are not the addressee, any disclosure, copy, distribution or use of the contents of this message is prohibited. If you have recieved this electronic message in error, please notify the sender immediately and destroy the original message and all copies.

Confidential: This electronic message and all contents contain information from Syntel, Inc. which may be privileged, confidential or otherwise protected from disclosure. The information is intended to be for the addressee only. If you are not the addressee, any disclosure, copy, distribution or use of the contents of this message is prohibited. If you have received this electronic message in error, please notify the sender immediately and destroy the original message and all copies.

[Axis2] Operation Not found WSA Action = null

2006-06-15 Thread heikki

Hi,I've seen the earlier posts on similar subjects but I have not found my solution ..I have a service that I want to access in REST style. The client code is  String toEpr = 

http://localhost:7001/axis2/rest/MyService; Options options = new Options(); options.setTo(new EndpointReference(toEpr)); options.setAction(MyAction);

 options.setTransportInProtocol(Constants.TRANSPORT_HTTP); options.setProperty(Constants.Configuration.ENABLE_REST, Constants.VALUE_TRUE); ServiceClient sender = new ServiceClient();
 sender.engageModule(new QName(Constants.MODULE_ADDRESSING)); sender.setOptions(options);  XMLStreamReader reader = document.newXMLStreamReader(); // document is an XMLBeans binding that already has read its data from an XML file
 StAXOMBuilder builder = new StAXOMBuilder(reader); OMElement payload= builder.getDocumentElement();  OMElement result = sender.sendReceive(payload);When executing, on the server I get the following exception :
org.apache.axis2.AxisFault: Operation Not found EPR is /axis2/services/MyService and WSA Action ="" nullIt makes no difference whether or not I set the action on the options, as in the above client code. It also makes no difference whether or not I set the addressing module on the sender, as in the above code. 
In services.xml on the server I have the followingserviceGroup service name=MyService messageReceivers messageReceiver mep=

http://www.w3.org/2004/08/wsdl/in-out class=com.this.and.that.MyServiceMessageReceiverInOut/ /messageReceivers parameter locked=false name=ServiceClass
com.this.and.that.MyServiceSkeleton/parameter operation name=MyRQ mep=
http://www.w3.org/2004/08/wsdl/in-out actionMappingMyAction/actionMapping
 /operation /service/serviceGroupDoes anyone have an idea what I'm missing or doing wrong ??thank youHeikki Doeleman

Re: [Axis 1.2] WSDL2Java for HTTPs url throws exception. -

2006-06-15 Thread Manuel Mall

On Thursday 15 June 2006 18:19, Dhakshinamoorthy, Hariharasudhan wrote:
 Iam not sure , i too had the same issue with https , then i did this
 to solve the issue
 Did it work for anyone ? please let us know.


Using https to point to a remote wsdl file for the wsdl2java tool works 
fine for me.

As far as I know the default Java SSL host name validation (that is the 
default implementation of the javax.net.ssl.HostnameVerifier interface) 
requires the hostname in the https request to match the name in the 
certificate. No dns or name resolution takes place.

So if your https request contains an IP address as hostname component 
and the server presents a certificate containing the unresolved 
hostname the default Java SSL implementation will throw an exception.

Manuel

 [Hariharasudhan.D]  -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 Sent: Thursday, June 15, 2006 3:14 PM
 To: axis-user@ws.apache.org
 Subject: [SPAM] - RE: [SPAM] - RE: [Axis 1.2] WSDL2Java for HTTPs url
 throws exception. - Message is from an unknown sender - Message is
 from an unknown sender



 That is a good suggestion!!!

 But that means you think that WSDL2Java will not work with https
 based urls...isn't it???




 -Subir S












   _


 From: Dhakshinamoorthy, Hariharasudhan
 [mailto:[EMAIL PROTECTED]
 Sent: Thursday, June 15, 2006 12:46 PM
 To: axis-user@ws.apache.org
 Subject: RE: [SPAM] - RE: [Axis 1.2] WSDL2Java for HTTPs url throws
 exception. - Message is from an unknown sender



 Aasi kukar ,

 Another way is to save a local copy of the wsdl and try WSDL2Java ;-)

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 Sent: Thursday, June 15, 2006 12:42 PM
 To: axis-user@ws.apache.org
 Subject: [SPAM] - RE: [Axis 1.2] WSDL2Java for HTTPs url throws
 exception. - Message is from an unknown sender

 Hi Remy,



 I agree with your first point that SSL enforces the name of the
 certificate and the server host.

 I agree that is what is happening in the first case. (The exception
 being thrown below).



 But in the client I suppose the URL that we talk is the same URL that
 we give as the targetEndPointAddress.



 I have changed this address from
 https://ip-address/prwp/services/UploadServices to
 https://host-name/prwp/services/UploadServices and vice versa and I
 can access the web service successfully. I don't understand the
 reason for that.



 I have added a aliastopaz.subir.com/alias for the Host
 192.168.134.145 ... / to the tomcat server.xml so that I can
 invoke my webservices using both ip address and host name.



 Shouldn't the same work with WSDL2Java also. Can you throw or some
 other Axis Developers throw some light on this.



 Regards,


 Subir S












   _


 From: Remy Bertrand [mailto:[EMAIL PROTECTED]
 Sent: Thursday, June 15, 2006 1:16 AM
 To: axis-user@ws.apache.org
 Subject: Re: [Axis 1.2] WSDL2Java for HTTPs url throws exception.



 The problem is not that WSDL2Java cannot resolve IP address, it's
 that https protocol enforce that the name of the certificate must
 correspond to the server host.



 If you generate the certificate with name topaz.subir.com, you have
 to give this name to WSDL2java, not the IP address.



 If you were doing that in a browser, you would have an alert because
 the name in the certificate doesn't correspond to the hostname. In a
 Java program, this is an exception...



 And lasts, your client probably uses the host name in his own code,
 thats why he can connect to the service.



 Rémy

 - Original Message -

 From: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]

 To: axis-user@ws.apache.org mailto:axis-user@ws.apache.org

 Sent: Wednesday, June 14, 2006 11:50 AM

 Subject: [Axis 1.2] WSDL2Java for HTTPs url throws exception.



 Hi,



 I am getting a weird error when trying run WSDL2Java using https
 connection.



 I have SSL enabled using mod-ssl in Apache server connected to tomcat
 server using JK2.



 Jdk is 1.5.0_03, tomcat 5.0.9, apache 2.0.52



 I use the following to generate the stubs



 java -Djavax.net.ssl.trustStore=C:\TraceLogs\tempstore.jks
 -Djavax.net.ssl.trustStorePassword=subir123
 org.apache.axis.wsdl.WSDL2Java
 https://192.168.134.145:443/prwp/services/UploadServices?wsdl -p
 prwp.soapclient -o .



 I get the following exception.



 java.io.IOException: HTTPS hostname wrong:  should be
 192.168.134.145

 at
 sun.net.www.protocol.https.HttpsClient.checkURLSpoofing(HttpsClient.j

 ava:493)

 at
 sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:

 418)

 at
 sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect

 (AbstractDelegateHttpsURLConnection.java:170)

 at
 sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon

 nection.java:913)

 at
 sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Http

 sURLConnectionImpl.java:234)

 at

[Axis2] Axis2SampleDocLitService not working.

2006-06-15 Thread Jan Bauer Nielsen


Hello.

I am an Axis2 novice and I am therefore trying to work my way through 
the examples provided in the Axis2 userguide, but I am having getting 
the data binding examples to work.


I am currently working on a debian sarge install with a Java 2 Standard 
Edition (build 1.5.0_06-b05). Axis2 v1.0 is deployed on a Geronimo v1.0 
web application server.


I created the skeleton using the following command:

% sh WSDL2Java.sh -uri ../samples/wsdl/Axis2SampleDocLit.wsdl -ss -sd -d 
xmlbeans -o ../samples -p org.apache.axis2.userguide


I added the code suggested to Axis2SampleDocLitServiceSkeleton.java and 
then ran


% ant jar.server

Finally I successfully deployed the service, I am not so sure it is 
working though. Testing from SOAP::Lite gives me


Request:
 POST /axis2/services/Axis2SampleDocLitService HTTP/1.1 TE: 
deflate,gzip;q=0.3 Connection: TE, close Accept: text/xml

Accept: multipart/*
Accept: application/soap
Host: localhost:8080
User-Agent: SOAP::Lite/Perl/0.67
Content-Length: 459
Content-Type: text/xml; charset=utf-8
SOAPAction: #echoString

?xml version=1.0 encoding=UTF-8?soap:Envelope 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; 
xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; 
xmlns:xsd=http://www.w3.org/2001/XMLSchema; 
soap:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 
xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;soap:BodyechoStringechoStringParam 
xsi:type=xsd:stringAxis2 
Echo/echoStringParam/echoString/soap:Body/soap:Envelope



Response:
HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 
Content-Type: text/html;charset=utf-8

Content-Length: 1901
Date: Thu, 15 Jun 2006 10:56:29 GMT
Connection: close

htmlheadtitleApache Tomcat/5.5.9 - Error 
report/titlestyle!--H1 
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} 
H2 
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} 
H3 
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} 
BODY 
{font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} 
B 
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} 
P 
{font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A 
{color : black;}A.name {color : black;}HR {color : #525D76;}--/style 
/headbodyh1HTTP Status 500 - /h1HR size=1 
noshade=noshadepbtype/b Exception report/ppbmessage/b 
u/u/ppbdescription/b uThe server encountered an internal 
error () that prevented it from fulfilling this 
request./u/ppbexception/b preorg.apache.axiom.om.OMException

org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:265)
org.apache.axiom.om.impl.traverse.OMChildrenQNameIterator.hasNext(OMChildrenQNameIterator.java:75)
org.apache.axiom.om.impl.llom.OMElementImpl.getFirstChildWithName(OMElementImpl.java:222)
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getHeader(SOAPEnvelopeImpl.java:76)
org.apache.axis2.engine.AxisEngine.createFaultMessageContext(AxisEngine.java:183)
org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:168)
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:153)
javax.servlet.http.HttpServlet.service(HttpServlet.java:615)
javax.servlet.http.HttpServlet.service(HttpServlet.java:688)
/pre/ppbnote/b uThe full stack trace of the root cause is 
available in the Apache Tomcat/5.5.9 logs./u/pHR size=1 
noshade=noshadeh3Apache Tomcat/5.5.9/h3/body/html


So obviously I have done something wrong somewhere?


As a further ado I also tried to build a client stub

% sh WSDL2Java.sh -uri 
../samples/build/classes/META-INF/Axis2SampleDocLitService.wsdl -d 
xmlbeans -o ../samples -p org.apache.axis2.userguide


% jar.client

I then wrote this simple client class:

import org.apache.axis2.userguide.*;

public class Client {
public static void main(String[] args) {
try {
Axis2SampleDocLitServiceStub stub = new 
Axis2SampleDocLitServiceStub(null, 
http://localhost:8080/axis2/services/Axis2SampleDocLitService;);


EchoStringParamDocument reqDoc = 
EchoStringParamDocument.Factory.newInstance();


reqDoc.setEchoStringParam(Axis2 Echo);
EchoStringReturnDocument resDoc = stub.EchoString(reqDoc);
System.out.println(resDoc.getEchoString());
} catch(Exception e)  {
e.printStackTrace();
}
}
}

which I am unable to compile with the following command:

% javac -classpath

RE: [SPAM] - Multiple WSDL files generation - Message is from an unknown sender




Jean ! 
My Comments 

  -Original Message-From: 
  [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED]Sent: Thursday, June 15, 
  2006 5:05 PMTo: axis-user@ws.apache.orgSubject: [SPAM] - 
  Multiple WSDL files generation - Message is from an unknown 
  sender
  Hello. 
  I have 2 Java Interfaces, each one 
  representing a WebService : public interface interf1 
  {  public void m1(MyObject o); } 
  public interface 
  interf2 {  public void m2(MyObject o); } As you can see, the 2 operations have a MyObject 
  instance input parameter. I would like to generate the following WSDL files with java2wsdl 
  :- one WSDL file containing the MyObject complex 
  type. [Hariharasudhan.D]WSDL means Web Services Description Language WSDL for 
  complex type doesn't make sense
  you should be having a 
  seperate XSD file forMyObject and then import them to the WSDL 
  files ( the two interfaces mentioned above )- one WSDL file containing the interf1 web service 
  and using the first WSDL file. - one WSDL file containing the interf2 web service 
  and using the first WSDL file. Is it possible ? If yes how can I do ? 
  Thanks a lot. 
  Regards. 
  Jean-BaptisteConfidential: This electronic message and all contents contain information from Syntel, Inc. which may be privileged, confidential or otherwise protected from disclosure. The information is intended to be for the addressee only. If you are not the addressee, any disclosure, copy, distribution or use of the contents of this message is prohibited. If you have recieved this electronic message in error, please notify the sender immediately and destroy the original message and all copies.




Confidential:  This electronic message and all contents contain information from Syntel, Inc. which may be privileged, confidential or otherwise protected from disclosure. The information is intended to be for the addressee only. If you are not the addressee, any disclosure, copy, distribution or use of the contents of this message is prohibited.  If you have received this electronic message in error, please notify the sender immediately and destroy the original message and all copies.

Re: [Axis2] Axis2SampleDocLitService not working.

2006-06-15 Thread Ajith Ranabahu


Hi,
For XMLbeans you'll have to add the generated xsb files to the
classpath. if you've used the  jar.client ant target then there should
be xmlbeans-packaged.jar file in the build folder. Add that to the
classpath and that should solve the problem :)

Ajith

On 6/15/06, Jan Bauer Nielsen [EMAIL PROTECTED] wrote:

Hello.

I am an Axis2 novice and I am therefore trying to work my way through
the examples provided in the Axis2 userguide, but I am having getting
the data binding examples to work.

I am currently working on a debian sarge install with a Java 2 Standard
Edition (build 1.5.0_06-b05). Axis2 v1.0 is deployed on a Geronimo v1.0
web application server.

I created the skeleton using the following command:

% sh WSDL2Java.sh -uri ../samples/wsdl/Axis2SampleDocLit.wsdl -ss -sd -d
xmlbeans -o ../samples -p org.apache.axis2.userguide

I added the code suggested to Axis2SampleDocLitServiceSkeleton.java and
then ran

% ant jar.server

Finally I successfully deployed the service, I am not so sure it is
working though. Testing from SOAP::Lite gives me

Request:
  POST /axis2/services/Axis2SampleDocLitService HTTP/1.1 TE:
deflate,gzip;q=0.3 Connection: TE, close Accept: text/xml
Accept: multipart/*
Accept: application/soap
Host: localhost:8080
User-Agent: SOAP::Lite/Perl/0.67
Content-Length: 459
Content-Type: text/xml; charset=utf-8
SOAPAction: #echoString

?xml version=1.0 encoding=UTF-8?soap:Envelope
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
soap:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;soap:BodyechoStringechoStringParam
xsi:type=xsd:stringAxis2
Echo/echoStringParam/echoString/soap:Body/soap:Envelope


Response:
HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1
Content-Type: text/html;charset=utf-8
Content-Length: 1901
Date: Thu, 15 Jun 2006 10:56:29 GMT
Connection: close

htmlheadtitleApache Tomcat/5.5.9 - Error
report/titlestyle!--H1
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}
H2
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}
H3
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
BODY
{font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;}
B
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;}
P
{font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A
{color : black;}A.name {color : black;}HR {color : #525D76;}--/style
/headbodyh1HTTP Status 500 - /h1HR size=1
noshade=noshadepbtype/b Exception report/ppbmessage/b
u/u/ppbdescription/b uThe server encountered an internal
error () that prevented it from fulfilling this
request./u/ppbexception/b preorg.apache.axiom.om.OMException
org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:265)
org.apache.axiom.om.impl.traverse.OMChildrenQNameIterator.hasNext(OMChildrenQNameIterator.java:75)
org.apache.axiom.om.impl.llom.OMElementImpl.getFirstChildWithName(OMElementImpl.java:222)
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getHeader(SOAPEnvelopeImpl.java:76)
org.apache.axis2.engine.AxisEngine.createFaultMessageContext(AxisEngine.java:183)
org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:168)
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:153)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:615)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:688)
/pre/ppbnote/b uThe full stack trace of the root cause is
available in the Apache Tomcat/5.5.9 logs./u/pHR size=1
noshade=noshadeh3Apache Tomcat/5.5.9/h3/body/html

So obviously I have done something wrong somewhere?


As a further ado I also tried to build a client stub

% sh WSDL2Java.sh -uri
../samples/build/classes/META-INF/Axis2SampleDocLitService.wsdl -d
xmlbeans -o ../samples -p org.apache.axis2.userguide

% jar.client

I then wrote this simple client class:

import org.apache.axis2.userguide.*;

public class Client {
 public static void main(String[] args) {
 try {
 Axis2SampleDocLitServiceStub stub = new
Axis2SampleDocLitServiceStub(null,
http://localhost:8080/axis2/services/Axis2SampleDocLitService;);

 EchoStringParamDocument reqDoc =
EchoStringParamDocument.Factory.newInstance();

 reqDoc.setEchoStringParam(Axis2 Echo);
 EchoStringReturnDocument resDoc = stub.EchoString(reqDoc);
 System.out.println(resDoc.getEchoString());
 } catch(Exception e)  {
 e.printStackTrace();
 }
 }
}

which I am unable to compile with the following command:

% javac -classpath

Re: [SPAM] - [Axis2] Client cookie support - Bayesian Filter detected spam

2006-06-15 Thread Davanum Srinivas


Sai,

Please see http://www.wso2.net/kb/87 it shows you how to access the
http client. You can set the http state on the client.

-- dims

On 6/15/06, Dhakshinamoorthy, Hariharasudhan
[EMAIL PROTECTED] wrote:



Sai Arunachalam ,

I don't think you can set a cookie in the HTTP Request and send it to a
webservice , webserives are not dependent on a particular transport , i mean
its not only for HTTP there could be other transport too.Best way is to set
your credentials in the SOAP Header and send it

Google  .. the best place for examples ;-) , incase if you have troubles
finding a good example let me .., will do advanced google programming for
you

-Original Message-
From: Sai Arunachalam [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 15, 2006 3:24 PM
To: axis-user@ws.apache.org
Subject: [SPAM] - [Axis2] Client cookie support - Bayesian Filter detected
spam

Hi,

   Is there a way I can set a cookie (my own) in the HTTP requests sent to a
web service via Axis2 clients? The cookie I wish to set contains
authentication information and not session information.

I currently use HttpClient wherein I am able to set the cookie as follows:

HttpState initialState = new HttpState( );
initialState.addCookie( mycookie );
httpclient.setState(initialState);

I am trying to move my codebase to use Axis2 and am not able to find out how
to do this in Axis2? If anyone can provide me with links to examples or any
resource, that would be a great help.

Thanks,
Sai

Confidential:  This electronic message and all contents contain information
from Syntel, Inc. which may be privileged, confidential or otherwise
protected from disclosure.  The information is intended to be for the
addressee only.   If you are not the addressee, any disclosure, copy,
distribution or use of the contents of this message is prohibited.  If you
have recieved this electronic message in error, please notify the sender
immediately and destroy the original message and all copies.




Confidential: This electronic message and all contents contain information
from Syntel, Inc. which may be privileged, confidential or otherwise
protected from disclosure. The information is intended to be for the
addressee only. If you are not the addressee, any disclosure, copy,
distribution or use of the contents of this message is prohibited. If you
have received this electronic message in error, please notify the sender
immediately and destroy the original message and all copies.



--
Davanum Srinivas : http://wso2.com/blogs/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [SPAM] - Multiple WSDL files generation - Message is from an unknown sender

2006-06-15 Thread Jean-Baptiste . Binet


Thanks for your comments but in the
generated WSDL file there is a wsdl:types section which contains
complexType tags describing
MyObject, and this was generated by Java2WSDL.

Jean-Baptiste







Dhakshinamoorthy, Hariharasudhan
[EMAIL PROTECTED]
15/06/2006 13:47
Please respond to axis-user

To:
   axis-user@ws.apache.org
cc:
   
Subject:
   RE: [SPAM] - Multiple WSDL files generation
- Message is from an unknown sender


Jean ! 
My Comments

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 15, 2006 5:05 PM
To: axis-user@ws.apache.org
Subject: [SPAM] - Multiple WSDL files generation - Message is from
an unknown sender


Hello. 

I have 2 Java Interfaces, each one representing a WebService :


public interface interf1 
{ 
 public void m1(MyObject o); 
} 

public interface interf2 
{ 
 public void m2(MyObject o); 
} 

As you can see, the 2 operations have a MyObject instance input parameter.

I would like to generate the following WSDL files with java2wsdl :

 
- one WSDL file containing the MyObject complex type.

[Hariharasudhan.D] WSDL means Web
Services Description Language WSDL for complex type doesn't make sense
you should be
having a seperate XSD file for MyObject and then import them
to the WSDL files ( the two interfaces mentioned above )
- one WSDL file containing the
interf1 web service and using the first WSDL file.

- one WSDL file containing the interf2 web service and using the first
WSDL file. 

Is it possible ? 
If yes how can I do ? 
Thanks a lot. 

Regards. 

Jean-Baptiste

Confidential: This electronic
message and all contents contain information from Syntel, Inc. which may
be privileged, confidential or otherwise protected from disclosure. The
information is intended to be for the addressee only.  If you are
not the addressee, any disclosure, copy, distribution or use of the contents
of this message is prohibited. If you have recieved this electronic
message in error, please notify the sender immediately and destroy the
original message and all copies.


Confidential: This electronic message and
all contents contain information from Syntel, Inc. which may be privileged,
confidential or otherwise protected from disclosure. The information is
intended to be for the addressee only. If you are not the addressee, any
disclosure, copy, distribution or use of the contents of this message is
prohibited. If you have received this electronic message in error, please
notify the sender immediately and destroy the original message and all
copies.

Re: [Axis2] Axis2SampleDocLitService not working.

Title: Apache Tomcat/5.5.9 - Errorbr report
Hi,I am having the same issue, with a different service (a generated one). In my .aar, I have all the package subdirectories, including schemaorg_apache_xmlbeans, directly under the top level of the jar (no classes directory). The .xsb files should be in the classpath there, right? (The .aar is an exploded deployment, which I have found to work so far).I can elaborate more on the structure of the .aar if required - I am desperate to get this problem solved.ThanksAjith Ranabahu [EMAIL PROTECTED] wrote: Hi,For XMLbeans you'll have to add the generated xsb files to theclasspath. if you've used the  jar.client ant target then there shouldbe xmlbeans-packaged.jar file in the build folder. Add that to theclasspath and that should solve the problem :)AjithOn 6/15/06, Jan Bauer
 Nielsen <[EMAIL PROTECTED]> wrote: Hello. I am an Axis2 novice and I am therefore trying to work my way through the examples provided in the Axis2 userguide, but I am having getting the data binding examples to work. I am currently working on a debian sarge install with a Java 2 Standard Edition (build 1.5.0_06-b05). Axis2 v1.0 is deployed on a Geronimo v1.0 web application server. I created the skeleton using the following command: % sh WSDL2Java.sh -uri ../samples/wsdl/Axis2SampleDocLit.wsdl -ss -sd -d xmlbeans -o ../samples -p org.apache.axis2.userguide I added the code suggested to Axis2SampleDocLitServiceSkeleton.java and then ran % ant jar.server Finally I successfully deployed the service, I am not so sure it is working though. Testing from SOAP::Lite gives me Request:   POST
 /axis2/services/Axis2SampleDocLitService HTTP/1.1 TE: deflate,gzip;q=0.3 Connection: TE, close Accept: text/xml Accept: multipart/* Accept: application/soap Host: localhost:8080 User-Agent: SOAP::Lite/Perl/0.67 Content-Length: 459 Content-Type: text/xml; charset=utf-8 SOAPAction: "#echoString"  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xsi:type="xsd:string"Axis2 Echo Response: HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 Content-Type:
 text/html;charset=utf-8 Content-Length: 1901 Date: Thu, 15 Jun 2006 10:56:29 GMT Connection: close  HTTP Status 500 -  noshade="noshade"type Exception
 reportmessage description The server encountered an internal error () that prevented it from fulfilling this request.exception org.apache.axiom.om.OMException org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:265) org.apache.axiom.om.impl.traverse.OMChildrenQNameIterator.hasNext(OMChildrenQNameIterator.java:75) org.apache.axiom.om.impl.llom.OMElementImpl.getFirstChildWithName(OMElementImpl.java:222) org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getHeader(SOAPEnvelopeImpl.java:76) org.apache.axis2.engine.AxisEngine.createFaultMessageContext(AxisEngine.java:183) org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:168) org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:153) 
 javax.servlet.http.HttpServlet.service(HttpServlet.java:615)  javax.servlet.http.HttpServlet.service(HttpServlet.java:688) note The full stack trace of the root cause is available in the Apache Tomcat/5.5.9 logs. noshade="noshade"Apache Tomcat/5.5.9 So obviously I have done something wrong somewhere? As a further ado I also tried to build a client stub % sh WSDL2Java.sh -uri ../samples/build/classes/META-INF/Axis2SampleDocLitService.wsdl -d xmlbeans -o ../samples -p org.apache.axis2.userguide % jar.client I then wrote this simple client class: import org.apache.axis2.userguide.*; public class Client {  public static void main(String[] args) {  try {  Axis2SampleDocLitServiceStub stub =
 new Axis2SampleDocLitServiceStub(null, "http://localhost:8080/axis2/services/Axis2SampleDocLitService");  EchoStringParamDocument reqDoc = EchoStringParamDocument.Factory.newInstance();  reqDoc.setEchoStringParam("Axis2 Echo");  EchoStringReturnDocument resDoc = stub.EchoString(reqDoc);  System.out.println(resDoc.getEchoString());  } catch(Exception e)  {  e.printStackTrace();  }  } } which I am unable to compile with the following command: % javac -classpath

Re: [Axis2] Axis2SampleDocLitService not working.

2006-06-15 Thread Jan Bauer Nielsen


Hi,

There is an XBeans-packaged.jar which I added to classpath, but the 
errors still persist.


Jan

Ajith Ranabahu wrote:

Hi,
For XMLbeans you'll have to add the generated xsb files to the
classpath. if you've used the  jar.client ant target then there should
be xmlbeans-packaged.jar file in the build folder. Add that to the
classpath and that should solve the problem :)

Ajith

On 6/15/06, Jan Bauer Nielsen [EMAIL PROTECTED] wrote:

Hello.

I am an Axis2 novice and I am therefore trying to work my way through
the examples provided in the Axis2 userguide, but I am having getting
the data binding examples to work.

I am currently working on a debian sarge install with a Java 2 Standard
Edition (build 1.5.0_06-b05). Axis2 v1.0 is deployed on a Geronimo v1.0
web application server.

I created the skeleton using the following command:

% sh WSDL2Java.sh -uri ../samples/wsdl/Axis2SampleDocLit.wsdl -ss -sd -d
xmlbeans -o ../samples -p org.apache.axis2.userguide

I added the code suggested to Axis2SampleDocLitServiceSkeleton.java and
then ran

% ant jar.server

Finally I successfully deployed the service, I am not so sure it is
working though. Testing from SOAP::Lite gives me

Request:
  POST /axis2/services/Axis2SampleDocLitService HTTP/1.1 TE:
deflate,gzip;q=0.3 Connection: TE, close Accept: text/xml
Accept: multipart/*
Accept: application/soap
Host: localhost:8080
User-Agent: SOAP::Lite/Perl/0.67
Content-Length: 459
Content-Type: text/xml; charset=utf-8
SOAPAction: #echoString

?xml version=1.0 encoding=UTF-8?soap:Envelope
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
soap:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;soap:BodyechoStringechoStringParam 


xsi:type=xsd:stringAxis2
Echo/echoStringParam/echoString/soap:Body/soap:Envelope


Response:
HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1
Content-Type: text/html;charset=utf-8
Content-Length: 1901
Date: Thu, 15 Jun 2006 10:56:29 GMT
Connection: close

htmlheadtitleApache Tomcat/5.5.9 - Error
report/titlestyle!--H1
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} 


H2
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} 


H3
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} 


BODY
{font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;}
B
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} 


P
{font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A 


{color : black;}A.name {color : black;}HR {color : #525D76;}--/style
/headbodyh1HTTP Status 500 - /h1HR size=1
noshade=noshadepbtype/b Exception report/ppbmessage/b
u/u/ppbdescription/b uThe server encountered an internal
error () that prevented it from fulfilling this
request./u/ppbexception/b preorg.apache.axiom.om.OMException
org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:265) 

org.apache.axiom.om.impl.traverse.OMChildrenQNameIterator.hasNext(OMChildrenQNameIterator.java:75) 

org.apache.axiom.om.impl.llom.OMElementImpl.getFirstChildWithName(OMElementImpl.java:222) 

org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getHeader(SOAPEnvelopeImpl.java:76) 

org.apache.axis2.engine.AxisEngine.createFaultMessageContext(AxisEngine.java:183) 

org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:168) 


org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:153)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:615)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:688)
/pre/ppbnote/b uThe full stack trace of the root cause is
available in the Apache Tomcat/5.5.9 logs./u/pHR size=1
noshade=noshadeh3Apache Tomcat/5.5.9/h3/body/html

So obviously I have done something wrong somewhere?


As a further ado I also tried to build a client stub

% sh WSDL2Java.sh -uri
../samples/build/classes/META-INF/Axis2SampleDocLitService.wsdl -d
xmlbeans -o ../samples -p org.apache.axis2.userguide

% jar.client

I then wrote this simple client class:

import org.apache.axis2.userguide.*;

public class Client {
 public static void main(String[] args) {
 try {
 Axis2SampleDocLitServiceStub stub = new
Axis2SampleDocLitServiceStub(null,
http://localhost:8080/axis2/services/Axis2SampleDocLitService;);

 EchoStringParamDocument reqDoc =
EchoStringParamDocument.Factory.newInstance();

 reqDoc.setEchoStringParam(Axis2 Echo);
 EchoStringReturnDocument resDoc = stub.EchoString(reqDoc);
 System.out.println(resDoc.getEchoString());
 } catch(Exception e)  {
 e.printStackTrace();
 }
 }
}

which I am unable to compile with the following command:

% javac -classpath

[Axis2]can anyone spot a problem with this SOAP request?

Hi,The SOAP request is:POST /axis2/services/TTWSServiceService HTTP/1.0Content-Type: text/xml; charset=utf-8Accept: application/soap+xml, application/dime, multipart/related, text/*User-Agent: Axis/1.3Host: 127.0.0.1:Cache-Control: no-cachePragma: no-cacheSOAPAction: ""Content-Length: 623Authorization: Basic V0FMTUFSVDpXQUwxMjNNQVJU?xml version="1.0" encoding="UTF-8"?soapenv:Envelope 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:BodyTTIS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="VW_TrailerData_Request_Schema.xsd" TRAILERDATATRNRQ  TRNID/TRNID  TRAILERDATARQ
   TARGETASSETSTARGETALLY/TARGETALL   /TARGETASSETS   GETLATESTDATAY/GETLATESTDATA   COMPRESSY/COMPRESS  /TRAILERDATARQ /TRAILERDATATRNRQ/TTIS/soapenv:Body/soapenv:EnvelopeThis is actually being generated by an Axis 1 client, calling an Axis2 service. The service bombs out with the exception:ERROR [[AxisServlet]] Servlet.service() for servlet AxisServlet threw exceptionorg.apache.axiom.om.OMException at
 org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:265) at org.apache.axiom.om.impl.traverse.OMChildrenQNameIterator.hasNext(OMChildrenQNameIterator.java:75) at org.apache.axiom.om.impl.llom.OMElementImpl.getFirstChildWithName(OMElementImpl.java:222) at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getHeader(SOAPEnvelopeImpl.java:76) at org.apache.axis2.engine.AxisEngine.createFaultMessageContext(AxisEngine.java:183) at org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:168) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:153) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717).The stack trace makes me think there is something wrong with the SOAP envelope, but I can't see what it is. Any help is appreciated - I have to
 get this thing working urgently.Thanks! __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: [Axis2] Axis2SampleDocLitService not working.

2006-06-15 Thread Martin Gainty




Personally..I would try JAXRPC 
first(Doc-literal support came in later implementations)

Martin--
This email message and any files transmitted with it contain 
confidentialinformation intended only for the person(s) to whom this email 
message isaddressed. If you have received this email message in error, 
please notifythe sender immediately by telephone or email and destroy the 
originalmessage without making a copy. Thank you.

  - Original Message - 
  From: 
  Andrew 
  B 
  To: axis-user@ws.apache.org 
  Sent: Thursday, June 15, 2006 8:08 
  AM
  Subject: Re: [Axis2] 
  Axis2SampleDocLitService not working.
  Hi,I am having the same issue, with a different service 
  (a generated one). In my .aar, I have all the package subdirectories, 
  including schemaorg_apache_xmlbeans, directly under the top level of the jar 
  (no classes directory). The .xsb files should be in the classpath there, 
  right? (The .aar is an exploded deployment, which I have found to work so 
  far).I can elaborate more on the structure of the .aar if required - I 
  am desperate to get this problem solved.ThanksAjith 
  Ranabahu [EMAIL PROTECTED] wrote:
  Hi,For 
XMLbeans you'll have to add the generated xsb files to theclasspath. if 
you've used the jar.client ant target then there shouldbe 
xmlbeans-packaged.jar file in the build folder. Add that to theclasspath 
and that should solve the problem :)AjithOn 6/15/06, Jan 
Bauer Nielsen <[EMAIL PROTECTED]>wrote: Hello. I am an 
Axis2 novice and I am therefore trying to work my way through the 
examples provided in the Axis2 userguide, but I am having getting 
the data binding examples to work. I am currently working on 
a debian sarge install with a Java 2 Standard Edition (build 
1.5.0_06-b05). Axis2 v1.0 is deployed on a Geronimo v1.0 web 
application server. I created the skeleton using the 
following command: % sh WSDL2Java.sh -uri 
../samples/wsdl/Axis2SampleDocLit.wsdl -ss -sd -d xmlbeans -o 
../samples -p org.apache.axis2.userguide I added the code 
suggested to Axis2SampleDocLitServiceSkeleton.java and then 
ran % ant jar.server Finally I successfully 
deployed the service, I am not so sure it is working though. Testing 
from SOAP::Lite gives me Request: POST 
/axis2/services/Axis2SampleDocLitService HTTP/1.1 TE: 
deflate,gzip;q=0.3 Connection: TE, close Accept: text/xml Accept: 
multipart/* Accept: application/soap Host: 
localhost:8080 User-Agent: SOAP::Lite/Perl/0.67 
Content-Length: 459 Content-Type: text/xml; charset=utf-8 
SOAPAction: "#echoString"  
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" 
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" 
xsi:type="xsd:string"Axis2 
Echo 
Response: HTTP/1.1 500 Internal Server Error Server: 
Apache-Coyote/1.1 Content-Type: text/html;charset=utf-8 
Content-Length: 1901 Date: Thu, 15 Jun 2006 10:56:29 GMT 
Connection: close 

 
HTTP Status 500 - 

 noshade="noshade"
type Exception report
message 
description The server encountered an internal error 
() that prevented it from fulfilling this request.
exception org.apache.axiom.om.OMException org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:265) org.apache.axiom.om.impl.traverse.OMChildrenQNameIterator.hasNext(OMChildrenQNameIterator.java:75) org.apache.axiom.om.impl.llom.OMElementImpl.getFirstChildWithName(OMElementImpl.java:222) org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getHeader(SOAPEnvelopeImpl.java:76) org.apache.axis2.engine.AxisEngine.createFaultMessageContext(AxisEngine.java:183) org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:168) org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:153) 
 javax.servlet.http.HttpServlet.service(HttpServlet.java:615)  javax.servlet.http.HttpServlet.service(HttpServlet.java:688) 

note The full stack trace of the root cause is 
available in the Apache Tomcat/5.5.9 logs.

 noshade="noshade"
Apache Tomcat/5.5.9 So obviously I have done 
something wrong somewhere? As a further ado I also 
tried to build a client stub % sh WSDL2Java.sh -uri 
../samples/build/classes/META-INF/Axis2SampleDocLitService.wsdl -d 
xmlbeans -o ../samples -p org.apache.axis2.userguide % 
jar.client I then wrote this simple client 
class: import org.apache.axis2.userguide.*; 
public class Client { public static void main(String[] args) 
{ try { Axis2SampleDocLitServiceStub stub = new 
Axis2SampleDocLitServiceStub(null, 
"http://localhost:8080/axis2/services/Axis2SampleDocLitService"); 
EchoStringParamDocument reqDoc =

please remove me from list

2006-06-15 Thread ANDY FABEL

Hi,
Please remove me from mailing list
my address: [EMAIL PROTECTED]

Thank You,
Andy Fabel


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Documentation at http://ws.apache.org/axis2/1_0/userguide3.html

2006-06-15 Thread Janet Moyer


Hi folks,
I'm working through the Axis2 examples using the user's guide. Thanks for a 
great job. I have some suggestions which I hope are helpful.


1) It would really help if you could explain what WSDL2Java and Axis2 are 
doing, in a similar to manner to Xfire's documentation.  Specifically, the 
original WSDL only has a soap binding, but Axis  seems to provide a REST 
binding.  Is that what I should expect? Where did that come from? How do I 
control it? The REST binding is POST, what if I want GET?


2) The very first example makes reference to something called an OMElement. 
If this is the first time you've worked with Axis, you're not going to know 
what that is.  Yet the text claims that no explanation is necessary.  I'd 
suggest that the first example should simply use String parameters and 
return values; save OMwhatever for a more advanced example.  The reason for 
using these examples is to get a gut feeling for how the technology works, 
and to assess how complicated or easy it is to use. In keeping with this, 
the examples should start a simple as possible, and add on complexity ( and 
build up confidence) as you go.


Thanks again!

Regards,
Janet Moyer



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [SPAM] - [Axis2] Client cookie support - Bayesian Filter detected spam

2006-06-15 Thread Sai Arunachalam

Hey Davanum and Hariharasudhan, Thanks a lot for your inputs. I'll try it out and get back in case I have more questions. Thanks again!- Sai

Re: Axis Proxy client problem

2006-06-15 Thread siddbob siddbob






Hi,
 I am new in web services. I have one WSDLI havegenerated proxy from WSDL by using AXIS1.2
 
 Now I don't have clue how to generate or write Client program to use these proxy. I can send WSDL and generated proxy/stubs

 Thanks for help
Sid

Re: [Axis2] Axis2SampleDocLitService not working.

Title: Apache Tomcat/5.5.9 - Errorbr report
I'm an Axis2 novice, so I'm not sure what that means, or how it relates to the classpath issue (I will look up the terminology though).Martin Gainty [EMAIL PROTECTED] wrote: Personally..I would try JAXRPC first(Doc-literal support came in later implementations) Martin-- This email message and any files transmitted with it contain confidentialinformation intended only for the person(s) to whom this email message isaddressed. If you have received this email message in error,
please notifythe sender immediately by telephone or email and destroy the originalmessage without making a copy. Thank you.- Original Message -From:AndrewBTo: axis-user@ws.apache.orgSent: Thursday, June 15, 2006 8:08AM Subject: Re: [Axis2]Axis2SampleDocLitService not working. Hi,I am having the same issue, with a different service(a generated one). In my .aar, I have all the package subdirectories,including schemaorg_apache_xmlbeans,
directly under the top level of the jar(no classes directory). The .xsb files should be in the classpath there,right? (The .aar is an exploded deployment, which I have found to work sofar).I can elaborate more on the structure of the .aar if required - Iam desperate to get this problem solved.ThanksAjithRanabahu [EMAIL PROTECTED] wrote: Hi,For XMLbeans you'll have to add the generated xsb files to theclasspath. if you've used the jar.client ant target then there shouldbe xmlbeans-packaged.jar file in the build folder. Add that to theclasspath and that should solve the problem :)AjithOn 6/15/06, Jan Bauer Nielsen <[EMAIL PROTECTED]>wrote: Hello. I am an Axis2 novice and I am therefore trying to work my way
through the examples provided in the Axis2 userguide, but I am having getting the data binding examples to work. I am currently working on a debian sarge install with a Java 2 Standard Edition (build 1.5.0_06-b05). Axis2 v1.0 is deployed on a Geronimo v1.0 web application server. I created the skeleton using the following command: % sh WSDL2Java.sh -uri ../samples/wsdl/Axis2SampleDocLit.wsdl -ss -sd -d xmlbeans -o ../samples -p org.apache.axis2.userguide I added the code suggested to Axis2SampleDocLitServiceSkeleton.java and then ran __Do You Yahoo!?Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

Invoking Web Service With No Input Parameters Using Doc/Lit

2006-06-15 Thread Ted Jones




Has anyone had 
success invoking a web service with no input parameters using doc/lit in Axis 
1.3? When I do it I get an NPE in the bowels of Axis.

Thanks,
Ted

Re: [Axis2]wsdl2java error

2006-06-15 Thread kavithaa Rajavenkateshwaran

Hi,please find my wsdl below. Also i noticed that the MessageReceiverInOut used in one of the axis2 samples(doclitservice) had  some jar files within it's package and was refering to the parse method in that and  not to the org.apache.axiom.om.OMElement.Factory.parse(as the one in generated file).I copied that particular jar from the sample  and changed the method in my code,then it works.But this is not the right way.pl. let me know how to get the correct files generated from wsdl.wsdl?xml version="1.0" encoding="UTF-8"?wsdl:definitions targetNamespace="urn:fibonacci" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="urn:fibonacci" xmlns:intf="urn:fibonacci" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" wsdl:types  schema targetNamespace="urn:fibonacci" xmlns="http://www.w3.org/2001/XMLSchema"   import namespace="http://schemas.xmlsoap.org/soap/encoding/"/   complexType name="ArrayOf_xsd_int"    complexContent     restriction base="soapenc:Array"      attribute ref="soapenc:arrayType" wsdl:arrayType="xsd:int[]"/     /restriction    /complexContent   /complexType  /schema /wsdl:types   wsdl:message name="calculateFibonacciRangeResponse"      wsdl:part name="calculateFibonacciRangeReturn" type="impl:ArrayOf_xsd_int"/   /wsdl:message   wsdl:message name="calculateFibonacciRequest"      wsdl:part name="in0" type="xsd:int"/   /wsdl:message   wsdl:message name="calculateFibonacciRangeRequest"      wsdl:part name="in0" type="xsd:int"/      wsdl:part name="in1" type="xsd:int"/   /wsdl:message   wsdl:message name="calculateFibonacciResponse"      wsdl:part name="calculateFibonacciReturn" type="xsd:int"/   /wsdl:message   wsdl:portType name="Fibonacci"      wsdl:operation name="calculateFibonacci" parameterOrder="in0"         wsdl:input message="impl:calculateFibonacciRequest" name="calculateFibonacciRequest"/         wsdl:output message="impl:calculateFibonacciResponse" name="calculateFibonacciResponse"/      /wsdl:operation      wsdl:operation name="calculateFibonacciRange" parameterOrder="in0 in1"         wsdl:input message="impl:calculateFibonacciRangeRequest" name="calculateFibonacciRangeRequest"/         wsdl:output message="impl:calculateFibonacciRangeResponse" name="calculateFibonacciRangeResponse"/      /wsdl:operation   /wsdl:portType   wsdl:binding name="fibonacciSoapBinding" type="impl:Fibonacci"      wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/      wsdl:operation name="calculateFibonacci"         wsdlsoap:operation soapAction=""/         wsdl:input name="calculateFibonacciRequest"            wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:fibonacci" use="encoded"/         /wsdl:input         wsdl:output name="calculateFibonacciResponse"            wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:fibonacci" use="encoded"/         /wsdl:output      /wsdl:operation      wsdl:operation name="calculateFibonacciRange"         wsdlsoap:operation soapAction=""/         wsdl:input name="calculateFibonacciRangeRequest"            wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:fibonacci" use="encoded"/         /wsdl:input         wsdl:output name="calculateFibonacciRangeResponse"            wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:fibonacci" use="encoded"/         /wsdl:output      /wsdl:operation   /wsdl:binding   wsdl:service name="FibonacciService"      wsdl:port binding="impl:fibonacciSoapBinding" name="fibonacci"         wsdlsoap:address location="http://localhost:8080/axis2/services/fibonacci"/      /wsdl:port   /wsdl:service/wsdl:definitionsOn Jun 14, 2006, at 11:57 PM, Ajith Ranabahu wrote:Hi, Can you post your WSDL pleaseAjithOn 6/15/06, kavithaa Rajavenkateshwaran [EMAIL PROTECTED] wrote: Hi,I  files created using wsdl2java give compilation error.It seems likesome incompatibility in the MessageReceiverInOut code. Pl.  suggesthow to resolve this.symbol  : method newXMLStreamReader ()     [javac] location: interface org.apache.axiom.om.OMElement     [javac](org.apache.axiom.om.OMAbstractFactory.getOMFactory(),neworg.apache.axis2.util.StreamWrapper(param.newXMLStreamReader())) ;[javac]                                                    ^     [javac] /Users/kavithaarajavenkateshwaran/software/axis2/fib/src/trial/Fibonnaci/FibonacciServiceMessageReceiverInOut.java:125: cannotresolve symbol     [javac] symbol  : variable Factory     [javac] location: interface org.apache.axiom.om.OMElement     [javac]                  returnorg.apache.axiom.om.OMElement.Factory.parse(     [javac]                                                      ^     [javac]

RE: [Axis2] Maintaining Session Ticket

2006-06-15 Thread Brian Russell

Seems your interaction goes beyond a simple IN-OUT MEP. So if you want
to maintain this you can either define a custom MEP or use WS-Addressing
replyTo mechanism to pass your ticket here and there.

It looks as though I will have to come up with something custom for
passing tickets back and forth. This ticket is just some made up
string that would allow me to track that this is the same communication
session (along with some other things I can check) so that I can
verify that I'm talking to the same client, and where I am in the
communication process. 

As I had mentioned, I had hoped to do this using HttpSession, but I
don't think it's possible. I really have no knowledge of SOAP or any of
the guts of Axis.. so really want to just use it to serve my Web
Service while I worry about the business logic of what the service
actually is supposed to do.

I will have to look at WS-Adressing but as you said, I think my
implementation goes beyond just a simple IN-OUT MEP. The client is going
to make specific method calls (which contain this ticket string) to my
WS which I cannot change, so that's all I have to work with. 

Is your client also uses Axis2 as the client. setting
options.setManageSession(true), Axis2 client will automatically do it
without client being worried about it. But if the clients are using some
other clients, then they have to explicitly do this.

No. This is Intuit's client program that they developed and I have no
control over. 

In Axis2 we do not have static methods in MessageContext. If you wanna
access message context within your skeleton, read this :
http://www.wso2.net/kb/106.;

Thanks! This will likely be useful as I learn more of what my
capabilities are in Axis2.

Brian Russell
www.closerware.com 
 

-Original Message-
From: Eran Chinthaka [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, June 14, 2006 1:04 AM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] Maintaining Session Ticket

Brian Russell wrote:
   
 
 1.Has anyone worked with maintaining session specifically with
 regard to the Quickbooks Web Connector v.1.0.52 and Axis2 v.1.0 on
 Tomcat 5 (I'm using v.5.5.15)? 
 
 a.If not, does anyone have any suggestions for implementing this
 session maintenance by passing this ticket (which is just a String)
back
 to the client, who sends it back to the server on subsequent calls
until
 the final closing call? 

Before I answer this questions, let explain two concepts.

1. Using WS-Addressing, if some one gets reference parameters within
replyTo header, then he needs to send out thr reference parameters back
to the place in his response.
2. Depending on the number and direction of messages happening, we
define a message exchange pattern (MEP).

Seems your interaction goes beyond a simple IN-OUT MEP. So if you want
to maintain this you can either define a custom MEP or use WS-Addressing
replyTo mechanism to pass your ticket here and there.

Is your client also uses Axis2 as the client. setting
options.setManageSession(true), Axis2 client will automatically do it
without client being worried about it. But if the clients are using some
other clients, then they have to explicitly do this.

 
 2.I will most likely be needing to access the HttpSession in the
 skeleton class for my web service, based on what I've read in the
 archives, that would look something like this:
 MessageContext messageContext = MessageContext.getCurrentContext();

In Axis2 we do not have static methods in MessageContext. If you wanna
access message context within your skeleton, read this :
http://www.wso2.net/kb/106.

-- Chinthaka



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[axis1] more stable version of axis

2006-06-15 Thread michel.lequim

Title: [axis1] more stable version of axis






Dear axis users, 


we are to plan here to use axis in production but we are not sure about the version we will use, I hope 

someone can help us. We think axis 2 is not enough stable, too recent release and some bugs are still found (by example

for the timeout configuration which is a feature we really need). We then hesitate between axis 1.2 to 1.4, 

axis 1.4 seems to be also very recent so we plan to use axis 1.3.


Do you think it is a good choice ? 


thanks in advance



= = = = = = = = = = = = = = = = = = = = = = = = =
Fortis Bank disclaimer :
http://www.fortisbank.be/legal/disclaimer.htm

Fortis Bank privacy policy :
http://www.fortisbank.be/legal/privacy_policy.htm
= = = = = = = = = = = = = = = = = = = = = = = = =


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [Axis2] Maintaining Session Ticket

2006-06-15 Thread Brian Russell

Your ticket is handled at the
application level where the ticket is passed to the application (the
service class) and then the business logic code checks for the
compatibility of the ticket ?

Yes.. true. I have to implement specific method calls on my web service.
The first method called by the client authenticates them.. then I give
them back a ticket string. Then the client calls a possible 5 other
methods which are always receiving the ticket string which I sent to
the client. I have no control over the client as it was developed by
Intuit and I'm just implementing my Web Service to fit their wsdl. 

If so you would not be able to use the addressing reference properties
to make it work. Addressing reference properties are a means of
handling sessions and other stuff without the application being aware!

Unfortunately I guess this seems to be the case. Because of the
requirements of the methods that the client is expecting to call, I will
have to handle the session maintenance and ticket tracking within the
application itself. 

Attached is the wsdl I have to implement for my Web Service, but here is
a basic breakdown of the methods that the client calls, so you can see
why I have to handle everything in the app:

- public java.lang.String[] authenticate(java.lang.String strUserName,
java.lang.String strPassword)
- public java.lang.String sendRequestXML(java.lang.String ticket,
java.lang.String strHCPResponse, java.lang.String strCompanyFileName,
java.lang.String qbXMLCountry, int qbXMLMajorVers, int qbXMLMinorVers)
- public int receiveResponseXML(java.lang.String ticket,
java.lang.String response, java.lang.String hresult, java.lang.String
message)
- public java.lang.String connectionError(java.lang.String ticket,
java.lang.String hresult, java.lang.String message)
- public java.lang.String getLastError(java.lang.String ticket)
- public java.lang.String closeConnection(java.lang.String ticket)

Brian Russell
www.closerware.com 
 

-Original Message-
From: Ajith Ranabahu [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, June 14, 2006 1:55 AM
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Subject: Re: [Axis2] Maintaining Session Ticket

Hi,
Lemme get your problem first :) Your ticket is handled at the
application level where the ticket is passed to the application (the
service class) and then the business logic code checks for the
compatibility of the ticket ?
If so you would not be able to use the addressing reference properties
to make it work. Addressing reference properties are a means of
handling sessions and other stuff without the application being aware!

Ajith

On 6/14/06, Eran Chinthaka [EMAIL PROTECTED] wrote:
 Brian Russell wrote:
 
 
  1.Has anyone worked with maintaining session specifically with
  regard to the Quickbooks Web Connector v.1.0.52 and Axis2 v.1.0 on
  Tomcat 5 (I'm using v.5.5.15)?
 
  a.If not, does anyone have any suggestions for implementing this
  session maintenance by passing this ticket (which is just a String)
back
  to the client, who sends it back to the server on subsequent calls
until
  the final closing call?

 Before I answer this questions, let explain two concepts.

 1. Using WS-Addressing, if some one gets reference parameters within
 replyTo header, then he needs to send out thr reference parameters
back
 to the place in his response.
 2. Depending on the number and direction of messages happening, we
 define a message exchange pattern (MEP).

 Seems your interaction goes beyond a simple IN-OUT MEP. So if you want
 to maintain this you can either define a custom MEP or use
WS-Addressing
 replyTo mechanism to pass your ticket here and there.

 Is your client also uses Axis2 as the client. setting
 options.setManageSession(true), Axis2 client will automatically do it
 without client being worried about it. But if the clients are using
some
 other clients, then they have to explicitly do this.

 
  2.I will most likely be needing to access the HttpSession in the
  skeleton class for my web service, based on what I've read in the
  archives, that would look something like this:
  MessageContext messageContext = MessageContext.getCurrentContext();

 In Axis2 we do not have static methods in MessageContext. If you wanna
 access message context within your skeleton, read this :
 http://www.wso2.net/kb/106.

 -- Chinthaka






-- 
Ajith Ranabahu

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


QBWebConnectorSvc.wsdl
Description: Binary data
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

callback web service

2006-06-15 Thread Plorks mail




hi all

does anyone have an example or a good tutorial of a Callback webservice 
(server and client) / calling a web service asynchronously that could show 
me?


many thanks for your help

_
Are you using the latest version of MSN Messenger? Download MSN Messenger 
7.5 today! http://join.msn.com/messenger/overview



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: callback web service

2006-06-15 Thread James Clinton

See the IBM developworks site.

-Original Message-
From: Plorks mail [mailto:[EMAIL PROTECTED] 
Sent: 15 June 2006 16:06
To: axis-user@ws.apache.org
Subject: callback web service

hi all

does anyone have an example or a good tutorial of a Callback webservice 
(server and client) / calling a web service asynchronously that could
show 
me?

many thanks for your help

_
Are you using the latest version of MSN Messenger? Download MSN
Messenger 
7.5 today! http://join.msn.com/messenger/overview

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
THE INFORMATION IN THIS E-MAIL AND IN ANY ATTACHMENTS IS CONFIDENTIAL

AND MAY BE PRIVILEGED OR OTHERWISE PROTECTED FROM DISCLOSURE. 
IF YOU ARE NOT THE INTENDED RECIPIENT AND HAVE RECEIVED IT IN ERROR YOU ARE ON 
NOTICE OF ITS STATUS. 
PLEASE NOTIFY THE SENDER IMMEDIATELY BY RETURN EMAIL AND THEN DELETE THIS EMAIL 
AND ANY ATTACHMENT FROM YOUR SYSTEM. 
YOU MUST NOT RETAIN, COPY OR USE THIS E-MAIL OR ANY ATTACHMENT FOR ANY PURPOSE, 
NOR DISCLOSE ALL OR ANY PART OF ITS CONTENTS TO ANY OTHER PERSON: 

TO DO SO COULD BE A BREACH OF CONFIDENCE

EMAIL MAY BE SUSCEPTIBLE TO DATA CORRUPTION, INTERCEPTION AND UNAUTHORISED 
AMENDMENT, 
AND WE DO NOT ACCEPT LIABILITY FOR ANY SUCH CORRUPTION, INTERCEPTION OR 
AMENDMENT OR THE CONSEQUENCES THEREOF. 

WE MAY MONITOR THE CONTENT OF EMAILS SENT AND RECEIVED VIA OUR NETWORK FOR 
VIRUSES OR UNAUTHORISED USE AND FOR OTHER LAWFUL BUSINESS PURPOSES. 
WE DO NOT ACCEPT RESPONSIBILITY FOR ANY LOSS OR DAMAGE ARISING FROM A VIRUS IN 
ANY EMAIL OR ATTACHMENT.

---
[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: callback web service

2006-06-15 Thread Hariharasudhan.D Dhakshinamoorthy


Dude !!

Axis2 has support for multiple transports , and has a transport In And
Transport Out option , just take a look at them.or you can use JAXM.

~~~ Enjoy Life ~


On 6/15/06, Plorks mail [EMAIL PROTECTED] wrote:



hi all

does anyone have an example or a good tutorial of a Callback webservice
(server and client) / calling a web service asynchronously that could show
me?

many thanks for your help

_
Are you using the latest version of MSN Messenger? Download MSN Messenger
7.5 today! http://join.msn.com/messenger/overview


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: callback web service

2006-06-15 Thread Plorks mail





thanks - i'll do a search on their site






From: James Clinton [EMAIL PROTECTED]
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: RE: callback web service
Date: Thu, 15 Jun 2006 16:09:02 +0100

See the IBM developworks site.

-Original Message-
From: Plorks mail [mailto:[EMAIL PROTECTED]
Sent: 15 June 2006 16:06
To: axis-user@ws.apache.org
Subject: callback web service




hi all

does anyone have an example or a good tutorial of a Callback webservice
(server and client) / calling a web service asynchronously that could
show
me?

many thanks for your help

_
Are you using the latest version of MSN Messenger? Download MSN
Messenger
7.5 today! http://join.msn.com/messenger/overview


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
THE INFORMATION IN THIS E-MAIL AND IN ANY ATTACHMENTS IS CONFIDENTIAL

AND MAY BE PRIVILEGED OR OTHERWISE PROTECTED FROM DISCLOSURE.
IF YOU ARE NOT THE INTENDED RECIPIENT AND HAVE RECEIVED IT IN ERROR YOU ARE 
ON NOTICE OF ITS STATUS.
PLEASE NOTIFY THE SENDER IMMEDIATELY BY RETURN EMAIL AND THEN DELETE THIS 
EMAIL AND ANY ATTACHMENT FROM YOUR SYSTEM.
YOU MUST NOT RETAIN, COPY OR USE THIS E-MAIL OR ANY ATTACHMENT FOR ANY 
PURPOSE, NOR DISCLOSE ALL OR ANY PART OF ITS CONTENTS TO ANY OTHER PERSON:


TO DO SO COULD BE A BREACH OF CONFIDENCE

EMAIL MAY BE SUSCEPTIBLE TO DATA CORRUPTION, INTERCEPTION AND UNAUTHORISED 
AMENDMENT,
AND WE DO NOT ACCEPT LIABILITY FOR ANY SUCH CORRUPTION, INTERCEPTION OR 
AMENDMENT OR THE CONSEQUENCES THEREOF.


WE MAY MONITOR THE CONTENT OF EMAILS SENT AND RECEIVED VIA OUR NETWORK FOR 
VIRUSES OR UNAUTHORISED USE AND FOR OTHER LAWFUL BUSINESS PURPOSES.
WE DO NOT ACCEPT RESPONSIBILITY FOR ANY LOSS OR DAMAGE ARISING FROM A VIRUS 
IN ANY EMAIL OR ATTACHMENT.


---
[EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



_
The new MSN Search Toolbar now includes Desktop search! 
http://join.msn.com/toolbar/overview



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: callback web service

2006-06-15 Thread Plorks mail




we're using axis 1.1, we haven't upgraded yet, so unfortunately can't take 
that option






From: Hariharasudhan.D Dhakshinamoorthy [EMAIL PROTECTED]
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: Re: callback web service
Date: Thu, 15 Jun 2006 08:14:43 -0700

Dude !!

Axis2 has support for multiple transports , and has a transport In And
Transport Out option , just take a look at them.or you can use JAXM.

~~~ Enjoy Life ~


On 6/15/06, Plorks mail [EMAIL PROTECTED] wrote:



hi all

does anyone have an example or a good tutorial of a Callback webservice
(server and client) / calling a web service asynchronously that could show
me?

many thanks for your help

_
Are you using the latest version of MSN Messenger? Download MSN Messenger
7.5 today! http://join.msn.com/messenger/overview


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



_
Are you using the latest version of MSN Messenger? Download MSN Messenger 
7.5 today! http://join.msn.com/messenger/overview



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: please remove me from list

2006-06-15 Thread Hariharasudhan.D Dhakshinamoorthy


Andy !!!

you should be sending mail to [EMAIL PROTECTED] :-)


May i know the reasion behind you leaving :(

On 6/15/06, ANDY FABEL [EMAIL PROTECTED] wrote:


Hi,
 Please remove me from mailing list
 my address: [EMAIL PROTECTED]

 Thank You,
 Andy Fabel
   - To
unsubscribe, e-mail: [EMAIL PROTECTED] For additional
commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[AXis2] best version to be on production

2006-06-15 Thread kavithaa Rajavenkateshwaran


Hi,

We are thinking about using axis in production. I tried with  the  
latest release in axis1.x and axis2.
Axis1.x seems to   be much more stable. But not sure.Can some suggest  
me which version to go with.


Thanks,
Kavithaa

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [AXis2] best version to be on production

2006-06-15 Thread Nicolas Guaneme


kavithaa Rajavenkateshwaran wrote:


Hi,

We are thinking about using axis in production. I tried with  the  
latest release in axis1.x and axis2.
Axis1.x seems to   be much more stable. But not sure.Can some suggest  
me which version to go with.


Thanks,
Kavithaa

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Hi, I prefer Axis 1 beacause you can find more doc and examples for 
develop and support... I work with Axis 1 in production easy and stable.



Nicolás G. Rico



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Axis2 Deployment Model Deficiency

2006-06-15 Thread Junaid . Bhatra

Dims,

I tried the latest nightly from 06-15. It still does not work. I simply
took the axis2.war, renamed addressing-SNAPSHOT.mar inside it to
addressing.mar, and deployed it in WebLogic 9.1. It gave me the following
error on startup about not being able to load the referenced addressing
module. I then removed the addressing module reference from axis2.xml and
tried it again. It came up fine now, but I still don't see the Version
service, which is part of Axis2.war, in the Axis admin console.

I took a peek at the source code in WarBasedAxisConfigurator. I don't see
any code that handles the case when getServletContext().getRealPath()  ==
null. So it looks like this is not yet implemented.

Here's the error about not being able to load the addressing module:

Jun 15, 2006 11:38:32 AM EDT Error HTTP BEA-101216 Servlet:
AxisServlet failed to preload
 on startup in Web application: axis2.war.
org.apache.axis2.deployment.DeploymentException: Trying to engage a module
which is not available :
addressing; nested exception is:
org.apache.axis2.AxisFault: Trying to engage a module which is not
available : addressing
at
org.apache.axis2.deployment.DeploymentEngine.loadFromClassPath(DeploymentEngine.java:147)

at
org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisCon
figurator.java:213)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(Configura
tionContextFactory.java:56)
at
org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:235)
at
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:203)
Truncated. see log file for complete stacktrace
org.apache.axis2.AxisFault: Trying to engage a module which is not
available : addressing
at
org.apache.axis2.engine.AxisConfiguration.engageModule(AxisConfiguration.java:301)
at
org.apache.axis2.deployment.DeploymentEngine.engageModules(DeploymentEngine.java:766)
at
org.apache.axis2.deployment.DeploymentEngine.loadFromClassPath(DeploymentEngine.java:143)

at
org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisCon
figurator.java:213)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(Configura
tionContextFactory.java:56)

Thanks,
Junaid




   
 Davanum  
 Srinivas 
 [EMAIL PROTECTED]  To 
 maxis-user@ws.apache.org 
cc 
 06/14/2006 11:43  
 AMSubject 
   Re: Axis2 Deployment Model  
   Deficiency  
 Please respond to 
 [EMAIL PROTECTED] 
  he.org   
   
   
   




Junaid,

Did you try latest nightly? I believe this is fixed.

thanks,
dims

On 6/14/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

 Hi,

 Here's my scenario which I believe might be a common requirement for a
lot
 of enterprise applications. I'm trying to bundle Axis2 webapp as part of
a
 bigger EAR application and deploy in an application server such as
 WebLogic. I would like to package up all of the Web Services inside of
the
 webapp/EAR file. The problem is that Axis2 cannot seem to load the
services
 from within the EAR file in WebLogic..

 The issue arises due to the fact that Axis2 relies on the concept of a
 repository, which MUST be a folder on the file system. On certain
 application servers like WebSphere, this is not an issue since they
 internally explode the EAR when you deploy it and Axis2 does not seem to
 have a problem. However application servers like WebLogic do NOT explode
 the EAR, hence Axis2 cannot find/load the services from the repository.

 Here is the offending code in WarBasedAxisConfigurator:

 repository =
 config.getServletContext().getRealPath(/WEB-INF);  --- this returns
null
 in Weblogic
 axis2Steram = new FileInputStream(repository +
 /conf/axis2.xml);

 There are 2 work-arounds as I understand it:
 1) Always deploy the application in an exploded format (WebLogic provides
 this feature). However this is not

Re: Axis2 Deployment Model Deficiency

2006-06-15 Thread Davanum Srinivas


Could u please log a bug so that we can track it?

thanks,
dims

On 6/15/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

Dims,

I tried the latest nightly from 06-15. It still does not work. I simply
took the axis2.war, renamed addressing-SNAPSHOT.mar inside it to
addressing.mar, and deployed it in WebLogic 9.1. It gave me the following
error on startup about not being able to load the referenced addressing
module. I then removed the addressing module reference from axis2.xml and
tried it again. It came up fine now, but I still don't see the Version
service, which is part of Axis2.war, in the Axis admin console.

I took a peek at the source code in WarBasedAxisConfigurator. I don't see
any code that handles the case when getServletContext().getRealPath()  ==
null. So it looks like this is not yet implemented.

Here's the error about not being able to load the addressing module:

Jun 15, 2006 11:38:32 AM EDT Error HTTP BEA-101216 Servlet:
AxisServlet failed to preload
 on startup in Web application: axis2.war.
org.apache.axis2.deployment.DeploymentException: Trying to engage a module
which is not available :
addressing; nested exception is:
org.apache.axis2.AxisFault: Trying to engage a module which is not
available : addressing
at
org.apache.axis2.deployment.DeploymentEngine.loadFromClassPath(DeploymentEngine.java:147)

at
org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisCon
figurator.java:213)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(Configura
tionContextFactory.java:56)
at
org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:235)
at
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:203)
Truncated. see log file for complete stacktrace
org.apache.axis2.AxisFault: Trying to engage a module which is not
available : addressing
at
org.apache.axis2.engine.AxisConfiguration.engageModule(AxisConfiguration.java:301)
at
org.apache.axis2.deployment.DeploymentEngine.engageModules(DeploymentEngine.java:766)
at
org.apache.axis2.deployment.DeploymentEngine.loadFromClassPath(DeploymentEngine.java:143)

at
org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisCon
figurator.java:213)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(Configura
tionContextFactory.java:56)

Thanks,
Junaid





 Davanum
 Srinivas
 [EMAIL PROTECTED]  To
 maxis-user@ws.apache.org
cc
 06/14/2006 11:43
 AMSubject
   Re: Axis2 Deployment Model
   Deficiency
 Please respond to
 [EMAIL PROTECTED]
  he.org







Junaid,

Did you try latest nightly? I believe this is fixed.

thanks,
dims

On 6/14/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

 Hi,

 Here's my scenario which I believe might be a common requirement for a
lot
 of enterprise applications. I'm trying to bundle Axis2 webapp as part of
a
 bigger EAR application and deploy in an application server such as
 WebLogic. I would like to package up all of the Web Services inside of
the
 webapp/EAR file. The problem is that Axis2 cannot seem to load the
services
 from within the EAR file in WebLogic..

 The issue arises due to the fact that Axis2 relies on the concept of a
 repository, which MUST be a folder on the file system. On certain
 application servers like WebSphere, this is not an issue since they
 internally explode the EAR when you deploy it and Axis2 does not seem to
 have a problem. However application servers like WebLogic do NOT explode
 the EAR, hence Axis2 cannot find/load the services from the repository.

 Here is the offending code in WarBasedAxisConfigurator:

 repository =
 config.getServletContext().getRealPath(/WEB-INF);  --- this returns
null
 in Weblogic
 axis2Steram = new FileInputStream(repository +
 /conf/axis2.xml);

 There are 2 work-arounds as I understand it:
 1) Always deploy the application in an exploded format (WebLogic provides
 this feature). However this is not an option for us.
 2) Use a repository folder OUTSIDE of the EAR by specifiying the
 axis2.xml.path in web.xml. However this option also poses a problem in a
 cluster scenario where you need to have a common accessible folder, which
 will serve as the repository and EVERY machine in the cluster must be
 mapped to this common folder. It's a setup  maintenance headache.

 I worked previously with Axis 1.x and it did not have a problem loading
 services from within the EAR file. Ofcourse any changes you make to the

RE: [axis2] dynamic client invocation w/o intermediate classgeneration

2006-06-15 Thread Tony Dean

Sanjiva,

Can you speak to what Dims eluded to... how to use complexTypes w/o generating 
helper classes to perform serialization/deserialization.  I want to do what 
WSIF and JROM started out to do.

Also, with the current ServiceClient API, I don't see a way distinquish between 
the style of service that you want to invoke.  Basically, you just pass in an 
OMElement as the payload.  I used WSDL2Java to see what kind of code would be 
generated from a simple RPC stockquote wsdl.  The wsdl is as follows:

?xml version='1.0' encoding='UTF-8'?
definitions name='net.xmethods.services.stockquote.StockQuote' 
 
targetNamespace='http://www.themindelectric.com/wsdl/net.xmethods.services.stockquote.StockQuote/'
 
 
xmlns:tns='http://www.themindelectric.com/wsdl/net.xmethods.services.stockquote.StockQuote/'
 
 xmlns:electric='http://www.themindelectric.com/' 
 xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' 
 xmlns:xsd='http://www.w3.org/2001/XMLSchema' 
 xmlns:soapenc='http://schemas.xmlsoap.org/soap/encoding/' 
 xmlns:wsdl='http://schemas.xmlsoap.org/wsdl/' 
 xmlns='http://schemas.xmlsoap.org/wsdl/'

   message name='getQuoteResponse1'
  part name='Result' type='xsd:float'/
   /message

   message name='getQuoteRequest1'
  part name='symbol' type='xsd:string'/
   /message

   portType name='net.xmethods.services.stockquote.StockQuotePortType'
  operation name='getQuote' parameterOrder='symbol'
 input message='tns:getQuoteRequest1'/
 output message='tns:getQuoteResponse1'/
  /operation
   /portType

   binding name='net.xmethods.services.stockquote.StockQuoteBinding' 
type='tns:net.xmethods.services.stockquote.StockQuotePortType'
  soap:binding style='rpc' 
transport='http://schemas.xmlsoap.org/soap/http'/
  operation name='getQuote'
 soap:operation soapAction='urn:xmethods-delayed-quotes#getQuote'/
 input
soap:body use='encoded' 
   namespace='urn:xmethods-delayed-quotes' 
   
encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'/
 /input
 output
soap:body use='encoded' 
   namespace='urn:xmethods-delayed-quotes' 
   
encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'/
 /output
  /operation
   /binding

   service name='net.xmethods.services.stockquote.StockQuoteService'
  documentationnet.xmethods.services.stockquote.StockQuote web 
service/documentation
  port name='net.xmethods.services.stockquote.StockQuotePort' 
binding='tns:net.xmethods.services.stockquote.StockQuoteBinding'
 soap:address location='http://64.124.140.30:9090/soap'/
 !-- soap:address location='http://localhost:/soap'/ --
  /port
   /service
/definitions

Axis2 ADB generated coded that produces the following client invocation stream:

?xml version='1.0' encoding='UTF-8'?
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
 soapenv:Header /
 soapenv:Body
  ns1:getQuote 
xmlns:ns1=http://www.themindelectric.com/wsdl/net.xmethods.services.stockquote.StockQuote/;
   symbolIBM/symbol
  /ns1:getQuote
 /soapenv:Body
/soapenv:Envelope

This is wrong.  First, for rpc style services, the namespace of the wrapper 
element (operation) must be specified with the binding soap:body extension 
namespace attribute.  In the wsdl above, this namespace is 
urn:xmethods-delayed-quotes.  Second, since use is encoded, don't you have to 
encode the data that you send?  A correct stream would look something like this:


?xml version=1.0 encoding=UTF-8?
soapenv:Envelope 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:Body
  ns1:getQuote 
soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 
xmlns:ns1=urn:xmethods-delayed-quotes
   ns1:symbol xsi:type=xsd:stringIBM/ns1:symbol
  /ns1:getQuote
 /soapenv:Body
/soapenv:Envelope



It seems that with Axis2 everything is treated as a document with literal 
encoding.  That is, both input/output of ServiceClient invocation is OMElement. 
 And is it the user's responsibility to encode the data if necessary 
(use=encoded) within the payload?  Hopefully, not.  In the old Axis 1.x 
codebase, you could pass in input data (along with type) and set the operation 
style that you wanted to use. How do you do this in Axis2?  What is the new 
paradigm here for client invocation such that I can code a client with a given 
set of data and work with services that are designed as rpc/literal, 
rpc/encoded, doc/literal, or doc/literal/wrapped?

And my initial question was... if I have custom complexTypes, can I get Axis2 
to interact with them some way without generating the helper classes.  I want 
to perform dynamic generation.

Please, help to

Axis-schema.jar in 1.3 axis

2006-06-15 Thread Flores, Raul

Title: Axis-schema.jar in 1.3 axis







axis-schema.jar



Can anyone tell me where this jar came from? Who owns it / what license it is being distributed under?



Thanks,


Raul Flores

Lockheed Martin Aeronautics Company

AxisServlet returns And now... Some Services only (blank page)

2006-06-15 Thread Ben Ethridge

Hi.

Ive spent several hours now, on google and yahoo attempting
to track down why AxisServlet is returning just a blank page with And
now... Some Services on it. Looking at the logs in tomcat shows no error
(or warning or info) about what might be the problem. Google was
uncharacteristically useless on this one, but I found some hints on Yahoo using
a search term of:

And now... Some Services blank

This was the best hint so far:

http://java2.5341.com/msg/8859.html

My symptoms are exactly as stated in the above. I can remove
all the packages and classes in my web service deployment and I then get more reasonable
errors, i.e. ClassNotFoundException and such. Also, I can remove the
offending service entirely from the server-config.wsdd, at which point
Axis behaves normally, showing the usual set of installed Axis services when I
call the AxisServlet, so its clearly a problem in my service or
classes or classpath, but Axis isnt giving me a clue as to what
the problem is.

This is running ok in my Eclipse set-up, but its set
up somewhat differently there.

Im guessing that there is some subtle library version
problem or classpath problem, and Ive been tinkering with both for many
hours with no success yet.

Any ideas on what might be causing this or how I can narrow
down the problem?

Ive tried to turn on DEBUG logging for axis, but no
success with that yet either. Is there a way to do that?

My setup is as follows:

Axis 1.2.1

Tomcat 5.5.17

Java 1.5.0_07

Linux Redhat 3.4.5-2, which if I remove my custom JAVA_HOME to
JDK1.5 shows java version 1.4.2

From the Yahoo search results, people seem to be finding their
solution tinkering and blind luck, so hopefully were missing something
simple about Axis deployment, yes?

Ben

Thank you.

RE: AxisServlet returns And now... Some Services only (blank page)

2006-06-15 Thread McCauley, Tim

Not
sure if this will help. I just ran into the same problem and move the
saaj.jar and jaxrpc.jar to the TOMCAT_HOME/common/lib/endorsed. I read in
the install documentation for Axis that this might be necessary for Tomcat 4 and
Java 1.4 so I tried it and it worked. I am running Tomcat 5.0.28 and Java
1.4.2.08 on a windows box.

Tim

-Original Message-From: Ben Ethridge
[mailto:[EMAIL PROTECTED]Sent: Thursday, June 15, 2006 1:19
PMTo: axis-user@ws.apache.orgSubject: AxisServlet
returns "And now... Some Services" only (blank page)

Hi.

Ive spent several hours now, on
google and yahoo attempting to track down why AxisServlet is returning just a
blank page with And now... Some Services on it. Looking at the logs in
tomcat shows no error (or warning or info) about what might be the problem.
Google was uncharacteristically useless on this one, but I found some hints on
Yahoo using a search term of:

And now... Some Services
blank

This was the best hint so
far:

http://java2.5341.com/msg/8859.html

My symptoms are exactly as stated
in the above. I can remove all the packages and classes in my web service
deployment and I then get more reasonable errors, i.e.
ClassNotFoundException and such. Also, I can remove the offending
service entirely from the server-config.wsdd, at which point Axis
behaves normally, showing the usual set of installed Axis services when I call
the AxisServlet, so its clearly a problem in my service or
classes or classpath, but Axis isnt giving me a clue as to what the
problem is.

This is running ok in my Eclipse
set-up, but its set up somewhat differently there.

Im guessing that there is some
subtle library version problem or classpath problem, and Ive been tinkering
with both for many hours with no success yet.

Any ideas on what might be causing
this or how I can narrow down the problem?

Ive tried to turn on DEBUG
logging for axis, but no success with that yet either. Is there a way to do
that?

My setup is as
follows:

Axis
1.2.1
Tomcat
5.5.17
Java
1.5.0_07
Linux Redhat 3.4.5-2, which if I
remove my custom JAVA_HOME to JDK1.5 shows java version
1.4.2

From the Yahoo search results,
people seem to be finding their solution tinkering and blind luck, so
hopefully were missing something simple about Axis deployment,
yes?

Ben

Thank you.

Re: [Axis2]wsdl schema type generation bug with byte[]- More bugs??

2006-06-15 Thread Anamitra . Bhattacharyya

Hi Deepal
Any update on the byte[] side? If this is a bug should I go ahead and
create a JIRA.

thanks
Anamitra


   
 Deepal Jayasinghe 
 [EMAIL PROTECTED] 
 e.lk  To 
   axis-user@ws.apache.org 
 06/08/2006 05:35   cc 
 AM
   Subject 
   Re: [Axis2]wsdl schema type 
 Please respond to generation bug with byte[]- More
 [EMAIL PROTECTED] bugs??  
  he.org   
   
   
   
   
   




Hi Anamitra;
I wrote a service implementation class with your method , and then I
generated the code and invoke the service and I got the following
response. So I can not find any bug can you please check the current
code base and let me know.

 MemberServiceStub stub = new MemberServiceStub();
MemberServiceStub.ProcessData req = new
MemberServiceStub.ProcessData();
req.setExtsysName(Deepal);
req.setIfaceName(123);
req.setXmldata(MXINVBALInterfacehello/MXINVBALInterface);
MemberServiceStub.ProcessDataResponse res = stub.processData(req);
System.out.println(res =  + res.get_return());

Out put was res = MXINVBALInterfacehello/MXINVBALInterface


And the service impl class look like;
  public String processData(String ifaceName, String extsysName, String
xmldata) {
return xmldata;
}


[EMAIL PROTECTED] wrote:

Hi
This is in contunuation of the prev mail. I changed my method signature to
take in String instead of byte[]
public String processData(String ifaceName, String extsysName, String
xmldata)

and the schema generated was as below

xs:element name=processData
- xs:complexType
  - xs:sequence
  xs:element type=xs:string name=ifaceName /
  xs:element type=xs:string name=extsysName /
  xs:element type=xs:string name=xmldata /
  /xs:sequence
/xs:complexType
  /xs:element
and the xml that I tried from client was

m:processData xmlns:m=http://testws.iface.psdi/xsd;
  ifaceNameanna111/ifaceName
  extsysName22/extsysName
  xmldataMXINVBALInterfacehello/MXINVBALInterface/xmldata
/m:processData

but when I printed in the service I got
anna111,22,

But if I try with no xml tags - it works good
m:processData xmlns:m=http://testws.iface.psdi/xsd;
  ifaceNameanna111/ifaceName
  extsysName22/extsysName
  xmldatahello/xmldata
/m:processData

and the o/p is
anna111,22,hello


Again is this a bug? or my bad?

thanks
Anamitra





 Anamitra.Bhattach

 [EMAIL PROTECTED]

To

 06/07/2006 04:39  axis-user@ws.apache.org

 PM cc



   Subject

 Please respond to [Axis2]wsdl schema type generation

 [EMAIL PROTECTED] bug with byte[]

  he.org
















Hi
I have a service with an operation whose signature reads like this

public String processData(String ifaceName, String extsysName, byte[]
xmldata)

when I deploy this service the wsdl generated will show the schema element
as below. The byte[] data type has been represented as
xs:element minOccurs=0 type=xs:byte name=xmldata
maxOccurs=unbounded
This is not how its supposed to represent this byte[] data
type as per jax rpc its supposed to be xs:base64Binary.
Is this a bug - or I am missing something.

xs:element name=processData
- xs:complexType
  - xs:sequencename=ifaceName /name=extsysName
/type=xs:byte name=xmldata
maxOccurs=unbounded //xs:sequence
thanks
Anamitra


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: AxisServlet returns And now... Some Services only (blank page)

2006-06-15 Thread Ben Ethridge









Same error when I moved them from axis/lib.




Did you mean common/endorsed or
common/lib/endorsed?



Unless there are other suggestions, next Im
going to try the Advanced Installation as per apache axis
install.html. This is how I have it set up and running ok in Eclipse. (I
currently have it set up the basic way, as per that same install.html.)



Ben











From: Ben Ethridge 
Sent: Thursday, June 15, 2006 1:53
PM
To: axis-user@ws.apache.org
Subject: RE: AxisServlet returns
And now... Some Services only (blank page)





Thanks. From where did you move them?



Ben











From: McCauley, Tim
[mailto:[EMAIL PROTECTED] 
Sent: Thursday, June 15, 2006 1:27
PM
To: axis-user@ws.apache.org
Subject: RE: AxisServlet returns
And now... Some Services only (blank page)







Not sure if this will help. I just
ran into the same problem and move the saaj.jar and jaxrpc.jar to the
TOMCAT_HOME/common/lib/endorsed. I read in the install documentation for
Axis that this might be necessary for Tomcat 4 and Java 1.4 so I tried it and
it worked. I am running Tomcat 5.0.28 and Java 1.4.2.08 on a windows box.











Tim





-Original Message-
From: Ben Ethridge
[mailto:[EMAIL PROTECTED]
Sent: Thursday, June 15, 2006 1:19
PM
To: axis-user@ws.apache.org
Subject: AxisServlet returns And
now... Some Services only (blank page)

Hi.



Ive spent several hours now, on google and yahoo
attempting to track down why AxisServlet is returning just a blank page with
And now... Some Services on it. Looking at the logs in tomcat
shows no error (or warning or info) about what might be the problem. Google was
uncharacteristically useless on this one, but I found some hints on Yahoo using
a search term of:



And now... Some Services blank



This was the best hint so far:



http://java2.5341.com/msg/8859.html



My symptoms are exactly as stated in the above. I can remove
all the packages and classes in my web service deployment and I then get more
reasonable errors, i.e. ClassNotFoundException and such.
Also, I can remove the offending service entirely from the
server-config.wsdd, at which point Axis behaves normally, showing the usual set
of installed Axis services when I call the AxisServlet, so its clearly a
problem in my service or classes or classpath, but Axis
isnt giving me a clue as to what the problem is. 



This is running ok in my Eclipse set-up, but its set
up somewhat differently there. 



Im guessing that there is some subtle library version
problem or classpath problem, and Ive been tinkering with both for many
hours with no success yet. 



Any ideas on what might be causing this or how I can narrow
down the problem?



Ive tried to turn on DEBUG logging for axis, but no
success with that yet either. Is there a way to do that?



My setup is as follows:



Axis 1.2.1

Tomcat 5.5.17

Java 1.5.0_07

Linux Redhat 3.4.5-2, which if I remove my custom JAVA_HOME
to JDK1.5 shows java version 1.4.2



From the Yahoo search results, people seem to be finding their
solution tinkering and blind luck, so hopefully were missing something
simple about Axis deployment, yes?



Ben







This e-mail message may contain confidential and/or privileged information. If you are not an addressee or otherwise authorized to receive this message, you should not use, copy, disclose or take any action based on this e-mail or any information contained in the message. If you have received this material in error, please advise the sender immediately by reply e-mail and delete this message. Thank you.

This e-mail message may contain confidential and/or privileged information. If you are not an addressee or otherwise authorized to receive this message, you should not use, copy, disclose or take any action based on this e-mail or any information contained in the message. If you have received this material in error, please advise the sender immediately by reply e-mail and delete this message. Thank you.

This e-mail message may contain confidential and/or privileged information. If you are 
not an addressee or otherwise authorized to receive this message, you should not use, 
copy, disclose or take any action based on this e-mail or any information contained in the 
message. If you have received this material in error, please advise the sender immediately 
by reply e-mail and delete this message. 

Thank you.

Re: Axis-schema.jar in 1.3 axis

2006-06-15 Thread Davanum Srinivas


It's built by running XmlSchema compiler on some xsd's. check the xml
files in the xmls/ directory for more info. It's under ASL 2.0 just
like other axis artifacts

-- dims

On 6/15/06, Flores, Raul [EMAIL PROTECTED] wrote:





axis-schema.jar


Can anyone tell me where this jar came from? Who owns it / what license it
is being distributed under?


Thanks,

Raul Flores
Lockheed Martin Aeronautics Company



--
Davanum Srinivas : http://wso2.com/blogs/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: AxisServlet returns And now... Some Services only (blank page)

2006-06-15 Thread McCauley, Tim

From
theAXIS_HOME/webapp/axis/WEB-INF/lib where there at in the Axis
distribution. After copying them to TOMCAT_HOME/common/lib/endorsed
restart Tomcat. Hopefully that will work it did for
me.

Tim

-Original Message-From: Ben Ethridge
[mailto:[EMAIL PROTECTED]Sent: Thursday, June 15, 2006 1:53
PMTo: axis-user@ws.apache.orgSubject: RE: AxisServlet
returns "And now... Some Services" only (blank page)

Thanks. >From where
did you move them?

Ben

From:
McCauley, Tim [mailto:[EMAIL PROTECTED] Sent: Thursday, June 15, 2006 1:27
PMTo:
axis-user@ws.apache.orgSubject: RE: AxisServlet returns "And
now... Some Services" only (blank page)

Not sure if this will
help. I just ran into the same problem and move the saaj.jar and
jaxrpc.jar to the TOMCAT_HOME/common/lib/endorsed. I read in the install
documentation for Axis that this might be necessary for Tomcat 4 and Java 1.4
so I tried it and it worked. I am running Tomcat 5.0.28 and Java
1.4.2.08 on a windows box.

Tim

-Original
Message-From: Ben
Ethridge [mailto:[EMAIL PROTECTED]Sent: Thursday, June 15, 2006 1:19
PMTo:
axis-user@ws.apache.orgSubject: AxisServlet returns "And
now... Some Services" only (blank page)
Hi.

Ive spent several hours now, on
google and yahoo attempting to track down why AxisServlet is returning just
a blank page with And now... Some Services on it. Looking at the logs in
tomcat shows no error (or warning or info) about what might be the problem.
Google was uncharacteristically useless on this one, but I found some hints
on Yahoo using a search term of:

And now... Some Services
blank

This was the best hint so
far:

http://java2.5341.com/msg/8859.html

My symptoms are exactly as
stated in the above. I can remove all the packages and classes in my web
service deployment and I then get more reasonable errors, i.e.
ClassNotFoundException and such. Also, I can remove the offending
service entirely from the server-config.wsdd, at which point Axis
behaves normally, showing the usual set of installed Axis services when I
call the AxisServlet, so its clearly a problem in my service or
classes or classpath, but Axis isnt giving me a clue as to what the
problem is.

This is running ok in my Eclipse
set-up, but its set up somewhat differently there.

Im guessing that there is some
subtle library version problem or classpath problem, and Ive been tinkering
with both for many hours with no success yet.

Any ideas on what might be
causing this or how I can narrow down the
problem?

Ive tried to turn on DEBUG
logging for axis, but no success with that yet either. Is there a way to do
that?

My setup is as
follows:

Axis
1.2.1
Tomcat
5.5.17
Java
1.5.0_07
Linux Redhat 3.4.5-2, which if I
remove my custom JAVA_HOME to JDK1.5 shows java version
1.4.2

From the Yahoo search results,
people seem to be finding their solution tinkering and blind luck, so
hopefully were missing something simple about Axis deployment,
yes?

Ben

This e-mail message may contain confidential and/or privileged information. If you are not an addressee or otherwise authorized to receive this message, you should not use, copy, disclose or take any action based on this e-mail or any information contained in the message. If you have received this material in error, please advise the sender immediately by reply e-mail and delete this message. Thank you.This e-mail message may contain confidential and/or privileged information. If you are
not an addressee or otherwise authorized to receive this message, you should not use,
copy, disclose or take any action based on this e-mail or any information contained in the
message. If you have received this material in error, please advise the sender immediately
by reply e-mail and delete this message.

Thank you.

Re: please remove me from list

2006-06-15 Thread ANDY FABEL


Hi,
The reason I am leaving is that about a year ago I was trying to develop an application using Net Beans but unfortunately I don't have the time anymore.Thank You,
Andy




From:"Hariharasudhan.D Dhakshinamoorthy" [EMAIL PROTECTED]Reply-To:axis-user@ws.apache.orgTo:axis-user@ws.apache.orgSubject:Re: please remove me from listDate:Thu, 15 Jun 2006 08:22:23 -0700Andy !!!you should be sending mail to [EMAIL PROTECTED] :-)May i know the reasion behind you leaving :(On 6/15/06, ANDY FABEL [EMAIL PROTECTED] wrote:Hi,Please remove me from mailing listmy address: [EMAIL PROTECTED]Thank You,Andy Fabel- 
Tounsubscribe, e-mail: [EMAIL PROTECTED] For additionalcommands, e-mail: [EMAIL PROTECTED]-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Axis2 Deployment Model Deficiency

2006-06-15 Thread Junaid . Bhatra

Done.

http://issues.apache.org/jira/browse/AXIS2-822

Thanks,
Junaid



   
 Davanum  
 Srinivas 
 [EMAIL PROTECTED]  To 
 maxis-user@ws.apache.org 
cc 
 06/15/2006 12:20  
 PMSubject 
   Re: Axis2 Deployment Model  
   Deficiency  
 Please respond to 
 [EMAIL PROTECTED] 
  he.org   
   
   
   




Could u please log a bug so that we can track it?

thanks,
dims

On 6/15/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
 Dims,

 I tried the latest nightly from 06-15. It still does not work. I simply
 took the axis2.war, renamed addressing-SNAPSHOT.mar inside it to
 addressing.mar, and deployed it in WebLogic 9.1. It gave me the following
 error on startup about not being able to load the referenced addressing
 module. I then removed the addressing module reference from axis2.xml and
 tried it again. It came up fine now, but I still don't see the Version
 service, which is part of Axis2.war, in the Axis admin console.

 I took a peek at the source code in WarBasedAxisConfigurator. I don't see
 any code that handles the case when getServletContext().getRealPath()
==
 null. So it looks like this is not yet implemented.

 Here's the error about not being able to load the addressing module:

 Jun 15, 2006 11:38:32 AM EDT Error HTTP BEA-101216 Servlet:
 AxisServlet failed to preload
  on startup in Web application: axis2.war.
 org.apache.axis2.deployment.DeploymentException: Trying to engage a
module
 which is not available :
 addressing; nested exception is:
 org.apache.axis2.AxisFault: Trying to engage a module which is
not
 available : addressing
 at

org.apache.axis2.deployment.DeploymentEngine.loadFromClassPath(DeploymentEngine.java:147)


 at

org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisCon

 figurator.java:213)
 at

org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(Configura

 tionContextFactory.java:56)
 at

org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:235)

 at
 org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:203)
 Truncated. see log file for complete stacktrace
 org.apache.axis2.AxisFault: Trying to engage a module which is not
 available : addressing
 at

org.apache.axis2.engine.AxisConfiguration.engageModule(AxisConfiguration.java:301)

 at

org.apache.axis2.deployment.DeploymentEngine.engageModules(DeploymentEngine.java:766)

 at

org.apache.axis2.deployment.DeploymentEngine.loadFromClassPath(DeploymentEngine.java:143)


 at

org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisCon

 figurator.java:213)
 at

org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(Configura

 tionContextFactory.java:56)

 Thanks,
 Junaid





  Davanum
  Srinivas
  [EMAIL PROTECTED]
To
  maxis-user@ws.apache.org

cc
  06/14/2006 11:43
  AM
Subject
Re: Axis2 Deployment Model
Deficiency
  Please respond to
  [EMAIL PROTECTED]
   he.org







 Junaid,

 Did you try latest nightly? I believe this is fixed.

 thanks,
 dims

 On 6/14/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
 
  Hi,
 
  Here's my scenario which I believe might be a common requirement for a
 lot
  of enterprise applications. I'm trying to bundle Axis2 webapp as part
of
 a
  bigger EAR application and deploy in an application server such as
  WebLogic. I would like to package up all of the Web Services inside of
 the
  webapp/EAR file. The problem is that Axis2 cannot seem to load the
 services
  from within the EAR file in WebLogic..
 
  The issue arises due to the fact that Axis2 relies on the concept of a
  repository, which MUST be a folder on the file system. On certain
  application servers like

RE: [axis2] dynamic client invocation w/o intermediate classgeneration

2006-06-15 Thread Sanjiva Weerawarana

Hi Tony,

Can you speak to what Dims eluded to... how to use complexTypes w/o
generating helper classes to perform serialization/deserialization. I
want to do what WSIF and JROM started out to do.

Yep I understand ... FYI Paul, Alek and I created WSIF. I created JROM
originally (and Rania Khalaf from my old group in IBM took it to
completion). So I know exactly what you want to do ..

Also, with the current ServiceClient API, I don't see a way distinquish
between the style of service that you want to invoke.

That's by design: ServiceClient is designed to follow WSDL 2.0 model ..
where the entire input is always a single element. That element plays
the same role that WSIFMessage did- provides a runtime representation
for the WSDL message instance that's to be sent as input for the
operation.

At that level, there's no concept of RPC vs document style nonsense.

Basically, you
just pass in an OMElement as the payload. I used WSDL2Java to see
what kind of code would be generated from a simple RPC stockquote
wsdl. The wsdl is as follows:

?xml version='1.0' encoding='UTF-8'?
definitions name='net.xmethods.services.stockquote.StockQuote'
...
/definitions

Axis2 ADB generated coded that produces the following client invocation
stream:

?xml version='1.0' encoding='UTF-8'?
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
soapenv:Header /
soapenv:Body
ns1:getQuote
xmlns:ns1=http://www.themindelectric.com/wsdl/net.xmethods.services.stockquote.StockQuote/;
symbolIBM/symbol
/ns1:getQuote
/soapenv:Body
/soapenv:Envelope

This is wrong. First, for rpc style services, the namespace of the
wrapper element (operation) must be specified with the binding
soap:body extension namespace attribute. In the wsdl above, this
namespace is urn:xmethods-delayed-quotes.

Yes this is a bug- please do file an issue for it. A simple patch to the
XSLT templates will fix this.

Second, since use is
encoded, don't you have to encode the data that you send? A correct
stream would look something like this:

Nope, that part is correct. SOAP Encoding was an algorithm which
described how to take a struct like data model and map it to an XML
instance. In this case, since the model is defined as an XML element of
type xsd:string, there's no mapping to do. Whether one generates
xsi:type or not is a totally orthogonal issue .. having that will allow
someone who doesn't have the full schema handy on the other side to do
something. (There are scenarios where xsi:type is required (if there's a
subtype involved) but that's not the case here.)

It seems that with Axis2 everything is treated as a document with
literal encoding. That is, both input/output of ServiceClient
invocation is OMElement. And is it the user's responsibility to
encode the data if necessary (use=encoded) within the payload?

Encoding is such a poorly understood thing .. the basic rules of SOAP
Enc was that you didn't use attributes but rather element children. If
the schema you're dealing with is like that already then a literal
encoding of a doc conforming to that schema an an SOAP-Enc encoding of
that doc will give the same thing.

IMO 100% of schemas people use with use='encoded' follow this pattern
already. Why? Because the WSDL 1.1 spec does not define how to map an
arbitrary XML Schema in to the SOAPEnc data model .. which means if you
have an attr in the schema there's no spec which tells where to put that
in the message. Not very interoperable, so smart people don't use it. As
one of the authors of WSDL 1.1 I accept this as a royal screwup .. we
used XML Schema as an abstract representation of any data model
including a SOAPEnc one and that's not quite right :(.

That's why RPC/Encoded (especially with SOAPEnc) is dead. (There are
other reasons too but that's a HUGE reason.) The people who are doing
RPC/Enc with SOAPEnc are actually doing RPC/Lit but they don't know it.
(The other interesting part of SOAPEnc was the graph encoding stuff ..
which people do care about at times. However, IMO if you care about that
your services aren't designed right .. XML and Web services should not
be sending graphs of data around .. but that's just me :).)

Hopefully, not. In the old Axis 1.x codebase, you could pass in input
data (along with type) and set the operation style that you wanted to
use. How do you do this in Axis2? What is the new paradigm here for
client invocation such that I can code a client with a given set of
data and work with services that are designed as rpc/literal,
rpc/encoded, doc/literal, or doc/literal/wrapped?

In what form do you have the data you want to send?

Is it as JavaBeans? If so Paul gave you the answer. It can be improved
further with annotations to help control the mapping into XML but the
idea is correct.

Do you want to store them as something like JROM? If so AXIOM fits the
bill. In fact I have a student working with me (yes Alek

RE: Axis-schema.jar in 1.3 axis

2006-06-15 Thread Flores, Raul

Thanks Dave.

Great Job! 


Raul Flores
Lockheed Martin Aeronautics Company


-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: Thursday, June 15, 2006 1:09 PM
To: axis-user@ws.apache.org
Subject: Re: Axis-schema.jar in 1.3 axis

It's built by running XmlSchema compiler on some xsd's. check the xml
files in the xmls/ directory for more info. It's under ASL 2.0 just like
other axis artifacts

-- dims

On 6/15/06, Flores, Raul [EMAIL PROTECTED] wrote:




 axis-schema.jar


 Can anyone tell me where this jar came from? Who owns it / what 
 license it is being distributed under?


 Thanks,

 Raul Flores
 Lockheed Martin Aeronautics Company


--
Davanum Srinivas : http://wso2.com/blogs/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[axis2] Sorry we don't support methods overloading.....

2006-06-15 Thread Ajay Upadhyaya

Hi,I'm in process of migrating from axis1.x, I was using Message style services in my application signatures were like Document method(Document in)Which I've changed to OMElement method(OMElement in).The code migration went okay, app works fine. I found one issue (for which I needed workaround in my code). Here is the scenario
class ServiceClass{ //service wrapper public OMElement operation1(OMElement in){ } //real implementation of service OMElement operation1(){ }}services.xml
-service name=myservice  description  my web service  /description  parameter name=ServiceClass locked=falseServiceClass/parameter
  operation name=operation1  messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/  actionMappingurn:operation1/actionMapping
  /operation /serviceDuring initialization following exception is thrownERROR [org.apache.axis2.deployment.ServiceBuilder] - Error in schema generating Sorry we don't support methods overloading  
java.lang.Exception: Sorry we don't support methods overloading   at org.apache.ws.java2wsdl.SchemaGenerator.generateSchema(SchemaGenerator.java:143) at org.apache.axis2.deployment.util.Utils.fillAxisService
(Utils.java:213) at org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:149) at org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:91)
 at org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:84) at org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:118)
 at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:620) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:195) at org.apache.axis2.deployment.RepositoryListener.update
(RepositoryListener.java:207) at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:155) at org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:91)
 at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:142) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java
:42) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:213) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:182)- To workaround this, I had to create a base class and move the real implementation method in base class 
class BaseClass
{
 //real implementation of service
 OMElement operation1(){ }
}class ServiceClass extends BaseClass
{
 //service wrapper
 public OMElement operation1(OMElement in){ }}Looking into the axis source, found that org.apache.ws.java2wsdl.SchemaGenerator.generateSchema method uses getDeclaredMethods() call to find the methods in the service class, and as getDeclaredMethods does not returns methods inherited by a class, the workaround works.
The irony is that, in my case, since I'm not using RPC message receivers, the SchemaGenerator class anyway is not useful, as it does not work for non RPC casesI'm wondering if not seeing inherited methods is a bug or a feature... but either way, this could be put somewhere in documentation. The message Sorry we don't support methods overloading is a bit misleading as I'm using overloaded (inherited) methods.
-Ajay Upadhyaya

RE: [axis2] dynamic client invocation w/o intermediateclassgeneration

2006-06-15 Thread Tony Dean

Sanjiva,

Thanks for responding...i'm trying to digest your comments.

1. OK, so Axis2 was designed with wsdl 2.0 in mind. And, thus you have a single 
input document and a single output document.  We will most likely be 
interoperating with wsdl 1.1 services for a long while so I must remain 
compliant in my client application of choice.

You said below since the input model is defined as an XML element of type 
xsd:string, there's no mapping to do.  I'm fuzzy on this... can you give me an 
example where a mapping is required?  I just thought use=encoded mean't that 
the encoding must be inlined with the soap message itself and use=literal 
mean't that the encoding is specified in the schema.

So bottom line, when will the Axiom model (doc/lit) not work with a particular 
wsdl 1.1 service type?  Sorry to be so hard-headed on this encoding issue.  An 
example may help me.

Can you also explain your statement about having attrs in your schema making 
for interoperable issues?  I'm not following.  Attributes can be typed in 
schema.  What's wrong with the following for instance:
Data name=string-representing-name-of-data
  Floatxsd:float typeFloat
/Data

2. I don't really have my data in any particular form.  I will gather 
information from a running system in order to inject values into a particular 
model based on the wsdl message, then send the request to a service endpoint.  
Basically, my goal is to dynamically, programatically interact with arbitrary 
service endpoints sort of the same way a bpel engine does with the invoke 
activity.  These endpoints will most likely by created from wsdl 1.1 toolkits 
for the forseeable forture so I need to be able to interop with them as a 
client.

3. If all input/output is treated as a document, WSIF/JROM becomes less 
important, right (at least for Axis2)?  JROM is basically a DOM representation 
of a complexType I thought.  What value-add can you provide for Axis2?  I guess 
creating an in-memory Axiom/DOM representation of the input complex type would 
be helpful.  Then the application could fill in the pertinent data; otherwise, 
the application would have to read the wsdl and do this itself before it now 
how to create the input representation.  I am talking about dynamic invocation 
only here.

Sorry to ramble here.  Just trying to understand and figure out my best 
approach to this problem

-Tony
 

-Original Message-
From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED] 
Sent: Thursday, June 15, 2006 3:49 PM
To: axis-dev@ws.apache.org
Cc: axis-user@ws.apache.org
Subject: RE: [axis2] dynamic client invocation w/o intermediateclassgeneration

Hi Tony,

 Can you speak to what Dims eluded to... how to use complexTypes w/o  
 generating helper classes to perform serialization/deserialization.  I  
 want to do what WSIF and JROM started out to do.

Yep I understand ... FYI Paul, Alek and I created WSIF. I created JROM 
originally (and Rania Khalaf from my old group in IBM took it to completion). 
So I know exactly what you want to do .. 

 Also, with the current ServiceClient API, I don't see a way 
 distinquish  between the style of service that you want to invoke.

That's by design: ServiceClient is designed to follow WSDL 2.0 model ..
where the entire input is always a single element. That element plays the same 
role that WSIFMessage did- provides a runtime representation for the WSDL 
message instance that's to be sent as input for the operation.

At that level, there's no concept of RPC vs document style nonsense.

  Basically, you
  just pass in an OMElement as the payload.  I used WSDL2Java to see  
 what kind of code would be generated from a simple RPC stockquote  
 wsdl.  The wsdl is as follows:
 
 ?xml version='1.0' encoding='UTF-8'? definitions 
 name='net.xmethods.services.stockquote.StockQuote'
...
 /definitions
 
 Axis2 ADB generated coded that produces the following client invocation 
 stream:
 
 ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope 
 xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
  soapenv:Header /
  soapenv:Body
   ns1:getQuote 
 xmlns:ns1=http://www.themindelectric.com/wsdl/net.xmethods.services.stockquote.StockQuote/;
symbolIBM/symbol
   /ns1:getQuote
  /soapenv:Body
 /soapenv:Envelope
 
 This is wrong.  First, for rpc style services, the namespace of the  
 wrapper element (operation) must be specified with the binding  
 soap:body extension namespace attribute.  In the wsdl above, this  
 namespace is urn:xmethods-delayed-quotes.

Yes this is a bug- please do file an issue for it. A simple patch to the XSLT 
templates will fix this.

   Second, since use is
  encoded, don't you have to encode the data that you send?  A correct  
 stream would look something like this:

Nope, that part is correct. SOAP Encoding was an algorithm which described how 
to take a struct like data model and map it to an XML instance. In this case, 
since the model is defined as an XML element of type xsd:string, there's no

[Axis2] dumb newbie question part 2

Hi,Having thought a bit more about it, maybe I shouldn't be using xmlbeans, since the WSDL for the service doesn't specify the schema for the input and return documents.What is the simplest way to just get an XML document passed in, be able to read its DOM, and build a new DOM for the return document? Is ADB data binding the way to go?Thanks __Do You Yahoo!?Tired of spam?  Yahoo! Mail has the best spam protection around http://mail.yahoo.com

Re: [Axis2] dumb newbie question part 2

Use the RawXMLProvider and don't use a databinding framework.On 6/15/06, Andrew B [EMAIL PROTECTED]
 wrote:Hi,Having thought a bit more about it, maybe I shouldn't be using xmlbeans, since the WSDL for the service doesn't specify the schema for the input and return documents.
What is the simplest way to just get an XML document passed in, be able to read its DOM, and build a new DOM for the return document? Is ADB data binding the way to go?Thanks
 __Do You Yahoo!?Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

Re: [AXis2] best version to be on production

2006-06-15 Thread Paul Ashton


Nicolas Guaneme wrote:

kavithaa Rajavenkateshwaran wrote:


Hi,

We are thinking about using axis in production. I tried with  the  
latest release in axis1.x and axis2.
Axis1.x seems to   be much more stable. But not sure.Can some suggest  
me which version to go with.


Thanks,
Kavithaa

Hi, I prefer Axis 1 beacause you can find more doc and examples for 
develop and support... I work with Axis 1 in production easy and 
stable.


Our experience late last year was that Axis 1.3 performance was unacceptable 
under load (too
much CPU and memory usage).  We switched to Axis 2 (0.92) which performed a lot 
better for us
(and 1.0 performs better again).  The lack of the ability to set the client
timeout in the current 1.0 release is also causing us pain.

Cheers, Paul.


--
Paul Ashton
iCom Project Leader
Tourplan
Christchurch, New Zealand
Phone: +64 3 3669669
Fax: +64 3 3791091


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [axis1] more stable version of axis

Axis 1.4 fixes a number of array bugs. I recommend it over 1.2.On 6/15/06, [EMAIL PROTECTED] 
[EMAIL PROTECTED] wrote:









Dear axis users, 


we are to plan here to use axis in production but we are not sure about the version we will use, I hope 

someone can help us. We think axis 2 is not enough stable, too recent release and some bugs are still found (by example

for the timeout configuration which is a feature we really need). We then hesitate between axis 1.2 to 1.4, 

axis 1.4 seems to be also very recent so we plan to use axis 1.3.


Do you think it is a good choice ? 


thanks in advance




-To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2]wsdl2java error

Axis2 does not support rpc/encoded. Convert your service to either rpc/literal or document/literal.AnneOn 6/15/06, kavithaa Rajavenkateshwaran 
[EMAIL PROTECTED] wrote:
Hi,please find my wsdl below. Also i noticed that the MessageReceiverInOut used in one of the axis2 samples(doclitservice) had some jar files within it's package and was refering to the parse method in that and not to the
org.apache.axiom.om.OMElement.Factory.parse(as the one in generated file).I copied that particular jar from the sample and changed the method in my code,then it 
works.But this is not the right way.pl. let me know how to get the correct files generated from wsdl.
wsdl
?xml version=1.0 encoding=UTF-8?wsdl:definitions targetNamespace=urn:fibonacci xmlns:apachesoap=
http://xml.apache.org/xml-soap xmlns:impl=urn:fibonacci xmlns:intf=urn:fibonacci xmlns:soapenc=
http://schemas.xmlsoap.org/soap/encoding/ xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/ xmlns:wsdlsoap=
http://schemas.xmlsoap.org/wsdl/soap/ xmlns:xsd=
http://www.w3.org/2001/XMLSchema wsdl:types schema targetNamespace=urn:fibonacci xmlns=
http://www.w3.org/2001/XMLSchema import namespace=http://schemas.xmlsoap.org/soap/encoding/
/ complexType name=ArrayOf_xsd_int  complexContent  restriction base=soapenc:Array   attribute ref=soapenc:arrayType wsdl:arrayType=xsd:int[]/
  /restriction  /complexContent /complexType /schema /wsdl:types wsdl:message name=calculateFibonacciRangeResponse
   wsdl:part name=calculateFibonacciRangeReturn type=impl:ArrayOf_xsd_int/ /wsdl:message wsdl:message name=calculateFibonacciRequest
   wsdl:part name=in0 type=xsd:int/ /wsdl:message wsdl:message name=calculateFibonacciRangeRequest
   wsdl:part name=in0 type=xsd:int/   wsdl:part name=in1 type=xsd:int/ /wsdl:message
 wsdl:message name=calculateFibonacciResponse   wsdl:part name=calculateFibonacciReturn type=xsd:int/
 /wsdl:message wsdl:portType name=Fibonacci   wsdl:operation name=calculateFibonacci parameterOrder=in0
wsdl:input message=impl:calculateFibonacciRequest name=calculateFibonacciRequest/wsdl:output message=impl:calculateFibonacciResponse name=calculateFibonacciResponse/
   /wsdl:operation   wsdl:operation name=calculateFibonacciRange parameterOrder=in0 in1wsdl:input message=impl:calculateFibonacciRangeRequest name=calculateFibonacciRangeRequest/
wsdl:output message=impl:calculateFibonacciRangeResponse name=calculateFibonacciRangeResponse/   /wsdl:operation
 /wsdl:portType wsdl:binding name=fibonacciSoapBinding type=impl:Fibonacci   wsdlsoap:binding style=rpc transport=
http://schemas.xmlsoap.org/soap/http/   wsdl:operation name=calculateFibonacci
wsdlsoap:operation soapAction=/wsdl:input name=calculateFibonacciRequest  wsdlsoap:body encodingStyle=
http://schemas.xmlsoap.org/soap/encoding/ namespace=urn:fibonacci use=encoded/
/wsdl:inputwsdl:output name=calculateFibonacciResponse  wsdlsoap:body encodingStyle=
http://schemas.xmlsoap.org/soap/encoding/ namespace=urn:fibonacci use=encoded/
/wsdl:output   /wsdl:operation   wsdl:operation name=calculateFibonacciRange
wsdlsoap:operation soapAction=/wsdl:input name=calculateFibonacciRangeRequest  wsdlsoap:body encodingStyle=
http://schemas.xmlsoap.org/soap/encoding/ namespace=urn:fibonacci use=encoded/
/wsdl:inputwsdl:output name=calculateFibonacciRangeResponse  wsdlsoap:body encodingStyle=
http://schemas.xmlsoap.org/soap/encoding/ namespace=urn:fibonacci use=encoded/
/wsdl:output   /wsdl:operation /wsdl:binding wsdl:service name=FibonacciService
   wsdl:port binding=impl:fibonacciSoapBinding name=fibonacciwsdlsoap:address location=
http://localhost:8080/axis2/services/fibonacci/   /wsdl:port /wsdl:service/wsdl:definitions

On Jun 14, 2006, at 11:57 PM, Ajith Ranabahu wrote:
Hi, Can you post your WSDL pleaseAjith
On 6/15/06, kavithaa Rajavenkateshwaran [EMAIL PROTECTED]
 wrote: Hi,I 
files created using wsdl2java give compilation error.It seems likesome incompatibility in the MessageReceiverInOut code. Pl. suggesthow to resolve this.
symbol : method newXMLStreamReader ()
  [javac] location: interface org.apache.axiom.om.OMElement  [javac](org.apache.axiom.om.OMAbstractFactory.getOMFactory(),new
org.apache.axis2.util.StreamWrapper(param.newXMLStreamReader())) ;[javac]
  ^  [javac] /Users/kavithaarajavenkateshwaran/software/axis2/fib/src/trial/Fibonnaci/FibonacciServiceMessageReceiverInOut.java:125: cannot
resolve symbol  [javac] symbol : variable Factory  [javac] location: interface 
org.apache.axiom.om.OMElement  [javac] returnorg.apache.axiom.om.OMElement.Factory.parse(
  [javac]   ^  [javac] /Users/kavithaarajavenkateshwaran/software/axis2/fib/src/
trial/Fibonnaci/FibonacciServiceMessageReceiverInOut.java:129: cannotresolve symbol  [javac] symbol : variable Factory
  [javac] location: interface org.apache.axiom.om.OMElement  [javac] returnorg.apache.axiom.om.OMElement.Factory.parse
(  [javac]

Re: [AXis2] best version to be on production

2006-06-15 Thread Dennis Sosnoski


Hi Paul,

Greetings from North Island.  :-) If you use the SVN code or a nightly 
build the problem with client timeouts should be fixed: 
http://issues.apache.org/jira/browse/AXIS2-670?page=all


 - Dennis

Dennis M. Sosnoski
SOA, Web Services, and XML
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-296-6194 - Wellington, NZ +64-4-298-6117



Paul Ashton wrote:


Our experience late last year was that Axis 1.3 performance was 
unacceptable under load (too
much CPU and memory usage).  We switched to Axis 2 (0.92) which 
performed a lot better for us
(and 1.0 performs better again).  The lack of the ability to set the 
client

timeout in the current 1.0 release is also causing us pain.

Cheers, Paul.




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2]can anyone spot a problem with this SOAP request?

One problem with this message is that the TTIS element in not namespace qualified. AnneOn 6/15/06, Andrew B 
[EMAIL PROTECTED] wrote:Hi,The SOAP request is:POST /axis2/services/TTWSServiceService HTTP/1.0
Content-Type: text/xml; charset=utf-8Accept: application/soap+xml, application/dime, multipart/related, text/*User-Agent: Axis/1.3Host: 
127.0.0.1:Cache-Control: no-cachePragma: no-cacheSOAPAction: Content-Length: 623Authorization: Basic V0FMTUFSVDpXQUwxMjNNQVJU?xml version=1.0 encoding=UTF-8?
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ xmlns:xsd=
http://www.w3.org/2001/XMLSchema xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instancesoapenv:BodyTTIS xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance xsi:noNamespaceSchemaLocation=VW_TrailerData_Request_Schema.xsd TRAILERDATATRNRQ  TRNID/TRNID  TRAILERDATARQ

   TARGETASSETSTARGETALLY/TARGETALL   /TARGETASSETS   GETLATESTDATAY/GETLATESTDATA   COMPRESSY/COMPRESS
  /TRAILERDATARQ /TRAILERDATATRNRQ/TTIS/soapenv:Body/soapenv:EnvelopeThis is actually being generated by an Axis 1 client, calling an Axis2 service. The service bombs out with the exception:
ERROR [[AxisServlet]] Servlet.service() for servlet AxisServlet threw exceptionorg.apache.axiom.om.OMException at
 org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:265) at org.apache.axiom.om.impl.traverse.OMChildrenQNameIterator.hasNext(OMChildrenQNameIterator.java:75) at org.apache.axiom.om.impl.llom.OMElementImpl.getFirstChildWithName
(OMElementImpl.java:222) at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getHeader(SOAPEnvelopeImpl.java:76) at org.apache.axis2.engine.AxisEngine.createFaultMessageContext(AxisEngine.java:183) at 
org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:168) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:153) at javax.servlet.http.HttpServlet.service(HttpServlet.java
:717).The stack trace makes me think there is something wrong with the SOAP envelope, but I can't see what it is. Any help is appreciated - I have to
 get this thing working urgently.Thanks! __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: Multiple WSDL files generation

java2wsdl won't generate the separate WSDL files, but you can certainly edit the generated files and convert them into one schema (defining MyObject) and two WSDLs.AnneOn 6/15/06, 
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

Hello. 

I have 2 Java Interfaces, each one representing
a WebService : 

public interface interf1 
{ 
  public void m1(MyObject o); 
} 

public interface interf2 
{ 
  public void m2(MyObject o); 
} 

As you can see, the 2 operations have a MyObject instance input parameter.

I would like to generate the following WSDL files with java2wsdl :

- one WSDL file containing the MyObject complex type.

- one WSDL file containing the interf1 web service and using the first
WSDL file. 
- one WSDL file containing the interf2 web service and using the first
WSDL file. 

Is it possible ? 
If yes how can I do ? 
Thanks a lot. 

Regards. 

Jean-Baptiste

Re: Adding namespace to Envelope at runtime (axis 1.4)

How are you generating the message in the first place? Why isn't the namespace specified then?On 6/14/06, Nicolas-Viet Nguyen 
[EMAIL PROTECTED] wrote:Does anyone have a neat solution for adding a namespace to the Envelope at runtime for a SOAP request message?
I hesitate to write a custom SOAP Handler just to do this.Thanks

Re: [Axis 1.4] Eclipse does not like WSDL

Please post the WSDL.On 6/14/06, [EMAIL PROTECTED] [EMAIL PROTECTED]
 wrote:Hello:I deployed a simple web service using Axis 1.4 on Tomcat 
5.5.17.When I downloaded the WSDL into a project to build a clientusing the Eclipse IDE, I get these errors from Eclipse:schema_reference.4: Failed to read schema document 'http://lang.java
',because 1) could not find the document; 2) the document could not be read;3) the root element of the document is not xsd:schema.The part 'fault' has an invalid value 'SAXException' defined for its type.
Type declarations must refer to valid values defined in a schema.They dont seem to interfere with using the WSDL.I can generatemy classes and write the client just fine.Any ideas on these?
Thanks,Neil--Neil Aggarwal, JAMMConsultingwww.JAMMConsulting.com, 214-986-3533-
To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]

How to load custom configuration (EngineConfiguration)

2006-06-15 Thread Nicolas-Viet Nguyen

Hello All,If I write my own Configuration to load my handlers, say MyClientConfig, how can I enable axis to load this configuration instead of using the default FileProvider as start up?I am using axis1.4
Thanks.

Re: Newbie: use more than one part in wsdl message [Re: Axis and multipart message]

You may have at most one message part in the SOAP Body in a document style message. If you want to send parameters, then you should use RPC style instead. If you want to use document style, then you must define a single wrapper element that encapsulates your four parameters. 
AnneOn 6/14/06, Monica Ruiu [EMAIL PROTECTED] wrote:
Hi all,

I'm a junior java developer and I'm trying to set up a document literal web service.
In the service there is a message with 4 input parameters and my problem is the loss
of values of the wsdl:parts.
Each part in wsdl:message refers to a xml element, the client builds the request
with all the elements referred by the parts. In the request all the elemets have the value
but on the server (*Impl class) only the first parameter contains the value all the others are null.

Could you tell me where I'm wrong ?

TIA 

monica

PS: 
...
   xsd:simpleType name=data-model-list-mode-type
xsd:restriction base=xsd:string
  
  xsd:enumeration
value=all/
  
  xsd:enumeration
value=active/
  
  xsd:enumeration
value=archive/
/xsd:restriction
   /xsd:simpleType
  
xsd:element name=data-model-list-request-application-name
type=xsd:string/
  
xsd:element name=data-model-list-request-repository-name
type=xsd:string/
  
xsd:element name=data-model-list-request-model-name
type=xsd:string/
  
xsd:element name=data-model-list-request-mode
type=clt:data-model-list-mode-type/
...
 wsdl:message name=modelDefinitionListRequest
  wsdl:part
name=applicationName
element=clt:data-model-list-request-application-name/
  wsdl:part
name=repositoryName
element=clt:data-model-list-request-repository-name/
  wsdl:part name=modelName element=clt:data-model-list-request-model-name/
  wsdl:part name=mode element=clt:data-model-list-request-mode/
 /wsdl:message
...
  wsdl:operation name=getModels
   wsdl:input message=cltengine:modelDefinitionListRequest/
   wsdl:output message=cltengine:modelDefinitionListResponse/
  /wsdl:operation
...
 wsdl:binding name=DataModelSOAP type=cltengine:DataModelPortType
  soap:binding style=document transport=http://schemas.xmlsoap.org/soap/http
/

  wsdl:operation name=getModels
  
soap:operation
soapAction=http://cmos.bassnet.biz/template/getModels/
   wsdl:input
  
 soap:body use=literal parts=applicationName
repositoryName modelName mode /
   /wsdl:input
   wsdl:output
soap:body use=literal/
   /wsdl:output
  /wsdl:operation

RE: [Axis 1.4] Eclipse does not like WSDL

2006-06-15 Thread Alick Buckley




Is the 
WSDL rpc/encoded or wrapped document/literal ?

If it is rpc/encoded does it 
contain"soapenc:string" vs."xsd:string" for the type 
attribute value

Use the -T 1.1 option on the Java2WSDL to generate 
JAX-RPC style.




  -Original Message-From: Anne Thomas Manes 
  [mailto:[EMAIL PROTECTED]Sent: Friday, 16 June 2006 10:42 
  AMTo: axis-user@ws.apache.orgSubject: Re: [Axis 1.4] 
  Eclipse does not like WSDLPlease post the WSDL.
  On 6/14/06, [EMAIL PROTECTED] [EMAIL PROTECTED]  
  wrote:
  Hello:I 
deployed a simple web service using Axis 1.4 on Tomcat 5.5.17.When I 
downloaded the WSDL into a project to build a clientusing the Eclipse 
IDE, I get these errors from Eclipse:schema_reference.4: Failed to 
read schema document 'http://lang.java 
',because 1) could not find the document; 2) the document could not 
be read;3) the root element of the document is not 
xsd:schema.The part 'fault' has an invalid value 
'SAXException' defined for its type. Type declarations must refer to 
valid values defined in a schema.They dont seem to interfere with 
using the WSDL.I can generatemy classes and write the client 
just fine.Any ideas on 
these?Thanks,Neil--Neil Aggarwal, 
JAMMConsultingwww.JAMMConsulting.com, 
214-986-3533- 
To unsubscribe, e-mail: [EMAIL PROTECTED]For 
additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] dumb newbie question part 2