Re: [axis2 - v1.0] [please help!] dual blocking client

2006-06-23 Thread Ali Sadik Kumlali
Hi Diego,

In insertMappingAnnotations() you set the action two times and the latter one 
seems like a copy-paste-and-forget issue:

   ...
 _operationClient.getOptions().setAction(insertMappingAnnotations);
   ...
 _operationClient.getOptions().setAction(urn:echo);

Might that be the problem?

Regards,

Ali Sadik Kumlali

- Original Message 
From: Diego [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Friday, June 23, 2006 4:29:49 AM
Subject: [axis2 - v1.0] [please help!] dual blocking client

Hi Everybody,

I really need to get this code working.  I've posted 5 times regarding 
this subject and had no reply at all.  I would like to know if someone 
knows how I could modify the code generated by the wsdl2java in order to 
have a blocking dual client behaviour.

The code and the exception that I get follow.

I'm a bit frustrated about that!

Thanks very much about for any help!

Diego


=
Exception
=

Exception in thread main java.lang.NullPointerException
 at 
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:260)
 at 
org.astrodas.ws.peer.AstrodasPeerStub.insertMappingAnnotations(AstrodasPeerStub.java:128)
 at 
org.astrodas.ws.peer.AstrodasPeerProxy.insertMappingAnnotations(AstrodasPeerProxy.java:36)
 at org.astrodas.test.Populate.populateLocal(Populate.java:239)
 at org.astrodas.test.Populate.main(Populate.java:350)

=
  Code
=

public InsertMappingAnnotationsResponseDocument 
insertMappingAnnotations(InsertMappingAnnotationsDocument requestDoc)
 throws RemoteException {
   try {
 OperationClient _operationClient = 
_serviceClient.createClient(_operations[0].getName());
 _operationClient.getOptions().setAction(insertMappingAnnotations);
 _operationClient.getOptions().setExceptionToBeThrownOnSOAPFault(true);
 // Dual client
 
_operationClient.getOptions().setTransportInProtocol(Constants.TRANSPORT_HTTP);
 _operationClient.getOptions().setUseSeparateListener(true);
 _operationClient.getOptions().setAction(urn:echo);
 _serviceClient.engageModule(new 
javax.xml.namespace.QName(Constants.MODULE_ADDRESSING));
 // create SOAP envelope with that payload
 SOAPEnvelope env = null;
 //Style is Doc.
 env = 
toEnvelope(getFactory(_operationClient.getOptions().getSoapVersionURI()),
  requestDoc,
  optimizeContent(new 
QName(,insertMappingAnnotations)));
 // create message context with that soap envelope
 MessageContext _messageContext = new MessageContext();
 _messageContext.setEnvelope(env);
 // add the message contxt to the operation client
 _operationClient.addMessageContext(_messageContext);
 //execute the operation client
 _operationClient.execute(true);
 MessageContext _returnMessageContext = 
_operationClient.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);
 SOAPEnvelope _returnEnv = _returnMessageContext.getEnvelope();
 Object object = fromOM(getElement(_returnEnv, document),
InsertMappingAnnotationsResponseDocument.class,
getEnvelopeNamespaces(_returnEnv));
 _messageContext.getTransportOut().getSender().cleanup(_messageContext);
 return (InsertMappingAnnotationsResponseDocument) object;
   } catch (AxisFault f) {...}

-
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: Is SOAP appropriate for large data transmission broken pipe exception

2006-06-23 Thread German Sakaryan

Hi,
it seems that brocken pipe exception (transfering large files axis2 
version 1) is a kind of a bug.
We have installed the latest nightly build version, and broken pipe 
exception has disapeared.


German

Rodrigo Ruiz schrieb:

Hi Betsy, German,

When you say FTP is faster than HTTP do you mean in equality conditions, 
or do you mean a native FTP server is faster than a Java HTTP server? 
AFAIK, both protocols introduce a little overhead for the connection 
establishment, and after that, just the raw data is sent over the wire. 
Perhaps the difference lies on the packet sizes? What happens if you 
need to secure the access to the file? Is it possible to use a common 
shared AAA mechanism for both servers?


The limits you mention for large attachments are, in part, related to 
the Axis implementation, and not to the SOAP protocol. I think there is 
a size limit for MIME attachments from the MIME multipart encoding 
specification. The document I read (a long time ago) stated that the 
size of the parts must be a 32bit integer. This leads to a 2Gb limit if 
you use a Java int to represent this value. I really don't know if 
this limit is still there, or if the specification has been updated 
since I read it, nor if Axis respects it. As MTOM is compatible with 
MIME attachments, I guess it shares the same limitations. I think it is 
important to note that this limit is only for a single MIME part, that 
is, a smart transfer service could split larger files into several 
smaller MIME parts and send them as separate attachments into a single 
response. DIME attachments, if streamed, do not require their size to be 
specified, and so, do not have such a limitation.


I have successfully transferred 10GByte files with Axis 1.4, using DIME 
attachments and chunked transfer (yes, this one do introduce an extra 
overhead :-D), so I guess broken pipe exceptions should be considered 
bugs to be solved, rather than technology limitations ;-)


Best Regards,
Rodrigo Ruiz

Betsy Frey wrote:


Hi German,

I have not tried sending attachments with Axis2.

Betsy


-Original Message-
From: German Sakaryan [mailto:[EMAIL PROTECTED] Sent: 
Thursday, June 22, 2006 4:43 AM

To: axis-user@ws.apache.org
Subject: Re: Is SOAP appropriate for large data transmission

Hi,Betsey
have tried to send large files with axis2 ?

I get fast always broken pipe exception.

German Sakaryan
Betsy Frey schrieb:


SOAP without an attachment is inappropriate for sending large amounts


of binary data, because the XML requires it to be converted to Base64,
which is inefficient.


With an attachment, SOAP over http has the overhead of the protocol,


which is not as fast as ftp, for instance.


I have used DIME attachments in Axis 1.1.  They worked fine up to some


limit, 2gb or so as I recall; 2 ^ 31 or 32.


Betsy

-Original Message-
From: Rodrigo Ruiz [mailto:[EMAIL PROTECTED] Sent: Thursday, 
June 22, 2006 2:51 AM

To: axis-user@ws.apache.org
Subject: Is SOAP appropriate for large data transmission

Hi all,

I usually read in this forum that web services and SOAP are not 
appropriate for large data transmission, but I have never read about


any


good technical reasons behind these sentences.

Most of the issues I have seen in this matter are related to the SOAP 
stack implementation, rather than to SOAP itself:


- Progress bar for file download: You can split the download in


smaller


chunks and transmit them using several calls. It should be possible to



modify the attachments implementation of SOAP and add the logic for 
asynchronous status notification, so it is technically possible to


track


the progress of attachments download/upload.

- SOAP XML overhead: In fact, the overhead of a SOAP envelope


containing

just a reference to the attachment part is more important for small 
attachments than for large ones. Just one or two kilobytes of XML are 
not too much when you are trying to transfer an 8GB stream.


- Partial/broken transmissions: Again, if the attachments


implementation

is able to track the progress of a download, it may be possible to 
resume it after a transmission error. We would just need to be able to




specify the range we are interested in, just like with old plain HTML.


Could somebody shed some light on the reasons that make SOAP 
inappropriate for this task?


Regards,
Rodrigo Ruiz




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


**
This email and any files transmitted with it are confidential and 
intended solely for the use of the individual or entity to whom they 
are addressed. Any unauthorized review, use, disclosure or 
distribution is prohibited. If you are not the intended recipient, 
please contact the sender by reply e-mail and destroy all copies of 
the original message.




RE: Java.net.SocketException: Connection Reset

2006-06-23 Thread Ravi_Srirangam
 Thanks for the response, Srinivas.
I tried out the listed options for Jrockit, but that didn't work.
Any other suggestions.

Thanks,
Ravi

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: Friday, June 23, 2006 12:38 AM
To: axis-user@ws.apache.org
Subject: Re: Java.net.SocketException: Connection Reset

please try tweaking the jvm parameters for jrockit. Try the examples in
the following sites [1]


[1]
http://www.google.com/search?hl=enlr=safe=offq=specjappserver+jrockit
+site%3Aspec.orgbtnG=Search


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



 Hi All,
 I'm not sure if this question has been posted before. There is an
 java.net.SocketException: Connection Reset when tried to call a web 
 service.

 I googled for the solution and found that disabling the -server option

 on the JVM would resolve the issue. In my project environment, we use 
 Jrockit JRE for Weblogic 8.1 SP4. Changing the JVM to Sun's JDK1.4 
 solved the problem, but there are increasing concerns from the server 
 admin people to use Jrockit JVM and they are unrelenting to use the
Sun's JDK.

 I have used Axis 1.3. Should I upgrade my Axis version? If anyone 
 knows the exact reason for this kind of behavior , pl. do let me know.

 Thanks in advance,
 Ravi


--
Davanum Srinivas : http://people.apache.org/~dims/

-
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] Missing jar file?

2006-06-23 Thread Kinichiro Inoguchi
Ron,

Package of OMxxx classes were refactored between 0.9x and 1.0.
- 0.9 org.apache.ws.commons.om.OMxxx
- 1.0 org.apache.axiom.om.OMxxx

If you want org.apache.ws.commons.om.OMContainer (0.9x) still,
you can find it in axis2-core-0.9x.jar of Axis2 0.9x distribution.
http://ws.apache.org/axis2/download.cgi

BTW, do you try to install Axis2 on Tomcat ?
Then using axis2.war distribution is easy.

Regards,
kinichiro

--- Ajith Ranabahu [EMAIL PROTECTED] wrote:

 Hi,
 What is the Axis2 version we are talking about here ? BTW
 OMPolicyReader is in the Neethi.**.jar AFAIR.
 
 Ajith
 
 On 6/22/06, Ron Turner [EMAIL PROTECTED] wrote:
  Thanks, Kinichiro.  In axiom-api-1.0.jar I can see
 
  org.apache.axiom.om.OMContainer
 
  but the version of OMPolicyReader I have is looking for
 
  org.apache.ws.commons.om.OMContainer
 
  when it's instantiated.  Just for curiosity's sake, where in your
 Axis2 distribution is OMPolicyReader located?
 
  Best regards,
 
  Ron
 
  - Original Message -
  From: Kinichiro Inoguchi [EMAIL PROTECTED]
  Date: Thursday, June 22, 2006 9:02 am
  Subject: Re: [Axis2] Missing jar file?
 
   Hi,
   It's axiom-api-1.0.jar.
  
   __
   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]
  
  
 
 
 
 -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 -- 
 Ajith Ranabahu
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 


__
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]



Is Axis Ws-I compliant

2006-06-23 Thread Price, Stephen
Title: Message



Hi, just starting 
for the first time developing a component to communicate with a web service. Our 
client has sent us the wsdl and we were going to use Axis to convert the wsdlto 
java to call the web service. Our client has told us that we shouldn't use axis 
as their service is WS-I compliant, whereas Axis is not. I am not 100% sure 
about this. Can anyone tell me ?
Thanks,
Stephen




  
  
Stephen PriceSoftware DeveloperTerraNua 
  

  

  
 
Phone: 
(+) 353 1 614 5585 
  


  
E-mail: 
[EMAIL PROTECTED] 
  
  
Website: 
www.TerraNua.com 
  

  

  
TerraNua Ltd., registered in Ireland no. 288648. Registered 
  office: Hardwicke House, Upper Hatch Street, Dublin 2. Telephone 
  +353-1-6145400. Any comments or statements made are not necessarily those 
  of Fidelity Investments, its subsidiaries, or affiliates. 


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

Re: [axis2 - v1.0] [please help!] dual blocking client

2006-06-23 Thread Diego

Hi Ali,

thanks very much for your answer.

Ali Sadik Kumlali wrote:

Hi Diego,

In insertMappingAnnotations() you set the action two times and the latter one 
seems like a copy-paste-and-forget issue:

   ...
 _operationClient.getOptions().setAction(insertMappingAnnotations);
   ...
 _operationClient.getOptions().setAction(urn:echo);

Might that be the problem?


That would have definitely be a problem after the message would have 
been send.  But the exception arises in the message creation phase. 
Anyway, I have modified the code as you say but still get the same 
exception.


Also note that the code works properly if I comment the 
setUseSeparateListener(true) statement but obviously it is not a dual 
client anymore as I would like.


Regards,

Diego

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



Re: [Axis2] sending large file problem

2006-06-23 Thread Wan Kaveevivitchai


Thank you for the recommendation about using the latest nightly builds.
I have downloaded and deployed it, and it's now working fine with sending 
10MB of data, it's actually pretty fast too.


So i am now move on trying to send the bigger file size which is 
approximately 100MB and i got the following errors


Sathita

Exception in thread main org.apache.axis2.AxisFault: null; nested 
exception is:

java.lang.reflect.InvocationTargetException
	at 
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:287)
	at 
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:451)
	at 
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:393)

at fileT.fileC.sendFile(fileC.java:117)
at fileT.fileC.main(fileC.java:50)
Caused by: java.lang.Exception: org.apache.axis2.AxisFault: null; nested 
exception is:

java.lang.reflect.InvocationTargetException
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:318)
	at 
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:144)
	at 
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37)

at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:483)
	at 
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284)

at 
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:144)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:767)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
at 
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:423)
at 
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:355)
at 
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:219)
at 
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:542)
	at 
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:145)
	at 
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:126)

at 
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:119)
at org.mortbay.jetty.Server.handle(Server.java:245)
at 
org.mortbay.jetty.HttpConnection.handlerRequest(HttpConnection.java:365)
at org.mortbay.jetty.HttpConnection.access$1500(HttpConnection.java:38)
	at 
org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:623)

at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:690)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:192)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:296)
	at 
org.mortbay.jetty.nio.SelectChannelConnector$HttpEndPoint.run(SelectChannelConnector.java:740)
	at 
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:435)

Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)
	at 
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:114)

... 22 more
Caused by: java.lang.OutOfMemoryError

at org.apache.axis2.AxisFault.init(AxisFault.java:159)
... 5 more



From: Davanum Srinivas [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Subject: Re: [Axis2] sending large file problem
Date: Thu, 22 Jun 2006 15:15:25 -0400

you need to bump up the timeout. For which you need to use latest
nightly builds.

thanks,
dims

On 6/22/06, Wan Kaveevivitchai [EMAIL PROTECTED] wrote:

Dear All Axis2 users

I am working on Axis2 1.0 version. I am now trying to send 
large
attachment file the size is about 10 MB. But it causes the error as 
follow.

Everything work file with the file in smaller size...approximate 5MB. I
don't think that it is something wrong with the code. But if anyone know
what is the problem please let me know. I am also enable the MTOM both on
client and server.

   Many thanks, looking forward to hear

Sathita

Exception in thread main org.apache.axiom.om.OMException: Problem with 
the

OutputStream.
at
org.apache.axiom.om.impl.MIMEOutputUtils.complete(MIMEOutputUtils.java:62)
at
org.apache.axiom.om.impl.MTOMXMLStreamWriter.flush(MTOMXMLStreamWriter.java:127)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:382)
at
org.apache.axis2.transport.http.SOAPOverHTTPSender$AxisSOAPRequestEntity.handleOMOutput(SOAPOverHTTPSender.java:145)
at

[AXIS 1.4]Problem after deploying web services using axis

2006-06-23 Thread Kashif Saleem
Hi All,
   I  installed couple of times axis-1_4 axis on apache-tomcat-5.5.17 and 
whenever  I deployed any services using any deploytment descriptor with some 
problem in it.Then it starts behavinh weirdly i.e when I click list web 
services  it goes to the following pages :

   http://localhost:8080/axis/servlet/AxisServlet

then instead of getting the list of services,I am getting the blank page saying
And now... Some Services



I would appreciate if someone could tell me the reason for this.


Kind Regards
Kashif

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



Re: Is Axis Ws-I compliant

2006-06-23 Thread Davanum Srinivas

No toolkit is ever 100% compliant. Yes, it is possible to write a WS-I
compliant service and client using some of the toolkits including
Axis/Axis2. Did you understand the distinction? The key is tesing with
WS-I compliant testing tools and tweaking the wsdl and schema to make
sure they are complaint and cross checking sample messages on the wire
to make sure they are compliant.

-- dims

On 6/23/06, Price, Stephen [EMAIL PROTECTED] wrote:




Hi, just starting  for the first time developing a component to communicate 
with a web service. Our  client has sent us the wsdl and we were going to use 
Axis to convert the wsdlto  java to call the web service. Our client has told 
us that we shouldn't use axis  as their service is WS-I compliant, whereas Axis 
is not. I am not 100% sure  about this. Can anyone tell me ?
Thanks,
Stephen



 Stephen Price
Software Developer
TerraNua




   Phone:  (+) 353 1 614 5585


 E-mail:  [EMAIL PROTECTED]
 Website:  www.TerraNua.com




 TerraNua Ltd., registered in Ireland no. 288648. Registeredoffice: 
Hardwicke House, Upper Hatch Street, Dublin 2. Telephone+353-1-6145400. 
Any comments or statements made are not necessarily thoseof Fidelity 
Investments, its subsidiaries, or affiliates.

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






--
Davanum Srinivas : http://people.apache.org/~dims/

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



Could I handler the exception in an common error handling class ?

2006-06-23 Thread 蘇 軼(CEC)
hi all,

I want to handle the exceptions throwed by the services in one common 
class, and tried to extend the AxisServlet class overwriting doGet() and
doPost() method, and catch error with code like below :

try {
super.doGet(request, response);
} catch (Exception e) {
// deal the exception
// like :  System.out.println(--- + e.getMessage);
}

but nothing happened.

I think Axis doesn't call the service in such methods, so could anybody
tell me how to do the error handling in common way ? Is there a class
I can extend ?

Any help or web resources would be greatly appreciated !

Regards,
- sukie


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



RE: [AXIS 1.4]Problem after deploying web services using axis

2006-06-23 Thread subir.sasikumar

Hi Kashif,

Can you check whether actually your web service is deployed or not??
i.e. try to access the link
http://localhost:8080/axis/services/yourServiceName
If the service is deployed you will get a message saying that a web
service exist here...

Are you not getting any errors in the tomcat console or catalina.out
file (if you are in linux).

Subir S

-Original Message-
From: Kashif Saleem [mailto:[EMAIL PROTECTED]
Sent: Friday, June 23, 2006 3:36 PM
To: axis-user@ws.apache.org
Subject: [AXIS 1.4]Problem after deploying web services using axis

Hi All,
   I  installed couple of times axis-1_4 axis on
apache-tomcat-5.5.17 and whenever  I deployed any services using any
deploytment descriptor with some problem in it.Then it starts behavinh
weirdly i.e when I click list web services  it goes to the following
pages :

   http://localhost:8080/axis/servlet/AxisServlet

then instead of getting the list of services,I am getting the blank page
saying
And now... Some Services



I would appreciate if someone could tell me the reason for this.


Kind Regards
Kashif

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



The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
email.

www.wipro.com

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



RE: Is Axis Ws-I compliant

2006-06-23 Thread Price, Stephen
Title: RE: Is Axis Ws-I compliant





Hi Davanum, thanks for that. So what you are saying is that we should be OK using axis once our service and wsdl are WS-I compliant ? Can you recommend any tools for testing whether our wsdl/schema is WS-I compliant ?

Thanks,
Stephen


-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]] 
Sent: 23 June 2006 11:18
To: axis-user@ws.apache.org
Subject: Re: Is Axis Ws-I compliant



No toolkit is ever 100% compliant. Yes, it is possible to write a WS-I
compliant service and client using some of the toolkits including
Axis/Axis2. Did you understand the distinction? The key is tesing with
WS-I compliant testing tools and tweaking the wsdl and schema to make
sure they are complaint and cross checking sample messages on the wire
to make sure they are compliant.


-- dims


On 6/23/06, Price, Stephen [EMAIL PROTECTED] wrote:



 Hi, just starting for the first time developing a component to communicate with a web service. Our client has sent us the wsdl and we were going to use Axis to convert the wsdlto java to call the web service. Our client has told us that we shouldn't use axis as their service is WS-I compliant, whereas Axis is not. I am not 100% sure about this. Can anyone tell me ?

 Thanks,
 Stephen



 Stephen Price
 Software Developer
 TerraNua
 


 Phone: (+) 353 1 614 5585


 E-mail: [EMAIL PROTECTED]
 Website: www.TerraNua.com
 


 TerraNua Ltd., registered in Ireland no. 288648. Registered office: Hardwicke House, Upper Hatch Street, Dublin 2. Telephone +353-1-6145400. Any comments or statements made are not necessarily those of Fidelity Investments, its subsidiaries, or affiliates.


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






-- 
Davanum Srinivas : http://people.apache.org/~dims/


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





Re: Is Axis Ws-I compliant

2006-06-23 Thread Davanum Srinivas

The official one is here:
http://www.ws-i.org/deliverables/workinggroup.aspx?wg=testingtools

There are several vendors who have this feature as part of their
tooling example Mindreef, Parasoft. Just google for them.

thanks,
dims

On 6/23/06, Price, Stephen [EMAIL PROTECTED] wrote:




Hi Davanum, thanks for that. So what you are saying is that we should be OK
using axis once our service and wsdl are WS-I compliant ? Can you recommend
any tools for testing whether our wsdl/schema is WS-I compliant ?

Thanks,
Stephen




-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: 23 June 2006 11:18
To: axis-user@ws.apache.org
Subject: Re: Is Axis Ws-I compliant


No toolkit is ever 100% compliant. Yes, it is possible to write a WS-I
compliant service and client using some of the toolkits including
Axis/Axis2. Did you understand the distinction? The key is tesing with
WS-I compliant testing tools and tweaking the wsdl and schema to make
sure they are complaint and cross checking sample messages on the wire
to make sure they are compliant.

-- dims

On 6/23/06, Price, Stephen [EMAIL PROTECTED] wrote:



 Hi, just starting  for the first time developing a component to
communicate with a web service. Our  client has sent us the wsdl and we were
going to use Axis to convert the wsdlto  java to call the web service. Our
client has told us that we shouldn't use axis  as their service is WS-I
compliant, whereas Axis is not. I am not 100% sure  about this. Can anyone
tell me ?

 Thanks,
 Stephen



  Stephen Price
 Software Developer
 TerraNua
 

Phone:  (+) 353 1 614 5585


  E-mail:  [EMAIL PROTECTED]
  Website:  www.TerraNua.com
 

  TerraNua Ltd., registered in Ireland no. 288648. Registered
office: Hardwicke House, Upper Hatch Street, Dublin 2. Telephone
+353-1-6145400. Any comments or statements made are not necessarily those
of Fidelity Investments, its subsidiaries, or affiliates.



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





--
Davanum Srinivas : http://people.apache.org/~dims/


-

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






--
Davanum Srinivas : http://people.apache.org/~dims/

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



Re: [axis2 - v1.0] [please help!] dual blocking client

2006-06-23 Thread Martin Gainty

Diego-
Can you post the WSDL??
Martin --
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.

- Original Message - 
From: Diego [EMAIL PROTECTED]

To: axis-user@ws.apache.org
Sent: Thursday, June 22, 2006 9:29 PM
Subject: [axis2 - v1.0] [please help!] dual blocking client



Hi Everybody,

I really need to get this code working.  I've posted 5 times regarding 
this subject and had no reply at all.  I would like to know if someone 
knows how I could modify the code generated by the wsdl2java in order to 
have a blocking dual client behaviour.


The code and the exception that I get follow.

I'm a bit frustrated about that!

Thanks very much about for any help!

Diego


=
   Exception
=

Exception in thread main java.lang.NullPointerException
at 
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:260)
at 
org.astrodas.ws.peer.AstrodasPeerStub.insertMappingAnnotations(AstrodasPeerStub.java:128)
at 
org.astrodas.ws.peer.AstrodasPeerProxy.insertMappingAnnotations(AstrodasPeerProxy.java:36)

at org.astrodas.test.Populate.populateLocal(Populate.java:239)
at org.astrodas.test.Populate.main(Populate.java:350)

=
 Code
=

public InsertMappingAnnotationsResponseDocument 
insertMappingAnnotations(InsertMappingAnnotationsDocument requestDoc)

throws RemoteException {
  try {
OperationClient _operationClient = 
_serviceClient.createClient(_operations[0].getName());

_operationClient.getOptions().setAction(insertMappingAnnotations);
_operationClient.getOptions().setExceptionToBeThrownOnSOAPFault(true);
// Dual client

_operationClient.getOptions().setTransportInProtocol(Constants.TRANSPORT_HTTP);
_operationClient.getOptions().setUseSeparateListener(true);
_operationClient.getOptions().setAction(urn:echo);
_serviceClient.engageModule(new 
javax.xml.namespace.QName(Constants.MODULE_ADDRESSING));

// create SOAP envelope with that payload
SOAPEnvelope env = null;
//Style is Doc.
env = 
toEnvelope(getFactory(_operationClient.getOptions().getSoapVersionURI()),

 requestDoc,
 optimizeContent(new 
QName(,insertMappingAnnotations)));

// create message context with that soap envelope
MessageContext _messageContext = new MessageContext();
_messageContext.setEnvelope(env);
// add the message contxt to the operation client
_operationClient.addMessageContext(_messageContext);
//execute the operation client
_operationClient.execute(true);
MessageContext _returnMessageContext = 
_operationClient.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);

SOAPEnvelope _returnEnv = _returnMessageContext.getEnvelope();
Object object = fromOM(getElement(_returnEnv, document),
   InsertMappingAnnotationsResponseDocument.class,
   getEnvelopeNamespaces(_returnEnv));

_messageContext.getTransportOut().getSender().cleanup(_messageContext);
return (InsertMappingAnnotationsResponseDocument) object;
  } catch (AxisFault f) {...}

-
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 - v1.0] [please help!] dual blocking client

2006-06-23 Thread Diego

Hi Martin,


Can you post the WSDL??


That's the wsdl.  I hope that it helps.

Thanks,

Diego

?xml version=1.0 encoding=UTF-8?
wsdl:definitions targetNamespace=http://astrodas.org/ws/peer;
xmlns:tns=http://astrodas.org/ws/peer;
   xmlns:tns1=http://astrodas.org/ws/model;
   xmlns:tns2=http://www.ivoa.net/xml/VOTable/v1.1;
   xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
   xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;

 wsdl:types
  xsd:schema elementFormDefault=qualified 
targetNamespace=http://astrodas.org/ws/model;

   xsd:import namespace=http://www.w3.org/2001/XMLSchema; /
   !--
   xsd:import namespace=http://www.ivoa.net/xml/VOTable/v1.1; 
schemaLocation=http://www.ivoa.net/xml/VOTable/v1.1; /

   --
   xsd:import namespace=http://www.ivoa.net/xml/VOTable/v1.1; 
schemaLocation=xsd/votable.xsd /

   !-- insertMappingAnnotations --
   xsd:complexType name=external-object
xsd:sequence
 xsd:element minOccurs=0 maxOccurs=1 name=id 
type=xsd:integer /
 xsd:element minOccurs=1 maxOccurs=1 name=external-id 
type=xsd:integer /
 xsd:element minOccurs=1 maxOccurs=1 name=external-db 
type=xsd:string /
 xsd:element minOccurs=1 maxOccurs=1 name=match 
type=xsd:boolean /

/xsd:sequence
   /xsd:complexType
   xsd:complexType name=annotation
xsd:sequence
 xsd:element minOccurs=0 maxOccurs=1 name=id 
type=xsd:integer /
 xsd:element minOccurs=0 maxOccurs=1 name=type 
type=xsd:string /
 xsd:element minOccurs=1 maxOccurs=1 name=author 
type=xsd:string /
 xsd:element minOccurs=0 maxOccurs=1 name=timestamp 
type=xsd:string /

/xsd:sequence
   /xsd:complexType
   xsd:complexType name=mapping-annotation
xsd:complexContent mixed=false
 xsd:extension base=tns1:annotation
  xsd:sequence
   xsd:element minOccurs=1 maxOccurs=unbounded 
name=external-object type=tns1:external-object /
   xsd:element minOccurs=0 maxOccurs=1 name=text 
type=xsd:string /
   xsd:element minOccurs=0 maxOccurs=1 
name=reliability type=xsd:float /
   xsd:element minOccurs=0 maxOccurs=1 name=ra-mean 
type=xsd:double /
   xsd:element minOccurs=0 maxOccurs=1 name=dec-mean 
   type=xsd:double /

  /xsd:sequence
 /xsd:extension
/xsd:complexContent
   /xsd:complexType
   xsd:element name=insertMappingAnnotations
xsd:complexType
 xsd:sequence
  xsd:element minOccurs=1 maxOccurs=unbounded 
name=mapping-annotation type=tns1:mapping-annotation / 


 /xsd:sequence
/xsd:complexType
   /xsd:element
   xsd:element name=insertMappingAnnotationsResponse
xsd:complexType
 xsd:sequence
  xsd:element minOccurs=1 maxOccurs=1 name=result 
type=xsd:int /

 /xsd:sequence
/xsd:complexType
   /xsd:element 



   !-- executeGlobalMappingTableQuery --
   xsd:element name=executeGlobalMappingTableQuery
xsd:complexType
 xsd:sequence
  xsd:element minOccurs=1 maxOccurs=1 name=query 
type=xsd:string /

 /xsd:sequence
/xsd:complexType
   /xsd:element
   xsd:element name=executeGlobalMappingTableQueryResponse
xsd:complexType 



 xsd:sequence
  xsd:element minOccurs=1 maxOccurs=1 ref=tns2:VOTABLE /
 /xsd:sequence
/xsd:complexType
   /xsd:element
  /xsd:schema
 /wsdl:types

 !-- insertMappingAnnotations --
 wsdl:message name=insertMappingAnnotationsMessage 



  wsdl:part name=body element=tns1:insertMappingAnnotations /
 /wsdl:message
 wsdl:message name=insertMappingAnnotationsResponseMessage
  wsdl:part name=body element=tns1:insertMappingAnnotationsResponse /
 /wsdl:message
 !-- executeGlobalMappingTableQuery --
 wsdl:message name=executeGlobalMappingTableQueryMessage
  wsdl:part name=body element=tns1:executeGlobalMappingTableQuery /
 /wsdl:message
 wsdl:message name=executeGlobalMappingTableQueryResponseMessage 



  wsdl:part name=body 
element=tns1:executeGlobalMappingTableQueryResponse /

 /wsdl:message

 wsdl:portType name=AstrodasPeer
  wsdl:operation name=insertMappingAnnotations
   wsdl:documentationStores an array of annotations in the annotation 
backend database/wsdl:documentation

   wsdl:input message=tns:insertMappingAnnotationsMessage /
   wsdl:output message=tns:insertMappingAnnotationsResponseMessage /
  /wsdl:operation
  wsdl:operation name=executeGlobalMappingTableQuery 



   wsdl:documentationExecutes a query on the global mapping table of 
the p2p network of annotation/wsdl:documentation

   wsdl:input message=tns:executeGlobalMappingTableQueryMessage /
   wsdl:output 
message=tns:executeGlobalMappingTableQueryResponseMessage /

  /wsdl:operation
 /wsdl:portType

 wsdl:binding name=AstrodasPeerBinding type=tns:AstrodasPeer
  soap:binding transport=http://schemas.xmlsoap.org/soap/http; 
style=document /

  wsdl:operation name=insertMappingAnnotations
   soap:operation 

https with WS

2006-06-23 Thread Vineet_Vashisht

Hello All,
I
am unable to get the https to work with WS. I have followed many posts
and other srticles on the web and I have tried just about all they have
suggested but am still unsuccessful. I was wondering if someone could help
me out.
I am using JDK1.4 with Axis2 (1.0) generated
client (WSDL2Java) to access an https WS hosted by a third party vendor.
Currently I am getting a sun.security.validator.ValidatorException:
No trusted certificate found
Any help would be appreciated.
On a sidenote, I was able to get this
to work using Axis 1.1 client stub (WSDL2Java) with JDK1.3 (inside WebSphere
Studio)
Vineet

adding handler into client

2006-06-23 Thread Jansen Werner
Hallo everybody,

I need to add a log handler to my axis client. I don't want to use
client-config.wsdd but want to include the handler in the code.

What I figured out, is that I can use service.getHandlerRegistry() to
get the registry.

But: Which chain needs to be modified? Which one has to include my Log
Handler? And how is it called (QName)?

No idea  :)

Thanks in advance,

Werner

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



Re: Is Axis Ws-I compliant

2006-06-23 Thread Martin Gainty
Title: RE: Is Axis Ws-I compliant



Good Morning Stephen-'Literal' is WS-I 
compliantencoded is not WS-I compliant..
changing binding characteristic to RPC-encoded to 
RPC-literal will make your implementation WS-I compliant
Taing,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: 
  Price, Stephen 
  To: 'axis-user@ws.apache.org' 
  Sent: Friday, June 23, 2006 6:32 AM
  Subject: RE: Is Axis Ws-I compliant
  
  Hi Davanum, thanks for that. So what you are saying is that we 
  should be OK using axis once our service and wsdl are WS-I compliant ? Can you 
  recommend any tools for testing whether our wsdl/schema is WS-I compliant 
  ?
  Thanks, Stephen 
  -Original Message- From: 
  Davanum Srinivas [mailto:[EMAIL PROTECTED]] Sent: 23 June 2006 11:18 To: axis-user@ws.apache.org 
  Subject: Re: Is Axis Ws-I compliant 
  No toolkit is ever 100% compliant. Yes, it is possible to 
  write a WS-I compliant service and client using some 
  of the toolkits including Axis/Axis2. Did you 
  understand the distinction? The key is tesing with WS-I compliant testing tools and tweaking the wsdl and schema to 
  make sure they are complaint and cross checking sample 
  messages on the wire to make sure they are 
  compliant. 
  -- dims 
  On 6/23/06, Price, Stephen [EMAIL PROTECTED] 
  wrote:   
Hi, just starting for 
  the first time developing a component to communicate with a web service. 
  Our client has sent us the wsdl and we were going to use Axis to convert 
  the wsdlto java to call the web service. Our client has told us that we 
  shouldn't use axis as their service is WS-I compliant, whereas Axis is 
  not. I am not 100% sure about this. Can anyone tell me ?
   Thanks,  Stephen 
  Stephen 
  Price  Software Developer  TerraNua  
   
   
  Phone: (+) 353 1 614 5585
  E-mail: [EMAIL PROTECTED] 
   
  Website: www.TerraNua.com  
   
   TerraNua Ltd., registered 
  in Ireland no. 288648. Registered 
  office: Hardwicke House, Upper Hatch Street, Dublin 2. 
  Telephone +353-1-6145400. Any 
  comments or statements made are not necessarily 
  those of Fidelity Investments, its 
  subsidiaries, or affiliates.

  - 
   To unsubscribe, e-mail: 
  [EMAIL PROTECTED]  For 
  additional commands, e-mail: [EMAIL PROTECTED]   
  -- Davanum Srinivas : http://people.apache.org/~dims/ 
  - 
  To unsubscribe, e-mail: 
  [EMAIL PROTECTED] For additional 
  commands, e-mail: [EMAIL PROTECTED] 



Re: Strange SOAP Reply...

2006-06-23 Thread Martin Gainty



Good Morning Mo-Can we see the 
WSDL?
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: 
  mo 
  To: axis-user@ws.apache.org 
  Sent: Thursday, June 22, 2006 8:34 
  AM
  Subject: Strange SOAP Reply...
  Hello list,I've developed my first axis-based service, 
  which methods give back complex types. It works fine until i call a 
  method, which gives back an array of a complex type. The data is correct, but 
  the response contains a number before and after the soapmessage. This causes 
  parser errors on the client side, and I want to understand what this numbers 
  stand for and how I can get rid of them! Thanks for any 
  help,MoAnd here the response:1560?xml version="1.0" 
  encoding="utf-8"? soapenv:Envelope xmlns:soapenv=" http://schemas.xmlsoaporg/soap/envelope/" 
  xmlns:xsd="http://www.w3.org/2001/XMLSchema" 

   xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance" 
  soapenv:Body ns1:getTop10InKatResponse 
  soapenv:encodingStyle=" 
  http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://ws.mydomain.com" 
  getTop10InKatReturn soapenc:arrayType="ns2:Top10Tune[10]" 
   
  xsi:type="soapenc:Array" 
   
  xmlns:ns2="http://mydomain/wservices/FlashService 
  " 
   
  xmlns:soapenc="http://schemas.xmlsoaporg/soap/encoding/" 
  getTop10InKatReturn href=""/ 
   
  getTop10InKatReturn 
  href=""/ 
  getTop10InKatReturn 
  href=""/ 
   ten getTop10InKatReturn #id0 to #id9 . 
   
  /getTop10InKatReturn/ns1:getTop10InKatResponsemultiRef 
  id="id1" soapenc:root="0" 
   
  soapenv:encodingStyle=" 
  http://schemas.xmlsoap.org/soap/encoding/" 
   
  xsi:type="ns3:Top10Tune" 
   
  xmlns:soapenc=" 
  http://schemas.xmlsoap.org/soap/encoding/" 
   
  xmlns:ns3="http:/mydomain/wservices/FlashService" 
  categoryid xsi:type="xsd:int"1/categoryid 
   
  count 
  xsi:type="xsd:int"322/count 
  id 
  xsi:type="xsd:int"2/id 
  name xsi:type="xsd:string"number 2/name 
   
  position 
  xsi:type="xsd:int"2/position/multiRefmultiRef 
  id="id8" soapenc:root="0" 
   
  soapenv:encodingStyle=" http://schemas.xmlsoaporg/soap/encoding/" 
   
  xsi:type="ns4:Top10Tune" 
   
  xmlns:ns4=" 
  http://mydomain/wservices/FlashService" 
   
  xmlns:soapenc="http://schemas.xmlsoaporg/soap/encoding/" 
  categoryid xsi:type="xsd:int"1/categoryid 
   
  count 
  xsi:type="xsd:int"42/count 
  id 
  xsi:type="xsd:int"9/id 
  name xsi:type="xsd:string"number 9/name 
   
  position 
  xsi:type="xsd:int"9/position/multiRefmultiRef 
  id="id0" soapenc:root="0" 
   
  soapenv:encodingStyle=" http://schemas.xmlsoaporg/soap/encoding/" 
   
  xsi:type="ns5:Top10Tune" 
   
  xmlns:ns5=" 
  http://mydomain/wservices/FlashService" 
   
  xmlns:soapenc="http://schemas.xmlsoaporg/soap/encoding/" 
  categoryid xsi:type="xsd:int"1/categoryid 
   
  count 
  xsi:type="xsd:int"332/count 
  id 
  xsi:type="xsd:int"1/id 
  name xsi:type="xsd:string"number 1/name 
   
  position 
  xsi:type="xsd:int"1/position/multiRef.. ten 
  multiRes id0 to 
  id9/soapenv:Body/soapenv:Envelope0


[Axis2] Problem on cache setting, Nightly build 22 Jun 06

2006-06-23 Thread Wan Kaveevivitchai


  According to email about sending large file, the problem of 
sending 10MB attachment was solve by deployment of the Nightly build 
Axis2.war version released on 22 Jun 06. However, it has some problem with 
sending the larger attachment because it seems like cacheattachment is not 
working eventhough all the configuration about cache has been set.


 The error i got is OutofMemory error, we have tried provide bigger 
memory and everything is fine. Can anyone tell me that how should i 
configure the cache properly?


 Sathita



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



RE: Is Axis Ws-I compliant

2006-06-23 Thread Price, Stephen
Title: Message



Thanks 
Martin, so is it just a matter of changing the WSDL to make it WSI compliant 
?

  
  -Original Message-From: Martin Gainty 
  [mailto:[EMAIL PROTECTED] Sent: 23 June 2006 13:05To: 
  axis-user@ws.apache.orgSubject: Re: Is Axis Ws-I 
  compliant
  Good Morning Stephen-'Literal' is WS-I 
  compliantencoded is not WS-I compliant..
  changing binding characteristic to RPC-encoded to 
  RPC-literal will make your implementation WS-I compliant
  Taing,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: 
Price, Stephen 
To: 'axis-user@ws.apache.org' 
Sent: Friday, June 23, 2006 6:32 
AM
Subject: RE: Is Axis Ws-I 
compliant

Hi Davanum, thanks for that. So what you are saying is that 
we should be OK using axis once our service and wsdl are WS-I compliant ? 
Can you recommend any tools for testing whether our wsdl/schema is WS-I 
compliant ?
Thanks, Stephen 
-Original Message- From: 
Davanum Srinivas [mailto:[EMAIL PROTECTED]] 
Sent: 23 June 2006 11:18 To: 
axis-user@ws.apache.org 
Subject: Re: Is Axis Ws-I compliant 
No toolkit is ever 100% compliant. Yes, it is possible to 
write a WS-I compliant service and client using some 
of the toolkits including Axis/Axis2. Did you 
understand the distinction? The key is tesing with WS-I compliant testing tools and tweaking the wsdl and schema to 
make sure they are complaint and cross checking 
sample messages on the wire to make sure they are 
compliant. 
-- dims 
On 6/23/06, Price, Stephen 
[EMAIL PROTECTED] wrote:
 Hi, just starting for the first time developing 
a component to communicate with a web service. Our client has sent us 
the wsdl and we were going to use Axis to convert the wsdlto java to 
call the web service. Our client has told us that we shouldn't use 
axis as their service is WS-I compliant, whereas Axis is not. I am not 
100% sure about this. Can anyone tell me ?
 Thanks,  Stephen 

Stephen Price  Software Developer 
 TerraNua  
 
 
Phone: (+) 353 1 614 5585
E-mail: [EMAIL PROTECTED] 
 
Website: www.TerraNua.com  
 
 TerraNua Ltd., registered 
in Ireland no. 288648. Registered 
office: Hardwicke House, Upper Hatch Street, Dublin 2. 
Telephone +353-1-6145400. Any 
comments or statements made are not necessarily 
those of Fidelity Investments, its 
subsidiaries, or affiliates.
  
- 
 To unsubscribe, e-mail: 
[EMAIL PROTECTED]  For 
additional commands, e-mail: [EMAIL PROTECTED]   
-- Davanum Srinivas : http://people.apache.org/~dims/ 
- 
To unsubscribe, e-mail: 
[EMAIL PROTECTED] For additional 
commands, e-mail: [EMAIL PROTECTED] 



Re: Is Axis Ws-I compliant

2006-06-23 Thread Rodrigo Ruiz

Did you mention your client is the one hosting the service?

In that case, if they give you a valid WS-I compliant WSDL, Axis 1.4 
should work for you. Just generate your stubs with wsdl2java and use them.


Regards,
Rodrigo Ruiz

Price, Stephen wrote:
Thanks Martin, so is it just a matter of changing the WSDL to make it 
WSI compliant ?


-Original Message-
*From:* Martin Gainty [mailto:[EMAIL PROTECTED]
*Sent:* 23 June 2006 13:05
*To:* axis-user@ws.apache.org
*Subject:* Re: Is Axis Ws-I compliant

Good Morning Stephen-

'Literal' is WS-I compliant
encoded is not WS-I compliant..
changing binding characteristic to RPC-encoded to RPC-literal will
make your implementation WS-I compliant

Taing,
Martin --
This email message and any files transmitted with it contain
confidential
information intended only for the person(s) to whom this email
message is
addressed.  If you have received this email message in error, please
notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.

- Original Message -
*From:* Price, Stephen mailto:[EMAIL PROTECTED]
*To:* 'axis-user@ws.apache.org' mailto:'axis-user@ws.apache.org'
*Sent:* Friday, June 23, 2006 6:32 AM
*Subject:* RE: Is Axis Ws-I compliant

Hi Davanum, thanks for that. So what you are saying is that we
should be OK using axis once our service and wsdl are WS-I
compliant ? Can you recommend any tools for testing whether our
wsdl/schema is WS-I compliant ?

Thanks,
Stephen

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: 23 June 2006 11:18
To: axis-user@ws.apache.org mailto:axis-user@ws.apache.org
Subject: Re: Is Axis Ws-I compliant


No toolkit is ever 100% compliant. Yes, it is possible to write
a WS-I
compliant service and client using some of the toolkits including
Axis/Axis2. Did you understand the distinction? The key is
tesing with
WS-I compliant testing tools and tweaking the wsdl and schema to
make
sure they are complaint and cross checking sample messages on
the wire
to make sure they are compliant.

-- dims

On 6/23/06, Price, Stephen [EMAIL PROTECTED] wrote:
 
 
 
  Hi, just starting  for the first time developing a component
to communicate with a web service. Our  client has sent us the
wsdl and we were going to use Axis to convert the wsdlto  java
to call the web service. Our client has told us that we
shouldn't use axis  as their service is WS-I compliant, whereas
Axis is not. I am not 100% sure  about this. Can anyone tell me ?

  Thanks,
  Stephen
 
 
 
   Stephen Price
  Software Developer
  TerraNua
  

 Phone:  (+) 353 1 614 5585
 
 
   E-mail:  [EMAIL PROTECTED]
   Website:  www.TerraNua.com
  

   TerraNua Ltd., registered in Ireland no. 288648.
Registeredoffice: Hardwicke House, Upper Hatch Street,
Dublin 2. Telephone+353-1-6145400. Any comments or
statements made are not necessarily thoseof Fidelity
Investments, its subsidiaries, or affiliates.

 
 
-

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



-- 
Davanum Srinivas : http://people.apache.org/~dims/


-

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




No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.9.2/373 - Release Date: 22/06/2006


--
---
GRIDSYSTEMSRodrigo Ruiz Aguayo
Parc Bit - Son Espanyol
07120 Palma de Mallorcamailto:[EMAIL PROTECTED]
Baleares - España  Tel:+34-971435085 Fax:+34-971435082
http://www.gridsystems.com
---


--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.9.2/373 - Release Date: 22/06/2006


-
To unsubscribe, e-mail: [EMAIL 

RE: Is Axis Ws-I compliant

2006-06-23 Thread Price, Stephen
Title: RE: Is Axis Ws-I compliant





Hi Rodrigo, yes the client will be hosting the service and is giving us the wsdl. So that means we should be fine. 
Thanks for the help,
Stephen


-Original Message-
From: Rodrigo Ruiz [mailto:[EMAIL PROTECTED]] 
Sent: 23 June 2006 13:47
To: axis-user@ws.apache.org
Subject: Re: Is Axis Ws-I compliant



Did you mention your client is the one hosting the service?


In that case, if they give you a valid WS-I compliant WSDL, Axis 1.4 
should work for you. Just generate your stubs with wsdl2java and use them.


Regards,
Rodrigo Ruiz


Price, Stephen wrote:
 Thanks Martin, so is it just a matter of changing the WSDL to make it 
 WSI compliant ?
 
 -Original Message-
 *From:* Martin Gainty [mailto:[EMAIL PROTECTED]]
 *Sent:* 23 June 2006 13:05
 *To:* axis-user@ws.apache.org
 *Subject:* Re: Is Axis Ws-I compliant
 
 Good Morning Stephen-
 
 'Literal' is WS-I compliant
 encoded is not WS-I compliant..
 changing binding characteristic to RPC-encoded to RPC-literal will
 make your implementation WS-I compliant
 
 Taing,
 Martin --
 This email message and any files transmitted with it contain
 confidential
 information intended only for the person(s) to whom this email
 message is
 addressed. If you have received this email message in error, please
 notify
 the sender immediately by telephone or email and destroy the original
 message without making a copy. Thank you.
 
 - Original Message -
 *From:* Price, Stephen mailto:[EMAIL PROTECTED]
 *To:* 'axis-user@ws.apache.org' mailto:'axis-user@ws.apache.org'
 *Sent:* Friday, June 23, 2006 6:32 AM
 *Subject:* RE: Is Axis Ws-I compliant
 
 Hi Davanum, thanks for that. So what you are saying is that we
 should be OK using axis once our service and wsdl are WS-I
 compliant ? Can you recommend any tools for testing whether our
 wsdl/schema is WS-I compliant ?
 
 Thanks,
 Stephen
 
 -Original Message-
 From: Davanum Srinivas [mailto:[EMAIL PROTECTED]]
 Sent: 23 June 2006 11:18
 To: axis-user@ws.apache.org mailto:axis-user@ws.apache.org
 Subject: Re: Is Axis Ws-I compliant
 
 
 No toolkit is ever 100% compliant. Yes, it is possible to write
 a WS-I
 compliant service and client using some of the toolkits including
 Axis/Axis2. Did you understand the distinction? The key is
 tesing with
 WS-I compliant testing tools and tweaking the wsdl and schema to
 make
 sure they are complaint and cross checking sample messages on
 the wire
 to make sure they are compliant.
 
 -- dims
 
 On 6/23/06, Price, Stephen [EMAIL PROTECTED] wrote:
 
 
 
  Hi, just starting for the first time developing a component
 to communicate with a web service. Our client has sent us the
 wsdl and we were going to use Axis to convert the wsdlto java
 to call the web service. Our client has told us that we
 shouldn't use axis as their service is WS-I compliant, whereas
 Axis is not. I am not 100% sure about this. Can anyone tell me ?
 
  Thanks,
  Stephen
 
 
 
  Stephen Price
  Software Developer
  TerraNua
  
 
  Phone: (+) 353 1 614 5585
 
 
  E-mail: [EMAIL PROTECTED]
  Website: www.TerraNua.com
  
 
  TerraNua Ltd., registered in Ireland no. 288648.
 Registered office: Hardwicke House, Upper Hatch Street,
 Dublin 2. Telephone +353-1-6145400. Any comments or
 statements made are not necessarily those of Fidelity
 Investments, its subsidiaries, or affiliates.
 
 
 
 -
 
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 
 -- 
 Davanum Srinivas : http://people.apache.org/~dims/
 
 -
 
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 No virus found in this incoming message.
 Checked by AVG Free Edition.
 Version: 7.1.394 / Virus Database: 268.9.2/373 - Release Date: 22/06/2006


-- 
---
GRIDSYSTEMS Rodrigo Ruiz Aguayo
Parc Bit - Son Espanyol
07120 Palma de Mallorca mailto:[EMAIL PROTECTED]
Baleares - España Tel:+34-971435085 Fax:+34-971435082
http://www.gridsystems.com
---



-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.9.2/373 - Release Date: 22/06/2006



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





unknown exception

2006-06-23 Thread Vineet_Vashisht

I am getting an exception while using
axis2 with a https Webservice whose client stub has been generated using
WSDL2Java. How can I dig in further to see what is going on? This does
not give me a lot of information. Earlier I thought that there was some
SSL auth problem but now I am thinking this might be unrelated. Please
advise.

org.apache.axis2.AxisFault:
Axis2 transport error : Unknown; nested exception is: 
   
org.apache.axis2.AxisFault: Axis2 transport error : Unknown; nested
exception is: 
   
org.apache.axis2.AxisFault: Axis2 transport error : Unknown; nested
exception is: 
   
org.apache.axis2.AxisFault: Axis2 transport error : Unknown
   
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:222)
   
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:641)
   
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:341)
   
at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:279)
   
at com.anf.ads.Sales10Stub.sales10(Sales10Stub.java:123)
   
at com.anf.ads.axis2.TestAxis2Client.main(TestAxis2Client.java:69)
Caused by: org.apache.axis2.AxisFault:
Axis2 transport error : Unknown; nested exception is: 
   
org.apache.axis2.AxisFault: Axis2 transport error : Unknown
   
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:304)
   
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:206)
   
... 5 more
Caused by: org.apache.axis2.AxisFault:
Axis2 transport error : Unknown
   
at org.apache.axis2.transport.http.SOAPOverHTTPSender.send(SOAPOverHTTPSender.java:141)
   
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:298)
   
... 6 more



[axis2] Does axis2 support any or choice?

2006-06-23 Thread Tim Oertel


I'm trying to set up a server with a service something like:

xs:element name=Update
   xs:complexType
   xs:all
  xs:element type=xs:anyType name=id   minOccurs=1 maxOccurs=1/
  xs:element type=xs:anyType name=arg0 minOccurs=0 maxOccurs=1/
  xs:element type=xs:anyType name=arg1 minOccurs=0 maxOccurs=1/
   /xs:all
   /xs:complexType
/xs:element

I'm invoking the service via REST via http://.../Update?id=123arg0=test+01

When my hand-written service is invoked, I do a toString on the OMElement
my service is invoked with.  It returns:
axis2ns1:Update xmlns:axis2ns1=http://foo/xsd; /

... without any of my parameters.

When I specify the collection as xs:sequence rather than xs:all, invoke
it the same way, it returns:

axis2ns2:Update xmlns:axis2ns2=http://foo/xsd;
id14723/id
arg0test 01/arg0
arg1tox/arg1
/axis2ns2:Update

which is what I expect (both from this and from the any case above), but
it doesn't seem to honor the minOccurs attribute in the wsdl.  Also, it
doesn't seem to care about ordering (which is fine with me, but seems
contrary to the WSDL spec).

Am I probably (or definitely) doing something wrong, or are these bugs in
axis2?

Thanks,
- Tim



--
Tim Oertel   |Why should I be content to simply
VP Engineering   | live in this world, when I, as a
Ashergroup, Inc. | human being, can CREATE it?!
IM via jabber: [EMAIL PROTECTED]

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



Re: [axis2] Does axis2 support any or choice?

2006-06-23 Thread Tim Oertel

Crud, I forgot to mention I was using the 1.0 release, but have
since upgraded and re-tested against the 2006/06/22 nightly snapshot.


Tim Oertel wrote, on or about 6/23/2006 9:20 AM:

I'm trying to set up a server with a service something like:

xs:element name=Update
xs:complexType
xs:all
   xs:element type=xs:anyType name=id   minOccurs=1 maxOccurs=1/
   xs:element type=xs:anyType name=arg0 minOccurs=0 maxOccurs=1/
   xs:element type=xs:anyType name=arg1 minOccurs=0 maxOccurs=1/
/xs:all
/xs:complexType
/xs:element

I'm invoking the service via REST via http://.../Update?id=123arg0=test+01

When my hand-written service is invoked, I do a toString on the OMElement
my service is invoked with.  It returns:
axis2ns1:Update xmlns:axis2ns1=http://foo/xsd; /

... without any of my parameters.

When I specify the collection as xs:sequence rather than xs:all, invoke
it the same way, it returns:

axis2ns2:Update xmlns:axis2ns2=http://foo/xsd;
id14723/id
arg0test 01/arg0
arg1tox/arg1
/axis2ns2:Update

which is what I expect (both from this and from the any case above), but
it doesn't seem to honor the minOccurs attribute in the wsdl.  Also, it
doesn't seem to care about ordering (which is fine with me, but seems
contrary to the WSDL spec).

Am I probably (or definitely) doing something wrong, or are these bugs in
axis2?

Thanks,
- Tim






--
Tim Oertel   |Why should I be content to simply
VP Engineering   | live in this world, when I, as a
Ashergroup, Inc. | human being, can CREATE it?!
IM via jabber: [EMAIL PROTECTED]

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



[Axis2] NullPointerException in OutInAxisOperationClient

2006-06-23 Thread Michele Mazzucco
Hi all,

I'm trying to send a message from a web service A to a web service B,
but I get this exception:

ERROR
ncl.qosp.controller.scheduler.weighted.WeightedAvgRespTimeServiceHandler
- java.lang.NullPointerException
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:260)
at 
org.apache.axis2.client.ServiceClient.sendRobust(ServiceClient.java:350)
at 
org.apache.axis2.client.ServiceClient.sendRobust(ServiceClient.java:330)
at
ncl.qosp.controller.scheduler.weighted.WeightedAvgRespTimeServiceHandler.client(WeightedAvgRespTimeServiceHandler.java:609)
at
ncl.qosp.controller.scheduler.weighted.WeightedAvgRespTimeServiceHandler.send(WeightedAvgRespTimeServiceHandler.java:560)
at
ncl.qosp.controller.scheduler.weighted.WeightedAvgRespTimeServiceHandler.addResource(WeightedAvgRespTimeServiceHandler.java:333)
at
ncl.qosp.controller.scheduler.weighted.WeightedAvgRespTimeScheduler.requireResources(WeightedAvgRespTimeScheduler.java:296)
at
ncl.qosp.controller.scheduler.weighted.WeightedAvgRespTimeServiceHandler.setOptimalValue(WeightedAvgRespTimeServiceHandler.java:284)
at
ncl.qosp.controller.scheduler.weighted.WeightedAvgRespTimeScheduler$ReminderTask.reallocateResources(WeightedAvgRespTimeScheduler.java:549)
at
ncl.qosp.controller.scheduler.weighted.WeightedAvgRespTimeScheduler$ReminderTask.run(WeightedAvgRespTimeScheduler.java:519)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)


The chunk of code generating the above exception is:

EndpointReference targetEPR = new EndpointReference(target);
Options options = new Options();
options.setTo(targetEPR);
options.setAction(urn:echo);
options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
options.setUseSeparateListener(true);

ServiceClient sender = new ServiceClient();
sender.engageModule(new QName(Constants.MODULE_ADDRESSING));
sender.setOptions(options);

try {
sender.sendRobust(r.request);
} catch (Exception e) {
StringWriter sw = new StringWriter();
PrintWriter pw = new PrintWriter(sw);
e.printStackTrace(pw);
log.error(sw.getBuffer().toString());
pw.close();
}


Please note that this code works if a sendReceiveNonBlocking() call is
used instead of sendRobust().


Should I create a JIRA?


Michele

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



Re: [axis2] Does axis2 support any or choice?

2006-06-23 Thread Ajith Ranabahu

Hi,
Report two Jiras and link them together.

Ajith

On 6/23/06, Tim Oertel [EMAIL PROTECTED] wrote:

Ajith Ranabahu wrote, on or about 6/23/2006 9:25 AM:
 Hi Tim,
 Please log a Jira. This smells like a bug !

Should this be written up as two bugs?  One for all support
and one for sequence not respecting minOccurs/maxOccurs?


 Ajith

 On 6/23/06, Tim Oertel [EMAIL PROTECTED] wrote:
 Crud, I forgot to mention I was using the 1.0 release, but have
 since upgraded and re-tested against the 2006/06/22 nightly snapshot.


 Tim Oertel wrote, on or about 6/23/2006 9:20 AM:
 I'm trying to set up a server with a service something like:

 xs:element name=Update
 xs:complexType
 xs:all
xs:element type=xs:anyType name=id   minOccurs=1 
maxOccurs=1/
xs:element type=xs:anyType name=arg0 minOccurs=0 
maxOccurs=1/
xs:element type=xs:anyType name=arg1 minOccurs=0 
maxOccurs=1/
 /xs:all
 /xs:complexType
 /xs:element

 I'm invoking the service via REST via http://.../Update?id=123arg0=test+01

 When my hand-written service is invoked, I do a toString on the OMElement
 my service is invoked with.  It returns:
 axis2ns1:Update xmlns:axis2ns1=http://foo/xsd; /

 ... without any of my parameters.

 When I specify the collection as xs:sequence rather than xs:all, invoke
 it the same way, it returns:

 axis2ns2:Update xmlns:axis2ns2=http://foo/xsd;
   id14723/id
   arg0test 01/arg0
   arg1tox/arg1
 /axis2ns2:Update

 which is what I expect (both from this and from the any case above), but
 it doesn't seem to honor the minOccurs attribute in the wsdl.  Also, it
 doesn't seem to care about ordering (which is fine with me, but seems
 contrary to the WSDL spec).

 Am I probably (or definitely) doing something wrong, or are these bugs in
 axis2?

 Thanks,
 - Tim


--
Tim Oertel   |Why should I be content to simply
VP Engineering   | live in this world, when I, as a
Ashergroup, Inc. | human being, can CREATE it?!
IM via jabber: [EMAIL PROTECTED]

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





--
Ajith Ranabahu

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



RE: https with WS

2006-06-23 Thread Ben Ethridge








Hi, Vineet. Did you see my post from a
couple of days ago on this?













From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Friday, June 23, 2006 7:54
AM
To: axis-user@ws.apache.org
Subject: https with WS





Hello
All, 


   I am unable to get the https to work with WS. I have
followed many posts and other srticles on the web and I have tried just about
all they have suggested but am still unsuccessful. I was wondering if someone
could help me out. 

I
am using JDK1.4 with Axis2 (1.0) generated client (WSDL2Java) to access an
https WS hosted by a third party vendor. 

Currently
I am getting a sun.security.validator.ValidatorException:
No trusted certificate found 

Any
help would be appreciated. 

On
a sidenote, I was able to get this to work using Axis 1.1 client stub
(WSDL2Java) with JDK1.3 (inside WebSphere Studio) 

Vineet



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.





[Axis2] NullPointerException in AbstractHTTPSender

2006-06-23 Thread Michele Mazzucco
Hi all,

I get a NullPointerException in AbstractHTTPSender:238 when the
following message is received:

?xml version='1.0' encoding='utf-8'?
soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:wsa=http://www.w3.org/2005/08/addressing;
soapenv:Header
node:qosp xmlns:node=http://org.ncl.ac.uk/qosp;
node:messageType
node:valueResult/node:value
/node:messageType
node:timeInfo
node:scheduling0/node:scheduling
node:queue0/node:queue
node:inNetwork0/node:inNetwork
node:codestore0/node:codestore
node:deployment0/node:deployment
node:execution1151071762667/node:execution
/node:timeInfo
/node:qosp


wsa:Tohttp://localhost:8080/axis2/services/RoutingService/wsa:To
wsa:ReplyTo /
wsa:From

wsa:Addresshttp://10.8.149.156:18080/axis2/services/MyService/wsa:Address
/wsa:From
wsa:FaultTo

wsa:Addresshttp://10.8.149.156:18080/axis2/services/MyService/wsa:Address
/wsa:FaultTo

wsa:MessageIDurn:uuid:B8218EB67E48B4770A11510717626673/wsa:MessageID
wsa:Actionurn:result/wsa:Action
wsa:RelatesTo
wsa:RelationshipType=http://www.w3.org/2005/08/addressing/reply;urn:uuid:6C3FF1911E6B2CC78411510717620891/wsa:RelatesTo
/soapenv:Header
soapenv:Body
client:echo
xmlns:client=http://org.ncl.ac.uk/qosp/clients/codestore;
xmlns:tns=http://ws.apache.org/axis2;
client:TextQoSP Echo String/client:Text
/client:echo
/soapenv:Body
/soapenv:Envelope


I tried to modify
$CATALINA_HOME\\webapps\axis2\WEB-INF\classes\log4j.properties, however
I still see the stack trace on the console only.

My axis 2 version is SNAPSHOT Jun 08, 2006.


Michele

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



RE: https with WS

2006-06-23 Thread Vineet_Vashisht

Ben, thanks for the reply. Yours was
one of the posts that I had read before eventually posting the email. The
article you referenced was one that I had worked with in the past.

I am still very unclear on how the whole
SSL works with WebServices. The axis 1.1 is working but I am not sure if
I even set up all the certificates etc. correctly. it just somehow works.
As far as the Axis 2.0 client goes, I am beginning to think it might be
something unrelated to authentication and certificates altogether.

I just get a transport error - unknown
from axis. I have tried a few things to try to give it more information
(changing axis2.xml) but they have had no impact. 

Looking at the actuall SOAP requests
generated, I can see that axis1.1 uses HTTP 1.0 and Axis2.0 uses HTTP1.1
. Do you think that could cause a problem?

The person who hosts the WS says he
is receiving no traffic from me whatsoever. When I change the endpoint
to oint to a generic https site, the message that I get back shows me that
I WAS able to at least reach that generic https site. Somehow the WS host
never sees anything at all.






Ben Ethridge
[EMAIL PROTECTED] 
06/23/2006 10:05 AM



Please respond to
axis-user@ws.apache.org





To
axis-user@ws.apache.org


cc



Subject
RE: https with WS








Hi, Vineet. Did you see my
post from a couple of days ago on this?





From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Friday, June 23, 2006 7:54 AM
To: axis-user@ws.apache.org
Subject: https with WS

Hello All,

I am unable
to get the https to work with WS. I have followed many posts and other
srticles on the web and I have tried just about all they have suggested
but am still unsuccessful. I was wondering if someone could help me out.

I am using JDK1.4 with Axis2 (1.0) generated
client (WSDL2Java) to access an https WS hosted by a third party vendor.

Currently I am getting a sun.security.validator.ValidatorException:
No trusted certificate found

Any help would be appreciated.

On a sidenote, I was able to get this
to work using Axis 1.1 client stub (WSDL2Java) with JDK1.3 (inside WebSphere
Studio) 
Vineet
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.



[AXIS 1.4]Problem in running axis with security

2006-06-23 Thread Kashif Saleem
Hi All,
   I am trying to run axis1.4 on apache-tomcat-5.5.17 but I am getting the 
following error on Axis happiness page:



Axis Happiness Page
Examining webapp configuration

Language: [en] [ja]
Needed Components

* Found SAAJ API ( javax.xml.soap.SOAPMessage ) at 
/a/green/cs/research/medic/home0/paramedic/ucackxs/Desktop/softwares/apache-tomcat-5.5.17/webapps/axis/WEB-INF/lib/saaj.jar

* Found JAX-RPC API ( javax.xml.rpc.Service ) at 
/a/green/cs/research/medic/home0/paramedic/ucackxs/Desktop/softwares/apache-tomcat-5.5.17/webapps/axis/WEB-INF/lib/jaxrpc.jar

* Found Apache-Axis ( org.apache.axis.transport.http.AxisServlet ) at 
/a/green/cs/research/medic/home0/paramedic/ucackxs/Desktop/softwares/apache-tomcat-5.5.17/webapps/axis/WEB-INF/lib/axis.jar

* Found Jakarta-Commons Discovery ( org.apache.commons.discovery.Resource ) 
at 
/a/green/cs/research/medic/home0/paramedic/ucackxs/Desktop/softwares/apache-tomcat-5.5.17/webapps/axis/WEB-INF/lib/commons-discovery-0.2.jar

* Found Jakarta-Commons Logging ( org.apache.commons.logging.Log ) at 
/a/green/cs/research/medic/home0/paramedic/ucackxs/Desktop/softwares/apache-tomcat-5.5.17/bin/commons-logging-api.jar

* Found Log4j ( org.apache.log4j.Layout ) at 
/a/green/cs/research/medic/home0/paramedic/ucackxs/Desktop/softwares/apache-tomcat-5.5.17/webapps/axis/WEB-INF/lib/log4j-1.2.8.jar

* Found IBM's WSDL4Java ( com.ibm.wsdl.factory.WSDLFactoryImpl ) at 
/a/green/cs/research/medic/home0/paramedic/ucackxs/Desktop/softwares/apache-tomcat-5.5.17/webapps/axis/WEB-INF/lib/wsdl4j-1.5.1.jar

* Found JAXP implementation ( javax.xml.parsers.SAXParserFactory ) at an 
unknown location

* Found Activation API ( javax.activation.DataHandler ) at 
/a/green/cs/research/medic/home0/paramedic/ucackxs/Desktop/softwares/apache-tomcat-5.5.17/webapps/axis/WEB-INF/lib/activation.jar

Optional Components

  Warning: could not find class javax.mail.internet.MimeMessage from file 
mail.jar
  Attachments will not work.
  See http://java.sun.com/products/javamail/

  Warning: could not find a dependency of class 
org.apache.xml.security.Init from file XML Security is not supported.

  See http://xml.apache.org/security/ {4}
  The root cause was: org/apache/xpath/compiler/FuncLoader
  This can happen e.g. if org.apache.xml.security.Init is in the 'common' 
classpath, but a dependency like activation.jar is only in the webapp classpath.

* Found Java Secure Socket Extension ( javax.net.ssl.SSLSocketFactory ) at 
an unknown location

The core axis libraries are present.2 wanted optional axis librar(ies) are 
missing

  Note: On Tomcat 4.x and Java1.4, you may need to put libraries that 
contain java.* or javax.* packages into CATALINA_HOME/common/lib
  jaxrpc.jar and saaj.jar are two such libraries.

  Note: Even if everything this page probes for is present, there is no 
guarantee your web service will work, because there are many configuration 
options that we do not check for. These tests are necessary but not sufficient

Examining Application Server

  Servlet version   2.4
  XML Parserorg.apache.xerces.jaxp.SAXParserImpl
  XML ParserLocation
/a/green/cs/research/medic/home0/paramedic/ucackxs/Desktop/softwares/apache-tomcat-5.5.17/shared/lib/xercesImpl.jar

Examining System Properties

java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
sun.boot.library.path=/usr/opt/SUNWjava/jdk1.5.0_05/jre/lib/i386
java.vm.version=1.5.0_05-b05
shared.loader=${catalina.base}/shared/classes,${catalina.base}/shared/lib/*.jar
java.vm.vendor=Sun Microsystems Inc.
java.vendor.url=http://java.sun.com/
path.separator=:
java.vm.name=Java HotSpot(TM) Client VM
tomcat.util.buf.StringCache.byte.enabled=true
file.encoding.pkg=sun.io
java.util.logging.config.file=/cs/research/medic/home0/paramedic/ucackxs/Desktop/softwares/apache-tomcat-5.5.17/conf/logging.properties
user.country=GB
sun.os.patch.level=unknown
java.vm.specification.name=Java Virtual Machine Specification
user.dir=/a/green/cs/research/medic/home0/paramedic/ucackxs/Desktop/softwares/apache-tomcat-5.5.17/webapps/axis/WEB-INF/lib
java.runtime.version=1.5.0_05-b05
java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
java.endorsed.dirs=/cs/research/medic/home0/paramedic/ucackxs/Desktop/softwares/apache-tomcat-5.5.17/common/endorsed
os.arch=i386
java.io.tmpdir=/cs/research/medic/home0/paramedic/ucackxs/Desktop/softwares/apache-tomcat-5.5.17/temp
line.separator=

java.vm.specification.vendor=Sun Microsystems Inc.
java.util.logging.manager=org.apache.juli.ClassLoaderLogManager
java.naming.factory.url.pkgs=org.apache.naming
os.name=Linux
sun.jnu.encoding=UTF-8
java.library.path=/usr/opt/SUNWjava/jdk1.5.0_05/jre/lib/i386/client:/usr/opt/SUNWjava/jdk1.5.0_05/jre/lib/i386:/usr/opt/SUNWjava/jdk1.5.0_05/jre/../lib/i386:/opt/ucl/lib:/usr/X11R6/lib
java.specification.name=Java Platform API Specification
java.class.version=49.0

RE: https with WS

2006-06-23 Thread Ben Ethridge








Sorry. Dont know. Ive only
been working with 1.x so far. Have you googled the error in the log? Or maybe
someone who knows 2.x could help.



Ben











From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Friday, June 23, 2006 10:13
AM
To: axis-user@ws.apache.org
Subject: RE: https with WS






Ben, thanks for the reply. Yours was one of the posts
that I had read before eventually posting the email. The article you referenced
was one that I had worked with in the past. 

I
am still very unclear on how the whole SSL works with WebServices. The axis 1.1
is working but I am not sure if I even set up all the certificates etc.
correctly. it just somehow works. As far as the Axis 2.0 client goes, I am
beginning to think it might be something unrelated to authentication and
certificates altogether. 

I
just get a transport error - unknown from axis. I have tried a few things to
try to give it more information (changing axis2.xml) but they have had no
impact. 

Looking
at the actuall SOAP requests generated, I can see that axis1.1 uses HTTP 1.0
and Axis2.0 uses HTTP1.1 . Do you think that could cause a problem?


The
person who hosts the WS says he is receiving no traffic from me whatsoever.
When I change the endpoint to oint to a generic https site, the message that I
get back shows me that I WAS able to at least reach that generic https site.
Somehow the WS host never sees anything at all. 





 
  
  Ben Ethridge
  [EMAIL PROTECTED] 
  06/23/2006 10:05 AM 
  
   

Please
respond to
axis-user@ws.apache.org

   
  
  
  
  
  
   

To


axis-user@ws.apache.org


   
   

cc




   
   

Subject


RE: https with WS

   
  
  
  
   






   
  
  
  
 





Hi, Vineet. Did you see my post from a couple of
days ago on this? 
 
 










From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Friday, June 23, 2006 7:54 AM
To: axis-user@ws.apache.org
Subject: https with WS 
 

Hello
All, 


   I am unable to get the https to work with WS. I have
followed many posts and other srticles on the web and I have tried just about
all they have suggested but am still unsuccessful. I was wondering if someone
could help me out. 

I
am using JDK1.4 with Axis2 (1.0) generated client (WSDL2Java) to access an
https WS hosted by a third party vendor. 

Currently
I am getting a sun.security.validator.ValidatorException:
No trusted certificate found 

Any
help would be appreciated. 

On
a sidenote, I was able to get this to work using Axis 1.1 client stub
(WSDL2Java) with JDK1.3 (inside WebSphere Studio) 

Vineet


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.





[axis2] - wsdl2java - exception

2006-06-23 Thread Gmail
hey I have similar problem. I'm new to axis2. I have wsdl from which in 
axis 1.* I have succesfully generated java code, but in axis2 I got 
following exception:


Exception in thread main 
org.apache.axis2.wsdl.codegen.CodeGenerationException: 
org.apache.axis2.wsdl.codegen.CodeGenerationException: 
java.lang.NullPointerException
   at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:185)
 

   at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
   at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: 
java.lang.NullPointerException
   at 
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitStub(AxisServiceBasedMultiLanguageEmitter.java:171)
 

   at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:176)
 

   ... 2 more
Caused by: java.lang.NullPointerException
   at 
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.getFaultParamElements(AxisServiceBasedMultiLanguageEmitter.java:1511)
 

   at 
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.getFaultElement(AxisServiceBasedMultiLanguageEmitter.java:1449)
 

   at 
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.loadOperations(AxisServiceBasedMultiLanguageEmitter.java:1199)
 

   at 
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.createDOMDocumentForCallbackHandler(AxisServiceBasedMultiLanguageEmitter.java:572)
 

   at 
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.writeCallBackHandlers(AxisServiceBasedMultiLanguageEmitter.java:551)
 

   at 
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitStubFromService(AxisServiceBasedMultiLanguageEmitter.java:266)
 

   at 
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitStub(AxisServiceBasedMultiLanguageEmitter.java:169)
 

   ... 3 more

linux: i686
java: sun-jdk1.5.0_06
axis:  2

I typed command :
sh WSDL2Java.sh -uri xxx.wsdl -ss -sd -d xmlbeans -o xxx

Is there any problem with wsdl types, namespaces in axis2 or something 
else please help me.

best regards
Borowski Filip

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



Re-post: How can I pass attachment file name

2006-06-23 Thread Qinjian Jian
All,

I am using Axis1.4. When doing attachment, I found it seems no elegant
way to pass the file name attached. Below is my source code fragment:

String sourceDir = C:\\temp\\example.doc;
//Get the file from the filesystem
FileDataSource fileDS = new FileDataSource(sourceDir);
DataHandler handler = new DataHandler(fileDS);

//Create the attachment as a MTOM attachment
AttachmentPart attachment = message.createAttachmentPart();
String fileName = getFileName(sourceDir);
attachment.addMimeHeader(DocumentDescriptor.FILE_NAME,
fileName);
 
message.getAttachmentsImpl().setSendType(
AttachmentsImpl.SEND_TYPE_MTOM);
attachment.setDataHandler(handler);
message.addAttachmentPart(attachment);

 

As you saw above, I have to add one more MimeHead to pass the file name.
It works but I think there must be better way to do this. Any idea?

Thanks
 
Tim Jian
Momentum systems, Inc.




NOTICE: This message (including any attachments) from Momentum Systems, Inc. 
contains information that is PRIVILEGED and CONFIDENTIAL.  If you are not an 
intended recipient, you are hereby notified that any dissemination of this 
message is strictly prohibited.  If you have received this message in error, 
please do not read, copy or forward this message.  Please permanently delete 
all copies and any attachments and notify the sender immediately by reply email 
or by calling our Office at 703.740.9300.

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



Re: [Axis2] NullPointerException in AbstractHTTPSender

2006-06-23 Thread Michele Mazzucco
Hi all,

yes, the reason of the null pointer is definitively the RelatesTo. Is it
possible to prevent the sender side to add it?

Michele

Michele Mazzucco wrote:
 Could it happen because of the RelatesTo 'field'? If so, how can I
 remove it (the request is sent by service A.foo, while the response
 should be received by service A.foo1)?
 
 Thanks,
 Michele
 
 Michele Mazzucco wrote:
 Hi all,

 I get a NullPointerException in AbstractHTTPSender:238 when the
 following message is received:

 ?xml version='1.0' encoding='utf-8'?
 soapenv:Envelope
 xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
 xmlns:wsa=http://www.w3.org/2005/08/addressing;
  soapenv:Header
  node:qosp xmlns:node=http://org.ncl.ac.uk/qosp;
  node:messageType
  node:valueResult/node:value
  /node:messageType
  node:timeInfo
  node:scheduling0/node:scheduling
  node:queue0/node:queue
  node:inNetwork0/node:inNetwork
  node:codestore0/node:codestore
  node:deployment0/node:deployment
  node:execution1151071762667/node:execution
  /node:timeInfo
  /node:qosp
  
  
 wsa:Tohttp://localhost:8080/axis2/services/RoutingService/wsa:To
  wsa:ReplyTo /
  wsa:From
  
 wsa:Addresshttp://10.8.149.156:18080/axis2/services/MyService/wsa:Address
  /wsa:From
  wsa:FaultTo
  
 wsa:Addresshttp://10.8.149.156:18080/axis2/services/MyService/wsa:Address
  /wsa:FaultTo
  
 wsa:MessageIDurn:uuid:B8218EB67E48B4770A11510717626673/wsa:MessageID
  wsa:Actionurn:result/wsa:Action
  wsa:RelatesTo
 wsa:RelationshipType=http://www.w3.org/2005/08/addressing/reply;urn:uuid:6C3FF1911E6B2CC78411510717620891/wsa:RelatesTo
  /soapenv:Header
  soapenv:Body
  client:echo
 xmlns:client=http://org.ncl.ac.uk/qosp/clients/codestore;
 xmlns:tns=http://ws.apache.org/axis2;
  client:TextQoSP Echo String/client:Text
  /client:echo
  /soapenv:Body
 /soapenv:Envelope


 I tried to modify
 $CATALINA_HOME\\webapps\axis2\WEB-INF\classes\log4j.properties, however
 I still see the stack trace on the console only.

 My axis 2 version is SNAPSHOT Jun 08, 2006.


 Michele

 -
 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]
 

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



Problem in running axis with wss4j security

2006-06-23 Thread Kashif Saleem
Hi All,
   I installed axis-1.3 on apache-tomcat-5.5.17 but I am accessing the 
happiness page,I am getting the following message:



Axis Happiness Page
Examining webapp configuration

Language: [en] [ja]
Needed Components

* Found SAAJ API ( javax.xml.soap.SOAPMessage ) at 
/a/green/cs/research/medic/home0/paramedic/ucackxs/Desktop/softwares/apache-tomcat-5.5.17/webapps/axis/WEB-INF/lib/saaj.jar

* Found JAX-RPC API ( javax.xml.rpc.Service ) at 
* Found JAXP implementation ( javax.xml.parsers.SAXParserFactory ) at an 
unknown location


..
.
* Found Activation API ( javax.activation.DataHandler ) at 
/a/green/cs/research/medic/home0/paramedic/ucackxs/Desktop/softwares/apache-tomcat-5.5.17/common/lib/activation.jar

Optional Components

  Warning: could not find class javax.mail.internet.MimeMessage from file 
mail.jar
  Attachments will not work.
  See http://java.sun.com/products/javamail/

  Warning: could not find class org.apache.xml.security.Init from file 
xmlsec.jar
  XML Security is not supported.
  See http://xml.apache.org/security/

* Found Java Secure Socket Extension ( javax.net.ssl.SSLSocketFactory ) at 
an unknown location

The core axis libraries are present.2 wanted optional axis librar(ies) are 
missing

  Note: On Tomcat 4.x and Java1.4, you may need to put libraries that 
contain java.* or javax.* packages into CATALINA_HOME/common/lib
  jaxrpc.jar and saaj.jar are two such libraries.

  Note: Even if everything this page probes for is present, there is no 
guarantee your web service will work, because there are many configuration 
options that we do not check for. These tests are necessary but not sufficient
.
...
.

Platform: Apache Tomcat/5.5.17 








I checked my classpath which includes all the required libraries.I would 
appreciate if someone could shed a light on the cause of this weird behavior.

Kind Regards
Kashif Saleem

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



RE: https with WS

2006-06-23 Thread Vineet_Vashisht

Just FYI. I was able to get it to work
with minimum fuss using Axis2-0.93 instead of Axis2-1.0 . Have no
idea why but 0.93 seems a lot easier to work with as far as just generating
a client goes.






Ben Ethridge
[EMAIL PROTECTED] 
06/23/2006 10:32 AM



Please respond to
axis-user@ws.apache.org





To
axis-user@ws.apache.org


cc



Subject
RE: https with WS








Sorry. Don’t know. I’ve only
been working with 1.x so far. Have you googled the error in the log? Or
maybe someone who knows 2.x could help.

Ben




From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Friday, June 23, 2006 10:13 AM
To: axis-user@ws.apache.org
Subject: RE: https with WS


Ben, thanks for the reply. Yours was one of the posts that I had read before
eventually posting the email. The article you referenced was one that I
had worked with in the past.


I am still very unclear on how the whole SSL works with WebServices. The
axis 1.1 is working but I am not sure if I even set up all the certificates
etc. correctly. it just somehow works. As far as the Axis 2.0 client goes,
I am beginning to think it might be something unrelated to authentication
and certificates altogether.


I just get a transport error - unknown from axis. I have tried a few things
to try to give it more information (changing axis2.xml) but they have had
no impact. 

Looking at the actuall SOAP requests generated, I can see that axis1.1
uses HTTP 1.0 and Axis2.0 uses HTTP1.1 . Do you think that could cause
a problem? 

The person who hosts the WS says he is receiving no traffic from me whatsoever.
When I change the endpoint to oint to a generic https site, the message
that I get back shows me that I WAS able to at least reach that generic
https site. Somehow the WS host never sees anything at all.






Ben Ethridge
[EMAIL PROTECTED] 
06/23/2006 10:05 AM






Please respond to
axis-user@ws.apache.org






To
axis-user@ws.apache.org



cc



Subject
RE: https with WS











Hi, Vineet. Did you see my post from a couple of days ago on this?

 
 





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

Sent: Friday, June 23, 2006 7:54 AM
To: axis-user@ws.apache.org
Subject: https with WS 
 
Hello All,

I am unable
to get the https to work with WS. I have followed many posts and other
srticles on the web and I have tried just about all they have suggested
but am still unsuccessful. I was wondering if someone could help me out.

I am using JDK1.4 with Axis2 (1.0) generated
client (WSDL2Java) to access an https WS hosted by a third party vendor.

Currently I am getting a sun.security.validator.ValidatorException:
No trusted certificate found

Any help would be appreciated.

On a sidenote, I was able to get this
to work using Axis 1.1 client stub (WSDL2Java) with JDK1.3 (inside WebSphere
Studio) 
Vineet

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: Problem in running axis with wss4j security

2006-06-23 Thread Ben Ethridge
What's the wierd behavior? You mean the missing activation.jar?

Ben

-Original Message-
From: Kashif Saleem [mailto:[EMAIL PROTECTED] 
Sent: Friday, June 23, 2006 12:17 PM
To: axis-user@ws.apache.org
Subject: Problem in running axis with wss4j security

Hi All,
   I installed axis-1.3 on apache-tomcat-5.5.17 but I am accessing
the happiness page,I am getting the following message:



Axis Happiness Page
Examining webapp configuration

Language: [en] [ja]
Needed Components

* Found SAAJ API ( javax.xml.soap.SOAPMessage ) at
/a/green/cs/research/medic/home0/paramedic/ucackxs/Desktop/softwares/apa
che-tomcat-5.5.17/webapps/axis/WEB-INF/lib/saaj.jar

* Found JAX-RPC API ( javax.xml.rpc.Service ) at 
* Found JAXP implementation ( javax.xml.parsers.SAXParserFactory )
at an unknown location


..
.
* Found Activation API ( javax.activation.DataHandler ) at
/a/green/cs/research/medic/home0/paramedic/ucackxs/Desktop/softwares/apa
che-tomcat-5.5.17/common/lib/activation.jar

Optional Components

  Warning: could not find class javax.mail.internet.MimeMessage from
file mail.jar
  Attachments will not work.
  See http://java.sun.com/products/javamail/

  Warning: could not find class org.apache.xml.security.Init from
file xmlsec.jar
  XML Security is not supported.
  See http://xml.apache.org/security/

* Found Java Secure Socket Extension (
javax.net.ssl.SSLSocketFactory ) at an unknown location

The core axis libraries are present.2 wanted optional axis librar(ies)
are missing

  Note: On Tomcat 4.x and Java1.4, you may need to put libraries
that contain java.* or javax.* packages into CATALINA_HOME/common/lib
  jaxrpc.jar and saaj.jar are two such libraries.

  Note: Even if everything this page probes for is present, there is
no guarantee your web service will work, because there are many
configuration options that we do not check for. These tests are
necessary but not sufficient
.
...
.

Platform: Apache Tomcat/5.5.17 








I checked my classpath which includes all the required libraries.I would
appreciate if someone could shed a light on the cause of this weird
behavior.

Kind Regards
Kashif Saleem

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

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.

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



Issues deploying axis 2.0

2006-06-23 Thread Srikanth


Hi,


 I am trying to create a RESTful webservice using Java and
hence looking at Axis to use that as a platform. I just downlaoded the
axis.war file and when I deployed it in my servlet container (tomcat
5.0.30) and tried to access the service (http://localhost:8080/axis2),
I encounter the following exception:

type Exception report
message 
description The server encountered an internal error () that prevented it from fulfilling this request.
exception 
javax.servlet.ServletException: org/apache/tools/ant/BuildException	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:244)	javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
root cause 
java.lang.NoClassDefFoundError: org/apache/tools/ant/BuildException	org.apache.jasper.JspCompilationContext.createCompiler(JspCompilationContext.java:197)	org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java
:508)	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295)	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)	org.apache.jasper.servlet.JspServlet.service(JspServlet.java
:236)	javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
note The full stack trace of the root cause is available in the Apache Tomcat/5.0.30 logs.

Could someone help me out as to what is wrong with my installation ???.

Thanks,
Srikanth K.




Re: [Axis2] Missing jar file?

2006-06-23 Thread Ron Turner
Thanks for your response, Ajith.  This is with respect to Axis2 v1.0.  Looks 
like I missed including neethi-1.0.1.jar on my classpath and so couldn't find 
the correct packaging of OMPolicyReader.  The version of OMPolicyReader I did 
have available was in package org.apache.ws.commons.om - I presume this is out 
of date?

Ron

- Original Message -
From: Ajith Ranabahu [EMAIL PROTECTED]
Date: Thursday, June 22, 2006 9:39 pm
Subject: Re: [Axis2] Missing jar file?

 Hi,
 What is the Axis2 version we are talking about here ? BTW
 OMPolicyReader is in the Neethi.**.jar AFAIR.
 
 Ajith
 
 On 6/22/06, Ron Turner [EMAIL PROTECTED] wrote:
  Thanks, Kinichiro.  In axiom-api-1.0.jar I can see
 
  org.apache.axiom.om.OMContainer
 
  but the version of OMPolicyReader I have is looking for
 
  org.apache.ws.commons.om.OMContainer
 
  when it's instantiated.  Just for curiosity's sake, where in 
 your Axis2 distribution is OMPolicyReader located?
 
  Best regards,
 
  Ron
 
  - Original Message -
  From: Kinichiro Inoguchi [EMAIL PROTECTED]
  Date: Thursday, June 22, 2006 9:02 am
  Subject: Re: [Axis2] Missing jar file?
 
   Hi,
   It's axiom-api-1.0.jar.
  
   __
   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]
  
  
 
 
  -
 
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 -- 
 Ajith Ranabahu
 
 ---
 --
 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: NullPointerException in MessageContext.setEnvelope(MessageContext.java:681)

2006-06-23 Thread Ted Jones
IP VP,

I encountered the same thing (or something very similar) with Axis 1.3. I was 
hoping an upgrade to Axis2 would fix my problem. Have you had any luck 
resolving?

Thanks,
Ted Jones

-Original Message-
From: ip vp [mailto:[EMAIL PROTECTED] 
Sent: Thursday, June 22, 2006 4:28 PM
To: axis-user@ws.apache.org
Subject: NullPointerException in 
MessageContext.setEnvelope(MessageContext.java:681)
Importance: High

Hi all,

I am trying  to call a comercial partner webservice thats return a string and 
do not need input parameters.

Based on User guide ( Client for echoVoid Operation)

I am doing the followig:

- generating java code  based on wsdl, using ecplise plugin.

- did a very simple client whit the following code:


GeneratedStubClass myStub = new GeneratedStubClass();

System.out.println(myStub.MethodWithOperationName());



I am getting the following error:

java.lang.NullPointerException
at
org.apache.axis2.context.MessageContext.setEnvelope(MessageContext.java:681)



This error occurs with all variants of WSDL2JAVA configuration: with and 
without databinds, using get, using post, using soap...


What am  I doing wrong ?


thanks in advance

IP VP

_
Você sabe em qual Copa o Pelé vestiu a camisa 10 pela 1a. vez? 
http://copa.br.msn.com/extra/curiosidades/1958/


-
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: Issues deploying axis 2.0

2006-06-23 Thread Anne Thomas Manes
If you want to implement a RESTful service, I recommend you use Axis2 rather than Axis.On 6/23/06, Srikanth [EMAIL PROTECTED]
 wrote:

Hi,


 I am trying to create a RESTful webservice using Java and
hence looking at Axis to use that as a platform. I just downlaoded the
axis.war file and when I deployed it in my servlet container (tomcat
5.0.30) and tried to access the service (http://localhost:8080/axis2),
I encounter the following exception:

type Exception report
message 
description The server encountered an internal error () that prevented it from fulfilling this request.
exception 
javax.servlet.ServletException: org/apache/tools/ant/BuildException	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:244)	javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
root cause 
java.lang.NoClassDefFoundError: org/apache/tools/ant/BuildException	org.apache.jasper.JspCompilationContext.createCompiler(JspCompilationContext.java:197)	org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java
:508)	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295)	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)	org.apache.jasper.servlet.JspServlet.service(JspServlet.java
:236)	javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
note The full stack trace of the root cause is available in the Apache Tomcat/5.0.30 logs.

Could someone help me out as to what is wrong with my installation ???.

Thanks,
Srikanth K.






RE: NullPointerException in MessageContext.setEnvelope(MessageContext.java:681)

2006-06-23 Thread ip vp

Hi Ted Jones,

Thanks for your response.

I am already using AXIS2.

I did not solve this problem yet .

Any suggestions are welcome.


regards

IP VP



From: Ted Jones [EMAIL PROTECTED]
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: RE: NullPointerException in 
MessageContext.setEnvelope(MessageContext.java:681)

Date: Fri, 23 Jun 2006 13:30:34 -0500

IP VP,

I encountered the same thing (or something very similar) with Axis 1.3. I 
was hoping an upgrade to Axis2 would fix my problem. Have you had any luck 
resolving?


Thanks,
Ted Jones

-Original Message-
From: ip vp [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 22, 2006 4:28 PM
To: axis-user@ws.apache.org
Subject: NullPointerException in 
MessageContext.setEnvelope(MessageContext.java:681)

Importance: High

Hi all,

I am trying  to call a comercial partner webservice thats return a string 
and do not need input parameters.


Based on User guide ( Client for echoVoid Operation)

I am doing the followig:

- generating java code  based on wsdl, using ecplise plugin.

- did a very simple client whit the following code:


GeneratedStubClass myStub = new GeneratedStubClass();

System.out.println(myStub.MethodWithOperationName());



I am getting the following error:

java.lang.NullPointerException
at
org.apache.axis2.context.MessageContext.setEnvelope(MessageContext.java:681)



This error occurs with all variants of WSDL2JAVA configuration: with and 
without databinds, using get, using post, using soap...



What am  I doing wrong ?


thanks in advance

IP VP

_





-
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]



_
Você sabe desde que ano as camisas de futebol são numeradas?  
http://copa.br.msn.com/extra/curiosidades/futebol2/



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



Re: NullPointerException in MessageContext.setEnvelope(MessageContext.java:681)

2006-06-23 Thread Martin Gainty

Good Afternoon Ted-

Could we see the WSDL?

Thanks,
Martin
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.

- Original Message - 
From: Ted Jones [EMAIL PROTECTED]

To: axis-user@ws.apache.org
Sent: Friday, June 23, 2006 2:30 PM
Subject: RE: NullPointerException in 
MessageContext.setEnvelope(MessageContext.java:681)



IP VP,

I encountered the same thing (or something very similar) with Axis 1.3. I 
was hoping an upgrade to Axis2 would fix my problem. Have you had any luck 
resolving?


Thanks,
Ted Jones

-Original Message-
From: ip vp [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 22, 2006 4:28 PM
To: axis-user@ws.apache.org
Subject: NullPointerException in 
MessageContext.setEnvelope(MessageContext.java:681)

Importance: High

Hi all,

I am trying  to call a comercial partner webservice thats return a string 
and do not need input parameters.


Based on User guide ( Client for echoVoid Operation)

I am doing the followig:

- generating java code  based on wsdl, using ecplise plugin.

- did a very simple client whit the following code:


GeneratedStubClass myStub = new GeneratedStubClass();

System.out.println(myStub.MethodWithOperationName());



I am getting the following error:

java.lang.NullPointerException
at
org.apache.axis2.context.MessageContext.setEnvelope(MessageContext.java:681)



This error occurs with all variants of WSDL2JAVA configuration: with and 
without databinds, using get, using post, using soap...



What am  I doing wrong ?


thanks in advance

IP VP

_
Você sabe em qual Copa o Pelé vestiu a camisa 10 pela 1a. vez?
http://copa.br.msn.com/extra/curiosidades/1958/


-
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]


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



[axis2] dynamic return types / external configuration / inheritance

2006-06-23 Thread studium-sbr
Hi to everyone,

suggest the follwing scenario:
- service with one method. 
- I'm NOT using code generated skeletons, but simple Java classes.
- depending on the request parameters, the returned objects are different. All 
returned objects have a superclass in common.
  Someone explained, how to achieve inheritance with axis2 a few days ago; but 
I need some more ;)
- I'm able to fully define the mentioned superclass; I would be able to 
implement all types as beans.
- For the subclasses I would like to hold things sort of configurable from 
outside - means without compiling the service again.
- therefore I thought about placing somewhere a XML-Schema Definition

My concern about tis is the following:
- with this I'm to my opinion not able to produce an always valid WSDL, cause 
the interface is not always the same?

My questions:
1) what are your comments on how to solve such a scenario
2) how to return a valid, meaningful WSDL-File to the possible clients 
3) as I'm farely new to axis2 and web services, any hints on examples, or short 
descriptions on how to make the service use beans, would be great.
  AFAIK I probably have to write my own MessageReceiver.
4) currently I'm working with OMElements an the RawXMLINOutMessageReceiver; do 
I have to switch that for using beans.

Hope anybody could shed some light on that

Nice weekend all

Bille

_
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071distributionid=0071


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



Re: Is Axis Ws-I compliant

2006-06-23 Thread Anne Thomas Manes
Just to clarify some of the comments made in this thread...As Dims said, no toolkit is 100% compliant. In fact it isn't really appropriate to refer to a toolkit as compliant. WS-I compliance applies to a specific service, not to the tools used to implement the service. The more appropriate question to ask is whether you can use Axis to build WS-I compliant services. As Dims said, this is true. You can build WS-I compliant services using Axis. 
Martin implied that the only factor affecting WS-I compliance is whether you use a literal schema or SOAP encoding to format the message. Message encoding is by far the most noticable contraint imposed by the WS-I Basic Profile, but there are in fact many rules and constraints defined by the WS-I BP that go way beyond just the simple choice between use=literal and use=encoded. 
In any case, if your partner supplies you with a WS-I compliant WSDL, Axis can generate a WS-I compliant client that can speak to the WS-I compliant service.AnneOn 6/23/06, 
Price, Stephen [EMAIL PROTECTED] wrote:









Hi Rodrigo, yes the client will be hosting the service and is giving us the wsdl. So that means we should be fine. 
Thanks for the help,
Stephen


-Original Message-
From: Rodrigo Ruiz [mailto:[EMAIL PROTECTED]] 
Sent: 23 June 2006 13:47
To: axis-user@ws.apache.org
Subject: Re: Is Axis Ws-I compliant



Did you mention your client is the one hosting the service?


In that case, if they give you a valid WS-I compliant WSDL, Axis 1.4 
should work for you. Just generate your stubs with wsdl2java and use them.


Regards,
Rodrigo Ruiz


Price, Stephen wrote:
 Thanks Martin, so is it just a matter of changing the WSDL to make it 
 WSI compliant ?
 
 -Original Message-
 *From:* Martin Gainty [mailto:[EMAIL PROTECTED]]
 *Sent:* 23 June 2006 13:05
 *To:* axis-user@ws.apache.org
 *Subject:* Re: Is Axis Ws-I compliant
 
 Good Morning Stephen-
 
 'Literal' is WS-I compliant
 encoded is not WS-I compliant..
 changing binding characteristic to RPC-encoded to RPC-literal will
 make your implementation WS-I compliant
 
 Taing,
 Martin --
 This email message and any files transmitted with it contain
 confidential
 information intended only for the person(s) to whom this email
 message is
 addressed. If you have received this email message in error, please
 notify
 the sender immediately by telephone or email and destroy the original
 message without making a copy. Thank you.
 
 - Original Message -
 *From:* Price, Stephen mailto:[EMAIL PROTECTED]

 *To:* 'axis-user@ws.apache.org' 
mailto:'axis-user@ws.apache.org'
 *Sent:* Friday, June 23, 2006 6:32 AM
 *Subject:* RE: Is Axis Ws-I compliant
 
 Hi Davanum, thanks for that. So what you are saying is that we
 should be OK using axis once our service and wsdl are WS-I
 compliant ? Can you recommend any tools for testing whether our
 wsdl/schema is WS-I compliant ?
 
 Thanks,
 Stephen
 
 -Original Message-
 From: Davanum Srinivas [mailto:[EMAIL PROTECTED]]
 Sent: 23 June 2006 11:18
 To: axis-user@ws.apache.org 
mailto:axis-user@ws.apache.org
 Subject: Re: Is Axis Ws-I compliant
 
 
 No toolkit is ever 100% compliant. Yes, it is possible to write
 a WS-I
 compliant service and client using some of the toolkits including
 Axis/Axis2. Did you understand the distinction? The key is
 tesing with
 WS-I compliant testing tools and tweaking the wsdl and schema to
 make
 sure they are complaint and cross checking sample messages on
 the wire
 to make sure they are compliant.
 
 -- dims
 
 On 6/23/06, Price, Stephen [EMAIL PROTECTED] wrote:

 
 
 
  Hi, just starting for the first time developing a component
 to communicate with a web service. Our client has sent us the
 wsdl and we were going to use Axis to convert the wsdlto java
 to call the web service. Our client has told us that we
 shouldn't use axis as their service is WS-I compliant, whereas
 Axis is not. I am not 100% sure about this. Can anyone tell me ?
 
  Thanks,
  Stephen
 
 
 
  Stephen Price
  Software Developer
  TerraNua
  
 
  Phone: (+) 353 1 614 5585
 
 
  E-mail: [EMAIL PROTECTED]
  Website: www.TerraNua.com
  
 
  TerraNua Ltd., registered in Ireland no. 288648.
 Registered office: Hardwicke House, Upper Hatch Street,
 Dublin 2. Telephone +353-1-6145400. Any comments or
 statements made are not necessarily those of Fidelity
 Investments, its subsidiaries, or affiliates.
 
 
 
 -
 
  To unsubscribe, e-mail: [EMAIL PROTECTED]

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

 
 
 
 
 
 -- 
 Davanum Srinivas : http://people.apache.org/~dims/
 
 -
 
 To unsubscribe, e-mail: [EMAIL PROTECTED]

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

 
 
 
 
 No virus found in this 

RE: NullPointerException in MessageContext.setEnvelope(MessageContext.java:681)

2006-06-23 Thread Ted Jones



Martin,
Here is the WSDL:definitions name="widgetServices" targetNamespace="http://com.widgets/test" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://com.widgets/test" xmlns:schema1="http://www.widgets.com/bqt_Output" types xsd:schema targetNamespace="http://com.widgets/test" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xsd:import namespace="http://www.widgets.com/bqt_Output" schemaLocation="http://chicago:8080/test/servlet/ArtifactDocumentService/test/bqt_Output.xsd" / /xsd:schema /types message name="bqt_SMALLA_getSMALLA_Input" documentationInput message for operation bqt_SMALLA/getSMALLA./documentation /message message name="bqt_SMALLA_getSMALLA_SMALLA_OutputMsg" documentationOutput message for operation bqt_SMALLA/getSMALLA./documentation part name="bqt_SMALLA_getSMALLA_SMALLA_OutputMsg" element="schema1:SMALLA_Output" / /message portType name="bqt_SMALLA" operation name="getSMALLA" input name="Input" message="tns:bqt_SMALLA_getSMALLA_Input" / output name="SMALLA_OutputMsg" message="tns:bqt_SMALLA_getSMALLA_SMALLA_OutputMsg" / /operation /portType binding name="bqt_SMALLA" type="tns:bqt_SMALLA" soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" / operation name="getSMALLA" soap:operation style="document" soapAction="bqt_WS.bqt_SMALLA.getSMALLA" / input name="Input" soap:body use="literal" / /input output name="SMALLA_OutputMsg" soap:body use="literal" / /output /operation /binding service name="widgetsDataServices" port name="bqt_SMALLA" binding="tns:bqt_SMALLA" soap:address location="http://chicago:8080/test/services/service" / /port /service/definitionsHere is the WSDD:deployment name="test" xmlns="http://xml.apache.org/axis/wsdd/"  xmlns:java="http://xml.apache.org/axis/wsdd/providers/java" xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance" !-- note that either style="message" OR provider="java:MSG" both work -- service name="service" provider="java:MSG"  parameter name="className" value="com.widgets.soap.lds.service.DataServiceWebService" / parameter name="allowedMethods" value="executeDataservice" / /service/deployment 

I am executing a web service with no input 
parametersso the SOAP body is empty like so:

soapenv:Envelope 
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" 
soapenv:Body//soapenv:Envelope

I am getting an NPE returned before I even 
hit my Web Service, so I am assuming the exception is happening in Axis 
somewhere (I'm not seeing a stack trace). Here is the 
response:

?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 
soapenv:Fault 
faultcodesoapenv:Server.userException/faultcode 
faultstringjava.lang.NullPointerException/faultstring 
detail/ 
/soapenv:Fault/soapenv:Body/soapenv:Envelope

I get this using Coral and Systinet as my 
clients. When I generate an Axis client, I do not get an NPE but I get a node 
added to my body with the operation name in it (which I don't want to 
seeas my logic depends on the body to be empty when no inputs are 
provided).
Any help would be greatly appreciated!Thanks,Ted Jones-Original Message-From: Martin Gainty [mailto:[EMAIL PROTECTED]]Sent: Friday, June 23, 2006 2:20 PMTo: axis-user@ws.apache.orgSubject: Re: NullPointerException in MessageContext.setEnvelope(MessageContext.java:681)Good Afternoon Ted-Could we see the WSDL?Thanks,MartinThis email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you.- Original Message -From: "Ted Jones" [EMAIL PROTECTED]To: axis-user@ws.apache.orgSent: Friday, June 23, 2006 2:30 PMSubject: RE: NullPointerException inMessageContext.setEnvelope(MessageContext.java:681)IP VP,I encountered the same thing (or something very similar) with Axis 1.3. I was hoping an upgrade to Axis2 would fix my problem. Have you had any luck resolving?Thanks,Ted Jones-Original Message-From: ip vp [mailto:[EMAIL PROTECTED]]Sent: Thursday, June 22, 2006 4:28 PMTo: axis-user@ws.apache.orgSubject: NullPointerException inMessageContext.setEnvelope(MessageContext.java:681)Importance: HighHi all,I am trying to call a comercial partner webservice thats return a string and do not need input parameters.Based on User guide ( Client for echoVoid Operation)I am doing the followig:- generating java code based on wsdl, using ecplise plugin.- did a very simple client whit the following code:GeneratedStubClass myStub = new GeneratedStubClass();System.out.println(myStub.MethodWithOperationName());I am getting the following 

AXIS Version

2006-06-23 Thread Jeff Lu



Hi,ALL

It is first time for me to post message 
here.
If I am wrong,please kindly tell me what I should 
do.

I have download AXIS version 
1.2RC,1.2.1,1.3,1.4.

Since I use WSDL2Java convert mappoint web service 
to java file.
The stup service is extended from 
org.apach.axis.client.Stup.

The problem is:
when It create a org.apache.axis.client.call, there 
is one method called
setScopedProperty is only supported 1.2RC, it is 
not supported by other version.

Because I want to use other method call:setHeader 
(belonged to Stup)
it is not supported 1.2RC, it is supported 
1.2.1,1.3,1.4

For me, I do not know how to get a solution. Is 
there a version support both of them.
or what is wrong with my step when creating Java 
calss by using WSDL2Java



Best 
RegardsJeff---http://www.mbiztech.comTel:(416)486 
3996x224E_mail:[EMAIL PROTECTED]--


Re: Could I handler the exception in an common error h andling class ?

2006-06-23 Thread studium-sbr
Hi Sukie,

maybe this helps:
http://marc.theaimsgroup.com/?l=axis-userm=115049348304601w=2 
http://marc.theaimsgroup.com/?l=axis-userm=115046828005645w=2
http://www.wso2.net/kb/171


I'm up to do the SOAPFault-Creation and the putting it on the INcoming 
MessageContext in one method:
private void handleException(Exception e, String message){
  // Instantiate the SOAPFault and put it on the MessageContext
}
cause the mechanism is always the same. If you are not interested in the 
details and stack traces there might be an easier way.

HTH

Bille


 -Ursprüngliche Nachricht-
 Von: axis-user@ws.apache.org
 Gesendet: 23.06.06 12:25:58
 An: axis-user@ws.apache.org
 Betreff: Could I handler the exception in an common error handling class ?


 hi all,
 
 I want to handle the exceptions throwed by the services in one common 
 class, and tried to extend the AxisServlet class overwriting doGet() and
 doPost() method, and catch error with code like below :
 
 try {
 super.doGet(request, response);
 } catch (Exception e) {
 // deal the exception
 // like :  System.out.println(--- + e.getMessage);
 }
 
 but nothing happened.
 
 I think Axis doesn't call the service in such methods, so could anybody
 tell me how to do the error handling in common way ? Is there a class
 I can extend ?
 
 Any help or web resources would be greatly appreciated !
 
 Regards,
 - sukie
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


_
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071distributionid=0071


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



Java web service client to .Net web service

2006-06-23 Thread Michael Schwab

Hi,

I am developing a Java web service client using Apache Axis 1.4.  The
client will connect to a .Net version 1.1 + WSE 2 SP3 web service.
The .Net web service requires X.509 based authentication and
signature.

I have created the Java stubs for the web service using WSDL2Java.
The automatically generated code can successfully query the .Net web
service and results in a WSE policy error.

I am attempting to add the signature and authenication to the web
service request.  I have modified the example client security code in
the Axis samples directory.  The certificate that was provided was
created by Microsoft Certificate Authority.  When the code attempts to
sign the SOAP envelope with the certificate, I receive the following
stack trace:

org.apache.xml.security.signature.XMLSignatureException: No installed
provider supports this key: sun.security.rsa.RSAPrivateCrtKeyImpl
Original Exception was
org.apache.xml.security.signature.XMLSignatureException: No installed
provider supports this key: sun.security.rsa.RSAPrivateCrtKeyImpl
Original Exception was java.security.InvalidKeyException: No installed
provider supports this key: sun.security.rsa.RSAPrivateCrtKeyImpl
at org.apache.xml.security.signature.XMLSignature.sign(Unknown Source)
at SignedSOAPEnvelope.init(SignedSOAPEnvelope.java:152)
at SignedSOAPEnvelope.init(SignedSOAPEnvelope.java:106)
at ShortLegalSearchWS.call(ShortLegalSearchWS.java:23)
at TitleDataTesterExe.main(TitleDataTesterExe.java:29)
org.apache.xml.security.signature.XMLSignatureException: No installed
provider supports this key: sun.security.rsa.RSAPrivateCrtKeyImpl
Original Exception was java.security.InvalidKeyException: No installed
provider supports this key: sun.security.rsa.RSAPrivateCrtKeyImpl
at 
org.apache.xml.security.algorithms.implementations.SignatureDSA.engineInitSign(Unknown
Source)
at 
org.apache.xml.security.algorithms.SignatureAlgorithm.initSign(Unknown
Source)
at org.apache.xml.security.signature.XMLSignature.sign(Unknown Source)
at SignedSOAPEnvelope.init(SignedSOAPEnvelope.java:152)
at SignedSOAPEnvelope.init(SignedSOAPEnvelope.java:106)
at ShortLegalSearchWS.call(ShortLegalSearchWS.java:23)
at TitleDataTesterExe.main(TitleDataTesterExe.java:29)
java.security.InvalidKeyException: No installed provider supports this
key: sun.security.rsa.RSAPrivateCrtKeyImpl
at java.security.Signature$Delegate.chooseProvider(Signature.java:1059)
at java.security.Signature$Delegate.engineInitSign(Signature.java:1100)
at java.security.Signature.initSign(Signature.java:485)
at 
org.apache.xml.security.algorithms.implementations.SignatureDSA.engineInitSign(Unknown
Source)
at 
org.apache.xml.security.algorithms.SignatureAlgorithm.initSign(Unknown
Source)
at org.apache.xml.security.signature.XMLSignature.sign(Unknown Source)
at SignedSOAPEnvelope.init(SignedSOAPEnvelope.java:152)
at SignedSOAPEnvelope.init(SignedSOAPEnvelope.java:106)
at ShortLegalSearchWS.call(ShortLegalSearchWS.java:23)
at TitleDataTesterExe.main(TitleDataTesterExe.java:29)
java.lang.RuntimeException:
org.apache.xml.security.signature.XMLSignatureException: No installed
provider supports this key: sun.security.rsa.RSAPrivateCrtKeyImpl
Original Exception was
org.apache.xml.security.signature.XMLSignatureException: No installed
provider supports this key: sun.security.rsa.RSAPrivateCrtKeyImpl
Original Exception was java.security.InvalidKeyException: No installed
provider supports this key: sun.security.rsa.RSAPrivateCrtKeyImpl
at SignedSOAPEnvelope.init(SignedSOAPEnvelope.java:170)
at SignedSOAPEnvelope.init(SignedSOAPEnvelope.java:106)
at ShortLegalSearchWS.call(ShortLegalSearchWS.java:23)
at TitleDataTesterExe.main(TitleDataTesterExe.java:29)

I suspect the default Java security providers do not support RSA signatures.

Could anyone suggest online resources that discuss Java client based
signatures and authentication using X.509 for web services or
interoperating between Java and .Net?  My searches have not provided
significant information.

Thanks,
Michael

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



AxisFault: Unconnected sockets not implemented; nested exceptio

2006-06-23 Thread ip vp

Hi All,

I am getting org.apache.axis2.AxisFault: Unconnected sockets not implemented 
exception.


Whant can be the root cause of this ?




JAVA CODE:
#
import java.security.Security;
import org.apache.axiom.om.OMAbstractFactory;
import org.apache.axiom.om.OMElement;
import org.apache.axiom.om.OMFactory;
import org.apache.axiom.om.OMNamespace;
import org.apache.axis2.AxisFault;
import org.apache.axis2.Constants;
import org.apache.axis2.addressing.EndpointReference;
import org.apache.axis2.client.Options;
import org.apache.axis2.client.ServiceClient;

public class WSClient {

public static void main(String[] args) {
System.setProperty(javax.net.ssl.trustStore,
D:\\clientcert.jks);
System.setProperty(javax.net.ssl.trustStorePassword, 
password123);

try {

OMFactory fac = OMAbstractFactory.getOMFactory();
OMNamespace omNs = fac
.createOMNamespace(

http://www.NAMESAPCEURL;,
methodname);
OMElement method = fac.createOMElement(wsmethodname, 
omNs);

EndpointReference endpoint = new EndpointReference(

https://webserviceurl.com/wsfile.asmx;);

Options options = new Options();

options.setTransportInProtocol(Constants.TRANSPORT_HTTP);

options.setTo(endpoint);

ServiceClient serviceClient = new ServiceClient();
serviceClient.setOptions(options);

OMElement result = serviceClient.sendReceive(method);

System.out.println(result);

} catch (AxisFault axisFault) {
axisFault.printStackTrace();
}

}

}
#


ERROR:

Jun 23, 2006 5:51:27 PM org.apache.commons.httpclient.HttpMethodDirector 
executeWithRetry
INFO: I/O exception (java.net.SocketException) caught when processing 
request: Unconnected sockets not implemented
Jun 23, 2006 5:51:27 PM org.apache.commons.httpclient.HttpMethodDirector 
executeWithRetry

INFO: Retrying request
Jun 23, 2006 5:51:27 PM org.apache.commons.httpclient.HttpMethodDirector 
executeWithRetry
INFO: I/O exception (java.net.SocketException) caught when processing 
request: Unconnected sockets not implemented
Jun 23, 2006 5:51:27 PM org.apache.commons.httpclient.HttpMethodDirector 
executeWithRetry

INFO: Retrying request
Jun 23, 2006 5:51:27 PM org.apache.commons.httpclient.HttpMethodDirector 
executeWithRetry
INFO: I/O exception (java.net.SocketException) caught when processing 
request: Unconnected sockets not implemented
Jun 23, 2006 5:51:27 PM org.apache.commons.httpclient.HttpMethodDirector 
executeWithRetry

INFO: Retrying request
org.apache.axis2.AxisFault: Unconnected sockets not implemented; nested 
exception is:
	java.net.SocketException: Unconnected sockets not implemented; nested 
exception is:
	org.apache.axis2.AxisFault: Unconnected sockets not implemented; nested 
exception is:

java.net.SocketException: Unconnected sockets not implemented
	at 
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:223)

at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:589)
	at 
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:328)
	at 
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:279)
	at 
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:457)
	at 
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:399)

at WSClient.main(WSClient.java:42)
Caused by: org.apache.axis2.AxisFault: Unconnected sockets not implemented; 
nested exception is:

java.net.SocketException: Unconnected sockets not implemented
	at 
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:305)
	at 
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:207)

... 6 more
Caused by: java.net.SocketException: Unconnected sockets not implemented
at javax.net.SocketFactory.createSocket(DashoA12275)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)
	at 
org.apache.commons.httpclient.protocol.ReflectionSocketFactory.createSocket(ReflectionSocketFactory.java:115)
	at 

Re: newbie question about WSDL2JAVA

2006-06-23 Thread studium-sbr
- Generate Java from WSDL
- Select the WSDL-File
- Next page you can leave all the selections. 
- If you want to get the service classes, then you have to additionally select 
Generate serverside code

Thats all

HTH 

Bille
 -Ursprüngliche Nachricht-
 Von: axis-user@ws.apache.org
 Gesendet: 22.06.06 06:39:07
 An: axis-user@ws.apache.org
 Betreff: newbie question about WSDL2JAVA


 Hi All,
 
 
 Sorry if it is a very basic question, but the user guide is not clear for 
 me.
 
 Can somebody send a step by step example about how to build a webservice 
 client?
 
 I am using wsdl2java in eclipse but I do not know what generated classes may 
 be used for what.
 
 I am in doubt about what fields in wizard I need to select to build only a 
 simple soap web service client.
 
 
 
 thanks a lot
 
 _
 COPA 2006: (¯`·._.·[ Ooola ]·._.·Ž¯) e + frases para seu MSN  Clique 
 aqui! http://copa.br.msn.com/extra/frases/
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


_
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071distributionid=0071


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



Re: newbie question about WSDL2JAVA

2006-06-23 Thread ip vp

Hi Bille,

It was ok. I did it. But, what methods and in what sequence I need to invoke 
to access the webservice?


I am doing the followig:

- generating java code  based on wsdl, using ecplise plugin.

- did a very simple client whit the following code:


GeneratedStubClass myStub = new GeneratedStubClass();

System.out.println(myStub.MethodWithOperationName());



I am getting the following error:

java.lang.NullPointerException
at
org.apache.axis2.context.MessageContext.setEnvelope(MessageContext.java:681)



An  other e-mail about this especific error is running in the list


thanks a lot



From: [EMAIL PROTECTED]
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: Re: newbie question about WSDL2JAVA
Date: Fri, 23 Jun 2006 23:04:32 +0200

- Generate Java from WSDL
- Select the WSDL-File
- Next page you can leave all the selections.
- If you want to get the service classes, then you have to additionally 
select Generate serverside code


Thats all

HTH

Bille
 -Ursprüngliche Nachricht-
 Von: axis-user@ws.apache.org
 Gesendet: 22.06.06 06:39:07
 An: axis-user@ws.apache.org
 Betreff: newbie question about WSDL2JAVA


 Hi All,


 Sorry if it is a very basic question, but the user guide is not clear 
for

 me.

 Can somebody send a step by step example about how to build a webservice
 client?

 I am using wsdl2java in eclipse but I do not know what generated classes 
may

 be used for what.

 I am in doubt about what fields in wizard I need to select to build only 
a

 simple soap web service client.



 thanks a lot

 _
 COPA 2006: (¯`·._.·[ Ooola ]·._.·´¯) e + frases para seu MSN  Clique
 aqui! http://copa.br.msn.com/extra/frases/


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



_
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071distributionid=0071


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



_
COPA 2006: (¯`·._.·[ Ooola ]·._.·´¯) e + frases para seu MSN  Clique 
aqui! http://copa.br.msn.com/extra/frases/



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



Re: Issues deploying axis 2.0

2006-06-23 Thread Srikanth

well, thats what I am trying to use and I get this exception when I try to look up the resource in a browser.

Thanks.On 6/23/06, Anne Thomas Manes [EMAIL PROTECTED] wrote:
If you want to implement a RESTful service, I recommend you use Axis2 rather than Axis.On 6/23/06, 
Srikanth [EMAIL PROTECTED]
 wrote:

Hi,


 I am trying to create a RESTful webservice using Java and
hence looking at Axis to use that as a platform. I just downlaoded the
axis.war file and when I deployed it in my servlet container (tomcat
5.0.30) and tried to access the service (http://localhost:8080/axis2),
I encounter the following exception:

type Exception report
message 
description The server encountered an internal error () that prevented it from fulfilling this request.
exception 
javax.servlet.ServletException: org/apache/tools/ant/BuildException	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:244)	javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
root cause 
java.lang.NoClassDefFoundError: org/apache/tools/ant/BuildException	org.apache.jasper.JspCompilationContext.createCompiler(JspCompilationContext.java:197)	org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java
:508)	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295)	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)	org.apache.jasper.servlet.JspServlet.service
(JspServlet.java:236)	javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
note The full stack trace of the root cause is available in the Apache Tomcat/5.0.30 logs.

Could someone help me out as to what is wrong with my installation ???.

Thanks,
Srikanth K.








I am ready to create a new JIRA issue

2006-06-23 Thread Jim Bender

Unless someone can give a good explanation why I should not, I will
create a new JIRA issue about what I am seeing when trying to use a generated
stub in my test client:

Caught Throwable exception in runPointsCalculator:
org.apache.axiom.om.OMException:
java.lang.IllegalStateExceptionorg.apache.axiom.om.OMException:
java.lang.IllegalStateException

at 
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:206)
at 
org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocumentImpl.java:144)
at 
org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:322)
at 
testexamples.types.PointsCalculatorStub.toOM(PointsCalculatorStub.java:213)
at 
testexamples.types.PointsCalculatorStub.toEnvelope(PointsCalculatorStub.java:230)
at 
testexamples.types.PointsCalculatorStub.calculatePoints(PointsCalculatorStub.java:105)
at 
com.recursionsw.ve.tools.webservices.TestWebServicesEndToEndTestNG.runPointsCalculator(TestWebSe
rvicesEndToEndTestNG.java:299)
at 
com.recursionsw.ve.tools.webservices.TestWebServicesEndToEndTestNG.testGeneratorEndToEnd(TestWeb
ServicesEndToEndTestNG.java:155)

I am using today's daily build: 23/06/2006.
I used it to produce a new WSDL file (although the bug that is
documented by my other JIRA ticket for the duplicate complex type
definition means that I must hand edit the file to remove the
duplicate definition).
After doing that, I ran the WSDL2Java, updated the generated skeleton,
and then tested with Embedded Tomcat 5.5. While invoking the web
service operation on the stub, the exception is thrown by the
StAXOMBuilder.

What I am doing works without a problem in Axis2 0.93, for the same
Java interface.
The only difference is that Axis2 0.93 generates a valid WSDL file,
without a problem.

Regards,

Jim
wsdl:definitions xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/; xmlns:http=http://schemas.xmlsoap.org/wsdl/http/; xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/; xmlns:ns1=http://testexamples/xsd; xmlns:ns=http://PointsCalculator.ve.recursionsw.com/types; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; targetNamespace=http://PointsCalculator.ve.recursionsw.com/types;wsdl:typesxs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema; xmlns:ns=http://testexamples/xsd; targetNamespace=http://testexamples/xsd; elementFormDefault=unqualified attributeFormDefault=unqualified
xs:element type=ns:FoodDescription name=FoodDescription /
xs:complexType name=FoodDescription
xs:sequence
xs:element type=xs:int name=calories /
xs:element type=xs:int name=fatGrams /
xs:element type=xs:int name=fiberGrams /
xs:element type=xs:int name=points /
/xs:sequence
/xs:complexType
xs:element name=calculatePoints
xs:complexType
xs:sequence
xs:element type=ns:FoodDescription name=param0 /
/xs:sequence
/xs:complexType
/xs:element
xs:element name=calculatePointsResponse
xs:complexType
xs:sequence
xs:element type=xs:int name=return /
/xs:sequence
/xs:complexType
/xs:element
/xs:schema/wsdl:typeswsdl:message name=calculatePointsMessagewsdl:part element=ns1:calculatePoints name=part1 //wsdl:messagewsdl:message name=calculatePointsResponseMessagewsdl:part element=ns1:calculatePointsResponse name=part1 //wsdl:messagewsdl:portType name=PointsCalculatorPortTypewsdl:operation name=calculatePointswsdl:input message=ns:calculatePointsMessage /wsdl:output message=ns:calculatePointsResponseMessage //wsdl:operation/wsdl:portTypewsdl:binding type=ns:PointsCalculatorPortType name=PointsCalculatorSOAP11Bindingsoap:binding style=document transport=http://schemas.xmlsoap.org/soap/http; /wsdl:operation name=calculatePointssoap:operation style=document soapAction=urn:calculatePoints /wsdl:inputsoap:body namespace=http://PointsCalculator.ve.recursionsw.com/types; use=literal //wsdl:inputwsdl:outputsoap:body namespace=http://PointsCalculator.ve.recursionsw.com/types; use=literal //wsdl:output/wsdl:operation/wsdl:bindingwsdl:binding type=ns:PointsCalculatorPortType name=PointsCalculatorSOAP12Bindingsoap12:binding style=document transport=http://schemas.xmlsoap.org/soap/http; /wsdl:operation name=calculatePointssoap12:operation style=document soapAction=urn:calculatePoints /wsdl:inputsoap12:body namespace=http://PointsCalculator.ve.recursionsw.com/types; use=literal //wsdl:inputwsdl:outputsoap12:body namespace=http://PointsCalculator.ve.recursionsw.com/types; use=literal //wsdl:output/wsdl:operation/wsdl:bindingwsdl:service name=PointsCalculatorwsdl:port binding=ns:PointsCalculatorSOAP11Binding name=PointsCalculatorSOAP11portsoap:address location=c:/Java/projects2/axis2-std-1.0testbed/build/wsdlPointsCalculator //wsdl:portwsdl:port binding=ns:PointsCalculatorSOAP12Binding name=PointsCalculatorSOAP12portsoap12:address location=c:/Java/projects2/axis2-std-1.0testbed/build/wsdlPointsCalculator //wsdl:port/wsdl:service/wsdl:definitions

PointsCalculatorStub.java
Description: Binary 

what's wrong about anyURI ?

2006-06-23 Thread maxim
 Hello,
Why the anyURI type represented by  org.apache.axis.types.URI type is
required to be absolute so if I am using something like urisomeURI/uri
it gives me the MalformedURIException No scheme found in URI. That’s
wrong,
it should accept relative URI as well.
Thanks,
 Maxim Grigoriev.



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



Re: NullPointerException in MessageContext.setEnvelope(MessageContext.java:681)

2006-06-23 Thread Anne Thomas Manes
Dims just filed a JIRA about this issue a day or two ago. http://issues.apache.org/jira/browse/AXIS2-837
 Please add your use cases to the JIRA.Thanks,AnneOn 6/23/06, Ted Jones 
[EMAIL PROTECTED] wrote:





Martin,
Here is the WSDL:
definitions name=widgetServices targetNamespace=http://com.widgets/test xmlns=http://schemas.xmlsoap.org/wsdl/ xmlns:xsd=http://www.w3.org/2001/XMLSchema xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/ xmlns:tns=http://com.widgets/test xmlns:schema1=http://www.widgets.com/bqt_Output types xsd:schema targetNamespace=http://com.widgets/test xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/ xsd:import namespace=http://www.widgets.com/bqt_Output schemaLocation=http://chicago:8080/test/servlet/ArtifactDocumentService/test/bqt_Output.xsd / /xsd:schema
 /types message name=bqt_SMALLA_getSMALLA_Input documentationInput message for operation bqt_SMALLA/getSMALLA./documentation /message message name=bqt_SMALLA_getSMALLA_SMALLA_OutputMsg
 documentationOutput message for operation bqt_SMALLA/getSMALLA./documentation part name=bqt_SMALLA_getSMALLA_SMALLA_OutputMsg element=schema1:SMALLA_Output /
 /message portType name=bqt_SMALLA operation name=getSMALLA input name=Input message=tns:bqt_SMALLA_getSMALLA_Input /
 output name=SMALLA_OutputMsg message=tns:bqt_SMALLA_getSMALLA_SMALLA_OutputMsg / /operation /portType binding name=bqt_SMALLA type=tns:bqt_SMALLA
 soap:binding style=document transport=http://schemas.xmlsoap.org/soap/http / operation name=getSMALLA soap:operation style=document soapAction=bqt_WS.bqt_SMALLA.getSMALLA /
 input name=Input soap:body use=literal / /input output name=SMALLA_OutputMsg soap:body use=literal /
 /output /operation /binding service name=widgetsDataServices port name=bqt_SMALLA binding=tns:bqt_SMALLA
 soap:address location=http://chicago:8080/test/services/service / /port /service/definitions

Here is the WSDD:

deployment name=test xmlns=http://xml.apache.org/axis/wsdd/  xmlns:java=http://xml.apache.org/axis/wsdd/providers/java xmlns:xsi=http://www.w3.org/2000/10/XMLSchema-instance !-- note that either style=message OR provider=java:MSG both work --
 service name=service provider=java:MSG  parameter name=className value=com.widgets.soap.lds.service.DataServiceWebService / parameter name=allowedMethods value=executeDataservice /
 /service/deployment 

I am executing a web service with no input 
parametersso the SOAP body is empty like so:

soapenv:Envelope 
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ 
soapenv:Body//soapenv:Envelope

I am getting an NPE returned before I even 
hit my Web Service, so I am assuming the exception is happening in Axis 
somewhere (I'm not seeing a stack trace). Here is the 
response:

?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:Body 
soapenv:Fault 
faultcodesoapenv:Server.userException/faultcode 
faultstringjava.lang.NullPointerException/faultstring 
detail/ 
/soapenv:Fault/soapenv:Body/soapenv:Envelope

I get this using Coral and Systinet as my 
clients. When I generate an Axis client, I do not get an NPE but I get a node 
added to my body with the operation name in it (which I don't want to 
seeas my logic depends on the body to be empty when no inputs are 
provided).
Any help would be greatly appreciated!Thanks,Ted Jones
-Original Message-From: Martin Gainty [mailto:[EMAIL PROTECTED]
]Sent: Friday, June 23, 2006 2:20 PMTo: axis-user@ws.apache.org
Subject: Re: NullPointerException in MessageContext.setEnvelope(MessageContext.java:681)Good Afternoon Ted-Could we see the WSDL?Thanks,MartinThis email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you.
- Original Message -From: Ted Jones [EMAIL PROTECTED]To: 
axis-user@ws.apache.orgSent: Friday, June 23, 2006 2:30 PMSubject: RE: NullPointerException in
MessageContext.setEnvelope(MessageContext.java:681)IP VP,I encountered the same thing (or something very similar) with Axis 1.3. I was hoping an upgrade to Axis2 would fix my problem. Have you had any luck resolving?
Thanks,Ted Jones-Original Message-From: ip vp [mailto:[EMAIL PROTECTED]]Sent: Thursday, June 22, 2006 4:28 PM
To: axis-user@ws.apache.orgSubject: NullPointerException inMessageContext.setEnvelope(MessageContext.java

:681)Importance: HighHi all,I am trying to call a comercial partner webservice thats return a string and do not need input parameters.Based on User guide ( Client for echoVoid Operation)

I am doing the followig:- generating java code based on wsdl, using ecplise plugin.- did a very simple client whit the following code:GeneratedStubClass 

Axis 2.0 REST Web services samples

2006-06-23 Thread Srikanth


Hi,

 I am trying to develop RESTful services using Axis2.0 and
just managed to setup Axis2.0, services, modules etc. I would
appreciate if someone could send me a small toy application or a simple
REST style server/client so that I could understand the nuances of Axis
and REST. I checked out the REST document at ws.apache.org but would
like to have something ore explanatory than that.

Thanks,
Srikanth K.




[Axis2] WSDL2Java fails to detect nonexistent element

2006-06-23 Thread Derek
Hi, folks.

I recently noticed that the Axis2 WSDL2Java program, when generating
XmlBeans, seems to accept WSDL which contains references to nonexistent
elements. For instance:

   types
  xs:schema
 xs:import namespace=http://www.dummy-im-address;
schemaLocation=im.xsd/
  /xs:schema
   /types

   message name=IEEE1512Event
  part name=iMWrapper element=im:thisDoesNotExist/
   /message

The element thisDoesNotExist is not defined anywhere in the im.xsd schema
file, yet WSDL2Java reports no warnings or errors when asked to generate
code for a service using this WSDL file. The server skeleton that is
generated takes a parameter of type XmlObject where the thisDoesNotExist
element would be passed. Considering that this can happen due to a simple
typo in an element name, this seems like a very difficult problem to track
down.

It seems to me that an error, or at least a warning, should be reported for
cases like this.

Should I file this as a JIRA bug?

Derek




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



RE: [Axis2] Why do I get service skeletons taking OMElement, and uncompilable code?

2006-06-23 Thread Derek
OK. I created the following:

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

Thanks.

Derek

 -Original Message-
 From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, June 21, 2006 7:15 PM
 To: axis-user@ws.apache.org; [EMAIL PROTECTED]
 Subject: Re: [Axis2] Why do I get service skeletons taking 
 OMElement, and uncompilable code?
 
 
 Yes, Please log a JIRA bug.
 
 thanks,
 dims
 
 On 6/21/06, Derek [EMAIL PROTECTED] wrote:
  Thanks for the suggestion, Robert.
 
  I tried downloading the June 21 nightly build of Axis, and that 
  version of WSDL2Java did produce the same skeleton files 
 for me that 
  it did for you (the ones taking an XmlObject parameter, rather than 
  OMObject as I was getting with the 1.0 release).
 
  I then tried to test your hypothesis about xs:any. I 
 modified my XML 
  schema to comment out the two xs:any tags. I then ran WSDL2Java and 
  regenerated the files. I got the same generated skeleton files as 
  before.
 
  After pounding my head against the keyboard vigorously for 
 a while, I 
  decided to start drastically simplifying the WSDL to try to 
 find out 
  what was going wrong. Eventually, I found a change that made the 
  problem go away. I still don't understand why, though.
 
  One of my xs:schema declarations in my WSDL has the same 
 namespace as 
  the targetNamespace declared at the top of the WSDL file itself. It 
  declares three elements: full-event-update, full-event-updates, 
  and return, which are referenced in the FEvent, FRecap, and 
  FResponse messages. When I change the WSDL so this schema 
 is declared 
  to instead have a different namespace from the WSDL 
 targetNamespace, 
  then the generated signature I get for my method is:
 
  /**
   *  FEUServiceSkeletonInterface java skeleton interface for the 
  axisService
   */
  public interface FEUServiceSkeletonInterface {
 
 
  /**
   * Auto generated method signature
 
* @param param0
 
   */
  public  
 com.crc_corp.www.wsdl._2004_10_01.feu2.ReturnDocument
  acceptFEUEvent
 
  
 (com.crc_corp.www.wsdl._2004_10_01.feu2.FullEventUpdateDocumen
 t param0 
  )
 
 ;
 
  }
 
  So it seems to be the case that if a message references an 
 XML element 
  declaration which is in the same namespace as the 
 targetNamespace of 
  the WSDL file itself, then the XMLBeans WSDL2Java code generator 
  decides for mysterious reasons of its own to pass those messages as 
  XmlObject instances instead of the types that should be 
 generated for 
  the messages. Why this should be so, I have no idea.
 
  There seems to be no documentation or warnigns of any such behavior 
  that I can find in the Axis documentation, so I assume this 
 is a bug. 
  Should I file this in Jira?
 
  Derek
 
   -Original Message-
   From: robert lazarski [mailto:[EMAIL PROTECTED]
   Sent: Tuesday, June 20, 2006 5:38 PM
   To: axis-user@ws.apache.org
   Subject: Re: [Axis2] Why do I get service skeletons taking 
   OMElement, and uncompilable code?
  
  
   Oops, a little late here and I misread the method 
 signature. Getting 
   XmlObject instead of OMElement probably isn't what you 
 were hoping 
   for, so perhaps as Anne implied xs:any is the culprit.
  
   Do keep in mind the bug fixes in the xmlbeans code since the 1.0 
   release, however.
  
   Good luck,
   Robert
   http://www.braziloutsource.com/
  
   On 6/20/06, robert lazarski [EMAIL PROTECTED] wrote:
To add to what Anne said, you're using a version of axis
   from May 05,
2006 . While that may be the official 1.0 release, there
   were several
important bugs fixed for xmlbeans after that.
   
The good news is that this is the code that I was able to
   produce from
the latest nightly:
   
/**
 * FServiceSkeleton.java
 *
 * This file was auto-generated from WSDL
 * by the Apache Axis2 version: SNAPSHOT Jun 20, 2006
   (11:24:21 GMT+00:00)
 */
package org.simple.endpoint;
/**
 *  FServiceSkeleton java skeleton for the axisService
 */
public class FServiceSkeleton{
   
   
/**
 * Auto generated method signature
   
  * @param param0
   
 */
public  org.apache.xmlbeans.XmlObject acceptFEvent
  (org.apache.xmlbeans.XmlObject param0 )
   
   throws
   org.simple.endpoint.FServiceSkeleton.GeneralFaultException{
//Todo fill this with the necessary 
 business logic
throw new
   java.lang.UnsupportedOperationException();
}
   
   
/**
 * Auto generated method signature
   
  * @param param4
   
 */
public  org.apache.xmlbeans.XmlObject acceptFRecap
  (org.apache.xmlbeans.XmlObject param4 )
   
   throws
   

Re: I am ready to create a new JIRA issue

2006-06-23 Thread Davanum Srinivas

Please create a JIRA issue. Most of the times, it does not hurt to
just create it :) and then ask here (rather than the other way around
:)

-- dims

On 6/23/06, Jim Bender [EMAIL PROTECTED] wrote:

Unless someone can give a good explanation why I should not, I will
create a new JIRA issue about what I am seeing when trying to use a generated
stub in my test client:

Caught Throwable exception in runPointsCalculator:
org.apache.axiom.om.OMException:
java.lang.IllegalStateExceptionorg.apache.axiom.om.OMException:
java.lang.IllegalStateException

at 
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:206)
at 
org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocumentImpl.java:144)
at 
org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:322)
at 
testexamples.types.PointsCalculatorStub.toOM(PointsCalculatorStub.java:213)
at 
testexamples.types.PointsCalculatorStub.toEnvelope(PointsCalculatorStub.java:230)
at 
testexamples.types.PointsCalculatorStub.calculatePoints(PointsCalculatorStub.java:105)
at 
com.recursionsw.ve.tools.webservices.TestWebServicesEndToEndTestNG.runPointsCalculator(TestWebSe
rvicesEndToEndTestNG.java:299)
at 
com.recursionsw.ve.tools.webservices.TestWebServicesEndToEndTestNG.testGeneratorEndToEnd(TestWeb
ServicesEndToEndTestNG.java:155)

I am using today's daily build: 23/06/2006.
I used it to produce a new WSDL file (although the bug that is
documented by my other JIRA ticket for the duplicate complex type
definition means that I must hand edit the file to remove the
duplicate definition).
After doing that, I ran the WSDL2Java, updated the generated skeleton,
and then tested with Embedded Tomcat 5.5. While invoking the web
service operation on the stub, the exception is thrown by the
StAXOMBuilder.

What I am doing works without a problem in Axis2 0.93, for the same
Java interface.
The only difference is that Axis2 0.93 generates a valid WSDL file,
without a problem.

Regards,

Jim


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






--
Davanum Srinivas : http://people.apache.org/~dims/

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