Return-Path: 
 <axis-c-dev-return-16750-apmail-ws-axis-c-dev-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org
Received: (qmail 68564 invoked from network); 28 Jan 2008 07:48:52 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 28 Jan 2008 07:48:52 -0000
Received: (qmail 67465 invoked by uid 500); 28 Jan 2008 07:48:42 -0000
Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org
Received: (qmail 67446 invoked by uid 500); 28 Jan 2008 07:48:42 -0000
Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:axis-c-dev-help@ws.apache.org>
list-unsubscribe: <mailto:axis-c-dev-unsubscribe@ws.apache.org>
List-Post: <mailto:axis-c-dev@ws.apache.org>
List-Id: "Apache AXIS C Developers List" <axis-c-dev.ws.apache.org>
Reply-To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Delivered-To: mailing list axis-c-dev@ws.apache.org
Received: (qmail 67435 invoked by uid 99); 28 Jan 2008 07:48:42 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 27 Jan 2008 23:48:42 -0800
X-ASF-Spam-Status: No, hits=1.2 required=10.0
	tests=SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Received: from [209.68.5.15] (HELO relay01.pair.com) (209.68.5.15)
    by apache.org (qpsmtpd/0.29) with SMTP; Mon, 28 Jan 2008 07:48:16 +0000
Received: (qmail 40615 invoked from network); 28 Jan 2008 07:48:20 -0000
Received: from unknown (HELO ?10.100.1.87?) (unknown)
  by unknown with SMTP; 28 Jan 2008 07:48:20 -0000
X-pair-Authenticated: 123.231.21.16
Message-ID: <479D88C2.4030807@wso2.com>
Date: Mon, 28 Jan 2008 13:18:18 +0530
From: Samisa Abeysinghe <samisa@wso2.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Apache AXIS C Developers List <axis-c-dev@ws.apache.org>
Subject: Re: Axis2C support for dynamic operations
References: <0CD5E28A763C8D4D84C690F5C463F94A58EE12@ord-mail.serena.com>
 <47994406.7020004@wso2.com>
 <0CD5E28A763C8D4D84C690F5C463F94A5F19ED@ord-mail.serena.com>
In-Reply-To: <0CD5E28A763C8D4D84C690F5C463F94A5F19ED@ord-mail.serena.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Dave Meier wrote:
> Hi Samisa,
>
> Is there any way to do the equivalent of "any" for a service?  Kind of
> like an "any" element in a schema, except for an operation.  All I need
> is to have the engine call my invoke method and at that point I can
> write all the code that knows how to handle the operation.
>   

You should be able to do that. It is an OM node that is passed to the 
function being invoked. So it is equivalent to an "any" element. You can 
decide to process it whichever way you want.

Thanks,
Samisa...
> If this is not possible, maybe I could alter the axis2 code where it
> looks up the operation and map it to an existing operation, but store
> the original operation name in the context.  So for example, if I have a
> known operation called "Update" and a request comes in called
> "UpdateFoo" I would map this operation to "Update" and store "UpdateFoo"
> somewhere in the context.  So I would have something like the following
> in my services.xml:
>
> <operation name="Update" dynamic="Update*">
> <parameter name="wsamapping">\"\"</parameter>
> </operation>
>
> Then on the response, I would need to make sure it used the original
> "UpdateFoo" name.
>
> I don't mind going off and modifying the axis2 code for my purposes to
> make this work.  Can you point me to where this would be done?
>
> Thanks,
>
> -Dave.
>
> -----Original Message-----
> From: Samisa Abeysinghe [mailto:samisa@wso2.com] 
> Sent: Thursday, January 24, 2008 6:06 PM
> To: Apache AXIS C Developers List
> Subject: Re: Axis2C support for dynamic operations
>
> This cannot be done with WSDLs because we do not have a WSDL model
> associated with the description hierarchy.
>
> However, you can add support for new operations, dynamically to the
> description hierarchy, in runtime, by accessing configuration. However,
> this may have threading issues. Other problem with dynamic operations,
> is how to map the operation to a function. For current operations this
> happens at the server startup time. We can achieve dynamic operation to
> function mapping using a custom message receiver, which will load the
> functions mapped to the operation on the run.
>
> In short, this can be done. However, that needs lots of engineering.
>
> Thanks,
> Samisa...
>
> Dave Meier wrote:
>   
>> Hi All,
>>  
>> I have a requirement to support dynamically generated wsdls.  Each 
>> wsdl will contain a core set of operations, but will then have 
>> additional operations defined.  I want to use the wsdl with the core 
>> set of operations as my service in Axis2C, but then write code in my 
>> invoke method that will know about the additional new operations as 
>> they will follow a standard pattern.
>>  
>> My question is, how can I get Axis2C to forward the request to my 
>> invoke method, for operations that are not in the services.xml file?
>>  
>> In services.xml could I somehow use wildcards?  Like this:
>>  
>> <operation name="Update*">
>> <parameter name="wsamapping">\"\"</parameter>
>> </operation>
>>  
>> So then a custom wsdl file would be given to a client and it could 
>> have operations like "UpdateFoo" and "UpdateBar", which are not in the
>>     
>
>   
>> services.xml, but the "Update*" could match them.  Then in my invoke 
>> method I could analyze the operation name and know what to do with it 
>> (e.g. "UpdateFoo" would tell me to use "Foo" logic and I would know 
>> how to handle that).
>>  
>> The purpose for this is ease of use to the client.  We have many 
>> operations that are generalized, but if I can generate new wsdl to do 
>> specifically what the user is trying to do, they can use these custom 
>> operation names directly.  This will result in greatly increased 
>> usability.
>>  
>> I think most of the work is on the service in my code, but I need a 
>> way to tell Axis2C to forward along the request even if it is not in 
>> the known set.  Is there a way to do this, or is there a way to modify
>>     
>
>   
>> the code to support this?
>>  
>> Thank you much,
>>  
>> -Dave.
>>  
>>
>> **********************************************************************
>>
>> This email and any files transmitted with it are confidential and 
>> intended solely for the use of the individual or entity to whom they 
>> are addressed. Any unauthorized review, use, disclosure or 
>> distribution is prohibited. If you are not the intended recipient, 
>> please contact the sender by reply e-mail and destroy all copies of 
>> the original message.
>>
>> **********************************************************************
>>
>>  
>>
>> ----------------------------------------------------------------------
>> --
>>
>> No virus found in this incoming message.
>> Checked by AVG Free Edition. 
>> Version: 7.5.516 / Virus Database: 269.19.10/1240 - Release Date: 
>> 1/23/2008 5:47 PM
>>   
>>     
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>
>
>
>   


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org