Nabble - Axis - C++ - User

Re: deploying axis2c with IBM http server

2009-12-22T08:11:37Z

Pradeep Patel wrote:

> Hi,
>
> I have written a web service on windows using Axis2c and i have
> deployed it successfully in axis2_http_server. Then i deployed it with
> Apache http server by following the procedure described in Axis2c manual.
>
> http://ws.apache.org/axis2/c/docs/axis2c_manual.html#mod_axis2
>
> Now I want to deploy the same service with IBM http server and i
> searched a lot but i could not find any help. The reason is we have
> IBM http server on the system where the web service will be deployed
> finally.
>
> IBM http server is based on Apache http server so i guess there should
> not be much difference. I tried to follow the same procedure from the
> manual but its not working.

What are the errors/problems you encounter?. If that server support
Apache modules support in the same way as the original Apache server
then it should work fine.

Thanks,
Damitha
>
> Has anyone did the same? Can someone please suggest me any guidelines
> or any link?
>
> --
> Thanks & Regards
> Pradeep Patel

--
__________________________________________________________________

Damitha Kumarage
Technical Lead; WSO2 Inc.
"Oxygenating the Web Service Platform; " http://www.wso2.com/

blog: " http://damithakumarage.wordpress.com/
__________________________________________________________________

deploying axis2c with IBM http server

2009-12-21T22:26:18Z

Hi,

I have written a web service on windows using Axis2c and i have deployed it successfully in axis2_http_server. Then i deployed it with Apache http server by following the procedure described in Axis2c manual.

http://ws.apache.org/axis2/c/docs/axis2c_manual.html#mod_axis2

Now I want to deploy the same service with IBM http server and i searched a lot but i could not find any help. The reason is we have IBM http server on the system where the web service will be deployed finally.

IBM http server is based on Apache http server so i guess there should not be much difference. I tried to follow the same procedure from the manual but its not working.

Has anyone did the same? Can someone please suggest me any guidelines or any link?

--
Thanks & Regards
Pradeep Patel

Signature verification failure when signing the body in Rampart/C (but not in Rampart/Java)

2009-12-18T09:46:04Z

Hi there,

I am trying to write a C client using Axis2/C (1.6.0) and Rampart/C (1.3.0) to consume a simple secured Echo web service. This web service has a security policy applied that requires that the content of the body be signed. The web service is written using Axis2/Java and secured using Rampart/Java. The C client stub is automatically generated using WSDL2C.bat, and a policy file is applied in the test code. While running this C client, I ran into a problem “The signature or decryption was invalid”, from tcpmon, I can see that a secured SOAP message is sent out but response has the detailed exception trace as follows:

org.apache.axis2.AxisFault: The signature or decryption was invalid org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:166 org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:95) at org.apache.axis2.engine.Phase.invoke(Phase.java:318 org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160 org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167 org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:266 org.apache.axis2.transport.http.server.AxisHttpService.doService(AxisHttpService.java:281 org.apache.axis2.transport.http.server.AxisHttpService.handleRequest(AxisHttpService.java:187 org.apache.axis2.transport.http.server.HttpServiceProcessor.run(HttpServiceProcessor.java:82 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675

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

Caused by: org.apache.ws.security.WSSecurityException: The signature or decryption was invalid org.apache.ws.security.processor.SignatureProcessor.verifyXMLSignature(SignatureProcessor.java:419 org.apache.ws.security.processor.SignatureProcessor.handleToken(SignatureProcessor.java:85 org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:311 org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:228

org.apache.rampart.RampartEngine.process(RampartEngine.java:146 org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92)

... 11 more

To make sure that my service is written properly, I also wrote a Java client (using wsdl2java to automatically generate stub from the same wsdl file) using Axis2/Java (1.5.1) and Rampart/Java (1.4) to consume it, with a similar policy file used in C client and same security keys stored in JKS keystore, and it works fine. This makes me wonder if this is a known bug in Rampart/C or Axis2/C?

Here attached related files for investigating this issue. Any help from Axis2-C developers or users will be greatly appreciated.

1. policy.xml: security policy file used in C client

2. services.xml: web service xml file

3. Echo.c : C client code

4. Keys.zip: containing all the security keys used in this exercise. server.jks contains keys for both client and server (alias are “client” and “server” respectively). Both keystore and key password are “testing”, and client and server PEM files are generated from server.jks by following steps in http://www.swview.org/node/191).

5. Echo.wsdl: wsdl used to generate code for client stub.

6. echo.log: detailed Axis2 log from running Echo client

7. reqsoap.xml: SOAP request sent from Echo c client

Thanks.

-min

<wsp:Policy xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy">
<wsp:ExactlyOne>
<wsp:All>
<sp:AsymmetricBinding xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
<wsp:Policy>
<sp:InitiatorToken>
<wsp:Policy>
<sp:X509Token sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient">
<wsp:Policy>
<sp:RequireThumbprintReference/>
<sp:WssX509V3Token10/>
</wsp:Policy>
</sp:X509Token>
</wsp:Policy>
</sp:InitiatorToken>
<sp:RecipientToken>
<wsp:Policy>
<sp:X509Token sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient">
<wsp:Policy>
<sp:RequireThumbprintReference/>
<sp:WssX509V3Token10/>
</wsp:Policy>
</sp:X509Token>
</wsp:Policy>
</sp:RecipientToken>
<sp:AlgorithmSuite>
<wsp:Policy>
<sp:Basic128Rsa15/>

</wsp:Policy>
</sp:AlgorithmSuite>
<sp:Layout>
<wsp:Policy>
<sp:Strict/>
</wsp:Policy>
</sp:Layout>
</wsp:Policy>
</sp:AsymmetricBinding>
<sp:Wss10 xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
<wsp:Policy>
<sp:MustSupportRefEmbeddedToken/>
<sp:MustSupportRefKeyIdentifier/>
<sp:MustSupportRefIssuerSerial/>
</wsp:Policy>
</sp:Wss10>
<sp:SignedParts xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
<sp:Body/>
</sp:SignedParts>


<rampc:RampartConfig xmlns:rampc="http://ws.apache.org/rampart/c/policy">




<rampc:ReceiverCertificate>c:/AlexEcho/c-client/keys/server.cer</rampc:ReceiverCertificate>
<rampc:Certificate>c:/AlexEcho/c-client/keys/client.cer</rampc:Certificate>
<rampc:PrivateKey>c:/AlexEcho/c-client/keys/client.pem</rampc:PrivateKey>
</rampc:RampartConfig>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>

<?xml version="1.0" encoding="UTF-8"?>


<serviceGroup>
<service name="EchoService">
<messageReceivers>
<messageReceiver mep="http://www.w3.org/ns/wsdl/in-out" class="org.apache.axis2.jaxws.samples.echo.EchoServiceMessageReceiverInOut"/>
</messageReceivers>
<parameter name="ServiceClass">org.apache.axis2.jaxws.samples.echo.EchoServiceSkeleton</parameter>
<parameter name="useOriginalwsdl">true</parameter>
<parameter name="modifyUserWSDLPortAddress">true</parameter>
<operation name="echoOperation" mep="http://www.w3.org/ns/wsdl/in-out" namespace="http://org/apache/axis2/jaxws/samples/echo/">
<actionMapping>echoOperation</actionMapping>
<outputActionMapping>http://org/apache/axis2/jaxws/samples/echo/EchoServicePortType/echoOperationResponse</outputActionMapping>
</operation>

<module ref="rampart" />

<wsp:Policy wsu:Id="EchoSecPol" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy">

<wsp:ExactlyOne>
<wsp:All>
<sp:AsymmetricBinding xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
<wsp:Policy>
<sp:InitiatorToken>
<wsp:Policy>
<sp:X509Token sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient">
<wsp:Policy>
<sp:RequireThumbprintReference/>
<sp:WssX509V3Token10/>
</wsp:Policy>
</sp:X509Token>
</wsp:Policy>
</sp:InitiatorToken>
<sp:RecipientToken>
<wsp:Policy>
<sp:X509Token sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient">
<wsp:Policy>
<sp:RequireThumbprintReference/>
<sp:WssX509V3Token10/>
</wsp:Policy>
</sp:X509Token>
</wsp:Policy>
</sp:RecipientToken>
<sp:AlgorithmSuite>
<wsp:Policy>
<sp:Basic128Rsa15/>

</wsp:Policy>
</sp:AlgorithmSuite>
<sp:Layout>
<wsp:Policy>
<sp:Strict/>
</wsp:Policy>
</sp:Layout>
</wsp:Policy>
</sp:AsymmetricBinding>
<sp:Wss10 xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
<wsp:Policy>
<sp:MustSupportRefEmbeddedToken/>
<sp:MustSupportRefKeyIdentifier/>
<sp:MustSupportRefIssuerSerial/>
</wsp:Policy>
</sp:Wss10>
<sp:SignedParts xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
<sp:Body/>
</sp:SignedParts>



<ramp:RampartConfig xmlns:ramp="http://ws.apache.org/rampart/policy">
<ramp:user>server</ramp:user>

<ramp:passwordCallbackClass>org.apache.axis2.jaxws.samples.echo.PWCBHandler</ramp:passwordCallbackClass>

<ramp:signatureCrypto>
<ramp:crypto provider="org.apache.ws.security.components.crypto.Merlin">
<ramp:property name="org.apache.ws.security.crypto.merlin.keystore.type">JKS</ramp:property>
<ramp:property name="org.apache.ws.security.crypto.merlin.file">resources/server.jks</ramp:property>
<ramp:property name="org.apache.ws.security.crypto.merlin.keystore.password">testing</ramp:property>
</ramp:crypto>
</ramp:signatureCrypto>

</ramp:RampartConfig>

</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
</service>
</serviceGroup>

/*
Demo client for Echo service
*/

#include "axis2_stub_EchoService.h"

#include "neethi_util.h" //SetPolicy

#include <stdio.h>
#include <axiom.h>
#include <axis2_util.h>
#include <axiom_soap.h>
#include <axis2_client.h>

int main(int argc, char **argv)
{

const axutil_env_t *env = NULL;
const axis2_char_t *address = NULL;
const axis2_char_t *client_home = NULL;
axis2_char_t *file_name = NULL;
axis2_char_t *policy_file = NULL;
axis2_stub_t *stub = NULL;
axis2_svc_client_t* svc_client = NULL;
axis2_status_t status = AXIS2_FAILURE;
neethi_policy_t *policy = NULL;
adb_echoStringInput_t* echoStringInput = NULL;
adb_echoStringResponse_t* echoStringResponse = NULL;

/* Set up the environment */
env = axutil_env_create_all("echo.log", AXIS2_LOG_LEVEL_TRACE);

/* Set end-point-reference and client repository of echo service */
address = "http://localhost:4041/axis2/services/EchoService";
if (argc > 2)
{
address = argv[1];
client_home = argv[2];
}
printf("Using endpoint : %s\n", address);
/*If the client home is not specified, use the AXIS2C_HOME*/
if (!client_home)
{
client_home = AXIS2_GETENV("AXIS2C_HOME");
printf("\nNo client_home specified. Using default %s\n", client_home);
}
printf("Using client_home : %s\n", client_home);

if ((axutil_strcmp(argv[1], "-h") == 0) || (axutil_strcmp(argv[1], "--help") == 0))
{
printf("Usage : %s [endpoint_url] [client_home]\n", argv[0]);
printf("use -h for help\n");
return 0;
}

// Create stub
stub = axis2_stub_create_EchoService(env, client_home, address);
if (!stub) {
printf("stub=NULL exit\n");
return 16;
}

/* Get service client from stub*/
svc_client = axis2_stub_get_svc_client(stub, env );
if (!svc_client)
{
printf("Error getting service client from stub\n");
return -1;
}

/*We need to specify the client's policy file location*/
if(client_home)
{
file_name = axutil_stracat(env, client_home, AXIS2_PATH_SEP_STR);
policy_file = axutil_stracat(env, file_name, "policy.xml" );
AXIS2_FREE(env->allocator, file_name);
file_name = NULL;
}else{
printf("Client Home not Specified\n");
printf("echo client invoke FAILED!\n");
return 0;
}

/*Create the policy, from file*/
policy = neethi_util_create_policy_from_file(env, policy_file);
if(policy_file){
AXIS2_FREE(env->allocator, policy_file);
policy_file = NULL;
}
if(!policy)
{
printf("\nPolicy creation failed from the file. %s\n", policy_file);
}

// set policy
status = axis2_svc_client_set_policy(svc_client, env, policy);

if(status == AXIS2_FAILURE)
{
printf("Policy setting failed\n");
}

/*If not engaged in the client's axis2.xml, uncomment this line*/
/*axis2_svc_client_engage_module(svc_client, env, "rampart");*/

echoStringInput = adb_echoStringInput_create(env);
if (!echoStringInput) {
printf("echoStringInput=NULL exit\n");
return 16;
}

adb_echoStringInput_set_echoInput(echoStringInput, env, "Hello there from Houston!");

echoStringResponse = axis2_stub_op_EchoService_echoOperation(stub, env,
echoStringInput);

if ( !echoStringResponse)
{
printf("echoStringResponse=%p\n", adb_echoStringResponse_get_echoResponse(echoStringResponse, env));
}
else
{
printf("Echo invoke failed!\n");
}

if (svc_client)
{
axis2_svc_client_free(svc_client, env);
svc_client = NULL;
}
if (env)
{
axutil_env_free((axutil_env_t *) env);
env = NULL;
}

return 0;

}

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" soapenv:mustUnderstand="1">
<wsse:BinarySecurityToken EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="CertID-a0078d0f-b599-441f-a5d2" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3">MIICbjCCAdegAwIBAgIEStbqSDANBgkqhkiG9w0BAQUFADBaMQswCQYDVQQGEwJVUzELMAkGA1UECBMCVFgxEDAOBgNVBAcTB0hPVVNUT04xDDAKBgNVBAoTA0JNQzENMAsGA1UECxMEVEVTVDEPMA0GA1UEAxMGQ0xJRU5UMB4XDTA5MTAxNTA5MjQyNFoXDTEyMTAxNTA5MjQyNFowWjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlRYMRAwDgYDVQQHEwdIT1VTVE9OMQwwCgYDVQQKEwNCTUMxDTALBgNVBAsTBFRFU1QxDzANBgNVBAMTBkNMSUVOVDCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAl8Qv3DNdBT7crJqQYMOaqM0fjA1mXwp4BC09re7mm5svvW8rNWZTxrI3uzdLyjlO6TSyA5c8qiLgXm2svMZIz1e0j+uEPWfdGs84OeugUMn8gd0LOcHsInZqyAS0D0S7jNXfHo9TFlGDaar/V/bxfhqwkSnJdZgRUQAbhyWYTckCAwEAAaNBMD8wHQYDVR0OBBYEFCgjLkue5/dvq0YP5GMv6viqa97PMB4GA1UdEQEB/wQUMBKBEG1kb3VnaHR5QGJtYy5jb20wDQYJKoZIhvcNAQEFBQADgYEAEHC5I1Thb1QVPep3TCng5MxHgNntkQN2TFJUSVBXaQwlG5cQyd+YjjGYHLW5pdC58XDccY/VzcXQg5qvbkI7VrJ1P/7OazotiDAflnpXfFf5BgmTQ1GbMzhfbcdkqdFBYB+IxrTU/igr2JjhJ8vjGW2S3IkUuPJP54IDj6qsgZk=</wsse:BinarySecurityToken>
<ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#" Id="SigID-d70a56fb-3433-4097-b660">
<ds:SignedInfo>
<ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></ds:CanonicalizationMethod>
<ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"></ds:SignatureMethod>
<ds:Reference URI="#SigID-2cf7d21a-6130-4155-99be">
<ds:Transforms>
<ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></ds:Transform>
</ds:Transforms>
<ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></ds:DigestMethod>
<ds:DigestValue>Th3oCK56mezV8qZPOEszDrzr/vE=</ds:DigestValue>
</ds:Reference>
</ds:SignedInfo>
<ds:SignatureValue>hvFwIKogUFN0D8K8qnuE5dDquhRd48KQnHejg7p65wUvRLUtjnSlZH4vcpr9emEmfDSQA3SmnKIMSoUBLW2pITTQovThqzSM6ijwU6Q9xfBck723s2GfKJLSMRjTTim6YWKcplW8oMy2mi/0CAV8ac5OSoGJ4AKqvqRchqChTLc=</ds:SignatureValue>
<ds:KeyInfo>
<wsse:SecurityTokenReference>
<wsse:Reference URI="#CertID-a0078d0f-b599-441f-a5d2" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"></wsse:Reference>
</wsse:SecurityTokenReference>
</ds:KeyInfo>
</ds:Signature>
</wsse:Security>
</soapenv:Header>
<soapenv:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="SigID-2cf7d21a-6130-4155-99be">
<n:echoStringInput xmlns:n="http://org/apache/axis2/jaxws/samples/echo/">
<echoInput>Hello there from Houston!</echoInput>
</n:echoStringInput>
</soapenv:Body></soapenv:Envelope>

keys.zip (12K) Download Attachment
Echo.wsdl (4K) Download Attachment
echo.log (20K) Download Attachment

Re: using faults w/ wsdl2c

2009-12-15T12:32:31Z

On Sat, Dec 5, 2009 at 5:56 AM, Samisa Abeysinghe <samisa@...> wrote:

On Fri, Dec 4, 2009 at 11:09 PM, Sam Carleton <scarleton@...> wrote:
Dimuthu,

Where EXACTLY does one find the latest WSDL2C code? Is it in an build or is it in the Axis2/Java SVN repository?

Hi,

In fact right now we are not maintaining an Axis2 nightly build. So you have to do your own build of Axis2/Java to get the latest WSDL2C code.

Thanks
Dimuthu

Axis2 svn.

Samisa...

Sam

On Thu, Dec 3, 2009 at 10:57 PM, Dimuthu Gamage <dimuthuc@...> wrote:

Hi,

If you use the latest axis2 WSDL2C generator code, you don't need to create soap fault message manually as the generated code provide lot of support in generating fault message.

Please have a look at this for the improved API, http://www.dimuthu.org/blog/2009/02/09/code-generate-custom-soap-faults-for-axis2c/

Thanks
Dimuthu

On Wed, Nov 18, 2009 at 3:49 AM, Doug Price <Doug.Price@...> wrote:

While I see that this approach allows the creation of user-defined fault types, is it possible to also use it to specify the standard SOAP-ENV:Fault? I see a struct named axiom_soap_fault_t in the distribution, but I can't seem to return it from the axis2_svc_skel_*_on_fault() function because it requires a pointer to the SOAP body to create one. Is there some other way to return a standard SOAP fault from a service?

--
Doug Price
Research Director | Presagis

T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399

DISCLAIMER: This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and/or proprietary information. Do not read, copy, or disseminate this message unless you are the addressee. Any unauthorized review, use, disclosure or distribution is strictly prohibited. If you have received this message in error, please contact the sender by reply e-mail and delete the original and any copies from your system.

-----Original Message-----

From: Amir Mousavizadegan [mailto:amir.mousavizadegan@...]

Sent: Tuesday, November 17, 2009 10:29 AM
To: Apache AXIS C User List
Subject: Re: using faults w/ wsdl2c

I did not write the sample codes nor the document, however in order to
get it working, you have to change the body of the generated code, or
create a replacement function as I did.
thx
Amir
----- Original Message -----
From: "Doug Price" <Doug.Price@...>
To: "Apache AXIS C User List" <axis-c-user@...>
Sent: Tuesday, November 17, 2009 11:05 AM
Subject: RE: using faults w/ wsdl2c

Just what I was looking for. Thanks so much.

A quick follow up question on the code though. Is there a reason that
axis2_svc_skel_Division_on_fault() doesn't use the adv_divFault api to
create the fault?

--
Doug Price
Research Director | Presagis

T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399

DISCLAIMER: This e-mail message is for the sole use of the intended
recipient(s) and may contain confidential and/or proprietary information. Do
not read, copy, or disseminate this message unless you are the addressee.
Any unauthorized review, use, disclosure or distribution is strictly
prohibited. If you have received this message in error, please contact the
sender by reply e-mail and delete the original and any copies from your
system.

-----Original Message-----

From: Amir Mousavizadegan [mailto:amir.mousavizadegan@...]
Sent: Tuesday, November 17, 2009 7:52 AM
To: Apache AXIS C User List
Subject: Re: using faults w/ wsdl2c

Please see attached document
----- Original Message -----
From: "Doug Price" <Doug.Price@...>
To: <axis-c-user@...>
Sent: Monday, November 16, 2009 4:47 PM
Subject: using faults w/ wsdl2c

I created a simple web service w/ Axis2c using wsdl2c on a WSDL file I
created in Eclipse. The default functionality of this works fine. However,
now I'd like to incorporate faults into my SOAP messages. I created a fault
type in my WSDL and wsdl2c creates the wrappers for the fault message, but
the service skeleton and client stubs files seem to hard coded to assume no
faults are ever sent / received. For example, the client axis2_stub_op_*()
function takes my request message type and returns my response message type,
but doesn't seem to account for my fault type. Modifying the code, I can
see that the fault is received and correctly deserialized, but I'll have to
continually hand edit the axis2_stub*.c and my client.c file as I make
modifications to my WSDL in order to make this work.

The same is true on the service side w/ the axis2_skel*() functions. Am I
missing something here, or are faults not supported w/ wsdl2c?

--
Doug Price
Research Director | Presagis

T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399

DISCLAIMER: This e-mail message is for the sole use of the intended
recipient(s) and may contain confidential and/or proprietary information. Do
not read, copy, or disseminate this message unless you are the addressee.
Any unauthorized review, use, disclosure or distribution is strictly
prohibited. If you have received this message in error, please contact the
sender by reply e-mail and delete the original and any copies from your
system.

--
Thanks,
Dimuthu Gamage

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

--
Samisa Abeysinghe
Director, Engineering - WSO2 Inc.

http://www.wso2.com/ - "The Open Source SOA Company"

--
Thanks,
Dimuthu Gamage

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

Re: DLL path for libTestCases_t.so is set to libTestCases.so

2009-12-15T09:41:42Z

Shankar & Samisa,
I checked Appendix B of the Axis2/C Manual, which explains what happened here. In the services.xml file both the service name and the library name (serviceClass) needed to be changed to have _t appended. I had only changed the service name.
Thank you for the help.
George

-------------- Original message from gsherwood@...: --------------

Shankar,
I looked at the services.xml files for the two services. The service names are set correctly to the different names, but I see that the ServiceClass is set to TestCases (without the _t) for both:
<parameter name="ServiceClass" locked="xsd:false">TestCases</parameter>
Could that explain the problem?
Thanks,
George

<service name="TestCases">
<parameter name="ServiceClass" locked="xsd:false">TestCases</parameter>
<parameter name="wsdl_path" locked="xsd:false">/usr/local/apache2/conf/TestCases.wsdl</parameter>
<description>
Testcover.com TestCases service.
Access by subscription. Please register at Testcover.com.
</description>
<operation name="getTestCases"/>
</service>

<service name="TestCases_t">
<parameter name="ServiceClass" locked="xsd:false">TestCases</parameter>
<parameter name="wsdl_path" locked="xsd:false">/usr/local/apache2/conf/TestCases_t.wsdl</parameter>
<description>
Testcover.com TestCases service, for internal testing only.
Access for authorized test staff only.
</description>
<operation name="getTestCases"/>
</service>

-------------- Original message from Selvaratnam Uthaiyashankar <uthaiyashankar@...>: --------------

> On Sun, Dec 13, 2009 at 3:24 PM, Samisa Abeysinghe wrote:
> >
> >
> > On Sat, Dec 5, 2009 at 7:46 AM, wrote:
> >>
> >> Samisa,
> >> Thanks for the response. I mentioned the _t because when I posted the
> >> message, the ONLY difference between the two services was their names. One
> >> has the _t and the other does not. So it seemed likely to me that the
> >> different behavior was related to their different names. This is not a big
> >> problem for me because I think I have a workaround. I guessed that the
> >> Axis2/C team would either recognize what's happening here, or would want to
> >> understand it sometime.
> >
> > Thank you for the input. I think there might be a bug/issue in handling the
> > service names with special characters such as '_'. Need to look into this.
> > If you could raise a Jira, that might be useful.
>
> I checked with a service having _t as part of its name. I could not
> recreate the problem. I also strongly believe that the problem is not
> due to _t.
>
> Can you send the services.xml file if possible? Is there any other
> libraries linked to your services?
>
> Regards,
> Shankar
>
>
> > Samisa...
> >
>
>
>
> --
> S.Uthaiyashankar
> Software Architect
> WSO2 Inc.
> http://wso2.com/ - "The Open Source SOA Company"

Re: DLL path for libTestCases_t.so is set to libTestCases.so

2009-12-14T07:20:18Z

Shankar,
I looked at the services.xml files for the two services. The service names are set correctly to the different names, but I see that the ServiceClass is set to TestCases (without the _t) for both:
<parameter name="ServiceClass" locked="xsd:false">TestCases</parameter>
Could that explain the problem?
Thanks,
George

<service name="TestCases">
<parameter name="ServiceClass" locked="xsd:false">TestCases</parameter>
<parameter name="wsdl_path" locked="xsd:false">/usr/local/apache2/conf/TestCases.wsdl</parameter>
<description>
Testcover.com TestCases service.
Access by subscription. Please register at Testcover.com.
</description>
<operation name="getTestCases"/>
</service>

<service name="TestCases_t">
<parameter name="ServiceClass" locked="xsd:false">TestCases</parameter>
<parameter name="wsdl_path" locked="xsd:false">/usr/local/apache2/conf/TestCases_t.wsdl</parameter>
<description>
Testcover.com TestCases service, for internal testing only.
Access for authorized test staff only.
</description>
<operation name="getTestCases"/>
</service>

-------------- Original message from Selvaratnam Uthaiyashankar <uthaiyashankar@...>: --------------

> On Sun, Dec 13, 2009 at 3:24 PM, Samisa Abeysinghe wrote:
> >
> >
> > On Sat, Dec 5, 2009 at 7:46 AM, wrote:
> >>
> >> Samisa,
> >> Thanks for the response. I mentioned the _t because when I posted the
> >> message, the ONLY difference between the two services was their names. One
> >> has the _t and the other does not. So it seemed likely to me that the
> >> different behavior was related to their different names. This is not a big
> >> problem for me because I think I have a workaround. I guessed that the
> >> Axis2/C team would either recognize what's happening here, or would want to
> >> understand it sometime.
> >
> > Thank you for the input. I think there might be a bug/issue in handling the
> > service names with special characters such as '_'. Need to look into this.
> > If you could raise a Jira, that might be useful.
>
> I checked with a service having _t as part of its name. I could not
> recreate the problem. I also strongly believe that the problem is not
> due to _t.
>
> Can you send the services.xml file if possible? Is there any other
> libraries linked to your services?
>
> Regards,
> Shankar
>
>
> > Samisa...
> >
>
>
>
> --
> S.Uthaiyashankar
> Software Architect
> WSO2 Inc.
> http://wso2.com/ - "The Open Source SOA Company"

Re: Getting the HTTP Status Codes

2009-12-14T06:36:37Z

On Mon, Dec 14, 2009 at 3:25 AM, Selvaratnam Uthaiyashankar <uthaiyashankar@...> wrote:

Hi Sam,

did you try axis2_svc_client_get_http_status_code?

No I did not, thank you, that worked like a charm!

Re: Getting the HTTP Status Codes

2009-12-14T00:25:55Z

Hi Sam,

did you try axis2_svc_client_get_http_status_code?

Regards,
Shankar

On Mon, Dec 14, 2009 at 9:25 AM, Sam Carleton
<scarleton@...> wrote:
> I am working with the Axis2/C client. The web server can reply with a
> number of different HTTP Status Codes, HTTP_UNAUTHORIZED
> or HTTP_MOVED_PERMANENTLY. It looks like in both
> cases env->error->error_number is AXIS2_ERROR_HTTP_CLIENT_TRANSPORT_ERROR
> (74). Is there any way to get to the actual HTTP Status Code?
> Sam

--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Re: DLL path for libTestCases_t.so is set to libTestCases.so

2009-12-14T00:10:37Z

On Sun, Dec 13, 2009 at 3:24 PM, Samisa Abeysinghe <samisa@...> wrote:

>
>
> On Sat, Dec 5, 2009 at 7:46 AM, <gsherwood@...> wrote:
>>
>> Samisa,
>> Thanks for the response. I mentioned the _t because when I posted the
>> message, the ONLY difference between the two services was their names. One
>> has the _t and the other does not. So it seemed likely to me that the
>> different behavior was related to their different names. This is not a big
>> problem for me because I think I have a workaround. I guessed that the
>> Axis2/C team would either recognize what's happening here, or would want to
>> understand it sometime.
>
> Thank you for the input. I think there might be a bug/issue in handling the
> service names with special characters such as '_'. Need to look into this.
> If you could raise a Jira, that might be useful.

I checked with a service having _t as part of its name. I could not
recreate the problem. I also strongly believe that the problem is not
due to _t.

Can you send the services.xml file if possible? Is there any other
libraries linked to your services?

Regards,
Shankar

> Samisa...
>

--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Re: client side memory management

2009-12-13T23:28:04Z

Sam Carleton wrote:
> I am looking at the hello.c sample and seeing a lot of things that are
> never freed. I am also not seeing any rules stated on who is
> responsible for freeing memory on things.
See whether this would help [1]

Thanks,
Damitha
[1]
http://damithakumarage.wordpress.com/2009/03/07/memory-handling-conventions-in-axis2c/

>
> For example, in the hello.c code an axis2_options_t *options is
> created but at no point is it freed. Is it automatically freed
> when axutil_env_free() is called or is that an oversight in the example?
>
> Another example is in the build_om_request method, it looks like
> axiom_element_create() creates both the axiom_node_t* greet_om_node
> and axiom_element_t * greet_om_ele, but at no point do I see either
> being freed. Does the axis2_svc_client_send_receive() free them or is
> this also an oversight in the example?
>
> Sam

--
__________________________________________________________________

Damitha Kumarage
Technical Lead; WSO2 Inc.
"Oxygenating the Web Service Platform; " http://www.wso2.com/

blog: " http://damithakumarage.wordpress.com/
__________________________________________________________________

Getting the HTTP Status Codes

2009-12-13T19:55:07Z

I am working with the Axis2/C client. The web server can reply with a number of different HTTP Status Codes, HTTP_UNAUTHORIZED or HTTP_MOVED_PERMANENTLY. It looks like in both cases env->error->error_number is AXIS2_ERROR_HTTP_CLIENT_TRANSPORT_ERROR (74). Is there any way to get to the actual HTTP Status Code?

Sam

client side memory management

2009-12-13T06:29:15Z

I am looking at the hello.c sample and seeing a lot of things that are never freed. I am also not seeing any rules stated on who is responsible for freeing memory on things.

For example, in the hello.c code an axis2_options_t *options is created but at no point is it freed. Is it automatically freed when axutil_env_free() is called or is that an oversight in the example?

Another example is in the build_om_request method, it looks like axiom_element_create() creates both the axiom_node_t* greet_om_node and axiom_element_t * greet_om_ele, but at no point do I see either being freed. Does the axis2_svc_client_send_receive() free them or is this also an oversight in the example?

Sam

Re: DLL path for libTestCases_t.so is set to libTestCases.so

2009-12-13T01:54:48Z

On Sat, Dec 5, 2009 at 7:46 AM, <gsherwood@...> wrote:

Samisa,
Thanks for the response. I mentioned the _t because when I posted the message, the ONLY difference between the two services was their names. One has the _t and the other does not. So it seemed likely to me that the different behavior was related to their different names. This is not a big problem for me because I think I have a workaround. I guessed that the Axis2/C team would either recognize what's happening here, or would want to understand it sometime.

Thank you for the input. I think there might be a bug/issue in handling the service names with special characters such as '_'. Need to look into this. If you could raise a Jira, that might be useful.

Samisa...

Re: [Axis2[ Time for a release?

2009-12-13T01:51:01Z

On Sun, Dec 6, 2009 at 8:27 AM, Selvaratnam Uthaiyashankar <uthaiyashankar@...> wrote:

On Fri, Dec 4, 2009 at 11:13 PM, Samisa Abeysinghe <samisa@...> wrote:
> I meant to say, Axis2!

> Samisa...
>
> On Fri, Dec 4, 2009 at 11:08 PM, Samisa Abeysinghe <samisa@...> wrote:
>>
>> Folks,
>> I looked at the Jiras after a loooong time and seems that there are
>> quite a number of them as well as few ones with patches from users.
>> May be it is a good time to fire up a new release. Thoughts are
>> welcome.

+1. I'll go through the Jira and fix them.

What will be the version number? 1.7.0?

Yes, I think it should be 1.7, as we have few new features.

Samisa...

Regards,
Shankar

>> Thanks,
>> Samisa...
>> --
>> Samisa Abeysinghe
>> Director, Engineering - WSO2 Inc.
>>
>> http://www.wso2.com/ - "The Open Source SOA Company"
>
>
>
> --
> Samisa Abeysinghe
> Director, Engineering - WSO2 Inc.
>
> http://www.wso2.com/ - "The Open Source SOA Company"
>

--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

--
Samisa Abeysinghe
Director, Engineering - WSO2 Inc.

http://www.wso2.com/ - "The Open Source SOA Company"

Re: .Net client can call Axis2/C service, Axis2/C client cannot

2009-12-12T17:34:41Z

Damitha,

Thank you! It is ParataMgr, don't know how I missed that one. I do appreciate the help and all the help in general wso2.com has provided me over the last year, it has been great!

Sam

On Sat, Dec 12, 2009 at 2:01 PM, Damitha Kumarage <damitha@...> wrote:

Check your service name. Is it parataMgr or ParataMgr?
Damitha

Re: .Net client can call Axis2/C service, Axis2/C client cannot

2009-12-12T11:01:14Z

Check your service name. Is it parataMgr or ParataMgr?
Damitha
Sam Carleton wrote:

> Selvaratnam,
>
> Thank you for your help!!!! I was assuming the issue was related to
> the header in the request.. Here is the TCPMon log for the Axis2/C
> client to Axis2/C service that does not work:
>
> ########## *************** BEGIN *************** ##########
>
> POST /axis2/services/parataMgr HTTP/1.1
> User-Agent: Axis2C/1.6.0
> SOAPAction: "urn:mmpp:parataMgr/getVersionCheck"
> Content-Length: 472
> Content-Type: text/xml;charset=UTF-8
> Host: 127.0.0.1:8041 <http://127.0.0.1:8041>
>
> <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
> <soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:To>http://localhost:8041/axis2/services/parataMgr</wsa:To>
> <wsa:Action>urn:mmpp:parataMgr/getVersionCheck</wsa:Action>
>
> <wsa:MessageID>urn:uuid:a6418349-1d84-43d4-801f-98333d974be4</wsa:MessageID>
> </soapenv:Header>
> <soapenv:Body>
> <n:getVersionCheck xmlns:n="urn:mmpp:parataMgr"></n:getVersionCheck>
> </soapenv:Body>
> </soapenv:Envelope>
>
> ///////////////////////////////////
>
> HTTP/1.1 500 Internal Server Error
> Date: Sat, 12 Dec 2009 16:02:42 GMT
> Server: Apache/2.2.11 (Win32) Axis2C/1.6.0 PHP/5.2.5
> Content-Length: 425
> Connection: close
> Content-Type: text/xml
>
> <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
> <soapenv:Body>
> <soapenv:Fault>
> <faultcode>soapenv:Server</faultcode>
> <faultstring>Service Not Found</faultstring>
> <detail>
> <Exception>Service Not Found, Endpoint referance address is
> http://localhost:8041/axis2/services/parataMgr and wsa actions is
> urn:mmpp:parataMgr/getVersionCheck</Exception>
> </detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
>
> ########## *************** END *************** ##########
>
> Here is the TCPMon log for the .Net WCF client to Axis2/C service that
> works just fine
>
> ########## *************** BEGIN *************** ##########
>
> POST /axis2/services/ParataMgr HTTP/1.1
> Content-Type: text/xml; charset=utf-8
> VsDebuggerCausalityData:
> uIDPoxSbbbbBUrlHuNPN/pxDwgwAAAAA34KEJ2oVP0O6Dw1Dp8a2Sfbfz3XaB2ZDq08omNFFhx8ACQAA
> SOAPAction: "urn:mmpp:parataMgr/getVersionCheck"
> Host: 127.0.0.1:8041 <http://127.0.0.1:8041>
> Content-Length: 238
> Expect: 100-continue
> Connection: Keep-Alive
>
> <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
> <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> <getVersionCheck xmlns="urn:mmpp:parataMgr"/>
> </s:Body>
> </s:Envelope>
>
> ///////////////////////////////////
>
> HTTP/1.1 100 Continue
>
> HTTP/1.1 200 OK
> Date: Sat, 12 Dec 2009 15:58:09 GMT
> Server: Apache/2.2.11 (Win32) Axis2C/1.6.0 PHP/5.2.5
> Content-Length: 230
> Keep-Alive: timeout=5, max=100
> Connection: Keep-Alive
> Content-Type: text/xml
>
> <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
> <soapenv:Body>
> <n:getVersionCheckResponse xmlns:n="urn:mmpp:parataMgr">
> <version>100</version>
> </n:getVersionCheckResponse>
> </soapenv:Body>
> </soapenv:Envelope>
>

Re: .Net client can call Axis2/C service, Axis2/C client cannot

2009-12-12T08:05:43Z

Selvaratnam,

Thank you for your help!!!! I was assuming the issue was related to the header in the request.. Here is the TCPMon log for the Axis2/C client to Axis2/C service that does not work:

########## *************** BEGIN *************** ##########

POST /axis2/services/parataMgr HTTP/1.1

User-Agent: Axis2C/1.6.0

SOAPAction: "urn:mmpp:parataMgr/getVersionCheck"

Content-Length: 472

Content-Type: text/xml;charset=UTF-8

Host: 127.0.0.1:8041

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

<soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">

<wsa:To>http://localhost:8041/axis2/services/parataMgr</wsa:To>

<wsa:Action>urn:mmpp:parataMgr/getVersionCheck</wsa:Action>

<wsa:MessageID>urn:uuid:a6418349-1d84-43d4-801f-98333d974be4</wsa:MessageID>

</soapenv:Header>

<soapenv:Body>

<n:getVersionCheck xmlns:n="urn:mmpp:parataMgr"></n:getVersionCheck>

</soapenv:Body>

</soapenv:Envelope>

///////////////////////////////////

HTTP/1.1 500 Internal Server Error

Date: Sat, 12 Dec 2009 16:02:42 GMT

Server: Apache/2.2.11 (Win32) Axis2C/1.6.0 PHP/5.2.5

Content-Length: 425

Connection: close

Content-Type: text/xml

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

<soapenv:Body>

<soapenv:Fault>

<faultcode>soapenv:Server</faultcode>

<faultstring>Service Not Found</faultstring>

<Exception>Service Not Found, Endpoint referance address is http://localhost:8041/axis2/services/parataMgr and wsa actions is urn:mmpp:parataMgr/getVersionCheck</Exception>

</detail>

</soapenv:Fault>

</soapenv:Body>

</soapenv:Envelope>

########## *************** END *************** ##########

Here is the TCPMon log for the .Net WCF client to Axis2/C service that works just fine

########## *************** BEGIN *************** ##########

POST /axis2/services/ParataMgr HTTP/1.1

Content-Type: text/xml; charset=utf-8

VsDebuggerCausalityData: uIDPoxSbbbbBUrlHuNPN/pxDwgwAAAAA34KEJ2oVP0O6Dw1Dp8a2Sfbfz3XaB2ZDq08omNFFhx8ACQAA

SOAPAction: "urn:mmpp:parataMgr/getVersionCheck"

Host: 127.0.0.1:8041

Content-Length: 238

Expect: 100-continue

Connection: Keep-Alive

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">

<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

</s:Body>

</s:Envelope>

///////////////////////////////////

HTTP/1.1 100 Continue

HTTP/1.1 200 OK

Date: Sat, 12 Dec 2009 15:58:09 GMT

Server: Apache/2.2.11 (Win32) Axis2C/1.6.0 PHP/5.2.5

Content-Length: 230

Keep-Alive: timeout=5, max=100

Connection: Keep-Alive

Content-Type: text/xml

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

<soapenv:Body>

<n:getVersionCheckResponse xmlns:n="urn:mmpp:parataMgr">

</n:getVersionCheckResponse>

</soapenv:Body>

</soapenv:Envelope>

Re: What is needed to distribute a Axis/2 Client

2009-12-12T07:53:26Z

On Fri, Dec 11, 2009 at 8:48 PM, Sam Carleton
<scarleton@...> wrote:
> I have been using Axis2/C sololy on the server side until now (I had been
> using Silverlight as the client). I now need to use Axis2/C on the client
> side but need to know what exactly needs to be in the clients repository.
> What files are actually needed?

You need axis2.xml, lib and modules.

Regards,
Shankar

> Sam

--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Re: in-only service operation

2009-12-12T07:51:34Z

Hi,

You have to set the operation as In-only MEP. Please have a look at
notify service's services.xml

Regards,
Shankar

On Sat, Dec 12, 2009 at 12:12 AM, Atanacio Reyes <areyesv@...> wrote:
> Hi:
> I have only a question:
> How I can do an operation service with only request but no response in server side?
>
>
>
>
>

--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Re: .Net client can call Axis2/C service, Axis2/C client cannot

2009-12-12T07:46:34Z

Hi Sam,

I assume, you are thinking that the problem is due to WS-Addressing..

What is the service you are using? Is it Axis2/C? And what is the
error message you are getting? If the server side is axis2/C, you will
not get any errors due to addressing headers.

You can disable WS-Addressing. Addressing module is engaged globally
in axis2.xml

Regards,
Shankar

On Sat, Dec 12, 2009 at 9:21 AM, Sam Carleton
<scarleton@...> wrote:

> For about a year now I have been using Axis2/C on the server side with a
> great deal of success. I am now trying to use it on the client side and
> things are not working. I just tried with .Net's WCF and it worked fine,
> looking at the envelopes, there is an obvious difference:
> .Net WCF Envelope:
>   <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
>    <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
>    <getVersionCheck xmlns="urn:mmpp:parataMgr"/>
>    </s:Body>
>   </s:Envelope>
> Axis2/C Envelope:
>   <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
>    <soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
>    <wsa:To>http://localhost:8041/axis2/services/parataMgr</wsa:To>
>    <wsa:Action>urn:mmpp:parataMgr/getVersionCheck</wsa:Action>
>
> <wsa:MessageID>urn:uuid:57dbfc1e-a42e-4501-894b-7e6bf4a8f2bb</wsa:MessageID>
>    </soapenv:Header>
>    <soapenv:Body>
>    <n:getVersionCheck xmlns:n="urn:mmpp:parataMgr"></n:getVersionCheck>
>    </soapenv:Body>
>   </soapenv:Envelope>
> I am using the auto generated method signature for
> "getVersionCheck|urn:mmpp:parataMgr" operation, I used these options to
> generate the code:
> -uri ParataMgr.wsdl -d adb -u
> And here is the schema from the WSDL:
>    <xsd:element name="getVersionCheck">
>    <xsd:complexType>
>    <xsd:sequence>
>    </xsd:sequence>
>    </xsd:complexType>
>    </xsd:element>
>    <xsd:element name="getVersionCheckResponse">
>    <xsd:complexType>
>    <xsd:sequence>
>    <xsd:element name="version" type="xsd:int"></xsd:element>
>    </xsd:sequence>
>    </xsd:complexType>
>    </xsd:element>
>

--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

.Net client can call Axis2/C service, Axis2/C client cannot

2009-12-11T19:51:25Z

For about a year now I have been using Axis2/C on the server side with a great deal of success. I am now trying to use it on the client side and things are not working. I just tried with .Net's WCF and it worked fine, looking at the envelopes, there is an obvious difference:

.Net WCF Envelope:

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">

<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

</s:Body>

</s:Envelope>

Axis2/C Envelope:

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

<soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">

<wsa:To>http://localhost:8041/axis2/services/parataMgr</wsa:To>

<wsa:Action>urn:mmpp:parataMgr/getVersionCheck</wsa:Action>

<wsa:MessageID>urn:uuid:57dbfc1e-a42e-4501-894b-7e6bf4a8f2bb</wsa:MessageID>

</soapenv:Header>

<soapenv:Body>

<n:getVersionCheck xmlns:n="urn:mmpp:parataMgr"></n:getVersionCheck>

</soapenv:Body>

</soapenv:Envelope>

I am using the auto generated method signature for "getVersionCheck|urn:mmpp:parataMgr" operation, I used these options to generate the code:

-uri ParataMgr.wsdl -d adb -u

And here is the schema from the WSDL:

<xsd:element name="getVersionCheck">

<xsd:complexType>

<xsd:sequence>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

<xsd:element name="getVersionCheckResponse">

<xsd:complexType>

<xsd:sequence>

<xsd:element name="version" type="xsd:int"></xsd:element>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

in-only service operation

2009-12-11T10:42:39Z

Hi:
I have only a question:
How I can do an operation service with only request but no response in server side?

Re: What is needed to distribute a Axis/2 Client

2009-12-11T08:14:06Z

I reread your question... If you're asking about how to distribute an existing client, I have not tried that yet.
George

-------------- Original message from gsherwood@...: --------------

Sam,
I built a test client by starting with the hello service from Section 1 of the Axis2/C manual and then adapting it to my service. In addition to the client source, you need $AXIS2C_HOME/include/axis2-1.6.0/ and $AXIS2C_HOME/lib (on Linux). See Section 1.2.4 Compiling the Client for details.
George Sherwood
Testcover.com

-------------- Original message from Sam Carleton <scarleton@...>: --------------

I have been using Axis2/C sololy on the server side until now (I had been using Silverlight as the client). I now need to use Axis2/C on the client side but need to know what exactly needs to be in the clients repository. What files are actually needed?

Sam

Re: What is needed to distribute a Axis/2 Client

2009-12-11T08:08:50Z

Sam,
I built a test client by starting with the hello service from Section 1 of the Axis2/C manual and then adapting it to my service. In addition to the client source, you need $AXIS2C_HOME/include/axis2-1.6.0/ and $AXIS2C_HOME/lib (on Linux). See Section 1.2.4 Compiling the Client for details.
George Sherwood
Testcover.com

-------------- Original message from Sam Carleton <scarleton@...>: --------------

I have been using Axis2/C sololy on the server side until now (I had been using Silverlight as the client). I now need to use Axis2/C on the client side but need to know what exactly needs to be in the clients repository. What files are actually needed?

Sam

What is needed to distribute a Axis/2 Client

2009-12-11T07:18:24Z

I have been using Axis2/C sololy on the server side until now (I had been using Silverlight as the client). I now need to use Axis2/C on the client side but need to know what exactly needs to be in the clients repository. What files are actually needed?

Sam

Re: Getting request IP address

2009-12-10T22:30:01Z

Hello Murphey,

I got the address using axis2_msg_ctx_get_property. For that I needed
a pointer to axis2_msg_ctx_t, which i updated in my
"axis2_skel_xxxxxx.h" file

Sample: "axis2_skel_KeyExchange.h"

adb_DoKeyExchangeResponse_t*
axis2_skel_KeyExchange_DoKeyExchange (const axutil_env_t *env ,
adb_DoKeyExchange_t*
doKeyExchange,axis2_msg_ctx_t *msg_ctx);

Similarly in my "axis2_skel_KeyExchange.c" file

updated the call,

adb_DoKeyExchangeResponse_t* axis2_skel_KeyExchange_DoKeyExchange
(const axutil_env_t *env,
adb_DoKeyExchange_t* doKeyExchange,axis2_msg_ctx_t *msg_ctx)
{

and with the following code got the address

axutil_property_t *peer = axis2_msg_ctx_get_property (msg_ctx, env,
AXIS2_SVR_PEER_IP_ADDR);
char *remote_ip = (char *) axutil_property_get_value (peer, env);
AXIS2_LOG_INFO (env->log, "Got a call from %s", remote_ip);

Regards,
Nabeel Ahsan

On Fri, Dec 11, 2009 at 1:24 AM, Murphey McCloy <MMcCloy@...> wrote:

> Hello.
>
> I am using axis2c 1.6 and I am trying to get the ip address (or hostname) of the host that generate the web service requests. I was attempting to use axis2_msg_ctx_get_from and then axis2_endpoint_ref_get_address to do this. Unfortunately this is giving me the address of the server, not the client.
>
> Am I mis-using this API call? Is there a better/different way to get this information?
>
> This is how my code looks:
>
> fromRef = axis2_msg_ctx_get_from(pMsgCtx, pEnv);
> if (fromRef) {
> from = (axis2_char_t*)axis2_endpoint_ref_get_address(fromRef, pEnv);
> }
>
> Any help is greatly appreciated.
>
> Thanks,
>
> Murphey
>

Getting request IP address

2009-12-10T12:24:42Z

Hello.

I am using axis2c 1.6 and I am trying to get the ip address (or hostname) of the host that generate the web service requests. I was attempting to use axis2_msg_ctx_get_from and then axis2_endpoint_ref_get_address to do this. Unfortunately this is giving me the address of the server, not the client.

Am I mis-using this API call? Is there a better/different way to get this information?

This is how my code looks:

fromRef = axis2_msg_ctx_get_from(pMsgCtx, pEnv);
if (fromRef) {
from = (axis2_char_t*)axis2_endpoint_ref_get_address(fromRef, pEnv);
}

Any help is greatly appreciated.

Thanks,

Murphey

Re: [Axis2[ Time for a release?

2009-12-05T18:57:51Z

On Fri, Dec 4, 2009 at 11:13 PM, Samisa Abeysinghe <samisa@...> wrote:
> I meant to say, Axis2!

> Samisa...
>
> On Fri, Dec 4, 2009 at 11:08 PM, Samisa Abeysinghe <samisa@...> wrote:
>>
>> Folks,
>> I looked at the Jiras after a loooong time and seems that there are
>> quite a number of them as well as few ones with patches from users.
>> May be it is a good time to fire up a new release. Thoughts are
>> welcome.

+1. I'll go through the Jira and fix them.

What will be the version number? 1.7.0?

Regards,
Shankar

>> Thanks,
>> Samisa...
>> --
>> Samisa Abeysinghe
>> Director, Engineering - WSO2 Inc.
>>
>> http://www.wso2.com/ - "The Open Source SOA Company"
>
>
>
> --
> Samisa Abeysinghe
> Director, Engineering - WSO2 Inc.
>
> http://www.wso2.com/ - "The Open Source SOA Company"
>

--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Re: DLL path for libTestCases_t.so is set to libTestCases.so

2009-12-04T18:16:20Z

Samisa,
Thanks for the response. I mentioned the _t because when I posted the message, the ONLY difference between the two services was their names. One has the _t and the other does not. So it seemed likely to me that the different behavior was related to their different names. This is not a big problem for me because I think I have a workaround. I guessed that the Axis2/C team would either recognize what's happening here, or would want to understand it sometime.
Best regards,
George

-------------- Forwarded Message: --------------
From: Samisa Abeysinghe <samisa@...>
To: Apache AXIS C User List <axis-c-user@...>
Subject: Re: DLL path for libTestCases_t.so is set to libTestCases.so
Date: Fri, 04 Dec 2009 17:19:58 +0000

AFAICT, _t has nothing to do with the problem you are facing.

Samisa...

On Wed, Oct 28, 2009 at 5:19 AM, <gsherwood@...> wrote:

I have set up two services which (for now) are identical except for their names, TestCases and TestCases_t. The choice of the suffix _t is historical and has nothing to do with type names. libTestCases.so and libTestCases_t.so are placed in their respective directories:
/usr/local/www/64.232.245.115/axis2c/services/TestCases and
/usr/local/www/64.232.245.115/axis2c/services/TestCases_t
However, log entries indicate the DLL path for libTestCases_t.so is not getting set correctly. Relevant entries include the following.
[Tue Oct 27 19:22:33 2009] [debug] svc_builder.c(318) DLL path is : /usr/local/www/64.232.245.115/axis2c/services/TestCases/libTestCases.so
[Tue Oct 27 19:22:33 2009] [debug] om_element.c(1114) There are no child elements for the node
[Tue Oct 27 19:22:33 2009] [debug] svc_builder.c(318) DLL path is : /usr/local/www/64.232.245.115/axis2c/services/TestCases_t/libTestCases.so
[Tue Oct 27 19:22:33 2009] [debug] om_element.c(1114) There are no child elements for the node
...
[Tue Oct 27 19:22:33 2009] [error] class_loader.c(162) Loading shared library /usr/local/www/64.232.245.115/axis2c/services/TestCases_t/libTestCases.so Failed. DLERROR IS /usr/local/www/64.232.245.115/axis2c/services/TestCases_t/libTestCases.so: cannot open shared object file: No such file or directory
If I depart from the usual naming convention (i.e. libTestCases_t.so for TestCases_t), and use the name in the DLL path instead (libTestCases.so), then the service works.
Can anyone help with answers to these questions?
1. Is this behavior (dropping the _t suffix) a bug or a feature?
2. Is setting the name to the DLL path indicated in the log a legitimate workaround?
3. Am I likely to encounter future trouble with a service name ending in _t?
Thanks,
George Sherwood
Testcover.com

--
Samisa Abeysinghe
Director, Engineering - WSO2 Inc.

http://www.wso2.com/ - "The Open Source SOA Company"

Re: using faults w/ wsdl2c

2009-12-04T16:26:07Z

On Fri, Dec 4, 2009 at 11:09 PM, Sam Carleton <scarleton@...> wrote:

Dimuthu,

Where EXACTLY does one find the latest WSDL2C code? Is it in an build or is it in the Axis2/Java SVN repository?

Axis2 svn.

Samisa...

Sam

On Thu, Dec 3, 2009 at 10:57 PM, Dimuthu Gamage <dimuthuc@...> wrote:

Hi,

If you use the latest axis2 WSDL2C generator code, you don't need to create soap fault message manually as the generated code provide lot of support in generating fault message.

Please have a look at this for the improved API, http://www.dimuthu.org/blog/2009/02/09/code-generate-custom-soap-faults-for-axis2c/

Thanks
Dimuthu

On Wed, Nov 18, 2009 at 3:49 AM, Doug Price <Doug.Price@...> wrote:

While I see that this approach allows the creation of user-defined fault types, is it possible to also use it to specify the standard SOAP-ENV:Fault? I see a struct named axiom_soap_fault_t in the distribution, but I can't seem to return it from the axis2_svc_skel_*_on_fault() function because it requires a pointer to the SOAP body to create one. Is there some other way to return a standard SOAP fault from a service?

--
Doug Price
Research Director | Presagis

T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399

DISCLAIMER: This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and/or proprietary information. Do not read, copy, or disseminate this message unless you are the addressee. Any unauthorized review, use, disclosure or distribution is strictly prohibited. If you have received this message in error, please contact the sender by reply e-mail and delete the original and any copies from your system.

-----Original Message-----

From: Amir Mousavizadegan [mailto:amir.mousavizadegan@...]

Sent: Tuesday, November 17, 2009 10:29 AM
To: Apache AXIS C User List
Subject: Re: using faults w/ wsdl2c

I did not write the sample codes nor the document, however in order to
get it working, you have to change the body of the generated code, or
create a replacement function as I did.
thx
Amir
----- Original Message -----
From: "Doug Price" <Doug.Price@...>
To: "Apache AXIS C User List" <axis-c-user@...>
Sent: Tuesday, November 17, 2009 11:05 AM
Subject: RE: using faults w/ wsdl2c

Just what I was looking for. Thanks so much.

A quick follow up question on the code though. Is there a reason that
axis2_svc_skel_Division_on_fault() doesn't use the adv_divFault api to
create the fault?

--
Doug Price
Research Director | Presagis

T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399

DISCLAIMER: This e-mail message is for the sole use of the intended
recipient(s) and may contain confidential and/or proprietary information. Do
not read, copy, or disseminate this message unless you are the addressee.
Any unauthorized review, use, disclosure or distribution is strictly
prohibited. If you have received this message in error, please contact the
sender by reply e-mail and delete the original and any copies from your
system.

-----Original Message-----

From: Amir Mousavizadegan [mailto:amir.mousavizadegan@...]
Sent: Tuesday, November 17, 2009 7:52 AM
To: Apache AXIS C User List
Subject: Re: using faults w/ wsdl2c

Please see attached document
----- Original Message -----
From: "Doug Price" <Doug.Price@...>
To: <axis-c-user@...>
Sent: Monday, November 16, 2009 4:47 PM
Subject: using faults w/ wsdl2c

I created a simple web service w/ Axis2c using wsdl2c on a WSDL file I
created in Eclipse. The default functionality of this works fine. However,
now I'd like to incorporate faults into my SOAP messages. I created a fault
type in my WSDL and wsdl2c creates the wrappers for the fault message, but
the service skeleton and client stubs files seem to hard coded to assume no
faults are ever sent / received. For example, the client axis2_stub_op_*()
function takes my request message type and returns my response message type,
but doesn't seem to account for my fault type. Modifying the code, I can
see that the fault is received and correctly deserialized, but I'll have to
continually hand edit the axis2_stub*.c and my client.c file as I make
modifications to my WSDL in order to make this work.

The same is true on the service side w/ the axis2_skel*() functions. Am I
missing something here, or are faults not supported w/ wsdl2c?

--
Doug Price
Research Director | Presagis

T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399

DISCLAIMER: This e-mail message is for the sole use of the intended
recipient(s) and may contain confidential and/or proprietary information. Do
not read, copy, or disseminate this message unless you are the addressee.
Any unauthorized review, use, disclosure or distribution is strictly
prohibited. If you have received this message in error, please contact the
sender by reply e-mail and delete the original and any copies from your
system.

--
Thanks,
Dimuthu Gamage

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

--
Samisa Abeysinghe
Director, Engineering - WSO2 Inc.

http://www.wso2.com/ - "The Open Source SOA Company"

Re: echo_rest and DELETE http_method

2009-12-04T10:07:41Z

Hi,
I also try the REST delete and it is failing. Looks like a bug in the code in trunk. Can you please report this bug in axis2/c jira

Thanks
Dimuthu

On Wed, Nov 25, 2009 at 2:09 AM, Ilia Gilderman <ilia.gilderman@...> wrote:

Yes, sure I did this

From: Supun Kamburugamuva [mailto:supun06@...]
Sent: Tuesday, November 24, 2009 10:36 PM
To: Apache AXIS C User List
Subject: Re: echo_rest and DELETE http_method

Hi,

Not sure weather you have done this, but AFAIK you need to edit the services.xml file to make them work.

Thanks,
Supun.

On Fri, Nov 20, 2009 at 7:19 PM, Ilia Gilderman <ilia.gilderman@...> wrote:

Hi

It looks like the DELETE pieces does not work. I tried with simple_axis2_server and mod_axis2 modules and echo_rest example. When I'm adding –mDELETE option I got internal servers error (500) from httpd. Is it known issue? What can be wrong with the sample?

Thanks

Ilia Gilderman, VP Product Development
xeround

4 Derech Hahoresh St.
P.O. Box 12621
Yehud, 56470 Israel
Office: +972-3-5390617
Mobile: +972-54-4878091

ilia.gilderman@...

--
Software Engineer, WSO2 Inc
http://wso2.org
supunk.blogspot.com

--
Thanks,
Dimuthu Gamage

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

Re: rampart/c http tutorial

2009-12-04T09:54:48Z

On Fri, 2009-12-04 at 22:59 +0530, Samisa Abeysinghe wrote:

> You need to enable https in the axis2.xml conf file
>

Ah, thanks one step closer.

I still need to figure out how to see the exact xml that is being sent
and received from the server. I am getting a fault back and I suspect it
is because the WSSE header information is not correct. I should be
sending something like this to the server:

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope"
xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:c14n="http://www.w3.org/2001/10/xml-exc-c14n#"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401..."
xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis..."
xmlns:negdb="http://secure.negativeaddress.research.att.com/"
>
<SOAP-ENV:Header>
<wsse:Security SOAP-ENV:mustUnderstand="true">
<wsse:UsernameToken
wsu:Id="apache"
>
<wsse:Username>apache</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss...">
password
</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
...
While I think I've engaged rampart properly to add the header
information, the debugging log does not include the data sent to the
server.

ASE

[Axis2[ Time for a release?

2009-12-04T09:43:11Z

I meant to say, Axis2!

Samisa...

On Fri, Dec 4, 2009 at 11:08 PM, Samisa Abeysinghe <samisa@...> wrote:

Folks,
I looked at the Jiras after a loooong time and seems that there are quite a number of them as well as few ones with patches from users.

May be it is a good time to fire up a new release. Thoughts are welcome.

Thanks,
Samisa...

--
Samisa Abeysinghe
Director, Engineering - WSO2 Inc.

http://www.wso2.com/ - "The Open Source SOA Company"

--
Samisa Abeysinghe
Director, Engineering - WSO2 Inc.

http://www.wso2.com/ - "The Open Source SOA Company"

Re: using faults w/ wsdl2c

2009-12-04T09:39:57Z

Dimuthu,

Where EXACTLY does one find the latest WSDL2C code? Is it in an build or is it in the Axis2/Java SVN repository?

Sam

On Thu, Dec 3, 2009 at 10:57 PM, Dimuthu Gamage <dimuthuc@...> wrote:

Hi,

If you use the latest axis2 WSDL2C generator code, you don't need to create soap fault message manually as the generated code provide lot of support in generating fault message.

Please have a look at this for the improved API, http://www.dimuthu.org/blog/2009/02/09/code-generate-custom-soap-faults-for-axis2c/

Thanks
Dimuthu

On Wed, Nov 18, 2009 at 3:49 AM, Doug Price <Doug.Price@...> wrote:

While I see that this approach allows the creation of user-defined fault types, is it possible to also use it to specify the standard SOAP-ENV:Fault? I see a struct named axiom_soap_fault_t in the distribution, but I can't seem to return it from the axis2_svc_skel_*_on_fault() function because it requires a pointer to the SOAP body to create one. Is there some other way to return a standard SOAP fault from a service?

--
Doug Price
Research Director | Presagis

T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399

DISCLAIMER: This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and/or proprietary information. Do not read, copy, or disseminate this message unless you are the addressee. Any unauthorized review, use, disclosure or distribution is strictly prohibited. If you have received this message in error, please contact the sender by reply e-mail and delete the original and any copies from your system.

-----Original Message-----

From: Amir Mousavizadegan [mailto:amir.mousavizadegan@...]

Sent: Tuesday, November 17, 2009 10:29 AM
To: Apache AXIS C User List
Subject: Re: using faults w/ wsdl2c

I did not write the sample codes nor the document, however in order to
get it working, you have to change the body of the generated code, or
create a replacement function as I did.
thx
Amir
----- Original Message -----
From: "Doug Price" <Doug.Price@...>
To: "Apache AXIS C User List" <axis-c-user@...>
Sent: Tuesday, November 17, 2009 11:05 AM
Subject: RE: using faults w/ wsdl2c

Just what I was looking for. Thanks so much.

A quick follow up question on the code though. Is there a reason that
axis2_svc_skel_Division_on_fault() doesn't use the adv_divFault api to
create the fault?

--
Doug Price
Research Director | Presagis

T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399

DISCLAIMER: This e-mail message is for the sole use of the intended
recipient(s) and may contain confidential and/or proprietary information. Do
not read, copy, or disseminate this message unless you are the addressee.
Any unauthorized review, use, disclosure or distribution is strictly
prohibited. If you have received this message in error, please contact the
sender by reply e-mail and delete the original and any copies from your
system.

-----Original Message-----

From: Amir Mousavizadegan [mailto:amir.mousavizadegan@...]
Sent: Tuesday, November 17, 2009 7:52 AM
To: Apache AXIS C User List
Subject: Re: using faults w/ wsdl2c

Please see attached document
----- Original Message -----
From: "Doug Price" <Doug.Price@...>
To: <axis-c-user@...>
Sent: Monday, November 16, 2009 4:47 PM
Subject: using faults w/ wsdl2c

I created a simple web service w/ Axis2c using wsdl2c on a WSDL file I
created in Eclipse. The default functionality of this works fine. However,
now I'd like to incorporate faults into my SOAP messages. I created a fault
type in my WSDL and wsdl2c creates the wrappers for the fault message, but
the service skeleton and client stubs files seem to hard coded to assume no
faults are ever sent / received. For example, the client axis2_stub_op_*()
function takes my request message type and returns my response message type,
but doesn't seem to account for my fault type. Modifying the code, I can
see that the fault is received and correctly deserialized, but I'll have to
continually hand edit the axis2_stub*.c and my client.c file as I make
modifications to my WSDL in order to make this work.

The same is true on the service side w/ the axis2_skel*() functions. Am I
missing something here, or are faults not supported w/ wsdl2c?

--
Doug Price
Research Director | Presagis

T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399

DISCLAIMER: This e-mail message is for the sole use of the intended
recipient(s) and may contain confidential and/or proprietary information. Do
not read, copy, or disseminate this message unless you are the addressee.
Any unauthorized review, use, disclosure or distribution is strictly
prohibited. If you have received this message in error, please contact the
sender by reply e-mail and delete the original and any copies from your
system.

--
Thanks,
Dimuthu Gamage

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

Time for a release?

2009-12-04T09:38:27Z

Folks,

I looked at the Jiras after a loooong time and seems that there are quite a number of them as well as few ones with patches from users.

May be it is a good time to fire up a new release. Thoughts are welcome.

Thanks,

Samisa...

--
Samisa Abeysinghe
Director, Engineering - WSO2 Inc.

http://www.wso2.com/ - "The Open Source SOA Company"