RE: multiple configurations (multiple axis2.xml with different names)?

2009-04-15 Thread Raghu Udupa
Hi,

 

I am using axis2c_1.5.0 release.

 

When I specify libDir and moduleDir in axis2.xml, axis2c client on Linux
still, axis2c client run time still does not use paths specified in
axis2.xml file and exits with an error.  I am attaching my axis2.xml
file.  I am specifying 

parameter name=libDir/usr/local/axis2c/lib/parameter

parameter name=moduleDir/usr/local/axis2c/modules/parameter

as children of axisconfig root element.

 

Here is the axis2client log

[Wed Apr 15 10:49:36 2009] [error] class_loader.c(162) Loading shared
library /usr/ops/5.0/config/wsclient/http/lib/libaxis2_http_sender.so
Failed. DLERROR IS
/usr/ops/5.0/config/wsclient/http/lib/libaxis2_http_sender.so: cannot
open shared object file: No such file or directory

[Wed Apr 15 10:49:36 2009] [error] conf_builder.c(898) Transport sender
is NULL for transport http, unable to continue

[Wed Apr 15 10:49:36 2009] [error] conf_builder.c(261) Processing
transport senders failed, unable to continue

[Wed Apr 15 10:49:36 2009] [error] dep_engine.c(939) Populating Axis2
Configuration failed

[Wed Apr 15 10:49:36 2009] [error] conf_init.c(195) Loading deployment
engine failed for client repository /usr/ops/5.0/config/wsclient/http

[Wed Apr 15 10:49:36 2009] [error] class_loader.c(162) Loading shared
library /usr/ops/5.0/config/wsclient/http/lib/libaxis2_http_sender.so
Failed. DLERROR IS
/usr/ops/5.0/config/wsclient/http/lib/libaxis2_http_sender.so: cannot
open shared object file: No such file or directory

[Wed Apr 15 10:49:36 2009] [error] conf_builder.c(898) Transport sender
is NULL for transport http, unable to continue

[Wed Apr 15 10:49:36 2009] [error] conf_builder.c(261) Processing
transport senders failed, unable to continue

[Wed Apr 15 10:49:36 2009] [error] dep_engine.c(939) Populating Axis2
Configuration failed

[Wed Apr 15 10:49:36 2009] [error] conf_init.c(195) Loading deployment
engine failed for client repository /usr/ops/5.0/config/wsclient/http

[Wed Apr 15 10:49:42 2009] [error] class_loader.c(162) Loading shared
library /usr/ops/5.0/config/wsclient/http/lib/libaxis2_http_sender.so
Failed. DLERROR IS
/usr/ops/5.0/config/wsclient/http/lib/libaxis2_http_sender.so: cannot
open shared object file: No such file or directory

[Wed Apr 15 10:49:42 2009] [error] conf_builder.c(898) Transport sender
is NULL for transport http, unable to continue

[Wed Apr 15 10:49:42 2009] [error] conf_builder.c(261) Processing
transport senders failed, unable to continue

 

 

I need to have lib and modules located in AXIS2C_HOME directory. I am
setting up soft links to actual lib and module dir. Once lib and modules
links are set up in axis2c_home dir every thing works fine.

 

Thanks,

Raghu



From: Raymond Zhou [mailto:raywang...@yahoo.com] 
Sent: Tuesday, March 10, 2009 1:11 PM
To: Apache AXIS C User List
Subject: Re: multiple configurations (multiple axis2.xml with different
names)?

 

OK, I just tried, it seems that I can only use the name axis2.xml. I can
specify different folds and axis2/c will look for axis2.xml in that
fold. I can also specify a file path ended with axis2.xml. All works
fine. But axis2/c will fail to create a wb service client if I specify a
full file path with a name different from axis2.xml.

 

I think this needs to be fixed. In my environment, my web service client
needs to connect to several web service providers with different
configurations, it would be convenient if I can create several config
files with different names.

 

Thanks!
Frank

--- On Mon, 3/2/09, Samisa Abeysinghe sam...@wso2.com wrote:


From: Samisa Abeysinghe sam...@wso2.com
Subject: Re: multiple configurations (multiple axis2.xml with
different names)?
To: Apache AXIS C User List axis-c-user@ws.apache.org
Date: Monday, March 2, 2009, 1:35 AM

Raymond Zhou wrote:
 OK, Thanks Dinesh.
  So it seems that I can create multiple configuration files
all named axis2.xml but put in different folds, and in each axis2.xml,
specify the library and module locations pointing to the single axis2/c
installation.
  It would be nice if I can create multiple configuration files
with different names, so I can put them in a same fold, and then set the
axis2_home programmatically.
 

That should be possible, but we might have to pach the current
implementation of config builder.

Thanks,
Samisa...

  Thanks!
 Frank
  
 
 --- On *Fri, 2/27/09, Dinesh Premalal /xydin...@gmail.com
http://us.mc464.mail.yahoo.com/mc/compose?to=xydin...@gmail.com /*
wrote:
 
 From: Dinesh Premalal xydin...@gmail.com
http://us.mc464.mail.yahoo.com/mc/compose?to=xydin...@gmail.com 
 Subject: Re: multiple configurations (multiple axis2..xml
with
 different names)?
 To: axis-c-user@ws.apache.org

Spurious client time out errors -- duplicate transmission

2009-02-06 Thread Raghu Udupa
Hi,

 

I am using Axis2C/1.5.0 on a Linux server as a client communicating to a
Web service. Each message is delivered to a possibly different web
service through a separate process. The process communicates either via
http or https depending on remote web service configuration

 

On couple of occasions, I got time out error at the client, while
message was successfully received at the host. I have set the session
time out to 3 minutes. When I enable the trace log, this problem does
not happen. Here is a snapshot of axis2c log.

 

1)

[Thu Feb  5 17:05:03 2009] [error] http_client.c(460) Response timed out

[Thu Feb  5 17:05:03 2009] [error] http_sender.c(1342) status_code  0

[Thu Feb  5 17:05:03 2009] [error] engine.c(179) Transport sender invoke
failed

2)

[Thu Feb  5 17:05:03 2009] [error] http_client.c(460) Response timed out

[Thu Feb  5 17:05:03 2009] [error] http_sender.c(1342) status_code  0

[Thu Feb  5 17:05:03 2009] [error] engine.c(179) Transport sender invoke
failed

3)

[Thu Feb  5 17:15:41 2009] [error] http_client.c(460) Response timed out

[Thu Feb  5 17:15:41 2009] [error] http_sender.c(1342) status_code  0

[Thu Feb  5 17:15:41 2009] [error] engine.c(179) Transport sender invoke
failed

4)

[Thu Feb  5 17:19:47 2009] [error] http_client.c(460) Response timed out

[Thu Feb  5 17:19:47 2009] [error] http_sender.c(1342) status_code  0

[Thu Feb  5 17:19:47 2009] [error] engine.c(179) Transport sender invoke
failed

 

For each of the above 4 attempts, message was delivered at the web
service. In addition, the client received time-out as soon as the
request was sent even though session timeout is set to 180 seconds.

 

Here is the time when message was sent.

1)

17:05:02 16 [9406] SendMessage: Call web service. Signature reqd 0

17:05:03 16 [9406] axis2_stub_op_ReceiveEasyLinkFaxService_ReceiveFax:
return code is null

 

2)

17:05:03 16 [9407] SendMessage: Call web service. Signature reqd 0

17:05:03 16 [9407] axis2_stub_op_ReceiveEasyLinkFaxService_ReceiveFax:
return code is null

3)

17:15:41 16 [9672] SendMessage: Call web service. Signature reqd 0

17:15:41 16 [9672] axis2_stub_op_ReceiveEasyLinkFaxService_ReceiveFax:
return code is null

4)

17:19:47 16 [9726] SendMessage: Call web service. Signature reqd 0

17:19:47 16 [9726] axis2_stub_op_ReceiveEasyLinkFaxService_ReceiveFax:
return code is null

 

Thanks,

Raghu

 



RE: Spurious client time out errors -- duplicate transmission

2009-02-06 Thread Raghu Udupa
Hi,

 

This problem happens only when I use HTTP protocol.  With HTTPS every
thing works fine. One message is sent and one is received.

 

I am using Axis2C/1.5.0 on a Linux server as a client communicating to a
Web service. Each message is delivered to a possibly different web
service through a separate process. The process communicates either via
http or https depending on remote web service configuration

 

On couple of occasions, I got time out error at the client, while
message was successfully received at the host. I have set the session
time out to 3 minutes. When I enable the trace log, this problem does
not happen. Here is a snapshot of axis2c log.

 

1)

[Thu Feb  5 17:05:03 2009] [error] http_client.c(460) Response timed out

[Thu Feb  5 17:05:03 2009] [error] http_sender.c(1342) status_code  0

[Thu Feb  5 17:05:03 2009] [error] engine.c(179) Transport sender invoke
failed

2)

[Thu Feb  5 17:05:03 2009] [error] http_client.c(460) Response timed out

[Thu Feb  5 17:05:03 2009] [error] http_sender.c(1342) status_code  0

[Thu Feb  5 17:05:03 2009] [error] engine.c(179) Transport sender invoke
failed

3)

[Thu Feb  5 17:15:41 2009] [error] http_client.c(460) Response timed out

[Thu Feb  5 17:15:41 2009] [error] http_sender.c(1342) status_code  0

[Thu Feb  5 17:15:41 2009] [error] engine.c(179) Transport sender invoke
failed

4)

[Thu Feb  5 17:19:47 2009] [error] http_client.c(460) Response timed out

[Thu Feb  5 17:19:47 2009] [error] http_sender.c(1342) status_code  0

[Thu Feb  5 17:19:47 2009] [error] engine.c(179) Transport sender invoke
failed

 

For each of the above 4 attempts, message was delivered at the web
service. In addition, the client received time-out as soon as the
request was sent even though session timeout is set to 180 seconds.

 

Here is the time when message was sent.

1)

17:05:02 16 [9406] SendMessage: Call web service. Signature reqd 0

17:05:03 16 [9406] axis2_stub_op_ReceiveEasyLinkFaxService_ReceiveFax:
return code is null

 

2)

17:05:03 16 [9407] SendMessage: Call web service. Signature reqd 0

17:05:03 16 [9407] axis2_stub_op_ReceiveEasyLinkFaxService_ReceiveFax:
return code is null

3)

17:15:41 16 [9672] SendMessage: Call web service. Signature reqd 0

17:15:41 16 [9672] axis2_stub_op_ReceiveEasyLinkFaxService_ReceiveFax:
return code is null

4)

17:19:47 16 [9726] SendMessage: Call web service. Signature reqd 0

17:19:47 16 [9726] axis2_stub_op_ReceiveEasyLinkFaxService_ReceiveFax:
return code is null

 

Thanks,

Raghu

 



Using tcpmon with axis2_http_server

2008-10-15 Thread Raghu Udupa
Hi,

 

I am using axis2_http_server provided with axis2c 1.5.0 release for unit
testing. The client and service applications are running properly. But,
I can not see the messages in tcpmon. Is there any thing specific I need
to specify in axis2.xml to get tcpmon to capture the messages. Client
and the server applications run on Linux server.

 

Thanks,

Raghu



RE: rampart_handler_util.c -- parameter not set

2008-10-04 Thread Raghu Udupa
Thanks Manjula.
 
Does the policy.xml has to reside in AXIS2_HOME? Can I specify full pathname  
(to point to the policy file located in some other directory) through neeti 
APIs?
 
Regards,
Raghu



From: Manjula Peiris [mailto:[EMAIL PROTECTED]
Sent: Fri 10/3/2008 11:11 PM
To: Apache AXIS C User List
Subject: RE: rampart_handler_util.c -- parameter not set




On Fri, 2008-10-03 at 22:43 -0400, Raghu Udupa wrote:
 Thanks, Shankar, for the explanation. I was trying to send a signed request 
 and receive a clear (un-signed) response.
 
 Our web services client need to connect to different web services some of 
 which may require signed messages. So, can we do either of the following:

 1.   
   Does the policy.xml has to be named as policy.xml on the client side? 
 If I can specify policy_cust1.xml for customer 1 and policy_cust2.xml for 
 customer 2, then, same client will be able to handle multiple customers. 
 Basically, my question is there a restriction like axis2c config file name 
 being axis2.xml

No it does not need to be policy.xml. If you carefully look at the
rampart sample client you will understand. What you need to do is
calling the neethi_util_create_policy_from_file() function with the
policy file name.

 2.   
   Can we specify receiver certificate, for each customer programmatically 
 through an API

Current API does not allow this. Even though there are some properties
like username can be passed through programmatically.


 Regards,

 Raghu


 

 From: Uthaiyashankar [mailto:[EMAIL PROTECTED]
 Sent: Fri 10/3/2008 10:07 PM
 To: Apache AXIS C User List
 Subject: Re: rampart_handler_util.c -- parameter not set



 Hi Raghu,

 I think your configurations are wrong. First of all, I have to be clear
 that whether message sent from server to client is also signed? It has
 to be signed, otherwise rampart will not work. From client side, still
 we don't have support to have different security policy for outgoing
 message and incoming message. Hence my further explanations will assume
 even the message from server to client is signed.

 To sign from server to client, you have to give rampc:Certificate and
 rampc:PrivateKey in server side configuration. Also, you have to give
 rampc:ReceiverCertificate in client's configuration.

 Sample4 shipped with Rampart[1] is actually the usecase you are trying
 to achieve. You can have a look at that.

 Regards,
 Shankar

 [1]
 https://svn.apache.org/repos/asf/webservices/rampart/trunk/c/samples/secpolicy/scenario4

 Raghu Udupa wrote:
  Thanks Shankar.
 
  I am a bit confused about specifying security phase in axis2.xml for
  client as well as for server.
 
  We need to sign the documents that are sent to the client which need to
  be verified at the server.
 
  Could you tell me whether my settings of axis2.xml and policy.xml on the
  client side and axis2.xml and service.xml on the server side are correct
  for a correct implementation of signature verification
 
  CLIENT SIDE
 
  axis2.xml
  =
 
  phaseOrder type=outflow
  !-- User defined phases could be added here --
  !--phase name=userphase1/--
  !--system predefined phase--
  phase name=MessageOut/
  phase name=Security/
  !--phase name=Security/--
  /phaseOrder
 
  policy.xml
  ==
 
  rampc:RampartConfig
  xmlns:rampc=http://ws.apache.org/rampart/c/policy;
  rampc:Certificate/usr/certdir/openssl_crt.pem/rampc:Certificate
  rampc:PrivateKey/usr/certdir/sign.key/rampc:PrivateKey
  /rampc:RampartConfig
 
 
  SERVER SIDE
 
  axis2.xml
  =
 
  phaseOrder type=inflow
!-- System pre defined phases   --
phase name=Transport/
phase name=PreDispatch/
phase name=Dispatch/
phase name=PostDispatch/
phase name=Security/
   /phaseOrder
 
  service.xml
  ===
 
  service name=ReceiveEasyLinkFaxService
  parameter name=ServiceClassReceiveEasyLinkFaxService/parameter
  descriptionReceiveEasyLinkFaxService Service/description
  module ref=rampart/
  operation name=ReceiveFax
  
  
  rampc:RampartConfig
  xmlns:rampc=http://ws.apache.org/rampart/c/policy;
  rampc:ReceiverCertificate/usr/certdir/openssl_crt.pem/rampc:ReceiverC
  ertificate
  /rampc:RampartConfig
 
  Thanks,
  Raghu
 
  -Original Message-
  From: Uthaiyashankar [mailto:[EMAIL PROTECTED]
  Sent: Thursday, October 02, 2008 1:13 PM
  To: Apache AXIS C User List
  Subject: Re: rampart_handler_util.c -- parameter not set
 
  Raghu Udupa wrote:
  
  Thanks Samisa.
 
  The first reported error is parameter 0 not being set in
  rampart_handler_util.c. I wanted to know which configuration parameter
  method rampart_get_rampart_configuration in rampart_handler_util.c is
  looking for.
  

 
  That error message is misleading. It is actually not an error. :). We
  have to remove it. So, you can safely ignore it.
 
  Regards,
  Shankar.
 
  
  Regards

RE: rampart_handler_util.c -- parameter not set

2008-10-03 Thread Raghu Udupa
Thanks Shankar.

I am a bit confused about specifying security phase in axis2.xml for
client as well as for server. 

We need to sign the documents that are sent to the client which need to
be verified at the server.

Could you tell me whether my settings of axis2.xml and policy.xml on the
client side and axis2.xml and service.xml on the server side are correct
for a correct implementation of signature verification

CLIENT SIDE

axis2.xml
=

phaseOrder type=outflow
!-- User defined phases could be added here --
!--phase name=userphase1/--
!--system predefined phase--
phase name=MessageOut/
phase name=Security/
!--phase name=Security/--
/phaseOrder

policy.xml
==

rampc:RampartConfig
xmlns:rampc=http://ws.apache.org/rampart/c/policy;
rampc:Certificate/usr/certdir/openssl_crt.pem/rampc:Certificate
rampc:PrivateKey/usr/certdir/sign.key/rampc:PrivateKey
/rampc:RampartConfig


SERVER SIDE

axis2.xml
=

phaseOrder type=inflow
  !-- System pre defined phases   --
  phase name=Transport/
  phase name=PreDispatch/
  phase name=Dispatch/
  phase name=PostDispatch/
  phase name=Security/
 /phaseOrder

service.xml
===

service name=ReceiveEasyLinkFaxService
parameter name=ServiceClassReceiveEasyLinkFaxService/parameter
descriptionReceiveEasyLinkFaxService Service/description
module ref=rampart/
operation name=ReceiveFax


rampc:RampartConfig
xmlns:rampc=http://ws.apache.org/rampart/c/policy;
rampc:ReceiverCertificate/usr/certdir/openssl_crt.pem/rampc:ReceiverC
ertificate 
/rampc:RampartConfig

Thanks,
Raghu

-Original Message-
From: Uthaiyashankar [mailto:[EMAIL PROTECTED] 
Sent: Thursday, October 02, 2008 1:13 PM
To: Apache AXIS C User List
Subject: Re: rampart_handler_util.c -- parameter not set

Raghu Udupa wrote:
 Thanks Samisa.

 The first reported error is parameter 0 not being set in
 rampart_handler_util.c. I wanted to know which configuration parameter
 method rampart_get_rampart_configuration in rampart_handler_util.c is
 looking for.
   

That error message is misleading. It is actually not an error. :). We 
have to remove it. So, you can safely ignore it.

Regards,
Shankar.

 Regards,
 Raghu

 -Original Message-
 From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, October 01, 2008 9:32 PM
 To: Apache AXIS C User List
 Subject: Re: rampart_handler_util.c -- parameter not set

   
2. Also, the webservices client is getting following error while
   attempting to engage rampart module.

 [Wed Oct  1 11:36:33 2008] [error] rampart_handler_util.c(241) 
 [rampart][rampart_handler_utils] 0 parameter is not set.

 [Wed Oct  1 11:36:33 2008] [warning] msg_ctx.c(1381) 
 RampartClientConfiguration not set in message context

 [Wed Oct  1 11:36:33 2008] [error] error.c(94) OXS ERROR [x509.c:284 
 in openssl_x509_get_subject_key_identifier] oxs defualt error , The 
 extenension index of NID_subject_key_identifier is not valid

 [Wed Oct  1 11:36:33 2008] [error] http_sender.c(1374) Error occurred

 in transport

 [Wed Oct  1 11:36:33 2008] [error] rampart_engine.c(122) 
 [rampart][rampart_engine] Cannot get saved rampart_context

 [Wed Oct  1 11:36:33 2008] [error] rampart_in_handler.c(114) 
 [rampart][rampart_in_handler] rampart_context creation failed.

 [Wed Oct  1 11:36:33 2008] [error] phase.c(216) Handler 
 RampartInHandler invoke failed within phase PreDispatch

 [Wed Oct  1 11:36:33 2008] [error] engine.c(696) Invoking phase 
 PreDispatch failed

 [Wed Oct  1 11:36:33 2008] [error] soap11_builder_helper.c(368) 
 Unidentified character in SOAP 1.1 builder helper processing

 
 As the error says, there is something wrong in your key.

 Samisa...
   
3. I am also including the server log. I am using a self signed
   certificate generated using openssl to sign the message. Digest
   verification is succeeding. But signature verification is
 
 failing.
   
  

 Thanks,
 Raghu
 
 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]



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



RE: certificate file for communicating via https

2008-10-03 Thread Raghu Udupa
Thanks Manjula. I need a couple more clarifications,

1) If I store multiple certificates in a PFX file, how would
axis2c/rampart know which certificate to use?

1.1) Does it go by the domain name in the URI? If so, what is the
criteria?  That is, if URI is
www.webservices.com/axis2/services/myservice, then, does it use the
domain www.webservices.com for retrieving the certificate.

1.2) Do I need to specify a password for each certificate?

2) You mention providing .pfx file and password to Rampart/C. My
thinking was to specify PFX file in axis2.xml under SERVER_CERT. There
is no tag in axis2.xml for specifying password. Where do I specify the
password? Can I do it programmatically or through module.xml? 

3) This is just a reconfirmation. In the client guide, it is mentioned
that I can specify a PEM file. As long as PEM file is one certificate
per PEM file, can I still use a PEM file.

Thanks,
Raghu

-Original Message-
From: Manjula Peiris [mailto:[EMAIL PROTECTED] 
Sent: Friday, September 19, 2008 5:35 AM
To: Apache AXIS C User List
Subject: Re: certificate file for communicating via https


On Thu, 2008-09-18 at 17:01 -0400, Raghu Udupa wrote:
 If a web services client wants to communicate with different servers,
 can certificates for different servers be specified in one PEM file.
 For curl, you can specify a single certificate file which can contain
 multiple certificates. I would like to know whether axis2c provides
 this feature.

No you can't specify it in one PEM file. Rampart/C the Axis2/C security
project does not support that. But you can store all the certificates in
a pfx key store and provide Rampart/C with the .pfx file with the
password to retrieve the certificate from the key store. 


 
  
 
 Thanks,
 
 Raghu
 
 


-
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: rampart_handler_util.c -- parameter not set

2008-10-03 Thread Raghu Udupa
Thanks, Shankar, for the explanation. I was trying to send a signed request and 
receive a clear (un-signed) response.
 
Our web services client need to connect to different web services some of which 
may require signed messages. So, can we do either of the following:

1.  
Does the policy.xml has to be named as policy.xml on the client side? 
If I can specify policy_cust1.xml for customer 1 and policy_cust2.xml for 
customer 2, then, same client will be able to handle multiple customers. 
Basically, my question is there a restriction like axis2c config file name 
being axis2.xml
2.  
Can we specify receiver certificate, for each customer programmatically 
through an API

Regards,

Raghu




From: Uthaiyashankar [mailto:[EMAIL PROTECTED]
Sent: Fri 10/3/2008 10:07 PM
To: Apache AXIS C User List
Subject: Re: rampart_handler_util.c -- parameter not set



Hi Raghu,

I think your configurations are wrong. First of all, I have to be clear
that whether message sent from server to client is also signed? It has
to be signed, otherwise rampart will not work. From client side, still
we don't have support to have different security policy for outgoing
message and incoming message. Hence my further explanations will assume
even the message from server to client is signed.

To sign from server to client, you have to give rampc:Certificate and
rampc:PrivateKey in server side configuration. Also, you have to give
rampc:ReceiverCertificate in client's configuration.

Sample4 shipped with Rampart[1] is actually the usecase you are trying
to achieve. You can have a look at that.

Regards,
Shankar

[1]
https://svn.apache.org/repos/asf/webservices/rampart/trunk/c/samples/secpolicy/scenario4

Raghu Udupa wrote:
 Thanks Shankar.

 I am a bit confused about specifying security phase in axis2.xml for
 client as well as for server.

 We need to sign the documents that are sent to the client which need to
 be verified at the server.

 Could you tell me whether my settings of axis2.xml and policy.xml on the
 client side and axis2.xml and service.xml on the server side are correct
 for a correct implementation of signature verification

 CLIENT SIDE

 axis2.xml
 =

 phaseOrder type=outflow
 !-- User defined phases could be added here --
 !--phase name=userphase1/--
 !--system predefined phase--
 phase name=MessageOut/
 phase name=Security/
 !--phase name=Security/--
 /phaseOrder

 policy.xml
 ==

 rampc:RampartConfig
 xmlns:rampc=http://ws.apache.org/rampart/c/policy;
 rampc:Certificate/usr/certdir/openssl_crt.pem/rampc:Certificate
 rampc:PrivateKey/usr/certdir/sign.key/rampc:PrivateKey
 /rampc:RampartConfig


 SERVER SIDE

 axis2.xml
 =

 phaseOrder type=inflow
   !-- System pre defined phases   --
   phase name=Transport/
   phase name=PreDispatch/
   phase name=Dispatch/
   phase name=PostDispatch/
   phase name=Security/
  /phaseOrder

 service.xml
 ===

 service name=ReceiveEasyLinkFaxService
 parameter name=ServiceClassReceiveEasyLinkFaxService/parameter
 descriptionReceiveEasyLinkFaxService Service/description
 module ref=rampart/
 operation name=ReceiveFax
 
 
 rampc:RampartConfig
 xmlns:rampc=http://ws.apache.org/rampart/c/policy;
 rampc:ReceiverCertificate/usr/certdir/openssl_crt.pem/rampc:ReceiverC
 ertificate
 /rampc:RampartConfig

 Thanks,
 Raghu

 -Original Message-
 From: Uthaiyashankar [mailto:[EMAIL PROTECTED]
 Sent: Thursday, October 02, 2008 1:13 PM
 To: Apache AXIS C User List
 Subject: Re: rampart_handler_util.c -- parameter not set

 Raghu Udupa wrote:
  
 Thanks Samisa.

 The first reported error is parameter 0 not being set in
 rampart_handler_util.c. I wanted to know which configuration parameter
 method rampart_get_rampart_configuration in rampart_handler_util.c is
 looking for.
  


 That error message is misleading. It is actually not an error. :). We
 have to remove it. So, you can safely ignore it.

 Regards,
 Shankar.

  
 Regards,
 Raghu

 -Original Message-
 From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, October 01, 2008 9:32 PM
 To: Apache AXIS C User List
 Subject: Re: rampart_handler_util.c -- parameter not set

  

2. Also, the webservices client is getting following error while
   attempting to engage rampart module.

 [Wed Oct  1 11:36:33 2008] [error] rampart_handler_util.c(241)
 [rampart][rampart_handler_utils] 0 parameter is not set.

 [Wed Oct  1 11:36:33 2008] [warning] msg_ctx.c(1381)
 RampartClientConfiguration not set in message context

 [Wed Oct  1 11:36:33 2008] [error] error.c(94) OXS ERROR [x509.c:284
 in openssl_x509_get_subject_key_identifier] oxs defualt error , The
 extenension index of NID_subject_key_identifier is not valid

 [Wed Oct  1 11:36:33 2008] [error] http_sender.c(1374) Error occurred
  

  
 in transport

 [Wed Oct  1 11:36:33 2008] [error

RE: rampart_handler_util.c -- parameter not set

2008-10-02 Thread Raghu Udupa
Thanks Samisa.

The first reported error is parameter 0 not being set in
rampart_handler_util.c. I wanted to know which configuration parameter
method rampart_get_rampart_configuration in rampart_handler_util.c is
looking for.

Regards,
Raghu

-Original Message-
From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 01, 2008 9:32 PM
To: Apache AXIS C User List
Subject: Re: rampart_handler_util.c -- parameter not set



2. Also, the webservices client is getting following error while
   attempting to engage rampart module.

 [Wed Oct  1 11:36:33 2008] [error] rampart_handler_util.c(241) 
 [rampart][rampart_handler_utils] 0 parameter is not set.

 [Wed Oct  1 11:36:33 2008] [warning] msg_ctx.c(1381) 
 RampartClientConfiguration not set in message context

 [Wed Oct  1 11:36:33 2008] [error] error.c(94) OXS ERROR [x509.c:284 
 in openssl_x509_get_subject_key_identifier] oxs defualt error , The 
 extenension index of NID_subject_key_identifier is not valid

 [Wed Oct  1 11:36:33 2008] [error] http_sender.c(1374) Error occurred 
 in transport

 [Wed Oct  1 11:36:33 2008] [error] rampart_engine.c(122) 
 [rampart][rampart_engine] Cannot get saved rampart_context

 [Wed Oct  1 11:36:33 2008] [error] rampart_in_handler.c(114) 
 [rampart][rampart_in_handler] rampart_context creation failed.

 [Wed Oct  1 11:36:33 2008] [error] phase.c(216) Handler 
 RampartInHandler invoke failed within phase PreDispatch

 [Wed Oct  1 11:36:33 2008] [error] engine.c(696) Invoking phase 
 PreDispatch failed

 [Wed Oct  1 11:36:33 2008] [error] soap11_builder_helper.c(368) 
 Unidentified character in SOAP 1.1 builder helper processing

As the error says, there is something wrong in your key.

Samisa...

3. I am also including the server log. I am using a self signed
   certificate generated using openssl to sign the message. Digest
   verification is succeeding. But signature verification is
failing.

  

 Thanks,
 Raghu
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]



Testing http basic authentication using axis2c http server

2008-09-26 Thread Raghu Udupa
Folks,

 

I am trying to test http authentication in a web services client. Is it
possible to test HTTP basic (or digest) authentication on axis2c http
server that is part of axis2c package?

 

Thanks,

Raghu



axis2c installation with and without SSL

2008-09-23 Thread Raghu Udupa
I am writing a web service client that could connect either to a HTTP or
HTTPS client. I installed axis2c with and without SSL support. 

 

When I see the axis2c/lib directory for with and without SSL support,
the shared object files have same names. 

 

I need to set the LD_LIBRARY_PATH to point to the correct library path
before I run the client. 

 

If I set the LD_LIBRARY_PATH to include both SSL and non-SSL paths, at
run time, the first path that has required shared object library file
will be used.  That is, if I specify library path that has SSL library
files first, then these files will be used for a non-SSL client as well.

 

Is there a simple way I can resolve this conflict? Or do I need 2
separate clients, one built with SSL axis2c library and the other with
regular (non-SSL library)?

 

Thanks,

Raghu

 

 

 



RE: axis2c installation with and without SSL

2008-09-23 Thread Raghu Udupa
Thanks Dumindu. 

 

Initially I did a normal install using configure. Afterwards, I did an
install for SSL client using 

%./configure --enable-openssl=yes --prefix=${AXIS2C_HOME}/deploy

 

The lib directory contained same number of library files, but their
sizes were different.

For example, the normal (without openssl), following .so files were
installed (/usr/local/axis2c/lib)

  libaxutil.so.0.5.0412529

  libguththila.so.0.5.0  338215

  libaxis2_parser.so.0.5.081773

  libaxis2_axiom.so.0.5.0496886

  libneethi.so.0.5.0 504229

  libaxis2_http_common.so.0.5.0  226953

  libaxis2_engine.so.0.5.0  1175501

  libaxis2_http_sender.so.0.5.0  205220

  libaxis2_http_receiver.so.0.5.0 32794

 

When I specified SSL option (/usr/local/axis2c-ssl/deploy/lib)

 libaxutil.so.0.5.0  412537   

 libguththila.so.0.5.0   338231

 libaxis2_parser.so.0.5.0 81777

 libaxis2_axiom.so.0.5.0 496902

 libneethi.so.0.5.0  504241

 libaxis2_http_common.so.0.5.0   226973

 libaxis2_engine.so.0.5.0   1175549

 libaxis2_http_sender.so.0.5.0   258473

 libaxis2_http_receiver.so.0.5.0  32810

 

As you can see, there is slight difference in file sizes. These
differences may have to do with time stamping in the object header
files. 

 

My question is does it matter which set of library files do I use? If
these differences do matter, can I use the .so library files generated
using SSL option for regular http server as well.

 

Regards,

Raghu



From: Dumindu Pallewela [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, September 23, 2008 3:33 PM
To: Apache AXIS C User List
Subject: Re: axis2c installation with and without SSL

 

You can use a single client for both http and https, if you provide the
ssl configuration in axis2.xml.

 

Regards,

Dumindu.

On Tue, Sep 23, 2008 at 10:15 PM, Raghu Udupa [EMAIL PROTECTED]
wrote:

I am writing a web service client that could connect either to a HTTP or
HTTPS client. I installed axis2c with and without SSL support. 

 

When I see the axis2c/lib directory for with and without SSL support,
the shared object files have same names. 

 

I need to set the LD_LIBRARY_PATH to point to the correct library path
before I run the client. 

 

If I set the LD_LIBRARY_PATH to include both SSL and non-SSL paths, at
run time, the first path that has required shared object library file
will be used.  That is, if I specify library path that has SSL library
files first, then these files will be used for a non-SSL client as well.

 

Is there a simple way I can resolve this conflict? Or do I need 2
separate clients, one built with SSL axis2c library and the other with
regular (non-SSL library)?

 

Thanks,

Raghu

 

 

 

 



clarification on axis2_svc_client_send_receive_with_op_qname API call

2008-09-18 Thread Raghu Udupa
If I use the synchronous call
axis2_svc_client_send_receive_with_op_qname to send and receive a
message, how do I track errors at server? It appears that I need to
check the response received and verify locally whether the service
execution is successful or not. My question, is can the error at service
be tracked by checking the value returned by
axis2_svc_client_send_receive_with_op_qname call? Or do I process the
response and handle error based on what I receive in the response?

 

Thanks,

Raghu



RE: Simplifying code generated by adb

2008-09-15 Thread Raghu Udupa
Thanks Dimuthu. At this point, I am proceeding with Samisa's suggestion to 
modify generated code by hand. I will take a look at the new wsdl2c at a later 
time.
 
Regards,
Raghu



From: Dimuthu Gamage [mailto:[EMAIL PROTECTED]
Sent: Mon 9/15/2008 11:26 AM
To: Apache AXIS C User List
Subject: Re: Simplifying code generated by adb


Hi Raghu,
The adb generated code will completely depends on the schema you have. If you 
really want to generate a similar set of adb structs you need to have a similar 
set of schemas in your WSDL.

Or with the fix to the JIRA https://issues.apache.org/jira/browse/AXIS2C-1145 
you are no longer need to write wrapper structs. And it will really minimize 
the code you have to write. (explained more on my blog, 
http://www.dimuthu.org/blog/2008/09/15/use-axis2c-wsdl2c-with-unwrapped-mode-for-simpler-code/
 )

Thanks
Dimuthu


On Fri, Sep 12, 2008 at 11:24 PM, Raghu Udupa [EMAIL PROTECTED] wrote:


I am using codegen with adb option to generate code for client stub and 
service processing. I have many simple string types defined in the XML schema. 
There is a significant amount of repetitive code generated for various 
elements. Generated code works properly. 

 

Is there a way, I mean, suggested guidelines to simplify the code 
generated to make all similar elements to share same methods?

 

Thanks,

Raghu

 

 




-- 
Thanks,
Dimuthu Gamage

http://www.dimuthu.org http://www.dimuthu.org/ 
http://www.wso2.org http://www.wso2.org/ 

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

User-id/password authentication while using https

2008-09-11 Thread Raghu Udupa
In axis2c user manual and API documentation, user-id and password
authentication appears to be provided only for HTTP protocol as shown in
the call below

axis2_options_set_http_auth_info( axis2_options_t * options, 

const axutil_env_t * env, 

const axis2_char_t * username, 

const axis2_char_t * password, 

const axis2_char_t * auth_type);

 

Could you let me know how to do similar validation on https transport?

 

Thanks,

Raghu



RE: User-id/password authentication while using https

2008-09-11 Thread Raghu Udupa
Thanks Hatim.

 

I am not using libcurl. 

 

I wanted to make sure I can use the same API call with https transport
as well.

 

Thanks,

Raghu

 



From: Hatim Daginawala [mailto:[EMAIL PROTECTED] 
Sent: Thursday, September 11, 2008 3:00 PM
To: Apache AXIS C User List
Subject: RE: User-id/password authentication while using https

 

I think this same call also works for https if you are not using
libcurl.

 

If you are using libcurl, I have a patch to get this to work. I can give
it to you.

 



From: Raghu Udupa [mailto:[EMAIL PROTECTED] 
Sent: Thursday, September 11, 2008 1:52 PM
To: axis-c-user@ws.apache.org
Subject: User-id/password authentication while using https

 

In axis2c user manual and API documentation, user-id and password
authentication appears to be provided only for HTTP protocol as shown in
the call below

axis2_options_set_http_auth_info( axis2_options_t * options, 

const axutil_env_t * env, 

const axis2_char_t * username, 

const axis2_char_t * password, 

const axis2_char_t * auth_type);

 

Could you let me know how to do similar validation on https transport?

 

Thanks,

Raghu



---
Confidentiality Notice: This electronic mail transmission is
confidential, 
may be privileged and should be read or retained only by the intended
recipient. If you have received this transmission in error, please
immediately notify the sender and delete it from your system. 



RE: User-id/password authentication while using https

2008-09-11 Thread Raghu Udupa
Thanks for the clarification Dimindu,

 

Regards,
Raghu

 



From: Dumindu Pallewela [mailto:[EMAIL PROTECTED] 
Sent: Thursday, September 11, 2008 3:18 PM
To: Apache AXIS C User List
Subject: Re: User-id/password authentication while using https

 

Yes the same API can be used for either http or https transports, if you
don't use libcurl.

Regards,
Dumindu.

On Fri, Sep 12, 2008 at 12:35 AM, Raghu Udupa [EMAIL PROTECTED]
wrote:

Thanks Hatim.

 

I am not using libcurl. 

 

I wanted to make sure I can use the same API call with https transport
as well.

 

Thanks,

Raghu

 



From: Hatim Daginawala [mailto:[EMAIL PROTECTED] 
Sent: Thursday, September 11, 2008 3:00 PM
To: Apache AXIS C User List
Subject: RE: User-id/password authentication while using https

 

I think this same call also works for https if you are not using
libcurl.

 

If you are using libcurl, I have a patch to get this to work. I can give
it to you.

 



From: Raghu Udupa [mailto:[EMAIL PROTECTED] 
Sent: Thursday, September 11, 2008 1:52 PM
To: axis-c-user@ws.apache.org
Subject: User-id/password authentication while using https

 

In axis2c user manual and API documentation, user-id and password
authentication appears to be provided only for HTTP protocol as shown in
the call below

axis2_options_set_http_auth_info( axis2_options_t * options, 

const axutil_env_t * env, 

const axis2_char_t * username, 

const axis2_char_t * password, 

const axis2_char_t * auth_type);

 

Could you let me know how to do similar validation on https transport?

 

Thanks,

Raghu



---
Confidentiality Notice: This electronic mail transmission is
confidential, 
may be privileged and should be read or retained only by the intended
recipient. If you have received this transmission in error, please
immediately notify the sender and delete it from your system. 




-- 
Dumindu Pallewela
Creately.com



RE: Get error while parsing an XML message containing a complex type at axis2_http_server

2008-09-10 Thread Raghu Udupa
Folks,

 

I replaced axutil_array_list_set with axutil_array_list_add and every
thing seem to work fine.

 

Thanks,

Raghu

 



From: Raghu Udupa [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, September 09, 2008 10:34 PM
To: axis-c-user@ws.apache.org
Subject: Get error while parsing an XML message containing a complex
type at axis2_http_server

 

I am using wsdl2c to generate code with data binding. I have been able
to send and receive messages when XML message contains simple types.

 

But, I have one unbounded array element FaxDataFiles defined as

xsd:element name=FaxDataFiles

  xsd:annotation

   xsd:documentationThe list of files to be faxed/xsd:documentation

  /xsd:annotation

  xsd:complexType

   xsd:sequence

xsd:element ref=ft:Data maxOccurs=unbounded/

   /xsd:sequence

  /xsd:complexType

 /xsd:element

 xsd:element name=Data

  xsd:annotation

   xsd:documentationThe file to be faxed/xsd:documentation

  /xsd:annotation

  xsd:complexType

   xsd:sequence

xsd:element name=FileContent type=xsd:string

 xsd:annotation

  xsd:documentationThe content of the file to be faxed (MIME
encoded)/xsd:documentation

 /xsd:annotation

/xsd:element

xsd:element name=FileType type=xsd:string maxLength=100

 xsd:annotation

  xsd:documentationThe type of the file to be
faxed/xsd:documentation

 /xsd:annotation

/xsd:element

   /xsd:sequence

  /xsd:complexType

 /xsd:element

 

 

Further, message request is defined as

 

xsd:element name=ProcRequest

  xsd:complexType

   xsd:sequence

xsd:element ref=ft:BASETID/

xsd:element ref=ft:CONTROLTID/

xsd:element ref=ft:DELIVERYTID/

xsd:element ref=ft:PHONE/

xsd:element ref=ft:StartTime/

xsd:element ref=ft:StopTime/

 

I get the following error at axis2_http_server

 

[Tue Sep  9 22:25:59 2008] [debug] phase.c(210) Invoke the handler
context_handler within the phase PostDispatch

[Tue Sep  9 22:25:59 2008] [debug] class_loader.c(140)
..//services/ReceiveFaxManagerService/libReceiveFaxManagerService.so
shared lib loaded successfully

[Tue Sep  9 22:25:59 2008] [error] src/adb_FaxDataFiles_type0.c(233)
Data (@minOccurs = '1') only have 0 elements

[Tue Sep  9 22:25:59 2008] [error] src/adb_ReceiveFaxRequest.c(1498)
failed in building adb object for element FaxDataFiles

[Tue Sep  9 22:25:59 2008] [error] src/adb_ReceiveFaxRequest.c(1508)
failed in setting the value for FaxDataFiles

[Tue Sep  9 22:25:59 2008] [error]
axis2_svc_skel_ReceiveFaxManagerService.c(166) NULL returnted from the
ReceiveFaxRequest_deserialize: This should be due to an invalid XML

[Tue Sep  9 22:25:59 2008] [debug] raw_xml_in_out_msg_recv.c(382)
fault_detail:Detail/Detail

[Tue Sep  9 22:25:59 2008] [debug] phase.c(210) Invoke the handler
AddressingOutHandler within the phase MessageOut

[Tue Sep  9 22:25:59 2008] [info]  Starting addressing out handler

[Tue Sep  9 22:25:59 2008] [info]  Request served in 0.006 seconds

[Tue Sep  9 22:27:15 2008] [info]  Received signal SIGINT. Server
shutting down

[Tue Sep  9 22:27:15 2008] [info]  Terminating HTTP server thread

 

I am populating all parts (parameters) properly as defined in xsd schema
file. In addition, FaxDataFiles structure contains one entry (That is,
one Data element).

 

I appreciate any advice as to how to resolve this issue.

 

Thanks,

Raghu Udupa

 



RE: axis2 client with HTTP as well as HTTPS connectivity

2008-09-09 Thread Raghu Udupa
Thanks Manjula.

I was going through the section on Using SSL client in axis2c manual. My
question is, can I use an axis2 client built with SSL library to
communicate with a client using plain http protocol? Or do I need 2
separate axis2c clients, one for using http protocol and the other for
https protocol.

Thanks,
Raghu

-Original Message-
From: Manjula Peiris [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, September 09, 2008 1:57 AM
To: Apache AXIS C User List
Subject: Re: axis2 client with HTTP as well as HTTPS connectivity


On Mon, 2008-09-08 at 15:09 -0400, Raghu Udupa wrote:
 I need connectivity to customers who would like to communicate either
 using HTTP or HTTPS protocol. Basically, I need to distribute
 documents, addressed to a particular customer, to that customer using
 the protocol (http/https) supported by their web service.
 
  
 
 I need to write a generic web-services generic client application that
 will support both. Could you let me know how I can do that
 programmatically?

Follow [1] and go through the samples which comes with the distribution.

[1] http://ws.apache.org/axis2/c/docs/axis2c_manual.html

-Manjula

 
  
 
 Thanks,
 
 Raghu
 
 


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



Clarification on axis2.xml

2008-09-09 Thread Raghu Udupa
When I set the axis2.xml home, do I need to keep the name of the file as
axis2.xml? What I mean is, can I name the file as say, cust1_axis2.xml
as shown below?

 

client_home = /home/cust1/axis2c/deploy/ cust1_axis2.xml

  /* Create service client */

  svc_client = axis2_svc_client_create(env, client_home);

 

Thanks,

Raghu



axis2 client with HTTP as well as HTTPS connectivity

2008-09-08 Thread Raghu Udupa
I need connectivity to customers who would like to communicate either
using HTTP or HTTPS protocol. Basically, I need to distribute documents,
addressed to a particular customer, to that customer using the protocol
(http/https) supported by their web service.

 

I need to write a generic web-services generic client application that
will support both. Could you let me know how I can do that
programmatically?

 

Thanks,

Raghu



wsdl2c question

2008-09-04 Thread Raghu Udupa
Hi,

 

I am using wsdl2c tool to generate C code for model object with ADB
bindings. For each XML element, I see 3 sets of files like

adb_UserCode.c

adb_UserCode.h

adb_UserCode_type0.c

adb_UserCode_type0.h

adb_UserCode_type1.c

adb_UserCode_type1.h

 

I would like to know how what each combination of files, adb_UserCode,
adb_UserCode_type0 and adb_UserCode_type 1 is used for?

 

Thanks,

Raghu



Need to write a web services client with optional digital signature on Linux EV4 servers

2008-09-02 Thread Raghu Udupa
I am writing a web services client to send messages to a customer's web
service. This client will be running on an Intel x86 based RedHat
Enterprise version 4.0 Linux server. 

 

Can I just install the Linux Binary distribution package? Or do I need
to download the source package and make a new set of binaries for Redhat
EV4 server?

 

Thanks,

Raghu